,0
0,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-9032\n\n### Instruction:\nWorkaround P1 incident\n\n### Response:\n[""Comment 1: [\'test\']""]\nRelated Issues:\n[]\n\n### End'}"
1,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-9031\n\n### Instruction:\nCzesc\r\nProsba o zweryfikowanie wymiany danych miedzy DHP a Exchange.\r\nZdazają sie VT które nie przechodzą dalej przez co potem nie sa dostępne w systemie PCS\r\n \r\nDla przykładu VT : \r\nVT-8016\r\n\r\nVT-8022\r\n\r\nVT-8024\r\n\r\nVT-8025\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: \'Any news ??\'"", ""Comment 3: \'{code:java}System.Web.Services.Protocols.SoapException: Serwer nie może przetworzyć żądania. ---> Nie można przypisać wartości zerowej do członka typu System.Decimal"", \'Comment 4: który jest członkiem typu wartość niezerowalna.   at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message\', \'Comment 5: WebResponse response\', \'Comment 6: Stream responseStream\', \'Comment 7: Boolean asyncCall)   at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName\', \'Comment 8: Object[] parameters)   at PlantAgentService.PCSWSWebReference.PCSIntegrationWebService.GetPendingDeliveries(Int32 numbersOfTickets\', ""Comment 9: Int32 pcsId) in E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\18317313\\\\\\\\DHAPPS25-PCSIT182-JOB1\\\\\\\\DHPAgent\\\\\\\\Web References\\\\\\\\PCSWSWebReference\\\\\\\\Reference.cs:line 2434   at PlantAgentService.PendingDeliveriesService.ImportPendingDeliveries() in E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\18317313\\\\\\\\DHAPPS25-PCSIT182-JOB1\\\\\\\\DHPAgent\\\\\\\\Service\\\\\\\\ServicePendingDeliveries.cs:line 19{code}\'"", \'Comment 10: ""This VT was causing the problem\', \'Comment 11: the field for VtE_EstimatedWeight was null.We updated this field to zero\', \'Comment 12: VT\\\'s have been processed.!image-2023-04-25-19-19-51-287.png!""\', \'Comment 13: ""{code:java}--update dbo.VehicleTicketElement--set VtE_EstimatedWeight = 0--where vte_id in (547641,--547642)SELECT top 100 *  FROM [DH_Exchange].[dbo].[Log]  order by 1 descselect * FROM [DH_Exchange].[dbo].[PendingDeliveryHeader]  order by 1 descWiszące:select E.VtE_Id as PendingDeliveryElementId\', \'Comment 14: E.VtE_VtHId as PendingDeliveryHeaderId\', \'Comment 15: E.VtE_No as Number\', ""Comment 16:  isnull(dbo.VehicleTicketNumber(E.VtE_VtHId) + \'-\' + cast(E.VtE_No as nvarchar(5)),\'\') as PendingDeliveryElementDocumentNumber"", \'Comment 17:  E.VtE_DirectionType as DirectionType\', \'Comment 18:  E.VtE_PackingForm as PackingForm\', \'Comment 19:  isnull(A1.CtA_CstId\', \'Comment 20: E.VtE_CstId) as CustomerId\', \'Comment 21: isnull(C1.Cst_Code\', \'Comment 22: C.Cst_Code) as CustomerCode\', \'Comment 23: isnull(A1.CtA_Name1\', \'Comment 24: A.CtA_Name1) as CustomerName\', \'Comment 25:  E.VtE_ArtId as ArticleId\', \'Comment 26:  E.VtE_EstimatedWeight as EstimateWeight\', \'Comment 27:  E.VtE_Weight as Weight\', \'Comment 28:  E.VtE_UnloadingPlace as UnloadingPlace\', \'Comment 29:  E.VtE_OdEId as OrderElementId\', ""Comment 30: isnull(dbo.OrderNumber(OdE_OdHId) + \'-\' + cast(OdE_No as nvarchar(5))"", ""Comment 31: \'\') as OrderNumber"", \'Comment 32:  E.VtE_CorrectionId as CorrectionPendingDeliveryElementId\', ""Comment 33: isnull(dbo.VehicleTicketNumber(E1.VtE_VtHId) + \'-\' + cast(E1.VtE_No as nvarchar(5))"", ""Comment 34: \'\') as CorrectionPendingDeliveryDocumentNumber"", \'Comment 35:  E.VtE_BagsCount as BagsCount\', \'Comment 36:  E.VtE_BagSize as BagSize\', \'Comment 37:  E.VtE_BagWeight as BagWeight\', \'Comment 38:  E.VtE_QuantityPallet as QuantityPallet\', \'Comment 39:  E.VtE_Description as Description\', \'Comment 40:  E.VtE_Cancel as Cancel\', \'Comment 41:  E.VtE_OtherWeight as OtherWeight\', \'Comment 42:  E.VtE_Quantity as Quantity\', \'Comment 43:  E.VtE_Description2 as Description2\', ""Comment 44:  E.VtE_ExpiryDate as ExpiryDatefrom dbo.VehicleTicketElement Ejoin dbo.MPCSPendingDeliveriesImport on E.VtE_VtHId = VtI_VtHNumerjoin dbo.CustomerCard C on E.VtE_CstId = C.Cst_Idjoin dbo.CustomerAdressCard A on C.Cst_CtAId = A.CtA_Idleft join dbo.OrderElement on E.VtE_OdEId = OdE_Idleft join dbo.OrderHeader on OdE_OdHId = OdH_Idleft join dbo.CustomerCard C1 on OdH_Cst2Id = C1.Cst_Idleft join dbo.CustomerAdressCard A1 on C1.Cst_CtAId = A1.CtA_Idleft join dbo.VehicleTicketElement E1 on E.VtE_Id = E1.VtE_CorrectionIdwhere --VtI_Ticket = \'25f67109-8c5b-46d0-9ce9-a648097a7e1d\'--andisnull(VtI_ConfirmDate,0) = 0 and e.VtE_EstimatedWeight is nullorder by E.VtE_VtHId"", \'Comment 45: E.VtE_No{code}""\', ""Comment 46: \'[[DHP 2.7] Brak VT w Exchange. Lack of VT in exchange database|onenote:https://kotrak.sharepoint.com/sites/erpasysta/Shared%20Documents/Baza%20wiedzy/Baza%20Wiedzy%20-%20ERPSD/Klienci/DEHEUS/DEHEUS%20APPLICATIONS/Polska/Baza%20wiedzy/DHP.one#%5bDHP%202.7%5d%20Brak%20VT%20w%20Exchange.%20Lack%20of&section-id=\\\\\\\\{F3B54834-6A02-4FD8-B2D4-74ADCAEDC4E9}&page-id=\\\\\\\\{7DA7A8BA-842F-45C1-964A-31B80B3F243D}&end] ([Widok sieci Web|https://kotrak.sharepoint.com/sites/erpasysta/_layouts/OneNote.aspx?id=%2Fsites%2Ferpasysta%2FShared%20Documents%2FBaza%20wiedzy%2FBaza%20Wiedzy%20-%20ERPSD&wd=target%28Klienci%2FDEHEUS%2FDEHEUS%20APPLICATIONS%2FPolska%2FBaza%20wiedzy%2FDHP.one%7CF3B54834-6A02-4FD8-B2D4-74ADCAEDC4E9%2F%5BDHP%202.7%5D%20Brak%20VT%20w%20Exchange.%20Lack%20of%7C7DA7A8BA-842F-45C1-964A-31B80B3F243D%2F%29])\']""]\nRelated Issues:\n[]\n\n### End'}"
2,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-9030\n\n### Instruction:\nSince March the 15e, we do not receive Warehouse movements in DHC (or those are not shown in the UI) can you please check what causes this?\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!afbeelding!\'"", ""Comment 2: \'That day we did the DHC release\'"", ""Comment 3: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\']""]\nRelated Issues:\n[]\n\n### End'}"
3,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-9029\n\n### Instruction:\nPlease remove (or disable) additional technology SN526402.\r\nIt isn\'t used yet and created ""by accident"".\r\n\r\nRegards,\r\nRob.\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Additional technology has been disabled.\']""]\nRelated Issues:\n[]\n\n### End'}"
4,"{'prompt': ""Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-9028\n\n### Instruction:\nPersonal User setting disappear after shutdown.\n\n### Response:\n['Comment 1: []']\nRelated Issues:\n[]\n\n### End""}"
5,"{'prompt': ""Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-9027\n\n### Instruction:\nMeeting about plan for Intense 2023.1 deployment on UAT and PROD environment.\n\n### Response:\n['Comment 1: []']\nRelated Issues:\n[]\n\n### End""}"
6,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-9026\n\n### Instruction:\nHello,\r\n\r\ncan you please set status back to \'In progress\' for lot number 87014124042324681? there are some missing batches, with cannot be resend due to status\r\n\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: ""{code:java}  FROM [DH_Exchange_NL_PROD].[dbo].[ProductionLotReportHeader] plr  where PlH_LotNumber in(\\\'87014124042324681\\\')  FROM [DHP_NL_PROD].[dbo].[ProductionLotReportHeader] plr  where PlH_LotNumber in(\\\'87014124042324681\\\'){code}""\', ""Comment 4: \'Status for PLR has been changed.\']""]\nRelated Issues:\n[]\n\n### End'}"
7,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-9025\n\n### Instruction:\ni have this error for documents generated for johnson warehouse wheni try to generate them from DHC into ERP.\r\n\r\nError of type XLApiException has been thrown (XLNowyDokument:33).\r\nAPI Name - XLNowyDokument\r\nAPI Result - 33\r\nFlags - 16\r\nBŁĘDY:|Nie udało się wymusić numeru dokumentu/niepoprawny numer. (NowyDokument-33)\r\n\r\nDo we need to also cancel every manually generated document for johnson also to help fix this error?\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: ""SELECT vt.ExpectedElementsQuantity\', \'Comment 3: vee.DocumentNumber,vt.documentnumber\', \'Comment 4: vee.message,o.DocumentNumber as ordernumber\', \'Comment 5: o.id as orderid\', \'Comment 6: d.*FROM [dbo].[VehicleTickets] vtjoin [dbo].[VehicleTicketElements] ve on vt.Id=ve.VehicleTicketIdjoin [dbo].[VehicleTicketElementERPDocuments] vee on vee.VehicleTicketElementId=ve.Idjoin [dbo].[VehicleTicketDocumentNumbers] d on d.Id=ve.DocumentNumberIdjoin dbo. OrderElements oe on oe.Id=ve.OrderElementIdjoin dbo.orders o on o.id=oe.OrderId--– join [ERPXL_GHA_PROD] .cdn.TraNag erp on erp.trn_gidnumer=pt.XlIdwhere d.id in (select id from [dbo].[VehicleTicketDocumentNumbers] where DocumentYear=2023 and DocumentMonth=4 and o.DocumentNumerator_Series=\\\'jons\\\') and vee.DocumentNumber is null and vee.Message like \\\'%APi%\\\' order by d.DocumentNumber desc""]\']\nRelated Issues:\n[]\n\n### End'}"
8,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-9024\n\n### Instruction:\nHello\r\nPlease help to check this stock unit: item 1101330 with serial number 240423PO805-070323V0. \r\nVT-1372/4/23 has already been closed, but the status of this stock unit is still in progress.\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'!image-2023-04-25-13-24-07-554.png!\'"", ""Comment 4: \'!image-2023-04-25-13-24-52-324.png!!image-2023-04-25-13-25-15-883.png!!image-2023-04-25-13-25-38-473.png!\'"", ""Comment 5: \'!image-2023-04-25-13-47-29-267.png!\'"", ""Comment 6: \'!image-2023-04-25-14-06-04-705.png!!image-2023-04-25-14-05-19-113.png!\'"", \'Comment 7: ""{code:java}Microsoft.EntityFrameworkCore.DbUpdateException: An error occurred while saving the entity changes. See the inner exception for details. ---> Microsoft.Data.SqlClient.SqlException (0x80131904): Cannot insert duplicate key row in object \\\'dbo.StockUnits\\\' with unique index \\\'IX_StockUnits_Barcode\\\'. The duplicate key value is (436-W0079E).The statement has been terminated.   at Microsoft.Data.SqlClient.SqlConnection.OnError(SqlException exception\', \'Comment 8: Boolean breakConnection\', \'Comment 9: Action`1 wrapCloseInAction)   at Microsoft.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj\', \'Comment 10: Boolean callerHasConnectionLock\', \'Comment 11: Boolean asyncClose)   at Microsoft.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior\', \'Comment 12: SqlCommand cmdHandler\', \'Comment 13: SqlDataReader dataStream\', \'Comment 14: BulkCopySimpleResultSet bulkCopyHandler\', \'Comment 15: TdsParserStateObject stateObj\', \'Comment 16: Boolean& dataReady)   at Microsoft.Data.SqlClient.SqlDataReader.TryConsumeMetaData()   at Microsoft.Data.SqlClient.SqlDataReader.get_MetaData()   at Microsoft.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds\', \'Comment 17: RunBehavior runBehavior\', \'Comment 18: String resetOptionsString\', \'Comment 19: Boolean isInternal\', \'Comment 20: Boolean forDescribeParameterEncryption\', \'Comment 21: Boolean shouldCacheForAlwaysEncrypted)   at Microsoft.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior\', \'Comment 22: RunBehavior runBehavior\', \'Comment 23: Boolean returnStream\', \'Comment 24: Boolean isAsync\', \'Comment 25: Int32 timeout\', \'Comment 26: Task& task\', \'Comment 27: Boolean asyncWrite\', \'Comment 28: Boolean inRetry\', \'Comment 29: SqlDataReader ds\', \'Comment 30: Boolean describeParameterEncryptionRequest)   at Microsoft.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior\', \'Comment 31: RunBehavior runBehavior\', \'Comment 32: Boolean returnStream\', \'Comment 33: TaskCompletionSource`1 completion\', \'Comment 34: Int32 timeout\', \'Comment 35: Task& task\', \'Comment 36: Boolean& usedCache\', \'Comment 37: Boolean asyncWrite\', \'Comment 38: Boolean inRetry\', \'Comment 39: 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:5304a8bd-c3cd-4e34-b8fe-db284c3d7fc8Error Number:2601,State:1,Class:14   --- 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 40: IRelationalConnection connection)   at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.StateManager.SaveChanges(IList`1 entriesToSave)   at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.StateManager.SaveChanges(StateManager stateManager\', \'Comment 41: Boolean acceptAllChangesOnSuccess)   at Microsoft.EntityFrameworkCore.SqlServer.Storage.Internal.SqlServerExecutionStrategy.Execute[TState,TResult](TState state\', \'Comment 42: Func`3 operation\', \'Comment 43: Func`3 verifySucceeded)   at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.StateManager.SaveChanges(Boolean acceptAllChangesOnSuccess)   at Microsoft.EntityFrameworkCore.DbContext.SaveChanges(Boolean acceptAllChangesOnSuccess)   at Kotrak.Common.Infrastructure.EF.GenericRepositoryEf`1.Persist(TEntity entity)   at Kotrak.Common.Infrastructure.EF.GenericConcurrencyRepositoryEf`1.Persist(TEntity entity)   at Kotrak.Common.Infrastructure.Persistence.Repositories.AggregateRootRepository`2.Persist(TAggregateRoot root)   at Plant.Stock.BusinessLogic.Application.Services.RegisterIntakeService.RegisterPackedIntake(RegisterPackedIntakeDataStructure dataStructure) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Application\\\\\\\\Services\\\\\\\\RegisterIntakeService.cs:line 134   at Plant.Stock.BusinessLogic.Application.CommandHandlers.PackedIntake.RegisterPackedIntakeCommandHandler.Handle(RegisterPackedIntakeCommand command) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Application\\\\\\\\CommandHandlers\\\\\\\\PackedIntake\\\\\\\\RegisterIntakeCommandHandler.cs:line 34   at Kotrak.Common.Infrastructure.Gate.CommandEnvironment.Run[TCommand](TCommand command)   at Castle.DynamicProxy.AbstractInvocation.Proceed()   at Kotrak.Common.Infrastructure.Interceptors.LoggingInterceptor`1.Intercept(IInvocation invocation)   at Castle.DynamicProxy.AbstractInvocation.Proceed()   at Kotrak.Common.Infrastructure.Gate.Filters.CommandProcessFilter`1.Execute(CommandPipelineContext`1 input)   at Kotrak.Extensions.Pipeline.PredefinedFilters.FilterDecorator`1.Execute(TContext input)   at Kotrak.Extensions.Pipeline.Pipeline`1.Execute(T input)   at Kotrak.Common.Infrastructure.Gate.StandardGate.DispatchCommand[TCommand](TCommand command)   at Plant.Stock.BusinessLogic.Infrastructure.ContextIntegration.IntercontextCommunication.WMS.PackedIntake.WarehouseIntakeUnitLoadRegisteredApplicationMessageHandler.Handle(WarehouseIntakeUnitLoadRegisteredApplicationEvent message) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Infrastructure.ContextIntegration\\\\\\\\IntercontextCommunication\\\\\\\\WMS\\\\\\\\PackedIntake\\\\\\\\WarehouseIntakeUnitLoadRegisteredApplicationMessageHandler.cs:line 47   at Kotrak.Common.Infrastructure.Integration.Filters.InboundMessageHandlerFilter.Execute(InternalStorageProcessContext`1 input)   at Kotrak.Extensions.Pipeline.Pipeline`1.Execute(T input)   at Kotrak.Common.Infrastructure.Integration.Filters.InboundMessagesProcessFilter.Execute(InternalStorageContext`1 input){code}""\', ""Comment 44: \'{code:java}Plant.Stock.BusinessLogic.DomainAbstractions.AggregationNotes.Exceptions.AggregationNoteInvalidOperationException: Validation failed: -- AggregationStockUnitShouldBeIntakeOngoingMessage   at Plant.Stock.BusinessLogic.Domain.Aggregation.Services.AggregationDomainService.RegisterIntakeAggregation(RegisterIntakeAggregationDomainDataStructure dataStructure) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Domain\\\\\\\\Aggregation\\\\\\\\Services\\\\\\\\AggregationDomainService.cs:line 323   at Plant.Stock.BusinessLogic.Domain.Aggregation.Services.AggregationDomainService.RegisterPackedIntakeAggregation(RegisterPackedIntakeAggregationDomainDataStructure dataStructure) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Domain\\\\\\\\Aggregation\\\\\\\\Services\\\\\\\\AggregationDomainService.cs:line 238   at Plant.Stock.BusinessLogic.Application.Services.RegisterIntakeService.RegisterPackedIntakeAggregation(RegisterPackedIntakeDataStructure data"", \'Comment 45: StockUnit stockUnit\', ""Comment 46: Delivery delivery) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Application\\\\\\\\Services\\\\\\\\RegisterIntakeService.cs:line 649   at Plant.Stock.BusinessLogic.Application.Services.RegisterIntakeService.RegisterPackedIntake(RegisterPackedIntakeDataStructure dataStructure) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Application\\\\\\\\Services\\\\\\\\RegisterIntakeService.cs:line 134   at Plant.Stock.BusinessLogic.Application.CommandHandlers.PackedIntake.RegisterPackedIntakeCommandHandler.Handle(RegisterPackedIntakeCommand command) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Application\\\\\\\\CommandHandlers\\\\\\\\PackedIntake\\\\\\\\RegisterIntakeCommandHandler.cs:line 34   at Kotrak.Common.Infrastructure.Gate.CommandEnvironment.Run[TCommand](TCommand command)   at Castle.DynamicProxy.AbstractInvocation.Proceed()   at Kotrak.Common.Infrastructure.Interceptors.LoggingInterceptor`1.Intercept(IInvocation invocation)   at Castle.DynamicProxy.AbstractInvocation.Proceed()   at Kotrak.Common.Infrastructure.Gate.Filters.CommandProcessFilter`1.Execute(CommandPipelineContext`1 input)   at Kotrak.Extensions.Pipeline.PredefinedFilters.FilterDecorator`1.Execute(TContext input)   at Kotrak.Extensions.Pipeline.Pipeline`1.Execute(T input)   at Kotrak.Common.Infrastructure.Gate.StandardGate.DispatchCommand[TCommand](TCommand command)   at Plant.Stock.BusinessLogic.Infrastructure.ContextIntegration.IntercontextCommunication.WMS.PackedIntake.WarehouseIntakeUnitLoadRegisteredApplicationMessageHandler.Handle(WarehouseIntakeUnitLoadRegisteredApplicationEvent message) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Infrastructure.ContextIntegration\\\\\\\\IntercontextCommunication\\\\\\\\WMS\\\\\\\\PackedIntake\\\\\\\\WarehouseIntakeUnitLoadRegisteredApplicationMessageHandler.cs:line 47   at Kotrak.Common.Infrastructure.Integration.Filters.InboundMessageHandlerFilter.Execute(InternalStorageProcessContext`1 input)   at Kotrak.Extensions.Pipeline.Pipeline`1.Execute(T input)   at Kotrak.Common.Infrastructure.Integration.Filters.InboundMessagesProcessFilter.Execute(InternalStorageContext`1 input){code}\'"", ""Comment 47: \'ID VTka52FB3FCE-4727-41B9-8E69-F44DF1137A6F!image-2023-04-25-14-18-57-328.png!!image-2023-04-25-17-04-21-380!\']""]\nRelated Issues:\n[]\n\n### End'}"
9,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-9023\n\n### Instruction:\nIOs from Johnson and Mag some of them especially from the 13th are not generating automatically kindly assist in solving this 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\']""]\nRelated Issues:\n[]\n\n### End'}"
10,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-9022\n\n### Instruction:\nFor order SO000105268 there are three orderlines, but only the one with item 088345 is coming through to DHP. The other two are in DHC but not synced with DHP. \n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'It looks like the recipe is in DHC but not in DHP\'"", ""Comment 3: \'Hi Theo,Recipes are now available in DHP system:!image-2023-04-24-22-43-03-529.png!!image-2023-04-24-22-43-16-017.png!Please resend the order to dhp. It should be complete.\'"", ""Comment 4: \'!image-2023-04-24-22-48-04-007.png!!image-2023-04-24-22-48-15-576.png!Please give us a feedback. Could we close this ticket ?\'"", ""Comment 5: \'In meantime the complete order is in DHP\'"", ""Comment 6: \'OK. Can we close this ticket ?\'"", ""Comment 7: \'Yes"", ""Comment 8: for my part please close the ticketI assume that with vertical integration the speed of accepting recipes will increase very much... \'"", ""Comment 9: \'{code:java}2023-04-24 20:52:49,639 [117] INFO  Evolution.DHCService.Dhc30.Handlers.RecipeChangedMessageHandler [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\31916033\\\\\\\\DHAPPSV3-DHCSER546-JOB1\\\\\\\\Evolution.DHCService\\\\\\\\Evolution.DHCService.Dhc30\\\\\\\\Handlers\\\\\\\\BaseMessageHandler.cs:42] - Receiving message (Evolution.DHCountry.Interfaces.Recipes.RecipeChangedMessage) [Id:eb24713e-600b-4574-9904-ca832a8336f1]2023-04-24 20:52:49,702 [117] ERROR Evolution.DHCService.Dhc30.Handlers.RecipeChangedMessageHandler [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\31916033\\\\\\\\DHAPPSV3-DHCSER546-JOB1\\\\\\\\Evolution.DHCService\\\\\\\\Evolution.DHCService.Dhc30\\\\\\\\Handlers\\\\\\\\BaseMessageHandler.cs:63] - Cannot handle message (Evolution.DHCountry.Interfaces.Recipes.RecipeChangedMessage). Exception occured:2023-04-24 20:52:49,702 [117] ERROR Evolution.DHCService.Dhc30.Handlers.RecipeChangedMessageHandler [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\31916033\\\\\\\\DHAPPSV3-DHCSER546-JOB1\\\\\\\\Evolution.DHCService\\\\\\\\Evolution.DHCService.Dhc30\\\\\\\\Handlers\\\\\\\\BaseMessageHandler.cs:64] - 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 conversion of a datetime2 data type to a datetime data type resulted in an out-of-range value.The statement has been terminated.{code}!image-2023-04-25-07-34-48-345.png!\'"", ""Comment 10: \'{code:java}2023-04-24 13:43:45,069 [14] INFO  Evolution.DHCService.Dhc30.Handlers.RecipeChangedMessageHandler [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\31916033\\\\\\\\DHAPPSV3-DHCSER546-JOB1\\\\\\\\Evolution.DHCService\\\\\\\\Evolution.DHCService.Dhc30\\\\\\\\Handlers\\\\\\\\BaseMessageHandler.cs:42] - Receiving message (Evolution.DHCountry.Interfaces.Recipes.RecipeChangedMessage) [Id:603c13f4-ed0e-4de7-a2fe-283d9d1511f6]2023-04-24 13:43:45,100 [14] ERROR Evolution.DHCService.Dhc30.Handlers.RecipeChangedMessageHandler [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\31916033\\\\\\\\DHAPPSV3-DHCSER546-JOB1\\\\\\\\Evolution.DHCService\\\\\\\\Evolution.DHCService.Dhc30\\\\\\\\Handlers\\\\\\\\BaseMessageHandler.cs:63] - Cannot handle message (Evolution.DHCountry.Interfaces.Recipes.RecipeChangedMessage). Exception occured:2023-04-24 13:43:45,100 [14] ERROR Evolution.DHCService.Dhc30.Handlers.RecipeChangedMessageHandler [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\31916033\\\\\\\\DHAPPSV3-DHCSER546-JOB1\\\\\\\\Evolution.DHCService\\\\\\\\Evolution.DHCService.Dhc30\\\\\\\\Handlers\\\\\\\\BaseMessageHandler.cs:64] - 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 conversion of a datetime2 data type to a datetime data type resulted in an out-of-range value.The statement has been terminated.{code}!image-2023-04-25-07-40-57-577.png!\'"", ""Comment 11: \'Pierwszy zarejestrowany w logach:!image-2023-04-25-10-58-18-871.png!Dla drugiego itemu:!image-2023-04-25-10-59-17-822.png!\'"", ""Comment 12: \'Upgrade był 19 kwietnia - potwierdzone z Przemkiem. Przemek mówi"", \'Comment 13: ze communication log czyści się po miesiącu\', ""Comment 14: więc pewnie jakaś staroć została\']""]\nRelated Issues:\n[]\n\n### End'}"
11,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-9021\n\n### Instruction:\nHi\r\n\r\nWe need to produce the item *PEP8147-T* and it\'s extension PEP8147-T-S25.\r\nHowever the Production Recipe is not in DHP.\r\n\r\nCould you please help us?\r\n\r\nThank you very much!\n\n### Response:\n[""Comment 1: [\'!image!!image-1!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 3: ""{code:java}SELECT i2.code  FROM [Evolution_DHCService].[dbo].[Items] i1  right join Evolution_DHCountry.[dbo].[Items] i2 on i1.id=i2.id  where i2.code in(SELECT i.code  FROM Evolution_DHCountry.[dbo].[RecipeIngredients] ri  inner join Evolution_DHCountry.[dbo].DhhItems dh on ri.DhhItemId=dh.Id  inner join Evolution_DHCountry.[dbo].Items i on i.id=dh.baseitemid  where RecipeId=\\\'6C8AED72-2897-4214-B6AA-E5F051659BFA\\\')  and i1.Code is null{code}!image-2023-04-24-20-01-55-795.png!""\', ""Comment 4: \'Missing items in DHCService218312183721838Incorrect linked items in DHC"", \'Comment 5: for example!image-2023-04-24-20-03-04-246.png!Pleasefinish linking items\', ""Comment 6: they will appear in dhcservice and you will be able to send the recipe to plant.\'"", ""Comment 7: \'Hi [~Piotr.Gaczorek@kotrak.com]How did you find this missing items?Is there any DHC screen"", ""Comment 8: report or SQL query where we can find this information by ourselfs?Thank you\'"", \'Comment 9: ""Hi Maicon\', \'Comment 10: we found this in sql database by sql query: SELECT i2.code FROM [Evolution_DHCService].[dbo].[Items] i1 right join Evolution_DHCountry.[dbo].[Items] i2 on i1.id=i2.id where i2.code in(SELECT i.code FROM Evolution_DHCountry.[dbo].[RecipeIngredients] ri inner join Evolution_DHCountry.[dbo].DhhItems dh on ri.DhhItemId=dh.Id inner join Evolution_DHCountry.[dbo].Items i on i.id=dh.baseitemid where RecipeId=\\\'6C8AED72-2897-4214-B6AA-E5F051659BFA\\\') and i1.Code is nullCan we close this ticket? Thank you.""\', ""Comment 11: \'HI [~Lukasz.Lasok@kotrak.com]Thanks for this SQL query.You can close this task.Thank you very much!\']""]\nRelated Issues:\n[]\n\n### End'}"
12,"{'prompt': ""Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-9020\n\n### Instruction:\nPlease create a new user for Agra-Matic. \r\n\r\nName: Jan Willem Meijer\r\n\r\nSame permissions as Freddy Westrik.\n\n### Response:\n['Comment 1: []']\nRelated Issues:\n[]\n\n### End""}"
13,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-9019\n\n### Instruction:\nThe following Lot reports are available in DHC (draft Lot reports) but do not seem to be send to Milas. \r\nExpected: all draft Lot reports and Lot reports available in DHC are available in Milas.\r\n\r\nCan you (re)send these Lot report from DHC to Milas?\r\n\r\n0021200423072\r\n0041030423013\r\n0071200423088\r\n0071200423096\r\n0081200423097\r\n0081200423106\r\n0081200423108\r\n0081200423109\r\n0081200423110\r\n0081200423111\r\n\n\n### Response:\n[""Comment 1: [\'!image-1!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 3: ""{code:java} select * FROM [Evolution_DHCERP_NL_AS400_Identities].[dbo].[ProductionLotReportMappings] p  where dhcid in(SELECT id  FROM DHCountry_NL_AS400_PROD.[dbo].[ProductionLotReports]  where LotNumber in(\\\'0021200423072\\\',\\\'0041030423013\\\',\\\'0071200423088\\\',\\\'0071200423096\\\',\\\'0081200423097\\\',\\\'0081200423106\\\',\\\'0081200423108\\\',\\\'0081200423109\\\',\\\'0081200423110\\\',\\\'0081200423111\\\')){code}""\', ""Comment 4: \'Please check lot reports have been sent again to Milas.\'"", ""Comment 5: \'Thank you"", ""Comment 6: we will check this\'"", ""Comment 7: \'We received the Lot reports in Milas now. This ticket can be closed.\'"", ""Comment 8: \'Thank you for confirmation.\']""]\nRelated Issues:\n[]\n\n### End'}"
14,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-9018\n\n### Instruction:\nThe following Lot reports are confirmed in DHP. In DHC we only have draft Lot report. We expect the Lot report in DHC (and in Milas).\r\n\r\n0021210323021\r\n0071210323022\r\n0071240123084\r\n0081270123068\r\n0111040123040\r\n0111160123014\r\n\r\nPlease (re)send these Lot reports from DHP to DHC (and export to Milas)\n\n### Response:\n[""Comment 1: [\'!image-1!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 3: ""{code:java}SELECT *  FROM [DHPlantProdBusinessLogicEvents].[dbo].[ProductionLots]  where AggregateId=\\\'2BBEB7D7-A953-4648-882A-70178836C43A\\\'  and EventType like \\\'%conf%\\\'  SELECT *  FROM [DHPlantProdBusinessLogicEvents].[dbo].[ProductionLots]  where AggregateId=\\\'2BBEB7D7-A953-4648-882A-70178836C43A\\\'  and EventType like \\\'%finish%\\\'  SELECT       [ProductionLotStatus],*  FROM [DHPlantProdBusinessLogicMain].[dbo].[ProductionLots]  where LotNumber=\\\'0071240123084\\\'{code}{code:java}SELECT *  FROM [dbo].[ProductionLotReports]  where LotNumber in(\\\'0071240123084\\\',\\\'0111040123040\\\',\\\'0111160123014\\\')0071210323022 utrecht0021210323021 sneek0081270123068 Veghel0011 maasb{code}!image-2023-04-25-13-49-05-697!""]\']\nRelated Issues:\n[]\n\n### End'}"
15,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-9017\n\n### Instruction:\nSO-2061/23/UMR wont sync as item code RD37071-S7980-P created today, is not in DHP. Needed for production tonight.\r\n\r\nItem code seems to be in other plants.\r\nItem code is linked.\r\nTechnology generated\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: ""Jak dla mnie wygląda na problem z paczką{code:java}SELECT *  FROM [DHCService_RSA_PROD].[dbo].[ItemExportInfoes]  where (EntityId=\\\'359FD908-8E70-4BF1-9696-E73EF09160AA\\\' and ClientId=\\\'205268AF-8BE3-4344-BFA8-157AC266AAFC\\\')  or PackageId=\\\'B988DCD7-0B46-4E21-A743-3E5B5DEC798C\\\'  select * from CommunicationLogs where MessageDetails like \\\'%RD37071-S7980-P%\\\'  select * from dbo.Items where id=\\\'359FD908-8E70-4BF1-9696-E73EF09160AA\\\'{code} !image-2023-04-24-13-57-08-885.png!DHP:!image-2023-04-24-13-58-18-650.png!W DHP jest sporo błędów dla towarów - nie wpadają do VC.Kotrak.Common.Application.Exceptions.CommandValidationException`1[Plant.VC.BusinessLogic.Application.Interfaces.Items.Commands.SynchronizeItemCommand]: Validation failed: -- WrongPackingFormMessage!image-2023-04-24-13-59-27-002.png!""]\']\nRelated Issues:\n[\'DGS-8999\']\n\n### End'}"
16,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-9016\n\n### Instruction:\nHello,\r\n\r\nCan you please send the lotreports from attached document from DHC to MILAS? It contains missing lot reports in MILAS from 1/1/2023 till 31/3/2023.\r\n\r\nKind regards,\r\nWijnand.\n\n### Response:\n[""Comment 1: [\'[^Ontbrekende lots in AIS.xlsx] _(11 kB)_\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Hi Wijnand,I have resent all lot reports from your file to Milas as requested. Please"", ""Comment 4: verify and let me know if everything is fine.Regards\']""]\nRelated Issues:\n[]\n\n### End'}"
17,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-9015\n\n### Instruction:\nPlease add the relation from column AA in the MAS NL for the guarantees.\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 zmiany relacja w sekcji gwarancji"", ""Comment 3: trzeba będzie teraz rozróżniać SI czy pochodzi z innego dokumentu - Doc_LeadingDocID czy nie.Do tej pory nie było rozróżniania. Do dodania nowa relacja z PI guarantees.!image-2023-04-25-12-04-07-849.png! \'"", ""Comment 4: \'Hi [~mbovene@deheus.com],we added new relation to Guarantees on Round (MAS NL) in Test Intense environment.You can verify it.Best regards,Grzegorz\']""]\nRelated Issues:\n[]\n\n### End'}"
18,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-9014\n\n### Instruction:\nCześć\r\n\r\nTask from Paulina.\r\n\r\nRafał Boniecki\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'[^DGS-9014.docx]\'"", ""Comment 4: \'**Information in the attachment[^DGS-9014.docx]\']""]\nRelated Issues:\n[]\n\n### End'}"
19,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-9013\n\n### Instruction:\nCould you give Steffen Driesens en Koen Huibers access to the mailboxes of:\r\n* Rick Reimerink AA\r\n* Erik de Groot AA\r\n* Oscar Visser AA\r\n* Arthur van der Linde\n\n### Response:\n[""Comment 1: [\'W międzyczasie dziś konto Rick Reimerink AA zmieniłem na Rick Reimerink"", ""Comment 2: a jego poprzednie konto jest jakoRick Reimerink_old i jest nieaktywne.Do zrobienia to samo z loginami Oscara i Erika\'"", ""Comment 3: \'Hi [~mbovene@deheus.com],we made changes on users and added access for Steffen and Koen.You can verify it.Best regards,Grzegorz\'"", ""Comment 4: \'Can be closed.\']""]\nRelated Issues:\n[]\n\n### End'}"
20,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-9012\n\n### Instruction:\nSometimes it\'s needed to choose round from Supplier on Purchase Invoice in MAS NL sector.\r\n\r\nIt should be added to list Rounds of Supplier.\r\n\r\nIt shoudln\'t be an issue when Rounds of Reference and Supplier will be shown always together because mainly only there are rounds for one of these (for Customer or for Supplier).\r\n\r\n\xa0\r\n\r\nExample from IBIP_DH database, ID\xa0118625,\xa0PI-RLM/2023/3331\r\n\r\n!image-2023-04-24-10-59-28-941.png!\n\n### Response:\n[\'Comment 1: [\\\'Hi [~mbovene@deheus.com],we\\\\\\\'ve added extra Rounds by Supplier in ""Full number"" lookup field in PI (MAS NL).Changes made on Test and Prod Intense enviornment.You can verify it.Best regards,Grzegorz\\\']\']\nRelated Issues:\n[\'DGS-8900\']\n\n### End'}"
21,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-9011\n\n### Instruction:\nInternal server error on FHP with the ip 10.233.3.37\r\nPlease help\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Hi,Application Pools have been restarted. Please"", ""Comment 3: verify.Regards\'"", ""Comment 4: \'Working please close\'"", ""Comment 5: \'Thank you\']""]\nRelated Issues:\n[]\n\n### End'}"
22,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-9010\n\n### Instruction:\nOd 14.04 do dziś nie wygenerowały się żadne MM z PMX do LECGS.\r\nPoproszę o pilną naprawę problemu ponieważ jutro mamy inwentaryzację\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: \'Whether the problem is still present. If so"", ""Comment 3: can I ask the number of the order / orders for which the documents were not generated?\'"", \'Comment 4: ""all since the 18th of April\', \'Comment 5:  looks like it\\\'s a problem after the update DHC/integrator!image!""\', ""Comment 6: \'hello I have problem to log on to you environment. after log on - choosing 3 hour and rdp I got this window!image-2023-04-24-09-46-51-254.png!\'"", ""Comment 7: \'Try now\'"", ""Comment 8: \'The manager needs information What caused the problem and did the problem occur only in this one location?\'"", ""Comment 9: \'now it is working thank you\'"", ""Comment 10: \'!image-2023-04-24-12-58-01-575.png!\'"", ""Comment 11: \'select * from WMSInternalDocumentelements where wre_headerid in (SELECT idx_wrhid FROM [DHP_Leczyca].[dbo].[WMSInternalDocumentHeadersExport] where idx_date is null )\'"", ""Comment 12: \'!image-2023-04-24-14-28-48-704.png!\'"", ""Comment 13: \'we need to verify this with our developers\']""]\nRelated Issues:\n[]\n\n### End'}"
23,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-9009\n\n### Instruction:\nwe are unable to confirm bags for PLR 0705240323001 because the system says the lot can no longer be found. this lot had to be force finished (stuck in progress). \r\nID details have been resent from the error logs but this has not solved the problem.\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'select * from ProductionLots where lotnumber= 0705240323001select * from DHPlantWmsBusinessLogicMain.dbo.productionlots where LotNumber= 0705240323001brak lotu w wms!image-2023-04-21-16-53-02-416.png!\'"", \'Comment 4: ""brakuje też production orderaSELECT * FROM DHPlantWmsBusinessLogicMain.dbo.ProductionOrders WHERE ID=\\\'11D12F7C-4432-4A36-89FE-C6107C3E1B4B\\\'""\', \'Comment 5: ""przy próbie wysylki2023-04-21 17:47:44 (/Plant.WMS.BusinessLogic/SAKDSRV04/5544/68) [Error] Kotrak.Common.Infrastructure.Integration.Filters.InboundMessagesProcessFilter - Error during process inbound messageSystem.ArgumentNullException: Value cannot be null. (Parameter \\\'code\\\')""\', ""Comment 6: \'Problem jest że wygląda jakby wms"", ""Comment 7: nie aktualizowały się cody itemów?Probowałam pro i prl przepchac rabitem i przez resend ale nic to nie dało.\'"", ""Comment 8: \'!klersdope.PNG|thumbnail!\'"", ""Comment 9: \'dzisiaj nie chodzi klersdope !klersdope.PNG!\'"", \'Comment 10: ""erory FROM [DHPlantWmsBusinessLogicIntercontext].[dbo].[Errors]where message like \\\'%519FEB6C-BA10-44E6-9F29-25ABD107DBBB%\\\'at Plant.WMS.BusinessLogic.Infrastructure.ContextIntegration.MappingProfiles.SynchronizeOrderCommandProfile.<>c.<.ctor>b__0_0(OrderChangedMessage message\', \'Comment 11: ResolutionContext context) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Infrastructure.ContextIntegration\\\\\\\\MappingProfiles\\\\\\\\SynchronizeOrderCommandProfile.cs:line 0 at lambda_method6663(Closure \', \'Comment 12: OrderChangedMessage \', \'Comment 13: SynchronizeOrderCommand \', \'Comment 14: ResolutionContext ) at AutoMapper.Mapper.AutoMapper.IMapper.Map[TSource,TDestination](TSource source) at Plant.WMS.BusinessLogic.Infrastructure.ContextIntegration.IntercontextCommunication.BaseInboundMessageHandler`2.Handle(TMessage message) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Infrastructure.ContextIntegration\\\\\\\\IntercontextCommunication\\\\\\\\BaseInboundMessageHandler.cs:line 26 at Kotrak.Integration.IntegrationPluginCommon.IntercontextCommunication.Inbound.IntercontextInboundHandler`2.Handle(InternalStorageDto message)""\', ""Comment 15: \'dla samego plr w wms brak ewentu oi bledów !image-2023-04-25-14-30-39-149.png!\'"", ""Comment 16: \'!image-2023-04-25-14-31-02-249.png!\'"", \'Comment 17: ""FROM [DHPlantProdBusinessLogicEvents].[dbo].[ProductionLots] where AggregateId=\\\'ED002A97-C84A-48D1-AD69-9318C8D1BE5F\\\'select* FROM [DHPlantwmsBusinessLogicEvents].[dbo].[ProductionLots] where AggregateId=\\\'ED002A97-C84A-48D1-AD69-9318C8D1BE5F\\\'""\', ""Comment 18: \'dla stocku taka sama sytuacja jak dla wms\']""]\nRelated Issues:\n[]\n\n### End'}"
24,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-9008\n\n### Instruction:\nHello,\r\n\r\nProduction helmond reports there is no communication to the pcs. Webservices are running, and are called by the pcs side, but no data is send. Please check and can you restart services on DHP side?\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: \'Just had contact with production"", ""Comment 3: communication seems to be running again\'"", ""Comment 4: \'Restart usług.\'"", ""Comment 5: \'!image-2023-04-24-12-42-13-226.png!\']""]\nRelated Issues:\n[]\n\n### End'}"
25,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-9007\n\n### Instruction:\nWe are unable to use IPOR for the additional purchase cost. we using IPOR 204/23/JON    and IPOR 205/23/JON.\r\n\r\nIt only works with PORs how do make it work\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 3: ""Hi\', \'Comment 4:  please be informed that the issue has held sales since yesterday; we can\\\'t sell the product without the total cost registered in the system. The product (KLC5) is also a raw material and would be used in production today. ""\', ""Comment 5: \'Koszty dodatkowe zakupu krajowego można przypisywać do założonych w Systemie dostaw za pomocą dokumentu: „Koszty Dodatkowe Zakupu – KDZ”. Koszty można dodać do dokumentów FZ"", \'Comment 6: PZ\', \'Comment 7: FRR\', \'Comment 8: PW\', ""Comment 9: PWK oraz ręcznych korekt ilościowych FKS/FKW/WKK.\'"", ""Comment 10: \'For documents of the PZI type the cost must be corrected by the SII - Internal document.First you need to issue an IMI - Import Invoice document from IPOR.Then SII Internal document from IMI.You will be able to enter costs on the Amounts tab.After confirmed SII document if fixed delivery value is selected for IPOR a correction from the SII level can be issued for this document.\'"", ""Comment 11: \'Please what is this SII document? how do correct with the SII\'"", ""Comment 12: \'Can i turn IPOR to POR if yes how do I do it\'"", ""Comment 13: \'Yes"", ""Comment 14: but it depends on the type of transaction on the order - only for Domestic transaction on PO can be process POR.We can change the transaction type for the order from the database but it will not be correct for Netherlands.\']""]\nRelated Issues:\n[]\n\n### End'}"
26,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-9006\n\n### Instruction:\nProblem z zaczytaniem listy płac I10/2023/03\r\nProszę o zdiagnozowanie i naprawienie problemu, jaki wystąpił podczas migracji listy nr I10/2023/03 z Optimy do CDn-a; poniżej screeny, lista utknęła i nie została pobrana.\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: \'Verification of the task is in progress\'"", ""Comment 4: \'If you changed something on this employee the last time (after made main payroll)?\'"", ""Comment 5: \'[^DGS-9006.docx]\'"", ""Comment 6: \'information in the attachment[^DGS-9006.docx]\']""]\nRelated Issues:\n[]\n\n### End'}"
27,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-9005\n\n### Instruction:\ni need the definition for the following product form in ERP when creating a product ;\r\nC\r\nF\r\nL\r\nM\r\nPLT\r\nPWD\r\nW\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Hello. They are already defined in XL you should add them to the product when creating the product from the level of the product attribute (from the green plus option).!image-2023-04-24-15-35-31-706.png!We can also change the settings in XL so that they appear automatically.\'"", ""Comment 3: \'what i mean is if i select C in the list of attributes under product form"", ""Comment 4: what does it mean. is C standing for something? that is what i what i want to know.\']""]\nRelated Issues:\n[]\n\n### End'}"
28,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-9004\n\n### Instruction:\nThe name and financial details of Business Partner 0526 have been changed within CDN-XL from Ajinomoto to Metex.\r\n\r\nwhen we consult via DH CDN, the data is not changed !!\r\n\r\nHow is this possible?\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: \'Adress data for customers (business parners) can be translated in DH CDN depending on choosen language. If data for selected language is gray then it came from ERPXL. If this data for choosen language is black then translation was created in DH CDN and can be modified by user. So you can modify it by yourself.This is standard functionality provided by DH CDN.There is no translation data for customer (business partner) information in ERP XL.!image-2023-04-20-13-17-34-062.png!!image-2023-04-20-13-20-37-646.png!Data shown by DH CDN depends on Language you choose when log into application!image-2023-04-20-13-20-15-643.png!Similar issue was in taskDGS-8455Regards\'"", ""Comment 4: \'Ticket can be closed\']""]\nRelated Issues:\n[]\n\n### End'}"
29,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-9003\n\n### Instruction:\nRecipe for 147475 was sent to DHC and accepted on 19-04-2023. It is missing in DHP/PCS for Maasbracht.\r\nItem seems to be linked correctly in DHC.\r\nIn DHP item is missing (and because of that I think recipe is not imported).\r\n\r\nCan you check why the item is missing in DHP, fix this and resent the recipe? It is needed in PCS for production.\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: \'Please check"", ""Comment 4: recipe should be in DHP already.\'"", ""Comment 5: \'Indeed"", ""Comment 6: item and recipe are now in DHP and recipe is delivered to PCS.What was the issue / how did you fix this?\'"", ""Comment 7: \'!image-2023-04-20-11-03-31-732.png!\'"", \'Comment 8: ""Hi Bob,this is a known issue that pops up every now and then\', \'Comment 9: should be fixed in a future release of DHC/DHP.Apparently the fix involves some database trickery that we can\\\'t do ourselves.Regards,Rob.PS there was a ticket for this case already: DGS-9002""\', ""Comment 10: \'Bob"", ""Comment 11: see DGS-8986\'"", ""Comment 12: \'Missing DHHitem in DHCService"", ""Comment 13: ithas been resolved since dhc 3.0.60.The current version should not have the problem but for items after the upgrade date.\'"", ""Comment 14: \'This ticket can be closedOk"", ""Comment 15: we will check for inconsistencies for items in DHC and DHP\'"", ""Comment 16: \'Thank you.\']""]\nRelated Issues:\n[\'DGS-9002\']\n\n### End'}"
30,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-9002\n\n### Instruction:\nItem/recipe/labels for 147475 are all present in DHH/DHC but don\'t arrive in DHP Maasbracht.\r\n\r\nSynchronize & resend didn\'t help.\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'{code:java}select h1.*,h2.* from [DHCountry_NL_AS400_PROD].[dbo].[DhhItems] h1select h1.*,h2.* from [DHCountry_NL_AS400_PROD].[dbo].[DhhItems] h1 left join [DHCService_NL_AS400_PROD].[dbo].[DhhItems] h2 on h1.id=h2.id where h2.id is null andh1.BaseItemId is not null{code}!image-2023-04-20-10-19-59-004.png!jeszcze temat z brakiem dhhitems.!image-2023-04-20-10-19-26-620.png!\'"", ""Comment 3: \'Resolved inDGS-9003.\'"", ""Comment 4: \'Technically speaking... I was first ;)This ticket can be closed. Thanks for the support.\'"", ""Comment 5: \'Thank you for confirmation.\']""]\nRelated Issues:\n[\'DGS-9003\']\n\n### End'}"
31,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-9001\n\n### Instruction:\nZZ-305/04/23 nie można zmienić kraju pochodzenia na SK-Słovakia.\r\nJeśli wybierzemy kraj SK-Slovakia wtedy po zapisie i ponownym otwarciu ZZ pole jest puste.\r\nWszystkie inne kraje zostają zapamiętane podczas zapisu i ponownego otwarcia ZZ.\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: \'https://helpdesk.kotrak.com/browse/DGS-7991\'"", ""Comment 3: \'Sprawdziłam"", \'Comment 4: i faktycznie orirgin country nie wpada\', ""Comment 5: sprawdziłam inne zz na słowacje z erp xl tj 381/12/2022 tez to pola jest puste w dhcdn!image-2023-04-20-13-34-09-562.png!\'"", ""Comment 6: \'na bazie kraj jest zapisany ale go nie widac widać go dla szwajcarii !image-2023-04-20-13-42-14-355.png!\'"", ""Comment 7: \'From what I verify the name of country it is visible in dhcdn gui database but not show in application.Did you have any example of order for that origin country (slovakia) when thi is visible?\'"", \'Comment 8: ""we don\\\'t\', \'Comment 9: we have such a contract first time""\', ""Comment 10: \'[~michal.kordys@kotrak.com]Ania będzie na to robić DCi.\'"", ""Comment 11: \'We ask developers ofr help with that issue.\'"", ""Comment 12: \'!image-2023-04-25-10-43-49-788.png!\'"", \'Comment 13: ""select * from cdn.krajecelne where kpc_nazwa=\\\'slovakia\\\'""\', \'Comment 14: ""--update cdn.KrajeCelne --set kpc_nazwa=\\\'test\\\'\', \'Comment 15: kpc_nazwapl=\\\'test\\\' --where kpc_id=205""\', ""Comment 16: \'pleae verify it seems it works now!image-2023-04-25-11-04-01-331.png!\'"", ""Comment 17: \'był; zdublowany wpis an bazie w erpxl na taebli cdn.kraje celne"", ""Comment 18: sprawdzalm od striony apki nie da sie tgeo dodac.\']""]\nRelated Issues:\n[]\n\n### End'}"
32,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-9000\n\n### Instruction:\nHi\r\n\r\nCould you please enable and configure SSRS for DHC? Or maybe the Printout functionality in the DHC\r\nI think we could use it for a lot of purpose.\r\n\r\nThank you\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'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: \'[~przemyslaw.przybyszewski@kotrak.com]to jest do zrobienia? Kolega z Amazonii pyta :)\'"", \'Comment 5: ""Hi [~mberbert@deheus.com]\', ""Comment 6: DHC doesn\'t support SSRS"", \'Comment 7: printout functionality in DHC is limited and it uses Crystal Reports to generate printouts.""]\']\nRelated Issues:\n[]\n\n### End'}"
33,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8999\n\n### Instruction:\nSO-2061/23/UMR wont sync as item code RD37071-S7980-P created today, is not in DHP. Needed for production tonight.\r\n\r\nItem code seems to be in other plants.\r\nItem code is linked.\r\nTechnology generated\n\n### Response:\n[""Comment 1: [\'!image!!image-1!!image-2!!image-3!\'"", \'Comment 2: ""If you find the issue\', ""Comment 3: please tell me what you did to resolve. I\'ve most of the normal solutIon. Checked for error"", \'Comment 4: Restarted application pools ,and services. Modified the item code\', \'Comment 5: etc.""\', ""Comment 6: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 7: \'Any update?\'"", \'Comment 8: ""We\\\'re working on it""\', ""Comment 9: \'!image-2023-04-19-23-46-24-523.png!\'"", ""Comment 10: \'Please verify. Now it should be ok.Please give us a feedback.\'"", ""Comment 11: \'The problem was on the side of an unknown change in the item RD37071-S7980-P. Updating this item and trying to restart the services. ErpIntegrator"", \'Comment 12: Dhc Country\', ""Comment 13: Dhc Service and integration services with DHC in side on DHP. Several times trying to restart services in that order solved the problem.Can we close this task ?\'"", ""Comment 14: \'Próba rozwiązania wg opisu w ON: [[DHC][DHC SERVICE] BRAK ITEMU"", \'Comment 15: RECEPTUR I STANDARD SPECIAL W DHC SERVICE|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%5BDHC%20SERVICE%5D%20BRAK%20ITEMU%2C&section-id=7d50734f-49d8-4579-83b9-e51158168a8f&page-id=6b290e1b-fdf7-44cf-ae24-ff050bc32bff&end] ([Widok sieci Web|https://kotrak.sharepoint.com/sites/erpasysta/_layouts/15/Doc.aspx?sourcedoc=\\\\\\\\{03c87c92-bf92-4b3e-bfbe-d3ad2729eba6}&action=edit&wd=target%28Klienci%2FDEHEUS%2FDEHEUS%20APPLICATIONS%2FPolska%2FBaza%20wiedzy%2FDHC.one%7C7d50734f-49d8-4579-83b9-e51158168a8f%2F%5BDHC%5D%5BDHC%20SERVICE%5D%20BRAK%20ITEMU%2C%7C6b290e1b-fdf7-44cf-ae24-ff050bc32bff%2F%29&wdorigin=703&wdpreservelink=1])Dodatkowo:Kilkukrotny restart usług - erpintgratora\', \'Comment 16: dhc country\', \'Comment 17: dhcservice\', ""Comment 18: i uslugi integracji z dhc w plant - w tej kolejności problem został rozwiązany.\'"", ""Comment 19: \'Thank you. You may close the ticket.\'"", ""Comment 20: \'Hello"", ""Comment 21: RCA DGS-9017 for issue has been created.\']""]\nRelated Issues:\n[\'DGS-9017\']\n\n### End'}"
34,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8998\n\n### Instruction:\nHi\r\n\r\nWe found one weird situation in DHP about Expiry Date.\r\nOn the Executiuon tab of PLR, system is getting the right information about Expiry date: 365 days.\r\nHowever, without any manual intervention, the Delivery of it\'s PLR is being created with Expiry date 180 days.\r\n\r\nWhy is that?\r\nCould you please help us to understand and fix that?\r\n\r\nThank you very much!\n\n### Response:\n[""Comment 1: [\'!image!!image-1!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Ten sam kejs co tuhttps://helpdesk.kotrak.com/browse/DGS-7160\'"", ""Comment 4: \'Hi [~mberbert@deheus.com],We know what happend.This issue is already fixed in R8.5\']""]\nRelated Issues:\n[\'DAP-12931\']\n\n### End'}"
35,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8997\n\n### Instruction:\nHi\r\n\r\nWe had a power issue 1 hour ago and now DHP is not working.\r\nThe following message are everywhere on DHP screens.\r\n\r\nHelps us, please\r\nThank you\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: \'Please check now should be ok.\'"", ""Comment 4: \'Hi [~Agnieszka.Januszewska@kotrak.com]Now everything is OK.Thank you very much!You can close this task\']""]\nRelated Issues:\n[]\n\n### End'}"
36,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8996\n\n### Instruction:\nRecipes exported from DHH are not arriving in DHC Compound anymore.\r\nSeveral recipes were sent, but none were imported after 11:12h.\r\n\r\nProbably a result of the upgrade.\r\n\r\nPlease check.\r\n\r\nRegards,\r\nRob\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Pytanie dlaczego usługa była nieuruchomiona to ktoś od nas się zagapil i co przekazac klientowi !image-2023-04-19-18-00-08-556.png!\'"", ""Comment 3: \'po logach tej uslugi wygląda że nie była uruchomiona miedzy 11:55 a 17.55 więc chyba nasz blad,dodatkowo do weryfikacji opis z ON.:[Brak komunikacji z DHH od strony kraju. Np. Pricelist nie przechodzą.|onenote:https://kotrak.sharepoint.com/sites/erpasysta/Shared%20Documents/Baza%20wiedzy/Baza%20Wiedzy%20-%20ERPSD/Klienci/DEHEUS/DEHEUS%20APPLICATIONS/MYANMAR/Baza%20wiedzy.one#Brak%20komunikacji%20z%20DHH%20od%20strony%20kraju.%20Np.%20Pricelist%20nie&section-id=\\\\\\\\{9275FC89-DE25-4053-A935-0246B426C25C}&page-id=\\\\\\\\{6685194F-9937-437F-9A1A-43879F0C77BD}&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%2FMYANMAR%2FBaza%20wiedzy.one%7C9275FC89-DE25-4053-A935-0246B426C25C%2FBrak%20komunikacji%20z%20DHH%20od%20strony%20kraju.%20Np.%20Pricelist%20nie%7C6685194F-9937-437F-9A1A-43879F0C77BD%2F%29])\']""]\nRelated Issues:\n[\'DGS-8995\']\n\n### End'}"
37,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8995\n\n### Instruction:\nRecipes exported from DHH are not arriving in DHC Compound anymore.\r\nSeveral recipes were sent, but none were imported after 11:12h.\r\n\r\nProbably a result of the upgrade.\r\n\r\nPlease check.\r\n\r\nRegards,\r\nRob\n\n### Response:\n[""Comment 1: [\'Hello,\\\\r\\\\rWe are investigating your issue. We will inform you about the solution as soon as possible.\\\\r\\\\rRegards\\\\r\\\\r\'"", ""Comment 2: \'!image-2023-04-19-16-53-11-208.png!\'"", ""Comment 3: \'!image-2023-04-19-16-54-16-305.png!\'"", ""Comment 4: \'a chwile pozniej!image-2023-04-19-16-55-42-145.png!\'"", ""Comment 5: \'logi dhh holdingu2023-04-19 17:06:45,868 [181] ERROR Evolution.DHHolding.Infrastructure.MessageHandlerBase`1 [(null)] - Error occurred when processing message of type Evolution.DHHolding.Interfaces.Stocks.StockChangedMessageSystem.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: Distributed transaction completed. Either enlist this session in a new transaction or the NULL transaction. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception"", \'Comment 6: Boolean breakConnection\', ""Comment 7: Action`1 wrapCloseInAction)\'"", ""Comment 8: \'Could you provide example of recipe ( item version)"", ""Comment 9: that I may try to resend ?\'"", ""Comment 10: \'czy to nie powinno być odkomentowane!image-2023-04-19-17-39-20-795.png!\'"", ""Comment 11: \'307302 is a nice one to try... it is also the most urgent one.\'"", ""Comment 12: \'trzeba było kopnać jeszcze te kolejkę!image-2023-04-19-18-00-08-556.png!\'"", ""Comment 13: \'The recipes are now going from dhh to DHC. About 307302 there are recipes up to 213 now "", \'Comment 14: but in DHH I can see version 214 I resend it\', ""Comment 15: but it may took a moment.\'"", ""Comment 16: \'Thank you Agniezka"", ""Comment 17: I see the recipes are being processed now.Can you think of a reason why the communication stopped (for future upgrades of DHC)?\'"", ""Comment 18: \'Please verify also version 214 for 307302"", ""Comment 19: should be in DHC in close future.\'"", ""Comment 20: \'Queue is filling up... still more recipes coming (see graph)!image!\'"", ""Comment 21: \' version 214 for 307302 has arrived :)\'"", ""Comment 22: \'May set this task too hold until you verify If everything comes to DHC or lower the priority?\'"", ""Comment 23: \'You may even close the ticket"", \'Comment 24: but I still would like to know the reason why this happened\', ""Comment 25: and how to avoid this in the future.\'"", ""Comment 26: \'Hello,In that case I will lower it to p2 until tomorrow morning"", \'Comment 27: hope to give you quick answer. But If there is a need from your sideto investigate the reasonof the issue\', ""Comment 28: we may raise RootCause Analysis (RCA)task for you.\'"", ""Comment 29: \'I think that is the plan. Close this task and raise a RCA please.For now... thank you for your invaluable support.Regards,Rob.\'"", ""Comment 30: \'RCA is underDGS-8995thank you\']""]\nRelated Issues:\n[\'DGS-8996\']\n\n### End'}"
38,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8994\n\n### Instruction:\nField Saldo on Financial Statement now is calculated with gross values from invoices and feed sales, but should be calculated with net values instad of gross values.\r\n\r\nIt should be changed in all sectors.\r\n\r\n\xa0 !image-2023-04-19-13-56-00-783.png!\r\n\r\n\xa0\n\n### Response:\n[""Comment 1: [\'zmieniona funkcja KR_FinancialStatementSaldo - dodatkowo dodana obsługa BV i EV z taska https://helpdesk.kotrak.com/browse/DGS-8714\'"", ""Comment 2: \'zmieniona funkcjaKR_FinancialStatementSaldo wrzucona już także na IBIP_DHzmieniona funkcjaKR_FinancialStatementSaldoMASBE na IBIP_DH_TEST.Do zmiany na TEST pozostałe sektory oprócz MAS NL i MAS BE\']""]\nRelated Issues:\n[\'DGS-8714\']\n\n### End'}"
39,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8993\n\n### Instruction:\nArticle is needed for dispatch today, so P1: \r\nArticle 088171 is an item with packing type = pcs. But in the WMO it\'s displayed as kg: therefore it cannot be taken in. Please check, see screenshots for 088171 compared to 088050\r\n\r\nVT-1131/4/23\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!afbeelding!!afbeelding-1!!afbeelding-2!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'088170 has the same issue...\'"", ""Comment 4: \'{code:java}SELECT count(*),BaseUnit  FROM [DHPlantVCBusinessLogicMain].[dbo].[Items]  where   PackingForm=4 and SettlementType=3   group by BaseUnit{code}!image-2023-04-19-09-22-02-330.png!\'"", ""Comment 5: \'these two items have BaseUnit as KG"", ""Comment 6: for pcs should be changed.088171 088170!image-2023-04-19-09-33-08-841.png!\'"", ""Comment 7: \'This has to be changed in the ERP?\'"", ""Comment 8: \'Yes,please make the change and the data will be sent to plants.\'"", \'Comment 9: ""We\\\'re on it\', \'Comment 10: thanks for explaining. Ticket can be closed""]\']\nRelated Issues:\n[]\n\n### End'}"
40,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8992\n\n### Instruction:\nIn ASN overview, a calloff is normally filtered out when a VT is created and it is not possible to add a second VT.\r\nSee eg. call off CL000028804, VT-386/4/23 was created, but the line is not filtered and the user can add another VT, even when VT is already closed. \r\nFor Andel, I found approx 60 call offs in total with this behaviour (DHP ASN list, sort on linked document).\r\n\r\nCan you check when an ASN is not correctly filtered when the VT is created? How can we prevent this? For this user it is not clear what is the status of these ASN\'s and sending a second VT for the same call off to PCS will give issues.\r\n\r\n \r\n\r\n\r\n\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!!image-1!!image-2!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'!image-2023-04-18-19-12-43-286.png!\'"", ""Comment 4: \'U nas na wersji 8.6 (.170)"", ""Comment 5: asn z utworzonymi vtkami są widoczne tylko przy opcji show all.!image-2023-04-18-19-41-09-786.png!!image-2023-04-18-19-22-12-811.png!\'"", ""Comment 6: \'From our annalist it is related toDGS-8837 and has the same cause,It is fix in 8,6 version.Are you able to cancel the wrong vt"", ""Comment 7: are this information sufficient for you ?\'"", ""Comment 8: \'Can you give me access to that ticket?\'"", ""Comment 9: \'please try now\'"", ""Comment 10: \'Ok"", ""Comment 11: I have access now. Indeed seems to be the same case. User did not create a second VT. He only asked about the filtering. So no cleanup is needed.This ticket can be closed.\']""]\nRelated Issues:\n[]\n\n### End'}"
41,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8991\n\n### Instruction:\nSee DGS-8651 which you closed without our permission\r\n\r\nThe point is that SORC-218/09 must be clipped with SOR-155/09\r\n\r\nThe user asks what exactly to do. How should he execute the yellow shaded without making CDN difficult again.\r\n\r\nHe has no working method of this, can she also provide it?\r\n\r\nHe assumes that after a new clipp document the Sorc can be clipped, but how do we get a new document to be clipped that is accepted by SORC218?\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: \'HelloUnfortunately"", \'Comment 4: I have not received the information that the xl operator does not understand the previous instructions\', ""Comment 5: can not operate ERP XL to the appropriate extent Also please let me know if you see my comment with the source task with this date :!image-2023-04-18-14-53-39-734.png! If yes please let me know what in this information the user did not understand .the solution was at the end :!image-2023-04-18-14-55-12-429.png!Did user try to cancell invoice 512/09/2022 and got some problems,Or user do not know how to cancell invoice?{color:#403294}*In this situation does the user need instructions or are we to perform these operations for the user ourselves?*{color}I would appreciate quick and precise answers.\']""]\nRelated Issues:\n[]\n\n### End'}"
42,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8990\n\n### Instruction:\nAccording to our agreement on last retro and based on DGS-7272 please prepare and implemente similar solution in other factories, in Grodzisk and Mieścisko\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Please be informed that we have forwarded the issue to the development team in order to internal analysis.We are waiting for more details and will be back with further information as soon as possible.\']""]\nRelated Issues:\n[]\n\n### End'}"
43,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8989\n\n### Instruction:\nCould you give:\r\nMinnen, Matteo <MMinnen@deheus.com>; \r\nBroek, Hans van de <hbroek@deheus.com>\r\n\r\nThe rights to create technical results?\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: \'Is it duplicated task to this one and we can close it?https://helpdesk.kotrak.com/servicedesk/customer/portal/56/DGS-8988\'"", ""Comment 3: \'Yes this is a dublicate. I am sorry"", ""Comment 4: I get a error message when creating the last one.\'"", ""Comment 5: \'Ok"", ""Comment 6: so I close this task\']""]\nRelated Issues:\n[\'DGS-8988\']\n\n### End'}"
44,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8988\n\n### Instruction:\nCould you give:\r\nMinnen, Matteo <MMinnen@deheus.com>; \r\nBroek, Hans van de <hbroek@deheus.com>\r\n\r\nThe rights to calculate technical results?\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 2: ""What do you mean about calculation technical results?There are no validations for this button on Financial statement. Do you have any example of document?Only when document is Archived it\\\'s not possible to edit anythin (also not possible to use this button) unless user has right to edit any document (we have a role for this and now few users have this rights like on screen. Users can edit any type of document in Archive)!image-2023-04-18-14-03-47-104.png!Should we add these users to this role?""]\']\nRelated Issues:\n[\'DGS-8989\']\n\n### End'}"
45,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8987\n\n### Instruction:\nIssue created on the basis of an e-mail notification.\r\n \r\nOn DHVD01AP09 there are a couple of services that will not start anymore. When trying to start the service, it states it cannot find the file specified.\r\n\r\n\n\n### Response:\n[""Comment 1: [\'[^Service issue on DHVD01AP09.msg] _(268 kB)_\'"", ""Comment 2: \'Powodem zgłoszenia był upgrade w ramach https://helpdesk.kotrak.com/browse/DGS-8630.Sprawa była dogadana z Thomasem"", ""Comment 3: w Premixie mieli nie pracować od 23\']""]\nRelated Issues:\n[]\n\n### End'}"
46,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8986\n\n### Instruction:\nEven after numerous resending of data from the ERP and synchronizing from DHH the items 506103* and recipes don\'t arrive in DHP.\r\nThere seems to be nothing wrong with them in DHC.\r\n\r\nCould you please have a look at it?\r\n\r\nRegards,\r\nRob.\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Hi,Shall I also resync967438?Regards\'"", ""Comment 3: \'Please do. Is that something I can do myself in the future?\'"", ""Comment 4: \'Recipe 506103 in plant now!image-2023-04-18-10-09-37-269.png!\'"", ""Comment 5: \'Thank you Aleksandra"", ""Comment 6: I will inform the users about it.\'"", ""Comment 7: \'Recipe for Andel is also in plant:!image-2023-04-18-10-22-00-963.png|width=669,height=294!To be honest"", \'Comment 8: part of processing is done under the db. This is known issue for Thomas and it is solved in DHC version 60 and highier.Please\', ""Comment 9: let us know if we can close this task.Regards\'"", \'Comment 10: ""If you could do your magic for the two other variants of the item first.... then you can close the ticket.They are the 506103-BB and 506103-Z20\', \'Comment 11: I still can\\\'t get them to DHP myself apparently.""\', ""Comment 12: \'Sure\'"", ""Comment 13: \'Thank you Aleksandra!\'"", ""Comment 14: \'!image-2023-04-18-10-46-48-919.png!\'"", ""Comment 15: \'All three are in Utrecht plant now.So I am closing this task as mentioned before.Regards\']""]\nRelated Issues:\n[]\n\n### End'}"
47,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8985\n\n### Instruction:\nHi\r\n\r\nWe have a Production recipe for GCN1392-T, version 1.0. However this version is not in DHP. Only version 0.0\r\n\r\nWhen we generate the subversion, then both version 1.0 and 1.1 goes to DHP.\r\nWe have another case too: GCN1390-T\r\n\r\nThis is happening to often. Could you please investigate why is this happening?\r\n\r\nThank you very much\n\n### Response:\n[""Comment 1: [\'Hi [~mberbert@deheus.com],For task DGS-8820 and DGS-8967 we have raised this RCA.Regards\'"", \'Comment 2: ""{code:java}select t.CreateDate,* from [Evolution_DHCountry].[dbo].[Technologies] tleft join [Evolution_DHCService].[dbo].[Technologies] tson t.id=ts.id where ts.id is nullorder by t.CreateDate desc{code}Sprawdzając braki technologi!image-2023-04-21-13-24-03-376.png!Jest 8 towarów jakby nie skończone linkowanie w DHCServer:{code:java}select * from DhhItems where Code=\\\'21837\\\'select * from DhhItems where Code=\\\'21837\\\'select * from Items where Code like \\\'21837%\\\' select h1.*,i1.* from [dbo].[DhhItems] h1 left join [dbo].[Items] i1 on h1.id=i1.DhhItemId where i1.DhhItemId is null andh1.BaseItemId is not null{code}!image-2023-04-21-13-24-39-598.png!""\', ""Comment 3: \'Hello,due to the manual linking of items the process as you can see below has not been completed by the operator:COB4421COB5051-T218382183121837COB5029For example item 21837:!image-2023-04-21-15-12-34-297.png!If the given raw material is not properly linked the production recipe and technologies will not be transferred to the plants.\']""]\nRelated Issues:\n[\'DGS-8820\', \'DGS-8967\']\n\n### End'}"
48,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8984\n\n### Instruction:\nGood afternoon, we have problem wit synchronization of  SO-537, it is not landing in DHC. The order is for foreign customer (export), and as far as I know it is first such case. Maybe there is an issue with county code (Burkina Faso)? \r\nAIS gives the the message (see the screen). \n\n### Response:\n[""Comment 1: [\'!image!!image-1!!image-2!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'order wysyłany 11.042023-04-11 16:06:11,961 [72] DEBUG Evolution.DHCERPService.ImplementationRestWoW.Savers.DataContractSaver`2 [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\18317313\\\\\\\\DHAPPSV3-DHCER400-JOB1\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.ImplementationRestWoW\\\\\\\\Savers\\\\\\\\DataContractSaver.cs:39] - Saving SalesOrderDataContractDeHeusWoW2023-04-11 16:06:11,976 [72] ERROR Evolution.DHCERPService.ImplementationRestWoW.Savers.DataContractSaver`2 [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\18317313\\\\\\\\DHAPPSV3-DHCER400-JOB1\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.ImplementationRestWoW\\\\\\\\Savers\\\\\\\\DataContractSaver.cs:49] - Evolution.DHCERPService.IdentityMapping.IdentityNotMappedException: Key of entity CustomerMappingEntity was not mapped. Key value Id: CIPC00070\'"", ""Comment 4: \'Country code seems ok. I found in erpintegrator logs that there is no customer with codeCIPC00070Please try to send first the customer from ERP to DHC"", ""Comment 5: then verify if it is viisble here :!image-2023-04-17-19-18-52-590.png!Then when it appears please resend order and verify.\'"", ""Comment 6: \'!image-3!\'"", ""Comment 7: \'Please verify data in your ERP application"", \'Comment 8: it seems that the the data in customer are incorrect. Please verify if the field country is not empty \', \'Comment 9: if yes\', ""Comment 10: fill it with correct value.We do not support and do not have access to your ERP system.\'"", \'Comment 11: ""Plugin return message: ERROR sending datacontract to webmethods.io.Bad request: Exception of type \\\'Evolution.DHCERPService.Service.Interface.ExceptionHandling.DataValidationException\\\' was thrown.CustomerAddressObject Id: 5637192585 Country Is required""\', ""Comment 12: \'This is the message I get from AIS when I exported the customer data to DHC. first it must be fixed before I resent the SO-537\'"", ""Comment 13: \'Yes but this address and customer is now only in YOUR ERP.Kotrak SA do not support this system. DO NOT HAVE access there"", \'Comment 14: DO NOT HAVE permissions to make any changes there.ASK someone who is this ERP Operator to create or correct this address.OR as I asked You before\', \'Comment 15: if you verified in that system\', \'Comment 16: that address is correct in that ERP \', \'Comment 17: please send some screenshot to show us that in program \', ""Comment 18: that the field named Country ( probably I do not know how this system looks) is completed.\']""]\nRelated Issues:\n[]\n\n### End'}"
49,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8983\n\n### Instruction:\nthe following production in pcs cannot be found as PLRs in DHP\r\nlot number : 202301130006 9004(6mm)-b20\r\n                     202304150002 9004(6mm)-b20\r\nkindly help\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'!image-2023-04-17-18-04-58-117.png!\'"", ""Comment 3: \'Lot number 202301130006 is in DHP as 0722130123003 but for other item!image-2023-04-17-18-10-21-960.png|width=671,height=276!You do not precise for what plant you are missing that plr.\'"", ""Comment 4: \'sorry i made a mistake with the first lot numberit is 202304130006 and it is tema plant\'"", ""Comment 5: \'brak wpisów tu dla lot z 15i 13 kwietnia!image-2023-04-17-19-39-03-591.png!\'"", \'Comment 6: ""Please I didn\\\'t find nothing in errors or log files. Could you please may ask you pcs provider if the plr\\\'s were sent? Or ask them to try again and send us date and our of that operation.""\', ""Comment 7: \'okay i will do that\'"", ""Comment 8: \'Waiting for your feedback then.Regards\'"", \'Comment 9: ""I see in the database that those batches are finished in manual mode. Due to the manual mode exports won\\\'t run\', \'Comment 10: the export is triggered by the PLC when the batch has finished.It is not possible to export these 2 lotnumbers by hand. this is the response from the pcs provider""\', ""Comment 11: \'Thank you response"", \'Comment 12: we do not have access to this database\', \'Comment 13: it seems it is not DHP database.So could this person send a screenshot\', ""Comment 14: so we can see date when it was send.Also could he verify LOGS in their application.Cause because it is not our we are not able to verify that,\'"", ""Comment 15: \'the pcs provider says that because the dosing was done manually"", ""Comment 16: data is not sent. what do we do in this case.\'"", \'Comment 17: ""Well\', \'Comment 18: we do not support your PCS. If PCS users and providers did sent it to DHP in correct in that case as a work around:You are able to add plr\\\'s for both items from DHP. Ask you PCS provider for data to create it to be correct.!image-2023-04-20-17-54-32-722.png!""\', ""Comment 19: \'ok thank you. please close\']""]\nRelated Issues:\n[]\n\n### End'}"
50,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8982\n\n### Instruction:\nWe have a small request. The guarantees section is a bit out of line with the rest of the margins, as you can see on the screenshot. Could you put this in line with the rest of the document?\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 3: ""Hi Steffen,we\\\'ve made changes in TEST and PROD environment.You can verify it.Best regards,Grzegorz""\', ""Comment 4: \'Hello"", \'Comment 5: This looks good\', ""Comment 6: thank you.\'"", \'Comment 7: ""Hi,I\\\'m closing the task.Best regards,Grzegorz""]\']\nRelated Issues:\n[]\n\n### End'}"
51,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8981\n\n### Instruction:\nplease i nee dan urgent answer to the following error in DHC and how to solve it. it is really causing issues for us.\r\n\r\nError of type XLApiException has been thrown (XLNowyDokument:33).\r\nAPI Name - XLNowyDokument\r\nAPI Result - 33\r\nFlags - 16\r\nBŁĘDY:|Nie udało się wymusić numeru dokumentu/niepoprawny numer. (NowyDokument-33)\n\n### Response:\n[""Comment 1: [\'Hello,Kindly approve lowering priority of this task to P2 as P1 issues are only those with a critical or a blocking impact on business processes . This seems not to be the case in this issue so we suggest decreasing the issue priority.Regards\'"", ""Comment 2: \'okay approved\'"", ""Comment 3: \'Please provide me with impacted VT number. Direct translation of the error is:Error of type XLApiException has been thrown (XLNewDocument:33).API Name - XLNewDocumentAPI Result - 33Flags - 16BUGS:|Failed to force document number/invalid number. (NewDocument-33)\'"", ""Comment 4: \'VT 340/4/23/MAG\'"", \'Comment 5: ""{code:java}2023-04-17 00:33:21,881 [8] INFO  Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor [(null)] - VehicleTicket - VT-340/2/2023/AC [Id: 2ac95ea4-c659-4b80-912e-4ff6d6d53b00]2023-04-17 00:33:21,881 [8] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor [(null)] - VehicleTicket Validator started - Evolution.ErpIntegrator.Extensions.VTOrderValidator.VehicleTicketOrderValidator2023-04-17 00:33:21,928 [8] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor [(null)] - VehicleTicket Validator finished - Evolution.ErpIntegrator.Extensions.VTOrderValidator.VehicleTicketOrderValidator2023-04-17 00:33:22,053 [12] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateWarehouseMovementReceipt [(null)] - GenerateWarehouseMovementReceipt execution started2023-04-17 00:33:22,116 [12] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2020.Transactions.XLTransaction [(null)] - XL transaction created\', \'Comment 6: token ID - A9;:>L8PO1G51lAK_JbP==5---.SH---2023-04-17 00:33:22,194 [12] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateWarehouseMovementReceipt [(null)] - Creating WMR+ element for vte Id: 58046c96-a30a-4acd-ac42-68c418020ed4 (1003400 - 22500.000000)2023-04-17 00:33:22,256 [12] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateWarehouseMovementReceipt [(null)] - Found 0 WMR- () for order IO-582/232023-04-17 00:33:22,287 [12] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2020.Transactions.XLTransaction [(null)] - XL transaction rollbacked\', ""Comment 7: token ID - A9;:>L8PO1G51lAK_JbP==5---.SH---2023-04-17 00:33:22,287 [12] DEBUG Evolution.ErpIntegrator.DHC.DHC30.Database.DhcTransaction [(null)] - DHC transaction rollback staeted2023-04-17 00:33:22,287 [12] DEBUG Evolution.ErpIntegrator.DHC.DHC30.Database.DhcTransaction [(null)] - DHC transaction rollback finished2023-04-17 00:33:22,303 [12] ERROR Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateWarehouseMovementReceipt [(null)] - Can\'t find WMR- document to map to WMR+Evolution.ErpIntegrator.ERP.Interfaces.Exceptions.WarehouseMovementReleaseNotMappedException: Can\'t find WMR- document to map to WMR+   at Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateWarehouseMovementReceipt.MapWarehouseMovementRelease(VehicleTicket vehicleTicket"", \'Comment 8: InternalOrder internalOrder\', \'Comment 9: WarehouseMovementReceipt warehouseMovementReceipt)   at Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateWarehouseMovementReceipt.OnExecute(VehicleTicket vehicleTicket)2023-04-17 00:33:22,381 [12] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateWarehouseMovementReceipt [(null)] - GenerateWarehouseMovementReceipt execution finished{code}""\', ""Comment 10: \'{code:java}2023-04-17 13:17:23,613 [14] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateWarehouseMovementReceipt [(null)] - GenerateWarehouseMovementReceipt execution finished2023-04-17 13:17:23,910 [9] INFO  Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor [(null)] - VehicleTicket - VT-340/4/2023/AC [Id: e4e59c58-ba22-4c83-9fce-2d64540747a2]2023-04-17 13:17:23,910 [9] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor [(null)] - VehicleTicket Validator started - Evolution.ErpIntegrator.Extensions.VTOrderValidator.VehicleTicketOrderValidator2023-04-17 13:17:23,910 [9] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor [(null)] - VehicleTicket Validator finished - Evolution.ErpIntegrator.Extensions.VTOrderValidator.VehicleTicketOrderValidator2023-04-17 13:17:24,270 [8] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateSalesOrderRelease [(null)] - GenerateSalesOrderRelease execution started2023-04-17 13:17:24,488 [8] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateSalesOrderRelease [(null)] - Forcing document number - 805/4/2023/MAG for vt element id - Id: 7a1e4ad0-e080-4b91-8abf-f96647fefdc22023-04-17 13:17:24,660 [8] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateSalesOrderRelease [(null)] - VehicleTicketElement Validator started - Evolution.ErpIntegrator.Extensions.VTOrderValidator.VehicleTicketOrderValidator2023-04-17 13:17:25,363 [8] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateSalesOrderRelease [(null)] - VehicleTicketElement Validator finished - Evolution.ErpIntegrator.Extensions.VTOrderValidator.VehicleTicketOrderValidator2023-04-17 13:17:25,379 [8] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2020.Transactions.XLTransaction [(null)] - XL transaction created"", \'Comment 11: token ID - gEl.P/^14Q7<8M]H^h`7A-5----_C]--2023-04-17 13:17:25,379 [8] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2020.Documents.Ordes.CdnXL2020OrderRepository [(null)] - Found reservation 1\', \'Comment 12: 2960142023-04-17 13:17:25,395 [8] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2020.Documents.Ordes.CdnXL2020OrderRepository [(null)] - Found reservation 1\', \'Comment 13: 2960152023-04-17 13:17:25,395 [8] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2020.Documents.Ordes.CdnXL2020OrderRepository [(null)] - Found reservation 1\', \'Comment 14: 2960132023-04-17 13:17:25,410 [8] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2020.Documents.Ordes.CdnXL2020OrderRepository [(null)] - Found reservation 1\', \'Comment 15: 2960162023-04-17 13:17:25,410 [8] INFO  Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateSalesOrderRelease [(null)] - Prcision 22023-04-17 13:17:25,410 [8] INFO  Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateSalesOrderRelease [(null)] - Prcision 22023-04-17 13:17:25,410 [8] INFO  Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateSalesOrderRelease [(null)] - Prcision 22023-04-17 13:17:25,410 [8] INFO  Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateSalesOrderRelease [(null)] - Prcision 22023-04-17 13:17:25,426 [8] DEBUG Evolution.ErpIntegrator.CdnXL.Interfaces.Documents.ExternalOrderTransactions.XLAPIExternalOrderTransaction [(null)] - NB Flag - Class = Net\', ""Comment 16: API = N2023-04-17 13:17:25,754 [8] ERROR Evolution.ErpIntegrator.CdnXL.CdnXL2020.Documents.ExternalOrderTransactions.CdnXL2020ExternalOrderTransactionRepository [(null)] - Error of type Evolution.ErpIntegrator.CdnXL.CdnXL2020.XLApiException has been thrown (XLNowyDokument:33).API Name - XLNowyDokumentAPI Result - 33Flags - 16B£ʄY:|Nie uda³o si꠷ymusi栮umeru dokumentu/niepoprawny numer. (NowyDokument-33)   at Evolution.ErpIntegrator.CdnXL.CdnXL2020.Documents.ExternalOrderTransactions.CdnXL2020ExternalOrderTransactionRepository.CreateHeader(XLExternalOrderTransaction documentHeader) in C:\\\\\\\\TeamCity\\\\\\\\buildAgent\\\\\\\\work\\\\\\\\57a7e278b67a115c\\\\\\\\Evolution.ErpIntegrator\\\\\\\\CdnXL\\\\\\\\Evolution.ErpIntegrator.CdnXL.CdnXL2020\\\\\\\\Documents\\\\\\\\ExternalOrderTransactions\\\\\\\\CdnXL2020ExternalOrderTransactionRepository.cs:line 792023-04-17 13:17:25,754 [8] ERROR Evolution.ErpIntegrator.CdnXL.CdnXL2020.Transactions.XLTransaction [(null)] - XL rollback error - possibly no transactionError of type Evolution.ErpIntegrator.CdnXL.CdnXL2020.XLApiException has been thrown (XLTransakcja - Rollback:-1).API Name - XLTransakcja - RollbackAPI Result - -1{code}\'"", ""Comment 17: \'zamowienie dla podanego vt[[DHC] generowanie dokumentów z VT|onenote:https://kotrak.sharepoint.com/sites/erpasysta/Shared%20Documents/Baza%20wiedzy/Baza%20Wiedzy%20-%20ERPSD/Klienci/DEHEUS/DEHEUS%20APPLICATIONS/RPA/Baza%20wiedzy.one#%5bDHC%5d%20generowanie%20dokument%C3%B3w%20z%20VT&section-id=\\\\\\\\{A2F09CD6-A23A-42F3-92F5-ED66B521455B}&page-id=\\\\\\\\{AFD9446F-4C74-4FAE-9502-1F02911E382C}&end] ([Widok sieci Web|https://kotrak.sharepoint.com/sites/erpasysta/_layouts/OneNote.aspx?id=%2Fsites%2Ferpasysta%2FShared%20Documents%2FBaza%20wiedzy%2FBaza%20Wiedzy%20-%20ERPSD&wd=target%28Klienci%2FDEHEUS%2FDEHEUS%20APPLICATIONS%2FRPA%2FBaza%20wiedzy.one%7CA2F09CD6-A23A-42F3-92F5-ED66B521455B%2F%5BDHC%5D%20generowanie%20dokument%C3%B3w%20z%20VT%7CAFD9446F-4C74-4FAE-9502-1F02911E382C%2F%29])\'"", \'Comment 18: ""SELECT vt.ExpectedElementsQuantity\', \'Comment 19: vee.DocumentNumber,vt.documentnumber,d.* FROM [dbo].[VehicleTickets] vt  join [dbo].[VehicleTicketElements] ve on vt.Id=ve.VehicleTicketId join [dbo].[VehicleTicketElementERPDocuments] vee on vee.VehicleTicketElementId=ve.Id join [dbo].[VehicleTicketDocumentNumbers] d on d.Id=ve.DocumentNumberId where vt.id = \\\'1D34D81C-0CEF-4B9A-B0B5-B957978A0EC7\\\' or d.id in ( select id from [dbo].[VehicleTicketDocumentNumbers] where DocumentYear=2023 and DocumentMonth=4 )order by d.DocumentNumber desc""\', ""Comment 20: \'!image-2023-04-17-14-50-43-569.png!\'"", ""Comment 21: \'Good morningWhile reviewing the request"", \'Comment 22: we noticed that there was a problem with the operation of erp xl on server 10.233.3.20.This is a bug which sometimes happens in ERPXL\', \'Comment 23: when the user mainly uses a language version other than Polish.This situation caused a problem with generation of documents - it has been fixed.As for the error itself\', \'Comment 24: it can be translated to"" Failed to force document number/invalid number.""It is due to the fact that in dhc is generated maximum document number predicted for VTwhich is already used in ERP XL ( it is about the full document number including series ).When such situation happened sometimes in other countries were single SOR documents generated manually by the operator then we suggest that you cancel the documents made manually\', \'Comment 25: then the number is released and you can generate an SOR document from DHC\', \'Comment 26: and the manual document from another order is then created again by the operator.I verified that recently for SOR documents with ""mag"" series from April\', \'Comment 27: the maximum number generated from dhc is SOR SOR-696/23/MAG with vt 34/4/2023/AC. However\', \'Comment 28: since then in erp xl for sales orders with MAG series\', \'Comment 29: there were manually generated SOR documents that block the indicated number.In addition\', \'Comment 30: after erp xl was repaired\', \'Comment 31: the message given appeared for some cases - so it is possible that some of the ungenerated SOs in dhc were generated manually.Like here :!image-2023-04-17-17-19-54-875.png!this message means that the source document\', \'Comment 32: i.e. SO is in the status not allowing executionSO for that vt is 811. This order is already executed in erp xl!image-2023-04-17-17-23-15-370.png!SOR documents with mag series for April generated by a non-erpint operator are currently 134.So numbers from 697 up tu 806 are blocked.In that case for the first one I am asking you to as users ( mainly Hdabi - who created all documents from that list) to stop creating manual SOR for SO for MAG series until we solve this,The second thing\', \'Comment 33: please review the given file in the first sheet is a list of vt for which there may be a problem with the generation.  The second sheet is the number of SOR and orders.  Please have them reviewed and decisions made or executed : their cancellation  If any SOr on the list concerned an order related to ""hanging vt""\', ""Comment 34: please add in the file what about the document in the following columns. !image-2023-04-17-17-40-50-483.png![^sors.xlsx]I!image-2023-04-17-17-40-50-483!\'"", \'Comment 35: ""select trn_gidnumer,cdn.nazwaobiektu(TrN_GIDTyp,trn_gidnumer,1,2) as numberSOR,--TrN_OpeNumerW,cdn.NazwaObiektu(zan_gidtyp,zan_gidnumer,1,2) as Ordernumber from cdn.tranag left join cdn.zamnag on zan_gidnumer=TrN_ZaNNumerwhere trn_gidtyp in ( 2001) and TrN_RokMiesiac=202304 and trn_trnnumer >=697 and trn_openumerw<>2and trn_stan not in (6) and TrN_TrNSeria in (\\\'mag\\\')SELECT vt.ExpectedElementsQuantity\', \'Comment 36: vee.DocumentNumber,vt.documentnumber\', \'Comment 37: d.* FROM [dbo].[VehicleTickets] vt  join [dbo].[VehicleTicketElements] ve on vt.Id=ve.VehicleTicketId join [dbo].[VehicleTicketElementERPDocuments] vee on vee.VehicleTicketElementId=ve.Id join [dbo].[VehicleTicketDocumentNumbers] d on d.Id=ve.DocumentNumberId where vt.id = \\\'1D34D81C-0CEF-4B9A-B0B5-B957978A0EC7\\\' or d.id in ( select id from [dbo].[VehicleTicketDocumentNumbers] where DocumentYear=2023 and DocumentMonth=4 ) and vee. DocumentNumber is null  order by d.DocumentNumber desc""\', ""Comment 38: \'okay your submission is well noted"", ""Comment 39: is there a way we can see which document number an SOR is supposed to have?\'"", ""Comment 40: \'so if i should cancel all the SORs in the list will it resume automatic generation?\'"", ""Comment 41: \'Yes in cases where there is a connection to vt in DHC,For other cases the SO will be confirmed or in progress.You may verify them later.\'"", ""Comment 42: \'okay then \'"", ""Comment 43: \'Will you cancel the Sors? If yes I will wait until you did it. I\'"", ""Comment 44: \'i will speak to finance if i can cancel the SORs"", ""Comment 45: if not i will let you know\'"", ""Comment 46: \'we have identified SORs we want to cancel"", \'Comment 47: we want to be sure if we should go ahead and cancel them\', ""Comment 48: can we force the start of automatic document generation?\'"", ""Comment 49: \'And we also need the excel list for Johnson as well"", ""Comment 50: you only sent MAG\'"", \'Comment 51: ""Please ignore what i have said earlier.The main issue now is all the SORs on the list has to be reported to head quarters this week and from Finance they are advising that we don\\\'t cancel anything and if we do not cancel anything\', \'Comment 52: is it possible to force the automatic generation starting from the last available SOR number?""\', ""Comment 53: \'I need to contact with developers with that - as I understand you want the SORs to be started with the first free number yes ?Automatic generation is still working"", \'Comment 54: but for some documents where you have an error.I prepare second file with 2 sheets in first you have vt with existing document number ( api-33) and in second sheet you have few VT\', ""Comment 55: that are related to orders that SOr documents generated manually as you can see.We may mapp this douments.For error api-33 we need to consult it with our developers.Also it looks that works willworks may exceed the 3 rbh.[^ghana_analisys2.xlsx]\'"", \'Comment 56: ""Przydatne selectySELECT vt.ExpectedElementsQuantity\', \'Comment 57: vee.DocumentNumber,vt.documentnumber\', \'Comment 58: vee.message,o.DocumentNumber as ordernumber\', \'Comment 59: o.id as orderid\', \'Comment 60: d.*FROM [dbo].[VehicleTickets] vtjoin [dbo].[VehicleTicketElements] ve on vt.Id=ve.VehicleTicketIdjoin [dbo].[VehicleTicketElementERPDocuments] vee on vee.VehicleTicketElementId=ve.Idjoin [dbo].[VehicleTicketDocumentNumbers] d on d.Id=ve.DocumentNumberIdjoin dbo. OrderElements oe on oe.Id=ve.OrderElementIdjoin dbo.orders o on o.id=oe.OrderId-- join [ERPXL_GHA_PROD] .cdn.TraNag erp on erp.trn_gidnumer=pt.XlIdwhere d.id in (select id from [dbo].[VehicleTicketDocumentNumbers] where DocumentYear=2023 and DocumentMonth=4 ) and vee.DocumentNumber is null and vee.Message is not null order by d.DocumentNumber desci dla wyfiltrowanych błędów z api-158 czyli tam gdzie status zamowienia jest złyselect ERPXL_GHA_PROD.CDN.nazwaobiektu(zan_gidtyp,zan_gidnumer,1,2)\', \'Comment 61: ERPXL_GHA_PROD.CDN.nazwaobiektu(TrN_GIDTyp,TrN_GIDNumer,1,2),z.zan_stan\', \'Comment 62: TrN_OpeNumerW from DhcErpPlugin_GHA_Prod.dbo.OrderSyncs pojoin ERPXL_GHA_PROD.cdn.ZamNag z on z.zan_gidnumer=xlidjoin ERPXL_GHA_PROD.cdn.TraNag t on t.trn_zannumer=z.ZaN_GIDNumerwhere po.DhcId in (\\\'6DE29D59-8F78-4647-A4FB-D619E6E0F6FA\\\',\\\'7610DC71-A50A-4057-A2E5-D6EBEFD81A2E\\\',\\\'12F2ED3C-66A1-4C75-BE90-AE82A5B4C4B0\\\',\\\'A9776347-68EF-49CD-A720-EC8EE38DCB91\\\',\\\'28443909-7191-40BA-9B0C-F6AAF0CC29C4\\\',\\\'2E226F97-2A0C-496E-BEDF-E1E3D49842A3\\\',\\\'5247F3C3-A272-4D10-9D3D-172703B28924\\\')erpint ma gidnumer 2 więc ostatniej kolumnie jak nie ma 2 znaczy to że oni wystawili.""\', ""Comment 63: \'what do you mean by mapping these documents please?\'"", \'Comment 64: ""Hello,I clicked all documents vt in april with the error api-result=33It took about 1 rbh.AsAs I informed you\', \'Comment 65: the part with the error api-33 ( no number) turned into 158 - that is\', \'Comment 66: they are VTs connected to orders already completed in part or in full. Sometimes there are 2-3 such cases in other customers then we can map the SOR document in ERPXL and DHC. However\', \'Comment 67: currently - at 8 pm such cases are with you : 112 VT. Counting for each about 10-15 minutes for updates it is about 28- manhours.And there still be 36 vt blocked by numeration.And the last free number is also set in DHP\', \'Comment 68: so I guess it may be also 2-3 hours of our work.I understand that the finance department may not be pleased to have to cancel erroneously generated documents by document users. However\', \'Comment 69: cancellation is the simplest\', \'Comment 70: fastest\', \'Comment 71: and safest solution in this situation. I can prepare for you a filter on the SOR list in erp xl\', \'Comment 72: which will search for all documents from April\', ""Comment 73: with the series \'mag\' created by an operator other than erp xl.You may then checked all filter documents and then just cancel it.Then maybe there will be need to press generate on hanging vt from april from Thema"", \'Comment 74: but we or you may do it\', \'Comment 75: and it want take more then 1 or max 2 hours\', \'Comment 76: to verify or resynchronised that.ALSO ASK YOUR TEAM to stop generating SOR\', \'Comment 77: until we finished blocking function.""\', ""Comment 78: \'ookay i understand you.I have asked them to stop generating SORs but it is not only tema but johnson also\'"", ""Comment 79: \'i mean it is not only mag but johnson also\'"", ""Comment 80: \'please create the filter for the series mag and jons please\'"", ""Comment 81: \'I do not know If you understand"", \'Comment 82: that this task is for problem with api-result-33 error message on vt.I do not see that VT with that error wich diffrent plant.If you see that VT for that plant are not generated for diffrent reason please create other task.For case I am trying to explain you I am asking for your decision,a. Do you agree to cancel incorrect SOR documents ?- and you will do It?b. Do you want other solution that could cost you about 30 man-hoursPlease send one clear response\', \'Comment 83: because\', \'Comment 84: every single comment\', \'Comment 85: which does not allow us to start any work\', \'Comment 86: it only disturbs the way SLa is calculated in this task. In addition\', \'Comment 87: if you would decide to second change suggest changing the type of request to Service Request because it is a large amount of work that is due to user errors or create new SR\', ""Comment 88: for fixing about 150 VT.\'"", ""Comment 89: \'We agree to cancel incorrect SOR documents and we will do it\'"", ""Comment 90: \'Ok so as I mentioned I created a filter so you can find all documents on SOR listwith that criteria : type=SOR"", \'Comment 91: created by user different then erp_integrator\', \'Comment 92: from april 042023\', ""Comment 93: with mag series.!image-2023-04-21-16-00-23-278.png!If you need to have some information for future what will be cancell you may use export to excel after you filtered that!image-2023-04-21-16-01-35-999.png!Please verify.\'"", ""Comment 94: \'okay\'"", ""Comment 95: \'i cannot find the filter \'"", ""Comment 96: \'!image!\'"", ""Comment 97: \'use module sales !image-2023-04-21-18-14-22-014.png!\'"", ""Comment 98: \'that is what i used\'"", \'Comment 99: ""let\\\'s meet on teams on Monday""\', ""Comment 100: \'Hellooo so i realised when i use the filter it only filters for MAG but not JOHNSON\'"", \'Comment 101: ""YESdid you read/see my previus comments - are all my comments visiblePlease read that and let me know if for vt that was matter for that task that were reason for THAT issue after cancellation it works fine.CAUSE AS I ALSO EXPLAINED YOU BEFORE\', \'Comment 102: for series different than mag there were no errors likeAPI Result - 33.So please if there are problem with Vt from Johnson CREATE A NEW TASK.And for VT\\\'s from Tema plant. Did you cancel them and they were generated successfully?!image-2023-04-25-10-11-40-462.png!""\', ""Comment 103: \'okay understood\'"", ""Comment 104: \'the SORs have been cancelled what is the next steps\']""]\nRelated Issues:\n[]\n\n### End'}"
52,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8980\n\n### Instruction:\nProduct 329900 is available in DHC, but not in DHP Helmond. Can you resend it to DHP Helmond?\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Item is in DHP now  !screenshot-1! \'"", \'Comment 3: ""Thanks\', \'Comment 4: it\\\'s working now.""\', ""Comment 5: \'Thank you for confirmation.\\\\rFrom DHC version 3.0.60 problem should not occur.\']""]\nRelated Issues:\n[]\n\n### End'}"
53,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8979\n\n### Instruction:\nHi, task from Paulina\r\n\r\nRafał Boniecki\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: \'Trigger has been disabled. Immediately after making changes"", ""Comment 4: please let me know if it can be turned on.\'"", ""Comment 5: \'Please let me know if the trigger can be enabled\'"", ""Comment 6: \'No"", ""Comment 7: we will turn it on ourselves if we need.\'"", ""Comment 8: \'Task to close.\'"", ""Comment 9: \'ok"", \'Comment 10: but we would like to inform you that the trigger was created to ensure the correctness of the provisions regarding fixed-term contracts\', \'Comment 11: its disabling may cause numerous irregularities in the system. The trigger should be constantly on\', \'Comment 12: only in exceptional situations (due to the layout of old data) it can be turned off for a while. If incorrect data is multiplied\', ""Comment 13: turning it on this trigger will generate enormous number of error messages.\']""]\nRelated Issues:\n[]\n\n### End'}"
54,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8978\n\n### Instruction:\nHi, \r\n\r\nThese item (883486200030, 883486500030, 883486900070) are zero quantity in Item screen. However, when I check with Administrator >>special function>> Restore Item stock, I do see transaction (please refer attached for more details). What kinds of these transactions are? Why cannot I restore it?\r\n\r\nBest Regards, \r\n\r\nClara\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: ""Hi Clara,On your screenshot I can see ERP XL version 2020\', \'Comment 4: however\', \'Comment 5: in our accesses I don\\\'t have information about server with 2020 versio. Could you please provide me with the ip address of the relevant server?Regards""\', ""Comment 6: \'Hi,I do raise for Food Business. Please reach there 10.95.1.41:3339.\'"", ""Comment 7: \'Hi"", \'Comment 8: Are you able to access it? Best Regards\', ""Comment 9: Clara\'"", ""Comment 10: \'Hi"", ""Comment 11: Any update? \'"", ""Comment 12: \'We are working on this issue.Regards\'"", ""Comment 13: \'What database?!image-2023-04-20-11-41-07-633.png!I should start that password: Admin@123 does not work for none of above DB.!image-2023-04-20-11-41-55-278.png!Regards\'"", ""Comment 14: \'Please work on DHF_MM\'"", ""Comment 15: \'But the passwordAdmin@123 does not work\'"", ""Comment 16: \'Last time has no issue. Any way please try again.\'"", ""Comment 17: \'Item stock restoration in history mode allows you to determine what happened to the items historically.Analysis below: # Item 883486200030When you double-click on the item"", ""Comment 18: you can see that there is a difference for the stock quantity forIR+211/04/23/Y!image-2023-04-20-14-24-26-126.png!If there is a delivery document in the details!image-2023-04-20-14-25-03-536.png!you can go to History and find the differences!image-2023-04-20-14-26-06-810.png!!image-2023-04-20-14-27-08-126.png!you can find the reason for the differenceThis document need to be confirm - WR--936/04/232.883486500030!image-2023-04-20-14-34-51-009.png!Same document:!image-2023-04-20-14-36-14-736.png!3.883486900070!image-2023-04-20-14-37-28-084.png!Same document:!image-2023-04-20-14-38-28-903.png!!image-2023-04-20-14-41-26-871.png!\'"", ""Comment 19: \'This document must be confirmed WR--936/04/23 and created related trade document.Another way is to delete this WR--936/04/23 ( if it is incorrect).There will be differences if there is no complete set of documents.\'"", ""Comment 20: \'Hi"", ""Comment 21: I will check with user and proceed. You can close the ticket now. Thanks\']""]\nRelated Issues:\n[]\n\n### End'}"
55,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8977\n\n### Instruction:\nHi\r\n\r\nPleas help to check this PLR 4361200323092 in Hai Phong 2 Plant ( 0436).\r\n\n\n### Response:\n[""Comment 1: [\'[^PLR - 4361200323092.docx] _(170 kB)_\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'View from App!image-2023-04-17-08-46-36-705.png!\'"", ""Comment 4: \'!image-2023-04-17-08-49-15-009.png!!image-2023-04-17-08-50-24-894.png!\'"", \'Comment 5: ""Hi,I tried to verify your issue but:>> there is no PLR: 4361200323092 visible in the app update: found it by PrO number>> I can see it under database but in PLR\\\'s elements I can see only one element: item1002010 Could you please explain that?""\', \'Comment 6: ""{code:java}SELECT *  FROM [DHPlantProdBusinessLogicMain].[dbo].[ProductionLots] where LotNumber = \\\'4361200323092\\\'  SELECT *  FROM [DHPlantProdBusinessLogicMain].[dbo].[ProductionLotElements] where RecipeId = \\\'241D59C2-D7DB-4D0A-BDCB-809E5171D163\\\' --and ItemId = \\\'6166FA3D-93F8-4A21-962D-018997A344AF\\\'   SELECT *  FROM [DHPlantProdBusinessLogicMain].[dbo].[Recipes] where ItemId = \\\'87130F35-55F0-41D1-97C1-5C9141434D19\\\'  SELECT *  FROM [DHPlantProdBusinessLogicMain].[dbo].[RecipeElements] where Id = \\\'241D59C2-D7DB-4D0A-BDCB-809E5171D163\\\'   SELECT *  FROM [DHPlantProdBusinessLogicMain].[dbo].[Items]  where code = \\\'2579\\\'  SELECT *  FROM [DHPlantProdBusinessLogicMain].[dbo].[Items] where id in (\\\'6166FA3D-93F8-4A21-962D-018997A344AF\\\',\\\'EC557595-73C0-41DA-B98C-D827B824026C\\\',\\\'47266428-01DF-42AF-818C-6A326688E5CB\\\'){code}""\', ""Comment 7: \'!image-2023-04-17-09-11-45-719.png!!image-2023-04-17-09-12-12-445.png!\'"", ""Comment 8: \'!image-2023-04-17-09-26-52-906.png!\'"", ""Comment 9: \'!image-2023-04-17-09-41-47-853.png!!image-2023-04-17-09-41-16-666.png!\'"", ""Comment 10: \'Cześć [~maciej.dobrzanski@kotrak.com]Maciej,[~marcin.block@kotrak.com]sugerujena analize w Developmencie"", ""Comment 11: to też zostawiam ciekawy kejs :P :)\'"", ""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: \'Hello,Is there any update on this issue?\'"", ""Comment 14: \'Hi [~Hardy.huy@deheus.com],We have planned to work on this ticket tomorrow\'"", ""Comment 15: \'[~marcin.block@kotrak.com] będzie rozmawiał z Ericiem\'"", ""Comment 16: \'[~maciej.dobrzanski@kotrak.com] [~marcin.block@kotrak.com]dziękuję <3\'"", ""Comment 17: \'hi Maciej"", \'Comment 18: this is user mistake. please close this case. this bagging recipe should not be prepare by this way. Normally\', ""Comment 19: bagging recipe will have 1 bulk and 1 empty bag.\'"", ""Comment 20: \'We are closing this task. Thank you.\'"", ""Comment 21: \'Hi [~Eric.quang@deheus.com]Thsnk you for the response\']""]\nRelated Issues:\n[]\n\n### End'}"
56,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8976\n\n### Instruction:\nHi,\r\nWe can not preview all printout\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: \'wydruki nie chodziły tez 16 i 15 mieli jakies bledy!image-2023-04-17-03-24-41-689.png!\'"", ""Comment 4: \'było przy wejsciu na serwer 503"", \'Comment 5: usluga niby działa\', ""Comment 6: teoretycznie,profilaktycznie restart usługi potem puli na iis !image-2023-04-17-04-09-06-849.png!teraz infow logach ndal o błedzie ale ze maszyna na ktorej jest ssrs odmawia dostępu !image-2023-04-17-04-06-48-230.png!!image-2023-04-17-04-08-11-895! !image-2023-04-17-04-09-06-849!\'"", ""Comment 7: \'bledy z uslugie srrs sprzed restartu: !image-2023-04-17-04-16-48-364.png!!image-2023-04-17-04-15-40-493.png!\'"", ""Comment 8: \'Widzę że ktoś u nas (?)coś zmieniał!image-2023-04-17-04-27-47-215.png!\'"", ""Comment 9: \'odnośnie daty licencji wyglada ze jest expired od 13.01ale to moze tez wskazywac na jakis blad w konfig ?!image-2023-04-17-04-35-19-217.png!\'"", ""Comment 10: \'Please let me know since when there are problems with Reporting Services"", ""Comment 11: have you done any work on it recently? Or on server10.84.162.71?The problems may indicate problems with the license for Reporting Services\'"", ""Comment 12: \'install that from Kotrak side and it have issue in this morning.what we have to do to solve thís?\'"", ""Comment 13: \'The situation requires verification and possible repair of the configuration of reporting services"", \'Comment 14: it is necessary to support the development team because to make the correct configuration\', \'Comment 15: including in terms of DHP. I forward this information to our development team\', ""Comment 16: assistance will be available in about 3 hours.\'"", ""Comment 17: \'in case continue issue"", ""Comment 18: please install SSRS in 10.84.162.72.\'"", ""Comment 19: \'hi,you can close the ticket\'"", ""Comment 20: \'update tematu: powód DGS - licencje SSRS wygasły\']""]\nRelated Issues:\n[]\n\n### End'}"
57,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8975\n\n### Instruction:\nHi\r\n\r\nWe created a STK-LO for location PRODUÇÃO which has 3 WMS locations.\r\nWhen we try to Confirm the WO(STK-LO), system shows an error message.\r\nCould you please confirm this WO document? Or cancel it.\r\nThere is only this 3 location to finish\r\n\r\nWe are stuck with no action.\r\n\r\nThank you\n\n### Response:\n[""Comment 1: [\'!image-1!!image-2!\'"", ""Comment 2: \'Hello,\\\\r\\\\rWe are investigating your issue. We will inform you about the solution as soon as possible.\\\\r\\\\rRegards\'"", ""Comment 3: \'Hello,could you bring back a new password for my user for mubrasil domain. - AjanuszewskaI am not able to log on.!image-2023-04-14-22-23-59-601.png!\'"", ""Comment 4: \'Hi [~lalmeida1@deheus.com]Could you please help us with this access?Thank you\'"", ""Comment 5: \'Hi [~Agnieszka.Januszewska@kotrak.com]You are using wrong domain.It must be LATAM.corp.deheus.comThank you\'"", ""Comment 6: \'!image-2023-04-14-22-40-12-802.png!\'"", ""Comment 7: \'it works thank You\'"", \'Comment 8: ""select *into dbo.StorageLocationsBack2from dbo.StorageLocationswhere ParentId = \\\'0b024a71-b586-49e3-a4c8-9237c088801b\\\'--update dbo.StorageLocations--set ParentId = null--where ParentId =\\\'0b024a71-b586-49e3-a4c8-9237c088801b\\\'""\', ""Comment 9: \'Could you try to confirm WOSTK please?\'"", ""Comment 10: \'WO are procesable please verify!image-2023-04-14-23-23-55-621.png!\'"", ""Comment 11: \'[[DHP 3.0] Inwentaryzacja "", ""Comment 12: 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])\'"", \'Comment 13: ""Hi AgnieszkaNow we can see WO on mobile scanners. Thank youI\\\'d like to ask your help to wait until we finish this coiunting and Settle this STK.So you can lower to P2Thank you""\', ""Comment 14: \'HiThank you for the support.You can close this task\'"", ""Comment 15: \'Hi [~mberbert@deheus.com]@lalmeida1@deheus.com,Could you be so kind and reply my email?Regards\'"", \'Comment 16: ""Hi [Aleksandra.Przybylek@kotrak.com]I asked for [~lalmeida1@deheus.com]\\\'s help in the email.Thank you""\', ""Comment 17: \'Thank you Maicon :)\']""]\nRelated Issues:\n[\'DGS-8246\']\n\n### End'}"
58,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8974\n\n### Instruction:\nUnable to run historical prices, when run they either time out or a blank screen appears with no indication as to whether it is running or not. \r\n\r\nServer stack trace: \r\n   at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)\r\n   at System.ServiceModel.Dispatcher.RequestChannelBinder.Request(Message message, TimeSpan timeout)\r\n   at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)\r\n   at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)\r\n   at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)\r\n\r\nException rethrown at [0]: \r\n   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)\r\n   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)\r\n   at DHCDNRMPriceService.Contracts.IDHCDNRMPriceService.GetHistoricPriceDocumentsWithPaging(PageRequest`1 request)\r\n   at Kotrak.XLInterface.RMPrices.Infrastructure.WcfService.DHCDNRMPriceServiceClient.GetHistoricPriceDocumentsWithPaging(PageRequest`1 request) in E:\\BambooHome\\xml-data\\build-dir\\152764417\\DHGUI-DHCDN1041-JOB1\\DHCDN.RMPrices\\Kotrak.XLInterface.RMPrices.Infrastructure\\WcfService\\DHCDNRMPriceServiceClient.cs:line 81\r\n   at Kotrak.XLInterface.RMPrices.Infrastructure.WcfService.Paging.<>c__DisplayClass2_0`2.<GetPaginated>b__0(String cursor) in E:\\BambooHome\\xml-data\\build-dir\\152764417\\DHGUI-DHCDN1041-JOB1\\DHCDN.RMPrices\\Kotrak.XLInterface.RMPrices.Infrastructure\\WcfService\\Paging.cs:line 33\r\n   at Kotrak.XLInterface.RMPrices.Infrastructure.WcfService.Paging.GetPaginated[TResult](Func`2 serviceMethod, Func`3 aggregate, TResult initResult) in E:\\BambooHome\\xml-data\\build-dir\\152764417\\DHGUI-DHCDN1041-JOB1\\DHCDN.RMPrices\\Kotrak.XLInterface.RMPrices.Infrastructure\\WcfService\\Paging.cs:line 20\r\n   at Kotrak.XLInterface.RMPrices.Infrastructure.WcfService.Paging.GetPaginated[TResult](Func`2 serviceMethod) in E:\\BambooHome\\xml-data\\build-dir\\152764417\\DHGUI-DHCDN1041-JOB1\\DHCDN.RMPrices\\Kotrak.XLInterface.RMPrices.Infrastructure\\WcfService\\Paging.cs:line 28\r\n   at Kotrak.XLInterface.RMPrices.Infrastructure.WcfService.Paging.GetPaginated[TFilter,TResult](Func`2 serviceMethod, TFilter filter) in E:\\BambooHome\\xml-data\\build-dir\\152764417\\DHGUI-DHCDN1041-JOB1\\DHCDN.RMPrices\\Kotrak.XLInterface.RMPrices.Infrastructure\\WcfService\\Paging.cs:line 33\r\n   at Kotrak.XLInterface.RMPrices.Presentation.Forms.ItemHistoricalPriceListModule.GetCalculatedHistoricalPrices(Filter filter) in E:\\BambooHome\\xml-data\\build-dir\\152764417\\DHGUI-DHCDN1041-JOB1\\DHCDN.RMPrices\\Kotrak.XLInterface.RMPrices.Presentation\\Forms\\ItemHistoricalPriceListModule.cs:line 767\r\n   at Kotrak.XLInterface.RMPrices.Presentation.Forms.ItemHistoricalPriceListModule.RefreshList() in E:\\BambooHome\\xml-data\\build-dir\\152764417\\DHGUI-DHCDN1041-JOB1\\DHCDN.RMPrices\\Kotrak.XLInterface.RMPrices.Presentation\\Forms\\ItemHistoricalPriceListModule.cs:line 411\r\n   at Kotrak.XLInterface.RMPrices.Presentation.Commands.BarItemUICommand`1.<>c__DisplayClass6_0.<.ctor>b__1(TArgument arg) in E:\\BambooHome\\xml-data\\build-dir\\152764417\\DHGUI-DHCDN1041-JOB1\\DHCDN.RMPrices\\Kotrak.XLInterface.RMPrices.Presentation\\Commands\\BarItemUICommand.cs:line 30\r\n   at Kotrak.XLInterface.RMPrices.Presentation.Commands.BarItemUICommand`1.OnExecute() in E:\\BambooHome\\xml-data\\build-dir\\152764417\\DHGUI-DHCDN1041-JOB1\\DHCDN.RMPrices\\Kotrak.XLInterface.RMPrices.Presentation\\Commands\\BarItemUICommand.cs:line 45\r\n   at Kotrak.XLInterface.RMPrices.Presentation.Commands.UserInterfaceCommandBase.Execute() in E:\\BambooHome\\xml-data\\build-dir\\152764417\\DHGUI-DHCDN1041-JOB1\\DHCDN.RMPrices\\Kotrak.XLInterface.RMPrices.Presentation\\Commands\\UserInterfaceCommandBase.cs:line 22\n\n### Response:\n[""Comment 1: [\'!image-1!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Dear Thabile,It seems to be the same case as underDGS-8940.Please check RDS server and confirm if everything is fine on server side.Best regards\'"", ""Comment 4: \'During Teams conversation with Thabile I have checked DB sahosrv07:>> time proceesin was quite high!image-2023-04-14-17-10-45-620.png|width=995,height=205!>> 134 blocking sessions!image-2023-04-14-17-12-08-110.png!>> verified sahosrv04 and sahosrv024: for me it worked on sahosrv04"", \'Comment 5: on 24 there was a timeout; for Thabile\', \'Comment 6: on 24 timeout\', ""Comment 7: on 04 worked very slow.\'"", ""Comment 8: \'Hi,Per Teams conversation"", \'Comment 9: please use sahosrv04 server as a workaround. What is more\', ""Comment 10: please let us know if there is any possibility to restart 024 and chech if it helped.Best regards\'"", ""Comment 11: \'Hello"", ""Comment 12: Plugin is working now thank you. task can be closed\'"", ""Comment 13: \'Thank you\']""]\nRelated Issues:\n[]\n\n### End'}"
59,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8973\n\n### Instruction:\nThe item is linked to the wrong base item, but this can\'t be changed.\r\nSee attached image.\r\n\r\nCould you change it for me?\r\n\r\nThanks in advance,\r\nRob.\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: \'Rob"", ""Comment 4: what base item should be used?Regards\'"", ""Comment 5: \'Hi Aleksandra"", ""Comment 6: it should be the regular 967367 instead of the 100kg variant\'"", ""Comment 7: \'ok\'"", ""Comment 8: \'Please"", \'Comment 9: verify now. In addition\', ""Comment 10: pleae remember that new recipes for this item must be generated now!image-2023-04-14-14-33-15-016.png|width=929,height=306!Regards\'"", \'Comment 11: ""It\\\'s looking great now\', \'Comment 12: thanks.I will inform the user they must create a new recipe fr the item.The ticket can be closed.""\', ""Comment 13: \'Thank you\']""]\nRelated Issues:\n[]\n\n### End'}"
60,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8972\n\n### Instruction:\nFor Andel incorrect additional technologies were created for item 087001. \r\nThis code must only be used in Andel-Mest. Not in Andel-West.\r\n\r\nPlease remove \r\nAM087001 subversion 0 \r\nAW087001 subversion 0\r\nAW087001-BB\r\nAW087001-Z25\r\n\r\nIssue is that these versions are still available in recipe list when manually creating a lot report for these items. User often selects AW recipe or AM subversion 0 recipe. This last one, results in a Lot report without RM and the Lot report does not show in Lot report overview (e.g. 0052140423005)\r\n\r\nAM087001 subversion 1 is correct. It is ok if you remove this one as well and then I will create one new additional technology for this item.\r\n\r\nAttached: \r\nDHC Additional technologies for 087001 (archived subversion 0 is not shown here)\r\nDHP recipes for 087001, AM version 0 is the one that does not have RM\n\n### Response:\n[""Comment 1: [\'!image-4!!image-5!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Hello,incorrect additional technologies have been removed. Please verify.Regards\'"", ""Comment 4: \'Hello,can we close this issue?Regards\'"", ""Comment 5: \'Additional technology indeed was removed. This ticket can be closed.The goal of this request was to clean up recipes for the plant when creating a Lot report in DHP (plant agent now often select incorrect recipe version"", \'Comment 6: e.g. Andel-West version instead of Andel-Mest version). However\', \'Comment 7: after removing /archiving of addtional technologies\', ""Comment 8: the recipes still exist. But I understand that this is not fixed with this action.\'"", ""Comment 9: \'Hi Bob,I have processed archivisation of questioned recipes:AM087001 subversion 0AW087001 subversion 0AW087001-BBAW087001-Z25in PCS once again. Please"", \'Comment 10: check. However\', ""Comment 11: starting from DGS-8666 we do not delete from db anything.Please verify.Regards\'"", ""Comment 12: \'Hi Aleksandra"", \'Comment 13: thank you. However when I create a Lot report for 08001\', \'Comment 14: line Andel-W is selected by default (there is a recipe) and after selecting line Andel-Mest\', ""Comment 15: I still can choose from recipes 0.0 and 0.1.!image!!image-1!\'"", ""Comment 16: \'!image-2023-04-20-11-29-55-025.png!!image-2023-04-20-11-30-12-105.png!!image-2023-04-20-11-30-35-118.png!\'"", ""Comment 17: \'Jeśli chodzi o te dwie receptury: AM087001 subversion 0 AW087001 subversion 0 trzy razy puszczałam skrypt na bazie PCS i guzik"", \'Comment 18: receptury nadal dostępne ...[~maciej.dobrzanski@kotrak.com]\', ""Comment 19: co mogło pójść nie tak?\'"", ""Comment 20: \'Dear Bob,Recipes are available because as I mentioned before"", \'Comment 21: we block it in PCS so that they are not used in PCS. What I can propose is tochange their status to blocked and renamed them with arch.Please\', ""Comment 22: let us know if this is fine for you.Regards\'"", ""Comment 23: \'Hi,Any feedback?Regards\'"", ""Comment 24: \'Yes"", ""Comment 25: this is fine with me. \'"", ""Comment 26: \'Dear Bob,I have archivedAM087001 subversion 0AW087001 subversion 0should I also archive:AW087001-BBAW087001-Z25the same way?Regards\'"", ""Comment 27: \'Hello Aleksandra"", ""Comment 28: yes please archive the AW087001-BB and -Z25 as well.\'"", ""Comment 29: \'AW087001-BBAW087001-Z25also archived. Please"", ""Comment 30: verify.Best regards\'"", ""Comment 31: \'Thank you. This is really helpful to prevent that the users create incorrect Lot reports.This ticket can be closed.\']""]\nRelated Issues:\n[]\n\n### End'}"
61,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8971\n\n### Instruction:\nApplicable for all plants.\r\n\r\nWe found that draft Lot reports received in Milas in some cases contains incorrect itemcode. In DHC I found that for items without repcipe, code 999999 is shown in draft Production Lot reports. And the basecode 969587 of this item is sent to Milas...\r\nThe Production Lot report contains the correct (produced) item and correct data is sent to Milas.\r\n\r\nNote that Bestmix item 999999 is used for linking ERP items without own recipe. This code 999999 and its basecode must never be used in reports and the base code in this item\r\n\r\nIssue is that draft production Lot reports are sent with incorrect item to Milas and possible Starlims.\r\n\r\nExpected: item that was produced is registered in the draft production lot report and sent to Milas and Starlims. So, use the ERP item and no lookup of Bestmix / base item.\r\n\r\nExample:\r\nAndel-Mest Lot report 0052140423005\r\nItem produced: 087001\r\nThis item does not have its own recipe and therefore it is linked to 999999\r\ndraft Lot report contains 999999. Exported to Milas 969587 (not correct)\r\nProduction Lot report contains 087001 (correct)\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: \'For your information: we already had many draft Production Lot reports with code 999999 for Helmond (009)"", ""Comment 4: Andel-West (005) and Andel-Mest (098)!image-2!\'"", \'Comment 5: \\\'{code:java}2023-04-14 09:19:22,260 [128] INFO  WcfSendRequestLogger [C:\\\\\\\\Projects\\\\\\\\evolution.dhcerpservice\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.Service\\\\\\\\Logging\\\\\\\\LoggingInspectorBehavior.cs:53] - Request:<s:Envelope xmlns:s=""http://schemas.xmlsoap.org/soap/envelope/"">  <s:Header>    <Action s:mustUnderstand=""1"" xmlns=""http://schemas.microsoft.com/ws/2005/05/addressing/none"">unit01_dhc_adapter_ws_provider_wsd_webMethods_DHC_Provider_Binder_insertProductionLotReport</Action>  </s:Header>  <s:Body xmlns:xsi=""http://www.w3.org/2001/XMLSchema-instance"" xmlns:xsd=""http://www.w3.org/2001/XMLSchema"">    <insertProductionLotReport xmlns=""http://deheus.com/unit01/DHC"">      <input xmlns="""">        <header>          <ReceivingSystem>Milas</ReceivingSystem>          <SendingSystem>DHC</SendingSystem>          <CreateDate>2023-04-14T08:35:00</CreateDate>          <CreateUser xsi:nil=""true"" />          <MessageID>1829561f-b0b0-46a0-bef7-d72ae569d507</MessageID>        </header>        <productionLotReport>          <ProductionOrderReference>0052140423005</ProductionOrderReference>          <ProducedItem>969587</ProducedItem>          <ProducedQTY>1860</ProducedQTY>          <ProducedQTYUOM>kg</ProducedQTYUOM>          <Plant>98</Plant>          <ProductionDateTime>2023-04-14T08:35:00</ProductionDateTime>          <ProductionLotTypeIndicator>9</ProductionLotTypeIndicator>        </productionLotReport>      </input>    </insertProductionLotReport>  </s:Body></s:Envelope>{code}\\\'\', ""Comment 6: \'Hello,a GDC change for the described issue was already resolved. In the DHC version 3.0.63 this change is already included.\'"", ""Comment 7: \'Ok"", ""Comment 8: that is great. Do you have the GDC number for me?\'"", ""Comment 9: \'Hello,GDC-886 this GDC exactly.\'"", ""Comment 10: \'I checked on DHC production today and I still find draft Lot reports for 999999see attachment. This draft Lot report should have reported 088521-Z25!image-3!!image-4!\'"", \'Comment 11: \\\'005221042300100522104230020092210423002Są z 21.4 piątku bez zmian:{code:java}2023-04-21 10:35:45,517 [50] INFO  WcfSendRequestLogger [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\152764417\\\\\\\\DHAPPSV3-DHCER412-JOB1\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.Service\\\\\\\\Logging\\\\\\\\LoggingInspectorBehavior.cs:54] - Request:<s:Envelope xmlns:s=""http://schemas.xmlsoap.org/soap/envelope/"">  <s:Header>    <Action s:mustUnderstand=""1"" xmlns=""http://schemas.microsoft.com/ws/2005/05/addressing/none"">unit01_dhc_adapter_ws_provider_wsd_webMethods_DHC_Provider_Binder_insertProductionLotReport</Action>  </s:Header>  <s:Body xmlns:xsi=""http://www.w3.org/2001/XMLSchema-instance"" xmlns:xsd=""http://www.w3.org/2001/XMLSchema"">    <insertProductionLotReport xmlns=""http://deheus.com/unit01/DHC"">      <input xmlns="""">        <header>          <ReceivingSystem>Milas</ReceivingSystem>          <SendingSystem>DHC</SendingSystem>          <CreateDate>2023-04-21T10:35:44.74</CreateDate>          <CreateUser xsi:nil=""true"" />          <MessageID>763d9979-40de-4531-b8bc-341c58e2bbcf</MessageID>        </header>        <productionLotReport>          <ProductionOrderReference>0092210423002</ProductionOrderReference>          <ProducedItem>969587</ProducedItem>          <ProducedQTY>100</ProducedQTY>          <ProducedQTYUOM>kg</ProducedQTYUOM>          <Plant>9</Plant>          <ProductionDateTime>2023-04-21T10:35:44.74</ProductionDateTime>          <ProductionLotTypeIndicator>9</ProductionLotTypeIndicator>        </productionLotReport>      </input>    </insertProductionLotReport>  </s:Body></s:Envelope>{code}{code:java}2023-04-21 07:32:49,838 [45] INFO  WcfSendRequestLogger [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\152764417\\\\\\\\DHAPPSV3-DHCER412-JOB1\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.Service\\\\\\\\Logging\\\\\\\\LoggingInspectorBehavior.cs:54] - Request:<s:Envelope xmlns:s=""http://schemas.xmlsoap.org/soap/envelope/"">  <s:Header>    <Action s:mustUnderstand=""1"" xmlns=""http://schemas.microsoft.com/ws/2005/05/addressing/none"">unit01_dhc_adapter_ws_provider_wsd_webMethods_DHC_Provider_Binder_insertProductionLotReport</Action>  </s:Header>  <s:Body xmlns:xsi=""http://www.w3.org/2001/XMLSchema-instance"" xmlns:xsd=""http://www.w3.org/2001/XMLSchema"">    <insertProductionLotReport xmlns=""http://deheus.com/unit01/DHC"">      <input xmlns="""">        <header>          <ReceivingSystem>Milas</ReceivingSystem>          <SendingSystem>DHC</SendingSystem>          <CreateDate>2023-04-21T06:02:00</CreateDate>          <CreateUser xsi:nil=""true"" />          <MessageID>91aa58f0-97e3-4f7f-972b-0eaede2fb702</MessageID>        </header>        <productionLotReport>          <ProductionOrderReference>0052210423001</ProductionOrderReference>          <ProducedItem>969587</ProducedItem>          <ProducedQTY>1980</ProducedQTY>          <ProducedQTYUOM>kg</ProducedQTYUOM>          <Plant>5</Plant>          <ProductionDateTime>2023-04-21T06:02:00</ProductionDateTime>          <ProductionLotTypeIndicator>9</ProductionLotTypeIndicator>        </productionLotReport>      </input>    </insertProductionLotReport>  </s:Body></s:Envelope>{code}{code:java}2023-04-21 10:35:45,517 [50] INFO  WcfSendRequestLogger [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\152764417\\\\\\\\DHAPPSV3-DHCER412-JOB1\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.Service\\\\\\\\Logging\\\\\\\\LoggingInspectorBehavior.cs:54] - Request:<s:Envelope xmlns:s=""http://schemas.xmlsoap.org/soap/envelope/"">  <s:Header>    <Action s:mustUnderstand=""1"" xmlns=""http://schemas.microsoft.com/ws/2005/05/addressing/none"">unit01_dhc_adapter_ws_provider_wsd_webMethods_DHC_Provider_Binder_insertProductionLotReport</Action>  </s:Header>  <s:Body xmlns:xsi=""http://www.w3.org/2001/XMLSchema-instance"" xmlns:xsd=""http://www.w3.org/2001/XMLSchema"">    <insertProductionLotReport xmlns=""http://deheus.com/unit01/DHC"">      <input xmlns="""">        <header>          <ReceivingSystem>Milas</ReceivingSystem>          <SendingSystem>DHC</SendingSystem>          <CreateDate>2023-04-21T10:35:44.74</CreateDate>          <CreateUser xsi:nil=""true"" />          <MessageID>763d9979-40de-4531-b8bc-341c58e2bbcf</MessageID>        </header>        <productionLotReport>          <ProductionOrderReference>0092210423002</ProductionOrderReference>          <ProducedItem>969587</ProducedItem>          <ProducedQTY>100</ProducedQTY>          <ProducedQTYUOM>kg</ProducedQTYUOM>          <Plant>9</Plant>          <ProductionDateTime>2023-04-21T10:35:44.74</ProductionDateTime>          <ProductionLotTypeIndicator>9</ProductionLotTypeIndicator>        </productionLotReport>      </input>    </insertProductionLotReport>  </s:Body></s:Envelope>{code}\\\'\', ""Comment 12: \'hej"", \'Comment 13: podali kolejne z 21.4 piątku. Mógłbyś popatrzeć? \', ""Comment 14: jest bez zmian.\\\\r\\\\rDzięki.\']""]\nRelated Issues:\n[]\n\n### End'}"
62,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8970\n\n### Instruction:\nCześć,\r\n\r\nError id 6467308  start transfer.\r\n\r\nProszę o szybkie usunięcie problemu -brak raportowania  i zaraz postój.\r\n\r\nPilne!!!!\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: \'Incorrect message has been canceled.\'"", ""Comment 3: \'Cześć ,Kolejny error id 6467379 – start transfer.\'"", ""Comment 4: \'StartTransferError 8: Production lot is already closed\'"", ""Comment 5: \'Mozliwe ze problemem jest raort produkcyjny ( z wczescniejszego bledu gdzie mimo produkcji workowanej do plr wpadly big bagi )!image!\'"", ""Comment 6: \'Kolejny errorId 6467407\'"", \'Comment 7: ""There were three PLR\\\'s already closed:230414003,230414004,230414005Messages have been canceled.""\', \'Comment 8: ""Now it\\\'s  Ok .""\', ""Comment 9: \' do zmiany statusu na ostatnia dla palety 27-6FDNG dla 915908-w25 lot 0272140423003\'"", ""Comment 10: \' !screenshot-1! \'"", ""Comment 11: \'Any news ?? \'"", ""Comment 12: \'But this barcode is a BigBag"", ""Comment 13: whether to make the change anyway? !screenshot-2! \'"", ""Comment 14: \'Please contact with business reporter\'"", ""Comment 15: \'Corrected.\'"", ""Comment 16: \'Confirmed with factory"", ""Comment 17: can we close?\'"", ""Comment 18: \'Yes\']""]\nRelated Issues:\n[]\n\n### End'}"
63,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8969\n\n### Instruction:\nIO-61/23/DKD and IO-62/23/DKD are not showing in DHP\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'!image-2023-04-14-09-04-29-819.png!\'"", \'Comment 3: ""{code:java}The \\\'TypeAs\\\' expression with an input of type \\\'System.Guid\\\' and a check of type \\\'System.Nullable`1[[System.Guid\', \'Comment 4: mscorlib\', \'Comment 5: Version=4.0.0.0\', \'Comment 6: Culture=neutral\', \'Comment 7: PublicKeyToken=b77a5c561934e089]]\\\' is not supported. Only entity types and complex types are supported in LINQ to Entities queries{code}""\', ""Comment 8: \'We need to do one more fix for DHC. It will take 15minutes,there will be a downtime at DHC.\'"", \'Comment 9: ""Ustalone na 16\', \'Comment 10: Michał Kordys będzie wgrywał\', \'Comment 11: do sprawdzenia po - ponowne przesłanie zamówień z XL:IO-61/23/DKD and IO-62/23/DKD{code:java}--update z  --set zan_stan=ZaN_Stan FROM [CDNXL_DHFU].[CDN].[ZamNag] z where ZaN_GIDNumer in(803632,803778){code}powiadomić Rey\\\'a iNosipho Basi po.""\', ""Comment 12: \'Hi,The fix has been deployed and ordersIO-61/23/DKD and IO-62/23/DKD have been resent.Please"", ""Comment 13: verify.Regards\'"", ""Comment 14: \'Hi,Can we close this task?Regards\'"", ""Comment 15: \'Yes you may\'"", ""Comment 16: \'Thank you.Regards\']""]\nRelated Issues:\n[]\n\n### End'}"
64,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8968\n\n### Instruction:\nHi\r\n\r\nPlease help to check this issue.  VT-728/4/23 can not complete and close ticket.\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,Could you please verify?!image-2023-04-13-19-13-36-840.png!Best regards\'"", ""Comment 4: \'HiPlease remote to 10.84.135.8\'"", ""Comment 5: \'we changed to new Servers!image-1!\'"", ""Comment 6: \'!image-2023-04-14-14-51-40-651.png!\'"", \'Comment 7: \\\'{code:java}2023-04-14 19:51:24 (6465440b-b56d-4b96-b0a2-39607b64c782/Plant.Stock.BusinessLogic/VNAPPDHP-PCDV/7976/20) [Error] Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware - Error during request{  ""scheme"": ""http""\', \'Comment 8:  ""host"": {    ""Value"": ""10.84.135.8:92""\', \'Comment 9:    ""HasValue"": true\', \'Comment 10:    ""Host"": ""10.84.135.8""\', \'Comment 11:    ""Port"": 92  }\', \'Comment 12:  ""path"": ""/api/RegisterBulkDispatch/getCompleteBulkDispatchValidationInfo""\', \'Comment 13:  ""queryString"": []\', \'Comment 14:  ""requestBody"": ""{\\\\\\\\""elements\\\\\\\\"":[{\\\\\\\\""sourceDocument\\\\\\\\"":{\\\\\\\\""id\\\\\\\\"":\\\\\\\\""77087023-2a75-494b-916e-febeada28666\\\\\\\\"",\\\\\\\\""no\\\\\\\\"":1,\\\\\\\\""number\\\\\\\\"":\\\\\\\\""VT-728/4/23\\\\\\\\"",\\\\\\\\""type\\\\\\\\"":100},\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""073b0b3b-f40f-442b-a646-f2ee64b26940\\\\\\\\"",\\\\\\\\""requestedQuantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":0},\\\\\\\\""stockUnits\\\\\\\\"":[{\\\\\\\\""stockUnitId\\\\\\\\"":\\\\\\\\""2254b5c5-ce2c-4bc6-939f-4e61bbbc7271\\\\\\\\"",\\\\\\\\""deliveryId\\\\\\\\"":\\\\\\\\""4c55ade3-1324-4d34-ad02-95584836cad7\\\\\\\\"",\\\\\\\\""stockUnitStatuses\\\\\\\\"":[4,2048,1048576],\\\\\\\\""quantityOnHand\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":239},\\\\\\\\""plannedReservedQuantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":0}}]}]}""}.System.ApplicationException: \\\\\\\'2052\\\\\\\' is not a valid value in Plant.Stock.BusinessLogic.Domain.StockUnits.Enumerations.LogisticStatus   at Kotrak.Common.SharedKernel.Enumeration.Parse[T,K](K value\', \'Comment 15: String description\', \'Comment 16: Func`2 predicate)   at Plant.Stock.BusinessLogic.Application.MappingProfiles.CompleteBulkDispatchValidationInfoQueryMappingProfile.<>c.<.ctor>b__0_1(CompleteBulkDispatchStockUnitValidationInfo x) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Application\\\\\\\\MappingProfiles\\\\\\\\CompleteBulkDispatchValidationInfoQueryMappingProfile.cs:line 21   at System.Linq.Enumerable.SelectListIterator`2.ToList()   at Plant.Stock.BusinessLogic.Domain.ActionData.CompleteBulkDispatchValidationDataStructure..ctor(IEnumerable`1 stockUnits\', \'Comment 17: SourceDocument sourceDocument\', \'Comment 18: AggregateId itemId\', \'Comment 19: Quantity requestedQuantity\', \'Comment 20: DocumentMissingStock missingStock\', \'Comment 21: IEnumerable`1 reservations) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Domain\\\\\\\\ActionData\\\\\\\\CompleteBulkDispatchValidationDataStructure.cs:line 17   at Plant.Stock.BusinessLogic.Application.MappingProfiles.CompleteBulkDispatchValidationInfoQueryMappingProfile.<.ctor>b__0_0(CompleteBulkDispatchElementValidationInfo s\', \'Comment 22: ResolutionContext _) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Application\\\\\\\\MappingProfiles\\\\\\\\CompleteBulkDispatchValidationInfoQueryMappingProfile.cs:line 21   at lambda_method8721(Closure \', \'Comment 23: CompleteBulkDispatchElementValidationInfo \', \'Comment 24: CompleteBulkDispatchValidationDataStructure \', \'Comment 25: ResolutionContext )   at lambda_method8722(Closure \', \'Comment 26: Object \', \'Comment 27: Object \', \'Comment 28: ResolutionContext )   at AutoMapper.Mapper.AutoMapper.IMapper.Map[TDestination](Object source)   at Plant.Stock.BusinessLogic.Application.RegisterBulkDispatch.CompleteBulkDispatchValidationInfoQueryHandler.Handle(CompleteBulkDispatchValidationInfoQuery query) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Application\\\\\\\\RegisterBulkDispatch\\\\\\\\CompleteBulkDispatchValidationInfoQueryHandler.cs:line 35   at Plant.Stock.BusinessLogic.Infrastructure.Api.Controllers.RegisterBulkDispatchController.GetCompleteBulkDispatchValidationInfo(CompleteBulkDispatchValidationInfoFilterViewModel viewModel) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Infrastructure.Api\\\\\\\\Controllers\\\\\\\\RegisterBulkDispatchController.cs:line 62   at lambda_method8714(Closure \', \'Comment 29: Object \', \'Comment 30: Object[] )   at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor.SyncActionResultExecutor.Execute(IActionResultTypeMapper mapper\', \'Comment 31: ObjectMethodExecutor executor\', \'Comment 32: Object controller\', \'Comment 33: Object[] arguments)   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeActionMethodAsync()   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next\', \'Comment 34: Scope& scope\', \'Comment 35: Object& state\', \'Comment 36: 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 37: Scope& scope\', \'Comment 38: Object& state\', \'Comment 39: 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 40: Task lastTask\', \'Comment 41: State next\', \'Comment 42: Scope scope\', \'Comment 43: Object state\', \'Comment 44: Boolean isCompleted)   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker\', \'Comment 45: Task task\', \'Comment 46: IDisposable scope)   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker\', \'Comment 47: Task task\', \'Comment 48: IDisposable scope)   at Microsoft.AspNetCore.Routing.EndpointMiddleware.<Invoke>g__AwaitRequestTask|6_0(Endpoint endpoint\', \'Comment 49: Task requestTask\', \'Comment 50: ILogger logger)   at Swashbuckle.AspNetCore.SwaggerUI.SwaggerUIMiddleware.Invoke(HttpContext httpContext)   at Swashbuckle.AspNetCore.Swagger.SwaggerMiddleware.Invoke(HttpContext httpContext\', \'Comment 51: ISwaggerProvider swaggerProvider)   at Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware.Invoke(HttpContext httpContext)2023-04-14 19:51:24 (7f6a931a-8d89-4aae-ac69-9c2d6ef00b36/Plant.Stock.BusinessLogic/VNAPPDHP-PCDV/7976/41) [Error] Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware - Error during request{  ""scheme"": ""http""\', \'Comment 52:  ""host"": {    ""Value"": ""10.84.135.8:92""\', \'Comment 53:    ""HasValue"": true\', \'Comment 54:    ""Host"": ""10.84.135.8""\', \'Comment 55:    ""Port"": 92  }\', \'Comment 56:  ""path"": ""/api/RegisterBulkDispatch/getCompleteBulkDispatchValidationInfo""\', \'Comment 57:  ""queryString"": []\', \'Comment 58:  ""requestBody"": ""{\\\\\\\\""elements\\\\\\\\"":[{\\\\\\\\""sourceDocument\\\\\\\\"":{\\\\\\\\""id\\\\\\\\"":\\\\\\\\""77087023-2a75-494b-916e-febeada28666\\\\\\\\"",\\\\\\\\""no\\\\\\\\"":2,\\\\\\\\""number\\\\\\\\"":\\\\\\\\""VT-728/4/23\\\\\\\\"",\\\\\\\\""type\\\\\\\\"":100},\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""073b0b3b-f40f-442b-a646-f2ee64b26940\\\\\\\\"",\\\\\\\\""requestedQuantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":0},\\\\\\\\""stockUnits\\\\\\\\"":[{\\\\\\\\""stockUnitId\\\\\\\\"":\\\\\\\\""2254b5c5-ce2c-4bc6-939f-4e61bbbc7271\\\\\\\\"",\\\\\\\\""deliveryId\\\\\\\\"":\\\\\\\\""4c55ade3-1324-4d34-ad02-95584836cad7\\\\\\\\"",\\\\\\\\""stockUnitStatuses\\\\\\\\"":[4,2048,1048576],\\\\\\\\""quantityOnHand\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":239},\\\\\\\\""plannedReservedQuantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":0}}]}]}""}.System.ApplicationException: \\\\\\\'2052\\\\\\\' is not a valid value in Plant.Stock.BusinessLogic.Domain.StockUnits.Enumerations.LogisticStatus   at Kotrak.Common.SharedKernel.Enumeration.Parse[T,K](K value\', \'Comment 59: String description\', \'Comment 60: Func`2 predicate)   at Plant.Stock.BusinessLogic.Application.MappingProfiles.CompleteBulkDispatchValidationInfoQueryMappingProfile.<>c.<.ctor>b__0_1(CompleteBulkDispatchStockUnitValidationInfo x) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Application\\\\\\\\MappingProfiles\\\\\\\\CompleteBulkDispatchValidationInfoQueryMappingProfile.cs:line 21   at System.Linq.Enumerable.SelectListIterator`2.ToList()   at Plant.Stock.BusinessLogic.Domain.ActionData.CompleteBulkDispatchValidationDataStructure..ctor(IEnumerable`1 stockUnits\', \'Comment 61: SourceDocument sourceDocument\', \'Comment 62: AggregateId itemId\', \'Comment 63: Quantity requestedQuantity\', \'Comment 64: DocumentMissingStock missingStock\', \'Comment 65: IEnumerable`1 reservations) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Domain\\\\\\\\ActionData\\\\\\\\CompleteBulkDispatchValidationDataStructure.cs:line 17   at Plant.Stock.BusinessLogic.Application.MappingProfiles.CompleteBulkDispatchValidationInfoQueryMappingProfile.<.ctor>b__0_0(CompleteBulkDispatchElementValidationInfo s\', \'Comment 66: ResolutionContext _) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Application\\\\\\\\MappingProfiles\\\\\\\\CompleteBulkDispatchValidationInfoQueryMappingProfile.cs:line 21   at lambda_method8721(Closure \', \'Comment 67: CompleteBulkDispatchElementValidationInfo \', \'Comment 68: CompleteBulkDispatchValidationDataStructure \', \'Comment 69: ResolutionContext )   at lambda_method8722(Closure \', \'Comment 70: Object \', \'Comment 71: Object \', \'Comment 72: ResolutionContext )   at AutoMapper.Mapper.AutoMapper.IMapper.Map[TDestination](Object source)   at Plant.Stock.BusinessLogic.Application.RegisterBulkDispatch.CompleteBulkDispatchValidationInfoQueryHandler.Handle(CompleteBulkDispatchValidationInfoQuery query) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Application\\\\\\\\RegisterBulkDispatch\\\\\\\\CompleteBulkDispatchValidationInfoQueryHandler.cs:line 35   at Plant.Stock.BusinessLogic.Infrastructure.Api.Controllers.RegisterBulkDispatchController.GetCompleteBulkDispatchValidationInfo(CompleteBulkDispatchValidationInfoFilterViewModel viewModel) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Infrastructure.Api\\\\\\\\Controllers\\\\\\\\RegisterBulkDispatchController.cs:line 62   at lambda_method8714(Closure \', \'Comment 73: Object \', \'Comment 74: Object[] )   at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor.SyncActionResultExecutor.Execute(IActionResultTypeMapper mapper\', \'Comment 75: ObjectMethodExecutor executor\', \'Comment 76: Object controller\', \'Comment 77: Object[] arguments)   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeActionMethodAsync()   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next\', \'Comment 78: Scope& scope\', \'Comment 79: Object& state\', \'Comment 80: 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 81: Scope& scope\', \'Comment 82: Object& state\', \'Comment 83: 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 84: Task lastTask\', \'Comment 85: State next\', \'Comment 86: Scope scope\', \'Comment 87: Object state\', \'Comment 88: Boolean isCompleted)   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker\', \'Comment 89: Task task\', \'Comment 90: IDisposable scope)   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker\', \'Comment 91: Task task\', \'Comment 92: IDisposable scope)   at Microsoft.AspNetCore.Routing.EndpointMiddleware.<Invoke>g__AwaitRequestTask|6_0(Endpoint endpoint\', \'Comment 93: Task requestTask\', \'Comment 94: ILogger logger)   at Swashbuckle.AspNetCore.SwaggerUI.SwaggerUIMiddleware.Invoke(HttpContext httpContext)   at Swashbuckle.AspNetCore.Swagger.SwaggerMiddleware.Invoke(HttpContext httpContext\', ""Comment 95: ISwaggerProvider swaggerProvider)   at Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware.Invoke(HttpContext httpContext){code}\'"", \'Comment 96: \\\'{code:java}023-04-14 19:51:24 (/Plant.Stock.BusinessLogic/VNAPPDHP-PCDV/7976/20) [Error] Serilog.AspNetCore.RequestLoggingMiddleware - HTTP ""POST"" ""/api/RegisterBulkDispatch/getCompleteBulkDispatchValidationInfo"" responded 500 in 10.7165 ms2023-04-14 19:51:24 (/Plant.Stock.BusinessLogic/VNAPPDHP-PCDV/7976/41) [Error] Serilog.AspNetCore.RequestLoggingMiddleware - HTTP ""POST"" ""/api/RegisterBulkDispatch/getCompleteBulkDispatchValidationInfo"" responded 500 in 6.9073 ms{code}\\\'\', \'Comment 97: \\\'{code:java}2023-04-14 23:08:09 (/Plant.Stock.BusinessLogic/VNAPPDHP-PCDV/7976/34) [Error] Serilog.AspNetCore.RequestLoggingMiddleware - HTTP ""POST"" ""/api/RegisterBulkDispatch/getCompleteBulkDispatchValidationInfo"" responded 500 in 10.1007 ms2023-04-14 23:08:09 (/Plant.Stock.BusinessLogic/VNAPPDHP-PCDV/7976/90) [Error] Serilog.AspNetCore.RequestLoggingMiddleware - HTTP ""POST"" ""/api/RegisterBulkDispatch/getCompleteBulkDispatchValidationInfo"" responded 500 in 15.3161 ms{code}{code:java}2023-04-14 23:08:09 (c6c51aae-ae3c-4c05-b7ac-93e7fb8f98c6/Plant.Stock.BusinessLogic/VNAPPDHP-PCDV/7976/90) [Error] Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware - Error during request{  ""scheme"": ""http""\', \'Comment 98:  ""host"": {    ""Value"": ""10.84.135.8:92""\', \'Comment 99:    ""HasValue"": true\', \'Comment 100:    ""Host"": ""10.84.135.8""\', \'Comment 101:    ""Port"": 92  }\', \'Comment 102:  ""path"": ""/api/RegisterBulkDispatch/getCompleteBulkDispatchValidationInfo""\', \'Comment 103:  ""queryString"": []\', \'Comment 104:  ""requestBody"": ""{\\\\\\\\""elements\\\\\\\\"":[{\\\\\\\\""sourceDocument\\\\\\\\"":{\\\\\\\\""id\\\\\\\\"":\\\\\\\\""77087023-2a75-494b-916e-febeada28666\\\\\\\\"",\\\\\\\\""no\\\\\\\\"":2,\\\\\\\\""number\\\\\\\\"":\\\\\\\\""VT-728/4/23\\\\\\\\"",\\\\\\\\""type\\\\\\\\"":100},\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""073b0b3b-f40f-442b-a646-f2ee64b26940\\\\\\\\"",\\\\\\\\""requestedQuantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":0},\\\\\\\\""stockUnits\\\\\\\\"":[{\\\\\\\\""stockUnitId\\\\\\\\"":\\\\\\\\""2254b5c5-ce2c-4bc6-939f-4e61bbbc7271\\\\\\\\"",\\\\\\\\""deliveryId\\\\\\\\"":\\\\\\\\""4c55ade3-1324-4d34-ad02-95584836cad7\\\\\\\\"",\\\\\\\\""stockUnitStatuses\\\\\\\\"":[4,2048,1048576],\\\\\\\\""quantityOnHand\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":239},\\\\\\\\""plannedReservedQuantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":0}}]}]}""}.System.ApplicationException: \\\\\\\'2052\\\\\\\' is not a valid value in Plant.Stock.BusinessLogic.Domain.StockUnits.Enumerations.LogisticStatus   at Kotrak.Common.SharedKernel.Enumeration.Parse[T,K](K value\', \'Comment 105: String description\', \'Comment 106: Func`2 predicate)   at Plant.Stock.BusinessLogic.Application.MappingProfiles.CompleteBulkDispatchValidationInfoQueryMappingProfile.<>c.<.ctor>b__0_1(CompleteBulkDispatchStockUnitValidationInfo x) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Application\\\\\\\\MappingProfiles\\\\\\\\CompleteBulkDispatchValidationInfoQueryMappingProfile.cs:line 21   at System.Linq.Enumerable.SelectListIterator`2.ToList()   at Plant.Stock.BusinessLogic.Domain.ActionData.CompleteBulkDispatchValidationDataStructure..ctor(IEnumerable`1 stockUnits\', \'Comment 107: SourceDocument sourceDocument\', \'Comment 108: AggregateId itemId\', \'Comment 109: Quantity requestedQuantity\', \'Comment 110: DocumentMissingStock missingStock\', \'Comment 111: IEnumerable`1 reservations) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Domain\\\\\\\\ActionData\\\\\\\\CompleteBulkDispatchValidationDataStructure.cs:line 17   at Plant.Stock.BusinessLogic.Application.MappingProfiles.CompleteBulkDispatchValidationInfoQueryMappingProfile.<.ctor>b__0_0(CompleteBulkDispatchElementValidationInfo s\', \'Comment 112: ResolutionContext _) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Application\\\\\\\\MappingProfiles\\\\\\\\CompleteBulkDispatchValidationInfoQueryMappingProfile.cs:line 21   at lambda_method8721(Closure \', \'Comment 113: CompleteBulkDispatchElementValidationInfo \', \'Comment 114: CompleteBulkDispatchValidationDataStructure \', \'Comment 115: ResolutionContext )   at lambda_method8722(Closure \', \'Comment 116: Object \', \'Comment 117: Object \', \'Comment 118: ResolutionContext )   at AutoMapper.Mapper.AutoMapper.IMapper.Map[TDestination](Object source)   at Plant.Stock.BusinessLogic.Application.RegisterBulkDispatch.CompleteBulkDispatchValidationInfoQueryHandler.Handle(CompleteBulkDispatchValidationInfoQuery query) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Application\\\\\\\\RegisterBulkDispatch\\\\\\\\CompleteBulkDispatchValidationInfoQueryHandler.cs:line 35   at Plant.Stock.BusinessLogic.Infrastructure.Api.Controllers.RegisterBulkDispatchController.GetCompleteBulkDispatchValidationInfo(CompleteBulkDispatchValidationInfoFilterViewModel viewModel) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Infrastructure.Api\\\\\\\\Controllers\\\\\\\\RegisterBulkDispatchController.cs:line 62   at lambda_method8714(Closure \', \'Comment 119: Object \', \'Comment 120: Object[] )   at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor.SyncActionResultExecutor.Execute(IActionResultTypeMapper mapper\', \'Comment 121: ObjectMethodExecutor executor\', \'Comment 122: Object controller\', \'Comment 123: Object[] arguments)   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeActionMethodAsync()   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next\', \'Comment 124: Scope& scope\', \'Comment 125: Object& state\', \'Comment 126: 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 127: Scope& scope\', \'Comment 128: Object& state\', \'Comment 129: 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 130: Task lastTask\', \'Comment 131: State next\', \'Comment 132: Scope scope\', \'Comment 133: Object state\', \'Comment 134: Boolean isCompleted)   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker\', \'Comment 135: Task task\', \'Comment 136: IDisposable scope)   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker\', \'Comment 137: Task task\', \'Comment 138: IDisposable scope)   at Microsoft.AspNetCore.Routing.EndpointMiddleware.<Invoke>g__AwaitRequestTask|6_0(Endpoint endpoint\', \'Comment 139: Task requestTask\', \'Comment 140: ILogger logger)   at Swashbuckle.AspNetCore.SwaggerUI.SwaggerUIMiddleware.Invoke(HttpContext httpContext)   at Swashbuckle.AspNetCore.Swagger.SwaggerMiddleware.Invoke(HttpContext httpContext\', ""Comment 141: ISwaggerProvider swaggerProvider)   at Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware.Invoke(HttpContext httpContext){code}\'"", \'Comment 142: ""Coś tu jest nie teges:!image-2023-04-14-18-36-06-348.png!{code:java}SELECT *  FROM [DHPlantStockBusinessLogicMain].[dbo].[StockUnits] where id = \\\'2254b5c5-ce2c-4bc6-939f-4e61bbbc7271\\\'  SELECT *  FROM [DHPlantStockBusinessLogicMain].[dbo].[Items] where code = \\\'FG00\\\' or id = \\\'073b0b3b-f40f-442b-a646-f2ee64b26940\\\'{code} !image-2023-04-14-18-48-31-748.png!""\', \'Comment 143: ""{code:java}/****** Script for SelectTopNRows command from SSMS  ******/SELECT *  FROM [DHPlantVCBusinessLogicMain].[dbo].[VehicleTicketBulkDispatchElements]  where ItemId = \\\'2C7C3E04-DC5C-4DCC-B685-3A02AC543AD7\\\' and id = \\\'77087023-2A75-494B-916E-FEBEADA28666\\\'  SELECT *  FROM [DHPlantVCBusinessLogicMain].[dbo].[VehicleTicketBulkDispatchElements]  where ItemId = \\\'073B0B3B-F40F-442B-A646-F2EE64B26940\\\' and id = \\\'77087023-2A75-494B-916E-FEBEADA28666\\\'  SELECT *  FROM [DHPlantVCBusinessLogicMain].[dbo].[VehicleTickets] where Document = \\\'VT-728/4/23\\\'{code}!image-2023-04-14-18-50-45-656.png!""\', \'Comment 144: ""Inna sprawa\', ""Comment 145: że żadnego z tych barcodów nie ma w WMS....!image-2023-04-14-18-53-47-621.png!{code:java}/****** Script for SelectTopNRows command from SSMS  ******/SELECT *  FROM [DHPlantWmsBusinessLogicMain].[dbo].[UnitLoads] where barcode in( \'436-S00C5Y\'"", \'Comment 146: \\\'VTBD-VC00KVT\\\',\\\'VTBD-VC00KVZ\\\'){code}""\', ""Comment 147: \'Hi,There is some inaccuracy: on VT we can see one element = item FG00*!image-2023-04-14-18-55-51-629.png|width=879,height=486!*But when I recreated your error"", ""Comment 148: I have received information about item1599C. Could you please let me know what should be onVT-728/4/23 ?Regards\'"", ""Comment 149: \'Hi First"", \'Comment 150: the user adds SO with element 1599C\', \'Comment 151: but system shows this error message when the user completes dispatching. Then\', ""Comment 152: user cancels element 1599C and adds element FG00 to try to complete VT and the system also shows this error message.!image-2!\'"", \'Comment 153: ""On clipped\\\'SO-4437/23/HPG2\\\' there is item1599C. Please cancelVT-728/4/23\', \'Comment 154: create a new one with correct item and if error reoccurs\', \'Comment 155: please inform us.""\', ""Comment 156: \'HiVT-1116/4/23 was created to replace VT-728/4/23 and still facing this issue . Please help to check.!image-3!\'"", ""Comment 157: \'Hi,I am sorry for my delay. VT-1116 is already closed. Please"", ""Comment 158: let me know if we should do something more on our side.Regards!image-2023-04-24-07-58-11-589.png!\'"", \'Comment 159: ""HelloYes\', ""Comment 160: that\'s right"", \'Comment 161: Eric Quang has solved this issue. Thanks you,""]\']\nRelated Issues:\n[]\n\n### End'}"
65,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8967\n\n### Instruction:\nHi\r\n\r\nWe have the Technology generated for:\r\n# POP5390-T-S30\r\n# SUN7835-T-S20\r\n\r\nThe technology for its base item isin the DHP, however for informed item, it\'s not.\r\nWe have DGS-8820 wih other cases.\r\nIf we resend it, they will get in DHP, however we need to understand what is happening. So I\'ll no resend until you check.\r\n\r\nCould you please help?\r\n\r\nThank you\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'[~mberbert@deheus.com]we will analyse tracing more tomorrow morning with devs. For now"", ""Comment 3: recipes are in Plant now.Regards\'"", ""Comment 4: \'Hi [~Aleksandra.Przybylek@kotrak.com]You can close this task and keep the tracing on DGS-8820Thank you very much!\'"", ""Comment 5: \'Thank you.Regards\']""]\nRelated Issues:\n[\'DGS-8820\', \'DGS-8985\']\n\n### End'}"
66,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8966\n\n### Instruction:\nPlease find enclosed review of the documents where the COGS seems to be unlogic. If we compare COGS of these products in some other weeks, it is easier to conclude that something went wrong in the calculation. What I noticed that some IRC documents were generated, and people whose names are on those documents cannot explain it. They claim that they not create it.\n\n### Response:\n[""Comment 1: [\'Zgłoszenie założone na prośbę Piotra Łuczaka w imieniu dyrektora finansowego z Serbii.\'"", ""Comment 2: \'To kogo wrzucić w reportera?\'"", ""Comment 3: \'Piotr Łuczak tel 604 494 664[~beata.kapturska@kotrak.com]Piotr Ł prosi o kontakt"", ""Comment 4: jeśli byś miała pytania.\'"", ""Comment 5: \'Na razie mam wszystkie potrzebne informacje. Myślę"", ""Comment 6: że dzisiaj w godzinach późniejszych zaloguję się do Serbii i sprawdzę te dokumenty. \'"", ""Comment 7: \'I attached excel file with additional column with JO and other documents that are reason of higher costs on SORs.[^Wrong Historic COGS_with JO documents.xlsx]\'"", ""Comment 8: \' [^Wrong Historic COGS_with JO documents.xlsx] \'"", \'Comment 9: ""We are interested in root cause of this calculation\', \'Comment 10: and we must be sure it won\\\'t happen again""\', ""Comment 11: \'If it was improper action of a user - we must instruct him/her what to avoid. If the additional documents have been generated in the different way - we must exclude such possibility. \'"", \'Comment 12: ""I found 3 reasons of incorrect COGS on sales documents:1. *value correction of IR+ document* like IRC+-4/02/23/SC for JO-326/02/23/S; IRC+3/02/23/SC for JO-248/02/23/S\', ""Comment 13: IRC+1/03/23/SC  for JO-208/03/23/S - those documents are made by user.Such documents should not be created because they have increased the cost of the product in relation to the materials used. The cost of the product is too high.2.  *the number of used materials is too large* - for example on JO-518/12/22/S (3820-B2) - used materials:  250 kg - product quantity - 100 kgThe quantity of materials in technology is correct.It looks like the quantity of product was 250kg before and then was changed (for some reasons) to 100 kg but the number of materials were left without changes.3. *the number of used bags on JO is too large* - it looks like the technology wasn\'t correct at the time when JO was generated"", \'Comment 14: The technology is correct now\', \'Comment 15: but the number of bags in JO wasn\\\'t corrected""\', ""Comment 16: \'[^Wrong Historic COGS_with_column_The_cause.xlsx]\'"", ""Comment 17: \' [^Wrong Historic COGS_with_column_The_cause.xlsx] \'"", \'Comment 18: \\\'HiI added report on the list of Job orders -> ""Cost difference between IR+ and IR-"" !screenshot-1! There are many documents where costs  of materials doesn\\\\\\\'t match with product cost.These documents can be fixed but if we fix them - the cost of sales will also change.On the list of documents there is a filter like ""Corrections""The filter shows correction documents like IRC+ !screenshot-2! We also can make report which will show IRC+ (value correction) that are created to Job Orders.Such documents should be verified and possibly removed.Please let us know if you want us to create such a reportAlso let me know if you want to correct wrong costs on documents? Best RegardsBeata\\\']\']\nRelated Issues:\n[]\n\n### End'}"
67,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8965\n\n### Instruction:\nHi\r\nVt tansfer didn\'t synchronized from Golub.\r\nHelp needed.\r\n\r\nRafał Boniecki \r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Please check VT is now in DHP.!image-2023-04-13-15-25-07-890.png!\'"", \'Comment 4: ""{code:java} select *   --update v --set Status=Status FROM [Evolution_DHCountry].[dbo].[VehicleTickets] v where-- DocumentNumber like \\\'4146/4/2023/D\\\' or  DocumentNumber like  \\\'4485/4/2023/D\\\' SELECT c.OrderElementId,s.OrderElementId,c.No --update s --set s.OrderElementId=c.OrderElementId  FROM [Evolution_DHCountry].[dbo].[VehicleTicketElements] c  join [Evolution_DHCService].[dbo].[VehicleTicketElements] s on c.id=s.Id  where c.[VehicleTicketId] in(select id  FROM [dbo].[VehicleTickets] where DocumentNumber like  \\\'4485/4/2023/D\\\')select *   FROM [Evolution_DHCService].[dbo].[VehicleTicketExportInfoes]  where EntityId=\\\'F96BD737-733F-47DA-BD29-D903E2BF74C7\\\'{code}""\', \'Comment 5: ""yep\', \'Comment 6: it is. What\\\'s happen?How to resynchronize vt transfer?""\', ""Comment 7: \'For this VT elements there was a difference between the data in DHCservice and DHCServer database in relation to orders elements.It is possible that the issue is related to the RCA DGS-8881 - it will be known if the problem will repeat when the RCA will be solved.\'"", ""Comment 8: \'ok"", \'Comment 9: thanks\', ""Comment 10: you can close it.\'"", ""Comment 11: \'Thank you\']""]\nRelated Issues:\n[\'DGS-8879\', \'DGS-8881\']\n\n### End'}"
68,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8964\n\n### Instruction:\nPlease remove/archive additional technology VE307617. Plant needs the recipe for an order for this item. Due to additional technology it is now blocked.\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Hi Bob,Technology has been archived. Please"", ""Comment 4: verify.Reards\'"", ""Comment 5: \'Thank you for the quick response. I now see that the recipe is sent to PCS. This ticket can be closed.\'"", ""Comment 6: \'Thank you\']""]\nRelated Issues:\n[]\n\n### End'}"
69,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8963\n\n### Instruction:\nDear, \r\nI need to add new period for window ""Frekvence a trvání léčby"". I need to fill ""7 -10 dnů / 7 - 10 dní"" for CZ_SK templates and ""7 - 10 dní / 7 - 10 napig"" for SK_HU templates.\r\nfor templates in annex\r\n\r\nCould you do it till tomorrow pls?\r\n\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!!image-2!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 3: \\\'New period for window ""Frekvence a trvání léčby"" has been added. Please verify and send a feedback.\\\'\', ""Comment 4: \'Hi"", ""Comment 5: it is okay. thx\']""]\nRelated Issues:\n[]\n\n### End'}"
70,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8962\n\n### Instruction:\nDears,\r\n\r\nall list of attached VT is in DHC and not in ERP.\r\n\r\nplease check and advise?\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: ""2023-04-13 11:17:42,374 [169] ERROR Evolution.DHCERPService.MessageSender.Actors.ClientServiceCallActor [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\152764417\\\\\\\\DHAPPSV3-DHCER-JOB1\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.MessageSender\\\\\\\\Actors\\\\\\\\ClientServiceCallActor.cs:86] - Message with command PurchaseOrderReceiptSave and object id a4c03943-08f2-44fe-bf8f-fdaf8183160f couldn\\\'t be processed. Exception occured:2023-04-13 11:17:42,374 [169] ERROR Evolution.DHCERPService.MessageSender.Actors.ClientServiceCallActor [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\152764417\\\\\\\\DHAPPSV3-DHCER-JOB1\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.MessageSender\\\\\\\\Actors\\\\\\\\ClientServiceCallActor.cs:87] - System.Exception: Internal server error. Problems witch getting object from database. at Evolution.DHCERPService.Service.BaseQuery`2.GetById(Guid Id) in E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\152764417\\\\\\\\DHAPPSV3-DHCER-JOB1\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.Service\\\\\\\\BaseQuery.cs:line 89 at Evolution.DHCERPService.EGWebServiceClient.Commands.PurchaseOrderReceiptSaveCommand.Execute(Guid id) in E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\152764417\\\\\\\\DHAPPSV3-DHCER-JOB1\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.EGWebServiceClient\\\\\\\\Commands\\\\\\\\PurchaseOrderReceiptSaveCommand.cs:line 42 at Evolution.DHCERPService.MessageSender.Actors.ClientServiceCallActor.CallClientService(ObjectChangedMessage message) in E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\152764417\\\\\\\\DHAPPSV3-DHCER-JOB1\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.MessageSender\\\\\\\\Actors\\\\\\\\ClientServiceCallActor.cs:line 592023-04-13 11:17:42,390 [157] ERROR Evolution.DHCERPService.Service.BaseQuery`2 [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\152764417\\\\\\\\DHAPPSV3-DHCER-JOB1\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.Service\\\\\\\\BaseQuery.cs:85] - System.Exception: Not all vehicle ticket elements are present.""\', ""Comment 4: \'!image-2023-04-13-13-59-11-862.png!\'"", ""Comment 5: \'!image-2023-04-13-14-01-24-456.png!\'"", ""Comment 6: \'We resend all vt for 1002010 "", \'Comment 7: there were problem with lacking end-dates for item nutrition levels.To other VT : 359\', \'Comment 8: 382\', ""Comment 9: are under analisys.\'"", ""Comment 10: \'dla kolejnego itema znowu nachodzi : !image-2023-04-13-15-11-58-197.png!\'"", ""Comment 11: \'vt - 382 was also resend"", ""Comment 12: there were the same problem as for previous one.\'"", \'Comment 13: ""vt 359 same towary packing!image-2023-04-13-15-42-20-426.png!2023-04-14 00:40:00,847 [40] ERROR Evolution.DHCERPService.MessageSender.Actors.ClientServiceCallActor [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\152764417\\\\\\\\DHAPPSV3-DHCER-JOB1\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.MessageSender\\\\\\\\Actors\\\\\\\\ClientServiceCallActor.cs:87] - System.Exception: Data were not found for vehicle ticket id 0a01c812-0877-4f0a-abdd-7e754122d8c3 at Evolution.DHCERPService.EGWebServiceClient.Commands.PurchaseOrderReceiptSaveCommand.Execute(Guid id) in E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\152764417\\\\\\\\DHAPPSV3-DHCER-JOB1\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.EGWebServiceClient\\\\\\\\Commands\\\\\\\\PurchaseOrderReceiptSaveCommand.cs:line 51 at Evolution.DHCERPService.MessageSender.Actors.ClientServiceCallActor.CallClientService(ObjectChangedMessage message) in E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\152764417\\\\\\\\DHAPPSV3-DHCER-JOB1\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.MessageSender\\\\\\\\Actors\\\\\\\\ClientServiceCallActor.cs:line 592023-04-14 00:40:16,742 [78] ERROR Evolution.DHCERPService.MessageSender.Actors.ClientServiceCallActor [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\152764417\\\\\\\\DHAPPSV3-DHCER-JOB1\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.MessageSender\\\\\\\\Actors\\\\\\\\ClientServiceCallActor.cs:86] - Message with command PurchaseOrderReceiptSave and object id 0a01c812-0877-4f0a-abdd-7e754122d8c3 couldn\\\'t be processed. Exception occured:2023-04-14 00:40:16,742 [78] ERROR Evolution.DHCERPService.MessageSender.Actors.ClientServiceCallActor [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\152764417\\\\\\\\DHAPPSV3-DHCER-JOB1\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.MessageSender\\\\\\\\Actors\\\\\\\\ClientServiceCallActor.cs:87] - System.Exception: Data were not found for vehicle ticket id 0a01c812-0877-4f0a-abdd-7e754122d8c3""\', ""Comment 14: \'!image-2023-04-13-16-03-29-390.png!\'"", \'Comment 15: ""po updatec na forced na 0 przeszło?update VehicleTicketForProcessings set forced=0 where VehicleTicketId=\\\'B979ED97-6D38-434C-BDF5-1E6EE6BF6F47\\\' and VehicleTicketElementId is null""\', ""Comment 16: \'please check also 359/4\'"", ""Comment 17: \'Thanks!all is in ERP. you can close this ticket.\']""]\nRelated Issues:\n[\'DGS-8788\', \'DGS-8936\']\n\n### End'}"
71,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8961\n\n### Instruction:\nProduction location Sneek reports that they have to cancel and recreate VT;s for intake on regular basis, because VT doesn\'t show up in pcs. I checked with the pcs supplier and reason is tha deliveryID is missing. example: 611/4/23\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: ""VT z 12/4 - jest accepted. {code:java}  FROM [DHPlantPCSBusinessLogicMain].[dbo].[WebApiRequestLog]  where Headers like \\\'%VT-611/4/23%\\\'  or body like \\\'%VT-611/4/23%\\\'{code}!image-2023-04-14-12-43-27-534.png!{code:java}SELECT *  FROM [DHPlantPCSBusinessLogicMain].[dbo].[VehicleTickets]  where DocumentNumber=\\\'vt-611/4/23\\\'SELECT *  FROM [DHPlantPCSBusinessLogicMain].[dbo].[ExportVehicleTickets]  order by 1 desc -- where EntityId=\\\'20520\\\'{code} !screenshot-1! ""\', ""Comment 3: \'Czy to może być ten case? Mają  już 8.5\\\\rhttps://helpdesk.kotrak.com/browse/DGS-8263\\\\rhttps://helpdesk.kotrak.com/browse/DAP-13164?\'"", \'Comment 4: \\\' !screenshot-2! {code:java}<VehicleTicketToPCS xmlns:xsi=""http://www.w3.org/2001/XMLSchema-instance"" xmlns:xsd=""http://www.w3.org/2001/XMLSchema"">  <VehicleTickets>    <VehicleTicket>      <VehicleTicketNumber>VT-611/4/23</VehicleTicketNumber>      <ASNNumber>CL000027027</ASNNumber>      <Status>1</Status>      <RealisationDate>2023-04-13T04:00:00</RealisationDate>      <ForwarderCode>HEU</ForwarderCode>      <ForwarderName>HEU</ForwarderName>      <PlantId>2</PlantId>      <VehiclePlateNumber>TRUCK</VehiclePlateNumber>      <VehicleTicketLines>        <VehicleTicketLine>          <LoadLineNumber>1</LoadLineNumber>          <ArticleCode>0642</ArticleCode>          <ArticleName>KALKSTEENTJES (CACO3</ArticleName>          <PackingForm>BLK</PackingForm>          <ItemBaseWeight>0.000000</ItemBaseWeight>          <ItemBaseWeightUnit>kg</ItemBaseWeightUnit>          <SupplierCode>L002368</SupplierCode>          <SupplierName>Cefetra Feed Service B.V.</SupplierName>          <EstimatedQuantity>25000.000000</EstimatedQuantity>          <EstimatedQuantityUnit>kg</EstimatedQuantityUnit>          <DeliveryId xsi:nil=""true"" />          <LotNumber xsi:nil=""true"" />          <CountryOfOrigin>*</CountryOfOrigin>          <Description xsi:nil=""true"" />        </VehicleTicketLine>      </VehicleTicketLines>    </VehicleTicket>  </VehicleTickets></VehicleTicketToPCS>{code}{code:java}<ConfirmationMessage xmlns:xsi=""http://www.w3.org/2001/XMLSchema-instance"">  <ListOfIds>    <Id>VT-611/4/23</Id>  </ListOfIds></ConfirmationMessage>{code}Oni dostali ten VT i go potwierdzili\\\'\', ""Comment 5: \'jakby mieli uwagi przekazać do ponownej weryfikacji do PCS provider.\'"", ""Comment 6: \'Hi [~TDankers@deheus.com],According to our investigation"", \'Comment 7: it looks like PCS did receive this VT on time (!pcsintergation!). VT-611/4/23 was sent to PCS on at 2023-04-12 at 19:05 and PCS confirmed this message on 2023-04-12 at 19:05.Please look at the response message:{code:java}<VehicleTicketToPCS xmlns:xsi=""http://www.w3.org/2001/XMLSchema-instance"" xmlns:xsd=""http://www.w3.org/2001/XMLSchema"">  <VehicleTickets>    <VehicleTicket>      <VehicleTicketNumber>VT-611/4/23</VehicleTicketNumber>      <ASNNumber>CL000027027</ASNNumber>      <Status>1</Status>      <RealisationDate>2023-04-13T04:00:00</RealisationDate>      <ForwarderCode>HEU</ForwarderCode>      <ForwarderName>HEU</ForwarderName>      <PlantId>2</PlantId>      <VehiclePlateNumber>TRUCK</VehiclePlateNumber>      <VehicleTicketLines>        <VehicleTicketLine>          <LoadLineNumber>1</LoadLineNumber>          <ArticleCode>0642</ArticleCode>          <ArticleName>KALKSTEENTJES (CACO3</ArticleName>          <PackingForm>BLK</PackingForm>          <ItemBaseWeight>0.000000</ItemBaseWeight>          <ItemBaseWeightUnit>kg</ItemBaseWeightUnit>          <SupplierCode>L002368</SupplierCode>          <SupplierName>Cefetra Feed Service B.V.</SupplierName>          <EstimatedQuantity>25000.000000</EstimatedQuantity>          <EstimatedQuantityUnit>kg</EstimatedQuantityUnit>          <DeliveryId xsi:nil=""true"" />          <LotNumber xsi:nil=""true"" />          <CountryOfOrigin>*</CountryOfOrigin>          <Description xsi:nil=""true"" />        </VehicleTicketLine>      </VehicleTicketLines>    </VehicleTicket>  </VehicleTickets></VehicleTicketToPCS>{code}And also on confirmation from pcs:{code:java}<ConfirmationMessage xmlns:xsi=""http://www.w3.org/2001/XMLSchema-instance"">  <ListOfIds>    <Id>VT-611/4/23</Id>  </ListOfIds></ConfirmationMessage>{code}Please contact the PCS supplier for further conclusionsRegards\\\'\', ""Comment 8: \'Yes it is send and received"", \'Comment 9: but as you can see in the response message\', ""Comment 10: deliveryID is missing:  DeliveryID is needed in the pcs to further process and send back intake weight!afbeelding!\'"", ""Comment 11: \'Hi [~TDankers@deheus.com],I have created a GDC-923. We will block sending VT to PCS where there will be no delivery yset\'"", ""Comment 12: \'this ticket can be closed\']""]\nRelated Issues:\n[\'DGS-8263\', \'DAP-13577\']\n\n### End'}"
72,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8960\n\n### Instruction:\nRecipe 3220.150KAU does not appear in DHP, even though it has been properly created in ERP system, linked with DHC, and there was no problem with technology generation\n\n### Response:\n[""Comment 1: [\'!1!!2!\'"", ""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: recipes are now in DHP\', ""Comment 5: please check and send a feedback. !image-2023-04-14-07-20-29-532.png!\'"", ""Comment 6: \'Can you tell me the reason? and will this problem be repeated in the future? thanks in advance\'"", ""Comment 7: \'Yes,this has been resolved in DHC 3.0.60.Isolated cases can unfortunately occur.\'"", ""Comment 8: \'thank you"", ""Comment 9: everything is ok now\'"", ""Comment 10: \'Thank you for confirmation.\']""]\nRelated Issues:\n[]\n\n### End'}"
73,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8959\n\n### Instruction:\nDears,\r\n\r\nall orders sent to DHC is not in DHP, Example (23009771, 23009772, 2300973)\r\n\r\nNote: we can\'t receive any raw materials without linking with orders.\n\n### Response:\n[""Comment 1: [\'Issue under analisys\'"", ""Comment 2: \'2023-04-12 13:50:20 (/Plant.DHC.Integration/DHP-3/8348/214) [Error] Plant.Integration.DhcService.Infrastructure.FetchDataFromDhcTask - ContaminationRulePipelineExecutor execution errorSystem.Exception: Cannot connect to server ---> System.ServiceModel.CommunicationException: No connection could be made because the target machine actively refused it ---> System.Net.Http.HttpRequestException: No connection could be made because the target machine actively refused it ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it\'"", ""Comment 3: \'Orders are in dhp now please verify!image-2023-04-13-02-18-52-282.png!\'"", ""Comment 4: \'Hello"", ""Comment 5: yes all in DHP.we have the same issue for all those VT in attachment.looks like there is an issue in DHC-ERP service.!image!\'"", \'Comment 6: \\\'Could you pleasespecify ""the same problem with vt""?Previously\', \'Comment 7: the topic was about not sending PO from DHC to DHP. From what I noticed there were problems with the service on the dhp side\', \'Comment 8: there were timeouts which disrupted its task after restarting the services on the dhp side and dhc service orders went through. VT documents\', \'Comment 9: on the other hand\', ""Comment 10: go from DHP to DHC. So this is a separate problem and should be reported with a separate ticket to this.I verified few VT from your list and there are in both system - DHC i DHP.If the problem is with DHC-> ERP integartion II restarted the service prophylactically if there still will be missing VT in ERP please create new task for this one cause this is a diffrent function.May we close this taskconcerning originally integartion dhc->dhp and orders.\'"", ""Comment 11: \'Hello,clear! i will open new ticket\']""]\nRelated Issues:\n[]\n\n### End'}"
74,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8958\n\n### Instruction:\nHi\r\n\r\nWe are trying to register the ULs from PLR 0831110423007\r\nHowever system displays an error message:\r\n{color:red}\r\n*Requested quantity for unit load exceeds available produced quantity. Unit load cannot be registered.*\r\n{color}\r\n\r\nBut we generated exactly what what produced.\r\n\r\nCould you please help?\r\n\r\nThank you\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: \'ID :7438398f-fe2d-4117-b287-72cf9b05a390\'"", ""Comment 4: \'!image-2023-04-12-21-09-01-452.png!\'"", \'Comment 5: \\\'An error occurred while saving the entity changes. See the inner exception for details. -> The INSERT statement conflicted with the FOREIGN KEY constraint ""FK_StockUnits_UnitLoads_UnitLoadId"". The conflict occurred in database ""DHPlantWmsBusinessLogicMain""\', \'Comment 6: table ""dbo.UnitLoads""\', ""Comment 7: column \\\\\'Id\\\\\'.The statement has been terminated.\'"", ""Comment 8: \'Please try now.\'"", ""Comment 9: \'[[DHP 3.0] Brak unit loadu"", ""Comment 10: na stocku jest|onenote:https://kotrak.sharepoint.com/sites/erpasysta/Shared%20Documents/Baza%20wiedzy/Baza%20Wiedzy%20-%20ERPSD/Klienci/DEHEUS/DEHEUS%20APPLICATIONS/Brazil/Baza%20wiedzy.one#%5bDHP%203.0%5d%20Brak%20unit%20loadu,%20na%20stocku%20jest&section-id=\\\\\\\\{05DF1439-683C-45FE-8260-61E2EC66DC91}&page-id=\\\\\\\\{961E2282-2E7C-47A8-B946-33764D357518}&end] ([Widok sieci Web|https://kotrak.sharepoint.com/sites/erpasysta/_layouts/OneNote.aspx?id=%2Fsites%2Ferpasysta%2FShared%20Documents%2FBaza%20wiedzy%2FBaza%20Wiedzy%20-%20ERPSD&wd=target%28Klienci%2FDEHEUS%2FDEHEUS%20APPLICATIONS%2FBrazil%2FBaza%20wiedzy.one%7C05DF1439-683C-45FE-8260-61E2EC66DC91%2F%5BDHP%203.0%5D%20Brak%20unit%20loadu%2C%20na%20stocku%20jest%7C961E2282-2E7C-47A8-B946-33764D357518%2F%29])\'"", ""Comment 11: \'HiThe message changed: look the attached screenshotThank you!image-2!\'"", ""Comment 12: \'!image-2023-04-12-22-25-18-605.png!\'"", ""Comment 13: \'po insercie kody przypiely sie do zamowienia 90/4/23!image-2023-04-12-22-32-41-961.png!\'"", ""Comment 14: \'tak wynika z selecta !image-2023-04-12-22-35-57-077.png!\'"", ""Comment 15: \'There was a bug that blocked the creation of the stock unit and unit load from the application level in the WMS module"", ""Comment 16: which in turn resulted in the first error. Stocks and UnitLoad were completed from the database side. Please verify.At this point it now looks like a problem with the status of the WO(ip) document itself .If the slopes are ok then can the level be downgraded to P2?!image-2023-04-12-22-43-20-687.png!\'"", \'Comment 17: ""Hi [~Agnieszka.Januszewska@kotrak.com]Yes we can lower to P2. We\\\'ll load the truck with these ULs.But then\', \'Comment 18: we need to execute the WO(IP). So could you please ask for someone to fix that tomorrow morning as first task?Thank you""\', ""Comment 19: \'Status for teh WO(ip) was fixed please verify.\'"", ""Comment 20: \'updatowano status na 50 ( exeuted na nagłówku i elemnta)"", \'Comment 21: na elemnatach uzupełniono też daty exeuted\', ""Comment 22: executed user na Admin - na id =b145240c-e1e8-462c-b0a3-6b48af0bc5ae)\'"", \'Comment 23: ""Hi [~Agnieszka.Januszewska@kotrak.com]I see that in the WO(IP) there are no realization\', \'Comment 24: however I can see the UL in the stock. So\', \'Comment 25: let\\\'s move as is.You can close this task.Thank you very much!""]\']\nRelated Issues:\n[]\n\n### End'}"
75,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8957\n\n### Instruction:\nSO000097321 does not appear in DHP Meppel.\r\n\r\nWhile doing some research I found that item 140402 (which is the only item in the salesorder) is not in DHP Meppel either. I tried to resend this from the recipes in DHH, but it still hasn\'t arrived.\r\n\r\nOrder is scheduled for tomorrow early in the morning, therefore this is a P1.\r\n\r\nCan you please investigate? Thanks!\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Forgot to mention that the Salesorder is visible in DHC.\'"", ""Comment 3: \'Resynced Item"", \'Comment 4: Recipe\', ""Comment 5: Production Recipe and Technology!image-2023-04-12-19-56-59-711.png!\'"", ""Comment 6: \'I see the recipe / item is there"", ""Comment 7: but the order not yet.Guess I have to be patient? :) Or should I try to resend it from Milas?\'"", ""Comment 8: \'Yes. The issue is known -the item was not in DHC service. Yes"", ""Comment 9: we need to wait a bit.Regards\'"", ""Comment 10: \'Dear Martijn,Please"", ""Comment 11: resend the order from Milas.Regards\'"", \'Comment 12: ""Done\', \'Comment 13: I see it now in DHP. I\\\'ve asked the reporter to check if everything is OK now.""\', ""Comment 14: \'Great. Waiting for your feedback then :)\'"", ""Comment 15: \'Confirmed"", ""Comment 16: everything is OK now. Thanks!\'"", ""Comment 17: \'Thank you\']""]\nRelated Issues:\n[]\n\n### End'}"
76,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8956\n\n### Instruction:\nCould you please uncheck all checkboxes called ""technical results"" in the customer cards in MAS BE?\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 3: ""[~mbovene@deheus.com],we\\\'ve updated all customers in MAS BE.Best regards,Grzegorz""]\']\nRelated Issues:\n[]\n\n### End'}"
77,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8955\n\n### Instruction:\nHello,\r\n\r\nPlease assist.\r\n\r\nAttached lot is not generating in DHC.\r\n\n\n### Response:\n[""Comment 1: [\'!image!!image-1!!image-2!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'HI,JO has been generated. IR documents should generate when all production will be registered!image-2023-04-12-19-54-09-381.png!!image-2023-04-12-19-54-27-043.png!Regards\'"", ""Comment 4: \'Hi AleksandraWhat stopped it from being generated?Regards\'"", \'Comment 5: ""Hi Rey,To be honest\', ""Comment 6: I have focused on unblocking the process / fixing the issue so what I\'ve done was only to resync Recipe"", \'Comment 7: Production Recipe and Technology and clicked generate documnets on PLR card in DHC as error message said about inactive technology. I am also pretty sure that resend technology only would also helped.Please\', \'Comment 8: let me know if we should treat it as an incident? Or wait to another example to perform some root cause analysis :)Best regards""\', ""Comment 9: \'Thanks"", ""Comment 10: you may close this ticket\'"", ""Comment 11: \'Thank you\'"", ""Comment 12: \'coś takiego się dzieje jak usuną technologię z XL.Jak technologii nie było przed wysyłką ponowną w XL.\']""]\nRelated Issues:\n[]\n\n### End'}"
78,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8954\n\n### Instruction:\nHi\r\n\r\nWe have this UL Barcode *89-W00YQ0-C202304041110494225*\r\nHowever we don\'t know why is it with this -C suffix.\r\nWe know who created it, and we know it was dispatched, but we don\'t know the source of it\'s creation: Was it created from DummyPallet in PLR? Was it splited from another UL?\r\nWe\'d like to understand what happened with this UL barcode.\r\n\r\nThank you\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Jest tylko ten długaśny:!image-2023-04-14-12-59-57-669.png!!image-2023-04-14-12-59-57-669!\'"", \'Comment 4: ""{code:java}SELECT *  FROM [DHPlantWmsBusinessLogicMain].[dbo].[UnitLoads] where barcode = \\\'89-W00YQ0-C202304041110494225\\\'  or barcode like \\\'89-W00YQ0%\\\'  SELECT *  FROM [DHPlantWmsBusinessLogicMain].[dbo].[UnitLoads] where ItemId in (--\\\'E4016894-DA25-4E4C-A554-28D858D3569B\\\',\\\'7A73A0CD-DC3A-46BF-8DBC-7155BD56262D\\\')--\\\'809594FF-5948-4561-8929-306F5CFA5810\\\')  SELECT *  FROM [DHPlantProdBusinessLogicMain].[dbo].[Items] where id = \\\'7A73A0CD-DC3A-46BF-8DBC-7155BD56262D\\\'  SELECT *  FROM [DHPlantProdBusinessLogicMain].[dbo].[Items] where  code like \\\'FCP4945-T%\\\'{code}!image-2023-04-13-19-56-19-098.png!""\', ""Comment 5: \'patrząc po unitloadzie!image-2023-04-13-19-59-10-307.png!\'"", ""Comment 6: \'do zapytania na stand up\'"", ""Comment 7: \'Hi [~Pawel.Sadowski@kotrak.com]Did you have opportunity to check this issue?I was noticed about one more case of it.Thank you\'"", ""Comment 8: \'Hej Maciek,[~maciej.dobrzanski@kotrak.com]skąd taki dziwny barcode"", \'Comment 9: tzn z czego pobrał taki ciąg znaków? Spacer kota po klawiaturze nie bierzemy pod uwagę. I nie jest to rework\', ""Comment 10: barcode jest z 3 kwietnia. Pomysły wyczerpane heh :)pytałam na DHApps :PZ góry dzięki\'"", ""Comment 11: \'Hi [~mberbert@deheus.com],Could you please provide us with second example and ask user to describe step by step how did he or she create questioned barcode (not how it should be done but what user did).We have forwarded your issue to Dev analysis.Reagards\'"", ""Comment 12: \'[~aleksandra.przybylek@kotrak.com] taki kod się tworzy jak jest anulowany\'"", ""Comment 13: \'[~mberbert@deheus.com]This suffix creates when the barcode is cancelled. C for cancelled"", \'Comment 14: then you have a date of cancellation:*C202304041110494225 -* the 4th of April\', ""Comment 15: 2023.Regards\'"", \'Comment 16: ""Hi [~Aleksandra.Przybylek@deheus.com]About ask user what step was used to create\', \'Comment 17: he doesn\\\'t remember what happened. And we need to understand what is happening. Why do we have 1.9tons of PLR and 2.4tons on WO(IP).Seems that — somehow — system is not validating the WO(IP) quantity with PLR quantity.If this barcode was cancelled how did they dispatch it?How this barcode was created?Thank you ""\', \'Comment 18: \\\'Id StoredAt AggregateType AggregateId Event EventType UserId UserName CorrelationId CreatedAt SentAtId StoredAt AggregateType AggregateId Event EventType UserId UserName CorrelationId CreatedAt SentAtCA02DFED-0251-44A9-9363-9C8C3ABB6BCE 2023-04-04 11:10:50.2010213 Plant.Stock.BusinessLogic.Domain.StockUnits.StockUnit 807a0522-5be4-4578-b434-e461789cd6a7 {""StockUnitId"":{""Id"":""807a0522-5be4-4578-b434-e461789cd6a7""},""*OldBarcode"":\\\\\\\\{""Code"":""89-W00YQ0""},""NewBarcode"":\\\\\\\\{""Code"":""89-W00YQ0-C202304041110494225""}}* Plant.Stock.BusinessLogic.DomainAbstractions.StockUnits.StockUnitBarcode*ChangedEvent* 51867B60-5E3C-4689-84E4-EE3DBBDABC08 *lqueiroz* E741EB87-FBFE-4F3D-9164-AD701C43CEDF 2023-04-04 11:10:50.1932341 2023-04-04 11:10:50.3503482WMS dla Unitload||Head |EventType|UserName|CreatedAt||Plant.WMS.BusinessLogic.DomainAbstractions.UnitLoads.DomainEvents.UnitLoadUpdatedEvent|lqueiroz|2023-04-04 11:10:49.4225918||Plant.WMS.BusinessLogic.DomainAbstractions.UnitLoads.DomainEvents.UnitLoadBarcodeChangedEvent|lqueiroz|2023-04-04 11:10:49.4225935||Plant.WMS.BusinessLogic.DomainAbstractions.UnitLoads.DomainEvents.UnitLoadCancelledEvent|lqueiroz|2023-04-04 11:10:49.4225942|ing 1||Heading 2|||Col A1|Col A2|\\\'\', ""Comment 19: \'Hello. User lqueiroz canceled this Barcode at2023-04-04 11:10.User tgrassi at 2023-04-04 10:44 released related stock for this barcode.Should we do a analysis for this case?\'"", ""Comment 20: \'Hi,Any feedback?Regards\']""]\nRelated Issues:\n[]\n\n### End'}"
79,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8953\n\n### Instruction:\nFor trip 01005748 two dispatch messages were sent from PCS. Both messages were not accepted in DHP. \r\nError message (with retry with these messages from Swagger):     ""Message"": ""An unexpected error occurred. Please contact system help desk."",\r\n\r\nCan you please check why these messages were not accepted / how it can be fixed? We need to deliver the sales packing slip to the customers.\r\n\r\n{\r\n""trips"":[{""tripId"":""01005748"",""loadingDate"":""2023-04-10T07:31:39.87"",""salesOrders"":[{""salesOrderNumber"":""SO-3677/4/23"",""salesOrderLines"":[{""salesOrderLineNumber"":""1"",""articleCode"":""114339"",""recipeId"":95784,""quantity"":18260.0,""compartments"":[{""compartmentNumber"":1,""compartmentWeight"":1100.0},{""compartmentNumber"":4,""compartmentWeight"":4100.0},{""compartmentNumber"":5,""compartmentWeight"":4080.0},{""compartmentNumber"":8,""compartmentWeight"":4120.0},{""compartmentNumber"":9,""compartmentWeight"":4860.0}]}]}]}]}\r\n\r\n{\r\n  ""trips"":[{""tripId"": ""01005748"",""loadingDate"": ""2023-04-10T07:23:06.955Z"",""salesOrders"":[{""salesOrderNumber"": ""SO-3678/4/23"",""salesOrderLines"": [\r\n{""salesOrderLineNumber"": ""1"",""articleCode"": ""115337"",""recipeId"": 95956,""quantity"": 9900,""compartments"": [{""compartmentNumber"": 2,""compartmentWeight"": 1160},{""compartmentNumber"": 3,""compartmentWeight"": 1180},{ ""compartmentNumber"": 7,""compartmentWeight"": 3880},{ ""compartmentNumber"": 6,""compartmentWeight"": 3680}]}]}]}]}\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: \\\'Same issue in Veghel for trip 01006224Message is not accepted in DHP (actually no indication if it is accepted or not) and error message:   ""Message"": ""An unexpected error occurred. Please contact system help desk."",I checked sales order/trip/itemline/recipeId... all seems to be okPlease check the issue for these tickets. We need to send the correct packing slip to the customers.{""trips"":[{""tripId"":""01006224"",""loadingDate"":""2023-04-12T12:20:34.563"",""salesOrders"":[{""salesOrderNumber"":""SO-4125/4/23"",""salesOrderLines"":[{""salesOrderLineNumber"":""1"",""articleCode"":""318235"",""recipeId"":59951,""quantity"":12024.0,""compartments"":[{""compartmentNumber"":1,""compartmentWeight"":2772.0},{""compartmentNumber"":3,""compartmentWeight"":1870.0},{""compartmentNumber"":5,""compartmentWeight"":3706.0},{""compartmentNumber"":7,""compartmentWeight"":3676.0}]}]}]}]}\\\'\', ""Comment 4: \'Same issue for a dispatch from Utrecht. In this case"", \'Comment 5: the operator manually created a VT and registered quantities on the VT. Original dispatch message from PCS was not accepted in DHP.<LoadingReport xmlns:xsi=""http://www.w3.org/2001/XMLSchema-instance""><Trips><Trip><TripId>01005662</TripId><LoadingDate>2023-04-11T09:12:25</LoadingDate><SalesOrders><SalesOrder><SalesOrderNumber>SO-3823/4/23</SalesOrderNumber><SalesOrderLines><SalesOrderLine><SalesOrderLineNumber>1</SalesOrderLineNumber><ArticleCode>505360</ArticleCode><RecipeId>67734</RecipeId><Quantity>4012</Quantity><Compartments><Compartment><CompartmentNumber>8</CompartmentNumber><CompartmentWeight>4012</CompartmentWeight></Compartment></Compartments></SalesOrderLine></SalesOrderLines></SalesOrder><SalesOrder><SalesOrderNumber>SO-3407/4/23</SalesOrderNumber><SalesOrderLines><SalesOrderLine><SalesOrderLineNumber>1</SalesOrderLineNumber><ArticleCode>505383</ArticleCode><RecipeId>67739</RecipeId><Quantity>5006</Quantity><Compartments><Compartment><CompartmentNumber>3</CompartmentNumber><CompartmentWeight>2002</CompartmentWeight></Compartment><Compartment><CompartmentNumber>5</CompartmentNumber><CompartmentWeight>3004</CompartmentWeight></Compartment></Compartments></SalesOrderLine></SalesOrderLines></SalesOrder><SalesOrder><SalesOrderNumber>SO-1811/4/23</SalesOrderNumber><SalesOrderLines><SalesOrderLine><SalesOrderLineNumber>1</SalesOrderLineNumber><ArticleCode>505360</ArticleCode><RecipeId>67734</RecipeId><Quantity>8014</Quantity><Compartments><Compartment><CompartmentNumber>2</CompartmentNumber><CompartmentWeight>2008</CompartmentWeight></Compartment><Compartment><CompartmentNumber>6</CompartmentNumber><CompartmentWeight>3000</CompartmentWeight></Compartment><Compartment><CompartmentNumber>9</CompartmentNumber><CompartmentWeight>3006</CompartmentWeight></Compartment></Compartments></SalesOrderLine></SalesOrderLines></SalesOrder></SalesOrders></Trip><Trip><TripId>01005862</TripId><LoadingDate>2023-04-11T09:12:25</LoadingDate><SalesOrders><SalesOrder><SalesOrderNumber>SO-4115/4/23</SalesOrderNumber><SalesOrderLines><SalesOrderLine><SalesOrderLineNumber>2</SalesOrderLineNumber><ArticleCode>505210</ArticleCode><RecipeId>67261</RecipeId><Quantity>3996</Quantity><Compartments><Compartment><CompartmentNumber>1</CompartmentNumber><CompartmentWeight>2056</CompartmentWeight></Compartment><Compartment><CompartmentNumber>7</CompartmentNumber><CompartmentWeight>1940</CompartmentWeight></Compartment></Compartments></SalesOrderLine><SalesOrderLine><SalesOrderLineNumber>1</SalesOrderLineNumber><ArticleCode>505075</ArticleCode><RecipeId>66429</RecipeId><Quantity>7522</Quantity><Compartments><Compartment><CompartmentNumber>4</CompartmentNumber><CompartmentWeight>3216</CompartmentWeight></Compartment><Compartment><CompartmentNumber>10</CompartmentNumber><CompartmentWeight>4306</CompartmentWeight></Compartment></Compartments></SalesOrderLine></SalesOrderLines></SalesOrder></SalesOrders></Trip></Trips></LoadingReport>\\\'\', ""Comment 6: \'For the dispatch from Utrecht"", \'Comment 7: I found and solved the issue: for one of the orders\', ""Comment 8: a different trip number was used. That trip was cancelled in DHP. I updated the tripnumber and reprocessed the dispatch message from PCS. Now it was processed correctly in DHP.For the not processed dispatches for Maasbracht and Veghel I need your help.\'"", \'Comment 9: ""Hi Bob,I\\\'m not sure what is the exact issue.In Veghelfor trip 01006224 I can see all data is in Plant. Could you please verify and let me know?!image-2023-04-12-19-11-15-422.png!!image-2023-04-12-19-10-42-735.png!""\', ""Comment 10: \'!image-2023-04-12-19-20-14-862.png!!image-2023-04-12-19-20-48-602.png!\'"", ""Comment 11: \'Hi Aleksandra"", \'Comment 12: the quanties were entered manually on the VT. This results in an incorrect SPS. For that compartment information and recipeId is required.I tried to register the quantities again using the original dispatch message from PCS. But  saw that this message was not accepted (not the first time it was sent from PCS and not when I resent it). I do not understand why the dispatch message from PCS is not accepted in DHP. I checked tripnumber\', \'Comment 13: SO number\', ""Comment 14: etc and all seems to be ok.I hope you can help me with this.That is my question.\'"", ""Comment 15: \'VT jest z 12 kwietnia"", ""Comment 16: na tą datę nie mamy errorów:!image-2023-04-13-14-32-35-010.png!!image-2023-04-13-14-32-50-599.png!\'"", ""Comment 17: \'!image-2023-04-13-16-33-42-460.png!!image-2023-04-13-16-35-22-711.png!\'"", \'Comment 18: ""*Veghel*{code:java}--SELECT *-- FROM [DHPlantVCBusinessLogicMain].[dbo].[VehicleTicketBulkDispatchElements] where ItemId = \\\'1A611975-3A76-4156-8590-97D2E811666C\\\' -- and OrderId = \\\'E7AE4918-A671-4289-B5CB-D73322A8A923\\\'SELECT * FROM [DHPlantProdBusinessLogicMain].[dbo].[Items] where code = \\\'318235\\\' --SELECT * --FROM [DHPlantProdBusinessLogicMain].[dbo].[Recipes] where itemid = \\\'1A611975-3A76-4156-8590-97D2E811666C\\\' order by CreateDate descSELECT* FROM [DHPlantVCBusinessLogicMain].[dbo].[Orders] where Document = \\\'SO-4125/4/23\\\' --SELECT* --FROM [DHPlantVCBusinessLogicMain].[dbo].[OrderElements] where ItemId = \\\'1A611975-3A76-4156-8590-97D2E811666C\\\'  --and id = \\\'E7AE4918-A671-4289-B5CB-D73322A8A923\\\'select RecipeId,* from VehicleTicketBulkDispatchElementswhere ItemId=\\\'1A611975-3A76-4156-8590-97D2E811666C\\\' and OrderId=\\\'E7AE4918-A671-4289-B5CB-D73322A8A923\\\'{code}!image-2023-04-13-18-11-54-342.png!""\', \'Comment 19: ""*Maasbracht*{code:java} SELECT *  FROM [DHPlantProdBusinessLogicMain].[dbo].[Items] where code = \\\'114339\\\'   SELECT *  FROM [DHPlantProdBusinessLogicMain].[dbo].[Items] where code = \\\'115337\\\'{code}{code:java}SELECT*  FROM [DHPlantVCBusinessLogicMain].[dbo].[Orders] where Document in (\\\'SO-3677/4/23\\\'\', ""Comment 20: \'SO-3678/4/23\'){code}{code:java} select RecipeId,* from [DHPlantVCBusinessLogicMain].[dbo].VehicleTicketBulkDispatchElementswhere ItemId in (\'368D6BA7-1AD5-45CC-AD8F-3AA40ABF67DF\'"", ""Comment 21: \'FAAB180C-A073-4440-ABAC-DB0F0E75108F\') and OrderId in (\'045816A0-33F3-4C83-8CF1-EF11CFC2BECA\'"", \'Comment 22: \\\'625BB384-4455-4938-B644-8DA8211C45F8\\\'){code}!image-2023-04-13-18-38-07-567.png!!image-2023-04-13-18-41-08-306.png!""\', \'Comment 23: ""Veghelfaktycznie brakuje vte recipe id na tym bulku w module vtogolnie takich pozycji w bazie dla Veghel jest ok 600 z czego cześć ma jakies dziwne daty i jest stara ale częścz jest z okresu do miesiącaSELECT vde.[Id]\', \'Comment 24: recipeid,FinalWeighingDate,*FROM [DHPlantVCBusinessLogicMain].[dbo].[VehicleTicketBulkDispatchElements] vde join VehicleTickets vt on vt.id=vde.id where  vt.id=\\\'0FB32AD6-C6EE-47B7-BD48-50C94657F5D4\\\' or vde.recipeid is null order by vde.FinalWeighingDate desc!image-2023-04-14-09-07-36-796.png!Podana receptura przeszła do pcs :!image-2023-04-14-09-08-38-496.png! zamówienie też pasuje!image-2023-04-14-09-09-58-759.png!""\', ""Comment 25: \'dla Veghel ustawiłam recznie recipe id bo wszystko pasuje"", \'Comment 26: wersja\', \'Comment 27: towar\', ""Comment 28: labelki sa w tej wersji zoabczymy czy pomogło\'"", ""Comment 29: \'Hello,Could you verify the Veghel VT and tripVeghel for trip 01006224I filled in teh recipe id"", ""Comment 30: that was missing on vt element.\'"", \'Comment 31: ""--update  -- [DHPlantVCBusinessLogicMain].[dbo].[VehicleTicketBulkDispatchElements] --set recipeid=\\\'D58BDABD-F3D8-437E-9DA8-EB8C65286F75\\\'-- where id=\\\'0FB32AD6-C6EE-47B7-BD48-50C94657F5D4\\\'""\', ""Comment 32: \'Hello Agnieszka"", \'Comment 33: I now see that VT is closed and that compartments are still missing...For a correct SPS printout from DHP we need a) compartment information b) reipeId. Both are in the original dispatch message that was sent by PCS but this was not accepted in DHP.My question is mainly to find the reason why the dispatch message from PCS was not accepted. As far as I could check\', ""Comment 34: the format and data of the message is ok (same for other two from Maasbracht).!image-1!\'"", ""Comment 35: \'[^SPS_admin_14042023_114227568_9c249fd0-cdf3-4623-a110-bd585519f8b2.xml]\'"", ""Comment 36: \'Yes butIn this task we have focused on clearingandunblocking the process. I add missing information from database and ask you if sps printout is now ok for vt 489/4/23 from plant Veghel.Because you feedback was unclear I generated test xml sps printout for that element ( see attachement). Please verify if that sps printout is correct.[^SPS_admin_14042023_114227568_9c249fd0-cdf3-4623-a110-bd585519f8b2.xml]I quess this is a printout you mentioned.If that works fine for that object I will fixed it for VT from Massbracht"", \'Comment 37: that you sent us before..If there is a need from your sideto investigate the reasonof the issue\', \'Comment 38: why recipeid\', \'Comment 39: it is not declared on VT elements\', \'Comment 40: we may raise RootCause Analysis (RCA)task for you.Please\', ""Comment 41: let us knowhow you wish us to proceed.\'"", ""Comment 42: \'Hi Agnieszka,The XML is processed in another application (Transform). It requires data for the compartments. This is currently missing in the XML that you generated.So"", \'Comment 43: it does not really help to manually add recipeId. The printout will still not be correct.The reason that recipeId and compartments are missing in the VT is that the dispatch message from PCS was not processed. Quantities were entered manually by the operator. The recipeId and compartments cannot be added by the user\', \'Comment 44: so the will be missing. Normally\', \'Comment 45: dispatch must be registered based on the dispatch message from PCS.To clarify my issue once more: Please check why the dispatch message from PCS is not processed in DHP. What is the reason for the error message ""An unexpected error occurred. Please contact system help desk.""\\\'\', \'Comment 46: ""Hi Bob,In that case this issue needs to be verified by dev team\', \'Comment 47: so please be informed that your task has been transferred to dev department. We\\\'ll let you know about the result as soon as possible.Regards""\', ""Comment 48: \'[~maciej.dobrzanski@kotrak.com]jeszcze pytanko"", \'Comment 49: powiązać task z https://helpdesk.kotrak.com/browse/DGS-8609i https://helpdesk.kotrak.com/browse/DGS-8610i robimy RCA?Tak naprawdę\', ""Comment 50: zgłaszają dosyć sporo tych problemów z packingslips... :/\'"", ""Comment 51: \'[~aleksandra.przybylek@kotrak.com] nie. Rozmawiałem w środę w tym temacie z Bobem. Pewnie bedzie potrzebne GDC\'"", ""Comment 52: \'ok :)\'"", ""Comment 53: \'Hi Aleksandra"", \'Comment 54: another example from Utrecht: <LoadingReport xmlns:xsi=""http://www.w3.org/2001/XMLSchema-instance""><Trips><Trip><TripId>01007890</TripId><LoadingDate>2023-04-14T09:31:39</LoadingDate><SalesOrders><SalesOrder><SalesOrderNumber>SO-6370/4/23</SalesOrderNumber><SalesOrderLines><SalesOrderLine><SalesOrderLineNumber>1</SalesOrderLineNumber><ArticleCode>505075</ArticleCode><RecipeId>68731</RecipeId><Quantity>7964</Quantity><Compartments><Compartment><CompartmentNumber>1</CompartmentNumber><CompartmentWeight>2292</CompartmentWeight></Compartment><Compartment><CompartmentNumber>2</CompartmentNumber><CompartmentWeight>2306</CompartmentWeight></Compartment><Compartment><CompartmentNumber>8</CompartmentNumber><CompartmentWeight>3366</CompartmentWeight></Compartment></Compartments></SalesOrderLine></SalesOrderLines></SalesOrder><SalesOrder><SalesOrderNumber>SO-6373/4/23</SalesOrderNumber><SalesOrderLines><SalesOrderLine><SalesOrderLineNumber>1</SalesOrderLineNumber><ArticleCode>506365</ArticleCode><RecipeId>68080</RecipeId><Quantity>5556</Quantity><Compartments><Compartment><CompartmentNumber>4</CompartmentNumber><CompartmentWeight>3068</CompartmentWeight></Compartment><Compartment><CompartmentNumber>6</CompartmentNumber><CompartmentWeight>2488</CompartmentWeight></Compartment></Compartments></SalesOrderLine></SalesOrderLines></SalesOrder></SalesOrders></Trip></Trips></LoadingReport>\\\\tThe error message (after retry in Swagger):500 UndocumentedError: Internal Server ErrorResponse bodyDownload[  {    ""Message"": ""An unexpected error occurred. Please contact system help desk.""\', \'Comment 55:    ""Code"": null  }]Note: for code 500 errors\', ""Comment 56: I think another ticket was already created.\'"", ""Comment 57: \'Hi [~BKennedy@deheus.com],For this case"", ""Comment 58: we have more than one shipping notice. One ASN is canceled and the other is in progress that is why the error appears. !doubledasns! There is a GDC-901 raised that is about to solve this issue: !901! The requirement marked in yellow will solve this issue since the PCS NL module will skip canceled trips.Regards\'"", \'Comment 59: \\\'Hi Maciej,Thank you for the response.I was not aware that the issue is cancelled trips (with same trip number). I think due to the approach in DHC that an update of an ASN results in a cancellation and a ""new"" ASN with the same trip number\', \'Comment 60: in DHP we have a lot of cases where we have multiple ASN with the same trip number.Priority of the GDC-901 I think has to be checked (I saw version 3.8...). We must be able to send a correct packing slip to the customer. For this we need compartment info and recipeId (it is not yet possible to enter this manually in the VT).If we have the issue now\', \'Comment 61: as a workaround\', ""Comment 62: it would help to update the trip number of the cancelled trip e.g. add a - or put it to 0... correct?\'"", ""Comment 63: \'Hi [~BKennedy@deheus.com],Yes"", \'Comment 64: I do really understand that is a big issue that is why both I and Theo have decided to implement the ""yellow"" point as a hotfix to the DHP R8.5. The rest of the scope will be planned for the later version.In my opinion\', \'Comment 65: we should be ready somewhere in the middle of next week\', ""Comment 66: then we can plan the upgrades of only PCS.NL service.I hope that is good news for you\'"", ""Comment 67: \'Ok"", ""Comment 68: thank you. Indeed this is good news!This ticket can be closed.\'"", ""Comment 69: \'Thank you.Regards\']""]\nRelated Issues:\n[]\n\n### End'}"
80,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8952\n\n### Instruction:\nHi, Task form Paulina\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'The task was addressed to the producer of the system OPT/993023\'"", \'Comment 4: \\\'Producer\\\\\\\'s response:""{color:#2e2e2e}Po aktualizacji zawsze usuwana jest data wyrejestrowania - {color}jest to standardowe działanie programu. Najczęściej aktualizacja po wyrejestrowaniu dotyczy ponownego zatrudnienia dlatego data wyrejestrowania jest automatycznie usuwana.""\\\'\', ""Comment 5: \'!image-1!\'"", ""Comment 6: \'Pani Paulino,Jeśli mają Panie taki przypadek że po zwolnieniu pracownika i wyrejestrowaniu go z ZUS robią Panie na nim aktualizację (dodają kolejny zapis historyczny np. zmieniający wydział) to trzeba pamiętać iż traci się informacja o wyrejestrowaniu z ZUS i dane te należy ponownie uzupełnić w ramach tego zapisu historycznego. Producent nie traktuje tego jako błąd.\'"", ""Comment 7: \'Could you please confirm if we can close this task?Regards\'"", \'Comment 8: ""I\\\'m waiting for user response""\', ""Comment 9: \'Thank you for the information\'"", ""Comment 10: \'Task to close"", ""Comment 11: thanks.\']""]\nRelated Issues:\n[]\n\n### End'}"
81,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8951\n\n### Instruction:\n I tried to Move opening Balance for 2023 from 2022 Ending and closing balance, but not working properly it will take 2022 Opening Balance as 2023 Opening balance. Can you help us to be resolved.\r\n\r\n\r\n Thanks.\r\nGetish Lemma\r\nAlema Koudijs Feed Plc\r\nFinance Manager\r\n\r\n\r\n \r\n\r\n\n\n### Response:\n[""Comment 1: [\'!1!!2!!3!!4!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Dear Sir"", \'Comment 4:  Ok thank you and much appreciated if you can help us. Thanks.   {color:#1F3864}With best Regards,{color} {color:#1F3864}{color} {color:#1F3864}Getish Lemma\', \'Comment 5: Finance Manager{color} {color:#1F3864}{color} {color:#1F3864}Alema Koudijs Feed PLC{color} {color:#1F3864}(+251) 912 144 728{color}{color:#2E74B5}{color} !image001!{color:#2E74B5}{color}         *From:* De Heus Global Service Desk <jira@kotrak.com>   *Sent:* Wednesday\', \'Comment 6: April 12\', ""Comment 7: 2023 2:32 PM  *To:* Getish Lemma <Getish@alemakoudijs.com>  *Subject:* DGS-8951 ERP Opening Balance Move to 2023   \'"", ""Comment 8: \'Dear Sir"", \'Comment 9:  Ok thank you and much appreciated if you can help us. Thanks.   {color:#1F3864}With best Regards,{color} {color:#1F3864}{color} {color:#1F3864}Getish Lemma\', \'Comment 10: Finance Manager{color} {color:#1F3864}{color} {color:#1F3864}Alema Koudijs Feed PLC{color} {color:#1F3864}(+251) 912 144 728{color}{color:#2E74B5}{color} !image001!{color:#2E74B5}{color}      *From:* Paweł Sadowski (Jira) <jira@kotrak.com>   *Sent:* Wednesday\', \'Comment 11: April 12\', ""Comment 12: 2023 2:34 PM  *To:* Getish Lemma <Getish@alemakoudijs.com>  *Subject:* DGS-8951 ERP Opening Balance Move to 2023   \'"", ""Comment 13: \'Hi1. change period to 2023 (1.png)2. Tools -> Transfer of opening balance -> check: all accounts"", ""Comment 14: Status : Accepted - > then click Lightning icon The system will only transfer the balances of those accounts that have a balance in 2022 and that have not already been transferredIt will transfer closing balance from 2022 as opening balance in 2023The opening balance can be transferred many times in this way - the system will always transfer only differences - creating an OB correction document.If you need-  the opening balance can be deleted very easily from the list of Menu Accounting -> Opening balancesYou can just change status of opening balance - Accepted to Buffer and then just delete it.\'"", ""Comment 15: \'Dear Sir"", \'Comment 16:  I have tried to do like below\', \'Comment 17: Still not resolved it is taking opening Balance of 2022 for 2023. See the attached Excel file.  Regards\', ""Comment 18: Getish[^Alema Koudijs Feed Plc Opping Balance moved for 2023 but it is openning balance of 2022.xlsx] _(20 kB)_\'"", ""Comment 19: \'I transferred opening balance. Please"", ""Comment 20: checkI had to change configuration  !screenshot-1! \'"", ""Comment 21: \'Dear Sir"", \'Comment 22:  Thanks a lot for helping me\', \'Comment 23: I have got a difference for below account which is not found and I added to the chart of account and also the balances: and for Retained earning account from Net income is not moving for total Amount of ETB 217,190,338.60 I have also added the Balance for account number 30-31000 (Retained Earning).   |{color:black} Number{color} |{color:black} Type{color} |{color:black} Name{color} |{color:black} Debit balance{color} |{color:black} Credit Balance{color} |{color:black} Credit and Debit Balance{color} | |{color:black} 11-11200-03--304{color} |{color:black} R{color} |{color:black} KEBEDE ZEWDE{color} |{color:black}  500.00{color} |{color:black} -{color} |{color:black} 500.00{color} | |{color:black} 11-11200-03-390{color} |{color:black} R{color} |{color:black} Temesgen Niguse{color} |{color:black}  3,250.00{color} |{color:black} -{color} |{color:black} 3,250.00{color} | |{color:black} 20-29401{color} |{color:black} R{color} |{color:black} Dividend Tax Payable{color} |{color:black}  1,422.00{color} |{color:black} - {color} |{color:black} 1,422.00{color} | | | | | | | | |{color:black} 30-31000{color} |{color:black} AP{color} |{color:black} Retained earnings{color} |{color:black} {color} |{color:black}  217,190,338.60{color} |{color:black} (217,190,338.60){color} |   Now the problem seems resolved. Thanks a lot.  Regards\', ""Comment 24: Getish!image001-1!\'"", ""Comment 25: \'Dear Getish,{color:#000000}The system didn\\\\\'t transfer the balance of those accounts:11-11200-03–304"", \'Comment 26: 11-11200-03-390\', \'Comment 27: 20-29401{color}{color:#000000}because they are created in 2023 by hand\', \'Comment 28: not by transferring chart of accounts from 2022\', \'Comment 29: so those account didnt have connection with account in 2022.I rebuilt this connection by filling the field ""Account in the next period"".!image-2023-04-18-15-42-03-221.png!Now \', ""Comment 30: everything is ok for me.{color}Could you please confirm if we can close this task?Regards,{color:#000000}Beata{color}\'"", ""Comment 31: \'Dear Beata Kapturska"", \'Comment 32:  Thanks for your effort to help me now it is fine\', \'Comment 33: and good. Thank you.  Regards\', ""Comment 34: Getish!image001-2!\']""]\nRelated Issues:\n[]\n\n### End'}"
82,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8950\n\n### Instruction:\nCould you change the customer numbers on these SR\'s to 100290:\r\n* SR/6406\r\n* SR/6407\r\n* SR/6409\r\n* SR/6412\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 [~mbovene@deheus.com],we are investingating this issue and which customer are you would to change on these SR\\\'s?If it will be Farmer (Farmer code\', \'Comment 3: Farmer name)\', \'Comment 4: which Round do we need to update?Best regards,Grzegorz""\', ""Comment 5: \'We can close the task\']""]\nRelated Issues:\n[]\n\n### End'}"
83,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8949\n\n### Instruction:\nHi\r\n\r\nThe factory reported that Production Order Printout for PRO-657/3/23 (FCP5290-T-S24) version 1.0 didn\'t list all elements.\r\nLooking to the PrO and PLR, all items are there, however printout is not displaying it.\r\nI found the problem: the scale number on DHP for this recipe is NULL.\r\nHowever on DHC we have the right scale number.\r\n\r\nWhen we execute the following query, we find 32 registers with ScaleNumber = NULL.\r\n\r\n{noformat}\r\nSELECT * FROM DHPlantProdBusinessLogicMain.dbo.RecipeElements re WHERE ScaleNumber IS NULL\r\n{noformat}\r\n\r\nCould you please fix that?\r\n\r\nThank you very much\n\n### Response:\n[""Comment 1: [\'Ostatni komentarz toHi[~Agnieszka.Januszewska@kotrak.com]We now have more 3 recipes with elements with ScaleNumber = NULL:||Item||Version||Subversion|||FCP5271-T-S12|8|2||GLN2217-S25|59|0||SUN7500-S15|14|1|And yes"", \'Comment 2: please\', \'Comment 3: raise a RCACzy te 3 przypadki updatowa\', ""Comment 4: czy zostawić wam do analizy.\'"", ""Comment 5: \'It will be necessary to log the exact data sent from the DHC to the DHP. We can incorporate them however we would ask for an exact date. We would ask for monitoring of free disk space during this period. Such logging would last about a week"", ""Comment 6: we would ask then and sending a new example\'"", ""Comment 7: \'Hi [~Agnieszka.Januszewska@kotrak.com]You have access to our servers"", ""Comment 8: feel free to get these logs.We are monitoring free disk space since last month and we are fine until know.Thank you\'"", ""Comment 9: \'[~przemyslaw.przybyszewski@kotrak.com]mamy zeilone światło\']""]\nRelated Issues:\n[\'DGS-8807\']\n\n### End'}"
84,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8948\n\n### Instruction:\nI would like to know if it is possible to block manual confirmations where documents are to be generated automatically\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 please provide more details: * what kind of documents ( SOR"", \'Comment 3: POR\', \'Comment 4: IR+\', ""Comment 5: JO?) * the blocking should be for all users? * What do you mean bygenerated automaticallyO maybe you have in mind to block generating sor/por and from orders?\'"", ""Comment 6: \'yes i want to block manual generation of SOR and POR from warehouses with DHP\'"", ""Comment 7: \'problem z logowaniem do ich erp xl!image-2023-04-17-13-35-42-635.png!\'"", ""Comment 8: \'!image-2023-04-17-13-43-29-047.png!\'"", ""Comment 9: \'if ERPINT is supposed to generate the document"", \'Comment 10: i dont want any user to be able to do manual execution of SOR\', \'Comment 11: POR\', ""Comment 12: IR and JO\'"", \'Comment 13: ""Could you please provide credentials for test envirovment - so I can test a solution?I reccomend add-inn \\\'s or bans.If that should be bans please provide a list of users\', \'Comment 14: if for bans provide a centers.""\', ""Comment 15: \'okay\'"", ""Comment 16: \'i dont think we have license for the test environment"", ""Comment 17: we moved all to production environment\'"", ""Comment 18: \'for the list of users that needs to be blocked from creating manual documents when ERPINT should do that are;Gilbert Laweh ZogblahChristian GodsonHarriet DabiRita AppiahEdem Zode\'"", ""Comment 19: \'any update for this?\'"", ""Comment 20: \'Are these users to be blocked from adding SOR Por"", \'Comment 21: eor and pori \', \'Comment 22: IR+\', ""Comment 23: Ir- documents completely?Or only for designated warehouses ?\'"", ""Comment 24: \'For just johnson and mag\'"", ""Comment 25: \'Do users ( you did listed) need to edit SO"", \'Comment 26: PO\', \'Comment 27: IO (except creating sor etc)?do they creating new document from order by using right-click ?There are 2 options: * I may created a filter that will hide all the orders that are for warehouses specified by you and in status confirmed and in progress\', \'Comment 28: it is kind of filter\', ""Comment 29: that unable to change it * We may create an add-inbut for that we need more tests\'"", ""Comment 30: \'Yes they need to edit SO"", ""Comment 31: PO and IO and i will prefer they are unable to create SOR or POR or WMR for MAG and JOHNSON by right clicking on the order. I dont knownif the filter will be very effective \'"", ""Comment 32: \'Could please set the test enviroment for erp xl"", \'Comment 33: so I can prepare solution and test it ?when the order are not visisble ( in specified ststaus and so one\', ""Comment 34: there an unreachable to use righcklick on order)\'"", ""Comment 35: \'in order for us to use the test environment we need to request an upgrade first\'"", ""Comment 36: \'we have to upgrade the key manager first\']""]\nRelated Issues:\n[]\n\n### End'}"
85,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8947\n\n### Instruction:\nRecipe version 46 of product 967118 for plant 4 is not exported from DHC to MILAS.  I don\'t see an entry in the recipemappings table as well.\r\n\r\nCan you check why it is not send and fix it?\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Hello,\\\\r\\\\rWe are investigating your issue. We will inform you about the solution as soon as possible.\\\\r\\\\rRegards\\\\r\\\\r\'"", \'Comment 3: ""recipeid=\\\'31901BFF-0161-4553-8E81-156D1E87722F\\\'""\', ""Comment 4: \'Please could you ask verify Milas to verify again.\'"", ""Comment 5: \'Is the recipe still missing or may we close the task?\']""]\nRelated Issues:\n[]\n\n### End'}"
86,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8946\n\n### Instruction:\nWhen we try to open the Comarch ERP program, an error comes, and it cannot be opened. An error message window attached with this request. The program version is Comarch ERP XL.\r\n\n\n### Response:\n[""Comment 1: [\'!Screenshot 2023-04-12 105101!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Issue is already analysis in DGS-8945.\'"", ""Comment 4: \'Issue resolved in DGS-8945.\']""]\nRelated Issues:\n[\'DGS-8945\']\n\n### End'}"
87,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8945\n\n### Instruction:\nDear help Desk ! \r\nwe are having this problem this week when users try login ; i tried sometime to clear the Temp files and sign out and restart the Server ; but what is the permanent solution you suggest to solve this ; \r\nThanks always  \n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Thanks Very Much !\'"", ""Comment 3: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 4: \'Thanks Very much !  Regards\'"", ""Comment 5: \'Hello"", ""Comment 6: I changed settings for public shortcut to run as administrator!screenshot-1! Please check if the problem still exists\'"", ""Comment 7: \'Dear Brother  Yes I see the difference in the login to CDNXL as Admin but I couldn`t login still ; same error notification are displaying ???!image001!\'"", ""Comment 8: \'The reasons for this may be vary.Please provide additional information:Please check if the problem is also on another server - ETAPP03.Is the problem opening every module?\'"", ""Comment 9: \'Hello Dear  We never experienced this problem on other Application except ETTS02 (ERP CDNXL).  ETAPP03 is fine and no problem login ;  Only this ETTS02 ERP CDNXL is rejecting the login ;  Last Monday problem happened and used the Run command and %Temp% and deleted the Temp folder ; signed out and worked Great ; but today this problem was happened n couldn`t fix ? hoping you have more expirence with the Applications and problems of this kinds ; For AKF Ethiopia it is our first experience  Regards \'"", ""Comment 10: \'Hey Dear  Status of my Desktop Short cut ; Admin User Name (Tgemechis ) ; hope it might be helpful .  Thanks\'"", \'Comment 11: ""!image001!     *From:* Gemechis Terefe   *Sent:* Wednesday\', \'Comment 12: April 12\', ""Comment 13: 2023 10:25  *To:* \'dgs@help.kotrak.com\' <dgs@help.kotrak.com>  *Subject:* RE: DGS-8945 ERP CDNXL Remotely login problems    Hey Dear  Status of my Desktop Short cut ; Admin User Name (Tgemechis ) ; hope it might be helpful .  Thanks     *From:* Piotr Gaczorek (Jira) <[jira@kotrak.com|mailto:jira@kotrak.com]>   *Sent:* Wednesday"", \'Comment 14: April 12\', \'Comment 15: 2023 09:48  *To:* Gemechis Terefe <[gemechis@alemakoudijs.com|mailto:gemechis@alemakoudijs.com]>  *Subject:* DGS-8945 ERP CDNXL Remotely login problems   !image001-1!""\', ""Comment 16: \'We will verify the differences between the servers"", ""Comment 17: but if you can work on the server can we reduce the priority to p2?Does the error occur only when trying to open a module?What hours users work on the problematic server?\'"", ""Comment 18: \'Hello Dear ; Additional information ?  Some users are login remotely after a long Wait . but I and other users still couldn`t !  I can login using the main server ; but Remote login problems are still happening ; All users can`t connect to the server at the same time . so"", ""Comment 19: operation is affected in our company  We all were supposed to do work Today from 07:20 till 17:00 pm ; but still I and some other users couldn`t login !  Yes The ERROR happens when trying open the Module using the desktop short cut !\'"", ""Comment 20: \'We will repair XL but I would like to ask you to log out all operators from XL - or specify what time will be appropriate.\'"", ""Comment 21: \'Hey Dear  We Will stop Working on CDNXL and related system after 16:00 (4pm) Netherlands Time / 17:00 (5pm) Ethiopian time .  Every one will log out and you can repair XL  Thanks very much !\'"", ""Comment 22: \'Thank you for information"", ""Comment 23: we will start at this time.\'"", ""Comment 24: \'You are Welcome to start anytime from now on even  ; Now all users are forced to Log out . no user can`t access the module any more for the same kind of Error .  \'"", ""Comment 25: \'Hi,We will push repairing at 8 p.m. Netherlands time.Regards\'"", ""Comment 26: \'Ok Dear Good ; Ask if anything we could help is needed . we ll be online to see your feed back . All users were forced to log out already. Thanks Again !\'"", ""Comment 27: \'Hello"", \'Comment 28: XL repair did not solve the problem\', ""Comment 29: we are consulting the issue with the XL app producer.Unfortunately - I will let you know as soon as I know something new.\'"", ""Comment 30: \'Hey May be XL repair worked ! including me ; all users are logged in . CDNXL is working great Again ;  just wanted to see the total progress and report that to ya sir. i appreciate the immediate response ya guys give us quick ! Thanks Again \'"", ""Comment 31: \'Thank you for information"", ""Comment 32: so please check and let me know.\'"", ""Comment 33: \'Hi i have some updates on the ERP module ! Users logged in Early in the morning are still working fine ! But users exited module and tried to login back had the same error like yesterday . including Me ; the picture is the remote login trail fail i received 5min ago . As it is very critical for us ; Sales and finance users are all told not to log out or ideal n end the session till customers are gone !So this problem is not fully resolved ; Last Monday we had unexpected shut down to the main server . (power Failure) Since this problem came an issue ! Tomorrow all day long there is no work here AKF Ethiopia ; no users will log in to the module. S you can have enough time to investigate What sup if possible ! Thanks always    !image-1!\'"", ""Comment 34: \'XL/993102\'"", \'Comment 35: ""I\\\'m still waiting for the manufacturer\\\'s information\', \'Comment 36: can users work on another server?""\', ""Comment 37: \'hithe ERP module was / is created on this Server ETTS02  . (This same server with error ) users  only use other servers for other modules . Here "", ""Comment 38: Sales gives service for customer n Finance-transaction both on ERP module . Tonight after 16 pm NL time all users will log out till 15th Saturday morning 7am NL. so let me know your updates !  \'"", ""Comment 39: \'Hi 👋Wanted to inform ya that"", ""Comment 40: tomorrow Friday 14 is holiday here in ETH. So no one will be around the factory from 7:00 am - 10 pm (NL time). We will shut down the main server also. Because electricians will shut down the power Generator n leave. But if you have new updates from t manufacturer n wants to login ? We will try our best to make it happen 🙏 Just let us know here yr plans beforehand.Less ya do schedule t time out of the mentioned time intervals.Regards \'"", ""Comment 41: \'Hi,No worries. I think it will take a day or two until we receive feedback from producer as the issue seems to be more complicated.We will inform you as soon as we receive some feedback.Best regards\'"", ""Comment 42: \'Well that is great. Thanks 👍\'"", ""Comment 43: \'hello dears are there any updates ? this issue became very critical ! Today Monday Apri-17  ; No user can log in to the ERP Module and both Sales and Finance Department already stopped Working ; so what is the immediate solution you advise ? our working environment is really affected ;   \'"", ""Comment 44: \'Hi,attempts were made today to repair the application after turning on the server but we are currently still working on solving the problem.Does the problem currently affect all operators?"", ""Comment 45: because I see that they are logged in to XL.We can repair the application again as a temporary solution but then you cannot work in XL on this server.Break about 15 minutes.\'"", ""Comment 46: \'Hi please "", ""Comment 47: Now every one stopped working ; some tried to login this morning but the session ended and i can`t cut users ; all Users and operators are affected ; No one is working ; only sales are trying server the customers by hand written Receipts manually ; Repair and do you miracles ; Becouse Finace is just sitting and weighbridge row material operators also just sitting  \'"", ""Comment 48: \'please repair it if you can now ; because every one is told not to try work on the XL \'"", ""Comment 49: \'just let me know when you guys are finished ? we will try login ASAP and change manual Documents to  CDNXL Regards \'"", ""Comment 50: \'Please check again"", ""Comment 51: can I get access the server WIN-27LQHK3KIPV?What license key is used for XL? !screenshot-2! \'"", ""Comment 52: \'Use My Credential !User Name ( Alemakoudijs\\\\\\\\Tgemechis)Password (Jesus@2021) use this account ; so i will update it later !  \'"", \'Comment 53: ""You don\\\'t have access to that server either.""\', ""Comment 54: \'User: Administrator Password : Summer2019! ----\'"", ""Comment 55: \'Hey dearUse this to accept WIN-27LQHK3KIPV User name (Administrator)Password (Akf@main2023!) Regards \'"", ""Comment 56: \'Please verify application should working correct now,the problem was incorrect data on the XL side for translations.\'"", ""Comment 57: \'[[ERP XL] [deheus]Nie można się zalogować "", ""Comment 58: informacje o braku licencji .|onenote:https://kotrak.sharepoint.com/sites/erpasysta/Shared%20Documents/Baza%20wiedzy/Baza%20Wiedzy%20-%20ERPSD/Baza%20wiedzy/XL.one#%5bERP%20XL%5d%20%5bdeheus%5dNie%20mo%C5%BCna%20si%C4%99%20zalogowa%C4%87%20&section-id=\\\\\\\\{FACAA0DC-563C-4105-A8C0-CDBAAB485E6B}&page-id=\\\\\\\\{3D9A0481-8941-4C49-9EDB-69C2A9CC5AAA}&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%28Baza%20wiedzy%2FXL.one%7CFACAA0DC-563C-4105-A8C0-CDBAAB485E6B%2F%5BERP%20XL%5D%20%5Bdeheus%5DNie%20mo%C5%BCna%20si%C4%99%20zalogowa%C4%87%20%7C3D9A0481-8941-4C49-9EDB-69C2A9CC5AAA%2F%29])\'"", ""Comment 59: \'Hey Dear The Application is working great ! checked it myself and Operators from sales and finance ; Great !new things we noticed was just a language changes in some area from English to Polish ; For example ; finance Department noticed this changes 1. Reference for inventory IR+ IR- changed to PW - and RW- 2. Purchase Documents invoice PI - changed to FZ- and POR to PZ-3. Sales invoice SI (Sales invoice) changed to FS and  SOR to WZ 4. Last Sales SOR print out customer name "", ""Comment 60: issued by . Date of Dispatch .. all changed to Polish from English  ; see attached Picture Thanks again !image-2!!image-3!\'"", ""Comment 61: \'Hello,Happy to see if the erp works fine"", \'Comment 62: please try to after log on use that option and verify if that works fine :Log to erp xl\', \'Comment 63: choose modul you need\', ""Comment 64: then use system - change languge and just confirm your settings . Then log out and log on and see if that helps.If not we will look at it but ,kindly approve lowering priority of this task to P2 as P1 issues are only those with a critical or a blocking impact on business processes . This seems not to be the case in this issue so we suggest decreasing the issue priority.Regards!image-2023-04-17-15-08-56-341.png!!image-2023-04-17-15-08-56-341!\'"", ""Comment 65: \'Hey dear This is were the only new things they noticed so far . ERP was great again. We will set the language n will report you the results ASAPThanks always \'"", ""Comment 66: \'Good Morning SirERP module is Working great again ! all operators are working ; The language setting was done and receipts are changed to English !Task P2 can be changed to Task P1 Thanks very much i will follow up the day routine responses from the operators and will let you know the Result . So we can close the Ticket finally . Regards \'"", ""Comment 67: \'Hello"", \'Comment 68: thank you for confirmation.So\', ""Comment 69: we will wait for final feedback.\'"", ""Comment 70: \'Hey Dear Today all our operators work day was great ! ERP is Doing Great again ; AKF was Dispatching and financial report sent using ERP module and no problems at all . Now we can close the ticket ! Problem Solved !  Thanks very much ! your immediate response and tentative support is very appreciated and helpful to our daily routine . Thanks again \']""]\nRelated Issues:\n[\'DGS-8946\']\n\n### End'}"
88,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8944\n\n### Instruction:\nHi\r\n\r\nWe have this SU barcode 90-W00WK4\r\nChecking the location tracking, we can find that it was moved with fast movement between 2 BUs, but the configuration is set to block such fast movement.\r\nCould you check why this happened and be sure that this will not happen again?\r\n\r\nThank you very much!\n\n### Response:\n[""Comment 1: [\'!image!!image-1!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'https://helpdesk.kotrak.com/browse/DAP-13372\'"", ""Comment 4: \'!image-2023-04-12-15-39-05-635.png!\'"", ""Comment 5: \'!image-2023-04-12-15-39-51-257.png!\'"", ""Comment 6: \'!image-2023-04-12-15-51-45-077.png!\'"", ""Comment 7: \'Na naszym tescie gdzie jest wersja 8,5 jest tylko jeden unit aleCiekawa rzecz kiedy sprawdząłam to wczoraj mieli to zaznczone"", ""Comment 8: aktualnie jest ti odznaczone u nichna false!image-2023-04-13-08-55-23-246.png!!image-2023-04-13-08-53-28-678.png!\'"", ""Comment 9: \'!dzisiaj.PNG! HelloWhen the movement was done,I noticed that when I verify configuration yestserday this parametr was checked - today it is unmarked ?Could you please verify why this was changed? There is possibility that in this case someone was able to create fast movement because"", ""Comment 10: the configuration was changed.!dzisiaj.PNG|thumbnail!\'"", \'Comment 11: ""Hi [~Agnieszka.Januszewska@kotrak.com]That\\\'s weird. I just access it and it\\\'s turned off. I\\\'m turning on right now!Only me and Priscyla have permission to configure this option. Priscyla is on vacation and I didn\\\'t turned off this configuration.Can you trace who is disabling it?Thank you very much!""\', ""Comment 12: \'HiThe situation is crtical: some users (like vandrade)  have access to WMS configuration screen"", ""Comment 13: however they are not System admin function.\'"", ""Comment 14: \'Ile takich przypadków wystąpiło? Moze po zmianie konfiguracji na zablokowana któryś z operatorów na mobilnym nie przelogował się i dalej miał zaczytana konfiguracje pozwalająca na movement?Użytkownik z uprawnieniami jak vandrade ma dostęp do konfiguracji"", \'Comment 15: ale po zapisie pojawia się komunikat o braku uprawnień.Oprócz Maicona i Priscyli konfiguracje mogą zmieniać aguelfi\', \'Comment 16: jveroneze (maja role system admina) i mój użytkownik :PInformacje o zmianie konfiguracji nie są zapisywane w tej wersji (dopiero w 8.6 w HttpRequestEvents)\', ""Comment 17: więc nie mam jak sprawdzić czy ktoś przestawiał konfigurację.!screenshot-1! \'"", ""Comment 18: \'Thank you for Your patience # regarding the functionality itself and with the blocking parameter enabled"", \'Comment 19: we have not been able to reproduce the situation. # from version 8.6 will be logged in the database information about who changed the configuration at this time we are not able to verify this # a user with permissions such as Vandrade only has access to view the configuration but should not be able to edit it (should show an error) # other users who can change configurations are Aguelfi\', ""Comment 20: Jveronezead 1,are there any more recent cases where you in production have managed to do fast movment and the parameter was definitely on ?If not and the explanations given are sufficient then can we close this task ?\'"", \'Comment 21: ""Hi [~Agnieszka.Januszewska@kotrak.com]Thank you for these information.Let\\\'s wait for R8.6You can close this taskThank you very much!""\', ""Comment 22: \'W AspNetUserClaims claima WmsConfiguration posiada:* admin* systemadmin\']""]\nRelated Issues:\n[]\n\n### End'}"
89,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8943\n\n### Instruction:\nHi\r\n\r\nThe PLR 0881100423005 didn\'t integrate from DHP to DHC.\r\nCould you please check why this happened and fix it?\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: \'12:56id=7c0a7f16-ab3d-4bca-8f6a-248a19b7c581!image-2023-04-11-18-01-13-510.png!!image-2023-04-11-18-01-13-510!\'"", ""Comment 3: \'!image-2023-04-11-18-03-33-100.png!!image-2023-04-11-18-25-23-759.png!!image-2023-04-11-18-25-23-759!\'"", ""Comment 4: \'Logi z wczoraj po id PLRa{code:java}2023-04-10 12:28:18 (9505b7fd-ae3a-4866-8563-0a83e5eb17cd/Plant.DHC.Integration/BR-3-SV-VM0202/6864/21) [Error] Plant.Integration.DhcService.Application.DhpToDhcMapFilter - Couldn\\\\\'t map dhp message Plant.QAM.BusinessLogic.DomainAbstractions.Quarantine.ProductionLotReportQuarantineSynchronizationEventKotrak.Integration.IdentityMapping.IdentityNotMappedException: Key of entity ProductionLotReportIdentityEntity was not mapped. Key value Id: 7c0a7f16-ab3d-4bca-8f6a-248a19b7c581   at Kotrak.Integration.IdentityMapping.EF.GenericIdentityMappingRepository`1.GetExternalKey(GuidKey key)   at Plant.Integration.DhcService.Application.ProductionLotReports.ProductionLotReportQuarantineMapFilter.MapIds(ProductionLotReportQuarantineSynchronizationEvent message"", \'Comment 5: ProductionLotReportQuarantine externalObject) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\e810c04f78ab209c\\\\\\\\Plant.Integration.DhcService\\\\\\\\Plant.Integration.DhcService.Application\\\\\\\\ProductionLotReports\\\\\\\\ProductionLotReportQuarantineMapFilter.cs:line 28   at Plant.Integration.DhcService.Application.DhpToDhcMapFilter`2.Process(PackageIntegrationState input) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\e810c04f78ab209c\\\\\\\\Plant.Integration.DhcService\\\\\\\\Plant.Integration.DhcService.Application\\\\\\\\DhpToDhcMapFilter.cs:line 442023-04-10 12:28:18 (9505b7fd-ae3a-4866-8563-0a83e5eb17cd/Plant.DHC.Integration/BR-3-SV-VM0202/6864/21) [Error] Plant.Integration.DhcService.Infrastructure.Handlers.BaseInboundMessageHandler - ProductionLotReportQuarantinePipelineExecutor execution errorKotrak.Integration.IdentityMapping.IdentityNotMappedException: Key of entity ProductionLotReportIdentityEntity was not mapped. Key value Id: 7c0a7f16-ab3d-4bca-8f6a-248a19b7c581   at Kotrak.Integration.IdentityMapping.EF.GenericIdentityMappingRepository`1.GetExternalKey(GuidKey key)   at Plant.Integration.DhcService.Application.ProductionLotReports.ProductionLotReportQuarantineMapFilter.MapIds(ProductionLotReportQuarantineSynchronizationEvent message\', \'Comment 6: ProductionLotReportQuarantine externalObject) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\e810c04f78ab209c\\\\\\\\Plant.Integration.DhcService\\\\\\\\Plant.Integration.DhcService.Application\\\\\\\\ProductionLotReports\\\\\\\\ProductionLotReportQuarantineMapFilter.cs:line 28   at Plant.Integration.DhcService.Application.DhpToDhcMapFilter`2.Process(PackageIntegrationState input) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\e810c04f78ab209c\\\\\\\\Plant.Integration.DhcService\\\\\\\\Plant.Integration.DhcService.Application\\\\\\\\DhpToDhcMapFilter.cs:line 44   at Kotrak.Integration.Pipeline.PredefinedFilters.FilterBase`1.Execute(T input)   at Kotrak.Integration.Pipeline.Pipeline`1.Excecute(T input)   at Plant.Integration.DhcService.Infrastructure.Handlers.BaseInboundMessageHandler`1.Handle(TEvent message) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\e810c04f78ab209c\\\\\\\\Plant.Integration.DhcService\\\\\\\\Plant.Integration.DhcService.Infrastructure\\\\\\\\Handlers\\\\\\\\BaseInboundMessageHandler.cs:line 492023-04-10 12:28:18 (9505b7fd-ae3a-4866-8563-0a83e5eb17cd/Plant.DHC.Integration/BR-3-SV-VM0202/6864/21) [Error] Kotrak.Integration.IntegrationPluginCommon.IntercontextCommunication.Inbound.InboundIntercontextErrorHandler - Error during handling message of type ""Plant.QAM.BusinessLogic.DomainAbstractions.Quarantine.ProductionLotReportQuarantineSynchronizationEvent""\', \'Comment 7: retry no 1Kotrak.Integration.IdentityMapping.IdentityNotMappedException: Key of entity ProductionLotReportIdentityEntity was not mapped. Key value Id: 7c0a7f16-ab3d-4bca-8f6a-248a19b7c581   at Kotrak.Integration.IdentityMapping.EF.GenericIdentityMappingRepository`1.GetExternalKey(GuidKey key)   at Plant.Integration.DhcService.Application.ProductionLotReports.ProductionLotReportQuarantineMapFilter.MapIds(ProductionLotReportQuarantineSynchronizationEvent message\', ""Comment 8: ProductionLotReportQuarantine externalObject) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\e810c04f78ab209c\\\\\\\\Plant.Integration.DhcService\\\\\\\\Plant.Integration.DhcService.Application\\\\\\\\ProductionLotReports\\\\\\\\ProductionLotReportQuarantineMapFilter.cs:line 28   at Plant.Integration.DhcService.Application.DhpToDhcMapFilter`2.Process(PackageIntegrationState input) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\e810c04f78ab209c\\\\\\\\Plant.Integration.DhcService\\\\\\\\Plant.Integration.DhcService.Application\\\\\\\\DhpToDhcMapFilter.cs:line 44   at Kotrak.Integration.Pipeline.PredefinedFilters.FilterBase`1.Execute(T input)   at Kotrak.Integration.Pipeline.Pipeline`1.Excecute(T input)   at Plant.Integration.DhcService.Infrastructure.Handlers.BaseInboundMessageHandler`1.Handle(TEvent message) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\e810c04f78ab209c\\\\\\\\Plant.Integration.DhcService\\\\\\\\Plant.Integration.DhcService.Infrastructure\\\\\\\\Handlers\\\\\\\\BaseInboundMessageHandler.cs:line 49   at Kotrak.Integration.IntegrationPluginCommon.IntercontextCommunication.Inbound.IntercontextInboundHandler`2.Handle(InternalStorageDto message){code}\'"", ""Comment 9: \'!image-2023-04-11-18-13-07-747.png!!image-2023-04-11-18-17-28-608.png!!image-2023-04-11-18-17-05-044.png!!image-2023-04-11-18-16-22-596.png!\'"", ""Comment 10: \'Ostatni PCSowy event dla tego Lota to finished:!image-2023-04-11-18-27-59-817.png!!image-2023-04-11-18-29-59-430.png!!image-2023-04-11-18-29-59-430!\'"", ""Comment 11: \'Stany poszły:!image-2023-04-11-18-38-28-547.png!\'"", ""Comment 12: \'Przy wróceniu PLRa na finished i confirm z aplikacji pojawia się błąd:Current settlement configuration requires that deliveries are explicitly specified appearsTo samo co tu:https://helpdesk.kotrak.com/browse/DGS-8639\'"", ""Comment 13: \'Hi [~mberbert@deheus.com]  I have verified this issue very carefully and it is the same as in taskDGS-8639. So similarly"", \'Comment 14: I need to ask dev team for help. We will revert to you as soon as possible. Please\', ""Comment 15: let me know if there is any possibility to downgrade priority to P2?Regards\'"", ""Comment 16: \'Hi AleksandraYes"", ""Comment 17: you can downgrade to P2Thank you\'"", ""Comment 18: \'Hej"", ""Comment 19: przekazuję zgodnie z ustaleniami z Olą. Dzięki.\'"", ""Comment 20: \'Hej,Po rozmowie z Łukaszem wynika że znowu poleciał timeout.Do wersji 8.5 udało się już zrobić rozwiązanie która zwiększa ten timeout: https://helpdesk.kotrak.com/browse/DAP-13377.Jeżeli chodzi o wygenerowanie eventa to jest skrypt który go tworzy:http://10.10.10.52:82/projects/PLA3/repos/dhp30implementations/browse/BASE/8.3.0/SQL/create_plr_confirmed_event.sqlW linii nr 8 nalezy podać id lotu\'"", ""Comment 21: \'Dziękuję <3\'"", ""Comment 22: \'Hi [~mberbert@deheus.com],PLR in DHC now:!image-2023-04-12-13-20-56-173.png!Regards\'"", \'Comment 23: ""Hi [~Aleksandra.Przybylek@kotrak.com]If the root cause is the same as DGS-8639\', \'Comment 24: do you know why the recipe is in DHP but not in DHC?You see? DHP only have the recipe because it was received from DHC\', \'Comment 25: and now DHC doesn\\\'t have it. Is it some crashing in the DHC database?Thank you""\', ""Comment 26: \'There was a timeout while confirm PLR. The event did not create correct and PLR did not arrive to DHC.In version 8.5 it is solved by extending the time untill the timeout.Can we close this task?Regards\'"", ""Comment 27: \'Hi [~Aleksandra.Przybylek@kotrak.com]Thank you!You can close this task.\'"", ""Comment 28: \'Thank you\'"", ""Comment 29: \'Timeout był - Łukasz Furlepa znalazł\']""]\nRelated Issues:\n[]\n\n### End'}"
90,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8942\n\n### Instruction:\nIn DHC test (3.0.63) we do not get any data from ERP in orders overview. Data seem to be processed in DHC (order is in communication log), but it is not visible in Order overview and not sent to DHP.\r\nSee e.g. sales order SO000057002, created 11/4/2023 15:44\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!!image-1!\'"", ""Comment 2: \'Hi Bob,I am very sorry but the DGS project is to raise the incident/issue tickets related to the production environment. In case of introducing new features or modifying existing ones please rise a GDC ticket"", ""Comment 3: for questions or issues on the test environment you can rise a DHITS.Best regards\'"", ""Comment 4: \'Hi Aleksandra"", ""Comment 5: I have created https://helpdesk.kotrak.com/projects/GDC/issues/GDC-914?filter=allissues for this issue.This ticket can be closed.\'"", ""Comment 6: \'Thank you"", ""Comment 7: Bob.Regards\']""]\nRelated Issues:\n[]\n\n### End'}"
91,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8941\n\n### Instruction:\nHello guys, we have problem with PO-213. in DHC and DHP it has status ""Executed"", which is incorrect. PO-213 has ordered quantity 1000t and received q-ty (from VTs) = 339.14t. I have checked in ERP and, each VT received by ERP has multiplied intake quantity - 3 or 4 times. In the attached .xml example you will see 4 lines for VT-240, which intake quantity was: 39.68 t, and in ERP we received 158.72t (4 times more), that is why each intake consumes ordered quantity 3 or 4 times faster. For PO-213 we have 9 VTs registered, and it is impossible that each of them is for 100-150 t, as we see in ERP. I have checked the log from DHC and I can see there are indeed wrong quantities sent from DHC to ERP (see attached screen). Please investigate the reason of such error, and fix it ASAP, users cannot register more intakes for this PO. \r\nAs another example there is .xml for VT-74 - for the same PO-213, tripled quantity. \r\nPlease make sure that DHC error is fixed, because we have such problems with other POs as well. Once the error is fixed, please deploy the update on the production environment asap, to prevent such issues in the future. \n\n### Response:\n[""Comment 1: [\'!image!!image-1!!image-2![^INTK_PO000213_2621.xml] _(3 kB)_[^INTK_PO000213_2944.xml] _(4 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: any news? \'"", \'Comment 5: ""{code:java}SELECT *  FROM [DHCountry_IVC_Prod].[dbo].[Orders] where DocumentNumber = \\\'PO000213\\\'  SELECT *  FROM [DHCountry_IVC_Prod].[dbo].[OrderElements] where OrderId = \\\'F2900603-1487-410E-8113-38796A186978\\\'  SELECT *  FROM [DHCountry_IVC_Prod].[dbo].[VehicleTickets] where DocumentNumber like \\\'240/1/2023%\\\'{code}!image-2023-04-12-17-06-45-081.png!""\', \'Comment 6: \\\'{code:java}xmlMessage: <?xml version=""1.0""?><IntakeDataContractDeHeusWoW xmlns:xsd=""http://www.w3.org/2001/XMLSchema"" xmlns:xsi=""http://www.w3.org/2001/XMLSchema-instance"">  <Lines>    <IntakeLineDeHeusWoW>      <LineId>1342243292</LineId>      <LineOrder>1</LineOrder>      <TransactionId>CIP-002585</TransactionId>      <ItemCode>1002010</ItemCode>      <ItemName>Maïs Importer</ItemName>      <PurchStatus>Received</PurchStatus>      <OrderQty>62.06</OrderQty>      <OrderQtyUOM>t</OrderQtyUOM>      <Origin />      <BatchProdDate>1900-01-01T00:00:00</BatchProdDate>      <BatchExpDate>1900-01-01T00:00:00</BatchExpDate>      <PSId>240/1/2023/</PSId>      <PSDate>2023-01-10T00:00:00</PSDate>      <VendorRef />      <DeliveredQty>158.72</DeliveredQty>      <DeliveredQtyUOM>t</DeliveredQtyUOM>      <SupplierQty>0</SupplierQty>      <DeliveryTime />      <DeliveryTimeDescr />      <ExpectedDeliveryDate>2022-12-28T00:00:00</ExpectedDeliveryDate>      <PurchOrder>PO000213</PurchOrder>      <OrderDate>2022-12-28T11:00:45</OrderDate>      <Type>0</Type>      <VendorCode>CIPV00071</VendorCode>      <VendorName>KENZ COTE D\\\\\\\'IVOIRE</VendorName>      <Remarks />      <VehicleTypeCode />      <VehicleId />      <VehicleCode />      <CarrierCode />      <CarrierName />      <PeriodCode />      <AnnouncementCode />      <ProgressStatus />      <ProgressStatusDescription />      <ProducerCode />      <ProducerName />      <PurchContractType />      <Purchcontract />      <PurchContractReference />      <DeliveryMode />      <PurchLineText />      <CustomerRequisition />      <SalesTerms>Delivered weight</SalesTerms>      <Price>300000</Price>      <PriceUnitFactor>1</PriceUnitFactor>      <PriceUnitId>t</PriceUnitId>      <CountryOrigin />      <SiteCode>CIPWH01</SiteCode>      <WhsCode>CIPWH01</WhsCode>      <SizeId />      <ConfigId />      <ColorId />      <LocationId />      <BatchId />      <AddressID>000006027</AddressID>    </IntakeLineDeHeusWoW>  </Lines>  <ApprovalStatus>Confirmed</ApprovalStatus>  <EndpointID>0</EndpointID>  <CreateDate>2023-01-10T17:51:49.2242058+01:00</CreateDate>  <CreateUser>Admin</CreateUser>  <TenantCode>CIP</TenantCode>  <SaveType>2</SaveType>  <LanguageCode />  <SourceAppVersion>7.0.6441.41</SourceAppVersion>  <ExpireDate>2023-01-11T17:51:49.2242058+01:00</ExpireDate>  <UniqueID>{3AD57C82-A1D7-47A2-9943-9396D95E6351}</UniqueID>  <EndpointCode>AX</EndpointCode>  <SourceInfo>Intake_20235110045149000_PO000213</SourceInfo></IntakeDataContractDeHeusWoW>2023-01-10 16:51:49,118 [29] DEBUG Evolution.DHCERPService.ImplementationRestWoW.Savers.DataContractSaver`2 [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\31916033\\\\\\\\DHAPPSV3-DHCER391-JOB1\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.ImplementationRestWoW\\\\\\\\Savers\\\\\\\\DataContractSaver.cs:39] - Saving IntakeDataContractDeHeusWoW2023-01-10 16:51:49,165 [29] DEBUG Evolution.DHCERPService.Service.BaseSaveService`1 [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\31916033\\\\\\\\DHAPPSV3-DHCER391-JOB1\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.Implementation\\\\\\\\Orders\\\\\\\\OrderSaveService.cs:165] - UnmapDeletedElements deletedElements.Count = 02023-01-10 16:51:49,165 [29] INFO  Evolution.DHCERPService.Service.BaseSaveService`1 [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\31916033\\\\\\\\DHAPPSV3-DHCER391-JOB1\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.Service\\\\\\\\BaseSaveService.cs:79] - Saved: OrderObject with Id Id: PO0002132023-01-10 16:51:49,165 [29] DEBUG Evolution.DHCERPService.ImplementationRestWoW.Savers.DataContractSaver`2 [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\31916033\\\\\\\\DHAPPSV3-DHCER391-JOB1\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.ImplementationRestWoW\\\\\\\\Savers\\\\\\\\DataContractSaver.cs:44] - IntakeDataContractDeHeusWoW saved2023-01-10 16:51:50,477 [61] INFO  Evolution.DHCERPService.MessageSender.Actors.ClientServiceCallActor [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\31916033\\\\\\\\DHAPPSV3-DHCER391-JOB1\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.MessageSender\\\\\\\\Actors\\\\\\\\ClientServiceCallActor.cs:66] - Message with command PurchaseOrderReceiptSave and object id 1255a0c0-6c77-4a20-8181-5757aaec751c was sucessfully processed.2023-01-10 16:51:50,477 [57] INFO  Evolution.DHCERPService.WoWWebServiceClient.Commands.CommandDecorator [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\31916033\\\\\\\\DHAPPSV3-DHCER391-JOB1\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.WoWWebServiceClient\\\\\\\\Commands\\\\\\\\CommandDecorator.cs:26] - Executing VehicleTicketSaveCommand 1255a0c0-6c77-4a20-8181-5757aaec751c2023-01-10 16:51:50,477 [57] WARN  Evolution.DHCERPService.WoWWebServiceClient.Commands.VehicleTicketSaveCommand [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\31916033\\\\\\\\DHAPPSV3-DHCER391-JOB1\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.WoWWebServiceClient\\\\\\\\Commands\\\\\\\\VehicletTicketSaveCommand.cs:63] - VT 1255a0c0-6c77-4a20-8181-5757aaec751c was already synchronized - skiped2023-01-10 16:51:50,477 [57] INFO  Evolution.DHCERPService.MessageSender.Actors.ClientServiceCallActor [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\31916033\\\\\\\\DHAPPSV3-DHCER391-JOB1\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.MessageSender\\\\\\\\Actors\\\\\\\\ClientServiceCallActor.cs:66] - Message with command PurchaseOrderReceiptSave and object id 1255a0c0-6c77-4a20-8181-5757aaec751c was sucessfully processed.2023-01-10 17:16:03,277 [52] DEBUG Evolution.DHCERPService.ImplementationRestWoW.Controllers.ServiceController [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\31916033\\\\\\\\DHAPPSV3-DHCER391-JOB1\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.ImplementationRestWoW\\\\\\\\Controllers\\\\\\\\ServiceController.cs:48] - dataContract: ArticleDataContractDeHeusWoW{code}\\\'\', ""Comment 7: \'Z 10 stycznia nie ma żadnego messega!image-2023-04-12-17-16-27-965.png!\'"", ""Comment 8: \'{code:java}2023-01-10 16:51:49,274 [24] INFO  Evolution.DHCService.Dhc30.Handlers.OrderChangedMessageHandler [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\31916033\\\\\\\\DHAPPSV3-DHCSER538-JOB1\\\\\\\\Evolution.DHCService\\\\\\\\Evolution.DHCService.Dhc30\\\\\\\\Handlers\\\\\\\\BaseMessageHandler.cs:37] - Receiving message (Evolution.DHCountry.Interfaces.Orders.Messages.OrderChangedMessage) [Id:f2900603-1487-410e-8113-38796a186978]2023-01-10 16:51:49,290 [24] INFO  Evolution.DHCService.Dhc30.Handlers.OrderChangedMessageHandler [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\31916033\\\\\\\\DHAPPSV3-DHCSER538-JOB1\\\\\\\\Evolution.DHCService\\\\\\\\Evolution.DHCService.Dhc30\\\\\\\\Handlers\\\\\\\\BaseMessageHandler.cs:49] - Message received successfuly!2023-01-10 16:52:12,874 [12] INFO  Evolution.DHCService.Dhc30.OrderService [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\31916033\\\\\\\\DHAPPSV3-DHCSER538-JOB1\\\\\\\\Evolution.DHCService\\\\\\\\Evolution.DHCService.Dhc30\\\\\\\\BaseGetService.cs:47] - [ClientId: (6be3433c-61ee-4586-94a0-f5c966542f45)] Handling: (Order) Package(33ba31df-b1bb-4080-b79c-18db6e34cb57) Sending: 12023-01-10 16:52:12,936 [12] INFO  Evolution.DHCService.Dhc30.OrderService [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\31916033\\\\\\\\DHAPPSV3-DHCSER538-JOB1\\\\\\\\Evolution.DHCService\\\\\\\\Evolution.DHCService.Dhc30\\\\\\\\BaseGetService.cs:64] - [ClientId: (6be3433c-61ee-4586-94a0-f5c966542f45)] Handling: (Order) Package(33ba31df-b1bb-4080-b79c-18db6e34cb57) Confirming: 12023-01-10 17:26:51,794 [27] INFO  Evolution.DHCService.Dhc30.Handlers.ItemChangedMessageHandler [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\31916033\\\\\\\\DHAPPSV3-DHCSER538-JOB1\\\\\\\\Evolution.DHCService\\\\\\\\Evolution.DHCService.Dhc30\\\\\\\\Handlers\\\\\\\\BaseMessageHandler.cs:37] - Receiving message (Evolution.DHCountry.Interfaces.Items.ItemChangedMessage) [Id:1fa62ef5-d7c8-44df-aee9-59700526448d]2023-01-10 17:26:51,856 [27] INFO  Evolution.DHCService.Dhc30.Handlers.ItemChangedMessageHandler [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\31916033\\\\\\\\DHAPPSV3-DHCSER538-JOB1\\\\\\\\Evolution.DHCService\\\\\\\\Evolution.DHCService.Dhc30\\\\\\\\Handlers\\\\\\\\BaseMessageHandler.cs:49] - Message received successfuly!2023-01-10 17:27:12,512 [32] INFO  Evolution.DHCService.Dhc30.ItemService [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\31916033\\\\\\\\DHAPPSV3-DHCSER538-JOB1\\\\\\\\Evolution.DHCService\\\\\\\\Evolution.DHCService.Dhc30\\\\\\\\BaseGetService.cs:47] - [ClientId: (6be3433c-61ee-4586-94a0-f5c966542f45)] Handling: (Item) Package(f8806264-93a0-40b5-80a6-2bb8243554f6) Sending: 12023-01-10 17:27:12,606 [32] INFO  Evolution.DHCService.Dhc30.ItemService [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\31916033\\\\\\\\DHAPPSV3-DHCSER538-JOB1\\\\\\\\Evolution.DHCService\\\\\\\\Evolution.DHCService.Dhc30\\\\\\\\BaseGetService.cs:64] - [ClientId: (6be3433c-61ee-4586-94a0-f5c966542f45)] Handling: (Item) Package(f8806264-93a0-40b5-80a6-2bb8243554f6) Confirming: 12023-01-10 17:27:19,325 [19] INFO  Evolution.DHCService.Dhc30.Handlers.ItemChangedMessageHandler [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\31916033\\\\\\\\DHAPPSV3-DHCSER538-JOB1\\\\\\\\Evolution.DHCService\\\\\\\\Evolution.DHCService.Dhc30\\\\\\\\Handlers\\\\\\\\BaseMessageHandler.cs:37] - Receiving message (Evolution.DHCountry.Interfaces.Items.ItemChangedMessage) [Id:1fa62ef5-d7c8-44df-aee9-59700526448d]2023-01-10 17:27:19,341 [19] INFO  Evolution.DHCService.Dhc30.Handlers.ItemChangedMessageHandler [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\31916033\\\\\\\\DHAPPSV3-DHCSER538-JOB1\\\\\\\\Evolution.DHCService\\\\\\\\Evolution.DHCService.Dhc30\\\\\\\\Handlers\\\\\\\\BaseMessageHandler.cs:49] - Message received successfuly!2023-01-10 17:27:19,622 [17] INFO  Evolution.DHCService.Dhc30.Handlers.ItemChangedMessageHandler [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\31916033\\\\\\\\DHAPPSV3-DHCSER538-JOB1\\\\\\\\Evolution.DHCService\\\\\\\\Evolution.DHCService.Dhc30\\\\\\\\Handlers\\\\\\\\BaseMessageHandler.cs:37] - Receiving message (Evolution.DHCountry.Interfaces.Items.ItemChangedMessage) [Id:1fa62ef5-d7c8-44df-aee9-59700526448d]2023-01-10 17:27:19,638 [17] INFO  Evolution.DHCService.Dhc30.Handlers.ItemChangedMessageHandler [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\31916033\\\\\\\\DHAPPSV3-DHCSER538-JOB1\\\\\\\\Evolution.DHCService\\\\\\\\Evolution.DHCService.Dhc30\\\\\\\\Handlers\\\\\\\\BaseMessageHandler.cs:49] - Message received successfuly!2023-01-10 17:27:19,888 [16] INFO  Evolution.DHCService.Dhc30.Handlers.ItemChangedMessageHandler [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\31916033\\\\\\\\DHAPPSV3-DHCSER538-JOB1\\\\\\\\Evolution.DHCService\\\\\\\\Evolution.DHCService.Dhc30\\\\\\\\Handlers\\\\\\\\BaseMessageHandler.cs:37] - Receiving message (Evolution.DHCountry.Interfaces.Items.ItemChangedMessage) [Id:1fa62ef5-d7c8-44df-aee9-59700526448d]2023-01-10 17:27:19,919 [16] INFO  Evolution.DHCService.Dhc30.Handlers.ItemChangedMessageHandler [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\31916033\\\\\\\\DHAPPSV3-DHCSER538-JOB1\\\\\\\\Evolution.DHCService\\\\\\\\Evolution.DHCService.Dhc30\\\\\\\\Handlers\\\\\\\\BaseMessageHandler.cs:49] - Message received successfuly!2023-01-10 17:28:12,491 [27] INFO  Evolution.DHCService.Dhc30.ItemService [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\31916033\\\\\\\\DHAPPSV3-DHCSER538-JOB1\\\\\\\\Evolution.DHCService\\\\\\\\Evolution.DHCService.Dhc30\\\\\\\\BaseGetService.cs:47] - [ClientId: (6be3433c-61ee-4586-94a0-f5c966542f45)] Handling: (Item) Package(064108f1-0585-4bcd-baa0-4ecfc437a3de) Sending: 12023-01-10 17:28:12,522 [27] INFO  Evolution.DHCService.Dhc30.ItemService [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\31916033\\\\\\\\DHAPPSV3-DHCSER538-JOB1\\\\\\\\Evolution.DHCService\\\\\\\\Evolution.DHCService.Dhc30\\\\\\\\BaseGetService.cs:64] - [ClientId: (6be3433c-61ee-4586-94a0-f5c966542f45)] Handling: (Item) Package(064108f1-0585-4bcd-baa0-4ecfc437a3de) Confirming: 1{code}\'"", ""Comment 9: \'Po id vt!image-2023-04-12-17-29-20-121.png!po ID elementu też nie!image-2023-04-12-17-31-36-451.png!\'"", ""Comment 10: \'!image-2023-04-12-17-36-48-323.png!\'"", ""Comment 11: \'Good morning"", ""Comment 12: any news? \'"", ""Comment 13: \'[~aleksandra.przybylek@kotrak.com]daj na DEV"", ""Comment 14: sprawdzimy\'"", ""Comment 15: \'[~piotr.chmielarski@kotrak.com]dziękuję bardzo :)ja mam w tym tygodniu 2 zmianę czyli od 12"", \'Comment 16: ogarniam maile :)Przeprowadziłam jakąś wstępną analizę\', \'Comment 17: ale szczerze mówiąc zabrakło mi pomysłu i jakichś jednoznacznych treści logów\', ""Comment 18: co w erpie poszło nie tak ...\'"", ""Comment 19: \'Good morning"", ""Comment 20: any news? \'"", ""Comment 21: \'Błąd był rozwiązany w tym tasku: https://helpdesk.kotrak.com/browse/DHITS-639podegranie było 01.19.2023 !screenshot-1! a zgłaszają problem z 01.10.2023 !screenshot-2! \'"", ""Comment 22: \'Hi,This issue has been resolved in https://helpdesk.kotrak.com/browse/DHITS-639and DHCERPService with a fix has been deployed on19th of January. Reported PO are from the 10th of January.Regards\'"", \'Comment 23: ""Indeed\', ""Comment 24: this is not the case for later PO\'s. Thank you for the response"", \'Comment 25: please close the ticket.""\', ""Comment 26: \'Thank you\']""]\nRelated Issues:\n[]\n\n### End'}"
92,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8940\n\n### Instruction:\nHello,\r\n\r\nPlease assist we are getting the attached error message when we log in on Replacement Prices/ Historical Price.\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'SELECT TOP (1000) * FROM [CDNXL_DHFU].[dbo].[RMPricesReplacementPriceQuery] where itemtype is null – tu jest czysto\'"", ""Comment 4: \'!image-2023-04-11-15-27-24-410.png!\'"", ""Comment 5: \'Could you please try again?\'"", ""Comment 6: \'https://helpdesk.kotrak.com/browse/DGS-4257\'"", ""Comment 7: \'Still getting the same error message.\'"", ""Comment 8: \'[[DHCDN] Historical Prices Upload timeout|#%5bDHCDN%5d%20Historical%20Prices%20Upload%20timeout&section-id=\\\\\\\\{A2F09CD6-A23A-42F3-92F5-ED66B521455B}&page-id=\\\\\\\\{8C2933BA-621C-4FF9-AA0C-BD7B0049AC54}&end] ([Widok sieci Web|https://kotrak.sharepoint.com/sites/erpasysta/_layouts/OneNote.aspx?id=%2Fsites%2Ferpasysta%2FShared%20Documents%2FBaza%20wiedzy%2FBaza%20Wiedzy%20-%20ERPSD&wd=target%28Klienci%2FDEHEUS%2FDEHEUS%20APPLICATIONS%2FRPA%2FBaza%20wiedzy.one%7CA2F09CD6-A23A-42F3-92F5-ED66B521455B%2F%5BDHCDN%5D%20Historical%20Prices%20Upload%20timeout%7C8C2933BA-621C-4FF9-AA0C-BD7B0049AC54%2F%29]) ale ten adres 138 jest już chyba niekatulny ,może to 248 - tam jest teraz BI.\'"", ""Comment 9: \'Please try again.\'"", \'Comment 10: ""As per teams\', \'Comment 11: I\\\'m still getting the same error message""\', ""Comment 12: \'Dear Nosipho,I have restarted service. For me it is working fine. Could you please check on your side?Regards\'"", ""Comment 13: \'I think the case is similar as in taskDGS-8328As you can see below"", ""Comment 14: percentage of fragmentation seems to be quite high. And there are 114 rows for fragmentation higher than 30%In taskDGS-8328 Rey mentioned that then server 20 has failed. Could you please verify the server and let me know if shall I rebuild indexes?Regards!image-2023-04-11-16-49-19-421.png!\'"", ""Comment 15: \'to raczej będzie tohttps://helpdesk.kotrak.com/browse/DGS-8328\'"", ""Comment 16: \'Reindex ran this morning"", ""Comment 17: but we still have the issue.I am going to reboot and manually run th ere-index.!image-1!!image-2!\'"", ""Comment 18: \'!serw20.PNG|thumbnail!\'"", ""Comment 19: \'According to what Aleksandra wrote yesterdayI check now the indexes on erp_xl database there are still indexes with high fragmentation - mainly related to tables use for replacment price!image-2023-04-12-09-17-25-218.png|width=503,height=324!So let us know whe you will finish the rebiuld or if you wish us to do it.Second thing is the working of server|SAHOSRV020|10.27.0.248|in previous similar task :DGS-8328There were problem with it. Could you please verify it alsoAnd could we change the priority for p2 issue?\'"", ""Comment 20: \'!image-3!\'"", ""Comment 21: \'ERP-XL  databases are indexed daily"", ""Comment 22: and that job is also succeeding !image-4!\'"", ""Comment 23: \'What server is in your screenshot? I just checked SAHOSRV07 and nothing of any size is above 6% fragmentation.\'"", ""Comment 24: \'Morning,Still getting the attached error message !image-5!\'"", ""Comment 25: \'|SAHOSRV07|10.27.0.7|I verified only erp xl database!image-2023-04-12-09-57-33-478.png!\'"", \'Comment 26: \\\'I double check and this are some tables that do not use clustered/nonclustered ""indexes \', \'Comment 27: but ""heaps"".Did you verify the server10.27.0.248 if t s working fine ?Hello,Kindly approve lowering priority of this task to P2 as P1 issues are only those with a critical or a blocking impact on business processes .Regards\\\'\', \'Comment 28: ""We have not modified or adjusted any index\\\'s in the SRV020. As we did not want to affect it\\\'s performance in a negative manner. Has someone from Kotrak removed index\\\'s with the last update?What server is 248?This issue is urgent. We need to resolve ASAP. Do you have a solution?""\', ""Comment 29: \'I restarted services again. Please verify if that help.\'"", ""Comment 30: \'Same error message\'"", ""Comment 31: \'As Aleksandra mentioned before And I also mentioned8328the server is the|SAHOSRV020|10.27.0.248|!image-2023-04-12-10-15-42-574.png!\'"", ""Comment 32: \'Your records are incorrect. See attached screenshot of ping to server. What server are you looking at?On the screenshot you supplied of the heap tables"", ""Comment 33: I assume you are refering to the KR_ReplacementPriceForecast table. This table is tiny. See second screenshot. Can you tell me what table is causing this issue?!image-6!!image-7!\'"", ""Comment 34: \'On task DGS-8328. All maintenance jobs were implimented and are running succefully. Have also been run manually this morning.  What further information do you require?\'"", ""Comment 35: \'We are consulting issue with developer"", ""Comment 36: if we have ither question we will ask\'"", ""Comment 37: \'komunikat wyslany an teams:!image-2023-04-12-11-35-57-816.png!\'"", ""Comment 38: \'Please try now. But it wroks slow 5-10 minutes!image-2023-04-12-12-44-01-192.png!!image-2023-04-12-12-44-01-192!\'"", \'Comment 39: ""I\\\'m getting this error message !image-8!""\', ""Comment 40: \'Please log out "", ""Comment 41: close dhcdn and ten start it and log again.\'"", ""Comment 42: \'The plug in is too slow"", ""Comment 43: it ran for 15min (no error messages).\'"", ""Comment 44: \'Hello,In this task we have focused on clearingandunblocking the process.Kindly approve lowering priority of this task to P2 as P1 issues are only those with a critical or a blocking impact on business processes . This seems not to be the case in this issue so we suggest decreasing the issue priority.In terms of performance"", \'Comment 45: it would be recommended to rebuild the current functionality\', \'Comment 46: one direction could be to make it independent of the ERPXL table\', ""Comment 47: for this we would ask you to create a change request - GDC.\'"", ""Comment 48: \'You can lower to P2.\'"", ""Comment 49: \'About slowly work "", \'Comment 50: today I verify the function again and list of historical prices and the list loaded after 1-2 minutes.So if there were any other job or other problems thatslowed down the operation ?Could you test it today ?Also as I wrote beforeIn terms of performance\', \'Comment 51: it would be recommended to rebuild the current functionality\', \'Comment 52: one direction could be to make it independent of the ERPXL table\', ""Comment 53: for this we would ask you to create a change request - GDC.\'"", ""Comment 54: \'Hello,We restarted RDS servers last night and the issue was resolved.\']""]\nRelated Issues:\n[]\n\n### End'}"
93,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8939\n\n### Instruction:\nProszę o analizę podstawy wynagrodzenia pracownika Johannes van der Wegen na liście E-UM/2023/03/*.\r\n\r\nJest bardzo wysoka podstawa do składki zdrowotnej.\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: \'[^DGS-8939.docx]\'"", ""Comment 3: \'The description in the attachment[^DGS-8939.docx]\'"", ""Comment 4: \'Task to close \']""]\nRelated Issues:\n[]\n\n### End'}"
94,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8938\n\n### Instruction:\nThere is PO-363 which is not synchronized to DHP. The PO element is new RM and it was not linked with BMX item before the PO was registered in ERP. I have linked the item 1116010 (po item) with production area IVC in DHH, the item was sent to DHC and automatically linked with ERP article, however the PO-363 (made for 1116010) is not synced to DHP. Please can you sent the PO-363 to DHP? Users must register the intake asap. \n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'please resend the order from ERP\'"", ""Comment 3: \'Done and it worked. Thanks for the support"", ""Comment 4: you can close the ticket. \'"", ""Comment 5: \'Thank you"", ""Comment 6: for confirmation.\']""]\nRelated Issues:\n[]\n\n### End'}"
95,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8937\n\n### Instruction:\nNext to item codes \'TARW\',\'OWNW\',\'0041\',\'0043\',\'0048\',\'702066\',\'704910\' we need to include \'704913\'.\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 2: ""w procedurach KR_calculatetechresults iKR_calculatetechresults_MASBEpowinnien być uwzględniany także kod \\\'704913\\\' w kalkulacji @WeightofWheat!image-2023-04-11-12-39-44-142.png!""\', \'Comment 3: ""Item with code\\\'704913\\\' has been added to calculation. Now it is also included for Weight of Wheat\', \'Comment 4: so value of \\\'Percentage Wheat\\\' will be calulated also including this item.It\\\'s ready to test on Test environment in MAS NL and MAS BE sectors.Please verify and then we can move it to Production environment.""\', ""Comment 5: \'Can be closed\'"", ""Comment 6: \'It has been moved to Production environment in MAS NL and MAS BE sectors.\']""]\nRelated Issues:\n[]\n\n### End'}"
96,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8936\n\n### Instruction:\nDears,\r\n\r\nVT no. 158/4/2023 is in DHC and not in ERP even after generation.\r\n\r\nNote this issue is repeated with the same item number.\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-04-11 10:03:58,992 [188] INFO  Evolution.DHCERPService.MessageSender.Handlers.BaseMessageHandler`1 [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\152764417\\\\\\\\DHAPPSV3-DHCER-JOB1\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.MessageSender\\\\\\\\Handlers\\\\\\\\BaseMessageHandler.cs:52] - Receiving message (Evolution.DHCountry.Interfaces.VehicleTickets.Messages.VehicleTicketFinishedChangedMessage) [Id:86768678-f8e1-4374-a1ca-c75bb38855fc]2023-04-11 10:03:58,995 [188] INFO  Evolution.DHCERPService.MessageSender.Handlers.BaseMessageHandler`1 [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\152764417\\\\\\\\DHAPPSV3-DHCER-JOB1\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.MessageSender\\\\\\\\Handlers\\\\\\\\BaseMessageHandler.cs:60] - Message received successfuly!2023-04-11 10:03:59,069 [141] INFO  Evolution.DHCERPService.MessageSender.Actors.ClientServiceCallActor [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\152764417\\\\\\\\DHAPPSV3-DHCER-JOB1\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.MessageSender\\\\\\\\Actors\\\\\\\\ClientServiceCallActor.cs:66] - Message with command PurchaseOrderReceiptSave and object id 86768678-f8e1-4374-a1ca-c75bb38855fc was sucessfully processed.{code}{code:java}2023-04-05 16:10:44,403 [95] INFO  Evolution.DHCERPService.MessageSender.Handlers.BaseMessageHandler`1 [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\152764417\\\\\\\\DHAPPSV3-DHCER-JOB1\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.MessageSender\\\\\\\\Handlers\\\\\\\\BaseMessageHandler.cs:52] - Receiving message (Evolution.DHCountry.Interfaces.VehicleTickets.Messages.VehicleTicketFinishedChangedMessage) [Id:86768678-f8e1-4374-a1ca-c75bb38855fc]2023-04-05 16:10:44,403 [95] INFO  Evolution.DHCERPService.MessageSender.Handlers.BaseMessageHandler`1 [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\152764417\\\\\\\\DHAPPSV3-DHCER-JOB1\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.MessageSender\\\\\\\\Handlers\\\\\\\\BaseMessageHandler.cs:60] - Message received successfuly!2023-04-05 16:10:44,653 [175] INFO  Evolution.DHCERPService.MessageSender.Handlers.BaseMessageHandler`1 [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\152764417\\\\\\\\DHAPPSV3-DHCER-JOB1\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.MessageSender\\\\\\\\Handlers\\\\\\\\BaseMessageHandler.cs:52] - Receiving message (Evolution.DHCountry.Interfaces.VehicleTickets.Messages.VehicleTicketFinishedChangedMessage) [Id:86768678-f8e1-4374-a1ca-c75bb38855fc]2023-04-05 16:10:44,653 [175] INFO  Evolution.DHCERPService.MessageSender.Handlers.BaseMessageHandler`1 [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\152764417\\\\\\\\DHAPPSV3-DHCER-JOB1\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.MessageSender\\\\\\\\Handlers\\\\\\\\BaseMessageHandler.cs:60] - Message received successfuly!2023-04-05 16:10:46,075 [186] INFO  Evolution.DHCERPService.MessageSender.Actors.ClientServiceCallActor [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\152764417\\\\\\\\DHAPPSV3-DHCER-JOB1\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.MessageSender\\\\\\\\Actors\\\\\\\\ClientServiceCallActor.cs:66] - Message with command PurchaseOrderReceiptSave and object id 86768678-f8e1-4374-a1ca-c75bb38855fc was sucessfully processed.2023-04-05 16:10:46,091 [38] INFO  Evolution.DHCERPService.MessageSender.Actors.ClientServiceCallActor [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\152764417\\\\\\\\DHAPPSV3-DHCER-JOB1\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.MessageSender\\\\\\\\Actors\\\\\\\\ClientServiceCallActor.cs:66] - Message with command PurchaseOrderReceiptSave and object id 86768678-f8e1-4374-a1ca-c75bb38855fc was sucessfully processed.{code}\'"", ""Comment 3: \'We have information from the DHCERPService that the document PurchaseOrderReceiptSave was sucessfully processed,can you check on the ERP side?\'"", ""Comment 4: \'Sorry"", ""Comment 5: the VT no is :185/4/2023\'"", ""Comment 6: \'Błąd jak we wcześniejszych taskach - System.Exception: Not all vehicle ticket elements are present.Brak end date dla Item nutrient level z 31.3 !screenshot-1! Po wpisaniu przeszło.\'"", \'Comment 7: ""itemversionclosed - taki message!image-2023-04-13-12-36-13-150.png!ostatnie błędy są z 2022!image-2023-04-13-12-37-39-400.png!\', \'Comment 8: dla tych co dodałem closed nie ma wpisu w logu DHCServer. tj.{code:java}select *  FROM [Evolution_DHCountry].[dbo].[ItemVersions]  where DhhItemId=\\\'E90F8CC2-6546-4F2D-B10A-BE40CDCC896C\\\'  and id in(\\\'F7BE2FD1-844E-4BD8-8173-7F617C905DAB\\\',\\\'EA544B81-2C29-4103-B689-BDB64F0C790D\\\')  order by version desc{code}EA544B81-2C29-4103-B689-BDB64F0C790DF7BE2FD1-844E-4BD8-8173-7F617C905DAB!image-2023-04-13-12-24-09-804.png!!image-2023-04-13-12-37-39-400!""\', ""Comment 9: \'185/4/2023 should be in ERP"", ""Comment 10: RCA will be needed to determine the cause of a recurring problem.Please confirm to create one.\']""]\nRelated Issues:\n[\'DGS-8788\', \'DGS-8962\']\n\n### End'}"
97,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8935\n\n### Instruction:\npleae check on 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: \'Sprawdzaliśmy wydruk. Poprawki wprowadzone. [~marcin.block@kotrak.com] jeszczem miał rozmawiać aby sobie Eric wgrał brakujące funkcje.\'"", ""Comment 4: \'Could you please verify"", ""Comment 5: it should be fine now.\'"", ""Comment 6: \'Przekazałem wczoraj Ericowi"", ""Comment 7: że brakowało procedury i funkcji. I zmieniliśmy konfigurację w aplikacji.\'"", ""Comment 8: \'May we close the task?\'"", ""Comment 9: \'May we close the task?\']""]\nRelated Issues:\n[]\n\n### End'}"
98,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8934\n\n### Instruction:\nW DHC zawisł VT-6797/M\r\nWprowadziłem zmainy w ZS w 1 pozycji ponieważ widac było większa wartosc która przeszła z DHP\r\nZmiany naniesione na zamóieniu w CDN nie przeniosły sie do DHC ( mówa tu o ilości w zmaóieniu ) Dodatkowo od bazy wprowadziłęm inna wartośc na ilosci z zamóienia co nie skutkowało jej zmiana w VT w DHC\r\nZmiana daty realizacji zamóienia rowniez nie zmieniła sie po modyfikacji w CDN\r\nProsba o weryfikacje \n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'!image-2023-04-07-20-49-41-568.png!!image-2023-04-07-20-53-24-676.png!!image-2023-04-07-20-53-52-445.png!\'"", ""Comment 3: \'Proszę o rozwinięcie myśli:W DHC zawisł VT-6797/M. Zawisł czyli co? VT w DHC jest w statusie Ticket Closed.Dodatkowo"", \'Comment 4: zmiana ilości od bazy nie zmieni ilości na innym dokumencie. Rozumiem\', ""Comment 5: że poprawne ilości są w CDN?Data realizacji zamówienia w CDN i w DHC jest taka sama - kwietnia.Jakie są dokładne oczekiwania? Zmiana ilości na VT?Pozdrawiam\'"", ""Comment 6: \'Stwierdzenie zawisło odnosi sie do tego ze VT nie przeszedł z DHC do CDNJAk widac w pozycji 1 w VT widac ze wiecej paszy przyszło z DHP niz jest to na zamóieniu w CDN stad tez była proba zmiany ilosci na zamowieniu by VT przeszedł z DHC do CDN lecz zmiana tak nie pokazałą sie w DHC i nadal w polu Quantity w Ordersach jest poprzednia wartośc a nie nowa zmieniona w CDN\'"", ""Comment 7: \'Na zamówieniu w DHC jest 23 tony!image-2023-04-07-21-22-14-012.png!W DHP (chyba"", ""Comment 8: że chodzi o pomocniczą)!image-2023-04-07-21-23-58-464.png!W GUI zrealizowana!image-2023-04-07-21-25-27-232.png!\'"", ""Comment 9: \'Na zamówieniu!image-2023-04-07-21-28-43-006.png!Minus niezrealizowane!image-2023-04-07-21-29-15-984.png!\'"", ""Comment 10: \'Proszę o ponowną weryfikację. VT jest generated w DHC czyli wpadlo do CDN. Zarówno w DHC"", \'Comment 11: DHP\', \'Comment 12: CDN i GUI ilość zrealizowana sumarycznie to 23 tony (po ok 11,5 per element)!image-2023-04-07-21-31-11-551.png!W CDN widzimy ilości zamawiane!image-2023-04-07-21-32-37-973.png!Ale jak zmienimy na niezrealizowane\', \'Comment 13: i odejmiemy\', ""Comment 14: wtedy też będą 23 tony!image-2023-04-07-21-33-14-795.png!\'"", ""Comment 15: \'Tak teraz widze ze VT sie wygenerował i że moja zmiana na ilosci w zamowieniu przeszła do DHC z bardzo dużym opoznieniem\'"", ""Comment 16: \'czyli wszystko w porządku i zamykamy? Wygenerował się"", ""Comment 17: bo puściłam synchronizację na zamówieniu.\'"", ""Comment 18: \'Tak . Zgłoszenie do zamkniecia\']""]\nRelated Issues:\n[]\n\n### End'}"
99,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8933\n\n### Instruction:\nExamples for Utrecht. Issue I think is applicable for all plants.\r\n\r\nIn Milas we have issues with stocks, e.g. for item 0048. For this item, corrections for 0041 (-)  and 0048 (+) are sent from PCS. The correction seems to be registered correctly in DHP. \r\nIn export from DHC to WM/ERP for some corrections we see that the signs of the quantities seem to be switched: we see + on 0041 and - on 0048\r\n\r\nExpected: corrections are processed/sent to WM/ERP as received from PCS/DHP\r\nPlease check/fix this issue; we have incorrect bookings and incorrect stocks due to this issue.\r\n\r\nExample correct message from DHC to WM/ERP:\r\n\r\nSTK-3521. Geregistreerd in DHP op 31-03-2023 23:59\r\n\r\n2023-03-31 23:59:02,932 [79] INFO\xa0 WcfSendRequestLogger [C:\\Projects\\evolution.dhcerpservice\\Evolution.DHCERPService\\Evolution.DHCERPService.Service\\Logging\\LoggingInspectorBehavior.cs:53] -\xa0\r\nRequest:<s:Envelope xmlns:s=""http://schemas.xmlsoap.org/soap/envelope/"">\r\n<s:Header>\r\n<Action s:mustUnderstand=""1"" xmlns=""http://schemas.microsoft.com/ws/2005/05/addressing/none"">unit01_dhc_adapter_ws_provider_wsd_webMethods_DHC_Provider_Binder_insertStockCorrection</Action>\r\n</s:Header>\r\n<s:Body xmlns:xsi=""http://www.w3.org/2001/XMLSchema-instance"" xmlns:xsd=""http://www.w3.org/2001/XMLSchema"">\r\n<insertStockCorrection xmlns=""http://deheus.com/unit01/DHC"">\r\n<input xmlns="""">\r\n<header>\r\n<ReceivingSystem>Milas</ReceivingSystem>\r\n<SendingSystem>DHC</SendingSystem>\r\n<CreateDate>2023-03-31T23:58:59.48</CreateDate>\r\n<CreateUser>DHPlant</CreateUser>\r\n<MessageID>7765e48e-5b6f-440d-adb8-ec2e3d9dd090</MessageID>\r\n</header>\r\n<StockCorrections>\r\n<ItemCode>0048</ItemCode>\r\n<CorrectionQTY>-3079.642</CorrectionQTY>\r\n<CorrectionQTYUOM>KG</CorrectionQTYUOM>\r\n<CorrectionDate>2023-03-31T23:58:26</CorrectionDate>\r\n<Plant>7</Plant>\r\n<ReasonCode>ChangeArticleCodeTransfer-D019</ReasonCode>\r\n<Description xsi:nil=""true"" />\r\n</StockCorrections>\r\n<StockCorrections>\r\n<ItemCode>0041</ItemCode>\r\n<CorrectionQTY>3079.642</CorrectionQTY>\r\n<CorrectionQTYUOM>KG</CorrectionQTYUOM>\r\n<CorrectionDate>2023-03-31T23:58:27</CorrectionDate>\r\n<Plant>7</Plant>\r\n<ReasonCode>ChangeArticleCodeTransfer-D019</ReasonCode>\r\n<Description xsi:nil=""true"" />\r\n</StockCorrections>\r\n</input>\r\n</insertStockCorrection>\r\n</s:Body>\r\n</s:Envelope>\r\n\r\nExample incorrect message from DHC to WM/ERP:\r\n\r\nSTK-3460, registered in DHP on 31-03-2023 14:29\r\nIn DHP: RM-for 0041 and RM+ for 0048\r\n\xa0\r\nOnly message I found from DHC to WM/ERP was sent at 16:42 and signs of the corrections are switched.\r\n\xa0\r\n2023-03-31 16:42:42,421 [75] INFO\xa0 WcfSendRequestLogger [C:\\Projects\\evolution.dhcerpservice\\Evolution.DHCERPService\\Evolution.DHCERPService.Service\\Logging\\LoggingInspectorBehavior.cs:53] -\xa0\r\nRequest:<s:Envelope xmlns:s=""http://schemas.xmlsoap.org/soap/envelope/"">\r\n<s:Header>\r\n<Action s:mustUnderstand=""1"" xmlns=""http://schemas.microsoft.com/ws/2005/05/addressing/none"">unit01_dhc_adapter_ws_provider_wsd_webMethods_DHC_Provider_Binder_insertStockCorrection</Action>\r\n</s:Header>\r\n<s:Body xmlns:xsi=""http://www.w3.org/2001/XMLSchema-instance"" xmlns:xsd=""http://www.w3.org/2001/XMLSchema"">\r\n<insertStockCorrection xmlns=""http://deheus.com/unit01/DHC"">\r\n<input xmlns="""">\r\n<header>\r\n<ReceivingSystem>Milas</ReceivingSystem>\r\n<SendingSystem>DHC</SendingSystem>\r\n<CreateDate>2023-03-31T14:25:51.127</CreateDate>\r\n<CreateUser>DHPlant</CreateUser>\r\n<MessageID>7abefab6-5cb4-485f-ace0-d7d029c7a885</MessageID>\r\n</header>\r\n<StockCorrections>\r\n<ItemCode>0041</ItemCode>\r\n<CorrectionQTY>17261.749</CorrectionQTY>\r\n<CorrectionQTYUOM>KG</CorrectionQTYUOM>\r\n<CorrectionDate>2023-03-31T14:25:26</CorrectionDate>\r\n<Plant>7</Plant>\r\n<ReasonCode>ChangeArticleCodeTransfer-D019</ReasonCode>\r\n<Description xsi:nil=""true"" />\r\n</StockCorrections>\r\n<StockCorrections>\r\n<ItemCode>0048</ItemCode>\r\n<CorrectionQTY>-17261.749</CorrectionQTY>\r\n<CorrectionQTYUOM>KG</CorrectionQTYUOM>\r\n<CorrectionDate>2023-03-31T14:25:26</CorrectionDate>\r\n<Plant>7</Plant>\r\n<ReasonCode>ChangeArticleCodeTransfer-D019</ReasonCode>\r\n<Description xsi:nil=""true"" />\r\n</StockCorrections>\r\n</input>\r\n</insertStockCorrection>\r\n</s:Body>\r\n</s:Envelope>\r\n\r\nExpected: same corrections as received from PCS/registered in DHP.\r\n\r\nNote: we do have additional technology defined for changing 0041 to 0048. But that must not change any correction bookings from PCS/DHP to WM/ERP.\n\n### Response:\n[""Comment 1: [\'!image!!image-1!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 3: ""{code:java}/****** Script for SelectTopNRows command from SSMS  ******/SELECT s.Document,i.Code,se.QuantityAfter-se.QuantityBefore,s.SettledDate,s.*  FROM [DHPlantStockBusinessLogicMain].[dbo].[StocktakingElements] se  inner join dbo.Items i on i.id=se.ItemId inner join  [DHPlantStockBusinessLogicMain].[dbo].[Stocktakings] s on s.id=se.Id  where s.Document like \\\'%STK-3521%\\\'  or s.Document like \\\'%STK-3460%\\\'{code} !screenshot-1! !image-2023-04-11-12-52-16-034!!image-2023-04-11-12-53-10-859! !image-2023-04-11-12-53-23-748!""\', \'Comment 4: ""{code:java}SELECT TOP (1000) [Id]      ,[No]      ,[DeliveryId]      ,[ItemId]      ,[CorrectionDate]      ,[Description]      ,[Quantity]      ,[QuantityUnit]      ,[ReasonCode]  FROM [DHPlantStockBusinessLogicMain].[dbo].[StockCorrectionElements] where id in(  SELECT [Id]     FROM [DHPlantStockBusinessLogicMain].[dbo].[StockCorrections]  where StocktakingId in(\\\'31505044-A633-4064-A852-E8AE67A66B30\\\',\\\'50117CBD-7F7F-45B9-A12D-8011D54547F2\\\'))select * from dbo.Itemswhere Id in(\\\'E6537639-D413-4EC7-AB70-F9D2469E71B1\\\',\\\'84BCB9B4-A989-49A0-B8D1-0DBE864D19A0\\\'  ){code}{code:java}SELECT TOP (1000) [PlantId]      ,[PlantIdNo]      ,[LongId]      ,[StringId]      ,[GuidId]  FROM [DHPlantIntegrationDhcServiceIdentityMapping].[dbo].[StockCorrectionIdentityMappings]  where plantid in(\\\'9D131D34-E7A7-4932-9B2B-6889E88E4AF2\\\',\\\'EBB34212-D1AC-437C-A0ED-12E477ABECCC\\\'){code}{code:java}SELECT s.*,i.Code  FROM [DHCService_NL_AS400_PROD].[dbo].[StockCorrectionElements] s  join dbo.items i on i.id=s.ItemId  where s.ExternalId in(\\\'7581\\\',\\\'7582\\\',\\\'7583\\\',\\\'7446\\\',\\\'7447\\\',\\\'7448\\\') and s.StockCorrectionId in(\\\'7C27CC46-647F-4D4E-867E-F5DF96F875A0\\\',\\\'7765E48E-5B6F-440D-ADB8-EC2E3D9DD090\\\'){code}jest jak w plancie: !screenshot-2! !image-2023-04-12-15-00-58-303!""\', ""Comment 5: \'ten STK w dhcservice jest jak w plancie jeden jest poprawny drugi na odwrót.\\\\r\\\\rProśba o pomoc w analizie"", ""Comment 6: jakby co to jestem do dyspozycji.\'"", ""Comment 7: \'Do you have an update on this issue?\'"", ""Comment 8: \'Do you have an update for this issue? We need correct sign in stock corrections in ERP.\'"", ""Comment 9: \'[~BKennedy@deheus.com]this is the only case or do you have other examples?\']""]\nRelated Issues:\n[]\n\n### End'}"
100,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8932\n\n### Instruction:\nOrder SOBE000019659 is planned for today but doesn\'t arrive from DHP into PCS. Could you see what is wrong with it?\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'!image-2023-04-07-12-22-50-720.png!\'"", ""Comment 3: \'Could you please verify with you pcs provider"", ""Comment 4: we may see that order was exported today about11:13:18.\'"", ""Comment 5: \'The problems for this particular order seems to be at the pcs provider indeed. Thanks for your assistance"", ""Comment 6: ticket can be closed\']""]\nRelated Issues:\n[]\n\n### End'}"
101,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8931\n\n### Instruction:\nHi.\r\nPleas help to check VT-12571/23 was closed without releasing stock .\r\n\n\n### Response:\n[""Comment 1: [\'!image!!image-1!!image-2!\'"", \'Comment 2: ""Hi 1. Checking at the database level\', \'Comment 3: we found that the system allowed VT-12571/23 to pick lot 43710060423004 even though this lot had just been created ,not confirmed. 2.  PLR 43710060423004 has been completed after VT-12571/23 execution and the quantity after completion is less than during creation. That\\\'s why the system is reserving a quantity in excess of the on-hand quantity?3. So. How to fix this case ?!image-3!""\', ""Comment 4: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 5: \'vt. zamkniety o 17-21 !image-2023-04-07-14-32-37-501.png!\'"", \'Comment 6: ""select * FROM [DHPlantVCBusinessLogicEvents].[dbo].[VehicleTickets] where AggregateId=\\\'ef4b4acd-ec15-45f0-8d01-c6f9e16e2900\\\' and eventtype like \\\'%close%\\\'!image-2023-04-07-14-36-34-408.png!""\', ""Comment 7: \'blad z czasu !image-2023-04-07-14-46-02-234.png!\'"", \'Comment 8: ""select* FROM [DHPlantStockBusinessLogicEvents].[dbo].[Deliveries] where AggregateId=\\\'5BCEDD86-2FFA-44A2-8E11-8284316F3219\\\'jest 2 razy event change id na deliwery raz na 10000 raz na 9921 ta róznica to 79.user który confirmowal mniejsza ilosc teżTAJINYKO- to on mogl to zrobić!image-2023-04-07-15-00-43-553.png!""\', ""Comment 9: \'If the PLR was created manually and by PCS then the system allows its use before approval. This is not an error. As for the resource for the given code you can try to make an inventory. Please let me know if these infirmations are sufficient?\']""]\nRelated Issues:\n[]\n\n### End'}"
102,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8930\n\n### Instruction:\nDear All,\r\n\r\nWe have issues on both the interfaces recipe and ingredients.\r\n\r\n1. Recipe interface\r\nThe recipe was originally sent and an error occurred - see attachment imagine\r\nI corrected the data in DHH but xml does not want to integrate and repeats the error. In the meantime, the new versions of recipes (6 and 7) were sent see Imagine 1.\r\n\r\n2. ingredient interface\r\nWe also had a whole-day issue with the ingredient interface. We cleaned the Kotrak tables a few times but the error repeated. I think it might be related to the recipe interface issue - see image 5\r\n\r\nCan you please help? For is it is PRIO 1\r\n\r\nKind regards,\r\nDiana Cielecka\r\nmobile +31 615 280 243\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!!image-1!!image-2!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \' !screenshot-1! \'"", ""Comment 4: \'Integration with Spain and Portugal sent the Pricelist to DHH in a loop"", ""Comment 5: which resulted in a large queue.As a result all messages except recipes and labels were delayed.We have stopped communication with Spain and Portugal. Clearing messages allowed others messages to be processed.Will provide information when all will be processed.\'"", ""Comment 6: \'Sprawdzanie kolejki.{code:java}select count(1) from DHHolding with (nolock){code}\'"", ""Comment 7: \'Spain and Portugal jeśli chodzi o te kraje Przemek zgłosił aby ze ogarnęli.\'"", ""Comment 8: \'!image-2023-04-06-20-15-38-793.png!\'"", ""Comment 9: \'Hi,Message queues are empty now. Please"", ""Comment 10: verify.Regards\'"", ""Comment 11: \'Everything works fine. Thank you very much. Great job!\']""]\nRelated Issues:\n[]\n\n### End'}"
103,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8929\n\n### Instruction:\nCould you please fix this ASAP?\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 2: ""Roles forArthur van der Linde has been added to his user in task [https://helpdesk.kotrak.com/servicedesk/customer/portal/56/DGS-8915]Please verify right now if he gets items to Inbox and should be also able to open list of New Items.!image-2023-04-06-16-40-04-940.png!If he need access to others inbox for old items\', \'Comment 3: we can share someone\\\'s inbox to allow him accept New Item Cards.""]\']\nRelated Issues:\n[\'DGS-8915\']\n\n### End'}"
104,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8928\n\n### Instruction:\nVT-89 is filled in from pcs intake, but not closed (that\'s the 1e problem)\r\nNow in this case there was also a wrong quantity send, so an opportunity to adjust, but after adjustment ticket cannot be close, see attached error message: Please close ticket with adjusted weight \n\n### Response:\n[""Comment 1: [\'!afbeelding!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'!afbeelding-1!\'"", ""Comment 4: \'Hi Thomas,I tried to recreate your error but in fact I managed to close VT without any issues. I will verify errors what happened yesterday and let you know.Regards!image-2023-04-07-08-02-50-647.png!\'"", \'Comment 5: \\\'W maintanance{code:java}2023-04-07 08:21:45 (dfa8eb10-811d-4057-81c5-3ae37cc3362b/Plant.Maint.BusinessLogic/DHVD01AP181/5512/94) [Error] Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware - Error during request{  ""scheme"": ""http""\', \'Comment 6:  ""host"": {    ""Value"": ""dhvd01ap181:89""\', \'Comment 7:    ""HasValue"": true\', \'Comment 8:    ""Host"": ""dhvd01ap181""\', \'Comment 9:    ""Port"": 89  }\', \'Comment 10:  ""path"": ""/api/intercontext/vc/errors""\', \'Comment 11:  ""queryString"": []\', \'Comment 12:  ""requestBody"": ""{\\\\\\\\""sortedColumns\\\\\\\\"":[{\\\\\\\\""columnName\\\\\\\\"":\\\\\\\\""createDate\\\\\\\\"",\\\\\\\\""order\\\\\\\\"":2}],\\\\\\\\""pagingViewModel\\\\\\\\"":{\\\\\\\\""pageSize\\\\\\\\"":25,\\\\\\\\""pageNumber\\\\\\\\"":1},\\\\\\\\""summaryColumns\\\\\\\\"":[],\\\\\\\\""createDate\\\\\\\\"":{\\\\\\\\""rangeStart\\\\\\\\"":null,\\\\\\\\""rangeEnd\\\\\\\\"":null}}""}.AutoMapper.AutoMapperMappingException: Error mapping types.Mapping types:PaginatedResultDto`1 -> ErrorPaginatedListViewModelKotrak.Common.Application.Dtos.PaginatedResultDto`1[[Plant.Maint.BusinessLogic.Application.Interfaces.Intercontext.ErrorListDto\', \'Comment 13: Plant.Maint.BusinessLogic.Application.Interfaces\', \'Comment 14: Version=8.5.0.0\', \'Comment 15: Culture=neutral\', \'Comment 16: PublicKeyToken=null]] -> Plant.Maint.BusinessLogic.Infrastructure.Api.ViewModels.Intercontext.ErrorPaginatedListViewModelType Map configuration:PaginatedResultDto`1 -> ErrorPaginatedListViewModelKotrak.Common.Application.Dtos.PaginatedResultDto`1[[Plant.Maint.BusinessLogic.Application.Interfaces.Intercontext.ErrorListDto\', \'Comment 17: Plant.Maint.BusinessLogic.Application.Interfaces\', \'Comment 18: Version=8.5.0.0\', \'Comment 19: Culture=neutral\', ""Comment 20: PublicKeyToken=null]] -> Plant.Maint.BusinessLogic.Infrastructure.Api.ViewModels.Intercontext.ErrorPaginatedListViewModelDestination Member:ItemViewModels ---> AutoMapper.AutoMapperMappingException: Error mapping types.Mapping types:ErrorListDto -> ErrorListViewModelPlant.Maint.BusinessLogic.Application.Interfaces.Intercontext.ErrorListDto -> Plant.Maint.BusinessLogic.Infrastructure.Api.ViewModels.Intercontext.ErrorListViewModelType Map configuration:ErrorListDto -> ErrorListViewModelPlant.Maint.BusinessLogic.Application.Interfaces.Intercontext.ErrorListDto -> Plant.Maint.BusinessLogic.Infrastructure.Api.ViewModels.Intercontext.ErrorListViewModelDestination Member:MessageType ---> System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection. (Parameter \\\\\'startIndex\\\\\')   at System.String.LastIndexOf(Char value"", \'Comment 21: Int32 startIndex\', \'Comment 22: Int32 count)   at Plant.Maint.BusinessLogic.Infrastructure.Api.MappingProfiles.ErrorMessageTypeResolver.Resolve(ErrorListDto source\', \'Comment 23: ErrorListViewModel destination\', \'Comment 24: String member\', \'Comment 25: ResolutionContext context) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\778bbb0f253eec26\\\\\\\\Plant.Maint.BusinessLogic\\\\\\\\Plant.Maint.BusinessLogic.Infrastructure.Api\\\\\\\\MappingProfiles\\\\\\\\ErrorMappingProfile.cs:line 42   at lambda_method99551(Closure \', \'Comment 26: PaginatedResultDto`1 \', \'Comment 27: ErrorPaginatedListViewModel \', \'Comment 28: ResolutionContext )   --- End of inner exception stack trace ---   at lambda_method99551(Closure \', \'Comment 29: PaginatedResultDto`1 \', \'Comment 30: ErrorPaginatedListViewModel \', \'Comment 31: ResolutionContext )   --- End of inner exception stack trace ---   at lambda_method99551(Closure \', \'Comment 32: PaginatedResultDto`1 \', \'Comment 33: ErrorPaginatedListViewModel \', \'Comment 34: ResolutionContext )   at Plant.Maint.BusinessLogic.Infrastructure.Api.Controllers.Intercontext.VcIntercontextController.GetErrorsPaginatedList(ErrorPaginatedListFilterViewModel filterViewModel) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\778bbb0f253eec26\\\\\\\\Plant.Maint.BusinessLogic\\\\\\\\Plant.Maint.BusinessLogic.Infrastructure.Api\\\\\\\\Controllers\\\\\\\\Intercontext\\\\\\\\VcIntercontextController.cs:line 71   at lambda_method99565(Closure \', \'Comment 35: Object \', \'Comment 36: Object[] )   at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor.SyncActionResultExecutor.Execute(IActionResultTypeMapper mapper\', \'Comment 37: ObjectMethodExecutor executor\', \'Comment 38: Object controller\', \'Comment 39: Object[] arguments)   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeActionMethodAsync()   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next\', \'Comment 40: Scope& scope\', \'Comment 41: Object& state\', \'Comment 42: Boolean& isCompleted)   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeNextActionFilterAsync()--- End of stack trace from previous location ---   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Rethrow(ActionExecutedContextSealed context)   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next\', \'Comment 43: Scope& scope\', \'Comment 44: Object& state\', \'Comment 45: Boolean& isCompleted)   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeInnerFilterAsync()--- End of stack trace from previous location ---   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeFilterPipelineAsync>g__Awaited|20_0(ResourceInvoker invoker\', \'Comment 46: Task lastTask\', \'Comment 47: State next\', \'Comment 48: Scope scope\', \'Comment 49: Object state\', \'Comment 50: Boolean isCompleted)   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker\', \'Comment 51: Task task\', \'Comment 52: IDisposable scope)   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker\', \'Comment 53: Task task\', \'Comment 54: IDisposable scope)   at Microsoft.AspNetCore.Routing.EndpointMiddleware.<Invoke>g__AwaitRequestTask|6_0(Endpoint endpoint\', \'Comment 55: Task requestTask\', \'Comment 56: ILogger logger)   at Swashbuckle.AspNetCore.SwaggerUI.SwaggerUIMiddleware.Invoke(HttpContext httpContext)   at Swashbuckle.AspNetCore.Swagger.SwaggerMiddleware.Invoke(HttpContext httpContext\', ""Comment 57: ISwaggerProvider swaggerProvider)   at Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware.Invoke(HttpContext httpContext){code} !image-2023-04-07-08-54-15-338.png!\'"", ""Comment 58: \'!image-2023-04-07-09-26-53-534.png!\'"", ""Comment 59: \'Ostatni error z wczoraj!image-2023-04-07-09-28-03-212.png!\'"", ""Comment 60: \'!image-2023-04-07-09-30-28-631.png!\'"", ""Comment 61: \'W inbound messages czysto"", ""Comment 62: restart servisu i restart pooli nie pomógł\'"", ""Comment 63: \'But it should be corrected to 18000..\'"", \'Comment 64: ""My fault and my mistake I haven\\\'t asked what quantity should be in VT\', \'Comment 65: what quantity is correct. Now the most sensible solution would be correct the stock by stock correction from PCS or opening balance in plant... Would that be possible for you?Regards""\', ""Comment 66: \'Hi,May we close this task?Regards\']""]\nRelated Issues:\n[]\n\n### End'}"
105,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8927\n\n### Instruction:\nAs follow up on DGS-8904:\r\n\r\nI asked the dba of Valid to investigate this. He came back with the following:\r\n\r\n================================================\r\nI’ve checked the DHVD01AG09 instance and found that\r\nthe process in the screenshot is the weekly index maintenance.\r\n\r\nIt seems it was blocked (which is also visible from\r\nthe screenshot) from process with ID 126 which was killed yesterday afternoon:\r\n\r\n\xa0\r\nDate\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\r\n4-4-2023 15:14:34\r\n\r\nLog\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\r\nSQL Server (Current - 5-4-2023 09:45:00)\r\n\r\nSource\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\xa0\r\nspid53\r\n\r\nMessage\r\n\r\nProcess ID 126 was killed by hostname DHVD01DB45, host\r\nprocess ID 7696.\r\n\r\n\xa0\r\nThe index maintenance was blocked during execution of\r\nthe following:\r\n\r\nALTER INDEX [PK_Deliveries] ON [dbo].[Deliveries]\r\nREBUILD WITH (SORT_IN_TEMPDB = OFF, ONLINE = ON, RESUMABLE = OFF)\r\n\xa0\r\n\r\nThe table DHPlantPCSBusinessLogicEvents is 20MB with 4\r\nMB indexes and for some reason this operation was blocked for more than 2 days,\r\nmeaning something else was holding lock on this table.\r\n\r\nIn order to prevent such long running Index maintenance operations\r\ncaused by table locks my proposal is to limit the time for the operation to\r\nwait for a lock to be released to let’s say 5 minutes. And if the lock is still\r\nactive to continue with the next index. \r\n\r\n===================================================\r\n\r\nI think this proposal makes sense. Do you agree? If so, I\'ll ask him to implement this.\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Please be informed that we have forwarded the issue to the development team in order to internal analysis.We are waiting for more details and will be back with further information as soon as possible.\'"", ""Comment 3: \'[~maciej.dobrzanski@kotrak.com]spojrzysz okiem swym? :)\'"", \'Comment 4: ""Hi [~mmeier@deheus.com],We are aware of issues related to the growing Events databases along with their indexes. That is why in agreement with Theo we decided to change the way of maintenance of those databases. We can expect this mechanism to be implemented in the Release 8.7 of the DHP. Since then\', \'Comment 5: both the size of databases and indexes should stop growing so much.Limiting operation time to 5 min is for sure a good idea. We don\\\'t recommend doing any activities related to rebuilding indexes or any other jobs that may affect the performance of the DB server during work time (when a factory is running).""]\']\nRelated Issues:\n[\'DGS-8904\']\n\n### End'}"
106,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8926\n\n### Instruction:\n6_L000175708 has an item in pcs packing, but it should be KG. On the order the packing form is correct, but on trip its false: Can you check reason and inform how to solve?\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!afbeelding!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 3: ""Hi Thomas,Have you resynced anything? The data on a Trip is correct - it\\\'s bulk and kg!image-2023-04-07-07-52-59-978.png!""\', ""Comment 4: \'Oke"", ""Comment 5: I did a resync yes. Ticket can be closed\'"", ""Comment 6: \'Thank you.Regards\']""]\nRelated Issues:\n[]\n\n### End'}"
107,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8925\n\n### Instruction:\nHello,\r\n\r\nPlease assist.\r\n\r\nIO-113/23/KLR is not showing in DHP.\r\n\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Please be informed that we have forwarded the issue to the development team in order to internal analysis.We are waiting for more details and will be back with further information as soon as possible.Regards\'"", ""Comment 3: \'https://helpdesk.kotrak.com/browse/DGS-8924?focusedCommentId=1122121&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-1122121\'"", ""Comment 4: \'Wczoraj był problem z tymi IO:O-56/23/DKDIO-36/23/DKDIO-54/23/DKDIO-58/23/DKDIO-57/23/DKDIO-28/23/DKDIO-59/23/DKDIO-26/23/DKDIO-45/23/DKDIO-55/23/DKDIO-60/23/DKDIO-37/23/DKD list of orders - please check.\'"", ""Comment 5: \'Po upgrade DHC w RPA"", \'Comment 6: dla IO ustawia się flaga isInnerBU\', \'Comment 7: mimo że w DHC nie ma w konfiguracji wpisu odpowiadającego za ustawianie tej flagi. Config ten był robiony pod BR RC task GDC-500.Aktualnie flaga jest zmieniana na bazie DHC. Natomiast jeśli zrobią w ERP update IO\', ""Comment 8: to znów się ustawi flaga na true.\'"", ""Comment 9: \'Please assist IO-133/23/KLR \'"", ""Comment 10: \'done!image-2023-04-06-15-08-44-843.png!\'"", ""Comment 11: \'IO-134/23/KLR\'"", ""Comment 12: \'Hi"", ""Comment 13: done.\'"", ""Comment 14: \'Thanks\'"", ""Comment 15: \'Hello,Please assist IO-28/23/DKD and IO-29/23/DKD are not showing in DHP\'"", ""Comment 16: \'Hi,orders should be in DHP (visible).\'"", \'Comment 17: ""DHC ustawia flagę IsInnerBusinessUnit gdy DestinationWarehouseId i SourceWarehouseId mają wartość i zapytanie:!screenshot-1! zwróci wpisy z jednym BusinessStructuresIddla magazynu \\\'KLD Depot - Klerksdorp\\\' brak wpisu w dbo.ProductionAreaWarehouses i zapytanie zamiast zwrócić dwa rezultaty zwraca jeden.jest 46 magazynów bez przypisanej production area: !screenshot-2! Przypisanie production area rozwiązało by problem.Można również zmienić zapytanie\', \'Comment 18: by uwzględniało magazyny bez przypiętego production area ""\', ""Comment 19: \'trzeba podegrać nową wersję. DHCountry-release-Release-3.0.63-4-202304111336-FTP No configuration.zip na ftp\'"", ""Comment 20: \'hej [~piotr.gaczorek@kotrak.com]przekażesz proszę klientowi rezultat analizy? Michał dodatkowo zmienił zapytanie więc trzeba by ustalić z nimi kiedy możemy podegrać DHC z zmianą tego zapytania (zakładany downtime - 30min(\'"", ""Comment 21: \'[~marek.mamcarz@kotrak.com] między godziną 7-15 ustalić tą lukę na podegranie? i będzie wyłączony DHC wtedy tak?\'"", ""Comment 22: \'Hello"", \'Comment 23: we need to upload a change for DHC.The DHC downtime will then be around 30 minutes.Please let me know when we can make the change between 9 a.m. and 4 p.m.If not today\', ""Comment 24: possibly tomorrow.As to the change will be required due to the fact that most warehouses do not have an assigned production area.Only the ones below: !screenshot-3! \'"", \'Comment 25: ""As per our teams discussion. Noon is the best time but\', ""Comment 26: I\'m happy with any time"", \'Comment 27: as long as we have at least 1 hour notification. ""\', ""Comment 28: \'Hi"", ""Comment 29: the change for DHC has been uploaded.\'"", ""Comment 30: \'Ostatnia poprawa:IO-57/23/KBDIO-56/23/KBDIO-18/23/KBSIO-8/23/KBGIO-53/23/KBDIO-59/23/KBDIO-58/23/KBDIO-54/23/KBDIO-51/23/KBDIO-29/23/DKDIO-28/23/DKDIO-19/23/KBSIO-17/23/MOMIO-6/23/KBGIO-20/23/KBSIO-55/23/KBDIO-52/23/KBD\'"", ""Comment 31: \'Hello.According to the changes for DHC please let me know if the problems still exist for IO?If not"", ""Comment 32: can we close this RCA?\'"", ""Comment 33: \'Hello,Can we keep the ticket open till Friday (21.04.2023)\'"", ""Comment 34: \'Yes"", \'Comment 35: please send me information on Friday\', ""Comment 36: thanks.\'"", ""Comment 37: \'Hello,You may close this ticket\'"", ""Comment 38: \'Hello"", ""Comment 39: thank you.\']""]\nRelated Issues:\n[\'DGS-8924\']\n\n### End'}"
108,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8924\n\n### Instruction:\nHello,\r\n\r\nPlease assist.\r\n\r\nIO-113/23/KLR is not showing in DHP.\r\n\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'[~marek.mamcarz@kotrak.com] [~piotr.chmielarski@kotrak.com]tak jak wspominałem po upgrade DHC w RPA mamy problemy z IO. Aktualizacje na bieżąco robi [~piotr.gaczorek@kotrak.com]Natomiast temat trzeba sprawdzić. Rozumiem że RCA dla [~przemyslaw.przybyszewski@kotrak.com]\'"", ""Comment 3: \'Na razie Wasza procka działa :)\'"", ""Comment 4: \'IO in plant now. Please"", ""Comment 5: verify!image-2023-04-06-11-54-08-385.png!\'"", ""Comment 6: \'RCA task underDGS-8925\'"", ""Comment 7: \'Hello,Please assist IO-28/23/DKD and IO-29/23/DKD are not showing in DHP\'"", ""Comment 8: \'Hi"", ""Comment 9: orders should be in DHP (visible).\'"", ""Comment 10: \'Can you give new cases only to RCA?Can p1 issue be closed?\'"", ""Comment 11: \'DGS-8925 - RCA related was closed. This ticket also has been closed.\']""]\nRelated Issues:\n[\'DGS-8925\']\n\n### End'}"
109,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8923\n\n### Instruction:\nHi\r\n\r\nCan we change the way the ERP calcualtes a customers SO block when over the limit? \r\n\r\nWe would like it to take into account existing confirmed SO\'s + outstanding SI.\r\n\r\nHow & were do we change this?\r\n\r\nRegards\n\n### Response:\n[""Comment 1: [\'https://helpdesk.kotrak.com/servicedesk/customer/portal/56/DGS-7197\'"", ""Comment 2: \'I see from the other ticket how this is done. Can you place this ticket on hold till we test please.\'"", \'Comment 3: ""HiPlease can we put this request back in progress. The configuration doesn\\\'t seem to be working as intended.Regards ""\', ""Comment 4: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 5: ""Thank you...We will need to put the ticket back on hold. I\\\'m getting new stories from the accounts team. I want to do some manual confirmations first to test.""]\']\nRelated Issues:\n[]\n\n### End'}"
110,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8922\n\n### Instruction:\nASN-870/04/2023 does not arrive in DHP\r\n\r\nAlready tried it 3 times to send, even created a whole new contract, in which everything is just right. (supplier is already known to us, has delivered more often and there was no problem)\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!!image-1!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Hello"", ""Comment 4: We kindly inform you that wecurrentlyare processing another Priority1 task.We will revert to processing your task as soon as possible.Regards\'"", ""Comment 5: \'we rae back working on Your issue\'"", ""Comment 6: \'!image-2023-04-06-11-46-13-432.png!\'"", \'Comment 7: \\\'The UPDATE statement conflicted with the FOREIGN KEY constraint ""FK_dbo.Orders_dbo.Addresses_MainBusinessPartnerAddressId"". The conflict occurred in database ""Evolution_DHCountry""\', \'Comment 8: table ""dbo.Addresses""\', ""Comment 9: column \\\\\'Id\\\\\'.The statement has been terminated.\'"", \'Comment 10: ""select * from AddressSyncs where dhcid in (\\\'3190D73A-D136-4D77-8C0D-A3635E32E7D5\\\',\\\'E3FAFAA8-3C17-4848-AEB1-8CF13C496DF4\\\') or xlid=3296!image-2023-04-06-12-28-28-199.png!""\', \'Comment 11: ""The problem was the changed address on the order on the order used an archived address\', \'Comment 12: which in erpxl had almost identical data to the current one ( screen from the database). On the order I changed the gidnumber of the address to the non-archived one.!image-2023-04-06-12-58-25-920.png!When trying to synchronize the address and the PO itself\', \'Comment 13: it turned out that the person editing the new address\', ""Comment 14: set the wrong country - the prefix PO instead of \'pl\'"", \'Comment 15: which was also corrected. The order went through and the new address went through\', \'Comment 16: but there is still an error about the address on the shipping notice\', \'Comment 17: which does not pass the items.!image-2023-04-06-12-58-47-553.png!I think that in this situation the fastest way is to cancel the order and create a new one on the basis of the already corrected order - please verify whether such an order will synchronize correctly.""\', ""Comment 18: \'Ticket can be closed\']""]\nRelated Issues:\n[]\n\n### End'}"
111,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8921\n\n### Instruction:\n VT-12423/23 can not release for intake\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'{code:java}2023-04-06 15:29:52 (028004eb-4560-44bb-af97-1685aa9f7d11/Plant.VC.BusinessLogic/VNPCT-TS01/32500/211) [Error] Kotrak.Common.Infrastructure.ICommandRunEnvironment - Error during Void Run[ReleaseVehicleTicketIntakeCommand](Plant.VC.BusinessLogic.Application.Interfaces.VehicleTickets.Commands.ReleaseVehicleTicketIntakeCommand) methodSystem.InvalidOperationException: Nullable object must have a value.   at Plant.VC.BusinessLogic.Domain.VehicleTickets.Factories.VehicleTicketDomainEventFactory.CreateVehicleTicketReleasedForIntakeEvent(VehicleTicket vehicleTicket) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\67ba263564c33499\\\\\\\\Plant.VC.BusinessLogic\\\\\\\\Plant.VC.BusinessLogic.Domain\\\\\\\\VehicleTickets\\\\\\\\Factories\\\\\\\\VehicleTicketDomainEventFactory.cs:line 538   at Plant.VC.BusinessLogic.Domain.VehicleTickets.VehicleTicket.ReleaseForIntake(DateTime date) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\67ba263564c33499\\\\\\\\Plant.VC.BusinessLogic\\\\\\\\Plant.VC.BusinessLogic.Domain\\\\\\\\VehicleTickets\\\\\\\\VehicleTicket.cs:line 521   at Plant.VC.BusinessLogic.Application.VehicleTickets.Services.VehicleTicketService.ReleaseVehicleTicketIntake(AggregateId vehicleTicketId"", \'Comment 4: DateTime date) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\67ba263564c33499\\\\\\\\Plant.VC.BusinessLogic\\\\\\\\Plant.VC.BusinessLogic.Application\\\\\\\\VehicleTickets\\\\\\\\Services\\\\\\\\VehicleTicketService.cs:line 194   at Kotrak.Common.Infrastructure.Commands.CommandEnvironment.Run[TCommand](TCommand command)   at Kotrak.Common.Infrastructure.Commands.Decorators.IntercontextEventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command)   at Kotrak.Common.Infrastructure.Commands.Decorators.EventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command)   at Kotrak.Common.Infrastructure.Commands.Decorators.ValidationCommandEnvironmentDecorator.Run[TCommand](TCommand command)   at Castle.DynamicProxy.AbstractInvocation.Proceed()   at Kotrak.Common.Infrastructure.Interceptors.LoggingInterceptor`1.Intercept(IInvocation invocation)2023-04-06 15:29:52 (null/Plant.VC.BusinessLogic/VNPCT-TS01/32500/207) [Error] Serilog.AspNetCore.RequestLoggingMiddleware - HTTP ""POST"" ""/api/VehicleTicket/releaseIntake"" responded 500 in 17.8458 ms{code}a ze stocka{code:java}2023-04-06 14:30:05 (null/Plant.Stock.BusinessLogic/VNPCT-TS01/19396/5) [Error] Kotrak.Common.Infrastructure.ICommandRunEnvironment - Error during Void Run[SynchronizeBusinessPartnerCommand](Plant.Stock.BusinessLogic.Application.Interfaces.BusinessPartners.SynchronizeBusinessPartnerCommand) methodKotrak.Extensions.Validation.Abstractions.ValidationException: Validation failed: -- Business partner name is missing ---> Kotrak.Common.Application.Exceptions.CommandValidationException`1[Plant.Stock.BusinessLogic.Application.Interfaces.BusinessPartners.SynchronizeBusinessPartnerCommand]: Validation failed: -- MissingBusinessPartnerNameMessage   at Kotrak.Common.Infrastructure.Commands.Decorators.ValidationCommandEnvironmentDecorator.Run[TCommand](TCommand command)   at Castle.DynamicProxy.AbstractInvocation.Proceed()   at Kotrak.Common.Infrastructure.Interceptors.LoggingInterceptor`1.Intercept(IInvocation invocation)   --- End of inner exception stack trace ---2023-04-06 14:30:05 (null/Plant.Stock.BusinessLogic/VNPCT-TS01/19396/5) [Error] Kotrak.Integration.IntegrationPluginCommon.IntercontextCommunication.Inbound.InboundIntercontextErrorHandler - Error during handling message of type ""Plant.Integration.Common.PublishedLanguage.BusinessPartnerChangedMessage""\', ""Comment 5: retry no 0Kotrak.Extensions.Validation.Abstractions.ValidationException: Validation failed: -- Business partner name is missing ---> Kotrak.Common.Application.Exceptions.CommandValidationException`1[Plant.Stock.BusinessLogic.Application.Interfaces.BusinessPartners.SynchronizeBusinessPartnerCommand]: Validation failed: -- MissingBusinessPartnerNameMessage   at Kotrak.Common.Infrastructure.Commands.Decorators.ValidationCommandEnvironmentDecorator.Run[TCommand](TCommand command)   at Castle.DynamicProxy.AbstractInvocation.Proceed()   at Kotrak.Common.Infrastructure.Interceptors.LoggingInterceptor`1.Intercept(IInvocation invocation)   at Castle.DynamicProxy.AbstractInvocation.Proceed()   at Kotrak.Common.Infrastructure.Commands.Decorators.HistoryGateDecorator.Dispatch[TCommand](TCommand command)   at Kotrak.Integration.IntegrationPluginCommon.IntercontextCommunication.Inbound.IntercontextInboundHandler`2.Handle(InternalStorageDto message)   --- End of inner exception stack trace ---{code}\'"", ""Comment 6: \'!image-2023-04-06-10-52-20-663.png!\'"", ""Comment 7: \'Please"", ""Comment 8: check now.Regards\'"", \'Comment 9: ""HiWhat\\\'s issue with VT? We have faced this issue a few times before. So how to fix it ?""\', ""Comment 10: \'There was no arrival date here:!image-2023-04-06-11-11-12-056.png|width=1171,height=257!I have updated it with arrival weight date.Can we close this task?Regards\'"", ""Comment 11: \'Yes . Please close this VT.\'"", ""Comment 12: \'Thank you\'"", ""Comment 13: \'more question : Why is arrival date missing here ?\'"", ""Comment 14: \'Hi,We still have RCA task open for this issue underDGS-8281 and will be fixed in 8.6 version of DHPAs soon as we get so information"", ""Comment 15: we will let you know.Regards\']""]\nRelated Issues:\n[\'DGS-8281\']\n\n### End'}"
112,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8920\n\n### Instruction:\nProszę o aktualizację i  cofnięcie anulowania wynagrodzeni Dobrzenieckiej Karoliny z listy E-UM/2023/02/*\r\n\r\nProsba tez o weryfikacje czemu w obecnej wersjii user nie moze tego dokonac od strony aplikacji\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Wypłata została przywrócona"", ""Comment 3: proszę o weryfikację.Wgrano też aktualną funkcję do cofania anulowania.\'"", \'Comment 4: ""Now it\\\'s OkTask to close""]\']\nRelated Issues:\n[]\n\n### End'}"
113,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8919\n\n### Instruction:\nthe attached recipes are not in DHC.\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Recipe is in DHC now"", ""Comment 4: please vervfied!image-2023-04-05-16-01-47-862.png!\'"", ""Comment 5: \'could you please also check the issue with attached list of recipes as all of them are also not in DHC.!image-1!\'"", ""Comment 6: \'We resnd it from the DHH"", ""Comment 7: please check.\'"", ""Comment 8: \'yes"", ""Comment 9: all is in DHC\'"", ""Comment 10: \'Could you please confirm if we can close this task?Regards\'"", ""Comment 11: \'yes"", ""Comment 12: please close this ticket.thank you!\']""]\nRelated Issues:\n[]\n\n### End'}"
114,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8918\n\n### Instruction:\nRecipe 967268 is present in DHC and is accepted, however, it doesn\'t arrive in DHP\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Recipe is in plant now!image-2023-04-05-15-42-00-150.png!\'"", ""Comment 3: \'thank you! Ticket can be closed\']""]\nRelated Issues:\n[]\n\n### End'}"
115,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8917\n\n### Instruction:\nPrzy naliczaniu wynagrodzeń za mc marzec pracownikowi Leszek Daraż, pokazuje się poniższy komunikat.\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Pracownik posiada Zajęcie wynagrodzenia ale nie został dla niego przypisany komornik:. !image-2023-04-05-16-58-10-531.png!\'"", ""Comment 4: \'Could you please confirm if we can close this task?Regards\'"", ""Comment 5: \'Yes\']""]\nRelated Issues:\n[]\n\n### End'}"
116,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8916\n\n### Instruction:\nPotrzebny pilnie (na dzisiaj) wykaz zmian zapisów historycznych ze szczegółami na kontach pracowników.\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Hello,Kindly approve lowering priority of this task to P2 as P1 issues are only those with a critical or a blocking impact on business processes that is production or transport. This seems not to be the case in this issue so we suggest decreasing the issue priority.Regards\'"", ""Comment 4: \'[^DGS-8916.docx]\'"", \'Comment 5: ""In the attachment description of Optima\\\'s functionality and topics to be detailed[^DGS-8916.docx]""\', ""Comment 6: \'We can lower priority to P2. I shared the doc with the user.\'"", \'Comment 7: ""Thank you\', \'Comment 8: I\\\'m waiting for an answer""\', \'Comment 9: \\\'User answer ""Na potrzeby audytu potrzebuje zestawienia zmian ,dokładnie :Dziennik zmian dokonywanych w zbiorze danych podstawowych pracownika (historia zmian „nowy vs stary”).""\\\'\', ""Comment 10: \'Please provide more information as described in the uploaded document\']""]\nRelated Issues:\n[]\n\n### End'}"
117,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8915\n\n### Instruction:\nCould you give Arthur the same rights in the MAS as Rick Reimerink.\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Now he has all roles which has user:Rick ReimerinkRick Reimerink AAPlease verify if he can do all needed operations.\'"", ""Comment 3: \'His inbox is still empty. He should have the same things as Rick Reimerink AA (but then only for MAS"", ""Comment 4: not PAS/OPPAS).\'"", \'Comment 5: ""Last New Item Card has been createt in MAS NL which can be accepted and then created Item card is from 2.02.2023 and then he hasn\\\'t been in process of New Item Cards.I gave him right now access to Rick Reimerink AA access. Arthur should be able to see in inbox all New Item Cards which also have Rick Reimeink.Only what he need to do is to use option \\\'All shared inboxes\\\' to see other users document (in this case only of Rick\\\'s) or direcly choose to which inbox in option \\\'Inboxe owned by user\\\'!image-2023-04-07-13-34-14-887.png!""\', \'Comment 6: ""I wasn\\\'t just talking about New Item Cards. He doesn\\\'t receive any tasks in his Inbox. So no SR\\\'s etc.""\', \'Comment 7: ""Oh\', \'Comment 8: so I deleted this shared inbox of Rick.For SR he should be added to role for this (Rick is not in this role -Slaughtery Report from Kofax users)Now there are users like below. I\\\'ve added Arthur also to this role. He should gets new SR to inbox.Does he need any other documents? He should be able to manually create documents,I see now in his inbox some Financial statement and Purchase Invoice and also Round and Feed sale (last 2 automatically generated to users inboxes).!image-2023-04-07-14-26-13-342.png!""]\']\nRelated Issues:\n[\'DGS-8929\']\n\n### End'}"
118,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8914\n\n### Instruction:\nBardzo proszę o zweryfikowanie poprawności działania środowiska produkcyjnego, pod kątem poprawności działania synchronizacji pomiędzy aplikacjami ERP-DHC-DHP i Integratorów.\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'1. Statusy tras się nie aktualizują w DHC"", \'Comment 3: T-2605/23/D tylko pierwsza zmiana spowodowała zmianę statusu na Anulowany\', \'Comment 4: a pozostałe pozostają już w statusie Potwierdzony2. T-2605/23/D jest nie kompletna w DHP. Brakuje elementów z fabryki pasz ZW-52/03/23/I\', \'Comment 5: zamówienie jest w DHP 3. ZW 52/03/23/I -  są dwa kompletnie różne zamówienia z różnymi elementami\', \'Comment 6: ale z tym samym numerem 4. Jeżeli brakuje Trasy w DHP i na VT są podpięte zamówienia zamiast tras\', ""Comment 7: to w DHC VT nie ma połączenia z ZS np.VT-6185/Ł!image!!image-1!!image-2!!image-3!!image-4!\'"", ""Comment 8: \'Order for unlinked VT /ZW-163/03/23/g and order ZW-52/03/23/I are from 2023-03-27"", \'Comment 9: do we have current examples\', ""Comment 10: e.g. from the last two or three days?\']""]\nRelated Issues:\n[\'DGS-8881\']\n\n### End'}"
119,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8913\n\n### Instruction:\nIf the original document is visible on the round than the credit document should also be visible on the round. \r\n\r\n\xa0\r\n\r\n\xa0\r\n\r\nCPI-M/2023/0200 isn\'t visible on Round\xa0015236/0187/0004\r\n\r\n!image-2023-04-05-10-09-33-789.png!\r\n\r\n\xa0\r\n\r\nIn relation table for this case leading doc is filled in and on the round only invoices without leading doc are displayed.\r\n\r\n\xa0\n\n### Response:\n[\'Comment 1: [""It\\\'s ready to test on Test environment.Changes are described in task [https://helpdesk.kotrak.com/servicedesk/customer/portal/56/DGS-8764]{quote}Changes have been made on TEST environment. You can verify them.In some sectors and sections displaying Credit invoices worked correctly before\', \'Comment 2: we\\\'ve made changes in Expenses sections.Changes that have been made in sectors on documents: * RoundMAS NL expenses sectionLAS expenses sectionNAS expenses sectionVAS expenses section * Financial StatementMAS NL expenses sectionLAS expenses sectionNAS expenses sectionVAS expenses section * Financial Statement printoutsMAS NLLASNASVAS * Saldo to PayMAS NLLASNASVAS{quote}""]\']\nRelated Issues:\n[\'DGS-8764\']\n\n### End'}"
120,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8912\n\n### Instruction:\nPlease cancel the following VT\'s:\r\nVT-36/4/23\r\nVT-38/4/23\r\nVT-185/4/23\r\n\r\nDue to wrong packaging type (pcs) for ASN the VT\'s cannot be cancelled by us. Should be more flexible in my opinion, I corrected the packaging type but VT is not updated and I cannot cancel it\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Hi Thomas,All three VTs are cancelled. Please"", ""Comment 3: verify,Regards\'"", ""Comment 4: \'Thanks"", ""Comment 5: ticket can be closed\']""]\nRelated Issues:\n[]\n\n### End'}"
121,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8911\n\n### Instruction:\nProblem with open and creating VT in DHP.\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'resolved by Mateusz Banaszczyk .\']""]\nRelated Issues:\n[]\n\n### End'}"
122,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8910\n\n### Instruction:\nDear, \r\nI need to link BMX code 0982 with Integra code 10892. I did it in the same way but now it looks different. After selection of ""Base item"", item isn´t seen at left side in ""unliked items""\r\npls look at it.\r\nthx\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'There are two steps of linking - first the base item"", ""Comment 4: then the rest when reopening the linking window.Were there any errors when linking the item for the first time?I had to correct it from the database.Now should be fine.\'"", ""Comment 5: \'It´s okay now.No"", ""Comment 6: it is firt time for longer period when I had problem with linking.\'"", ""Comment 7: \'The question is whether this is an incident"", ""Comment 8: please check in the following days if the problem will repeat for other items linking and send a example.\'"", ""Comment 9: \'Hi"", ""Comment 10: today I have linked item. it was ok.\'"", ""Comment 11: \'Can we close it as an incident?\'"", ""Comment 12: \'Hi"", ""Comment 13: today. another link was created. Everything is okay. you can close the issue.thx\']""]\nRelated Issues:\n[]\n\n### End'}"
123,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8909\n\n### Instruction:\nHi\r\n\r\nWe have this GDC-805 to select Packing Form for ShippingNotice item when creating VT based on Shipping Notice.\r\n\r\nHowever, we are facing an issue, because now the Packing Form for ShippingNotice item is Packed, but DHP is getting the Packing form from Item when creating the VT based on Shipping Notice.\r\n\r\nI integrated a Shipping Notice Trip from ERP to DHP test server, so you can check by yourself this case: CG040192\r\n\r\nCould you please fix that?\r\n\r\nThank you very much!\n\n### Response:\n[""Comment 1: [\'!image!!image-1!!image-2!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Dear Maicon,The DGS project is to raise the incident/issue tickets related to the production environment. In case of introducing new features or modifying existing ones please rise a GDC ticket"", ""Comment 4: for questions or issues on the test environment you can rise a DHITS.Regards\'"", ""Comment 5: \'!image-2023-04-05-14-32-25-042.png!!image-2023-04-05-14-33-41-853.png! !image-2023-04-05-14-32-25-042!!image-2023-04-05-14-33-41-853!\'"", ""Comment 6: \'Plus this is how item is configured in DHC"", ""Comment 7: it is a bulk!image-2023-04-05-14-36-39-044.png!\'"", \'Comment 8: ""Hi [~Aleksandra.Przybylek@kotrak.com]I understand the differences betweem GDC and DGS. I\\\'m sorry if I wasn\\\'t too clear in the description of issue. I thought that mentining the GDC would help the understanding of this issue\', ""Comment 9: but I screwed up. I\'m sorry!*Let me try again:*h4. SCENARIOWe have the ShippingNotice document in DHP!As far as I was informed"", \'Comment 10: when creating the VT\', \'Comment 11: the +Packing form+ in VT will get this information from the ShippingNotice Element.h4. ISSUEWhen creating the VT document based on Shipping Notice\', \'Comment 12: instead of getting the +Packing form+ from Shipping Notice\', \'Comment 13: it is getting the +Packing form+ from the Article card.Could you please help with that?""\', \'Comment 14: ""Hi [~mberbert@deheus.com]That\\\'s not the point. Your scenario and description says about test environment. And on service desk we can only verify issue on Production environment. I understand your scenario. But still\', \'Comment 15: I need example from porduction\', \'Comment 16: otherwise you need to create DHITS to check on test.Best regards :)""\', ""Comment 17: \'HiYou can check *CG041697* in the Production environmentThank you!image-3!\'"", ""Comment 18: \'!image-2023-04-06-09-29-46-904.png! Dla wszystkich itemów packing form = bulk!image-2023-04-06-09-37-04-998.png!!image-2023-04-06-10-15-56-866.png!!image-2023-04-06-10-16-31-716.png!!image-2023-04-06-10-15-56-866! !image-2023-04-06-10-16-31-716!\'"", ""Comment 19: \'21518!image-2023-04-06-09-39-06-364.png!21500!image-2023-04-06-09-38-44-044.png!21533!image-2023-04-06-09-39-31-842.png!21509-MP!image-2023-04-06-09-40-02-948.png!\'"", ""Comment 20: \'HejOlcia [~aleksandra.masternak@kotrak.com]MAciek [~maciej.dobrzanski@kotrak.com]pytanko mam:Berbeć powiada"", \'Comment 21: że jak na SN jest packed\', \'Comment 22: to na VT też powinien być packed\', \'Comment 23: ale:>> item w DHC i DHP jest bulk (wszystkie 4)\', \'Comment 24: czyli zakładam\', \'Comment 25: że w erp też tak jest>> zakładam również\', \'Comment 26: że packing form został na SN zmieniony ręcznie\', \'Comment 27: być może na poziomie erpa>> pytanie: czy przy tworzeniu VT bierze packing form z SN czy jednak z konfiguracji itema?Berbeć podpiera się tym stwierdzeniem:!image-2023-04-06-10-13-28-377.png|width=737,height=177!Ale chyba nie doczytał reszty\', \'Comment 28: i znadinterpretował...Niestety\', \'Comment 29: do tego tripa nie ma VT w systemie\', ""Comment 30: ale z chęcią stworzę if you agree!image-2023-04-06-10-15-11-479.png!\'"", \'Comment 31: \\\'[~aleksandra.przybylek@kotrak.com]Co mają ustawione w konfigu w VC ""Vehicle ticket from shipping notice generation policy""? Może jest tam wybrane itemsettlement zamiast default?Bo generalnie powinno to działać tak:DefaultVehicleTicketFromShippingNoticeGenerationPolicy - patrzy na packing form elementu ASNA\', \'Comment 32: wiec powinien utworzyć pakowane elementy.ItemSettlementTypeVehicleTicketFromShippingNoticeGenerationPolicy - patrzy na settlement type itema\', \'Comment 33: więc jeśli te elementy mają settlement type bulky\', ""Comment 34: to powinien utworzyć bulkowe elementy\'"", ""Comment 35: \'[~aleksandra.masternak@kotrak.com]Mają niby poprawnie:!image-2023-04-06-11-18-51-756.png!Tylko w tym przypadku chyba jedyna metoda weryfikacji"", \'Comment 36: to create VT. Bo ten ASN nie ma jeszcze VT. Więc ewentualnie trzeba wierzyć mu na słowo :PWybacz\', \'Comment 37: że troszku zeszło\', ""Comment 38: P1 z Vietnamu miałam :)\'"", ""Comment 39: \'Hi [~Aleksandra.Przybylek@kotrak.com]Any news from this task?We need to start using the functionality this asap.Thank you\'"", ""Comment 40: \'Aktualnie dla dispatcha działa to w oparciu o settlement type na kartotece towarowej"", ""Comment 41: jesli chca zmiany to musza zrobić GDC.\'"", ""Comment 42: \'Hi Maicon,We have investigated your case. Currently"", \'Comment 43: for dispatch VT\', \'Comment 44: it takes settlement type from item card.If you need a change\', ""Comment 45: please raise a GDC task.Regards\'"", \'Comment 46: ""Hi [~Aleksandra.Przybylek@kotrak.com]I won\\\'t raise a new GDC for that we already have one: GDC-805I received the information in the GDC-805 that this Packing form needs to come in Shipping notices from ERP\', \'Comment 47: now I have new information.Could you please talk with Maciej Dobrzański and Theo Berendsen and check what information is right?Thank you""\', ""Comment 48: \'Hi [~mberbert@deheus.com],As I understand this DGS correctly it refers to the TRIP (ASN for dispatch).The rules for creating vehicle tickets based on ASN differ on whether it is for dispatch or intake. What is more"", \'Comment 49: we have more than one policy for generating Vehicle tickets from shipping notices eg. In the case of ASN intake (packing form and settlement type) are considered and for dispatch only (item settlement type)The request from GDC-805 is in my opinion different. First of all\', \'Comment 50: you mentioned raw materials so that is why we understood it as an ASN for intake\', \'Comment 51: not dispatch. It was described so the user will be able to choose the packing form on the Vehicle Ticket\', ""Comment 52: not on the Shipping notice during the generation of the Vehicle Ticket.I suggest scheduling a meeting with Theo in order to discuss all of the details.\'"", \'Comment 53: ""Hi [~mberbert@deheus.com]Is Maciej\\\'s explanation sufficient for you? Can we close this task?Regards""]\']\nRelated Issues:\n[]\n\n### End'}"
124,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8908\n\n### Instruction:\nwe have problem in recipe scale when element is added by additional techologies, DHC is not adding the scale.\r\n* example: item SUE1605-S25 version 114/1, we added the element ROPBCO12A scale type bag, but in the recipe the field is empty, when integrate to DHP was added automatically the scale macro, and the element is sent for wrong production area when integrate to PCS.\r\n\r\nCould you check why recipe is without scale and fix it the functionality (not only this recipe)?\r\n\r\nThank you\r\n\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!!image-1!!image-2!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 3: "" !screenshot-1! {code:java}2023-04-04 09:42:11,487 [311] DEBUG Evolution.DHCountry.Logging.EventPublisherWithLog4NetTracing [(null)] - Published event [Evolution.DHCountry.Production.ProductionRecipes.Events.ProductionRecipeChangedEvent[ProductionRecipeId=\\\'81ccab2b-0573-44da-827b-cbe2d1baee20\\\']] to publisher [Evolution.Events.EventPublisher] under domain context [d22dcd7d00654c0b96f1d79170665cad]2023-04-04 09:42:12,722 [DefaultQuartzScheduler_QuartzSchedulerThread] DEBUG Quartz.Core.QuartzSchedulerThread [(null)] - Batch acquisition of 0 triggers2023-04-04 09:42:16,648 [330] DEBUG Evolution.DHCountry.Logging.DomainCommandHandlerWithLog4NetTracing [(null)] - Handled command [Evolution.DHCountry.Production.ProductionRecipes.Commands.AcceptProductionRecipeCommand] by command handler [Evolution.DHCountry.Domain.DomainCommandHandlerWithPublishingEvents] under domain context [32a19184cb3c48929b8a3babde1b2592]2023-04-04 09:42:16,723 [330] DEBUG Evolution.DHCountry.Logging.EventPublisherWithLog4NetTracing [(null)] - Published event [Evolution.DHCountry.Production.ProductionRecipes.Events.ProductionRecipeAcceptedEvent[ProductionRecipeId=\\\'81ccab2b-0573-44da-827b-cbe2d1baee20\\\']] to publisher [Evolution.Events.EventPublisher] under domain context [2c2168f4537d4cf6a854dae6c6987f08]{code}{code:java}/****** Script for SelectTopNRows command from SSMS  ******/SELECT *  FROM [Evolution_DHCountry].[dbo].[TechnologyIngredients]  where TechnologyId=\\\'833ED31F-5249-48B0-9A45-20BCF32BAF0D\\\'  SELECT ScaleType,*  FROM [Evolution_DHCountry].[dbo].[Items]  where id=\\\'B45C5C4A-49B3-41E7-AD40-AE65FED4A8EF\\\'------------------------------2023-04-04 09:42:25,642 [183] DEBUG Evolution.DHCountry.Logging.EventPublisherWithLog4NetTracing [(null)] - Published event [Evolution.DHCountry.Production.Technologies.Events.TechnologyGeneratedEvent[TechnologyId=\\\'833ed31f-5249-48b0-9a45-20bcf32baf0d\\\']] to publisher [Evolution.Events.EventPublisher] under domain context [90b7c4d930174e85b8ada49eda5ccf4b]{code}!image-2023-04-11-08-56-20-136!""\', ""Comment 4: \'DHC nie przenosi się Scale type do pozycji technologi jak klient dodaje element z poziomu add.technology. Jak to można zreprodukować? Jest jeszcze coś takiego ale tutaj wygląda że chodzi o planta? DGS-8807\'"", ""Comment 5: \'Na widoku related items ScaleType brane jest z składnika technologii połączonej do production recipe.Jeżeli nie ma technologii"", \'Comment 6: jest generowana.Widzę\', ""Comment 7: że przy dodawaniu packing technologii w AddPackagingTechnologyActivity nie jest przepisywane scaleType !screenshot-2! Wymagana jest zmiana \'"", ""Comment 8: \'Prosił bym aby konsultować wpisywanie DGS reason w przypadku Application Bug"", ""Comment 9: to że user oczekiwał ze aplikacja działa inaczej nie oznacza zaraz że jest to błąd aplikacji.\'"", ""Comment 10: \'[~psilva@deheus.com]this is how the Additional Technology Form was designed. If you would like to change this please contact PO Wijnand van Geerenstein but I also this that change https://helpdesk.kotrak.com/browse/GDC-895will solve this issue.\']""]\nRelated Issues:\n[]\n\n### End'}"
125,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8907\n\n### Instruction:\nOn printout there is verification on document which Round category exist on Invoice, but in this case there is no \'Doc No. Intense\'.\r\n When there is no Intense document on S2P like on screen it\'s treated as a invoice from Slaughtery section.\r\n\r\n\r\n I think in those cases we should always go for “Voer”, because feed deliveries can be missing in Intense (but existing in Milas). Slaughter revenues can never not exist in Intense.\r\n\r\n!https://attachments.office.net/owa/damian.swistek%40kotrak.com/service.svc/s/GetAttachmentThumbnail?id=AAMkADY2ZTAxMzM3LTE0YjctNGI0Ni1hYjIxLWE3MDFjOTVkNmExNwBGAAAAAAA%2FcPjpt4lNRZFonusrO6C9BwA5bA29TyJrQIX6A6F8SkSqAAAAAAEJAAA5bA29TyJrQIX6A6F8SkSqAATcM30IAAABEgAQAI9G%2Bh4R%2FQROh0ZHcQ%2B8g%2Fs%3D&thumbnailType=2&token=eyJhbGciOiJSUzI1NiIsImtpZCI6IkQ4OThGN0RDMjk2ODQ1MDk1RUUwREZGQ0MzODBBOTM5NjUwNDNFNjQiLCJ0eXAiOiJKV1QiLCJ4NXQiOiIySmozM0Nsb1JRbGU0Tl84dzRDcE9XVUVQbVEifQ.eyJvcmlnaW4iOiJodHRwczovL291dGxvb2sub2ZmaWNlLmNvbSIsInVjIjoiNzQ1YWJkOWJmNWUxNGJhMWJkNjE5OTZmNzhmMzQzNGYiLCJzaWduaW5fc3RhdGUiOiJbXCJrbXNpXCJdIiwidmVyIjoiRXhjaGFuZ2UuQ2FsbGJhY2suVjEiLCJhcHBjdHhzZW5kZXIiOiJPd2FEb3dubG9hZEA5OGIwMzVmZi1iMTIxLTQ1OGItYTNmMC0zMjM1NGRiMWI3ODEiLCJpc3NyaW5nIjoiU0lQIiwiYXBwY3R4Ijoie1wibXNleGNocHJvdFwiOlwib3dhXCIsXCJwdWlkXCI6XCIxMTUzNzY1OTMyMzQ4MzE1MTQ3XCIsXCJzY29wZVwiOlwiT3dhRG93bmxvYWRcIixcIm9pZFwiOlwiYjU1MGNmY2EtYjZhYS00NmFkLWFlYjAtZTllNjIyYTMyOTE2XCIsXCJwcmltYXJ5c2lkXCI6XCJTLTEtNS0yMS0zNjk5NTUyNDA4LTIxNDA2MTAxMy0yMzI0NTA4MTctMTMxMDk3OTRcIn0iLCJuYmYiOjE2ODA2MTY3ODEsImV4cCI6MTY4MDYxNzM4MSwiaXNzIjoiMDAwMDAwMDItMDAwMC0wZmYxLWNlMDAtMDAwMDAwMDAwMDAwQDk4YjAzNWZmLWIxMjEtNDU4Yi1hM2YwLTMyMzU0ZGIxYjc4MSIsImF1ZCI6IjAwMDAwMDAyLTAwMDAtMGZmMS1jZTAwLTAwMDAwMDAwMDAwMC9hdHRhY2htZW50cy5vZmZpY2UubmV0QDk4YjAzNWZmLWIxMjEtNDU4Yi1hM2YwLTMyMzU0ZGIxYjc4MSIsImhhcHAiOiJvd2EifQ.RxgLnlWD94h6yCeFLSc0ElebIk2_fYnT0n7Gjm-5oLh8oHzyGA2cAoSGutoOBWYRnM2DhaoniNCNVPoX099BZOB9HRjUjxPDjorUqV6Kh626Om9RcPHMJiYX66yVZLglQukCUY6aNlKSDM9dGAOkJTHcfhBGPiEDnEhbmyy1ssOjfZZO0gCc0FsDSvcsfoifpQ-ilVV5vVK-JPfvLM8D933lpkpL1N5BDFIxox3W7uZk1VVuzXx1ytIpRt8rqOqiKw2xT6uDxP1eDBavZq48bYJNgQ6Li8uYRnVPju-HNLlYMdddEQykRdfQZ3TDbkKEf5O0mMyWnMfJxRPNA4tP-Q&X-OWA-CANARY=GLSHExmL6Eu7znDmDGZ5nxB-2n0VNdsYJ-jRsGybjBBV9mGxDMviQ4OL_y0B6YPZHiU-go2WSF4.&owa=outlook.office.com&scriptVer=20230324008.13&animation=true!\r\n\r\n!https://attachments.office.net/owa/damian.swistek%40kotrak.com/service.svc/s/GetAttachmentThumbnail?id=AAMkADY2ZTAxMzM3LTE0YjctNGI0Ni1hYjIxLWE3MDFjOTVkNmExNwBGAAAAAAA%2FcPjpt4lNRZFonusrO6C9BwA5bA29TyJrQIX6A6F8SkSqAAAAAAEJAAA5bA29TyJrQIX6A6F8SkSqAATcM30IAAABEgAQAHIKh4tjHrZCoo2dB%2FrRHHk%3D&thumbnailType=2&token=eyJhbGciOiJSUzI1NiIsImtpZCI6IkQ4OThGN0RDMjk2ODQ1MDk1RUUwREZGQ0MzODBBOTM5NjUwNDNFNjQiLCJ0eXAiOiJKV1QiLCJ4NXQiOiIySmozM0Nsb1JRbGU0Tl84dzRDcE9XVUVQbVEifQ.eyJvcmlnaW4iOiJodHRwczovL291dGxvb2sub2ZmaWNlLmNvbSIsInVjIjoiNzQ1YWJkOWJmNWUxNGJhMWJkNjE5OTZmNzhmMzQzNGYiLCJzaWduaW5fc3RhdGUiOiJbXCJrbXNpXCJdIiwidmVyIjoiRXhjaGFuZ2UuQ2FsbGJhY2suVjEiLCJhcHBjdHhzZW5kZXIiOiJPd2FEb3dubG9hZEA5OGIwMzVmZi1iMTIxLTQ1OGItYTNmMC0zMjM1NGRiMWI3ODEiLCJpc3NyaW5nIjoiU0lQIiwiYXBwY3R4Ijoie1wibXNleGNocHJvdFwiOlwib3dhXCIsXCJwdWlkXCI6XCIxMTUzNzY1OTMyMzQ4MzE1MTQ3XCIsXCJzY29wZVwiOlwiT3dhRG93bmxvYWRcIixcIm9pZFwiOlwiYjU1MGNmY2EtYjZhYS00NmFkLWFlYjAtZTllNjIyYTMyOTE2XCIsXCJwcmltYXJ5c2lkXCI6XCJTLTEtNS0yMS0zNjk5NTUyNDA4LTIxNDA2MTAxMy0yMzI0NTA4MTctMTMxMDk3OTRcIn0iLCJuYmYiOjE2ODA2MTY3ODEsImV4cCI6MTY4MDYxNzM4MSwiaXNzIjoiMDAwMDAwMDItMDAwMC0wZmYxLWNlMDAtMDAwMDAwMDAwMDAwQDk4YjAzNWZmLWIxMjEtNDU4Yi1hM2YwLTMyMzU0ZGIxYjc4MSIsImF1ZCI6IjAwMDAwMDAyLTAwMDAtMGZmMS1jZTAwLTAwMDAwMDAwMDAwMC9hdHRhY2htZW50cy5vZmZpY2UubmV0QDk4YjAzNWZmLWIxMjEtNDU4Yi1hM2YwLTMyMzU0ZGIxYjc4MSIsImhhcHAiOiJvd2EifQ.RxgLnlWD94h6yCeFLSc0ElebIk2_fYnT0n7Gjm-5oLh8oHzyGA2cAoSGutoOBWYRnM2DhaoniNCNVPoX099BZOB9HRjUjxPDjorUqV6Kh626Om9RcPHMJiYX66yVZLglQukCUY6aNlKSDM9dGAOkJTHcfhBGPiEDnEhbmyy1ssOjfZZO0gCc0FsDSvcsfoifpQ-ilVV5vVK-JPfvLM8D933lpkpL1N5BDFIxox3W7uZk1VVuzXx1ytIpRt8rqOqiKw2xT6uDxP1eDBavZq48bYJNgQ6Li8uYRnVPju-HNLlYMdddEQykRdfQZ3TDbkKEf5O0mMyWnMfJxRPNA4tP-Q&X-OWA-CANARY=1mI5yJ-jBEuBYBZ0G7hUesA1F1cVNdsYKjzn0au9aJcB07w9uuqnY6Elc3kjLAOeLl8vEy_44pU.&owa=outlook.office.com&scriptVer=20230324008.13&animation=true!\r\n\r\n\xa0\r\n\r\n\xa0\n\n### Response:\n[\'Comment 1: [\\\'[~mbovene@deheus.com],we\\\\\\\'ve made changes for empty ""Doc No. Intense"" in S2P new printouts (MAS NL\', ""Comment 2: MAS BE).You can verify it.Best regards,Grzegorz\'"", ""Comment 3: \'Do przeniesienia na Prod!image-2023-04-21-13-30-38-807.png!\'"", \'Comment 4: ""Hi [~mbovene@deheus.com],we\\\'ve moved it to the PROD Intense environment.Best regards,Grzegorz""\', ""Comment 5: \'Can be closed\']""]\nRelated Issues:\n[\'DGS-8326\']\n\n### End'}"
126,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8906\n\n### Instruction:\nOn Round is displayed and in this column for SI Regular and Financed there is displayed Delivery date from Leading doc - Purchasae Invoice where Delivery date is 6.12.2022\r\n\r\n!https://attachments.office.net/owa/damian.swistek%40kotrak.com/service.svc/s/GetAttachmentThumbnail?id=AAMkADY2ZTAxMzM3LTE0YjctNGI0Ni1hYjIxLWE3MDFjOTVkNmExNwBGAAAAAAA%2FcPjpt4lNRZFonusrO6C9BwA5bA29TyJrQIX6A6F8SkSqAAAAAAEMAAA5bA29TyJrQIX6A6F8SkSqAATeOusYAAABEgAQAIpBwolwUt5Kp9labJwZCpM%3D&thumbnailType=2&token=eyJhbGciOiJSUzI1NiIsImtpZCI6IkQ4OThGN0RDMjk2ODQ1MDk1RUUwREZGQ0MzODBBOTM5NjUwNDNFNjQiLCJ0eXAiOiJKV1QiLCJ4NXQiOiIySmozM0Nsb1JRbGU0Tl84dzRDcE9XVUVQbVEifQ.eyJvcmlnaW4iOiJodHRwczovL291dGxvb2sub2ZmaWNlLmNvbSIsInVjIjoiNzQ1YWJkOWJmNWUxNGJhMWJkNjE5OTZmNzhmMzQzNGYiLCJzaWduaW5fc3RhdGUiOiJbXCJrbXNpXCJdIiwidmVyIjoiRXhjaGFuZ2UuQ2FsbGJhY2suVjEiLCJhcHBjdHhzZW5kZXIiOiJPd2FEb3dubG9hZEA5OGIwMzVmZi1iMTIxLTQ1OGItYTNmMC0zMjM1NGRiMWI3ODEiLCJpc3NyaW5nIjoiU0lQIiwiYXBwY3R4Ijoie1wibXNleGNocHJvdFwiOlwib3dhXCIsXCJwdWlkXCI6XCIxMTUzNzY1OTMyMzQ4MzE1MTQ3XCIsXCJzY29wZVwiOlwiT3dhRG93bmxvYWRcIixcIm9pZFwiOlwiYjU1MGNmY2EtYjZhYS00NmFkLWFlYjAtZTllNjIyYTMyOTE2XCIsXCJwcmltYXJ5c2lkXCI6XCJTLTEtNS0yMS0zNjk5NTUyNDA4LTIxNDA2MTAxMy0yMzI0NTA4MTctMTMxMDk3OTRcIn0iLCJuYmYiOjE2ODA2MTY3ODEsImV4cCI6MTY4MDYxNzM4MSwiaXNzIjoiMDAwMDAwMDItMDAwMC0wZmYxLWNlMDAtMDAwMDAwMDAwMDAwQDk4YjAzNWZmLWIxMjEtNDU4Yi1hM2YwLTMyMzU0ZGIxYjc4MSIsImF1ZCI6IjAwMDAwMDAyLTAwMDAtMGZmMS1jZTAwLTAwMDAwMDAwMDAwMC9hdHRhY2htZW50cy5vZmZpY2UubmV0QDk4YjAzNWZmLWIxMjEtNDU4Yi1hM2YwLTMyMzU0ZGIxYjc4MSIsImhhcHAiOiJvd2EifQ.RxgLnlWD94h6yCeFLSc0ElebIk2_fYnT0n7Gjm-5oLh8oHzyGA2cAoSGutoOBWYRnM2DhaoniNCNVPoX099BZOB9HRjUjxPDjorUqV6Kh626Om9RcPHMJiYX66yVZLglQukCUY6aNlKSDM9dGAOkJTHcfhBGPiEDnEhbmyy1ssOjfZZO0gCc0FsDSvcsfoifpQ-ilVV5vVK-JPfvLM8D933lpkpL1N5BDFIxox3W7uZk1VVuzXx1ytIpRt8rqOqiKw2xT6uDxP1eDBavZq48bYJNgQ6Li8uYRnVPju-HNLlYMdddEQykRdfQZ3TDbkKEf5O0mMyWnMfJxRPNA4tP-Q&X-OWA-CANARY=y6c3QNbRokWcBtjbMC8OwkCPftcUNdsYXm6OfBQhJ-droiov8sMRjvX3fVB2LsdtmZ3VP1Y1aCU.&owa=outlook.office.com&scriptVer=20230324008.13&animation=true!\r\n\r\n\xa0\r\n\r\n\xa0\r\n\r\n!image-2023-04-04-15-59-22-635.png!\n\n### Response:\n[\'Comment 1: [""Do zmiany wyświetlanie \\\'Delivery date\\\' dla SI Regular i SI Financed. Powinna być wyświetlana Delivery date z dokumentu SI\', \'Comment 2: a nie z PI\', \'Comment 3: który jest Leading doc.""\', ""Comment 4: \'Changed on production and test database.\'"", ""Comment 5: \'Can be closed\']""]\nRelated Issues:\n[]\n\n### End'}"
127,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8905\n\n### Instruction:\nSee attached screenshot, the \'unsupported VT close direction\' error is new for me: Can you please check and solve, and advice how to prevent this next time?\r\n\r\nVT-1916/3/23\n\n### Response:\n[""Comment 1: [\'!afbeelding!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Hi"", \'Comment 4: I have now information about missing stock\', ""Comment 5: can you please check again? !screenshot-1! \'"", ""Comment 6: \'After adding stock"", ""Comment 7: I get the same message: !afbeelding-1!\'"", \'Comment 8: \\\'{code:java}2023-04-17 08:53:36 (a4569f8e-3213-4200-832c-88063fcc7253/Plant.VC.BusinessLogic/DHVD01AP183/23516/12) [Error] Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware - Error during request{  ""scheme"": ""http""\', \'Comment 9:  ""host"": {    ""Value"": ""dhvd01ap183:82""\', \'Comment 10:    ""HasValue"": true\', \'Comment 11:    ""Host"": ""dhvd01ap183""\', \'Comment 12:    ""Port"": 82  }\', \'Comment 13:  ""path"": ""/api/VehicleTicket/registerBulkDispatchElementWeightsToVehicleTicket""\', \'Comment 14:  ""queryString"": []\', \'Comment 15:  ""requestBody"": ""{\\\\\\\\""vehicleTicketId\\\\\\\\"":\\\\\\\\""714f3e93-1639-450f-ac66-09ccd9b367b6\\\\\\\\"",\\\\\\\\""elements\\\\\\\\"":[{\\\\\\\\""vehicleTicketNo\\\\\\\\"":12,\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":1360}},{\\\\\\\\""vehicleTicketNo\\\\\\\\"":14,\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":2012}}]}""}.Kotrak.Extensions.Validation.Abstractions.ValidationException: Validation failed: -- Vehicle ticket should be in dispatch in progress -- Vehicle ticket should be in dispatch completed -- Vehicle ticket should be released for dispatch ---> Plant.VC.BusinessLogic.DomainAbstractions.VehicleTickets.VehicleTicketInvalidDispatchOperationException: Validation failed: -- VehicleTicketShouldBeInDispatchInProgressMessage -- VehicleTicketShouldBeInDispatchCompletedMessage -- VehicleTicketShouldBeReleasedForDispatchMessage   at Plant.VC.BusinessLogic.Domain.VehicleTickets.VehicleTicket.PerformBulkDispatchInitialWeighing(Int32 vehicleTicketElementId\', \'Comment 16: Weighing weighing) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\67ba263564c33499\\\\\\\\Plant.VC.BusinessLogic\\\\\\\\Plant.VC.BusinessLogic.Domain\\\\\\\\VehicleTickets\\\\\\\\VehicleTicket.cs:line 947   at Plant.VC.BusinessLogic.Domain.VehicleTickets.Policies.DefaultFeedRecalculationPolicy.RecalculateFeed(VehicleTicket vehicleTicket\', \'Comment 17: ICurrentUserPolicy currentUserPolicy\', \'Comment 18: String weighbridgeId\', \'Comment 19: IEnumerable`1 changedElements) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\67ba263564c33499\\\\\\\\Plant.VC.BusinessLogic\\\\\\\\Plant.VC.BusinessLogic.Domain\\\\\\\\VehicleTickets\\\\\\\\Policies\\\\\\\\DefaultFeedRecalculationPolicy.cs:line 33   at Plant.VC.BusinessLogic.Domain.VehicleTickets.Services.Implementations.RegisterBulkDispatchDomainService.RegisterBulkDispatchWeights(RegisterMultipleBulkDispatchWeightsDomainDataStructure dataStructure) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\67ba263564c33499\\\\\\\\Plant.VC.BusinessLogic\\\\\\\\Plant.VC.BusinessLogic.Domain\\\\\\\\VehicleTickets\\\\\\\\Services\\\\\\\\Implementations\\\\\\\\RegisterBulkDispatchDomainService.cs:line 66   at Plant.VC.BusinessLogic.Application.VehicleTickets.Services.VehicleTicketBulkDispatchService.RegisterBulkDispatchWeights(RegisterMultipleBulkDispatchWeightsDataStructure dataStructure) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\67ba263564c33499\\\\\\\\Plant.VC.BusinessLogic\\\\\\\\Plant.VC.BusinessLogic.Application\\\\\\\\VehicleTickets\\\\\\\\Services\\\\\\\\VehicleTicketBulkDispatchService.cs:line 327   at Plant.VC.BusinessLogic.Application.VehicleTickets.CommandHandlers.RegisterBulkDispatchElementWeightsToVehicleTicketCommandHandler.Handle(RegisterBulkDispatchElementWeightsToVehicleTicketCommand command) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\67ba263564c33499\\\\\\\\Plant.VC.BusinessLogic\\\\\\\\Plant.VC.BusinessLogic.Application\\\\\\\\VehicleTickets\\\\\\\\CommandHandlers\\\\\\\\RegisterBulkDispatchElementWeightsToVehicleTicketCommandHandler.cs:line 29   at Kotrak.Common.Infrastructure.Gate.CommandEnvironment.Run[TCommand](TCommand command)   at Castle.DynamicProxy.AbstractInvocation.Proceed()   at Kotrak.Common.Infrastructure.Interceptors.LoggingInterceptor`1.Intercept(IInvocation invocation)   at Castle.DynamicProxy.AbstractInvocation.Proceed()   at Kotrak.Common.Infrastructure.Gate.Filters.CommandProcessFilter`1.Execute(CommandPipelineContext`1 input)   at Kotrak.Extensions.Pipeline.PredefinedFilters.FilterDecorator`1.Execute(TContext input)   at Kotrak.Extensions.Pipeline.Pipeline`1.Execute(T input)   at Kotrak.Common.Infrastructure.Gate.StandardGate.DispatchCommand[TCommand](TCommand command)   at Plant.VC.BusinessLogic.Infrastructure.Api.Controllers.VehicleTicketController.RegisterBulkDispatchElementWeightsToVehicleTicket(RegisterBulkDispatchElementWeightsToVehicleTicketViewModel viewModel) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\67ba263564c33499\\\\\\\\Plant.VC.BusinessLogic\\\\\\\\Plant.VC.BusinessLogic.Infrastructure.Api\\\\\\\\Controllers\\\\\\\\VehicleTicketController.cs:line 558   at lambda_method20037(Closure \', \'Comment 20: Object \', \'Comment 21: Object[] )   at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor.SyncActionResultExecutor.Execute(IActionResultTypeMapper mapper\', \'Comment 22: ObjectMethodExecutor executor\', \'Comment 23: Object controller\', \'Comment 24: Object[] arguments)   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeActionMethodAsync()   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next\', \'Comment 25: Scope& scope\', \'Comment 26: Object& state\', \'Comment 27: Boolean& isCompleted)   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeNextActionFilterAsync()--- End of stack trace from previous location ---   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Rethrow(ActionExecutedContextSealed context)   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next\', \'Comment 28: Scope& scope\', \'Comment 29: Object& state\', \'Comment 30: Boolean& isCompleted)   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeInnerFilterAsync()--- End of stack trace from previous location ---   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeFilterPipelineAsync>g__Awaited|20_0(ResourceInvoker invoker\', \'Comment 31: Task lastTask\', \'Comment 32: State next\', \'Comment 33: Scope scope\', \'Comment 34: Object state\', \'Comment 35: Boolean isCompleted)   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker\', \'Comment 36: Task task\', \'Comment 37: IDisposable scope)   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker\', \'Comment 38: Task task\', \'Comment 39: IDisposable scope)   at Microsoft.AspNetCore.Routing.EndpointMiddleware.<Invoke>g__AwaitRequestTask|6_0(Endpoint endpoint\', \'Comment 40: Task requestTask\', \'Comment 41: ILogger logger)   at Swashbuckle.AspNetCore.SwaggerUI.SwaggerUIMiddleware.Invoke(HttpContext httpContext)   at Swashbuckle.AspNetCore.Swagger.SwaggerMiddleware.Invoke(HttpContext httpContext\', ""Comment 42: ISwaggerProvider swaggerProvider)   at Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware.Invoke(HttpContext httpContext)   --- End of inner exception stack trace ---{code}!image-2023-04-17-15-48-11-121! !image-2023-04-17-15-48-49-471!!image-2023-04-17-15-49-42-126!!image-2023-04-17-15-58-39-468!\'"", ""Comment 43: \'Hello,The VT status has been corrected from the database and a message about closing the VT has been sent again to WMS. After the changes in version 8.6 the problem should not occur. The theme of the changes is manageable response time between modules.Regards.\'"", ""Comment 44: \'Oke thanks. same problem also applies to \'"", ""Comment 45: \'VT-452/4/23\'"", \'Comment 46: ""{code:java}SELECT v.Status,s.status  FROM [DHPlantVCBusinessLogicMain].[dbo].[VehicleTickets] v   join DHPlantStockBusinessLogicMain.[dbo].[VehicleTickets] son v.id=s.id  where v.DocumentNumber=452 and v.DocumentMonth=4 and v.DocumentYear=2023  select *   FROM [DHPlantStockBusinessLogicMain].[dbo].[StockUnitReleases]  where SourceDocumentId=\\\'abbebe20-b427-4417-b157-5460b44633cd\\\'{code} !image-2023-04-18-15-02-53-873.png!""\', ""Comment 47: \'VT-1916 został poprawiony "", \'Comment 48: zgłosili kolejny gdzie status VT-452/4/23 jest 110 w bazach stock\', \'Comment 49: vc.nie ma już rezerwacji\', ""Comment 50: WO są executed.Jakby co jestem do dyspozycji :).\']""]\nRelated Issues:\n[]\n\n### End'}"
128,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8904\n\n### Instruction:\nVT\'s are send to pcs, without the deliveryID: This is needed for processing in the pcs system: please solve this, intakes cannot be done automatically at this moment.\r\n\r\n2 example VTs:\r\nVT-128/4/23\r\nVT-12/4/23\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!afbeelding!\'"", ""Comment 2: \'VT-127/4/23\'"", ""Comment 3: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 4: \'!image-2023-04-04-13-23-58-332.png!\'"", \'Comment 5: ""select * from VehicleTicketElements where id in (\\\'7C1AAAAD-D0C1-4E3A-9B8E-3D64115FD064\\\',\\\'1714F1F6-47A0-4638-B8C6-5A359D5BDF3F\\\')""\', ""Comment 6: \'w dhc service też brak deliveryid!image-2023-04-04-13-33-26-434.png!\'"", ""Comment 7: \'!image-2023-04-04-13-45-08-274.png!\'"", ""Comment 8: \'wydaje się być powiązane z tymhttps://helpdesk.kotrak.com/browse/DGS-8263\'"", ""Comment 9: \'select * FROM [DHPlantPCSBusinessLogicIntercontext].[dbo].[InboundMessages] where Retries>1jeden problem!image-2023-04-04-13-55-03-837.png!\'"", ""Comment 10: \'!image-2023-04-04-13-57-22-784.png!\'"", \'Comment 11: \\\'uusnieto event wiszacy z 900 retry messageselect * FROM [DHPlantPCSBusinessLogicIntercontext].[dbo].[InboundMessages]{""DeliveryId"":\\\\\\\\{""Id"":""68c0b827-b28f-41c9-aaeb-029e79548330""},""InitialOwnerId"":\\\\\\\\{""Id"":""423c58b5-f3a8-4e9d-817d-63710a86c93e""},""BusinessUnitId"":\\\\\\\\{""Id"":""423c58b5-f3a8-4e9d-817d-63710a86c93e""},""ItemId"":\\\\\\\\{""Id"":""b81ceec3-4ed3-42ba-86f0-4ff700074a3b""},""CreatedDate"":""2023-04-03T06:11:44.2540018+02:00"",""InitialSourceDocument"":\\\\\\\\{""DocumentId"":{""Id"":""3d6bdfad-4d53-47ba-a6d4-a5fa9742de3e""},""DocumentNo"":1,""DocumentNumber"":""VT-17/4/23"",""DocumentTypeValue"":100},""SourceDocument"":\\\\\\\\{""DocumentId"":{""Id"":""3d6bdfad-4d53-47ba-a6d4-a5fa9742de3e""},""DocumentNo"":1,""DocumentNumber"":""VT-17/4/23"",""DocumentTypeValue"":100},""SerialNumber"":null,""ForeignSerialNumber"":null,""InternalSerialNumber"":""VT-17/4/23-1"",""Quantity"":\\\\\\\\{""Unit"":""kg"",""Value"":0.0},""ProducerId"":null,""ExpiryDate"":null,""IsMedicated"":false,""IsBrokenBatch"":false,""UnitLoadId"":null,""BusinessPartners"":[],""OrderElements"":[]}\\\'\', \'Comment 12: ""eventid=id=\\\'303F8B94-E88A-4E01-AC19-97A92FE2754F\\\'""\', ""Comment 13: \'deliveries were not created because the database was locked the following session"", ""Comment 14: looks like a query to create/modify indexes!image-2023-04-04-15-18-42-679.png|width=926,height=196!\'"", \'Comment 15: ""trzeba pilnowac te dostawe :select * FROM [DHPlantPCSBusinessLogicIntercontext].[dbo].[InboundMessages] where Id =\\\'303F8B94-E88A-4E01-AC19-97A92FE2754F\\\'""\', ""Comment 16: \'insert into DHPlantPCSBusinessLogicIntercontext.dbo.InboundMessages(Id"", \'Comment 17: ReceivedAt\', \'Comment 18: Retries\', \'Comment 19: MessageType\', \'Comment 20: Message\', \'Comment 21: ProcessDate\', \'Comment 22: Queue\', \'Comment 23: Metadata\', \'Comment 24: CreatedAt\', \'Comment 25: MetadataType\', \'Comment 26: Priority\', \'Comment 27: PriorityText\', \'Comment 28: Sender\', \'Comment 29: SentAt\', \'Comment 30: Status\', \'Comment 31: StatusText)select d.Id\', \'Comment 32: GETDATE()\', \'Comment 33: 0\', \'Comment 34: d.EventType\', \'Comment 35: d.Event\', \'Comment 36: GETDATE()\', ""Comment 37: \\\\\'Plant.Stock.BusinessLogic.DomainAbstractions\\\\\'"", \'Comment 38: \\\\\\\'\\\\\\\\{""CorrelationId"":{""Id"":""\\\\\\\'+CAST(NEWID() AS NVARCHAR(MAX))+\\\\\\\'""}}\\\\\\\'\', \'Comment 39: GETDATE()\', ""Comment 40: \\\\\'Kotrak.Common.Infrastructure.Integration.IntercontextMessageMetadata"", \'Comment 41: Kotrak.Common.Infrastructure.Integration\', \'Comment 42: Version=6.5.0.0\', \'Comment 43: Culture=neutral\', ""Comment 44: PublicKeyToken=null\\\\\'"", \'Comment 45: 3\', ""Comment 46: \\\\\'Medium\\\\\'"", ""Comment 47: \\\\\'Stock\\\\\'"", \'Comment 48: GETDATE()\', \'Comment 49: 0\', ""Comment 50: \\\\\'Created\\\\\'from DHPlantStockBusinessLogicEvents.dbo.Deliveries d where d.Id = \\\\\'303F8B94-E88A-4E01-AC19-97A92FE2754F\\\\\'\'"", ""Comment 51: \'Any update?\'"", ""Comment 52: \'So it is fixed now?\'"", ""Comment 53: \'Yes"", ""Comment 54: the messages queue has been unlocked and messages have been processed.\'"", ""Comment 55: \'Hi"", \'Comment 56: the problem was caused by unconsulted actions on the datbase (creation of indexes on the previous screenshot) not implemented by us\', ""Comment 57: they caused time-outs that blocked the queue and prevented the generation of stock which caused deliveryid=0 on VT. The name of the login of the db user is visible on the screen shoot.!image-2023-04-05-08-05-48-141.png!\'"", ""Comment 58: \'do you still have problem with deliveryid on this vt"", ""Comment 59: or may we close this task?\'"", \'Comment 60: ""Hi,I asked the dba of Valid to investigate this. He came back with the following:================================================I’ve checked the DHVD01AG09 instance and found thatthe process in the screenshot is the weekly index maintenance.It seems it was blocked (which is also visible fromthe screenshot) from process with ID 126 which was killed yesterday afternoon:Date4-4-2023 15:14:34LogSQL Server (Current - 5-4-2023 09:45:00)Sourcespid53MessageProcess ID 126 was killed by hostname DHVD01DB45\', \'Comment 61: hostprocess ID 7696.The index maintenance was blocked during execution ofthe following:ALTER INDEX [PK_Deliveries] ON [dbo].[Deliveries]REBUILD WITH (SORT_IN_TEMPDB = OFF\', \'Comment 62: ONLINE = ON\', \'Comment 63: RESUMABLE = OFF)The table DHPlantPCSBusinessLogicEvents is 20MB with 4MB indexes and for some reason this operation was blocked for more than 2 days,meaning something else was holding lock on this table.In order to prevent such long running Index maintenance operationscaused by table locks my proposal is to limit the time for the operation towait for a lock to be released to let’s say 5 minutes. And if the lock is stillactive to continue with the next index. ===================================================I think this proposal makes sense. Do you agree? If so\', \'Comment 64: I\\\'ll ask him to implement this.""\', ""Comment 65: \'Hello,In this task we have focused on clearingandunblocking the process.[~mmeier@deheus.com] about the last comment"", \'Comment 66: thank you for all information\', ""Comment 67: please raise another task for this (SR) I will pass this to our developers to verify it.About themain subject of the task can we close it?\'"", ""Comment 68: \'DGS-8927 is created.@Thomas Dankers"", ""Comment 69: do you agree to close this one?\'"", ""Comment 70: \'Yes I agree\'"", ""Comment 71: \'Thank you\']""]\nRelated Issues:\n[\'DGS-8927\']\n\n### End'}"
129,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8903\n\n### Instruction:\nWhen Anja makes a credit invoice from a PI to reverse the SI she must be able to create a SI again.\r\n\r\nShe sees the button but it is not active, so she cannot create a new SI.\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Do sprawdzenia czy w tym przypadku była dostępna akcja spod pioruna do generowania SI.\'"", ""Comment 4: \'Due to the fact that the document was in the archive"", \'Comment 5: the button was inactive\', \'Comment 6: but we got the functionality on the document that when the button is visible\', ""Comment 7: at the same time the action create sales invoice from lightning is active.\'"", ""Comment 8: \'To verify by Anja\']""]\nRelated Issues:\n[]\n\n### End'}"
130,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8902\n\n### Instruction:\nHi, from Wiola\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'[^DGS-8902.docx]\'"", ""Comment 4: \'Description in the attachment[^DGS-8902.docx]^^\'"", ""Comment 5: \'!image-1!\']""]\nRelated Issues:\n[]\n\n### End'}"
131,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8901\n\n### Instruction:\nVT-1214/2/23 contains intake of 0303 from a barge. During intake, a correction was made on this VT. The intake was closed and has status On stock. The correction still has status In Progress and many Lot reports have made a reservation on this line. Due to this, many production reports cannot automatically be confirmed.\r\nCan you \r\n- change the status of this correction to On stock, or \r\n- remove this correction and the reservations that were made on this line?\r\n\r\nso that Lot reports that consume 0303 can be automatically confirmed\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'!image-2023-04-11-15-31-09-412.png!!image-2023-04-11-15-30-54-012.png!\'"", \'Comment 4: \\\'Dla tego ""correction"" barcode:!image-2023-04-11-15-32-35-607.png!!image-2023-04-11-15-34-14-813.png!\\\'\', ""Comment 5: \'Obecnie jest 67 PLRów w statusie Finished!image-2023-04-11-15-34-49-055.png!\'"", ""Comment 6: \'We updated the status of this stock unit. The stock can now automatically be consumed in the lot reports. This ticket can be closd.\'"", ""Comment 7: \'Thank you for your informationRegards\'"", ""Comment 8: \'Dear Bob,If you have another case like that"", ""Comment 9: please let us know via new task. We would like to check why this happened.Regards\']""]\nRelated Issues:\n[]\n\n### End'}"
132,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8900\n\n### Instruction:\nWe are dealing with the following situation. When Farach sends an PI to Nancy and the round number is not correct (see the example in the attachment) than Nancy is not able to select the correct round number.\r\n\r\nWhen she sends it back to entry however Farach is also not able to change the full round number. Both users should be able to do so.\r\n\r\nNote: for SI\'s this is possible at the moment. Could you make it possible for PI\'s as well?\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Do sprawdzenia dla przesłanego przykładu dlaczego nie da się wybrać rundy - sprawdzenie co jest na lookupie w liście wartości i jakie są tam warunki.\'"", \'Comment 4: ""* For Sales invoice documents\', ""Comment 5: we check whether the customer indicated in the \'customer\' field has BP_Category set as Slaughter"", ""Comment 6: we are looking for rounds for the customer indicated in the \'reference\' field. * For Sales invoice"", \'Comment 7: which have customers in other BP_Category as likeSlaughter wejust check active rounds for this customer. * For Purchase invoice documents\', \'Comment 8: we just check active rounds for customers from \\\'Refence\\\' field""\', \'Comment 9: ""[~mbovene@deheus.com]When PI is generated from SI Full round number is copied to PI. Probably you expect that it will be possible to choose rounds from \\\'Supplier\\\'\', ""Comment 10: but it\'s possible right now to choose only rounds from \'Reference\'"", \'Comment 11: not from Supplier.Should we adjust it somehow?""\', ""Comment 12: \'Yes"", \'Comment 13: please make the rounds for the user who is selected as ""Supplier"" available as well.\\\'\', ""Comment 14: \'It has been done in task [https://helpdesk.kotrak.com/servicedesk/customer/portal/56/DGS-9012]Please verify that is possible.\']""]\nRelated Issues:\n[\'DGS-9012\']\n\n### End'}"
133,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8899\n\n### Instruction:\nFor some labels the feeding program section in the XML to MILAS is not populated with feeding programs.\r\n\r\nE.g. item 705900  and item 704922 .\r\nIf you check the most recent label messages that are sent from DHC there should be a feeding program in it. \r\n705900 should contain BE\r\nand the other one a whole list: \r\nBE\r\nQS\r\nVP\r\nVB\r\nVG\r\nCV\r\nVC\r\nDU\r\nDV\r\nBE\r\nQS\r\nVP\r\nVB\r\nVG\r\nCV\r\nVC\r\nDU\r\nDV\r\n\r\nCan you please check why it is not send. Probably this is the case for more labels. Is there a way to find out for which ones it goes wrong and since when?\r\n\r\n\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Wchodząc w Label config np. nie ma BE dla Feeding program -  !screenshot-1! Ale inne już są.!image-2023-04-11-09-53-33-863!\'"", ""Comment 3: \'synchro z MILAS było GDC-719"", \'Comment 4: czy to jest ten zakres zmian? Wchodząc w Label config np. nie ma BE dla Feeding program\', ""Comment 5: ale inne już są.\'"", ""Comment 6: \'label configuration nie ma nic do tego\'"", ""Comment 7: \'niech podadzą dla których fabryk"", ""Comment 8: widzę ze dla jednych fabryk te informacje otrzymujemy z bestmixa a dla innych nie więc pewnie muszą się pokornie udać do działu nutrition.\'"", ""Comment 9: \'Hello"", ""Comment 10: we need an additional information. For which factories is the problem?because for some this information is provided from Bestmix.\']""]\nRelated Issues:\n[]\n\n### End'}"
134,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8898\n\n### Instruction:\nPlant Maasbracht sometimes has big delays in printing of SPS. In those cases plant is using PCS printouts, but that is not desired, because e.g. label information is missing\r\nI tried to analyze the following case:\r\n\r\nSO-12553/3/23\r\ntrip 00999257\r\n2 sales orders: SOBE000018544 (SO-13410/3/23) en SOBE000018362 (SO-12553/3/23)\r\n\r\nVT-2136/3/23 \r\ncreationdate: 29/03/2023 6:34 AM (corresponds to dispatch message received from PCS for order SO-12553/3/23)\r\nclosed: 29/03/2023 6:54 AM (corresponds to dispatch message received from PCS for order SO-13410/3/23)\r\n\r\nGeneration of XML for SPS for both sales orders: 07.25\r\n\r\nSo, the dispatch message from PCS is processed immediately in the VT.\r\nHowever, the XML for Transform is genertated 50 (for first order) -30 (for second order) minutes later!\r\n\r\nWhat can cause these delays? Is the process to close Lot reports/VT\'s (I remember this was the issue in Utrecht)? \r\nHow can we solve this issue? Plant mus be able to deliver correct SPS to the driver directly after dispatch is registered.\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'[~maciej.dobrzanski@kotrak.com]czy mamy jakiś sposób"", ""Comment 3: żeby zbadać przyczynę opóźnień? :)\'"", ""Comment 4: \'Hello,Please be informed that we have forwarded the issue to the development team in order to internal analysis.We are waiting for more details and will be back with further information as soon as possible.Regards\'"", ""Comment 5: \'[~aleksandra.przybylek@kotrak.com] możemy zrobić RCA i zaplanować to analizy\'"", ""Comment 6: \'Hi Bob,We have discussed your task. As you have asked for analysis of the rootcause"", \'Comment 7: due to service process\', \'Comment 8: we need to close this incident and raise RCA task. Please\', ""Comment 9: let us know if you accept RCA task.Regards\'"", ""Comment 10: \'[~aleksandra.przybylek@kotrak.com] to może być też przczyną tych opóźnień:https://helpdesk.kotrak.com/browse/DGS-8904?focusedCommentId=1120975&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-1120975\'"", ""Comment 11: \'Hi Bob,Are you able to tell me if there is anydelay in printing of SPS today? If any delay occurs today"", ""Comment 12: could you please let me know?Regards\'"", ""Comment 13: \'Tak na szybko"", \'Comment 14: inbound czysto:!image-2023-04-05-11-29-55-423.png!Tu też czysto:!image-2023-04-05-11-30-55-006.png!!image-2023-04-05-11-31-40-043.png!Musieliby rzeczywiście dać znać\', \'Comment 15: że tu i teraz jest opóźnienie\', ""Comment 16: a nie tydzień temu ...\'"", ""Comment 17: \'Plant is not reporting every delay directly. I am not able to provide this information. I did not get any further information about delays. This task can be closed.\'"", ""Comment 18: \'Sure. Waiting for new examples and new task then.Regards\']""]\nRelated Issues:\n[]\n\n### End'}"
135,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8897\n\n### Instruction:\nUsers who close S2P documents should have access to inboxes of other users who has linked documents Financial Statement, Round, Feed sale in their inboxes.\r\n\r\nIt\'s related to recent changes in S2P closing: If the user sends S2P to Archive via flow, others documents such as FS, Round and Feed sale will also be in Archived status.\xa0\r\n\r\n\xa0\r\n\r\nExample\xa0SP-M/0706\r\n\r\nS2P has been sent to Archive\r\n\r\nFS has been sent to Archive\r\n\r\nRound hasn\'t been sent to Archive\r\n\r\nFeed sale hasn\'t been sent to Archive.\r\n\r\n\xa0\r\n\r\nRound\r\n!image-2023-04-03-15-17-47-365.png!\r\n\r\nUsers shared inboxes\r\n\r\n!image-2023-04-03-15-18-04-171.png!\r\n\r\n\xa0\r\n\r\n\xa0\n\n### Response:\n[\'Comment 1: [""The solution will be to extend shared inboxes for users who can close S2P\\\'s and give them access to all users who can create Round\', \'Comment 2: Financial Statement\', \'Comment 3: S2P.[~mbovene@deheus.com]do you know which users are closing S2P documents?We can also verify who can process S2Ps and give them access to inboxes ofusers who can create Rounds\', \'Comment 4: Feed sales\', \'Comment 5: Financial statement. If we should do it in that way\', \'Comment 6: please let us know and we can also prepare some analysis to be sure that we don\\\'t want to give access for too many users.""\', ""Comment 7: \'do you know which users are closing S2P documents? -->MAS: Nancy van Dam"", \'Comment 8: Peter Moeiliker\', \'Comment 9: Steffen Driessens\', \'Comment 10: Koen Huiberts,NAS: Bert Geijtenbeek and Christine de JongVAS: Bert GeijtenbeekLAS: Bert GeijtenbeekOPPAS/PAS: Rick Reimerink\', ""Comment 11: Thelma Meijer \'"", ""Comment 12: \'Poniżej wymienieni userzy powinni mieć prawo do udostępnionych inboxów wszystkuich userów"", \'Comment 13: którzy mogą tworzyć Rundy\', \'Comment 14: Feed sale\', \'Comment 15: Financial statement (do sprawdzenia na węzłach dla tych dokumentów\', \'Comment 16: kto może je tworzyć). Bez tego wymienieni userzy nie są w stanie przesłać dokumentów do Archiwum. Przy zamykaniu S2P zamykane są automatycznie powiązane dokument FS\', \'Comment 17: Runda\', \'Comment 18: Feed sale.MAS: Nancy van Dam\', \'Comment 19: Peter Moeiliker\', \'Comment 20: Steffen Driessens\', \'Comment 21: Koen Huiberts,NAS: Bert Geijtenbeek and Christine de JongVAS: Bert GeijtenbeekLAS: Bert GeijtenbeekOPPAS/PAS: Rick Reimerink\', ""Comment 22: Thelma Meijer\'"", ""Comment 23: \'Dwie role obejmują całość-Normal contract administrator-Senior contract administrator\'"", ""Comment 24: \'Dodano na każdym przepływie do archiwum w dokumentach saldo2pay przed wykonaniem flow na innych dokumentach insert na tabele userrelation a po wykonaniu flow jest wykonywany delete na danym użytkowniku.\'"", \'Comment 25: ""Finally to avoid giving rights of many shared inboxes to users we found another solution.When user will perform flow to \\\'Archive\\\' for Saldo 2 Pay document we add for a while permission for shared inboxes users who can perform flows for archiving FS\', \'Comment 26: Round\', \'Comment 27: Feed sale. This rights will be added only when user perform this flow to Archive for S2P document and will be removed at the end of performing flow.In this case flows should be always performed properly and FS\', \'Comment 28: Round\', \'Comment 29: Feed sale should be perform to Archive even if these documents are in other users inboxes.You can verify it on test environment.For this case it should be tested on some user who has rights for performing S2P flow and for example linked FS or Round is in inbox of other users. User who want to archived S2P shouldn\\\'t has rights to inbox of user who has in inbox FS or Round document.""\', ""Comment 30: \'It will be tested internally by Kotrak on IBIP_DH_TEST and after then will be moved to Prod environment.When it will be good and will be no issues in logs in Intense on prod after deployment on Prod we will close the task.\'"", ""Comment 31: \'[~damian.swistek@kotrak.com]do sprawdzenia na IBIP_DH_TEST\'"", ""Comment 32: \'[~tomasz.zygon@kotrak.com]"", \'Comment 33: sprawdziłem na IBIP_DH_TEST i wygląda ok\', ""Comment 34: do przerzucenia na Prod.Po przerzuceniu daj znać w komentarzu i zobaczymy przez jakiś czas czy w logach nie ma już błędów związanych z brakiem uprawnień do przesyłanych tasków.\'"", ""Comment 35: \'Przerzucono na proda jednak tylko w mas be i mas nl wykonują się przepływy dla powiązanych dokumentów w reszcie dodałem to w oczekiwaniu na przeniesienie całościowe rozwiązania z testa\'"", ""Comment 36: \'Moved to prod\']""]\nRelated Issues:\n[\'DGS-8705\']\n\n### End'}"
136,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8896\n\n### Instruction:\nGood morning,\r\n\r\nplease we have got a problem with communication between PCS and DHP on plant Helmond.\r\n\r\nFor example SO-14644/3/23\r\n\r\nIt\'s not processed on DHP.\r\n\r\nCould you have a look at it.\r\n\r\nKind regards,\r\n\r\nGerard Geerts\r\n\r\n\n\n### Response:\n[""Comment 1: [\'Hello,\\\\r\\\\rWe are investigating your issue. We will inform you about the solution as soon as possible.\\\\r\\\\rRegards\\\\r\\\\r\'"", \'Comment 2: \\\'01.04 dla modułu pcs były timeouty i 03.04 też.W logach host dla pcs jest info o braku z order w module pcs.2023-04-03 12:11:55 (40516f78-4f32-487a-9659-9efe1467fe6e/Plant.PCS.BusinessLogic/DHVD01AP203/13480/15) [Error] Microsoft.EntityFrameworkCore.Update - An exception occurred in the database while saving changes for context type \\\\\\\'""Plant.PCS.BusinessLogic.Infrastructure.EF.PcsDbContext""\\\\\\\'.""""""Microsoft.EntityFrameworkCore.DbUpdateException: An error occurred while saving the entity changes. See the inner exception for details. ---> Microsoft.Data.SqlClient.SqlException (0x80131904): The MERGE statement conflicted with the FOREIGN KEY constraint \\\\\\\\""FK_VehicleTicketElements_Orders_OrderId\\\\\\\\"". The conflict occurred in database \\\\\\\\""DHPlantPCSBusinessLogicMain\\\\\\\\""\', \'Comment 3: table \\\\\\\\""dbo.Orders\\\\\\\\""\', ""Comment 4: column \\\\\'Id\\\\\'\'"", ""Comment 5: \'!image-2023-04-04-12-09-21-312.png!\'"", ""Comment 6: \'W module dhc były problemy z deadlockami2023-04-03 07:18:45 (/Plant.DHC.Integration/DHVD01AP203/12848/3) [Error] Kotrak.Common.Infrastructure.Integration.Jobs.InboundProcessJob - Error during inbound processingMicrosoft.Data.SqlClient.SqlException (0x80131904): Transaction (Process ID 158) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. at Microsoft.Data.SqlClient.SqlConnection.OnError(SqlException exception"", \'Comment 7: Boolean breakConnection\', \'Comment 8: Action`1 wrapCloseInAction) at Microsoft.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj\', \'Comment 9: Boolean callerHasConnectionLock\', \'Comment 10: Boolean asyncClose) at Microsoft.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior\', \'Comment 11: SqlCommand cmdHandler\', \'Comment 12: SqlDataReader dataStream\', \'Comment 13: BulkCopySimpleResultSet bulkCopyHandler\', \'Comment 14: TdsParserStateObject stateObj\', \'Comment 15: Boolean& dataReady) at Microsoft.Data.SqlClient.SqlDataReader.TryHasMoreRows(Boolean& moreRows) at Microsoft.Data.SqlClient.SqlDataReader.TryReadInternal(Boolean setTimeout\', ""Comment 16: Boolean& more) at Microsoft.Data.SqlClient.SqlDataReader.Read() at Microsoft.EntityFrameworkCore.Query.Internal.SplitQueryingEnumerable`1.Enumerator.MoveNext() at System.Collections.Generic.LargeArrayBuilder`1.AddRange(IEnumerable`1 items) at System.Collections.Generic.EnumerableHelpers.ToArray[T](IEnumerable`1 source) at Kotrak.Extensions.Communication.InternalStorage.Fetch.InternalStorageInboundFetchService`1.FetchEntities(Int32 packageSize) at Kotrak.Extensions.Communication.Database.Fetch.DbFetchService`2.Fetch() at Kotrak.Common.Infrastructure.Integration.Filters.InternalStorageFetchFilter`1.Execute(InternalStorageContext`1 input) at Kotrak.Extensions.Pipeline.Pipeline`1.Execute(T input) at Kotrak.Extensions.Pipeline.ContinuousPipeline`1.Execute(TContext input) at Kotrak.Common.Infrastructure.Integration.Jobs.InboundProcessJob.<>c__DisplayClass3_0.<Execute>b__3()ClientConnectionId:733ba743-ff1e-4b55-901c-825655c09f3f\'"", ""Comment 17: \'023-03-31 15:37:50 (c780c84f-ec61-4491-8a54-cf8403b82ab5/Plant.DHC.Integration/DHVD01AP203/12848/56) [Error] Plant.Integration.DhcService.Infrastructure.Handlers.BaseInboundMessageHandler - VehicleTicketDispatchPipelineExecutor execution errorKotrak.Extensions.Communication.Exceptions.ConnectionBrokenException: A connection attempt failed because the connected party did not properly respond after a period of time"", \'Comment 18: or established connection failed because connected host has failed to respond. (dhvd01ap174:8087) ---> System.ServiceModel.CommunicationException: A connection attempt failed because the connected party did not properly respond after a period of time\', \'Comment 19: or established connection failed because connected host has failed to respond. *{color:#de350b}(dhvd01ap174:8087){color}* ---> System.Net.Http.HttpRequestException: A connection attempt failed because the connected party did not properly respond after a period of time\', \'Comment 20: or established connection failed because connected host has failed to respond. (dhvd01ap174:8087) ---> System.Net.Sockets.SocketException (10060): A connection attempt failed because the connected party did not properly respond after a period of time\', \'Comment 21: or established connection failed because connected host has failed to respond. at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error\', ""Comment 22: CancellationToken cancellationToken) at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource.GetResult(Int16 token)\'"", ""Comment 23: \'server dhc !image-2023-04-04-12-17-39-887.png!\'"", ""Comment 24: \'!image-2023-04-04-12-19-22-720.png!\'"", ""Comment 25: \'Hello"", \'Comment 26: after yesterday situation on Helmond\', \'Comment 27: raised in task https://helpdesk.kotrak.com/browse/DGS-8904we found someunautorized actions on the database that practically blocked pcs module\', \'Comment 28: causing a lot of timeouts and deadlocks\', \'Comment 29: it seems\', ""Comment 30: that this could be ( with high possibility) reason for also situation raised in dgs-8090.log analysis earlier also showed only timeout You can see that values in milliseconds is close to over 56 hour!image-2023-04-05-08-17-24-523.png!Is that information sufficient for you and may we close the task?\'"", ""Comment 31: \'May we close the task?\'"", ""Comment 32: \'May we close the task?\']""]\nRelated Issues:\n[\'DGS-8890\']\n\n### End'}"
137,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8895\n\n### Instruction:\nHi\r\n\r\nPlease could you find the entry that is breaking the cross posting rule for me.\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 3: \\\'This entry (screenshot-1) is breaking the cross posting rule ""Deny company cross posting"" !screenshot-1!  !screenshot-2! \\\'\', ""Comment 4: \'HiYes"", ""Comment 5: but how is that a cross entry?\'"", ""Comment 6: \'The finance team found the issue. Wrong accountTicket may be closed. Thank you for the help!!image-3!\'"", ""Comment 7: \'Thank you for information :)\']""]\nRelated Issues:\n[]\n\n### End'}"
138,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8894\n\n### Instruction:\nIn the category ""Eggs"" we have multiple sections (in the round and one the FS). We miss one important one called ""Tweede soort"". Could you add this?\r\n\r\nIn this section we should present the bookings with item code ""TWEE"". \n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Section Tweede soort are added in FS document and Round document for sector PAS.\'"", ""Comment 4: \'Can be closed.\']""]\nRelated Issues:\n[]\n\n### End'}"
139,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8893\n\n### Instruction:\nHi, from Iwona.\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'The definition of the category for this pay component has been changed.The changes will be visible when the system recreates the analytic description for this payroll.Please verify.\'"", ""Comment 4: \'Task to close. Thanks.\']""]\nRelated Issues:\n[]\n\n### End'}"
140,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8892\n\n### Instruction:\nMorning\r\nPlease could you assist with the following issue:\r\n\r\nDHM BANK 31/03/2023 23/MFNBC/73/39 is not closing\n\n### Response:\n[""Comment 1: [\'!image!!image-1!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'!image-2!\'"", ""Comment 4: \'Please place this ticket on hold as per screenshot. User is going to make a work around.\'"", ""Comment 5: \'Apologies"", ""Comment 6: the work around failed. We need to continue with this ticket.\'"", ""Comment 7: \'HiCould we unpost this bank report and try to do this again?\'"", ""Comment 8: \'Asking finance to do it now.\'"", ""Comment 9: \'Still getting an error!image-3!\'"", ""Comment 10: \'I changed the posting scheme 020IN.Please"", ""Comment 11: check\'"", ""Comment 12: \'DHM is closed now. What was wrong with 020IN?\'"", \'Comment 13: ""I changed  the formula in 4th position to:\\\'020-\\\'&KontoWymiaru(\\\'category\\\')it was before:\\\'020-\\\'&KontoWymiaru(\\\'kategoria\\\')""\', ""Comment 14: \'Oh"", ""Comment 15: ok. So a small translation issue. Thanks You can close the ticket.\']""]\nRelated Issues:\n[]\n\n### End'}"
141,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8891\n\n### Instruction:\nHi,\r\n\r\nPlease help to check this issue. User can not confirm PLR . \n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,\\\\r\\\\rWe are investigating your issue. We will inform you about the solution as soon as possible.\\\\r\\\\rRegards\\\\r\\\\r\'"", \'Comment 3: \\\'{code:java}2023-04-03 14:04:31 (96389402-eba3-4a08-9cb4-623c54f63b91/Plant.Prod.BusinessLogic/VNTN-TS01/5984/161) [Error] Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware - Error during request{  ""scheme"": ""http""\', \'Comment 4:  ""host"": {    ""Value"": ""10.84.50.199:83""\', \'Comment 5:    ""HasValue"": true\', \'Comment 6:    ""Host"": ""10.84.50.199""\', \'Comment 7:    ""Port"": 83  }\', \'Comment 8:  ""path"": ""/api/productionLot/update""\', \'Comment 9:  ""queryString"": []\', \'Comment 10:  ""requestBody"": ""{\\\\\\\\""elements\\\\\\\\"":[{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":1,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""da8b4cf8-b081-43f0-bfa6-9a651ea7f8ee\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":1100}},{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":2,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""c3c1752d-4b4a-48b4-9cb6-8387d15fd902\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":1980}},{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":3,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""9812dcb6-1f33-4b8d-b785-2cc7f7641e86\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":19}},{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":4,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""7d031926-b504-410c-a97c-d10aac1b79b2\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":2}},{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":5,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""8bf5c2dc-2412-4c4f-af09-9d5e6b34d26f\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":900}},{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":6,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""4d72d853-c912-4754-8e83-b36fa1d8808b\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":400}},{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":7,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""bb42bf8f-e30c-4fbf-aec2-925ad555eb80\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":600}},{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":8,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""616e78e9-b902-4b56-894c-7fb0592ece24\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":1000}},{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":9,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""aa6a64e6-5a7e-4d95-9e4e-620dc018273d\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":980}},{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":10,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""e471178c-187e-4803-a94c-df14d19f56c0\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":4.4}},{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":11,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""dd7d749a-1f3d-4c0a-b38e-53a9cc21b24f\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":1000}},{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":12,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""556a242e-5178-44fa-b5d0-6b6a3b4acc3c\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":2}},{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":13,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""3f4ae0f3-1122-4e8d-9f30-1a53b8e4dd93\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":2}},{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":14,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""2ceee972-9822-49f3-b10f-e15fabacb0f7\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":10}},{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":15,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""e2eb8227-7f3f-47fd-83e9-9091b3a13b31\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":200}},{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":16,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""47266428-01df-42af-818c-6a326688e5cb\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":6005.2}},{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":17,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""8ad69d7a-59be-44ab-90b6-dfabcabb0711\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":2500}},{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":18,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""94c5d2b6-32b4-497a-ad16-984cfc18201b\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":40}},{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":19,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""422f7a50-31ca-4ade-89c7-a8c0f9eb2e1c\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":762}},{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":20,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""956a30a8-4b2c-4027-9795-39a512a9fc2f\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":10}},{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":21,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""e12d47bc-5607-41d1-81a1-1d1d05dcf7d0\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":34.2}},{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":22,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""197f87e5-888a-4616-8d9c-00c9e9668848\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":50}},{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":23,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""a5435af9-9474-459f-8877-d8cbf8b55dde\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":600}},{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":24,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""80dacfdf-b704-47e2-a76d-0ebea48cccb3\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":10}},{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":25,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""7e761c59-9674-4716-9cd3-0f0c75a8c35a\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":620}},{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":26,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""06d3c0ce-46a0-417e-88fa-7b74a1915a5b\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":69.2}},{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":27,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""91269b01-7f68-4512-8d53-9a71454454da\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":280}},{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":28,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""9c3faeff-33a8-455b-b481-3cc2f11b8a91\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":800}},{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":29,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""6320244d-2132-472e-a519-ae1a57138a66\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":20}}],\\\\\\\\""executions\\\\\\\\"":[{\\\\\\\\""elements\\\\\\\\"":[],\\\\\\\\""readyProductId\\\\\\\\"":\\\\\\\\""da56e314-e09c-49a8-b53a-30ccaadd5add\\\\\\\\"",\\\\\\\\""packingRecipeId\\\\\\\\"":null,\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":20000},\\\\\\\\""requestedQuantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":20000},\\\\\\\\""expiryDate\\\\\\\\"":\\\\\\\\""2023-07-02T06:15:24.936Z\\\\\\\\""}],\\\\\\\\""reservations\\\\\\\\"":[{\\\\\\\\""deliveryId\\\\\\\\"":\\\\\\\\""7555b496-59c0-4305-89c1-3e87e3d9d332\\\\\\\\"",\\\\\\\\""stockUnitId\\\\\\\\"":\\\\\\\\""b53c2fd7-3e48-4c8e-82ca-71576d084a92\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":19}},{\\\\\\\\""deliveryId\\\\\\\\"":\\\\\\\\""cccb707c-6597-48a4-9e79-5ddf98ac80e4\\\\\\\\"",\\\\\\\\""stockUnitId\\\\\\\\"":\\\\\\\\""7cac85ea-d639-40d2-b9dc-d8708843e6f3\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":10}},{\\\\\\\\""deliveryId\\\\\\\\"":\\\\\\\\""2f8a1e44-af6a-4dca-b1b4-d3b95af4d6c2\\\\\\\\"",\\\\\\\\""stockUnitId\\\\\\\\"":\\\\\\\\""3902d8f0-7f0e-4aa3-b1c0-22902a21e51b\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":800}},{\\\\\\\\""deliveryId\\\\\\\\"":\\\\\\\\""255961c9-c8f7-48ed-9faf-5ecb6c479a0f\\\\\\\\"",\\\\\\\\""stockUnitId\\\\\\\\"":\\\\\\\\""121fb072-f4f3-49ce-a43f-454389090f90\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":1000}},{\\\\\\\\""deliveryId\\\\\\\\"":\\\\\\\\""2ecc2f02-40b7-45c0-b74c-bdd459b15773\\\\\\\\"",\\\\\\\\""stockUnitId\\\\\\\\"":\\\\\\\\""66dbc653-3b16-49e2-96a2-818051459add\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":980}},{\\\\\\\\""deliveryId\\\\\\\\"":\\\\\\\\""8338f0c3-071a-40aa-88ae-4b8b000a5436\\\\\\\\"",\\\\\\\\""stockUnitId\\\\\\\\"":\\\\\\\\""4525fe5f-802a-4761-adf2-86b793bb9f99\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":6005.2}},{\\\\\\\\""deliveryId\\\\\\\\"":\\\\\\\\""ff78bd19-dccf-41bf-837c-1b8ce6e63e36\\\\\\\\"",\\\\\\\\""stockUnitId\\\\\\\\"":\\\\\\\\""05f47cf4-2a76-4959-9c13-8b7eff10d1a6\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":2}},{\\\\\\\\""deliveryId\\\\\\\\"":\\\\\\\\""dbc3e51d-2582-42f3-b489-c64d1048253f\\\\\\\\"",\\\\\\\\""stockUnitId\\\\\\\\"":\\\\\\\\""3bec8ccd-b20b-4f4f-8903-bcc135005cb0\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":69.2}},{\\\\\\\\""deliveryId\\\\\\\\"":\\\\\\\\""ef542311-1979-482c-b72f-f48e1804ec58\\\\\\\\"",\\\\\\\\""stockUnitId\\\\\\\\"":\\\\\\\\""0d1db1d4-d583-4e5f-87c1-7c6d1d8d465f\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":1000}},{\\\\\\\\""deliveryId\\\\\\\\"":\\\\\\\\""a6eb4819-1d61-4e27-a61b-5bc264ccb4d8\\\\\\\\"",\\\\\\\\""stockUnitId\\\\\\\\"":\\\\\\\\""96ae00bc-c3c5-464d-a8d2-cfcb5995daab\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":1980}},{\\\\\\\\""deliveryId\\\\\\\\"":\\\\\\\\""562ddace-e33f-4e38-9f12-153885f197f2\\\\\\\\"",\\\\\\\\""stockUnitId\\\\\\\\"":\\\\\\\\""59cf136f-cd20-435f-ab7f-bf82ada010e1\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":200}},{\\\\\\\\""deliveryId\\\\\\\\"":\\\\\\\\""842a0974-2899-49ae-bea3-54a3a397e2e4\\\\\\\\"",\\\\\\\\""stockUnitId\\\\\\\\"":\\\\\\\\""fefae1df-b013-4dbf-874b-103f2661129b\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":600}},{\\\\\\\\""deliveryId\\\\\\\\"":\\\\\\\\""f50d0faf-c691-4e9b-bc56-d00e6d995de1\\\\\\\\"",\\\\\\\\""stockUnitId\\\\\\\\"":\\\\\\\\""0f31c250-2103-4c89-b3af-692c55f38b1f\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":40}},{\\\\\\\\""deliveryId\\\\\\\\"":\\\\\\\\""ab669de7-86d5-43e0-a97d-df736159bbff\\\\\\\\"",\\\\\\\\""stockUnitId\\\\\\\\"":\\\\\\\\""c4827d6c-3d59-4221-a41e-d25cdeb591d7\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":1100}},{\\\\\\\\""deliveryId\\\\\\\\"":\\\\\\\\""63e2941f-ace6-45a6-bd28-c0d4931bdf78\\\\\\\\"",\\\\\\\\""stockUnitId\\\\\\\\"":\\\\\\\\""6f48c4af-282b-4b00-8bdd-a7b8d6f80a02\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":280}},{\\\\\\\\""deliveryId\\\\\\\\"":\\\\\\\\""4cb2b135-5539-4546-bf6d-f4380adef53d\\\\\\\\"",\\\\\\\\""stockUnitId\\\\\\\\"":\\\\\\\\""f41f3f99-9951-4542-ad41-77b55c643ff2\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":900}},{\\\\\\\\""deliveryId\\\\\\\\"":\\\\\\\\""51d8f758-98e7-48d3-af53-f5cb4fb26da8\\\\\\\\"",\\\\\\\\""stockUnitId\\\\\\\\"":\\\\\\\\""3701ff2d-7eb1-45fc-99ad-35d2d7f01545\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":762}},{\\\\\\\\""deliveryId\\\\\\\\"":\\\\\\\\""4ed334e5-5e68-4467-b51d-b84d45ff5a85\\\\\\\\"",\\\\\\\\""stockUnitId\\\\\\\\"":\\\\\\\\""bf33b145-3f89-4e99-9f2f-b3c32cecef3a\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":20}},{\\\\\\\\""deliveryId\\\\\\\\"":\\\\\\\\""7b31a984-5f4f-461c-9c39-3a29af08faa6\\\\\\\\"",\\\\\\\\""stockUnitId\\\\\\\\"":\\\\\\\\""9886856f-aad6-40ef-9e3f-07c70b5c799d\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":400}},{\\\\\\\\""deliveryId\\\\\\\\"":\\\\\\\\""e0b295ef-1c8f-4aa8-a847-0796184dc331\\\\\\\\"",\\\\\\\\""stockUnitId\\\\\\\\"":\\\\\\\\""366a9db9-08fb-45f8-939a-a23a7def5dbb\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":2}},{\\\\\\\\""deliveryId\\\\\\\\"":\\\\\\\\""1466480b-2a33-435c-9777-14570905551b\\\\\\\\"",\\\\\\\\""stockUnitId\\\\\\\\"":\\\\\\\\""4ff95f11-622b-47a9-b401-d60783e5a3f9\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":600}},{\\\\\\\\""deliveryId\\\\\\\\"":\\\\\\\\""7b10e6e1-4497-4565-a9d4-2254d9a6b61e\\\\\\\\"",\\\\\\\\""stockUnitId\\\\\\\\"":\\\\\\\\""c8357944-3e3b-4449-a1d4-ac939d3cd7e3\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":4.4}},{\\\\\\\\""deliveryId\\\\\\\\"":\\\\\\\\""9a92cbe8-a60a-4ca4-a0ba-ec1dbb037f92\\\\\\\\"",\\\\\\\\""stockUnitId\\\\\\\\"":\\\\\\\\""3965e4c2-24e9-46a4-a966-798d2f96a5a8\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":2500}},{\\\\\\\\""deliveryId\\\\\\\\"":\\\\\\\\""d8881bfc-5f33-4097-8d62-05d72011c791\\\\\\\\"",\\\\\\\\""stockUnitId\\\\\\\\"":\\\\\\\\""8ce4e88e-28d8-4a8f-ac81-4d5dbae50c3b\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":10}}],\\\\\\\\""productionLotId\\\\\\\\"":\\\\\\\\""a12a4bde-930d-4539-803a-980a11af4113\\\\\\\\"",\\\\\\\\""recipeId\\\\\\\\"":\\\\\\\\""e0c008ad-28bd-4005-b671-509d0a471d26\\\\\\\\"",\\\\\\\\""labelId\\\\\\\\"":null,\\\\\\\\""productionOrderId\\\\\\\\"":\\\\\\\\""a02545ce-a9b2-420f-b033-4272e08c6583\\\\\\\\"",\\\\\\\\""shiftNumberId\\\\\\\\"":\\\\\\\\""0f4af611-a440-462b-b369-769f1457b817\\\\\\\\"",\\\\\\\\""statusChange\\\\\\\\"":2}""}.System.AggregateException: One or more errors occurred. (Response status code does not indicate success: 500 (Internal Server Error).) ---> Refit.ApiException: Response status code does not indicate success: 500 (Internal Server Error).   at Refit.RequestBuilderImplementation.<>c__DisplayClass14_0`2.<<BuildCancellableTaskFuncForMethod>b__0>d.MoveNext() in d:\\\\\\\\a\\\\\\\\1\\\\\\\\s\\\\\\\\Refit\\\\\\\\RequestBuilderImplementation.cs:line 273   --- End of inner exception stack trace ---   at System.Threading.Tasks.Task`1.GetResultCore(Boolean waitCompletionNotification)   at Plant.Prod.BusinessLogic.Infrastructure.ContextIntegration.ApiServices.StockEngine.StockEngineApi.UpdateReservationsAndConfirmProductionLot(AggregateId productionLotId\', \'Comment 11: AggregateId businessUnitId\', \'Comment 12: Quantity productionQuantity\', \'Comment 13: IEnumerable`1 settlementData\', \'Comment 14: IEnumerable`1 dosingSiloItemData) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Infrastructure.ContextIntegration\\\\\\\\ApiServices\\\\\\\\StockEngine\\\\\\\\StockEngineApi.cs:line 135   at Plant.Prod.BusinessLogic.Domain.ProductionLots.ConfirmProductionLotDomainService.UpdateReservationsAndConfirmProductionLot(ProductionLot productionLot\', \'Comment 15: ConfirmProductionLotActionData data\', \'Comment 16: IEnumerable`1 reservations\', \'Comment 17: IEnumerable`1 dosingSiloItemData) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Domain\\\\\\\\ProductionLots\\\\\\\\ConfirmProductionLotDomainService.cs:line 82   at Plant.Prod.BusinessLogic.Application.ProductionLots.ProductionLotService.UpdateProductionLot(UpdateProductionLotActionData data) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Application\\\\\\\\ProductionLots\\\\\\\\ProductionLotService.cs:line 325   at Plant.Prod.BusinessLogic.Application.ProductionLots.CommandHandlers.UpdateProductionLotCommandHandler.Handle(UpdateProductionLotCommand command) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Application\\\\\\\\ProductionLots\\\\\\\\CommandHandlers\\\\\\\\UpdateProductionLotCommandHandler.cs:line 39   at Kotrak.Common.Infrastructure.Commands.CommandEnvironment.Run[TCommand](TCommand command)   at Kotrak.Common.Infrastructure.Commands.Decorators.IntercontextEventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command)   at Kotrak.Common.Infrastructure.Commands.Decorators.EventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command)   at Kotrak.Common.Infrastructure.Commands.Decorators.ValidationCommandEnvironmentDecorator.Run[TCommand](TCommand command)   at Castle.DynamicProxy.AbstractInvocation.Proceed()   at Kotrak.Common.Infrastructure.Interceptors.LoggingInterceptor`1.Intercept(IInvocation invocation)   at Castle.DynamicProxy.AbstractInvocation.Proceed()   at Kotrak.Common.Infrastructure.Commands.Decorators.HistoryGateDecorator.Dispatch[TCommand](TCommand command)   at Plant.Prod.BusinessLogic.Infrastructure.Api.Controllers.ProductionLotController.UpdateProductionLot(UpdateProductionLotViewModel viewModel) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Infrastructure.Api\\\\\\\\Controllers\\\\\\\\ProductionLotController.cs:line 110   at lambda_method(Closure \', \'Comment 18: Object \', \'Comment 19: Object[] )   at Microsoft.Extensions.Internal.ObjectMethodExecutor.Execute(Object target\', \'Comment 20: Object[] parameters)   at Microsoft.AspNetCore.Mvc.Internal.ActionMethodExecutor.SyncObjectResultExecutor.Execute(IActionResultTypeMapper mapper\', \'Comment 21: ObjectMethodExecutor executor\', \'Comment 22: Object controller\', \'Comment 23: Object[] arguments)   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.InvokeActionMethodAsync()   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.InvokeNextActionFilterAsync()   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.Rethrow(ActionExecutedContext context)   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.Next(State& next\', \'Comment 24: Scope& scope\', \'Comment 25: Object& state\', \'Comment 26: Boolean& isCompleted)   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.InvokeInnerFilterAsync()   at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.InvokeNextResourceFilter()   at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.Rethrow(ResourceExecutedContext context)   at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.Next(State& next\', \'Comment 27: Scope& scope\', \'Comment 28: Object& state\', ""Comment 29: Boolean& isCompleted)   at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.InvokeFilterPipelineAsync()   at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.InvokeAsync()   at Microsoft.AspNetCore.Builder.RouterMiddleware.Invoke(HttpContext httpContext)   at Microsoft.AspNetCore.StaticFiles.StaticFileMiddleware.Invoke(HttpContext context)   at Swashbuckle.AspNetCore.SwaggerUI.SwaggerUIIndexMiddleware.Invoke(HttpContext httpContext)   at Swashbuckle.AspNetCore.Swagger.SwaggerMiddleware.Invoke(HttpContext httpContext)   at Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware.Invoke(HttpContext httpContext)---> (Inner Exception #0) Refit.ApiException: Response status code does not indicate success: 500 (Internal Server Error).   at Refit.RequestBuilderImplementation.<>c__DisplayClass14_0`2.<<BuildCancellableTaskFuncForMethod>b__0>d.MoveNext() in d:\\\\\\\\a\\\\\\\\1\\\\\\\\s\\\\\\\\Refit\\\\\\\\RequestBuilderImplementation.cs:line 273<---{code}\'"", ""Comment 30: \'{code:java}2023-04-03 14:04:31 (96389402-eba3-4a08-9cb4-623c54f63b91/Plant.Prod.BusinessLogic/VNTN-TS01/5984/161) [Error] Kotrak.Common.Infrastructure.ICommandRunEnvironment - Error during Void Run[UpdateProductionLotCommand](Plant.Prod.BusinessLogic.Application.Interfaces.ProductionLots.Commands.UpdateProductionLotCommand) methodSystem.AggregateException: One or more errors occurred. (Response status code does not indicate success: 500 (Internal Server Error).) ---> Refit.ApiException: Response status code does not indicate success: 500 (Internal Server Error).   at Refit.RequestBuilderImplementation.<>c__DisplayClass14_0`2.<<BuildCancellableTaskFuncForMethod>b__0>d.MoveNext() in d:\\\\\\\\a\\\\\\\\1\\\\\\\\s\\\\\\\\Refit\\\\\\\\RequestBuilderImplementation.cs:line 273   --- End of inner exception stack trace ---   at System.Threading.Tasks.Task`1.GetResultCore(Boolean waitCompletionNotification)   at Plant.Prod.BusinessLogic.Infrastructure.ContextIntegration.ApiServices.StockEngine.StockEngineApi.UpdateReservationsAndConfirmProductionLot(AggregateId productionLotId"", \'Comment 31: AggregateId businessUnitId\', \'Comment 32: Quantity productionQuantity\', \'Comment 33: IEnumerable`1 settlementData\', \'Comment 34: IEnumerable`1 dosingSiloItemData) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Infrastructure.ContextIntegration\\\\\\\\ApiServices\\\\\\\\StockEngine\\\\\\\\StockEngineApi.cs:line 135   at Plant.Prod.BusinessLogic.Domain.ProductionLots.ConfirmProductionLotDomainService.UpdateReservationsAndConfirmProductionLot(ProductionLot productionLot\', \'Comment 35: ConfirmProductionLotActionData data\', \'Comment 36: IEnumerable`1 reservations\', \'Comment 37: IEnumerable`1 dosingSiloItemData) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Domain\\\\\\\\ProductionLots\\\\\\\\ConfirmProductionLotDomainService.cs:line 82   at Plant.Prod.BusinessLogic.Application.ProductionLots.ProductionLotService.UpdateProductionLot(UpdateProductionLotActionData data) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Application\\\\\\\\ProductionLots\\\\\\\\ProductionLotService.cs:line 325   at Plant.Prod.BusinessLogic.Application.ProductionLots.CommandHandlers.UpdateProductionLotCommandHandler.Handle(UpdateProductionLotCommand command) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Application\\\\\\\\ProductionLots\\\\\\\\CommandHandlers\\\\\\\\UpdateProductionLotCommandHandler.cs:line 39   at Kotrak.Common.Infrastructure.Commands.CommandEnvironment.Run[TCommand](TCommand command)   at Kotrak.Common.Infrastructure.Commands.Decorators.IntercontextEventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command)   at Kotrak.Common.Infrastructure.Commands.Decorators.EventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command)   at Kotrak.Common.Infrastructure.Commands.Decorators.ValidationCommandEnvironmentDecorator.Run[TCommand](TCommand command)   at Castle.DynamicProxy.AbstractInvocation.Proceed()   at Kotrak.Common.Infrastructure.Interceptors.LoggingInterceptor`1.Intercept(IInvocation invocation)---> (Inner Exception #0) Refit.ApiException: Response status code does not indicate success: 500 (Internal Server Error).   at Refit.RequestBuilderImplementation.<>c__DisplayClass14_0`2.<<BuildCancellableTaskFuncForMethod>b__0>d.MoveNext() in d:\\\\\\\\a\\\\\\\\1\\\\\\\\s\\\\\\\\Refit\\\\\\\\RequestBuilderImplementation.cs:line 273<---2023-04-03 14:04:31 (null/Plant.Prod.BusinessLogic/VNTN-TS01/5984/161) [Error] Serilog.AspNetCore.RequestLoggingMiddleware - HTTP ""POST"" ""/api/productionLot/update"" responded 500 in 4844.1201 ms{code}\\\'\', ""Comment 38: \'{code:java}2023-04-03 14:04:31 (96389402-eba3-4a08-9cb4-623c54f63b91/Plant.Stock.BusinessLogic/VNTN-TS01/9384/250) [Error] Kotrak.Common.Infrastructure.ICommandRunEnvironment - Error during Void Run[UpdateReservationsAndConfirmProductionLotCommand](Plant.Stock.BusinessLogic.Application.Interfaces.ProductionLots.Commands.UpdateReservationsAndConfirmProductionLotCommand) methodSystem.Data.SqlClient.SqlException (0x80131904): Could not allocate a new page for database \\\\\'DHPlantStockBusinessLogicEvents\\\\\' because of insufficient disk space in filegroup \\\\\'PRIMARY\\\\\'. Create the necessary space by dropping objects in the filegroup"", \'Comment 39: adding additional files to the filegroup\', \'Comment 40: or setting autogrowth on for existing files in the filegroup.   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception\', \'Comment 41: Boolean breakConnection\', \'Comment 42: Action`1 wrapCloseInAction)   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj\', \'Comment 43: Boolean callerHasConnectionLock\', \'Comment 44: Boolean asyncClose)   at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior\', \'Comment 45: SqlCommand cmdHandler\', \'Comment 46: SqlDataReader dataStream\', \'Comment 47: BulkCopySimpleResultSet bulkCopyHandler\', \'Comment 48: TdsParserStateObject stateObj\', \'Comment 49: Boolean& dataReady)   at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior\', \'Comment 50: SqlCommand cmdHandler\', \'Comment 51: SqlDataReader dataStream\', \'Comment 52: BulkCopySimpleResultSet bulkCopyHandler\', \'Comment 53: TdsParserStateObject stateObj)   at System.Data.SqlClient.SqlBulkCopy.RunParser(BulkCopySimpleResultSet bulkCopyHandler)   at System.Data.SqlClient.SqlBulkCopy.CopyBatchesAsyncContinuedOnSuccess(BulkCopySimpleResultSet internalResults\', \'Comment 54: String updateBulkCommandText\', \'Comment 55: CancellationToken cts\', \'Comment 56: TaskCompletionSource`1 source)   at System.Data.SqlClient.SqlBulkCopy.CopyBatchesAsyncContinued(BulkCopySimpleResultSet internalResults\', \'Comment 57: String updateBulkCommandText\', \'Comment 58: CancellationToken cts\', \'Comment 59: TaskCompletionSource`1 source)   at System.Data.SqlClient.SqlBulkCopy.CopyBatchesAsync(BulkCopySimpleResultSet internalResults\', \'Comment 60: String updateBulkCommandText\', \'Comment 61: CancellationToken cts\', \'Comment 62: TaskCompletionSource`1 source)   at System.Data.SqlClient.SqlBulkCopy.WriteToServerInternalRestContinuedAsync(BulkCopySimpleResultSet internalResults\', \'Comment 63: CancellationToken cts\', \'Comment 64: TaskCompletionSource`1 source)   at System.Data.SqlClient.SqlBulkCopy.WriteToServerInternalRestAsync(CancellationToken cts\', \'Comment 65: TaskCompletionSource`1 source)   at System.Data.SqlClient.SqlBulkCopy.WriteToServerInternalAsync(CancellationToken ctoken)   at System.Data.SqlClient.SqlBulkCopy.WriteRowSourceToServerAsync(Int32 columnCount\', \'Comment 66: CancellationToken ctoken)   at System.Data.SqlClient.SqlBulkCopy.WriteToServer(DbDataReader reader)   at EFCore.BulkExtensions.SqlBulkOperation.Insert[T](DbContext context\', \'Comment 67: IList`1 entities\', \'Comment 68: TableInfo tableInfo\', \'Comment 69: Action`1 progress)   at EFCore.BulkExtensions.DbContextBulkExtensions.BulkInsert[T](DbContext context\', \'Comment 70: IList`1 entities\', \'Comment 71: BulkConfig bulkConfig\', \'Comment 72: Action`1 progress)   at Kotrak.Common.Infrastructure.EF.EventRepository.GenericEventRepositoryEf`2.Persist(TAggregateRoot aggregateRoot)   at Plant.Stock.BusinessLogic.Infrastructure.Persistance.StockUnits.Repositories.StockUnitRepository.PersistRangeAfterProductionConfirmation(IEnumerable`1 modifiedStockUnits\', \'Comment 73: IEnumerable`1 newStockUnits) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Infrastructure.Persistance\\\\\\\\StockUnits\\\\\\\\Repositories\\\\\\\\StockUnitRepository.cs:line 316   at Plant.Stock.BusinessLogic.Application.ProductionLots.ProductionLotService.PersistConfirmProductionLotResult(ProductionLot productionLot\', \'Comment 74: ICollection`1 semiProductProductionLots\', \'Comment 75: ConfirmProductionLotResult result) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Application\\\\\\\\ProductionLots\\\\\\\\ProductionLotService.cs:line 756   at Plant.Stock.BusinessLogic.Application.ProductionLots.ProductionLotService.UpdateReservationsAndConfirmProductionLot(UpdateReservationsAndConfirmProductionLotActionData data) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Application\\\\\\\\ProductionLots\\\\\\\\ProductionLotService.cs:line 450   at Plant.Stock.BusinessLogic.Application.ProductionLots.CommandHandlers.UpdateReservationsAndConfirmProductionLotCommandHandler.Handle(UpdateReservationsAndConfirmProductionLotCommand command) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Application\\\\\\\\ProductionLots\\\\\\\\CommandHandlers\\\\\\\\UpdateReservationsAndConfirmProductionLotCommandHandler.cs:line 33   at Kotrak.Common.Infrastructure.Commands.CommandEnvironment.Run[TCommand](TCommand command)   at Kotrak.Common.Infrastructure.Commands.Decorators.IntercontextEventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command)   at Kotrak.Common.Infrastructure.Commands.Decorators.EventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command)   at Kotrak.Common.Infrastructure.Commands.Decorators.ValidationCommandEnvironmentDecorator.Run[TCommand](TCommand command)   at Castle.DynamicProxy.AbstractInvocation.Proceed()   at Kotrak.Common.Infrastructure.Interceptors.LoggingInterceptor`1.Intercept(IInvocation invocation)ClientConnectionId:2bcc4c1b-68ec-4dbf-9bb7-c952c05bf408Error Number:1101,State:12,Class:172023-04-03 14:04:31 (null/Plant.Stock.BusinessLogic/VNTN-TS01/9384/250) [Error] Serilog.AspNetCore.RequestLoggingMiddleware - HTTP ""POST"" ""/api/productionLot/updateReservationsAndConfirm"" responded 500 in 4693.3152 ms{code}\\\'\', \'Comment 76: ""I have recreated your error. In logs we have information:{code:java}2023-04-03 14:04:31 (96389402-eba3-4a08-9cb4-623c54f63b91/Plant.Stock.BusinessLogic/VNTN-TS01/9384/250) [Error] Kotrak.Common.Infrastructure.ICommandRunEnvironment - Error during Void Run[UpdateReservationsAndConfirmProductionLotCommand](Plant.Stock.BusinessLogic.Application.Interfaces.ProductionLots.Commands.UpdateReservationsAndConfirmProductionLotCommand) methodSystem.Data.SqlClient.SqlException (0x80131904): Could not allocate a new page for database \\\'DHPlantStockBusinessLogicEvents\\\' because of insufficient disk space in filegroup \\\'PRIMARY\\\'. Create the necessary space by dropping objects in the filegroup\', \'Comment 77: adding additional files to the filegroup\', \'Comment 78: or setting autogrowth on for existing files in the filegroup.{code}Please\', \'Comment 79: see db server below: !image-2023-04-03-09-17-49-468.png!Regards""\', ""Comment 80: \'i have been clean our backup for space but may we have clean data in event DBs?!image-1!\'"", ""Comment 81: \'Hi,You can clean this data but please"", ""Comment 82: clean the oldest ones. But please try to shrink them first.Regards\'"", ""Comment 83: \'i try to shrink database but it still have it\'"", ""Comment 84: \'Can we lower the priority?If you cannot shrink"", ""Comment 85: please delete the oldest data.Regards\'"", ""Comment 86: \'yes"", ""Comment 87: please set it to P3\'"", ""Comment 88: \'Did you delete oldest data?Regards\'"", \'Comment 89: ""hi\', \'Comment 90: i\\\'m not delete data. just shrink database but after sometime still back to old""\', ""Comment 91: \'[~maciej.dobrzanski@kotrak.com] Maciek"", \'Comment 92: Marcin Block mówił\', \'Comment 93: żew czwratek w tej fabryce jest upgrade plus zmiana serwerów\', ""Comment 94: drążyć temat? Albo po prostu wrzucam FYI :)\'"", ""Comment 95: \'ja bym poczekał na przypadek po upgrade. Nie mam wersji 8.3 (a taka chyba mają) więc cięzko będzie nam cokolwiek zreprodukować.\'"", ""Comment 96: \'Hi,I have some information that on Thursday afternoon CET time you have upgrade inHai Phong 2 factory. After short discussion with dev"", ""Comment 97: it is advise to wait to upgrade and check if the issue wll occur for 8.5 version.Regards\'"", ""Comment 98: \'so mean that this ticket will be hold to after upgrade?\'"", ""Comment 99: \'Yes"", ""Comment 100: if you agree\'"", ""Comment 101: \'agree"", ""Comment 102: please keep in HOLD\'"", ""Comment 103: \'Sure\'"", ""Comment 104: \'Hi,Does the issue occur in version 8.5?Regards\']""]\nRelated Issues:\n[]\n\n### End'}"
142,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8890\n\n### Instruction:\nGood morning,\r\n\r\nplease we have got a problem with communication between PCS and DHP on plant Helmond.\r\n\r\nFor example SO-14644/3/23\r\n\r\nIt\'s not processed on DHP.\r\n\r\nCould you have a look at it.\r\n\r\nKind regards,\r\n\r\nGerard Geerts\r\n\r\n\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'!image-2023-04-03-09-00-49-160.png!\'"", ""Comment 3: \'!image-2023-04-03-09-04-14-125.png!\'"", ""Comment 4: \'Culd please verify again "", \'Comment 5: I do not see any errors\', ""Comment 6: and we had informaction that order was exported 31.03 at 16:28.\'"", ""Comment 7: \'Hello Agnieszka,Problem still on. Could it be a problem with the Webservices?Gerard\'"", ""Comment 8: \'Hello Agnieska,There is no data communicating tot DHP.Maybe first to have a look at the communication between DHC and DHP. Because the salesorder SO000092646  with trip: 9_L000275519 is not communicating to DHP.Regards,Gerard  \'"", ""Comment 9: \'Helloso-14644 is in dhp: its forieng number isSO000091362 ? did you still have problem with that order?!image-2023-04-03-11-18-04-800.png|width=1062,height=171!\'"", ""Comment 10: \'Hallo Agnieska"", \'Comment 11: with so-14644 the problem is that there no VT created\', \'Comment 12: while the dispatch message is accepted in the webservice: Please check thatBesides\', \'Comment 13: Gerard also reports that orders and trips are not coming into DHP\', \'Comment 14: with the example SO000092646  and trip  9_L000275519: please check that also,this as a higher priority\', ""Comment 15: because orders and trips do not arrive in the pcs and are blocking the production\'"", ""Comment 16: \'For your other example it was send to DHP. Please check others.\'"", ""Comment 17: \'SO000092646 is indeed now in DHP but not send to pcs. please check\'"", ""Comment 18: \'!afbeelding!\'"", ""Comment 19: \'!afbeelding-1!\'"", \'Comment 20: ""Ok so by now there are 2 cases : # that from 1 so no VT was created.- Are you able to create a VT from DHP as workaround? # that other SO\\\'s need resynchro to PCS""\', ""Comment 21: \'For 2 Please trigger resync"", \'Comment 22: I expect you can do thisFor 1: No we cannot\', ""Comment 23: because we need a correct packing slip therefore info from the dispatch message is required\'"", ""Comment 24: \'ad 2. it looks like integration looks fine"", ""Comment 25: please verify If there is still something missing.\'"", ""Comment 26: \'ad 1. VT was created please verify!image-2023-04-03-12-15-50-874.png!\'"", ""Comment 27: \'Oke"", ""Comment 28: can we determine root cause because complete communication seems to be down during this mornng: Was the problem mainly in DHC>DHP communication?\'"", ""Comment 29: \'RCA is underDGS-8896 may we close this one?\'"", ""Comment 30: \'yes can be closed\']""]\nRelated Issues:\n[\'DGS-8896\']\n\n### End'}"
143,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8889\n\n### Instruction:\nMorning\r\nMy support team is not in today, and we are deploying a DHApps update. I\'m not able to investigate this issue. Please can you take a look for me. This is word for word from the internal ticket supplied by the user.\r\n\r\n""Please see below, the accounting note does not reflect on the payment plan for the customer 010-15-10-06070""\r\n\r\nThe finance team needs this resolved today to close the period.\r\n\r\nRegards\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 3: ""Hi This accounting note is not visible in Payment plan because there is no customer (Payer) on this Note.There is only amount.As I see this type of Accounting note - ACC19 is configured in a way it doesn\\\'t allow to add the Payer on it.I can change configuration for this document or you could use simplified note to enter this payment.Best Regards""\', ""Comment 4: \'Will ask the finance team what they would like\'"", ""Comment 5: \'HiThis ticket can be closed. Thank you for the help. Finance team used a simplified note.Regards\']""]\nRelated Issues:\n[]\n\n### End'}"
144,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8888\n\n### Instruction:\nHi\r\n\r\nPlease help to check 2PLRs 4322010423007 and 4322010423006 .\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Hi!.Please help to close this ticket . t has been resolved  . Thanks u.\'"", ""Comment 4: \'Issue has been closed as requested.\']""]\nRelated Issues:\n[]\n\n### End'}"
145,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8887\n\n### Instruction:\nCould you please cancel PRO-1032/3/23?\r\n\r\nItem SUR6912-MD-B500\r\nOrder SO-638076283/23/PED\r\n\r\nWe need to produce urgent and system not allow to create new PRO.\r\nThank you\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'PrO has been canceled.\'"", ""Comment 3: \'Hi Piotr,ok"", ""Comment 4: you can close this task. Thank you.\'"", ""Comment 5: \'Thank you for confirmation.\']""]\nRelated Issues:\n[\'DGS-8869\']\n\n### End'}"
146,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8886\n\n### Instruction:\nerror id 6428793 -  Intake for this barcode is already closed\r\n\r\nProduction stopped please take care about the problem fast.\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'It seems that the message was incorrect. We have cancelled this message. Please"", ""Comment 3: verify.Regards\'"", ""Comment 4: \'Production started - task to close.\']""]\nRelated Issues:\n[]\n\n### End'}"
147,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8885\n\n### Instruction:\nWe got informed the Belgian Intense users experience a very slow performance of Intense in the past weeks. Today is really slow. \r\n\r\nThis is opposed by the Dutch users, who don\'t have such complaints.\r\n\r\nBoth working via Citrix.\r\n\r\nCan you please investigate why the performance is so poor for the Belgian users?\n\n### Response:\n[""Comment 1: [\'Hi Martijn,Do you have any details about examples of slow operations in Intense? Regards,Tomasz\'"", ""Comment 2: \'{color:black}Hi Koen,{color} {color:black}{color} {color:black}I created a ticket at Kotrak for the slowness you experience. As the Dutch users don’t experience this slowness"", \'Comment 3: I don’t think Citrix is the issue.{color} {color:black}{color} {color:black}Can you give Tomasz some examples as he requests below? Thanks!{color} {color:black}{color} | |{color:#000001} Kindregards,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Martijn{color} |{color:#000001} {color} |{color:#000001} Meier{color} |  {color:#000001}ApplicationEngineer{color} | | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.deheus.com/]>{color} | |  *{color:#006FB7} *DEHEUSANIMALNUTRITIONB.V.*{color}* | | | |{color:#000001} P.O.Box396 6710BJEde TheNetherlands{color} | |{color:#000001} Rubensstraat175 6717VEEde TheNetherlands{color} | | |{color:#000001} M:{color}{color:#000001}{color}{color:#000001}+31621679216{color}{color:#000001} <tel:+31%206%2021%20679%20216>{color} |  {color:#000001}CoC16011201{color}   _{color:#000001} _Thise‑mailmessageanditsattachmentsaresubjecttothedisclaimer_ _publishedonthewebsiteof_{color}_{color:#000001} _+{color}[{color:#000001}{color}{color:#000001} _+ DeHeusAnimalNutrition+_{color}{color:#000001} {color}|https://www.deheus.com/disclaimer]{color:#000001} {color}+__{color:#000001} _._{color}_ | | !image002! <[https://www.facebook.com/deheusanimalnutrition]>{color:black}{color} | | !image003! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image004! <[https://www.linkedin.com/company/royal-de-heus/mycompany/]>{color:black}{color} | | !image005! <[https://www.instagram.com/de_heus_animal_nutrition/]>{color:black}{color} |        *From:* Tomasz Kozioł (Jira) <jira@kotrak.com>   *Sent:* vrijdag 31 maart 2023 13:54  *To:* Meier\', ""Comment 4: Martijn <mmeier@deheus.com>  *Subject:* DGS-8885 Intense slow for Belgian users   \'"", ""Comment 5: \'To verify possibilty of adding RAM memory on SQL Server\']""]\nRelated Issues:\n[]\n\n### End'}"
148,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8884\n\n### Instruction:\nNote: ticket is applicable for all DHP\'s\r\n\r\nVehicle tickets for dispatches are missing in DHC/Milas. We checked and found that Vehicle tickets with status Dispatch completed do not seem to be sent anymore from DHP to DHC. \r\nFor Dutch Feed plants this was the case and it is still needed. \r\n\r\nCan you check if configuration is missing and correct this? \r\nWe need VT\'s with status Dispatch completed in DHC/Milas.\r\n\r\nExamples e.g,1314/3/23 and 1315/3/23 for Sneek: dispatch completed in DHP, no data in DHC\r\n\r\n\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!!image-1!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Hi Bob,Are you able to confirm if missing VTs are only from March?Regards\'"", \'Comment 4: ""Indeed only VT\\\'s from March seem to be missing in DHC.I checked for Sneek in February and March and I found only issues in March (from March 9 - date of the deploy of new DHP version for Sneek). First plant for which new DHP was deployed was Ravenstein (28-feb). Also for that plan I only found missing VT in DHC in March""\', ""Comment 5: \'Cześć.[~maciej.dobrzanski@kotrak.com],W tym statusie jest ogólnie 145 VT"", \'Comment 6: ale zakładam\', \'Comment 7: że nie tylko o status Dispatch Completed chodzi.Rozumiem\', \'Comment 8: że to ten sam kejs\', \'Comment 9: co tu https://helpdesk.kotrak.com/browse/DGS-8694 # Czy jest szansa na skrypt + czy chodzi tylko o VT dispatch completed? # Czy ktoś mógłby spawdzić konfigurację\', \'Comment 10: ewentualnie podac screena\', \'Comment 11: co sprawdzić\', ""Comment 12: to sprawdzę?Thanks from the mountain :)[~marek.mamcarz@kotrak.com]ktoś juz pisał z NL z tym do Ciebie?\'"", ""Comment 13: \'Thank you Bob for your information.Regards\'"", ""Comment 14: \'[~aleksandra.przybylek@kotrak.com] a nie przesyłaliście ostatnio we współpracy z [~maciej.buchacz@kotrak.com]?\'"", ""Comment 15: \'[~maciej.dobrzanski@kotrak.com] ale to były PLR"", ""Comment 16: a tu chcą VT :)to ten scrypt wymagałby małej modyfkacji czy dużego przemeblowania? :)\'"", ""Comment 17: \'[~aleksandra.przybylek@kotrak.com] tak trzeba troche pozmieniać.[~marcin.kleszcz@kotrak.com] może [~maciej.buchacz@kotrak.com] mógłby pomóc? Już podobne skrypty przerabiał.Jeśli nie trzeba resendować ręcznie\'"", ""Comment 18: \'[~aleksandra.przybylek@kotrak.com] Czy mogłabyś podać listę dokumentów VT"", ""Comment 19: którą należy przesłać? (albo skąd wzięłaś ilość 145 vt :) ).\'"", ""Comment 20: \'[~maciej.buchacz@kotrak.com] Z bazy danych wyszukałam po statusie Dispatch complete we wszystkich plantach. Ale nauczona doświadczeniem z akcji z PLR"", \'Comment 21: to nie jestem pewna\', ""Comment 22: czy to jedyny właściwy status... [~marek.mamcarz@kotrak.com]??\'"", ""Comment 23: \'no i zawęziłam do marca ofkors :P\'"", ""Comment 24: \'Do you have an update on this ticket?\'"", ""Comment 25: \'[^dgs8884.xlsx]\'"", \'Comment 26: \\\'Dear Bob,I have doubts if status ""dispatch completed"" and month = march is accurate filter for Vehicle Tickets.I have filtered documents list two days ago and today and they differ. In attach\', \'Comment 27: please see al VT documents with status dispatch completed. In some plants we do not have VTs with this status on the VT list. If someone could verified this list and confirm or provide us with the list of VT documents that should be sent\', ""Comment 28: I would be very thankful.Regards[^dgs8884.xlsx]\'"", ""Comment 29: \'[^DGS-8884.xlsx]\'"", ""Comment 30: \'lista z id i cała resztą informacji[^DGS-8884.xlsx]\'"", ""Comment 31: \'Hi Aleksandra"", \'Comment 32: The list will indeed change every day: - as soon as VT is closed (by operator or automatic closing process by the system)\', \'Comment 33: the VT gets status Closed and is automatically synced -> no action needed- as long as the bug is not fixed\', \'Comment 34: new VT in April will be on the list that still need to be send (e.g. VT-160/4/23\', \'Comment 35: 167/4/23\', \'Comment 36: 173/4/23 for Nijkerk). So\', ""Comment 37: I think correct filter is: all VT with status Dispatch Completed from March 1 until todaySecond part of this ticket is solving the bug/change config so that VT with status Dispatch completed are automatically synced to DHC.\'"", ""Comment 38: \'I have resent those four for Utrecht. Please"", ""Comment 39: verify and let me know if this is fine for you so that I could send from other plants!image-2023-04-06-11-29-01-363.png!\'"", ""Comment 40: \'This list for Utrecht is correct\'"", ""Comment 41: \' !before after! konfigi dla fabryk przed i po upgrade\'"", \'Comment 42: \\\'I have resent all VTs with status ""Dispatch complete"" from March.Now I will check April and will provide you with the list of resent documents\\\'\', ""Comment 43: \'Below is the list of VTs from April sent to MilasVeghel:VT-227/4/23Maasbracht:VT-361/4/23VT-179/4/23VT-243/4/23VT-84/4/23VT-170/4/23VT-384/4/23VT-211/4/23VT-344/4/23VT-152/4/23VT-318/4/23VT-150/4/23Ravenstein:VT-118/4/23VT-92/4/23VT-56/4/23VT-55/4/23VT-24/4/23VT-123/4/23VT-36/4/23VT-33/4/23VT-119/4/23VT-89/4/23VT-117/4/23VT-70/4/23VT-98/4/23Helmond:VT-81/4/23VT-242/4/23Nijkekr:VT-111/4/23VT-64/4/23VT-1/4/23VT-122/4/23VT-13/4/23VT-160/4/23VT-173/4/23VT-167/4/23VT-123/4/23VT-41/4/23VT-98/4/23Sneek:VT-9/4/23VT-117/4/23VT-133/4/23VT-257/4/23VT-160/4/23VT-189/4/23VT-24/4/23VT-192/4/23VT-287/4/23\'"", ""Comment 44: \'To skoro konfiguracja dla tego procesu się nie zmieniła"", \'Comment 45: to już nie wiem co... Na razie przesłałam marzec i na bieżąco\', \'Comment 46: ale jest coś\', ""Comment 47: że nie działa...\'"", ""Comment 48: \'[^Resend draft vehicle ticket to DHC 8.5.sql]\'"", ""Comment 49: \'[^Resend draft vehicle ticket to DHC 8.5.sql]\'"", \'Comment 50: ""Hi [~BKennedy@deheus.com],We found some cases that may not be sent to DHC. We have fix for that. Do you agree if we deploy the fix? You don\\\'t need to stop production.Best regards""\', \'Comment 51: ""Hi Aleksandra,Thank you for sending the VT\\\'s. Will the fix solve the issue that next VT\\\'s with status Dispatch completed will be sent to DHC automatically?Can it be that some of the VT\\\'s listed below are not yet in DHC? (e.g. 118/4/2023/004 - for Ravenstein). Or will this be solved with the fix as well?On Tuesday\', \'Comment 52: I will check with Thomas for the deploy of the fix.""\', \'Comment 53: ""Hi Bob,Yes\', \'Comment 54: there may be taht some VTs from the list still did not arrive.The fix will solve the issue ofnext VT\\\'s with status Dispatch complete to be sent.Waitng for your feedback then after Thomas\\\'s acceptance.Regards""\', ""Comment 55: \'Update w Utrecht done.\'"", ""Comment 56: \'pięknie <3\'"", ""Comment 57: \'Hi [~BKennedy@deheus.com],The fix has been implemented to Utrecht. Please"", ""Comment 58: test if it is woring fine for you now and provide us with the feedback so that we could implement in other factories.Regards\'"", \'Comment 59: ""Hi @Aleksandra\', \'Comment 60: after the update I did not find any VT with status Dispatch Completed\', ""Comment 61: so I could not check if the fix is working correctly. I did check if all other VT\'s (with status Closed) are in DHC"", \'Comment 62: and that is still ok. I think you can continue with update for other plants ""\', ""Comment 63: \'Thank you. I am transferring this task to Dev Team.Regards\'"", ""Comment 64: \'Hi,The fix has been implemented in all plants.Please"", ""Comment 65: let us know if we can close this taskRegards\'"", \'Comment 66: ""New VT\\\'s with status Dispatch Completed are indeed in DHC now. This ticket can be closed.""\', ""Comment 67: \'Thank you.Regards\']""]\nRelated Issues:\n[\'DGS-8694\', \'DAP-13538\']\n\n### End'}"
149,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8883\n\n### Instruction:\nWe still see a lot of old S2P’s in Intense that are still on the status Entry. We are for 99% sure that all these S2P’s are already settled in Milas. However the users forgot to put the status on archive.\r\n\r\nAfter some modifications in the system now it won’t be possible to settle a S2P in Milas if it is not archived so this problem will not exist in the future.\r\n\r\nAre you able to change the status of these S2P to archive without sending them again to Milas? Just to make sure: we don’t want these to be send to Milas again.\n\n### Response:\n[""Comment 1: [\'[^S2P Entry.xlsx]\'"", ""Comment 2: \'There are list of documents from Excel which have been sent to Archive in Intense without sending to Milas.There are some documents with no mapping in mapping table of sent to Milas S2Ps.Please verify that all these documents are in Milas.|*ID*|*Number*|*Mapping*||55460|SP-M/0005|No mapping||63362|SP-M/0020|||68583|SP-M/0029|||71689|SP-M/0043|No mapping||72091|SP-M/0051|No mapping||72619|SP-M/0068|No mapping||72644|SP-M/0070|No mapping||73007|SP-M/0080|||73563|SP-M/0090|||73816|SP-M/0094|||74088|SP-M/0100|No mapping||74462|SP-M/0105|||75705|SP-M/0124|||75921|SP-M/0127|No mapping||76001|SP-M/0128|||77272|SP-M/0152|||77426|SP-M/0156|||77447|SP-M/0157|No mapping||77457|SP-M/0158|No mapping||77987|SP-M/0172|No mapping||78695|SP-M/0185|No mapping||78790|SP-M/0187|||78813|SP-M/0189|||78871|SP-M/0190|||80239|SP-M/0202|||80275|SP-M/0203|No mapping||80646|SP-M/0214|||81796|SP-M/0222|||82056|SP-M/0231|||82721|SP-M/0234|||83141|SP-M/0244|||83220|SP-M/0246|No mapping||83730|SP-M/0262|||83732|SP-M/0263|||83909|SP-M/0269|||84748|SP-M/0296|No mapping||85623|SP-M/0307|No mapping||86661|SP-M/0327|No mapping||86712|SP-M/0328|||86762|SP-M/0330|||86968|SP-M/0331|No mapping||87636|SP-M/0337|||88179|SP-M/0347|||88189|SP-M/0349|||88630|SP-M/0357|||88935|SP-M/0362|||89349|SP-M/0370|||89519|SP-M/0378|||89612|SP-M/0379|No mapping||90107|SP-M/0388|||90344|SP-M/0389|||90379|SP-M/0392|||90449|SP-M/0396|||90540|SP-M/0398|||90650|SP-M/0400|||90817|SP-M/0403|No mapping||90869|SP-M/0404|No mapping||90872|SP-M/0405|No mapping||90965|SP-M/0406|No mapping||91016|SP-M/0407|No mapping||91020|SP-M/0408|No mapping||91046|SP-M/0410|No mapping||91051|SP-M/0411|No mapping||91052|SP-M/0412|||91149|SP-M/0416|||91395|SP-M/0425|||91497|SP-M/0427|||91628|SP-M/0432|||91636|SP-M/0433|||91670|SP-M/0434|No mapping||91751|SP-M/0435|||92041|SP-M/0437|||92112|SP-M/0438|||92135|SP-M/0439|||92197|SP-M/0440|||92199|SP-M/0441|||92277|SP-M/0442|||92293|SP-M/0443|||92321|SP-M/0444|||92375|SP-M/0445|||92382|SP-M/0446|||92402|SP-M/0447|||92406|SP-M/0448|||92416|SP-M/0449|||92449|SP-M/0450|||92482|SP-M/0451|||92485|SP-M/0452|||92491|SP-M/0453|||92669|SP-M/0454|||92673|SP-M/0455|||92681|SP-M/0456|||92688|SP-M/0457|||92701|SP-M/0458|||92705|SP-M/0459|||92710|SP-M/0460|||92843|SP-M/0461|||92909|SP-M/0464|No mapping||93167|SP-M/0466|No mapping||93206|SP-M/0467|||93357|SP-M/0469|||93442|SP-M/0473|No mapping||93686|SP-M/0479|||93859|SP-M/0483|||93877|SP-M/0484|||93886|SP-M/0485|||94327|SP-M/0487|No mapping||95350|SP-M/0504|No mapping||96840|SP-M/0518|No mapping||97187|SP-M/0523||\'"", ""Comment 3: \'We are verifying this. The task can be closed. \']""]\nRelated Issues:\n[\'DGS-8877\']\n\n### End'}"
150,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8882\n\n### Instruction:\nFor sales order SO000091430 with special for Helmond, the one time recipe 303436 version 136 subversion 1 is generated and in DHP, but it is not sent to PCS.\r\n\r\nYesterday an additional technology for this code was archived (see: https://helpdesk.kotrak.com/servicedesk/customer/portal/56/DGS-8852)\r\n\r\nIn DHC the one time recipe is generated on the correct (303436) code. However, plant did not receive the one time recipe in PCS.\r\n\r\nPlease check if archiving of additional technology was done correctly (in DHC and DHP).\r\nPlant needs the one time recipe for production.\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 3: ""select * from items where code=\\\'303436\\\'select * from Recipes where id=\\\'5718735F-47FA-4453-81F3-C690A2A60F0C\\\'select * from ExportRecipes where entityid=15317!image-2023-03-31-09-47-42-220.png!""\', ""Comment 4: \'!image-2023-03-31-09-49-30-691.png!\'"", \'Comment 5: ""obu nie ma tabeli export recipes dla tego itema jest tylkoselect * from ExportRecipes where entityid in(select entityid from Recipes where id=\\\'5718735F-47FA-4453-81F3-C690A2A60F0C\\\' or (ItemId=\\\'08B78E4E-277B-4282-8154-FB338C827580\\\'))!image-2023-03-31-09-59-10-730.png!""\', \'Comment 6: ""-- DECLARE @RecipeId UNIQUEIDENTIFIER = \\\'FEF262AC-67B2-4F07-A79E-0A299ED68592\\\'; -- id receptury version 0-- DECLARE @RecipeId UNIQUEIDENTIFIER = \\\'FEF262AC-67B2-4F07-A79E-0A299ED68592\\\'; -- id receptury version 0-- DECLARE @RecipeEntityId INT= (SELECT r.EntityId FROM dbo.Recipes r WHERE r.Id = @RecipeId);-- UPDATE dbo.Recipes-- SET IsProductDefinition = 0-- WHERE Id = @RecipeId;-- DELETE FROM dbo.ExportRecipes-- WHERE EntityId = @RecipeEntityId;-- INSERT INTO dbo.ExportRecipes (PackageId\', \'Comment 7: SendDate\', \'Comment 8: ConfirmDate\', \'Comment 9: ExternalSystemId\', \'Comment 10: EntityId)-- SELECT NEWID()\', \'Comment 11: GETDATE()\', \'Comment 12: GETDATE()\', \'Comment 13: er.Id\', \'Comment 14: r.EntityId-- FROM dbo.Recipes r-- JOIN dbo.ExternalSystems er ON 1 = 1--WHERE r.Id = @RecipeId;update [DHPlantProdBusinessLogicMain].dbo.Recipes set IsProductDefinition = 0where Id = \\\'FEF262AC-67B2-4F07-A79E-0A299ED68592\\\'""\', ""Comment 15: \'Please check should be ok now.\'"", ""Comment 16: \'Thank you"", ""Comment 17: I asked plant to verify if they received the one time recipe correctly.\'"", ""Comment 18: \'This ticket can be closed\']""]\nRelated Issues:\n[]\n\n### End'}"
151,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8881\n\n### Instruction:\nPo wczorajszej aktualizacji ERP integratora nasili się problem z synchronizacją tras z DHC do DHP, np:\r\n5041/23/L\r\n\r\n5059/23/G\r\n\r\n2040/23/P\r\n\r\n2224/23/I\r\n\r\n2225/23I\r\n\r\n1039/23/J\r\n\r\nPo wygenerowaniu VT poprzez podpięcie ZS w DHC generują sie elementy bez powiązania z ZS, np. \r\n\r\nVT 4237/P, 4279/P, 4280/P, 6124/M, 6289/G\n\n### Response:\n[""Comment 1: [\'ERP Integratora"", \'Comment 2: są dwa rodzaje błędów\', \'Comment 3: dla change message:[^error_1.txt]-- dla calego ordera i dla elementówSystem.NullReferenceException: Object reference not set to an instance of an object.   at Evolution.DHCService.Dhc30.Handlers.ShippingNoticeElementChangedMessageHandler.FillEntity(ShippingNoticeElementChangedMessage message\', \'Comment 4: ShippingNoticeElementEntity entity) in E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\31916033\\\\\\\\DHAPPSV3-DHCSER538-JOB1\\\\\\\\Evolution.DHCService\\\\\\\\Evolution.DHCService.Dhc30\\\\\\\\Handlers\\\\\\\\ShippingNoticeElementChangedMessageHandler.cs:line 43   at Evolution.DHCService.Dhc30.Handlers.BaseMessageHandler`2.Handle(TMessage message) in E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\31916033\\\\\\\\DHAPPSV3-DHCSER538-JOB1\\\\\\\\Evolution.DHCService\\\\\\\\Evolution.DHCService.Dhc30\\\\\\\\Handlers\\\\\\\\BaseMessageHandler.cs:line 56   at lambda_method(Closure \', \'Comment 5: Object \', \'Comment 6: Object )   at NServiceBus.Unicast.MessageHandlerRegistry.Invoke(Object handler\', \'Comment 7: Object message\', \'Comment 8: Dictionary`2 dictionary) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Unicast\\\\\\\\MessageHandlerRegistry.cs:line 126   at NServiceBus.Unicast.MessageHandlerRegistry.InvokeHandle(Object handler\', \'Comment 9: Object message) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Unicast\\\\\\\\MessageHandlerRegistry.cs:line 84   at NServiceBus.LoadHandlersBehavior.<Invoke>b__1(Object handlerInstance\', \'Comment 10: Object message) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Unicast\\\\\\\\Behaviors\\\\\\\\LoadHandlersBehavior.cs:line 40   at NServiceBus.InvokeHandlersBehavior.Invoke(IncomingContext context\', \'Comment 11: Action next) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Unicast\\\\\\\\Behaviors\\\\\\\\InvokeHandlersBehavior.cs:line 24   at NServiceBus.BehaviorChain`1.InvokeNext(T context) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 107   at NServiceBus.BehaviorChain`1.<>c__DisplayClass5.<InvokeNext>b__2() in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 94   at NServiceBus.SetCurrentMessageBeingHandledBehavior.Invoke(IncomingContext context\', ""Comment 12: Action next) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Unicast\\\\\\\\Behaviors\\\\\\\\SetCurrentMessageBeingHandledBehavior.cs:line 17\'"", ""Comment 13: \'Moja mała uwaga odnosnie twierdzenia że nic nie zmieniali na zamówieniach"", ""Comment 14: z tego co widze to na tabeli w ERP xl nie loguje sie info o zmianach na zamówieniach ( kwestiach ich konfigu ale np dla zamówienia 130 na tabeli cdn.zamvat ( nie ma tej zakładki widocznej w erp xl) ale widzimy dla zamówieniaZW-130/03/23/D na tabeli cdn.zamvat mamy zav_gidlp tylko 5 - wiec oznacza to ze pozycje jakies były usuwane bo nie ma pozycji miedzy 1-5 wiec zdecydowanie cos z tymi zamówienia się działo,!image-2023-03-31-07-42-46-952.png|width=950,height=347!\'"", ""Comment 15: \'Trasę \\\\\'T-5041/23/L\\\\\' nawet nie wiem jak miałbym sprawdzać"", \'Comment 16: powstały trzy awizacje o takim numerze jedna wyjazdowa z jednej fabryki i dwie identyczne wjazdowe na drugą fabrykę co już samo w sobie jest absurdalne. Do trasy ""T-5059/23/G"" sprawdziłem jak wyglądała historia zmian zamówienia (można sprawdzić wpisy w tabeli communicationLogs) otóż na przestrzeni 3 dni dostaliśmy 69 aktualizacji tego zamówienia. Generalnie analiza w tym przypadku mija się już z celem bo i tak nigdy nie dojdziemy czemu brakowało elementów zamówienia spiętych z tymi trasami.Generalnie mają ERP integratora ustawionego tak zeby synchronizował niepotwierdzone zamówienia w których grzebią jak tylko mogą i takie są tego efekty.\\\'\', ""Comment 17: \'Hello"", ""Comment 18: is there any progress with this RCA? Similar cases pop up everyday and engage local IT resources. \'"", ""Comment 19: \'Good morning,Short analysis results below in two languages to avoid misunderstandingTrasa \\\\\'T-5041/23/L\\\\\' - powstały trzy awizacje o takim numerze - jedna wyjazdowa z jednej fabryki i dwie identyczne wjazdowe na drugą fabrykę"", \'Comment 20: co nie jest dobre dla systemu\', \'Comment 21: a przede wszystkim procesu biznesowego i powoduje zamieszanie. Do trasy ""T-5059/23/G"" sprawdziliśmy jak wyglądała historia zmian zamówienia. W ciągu 3 dni dostaliśmy 69 aktualizacji tego zamówienia. Generalnie analiza w tym przypadku mija się już z celem\', \'Comment 22: bo nie jesteśmy w stanie ustalić\', \'Comment 23: dlaczego brakowało elementów zamówienia spiętych z tymi trasami.ERP integratora macie ustawionego tak żeby synchronizował niepotwierdzone zamówienia\', \'Comment 24: w których są dokonywane pewne zmiany\', ""Comment 25: co również powoduje wskazane problemy.Route \\\\\'T-5041/23/L\\\\\' - three Shipping Notices with this number were created"", \'Comment 26: one dispatch SN from one factory and two identical intake Shipping Notices to the other factory\', \'Comment 27: which is not good for the system\', \'Comment 28: and above all for the business process\', \'Comment 29: and it also causes confusion. For the ""T-5059/23/G"" route\', \'Comment 30: we checked the history of the order changes. We have got 69 updates related to this order within 3 days. In general\', \'Comment 31: the analysis in this case misses the point because we are unable to determine why the order elements associated with these routes were missing.Your ERP integrator is set up to synchronize unconfirmed orders where some changes are made\', ""Comment 32: which also causes the indicated problems.Best regards\'"", ""Comment 33: \'Informacyjnie"", \'Comment 34: config ErpIntegrator_MSG oraz ErpIntegrator_DOC nie zmienił się podczas zeszłotygodniowej aktualizacji. Jedynie na końcu configu została zmieniona wersja biblioteki log4net.dll z 2.0.8.0 na 2.0.12.0\', \'Comment 35: co wyszło na środowisku testowym podczas pierwszych testów bo nie otrzymaliśmy informacji o tej zmianie.Zaznaczę też że podczas poprzednich aktualizacji wykonywanych przez DH PL IT\', \'Comment 36: nie były zmieniane configi od PlatformApplication\', \'Comment 37: chyba że w kooperacji z Wami\', ""Comment 38: przy zgłoszonych DGSach że nagle coś przestało działać po podniesieniu integratora.\'"", ""Comment 39: \'[~przemyslaw.przybyszewski@kotrak.com] Przemek"", ""Comment 40: a ERP Int wcześniej też był tak skonfigurowany? Pamiętasz może?\'"", ""Comment 41: \'W tej chwili pojawił się przykład trasy 5096/23/G która zaczyna się w Mieścisku jedzie przez Janowiec "", ""Comment 42: Buk i kończy się w Grodzisku. Powodem braku trasy w DHP Mieścisko były zamówienia 168 i 169 /03/23/G które z jakiegoś powodu nie przeszły do DHP. Wymuszony update na zamówieniu ( poprzez zmianę daty realizacji w CDN ) przepchnął zamówienia do DHP co po ponownym potwierdzeniu trasy skutkowało jej pojawieniem się w systemie Jak widać takie trasy nie powodują wielkiego zamieszania lecz z jakiś powodów Integrator nie przesyła wszystkich danych miedzy systemami . !image!\'"", ""Comment 43: \'T-1099/23/J jest w DHC nie ma w DHCService\'"", ""Comment 44: \'Hello"", ""Comment 45: due to the number of operations on the orders( as it was mentioned earlier)  can I get the current case/example (without synchronization attempts)?Thanks.\'"", ""Comment 46: \'T-5494/L  brak trasy w DHPZamówienie dla tej trasy jest w DHP !image-1!\'"", ""Comment 47: \'Any news ?? \'"", ""Comment 48: \'Kolejny przykład T-5467 / L \'"", ""Comment 49: \'It can be process now this second one. Thank you.\'"", ""Comment 50: \'{code:java} SELECT o.* FROM [dbo].[Orders] o left join [dbo].[OrderElements] e on o.id=e.orderid  where   DocumentNumerator_Year=2023 and\\\\tDocumentNumerator_Month in(2,3,4)  and e.id is null and status <>6 {code}\'"", ""Comment 51: \'Two examples from today:T-5467/23/L ZS-2431/03/23/LT-5494/23/L ZS-2445/03/23/LOrders elements were missing in DHCService.After sending again orders and trips are in DHC Service and DHP.All orders have a common creation date on 27.3.2023.Was there an upgrade day?All problematic orders have the same date- apart from one ZW(ZW-38/03/23/M)"", ""Comment 52: there are currently 79 of them.ZS-959/03/23/PZS-953/03/23/DZS-952/03/23/DZS-851/03/23/IZS-1028/03/23/DZS-1001/03/23/DZW-38/03/23/MZS-1445/03/23/ŁZS-2455/03/23/LZS-2433/03/23/LZS-958/03/23/PZS-963/03/23/PZS-859/03/23/IZS-1656/03/23/SZS-858/03/23/IZS-870/03/23/IZS-871/03/23/IZZ-976/03/23ZS-1026/03/23/DZS-874/03/23/IZS-951/03/23/DZS-1627/03/23/SZS-862/03/23/IZS-1043/03/23/DZS-865/03/23/IZS-2439/03/23/LZS-1003/03/23/DZW-154/03/23/MZS-1449/03/23/ŁZS-978/03/23/DZS-967/03/23/DZS-842/03/23/IZS-2450/03/23/LZS-1450/03/23/ŁZS-958/03/23/DZS-943/03/23/DZS-861/03/23/IZS-959/03/23/DZS-2454/03/23/LZS-1443/03/23/ŁZS-841/03/23/IZS-864/03/23/IZS-2451/03/23/LZS-849/03/23/IZS-954/03/23/DZS-857/03/23/IZS-1655/03/23/SZS-872/03/23/IZS-964/03/23/DZS-2453/03/23/LZS-844/03/23/IZS-845/03/23/IZS-840/03/23/IZS-873/03/23/IZS-1444/03/23/ŁZS-850/03/23/IZS-866/03/23/IZS-1007/03/23/DZS-876/03/23/IZS-1439/03/23/ŁZS-863/03/23/IZS-980/03/23/DZS-70/03/23/YZS-843/03/23/IZS-999/03/23/DZS-2452/03/23/LZS-1441/03/23/ŁZS-960/03/23/DZS-1438/03/23/ŁZZ-997/03/23ZS-2438/03/23/LZS-875/03/23/IZS-846/03/23/IZS-965/03/23/PZS-2446/03/23/LZS-2434/03/23/LZS-1442/03/23/ŁZS-960/03/23/PZS-1448/03/23/Ł,we can correct (send again) them and check if there are new cases. \'"", ""Comment 53: \'I have found that re-syncing the order helps in my cases. The idea of \\\\u200b\\\\u200bre-syncing orders may solve the problem.\'"", ""Comment 54: \'Orders have been sent again"", ""Comment 55: please check after current date and time.\'"", ""Comment 56: \'Problem nadal występuje . Zamówienia potwierdzane wczoraj - przeszły do DHPTrasa potwierdzana godzinę temu - nie przeszła do DHP Przykład trasa 2248/P \'"", \'Comment 57: ""I\\\'m waiting for another one\', \'Comment 58: this one has already gone to DHP.""\', ""Comment 59: \'Brak trasy w DHP T-5527/23/G\'"", ""Comment 60: \'When it comes to this route  T-5527/23/G"", \'Comment 61: the problem was when changing the Vehicles/Platenumbers to PZ1H806\', \'Comment 62: PZ2K201from  PZ 1H806\', ""Comment 63: PZ 2K201. The user made several changes to these Vehicles looking at the logs. I sent the registrations again in the order and route.\'"", ""Comment 64: \'Kolejna trasa : T-2455 /23/ I\'"", ""Comment 65: \'For DHcService messages need to be process !screenshot-2! \'"", ""Comment 66: \'Why does the queue raised up to almost 700 orders changed?\'"", ""Comment 67: \'Were any changes made to the documents"", ""Comment 68: as indicated by the message?\'"", \'Comment 69: ""I think some orders have been modified\', \'Comment 70: but many of them were synchronizing all the time so queue shouldn\\\'t raise that much. I think queue should be clear or have only few documents to sync - not 700 orders""\', ""Comment 71: \'Kolejna trasa : 131/23/MS \'"", ""Comment 72: \'Messages need time to process"", \'Comment 73: some are more time consuming\', ""Comment 74: e.g. technologies.Each order operation is logged as a change - so there can be several of them for each order.\'"", ""Comment 75: \'Kolejne trasy: 3527/23/S"", \'Comment 76: 465/23/P\', ""Comment 77: 5624/23/L\'"", ""Comment 78: \'ZS-742/4/23/L (nie było w dhp"", \'Comment 79: przeszło po odświeżeniu\', \'Comment 80: ale jako niepotwierdzone\', \'Comment 81: pomimo\', ""Comment 82: ,że w cdn było potwierdzone)\'"", ""Comment 83: \'Kolejne nie przeszły: 3517/23/S"", ""Comment 84: 5621/23/G\'"", ""Comment 85: \'brak ZS-438/04/23/S oraz trasy 3531/23/S\'"", ""Comment 86: \'brak ZS-53/4/23/G (towar niezlinkowany) oraz T-5757/23/G\'"", ""Comment 87: \'brak T-5641/23/G\'"", ""Comment 88: \'brak T-5653/23/G\'"", ""Comment 89: \'brak T-3491/04/23/S"", ""Comment 90: T-3504/04/23/S\'"", ""Comment 91: \'brak T-2310/04/23/P\'"", ""Comment 92: \'T-2310/04/23/P finalnie w ogóle nie przeszła nawet do serwisu\'"", ""Comment 93: \'Hello"", \'Comment 94: referring to yesterday\', \'Comment 95: after 1:30 pm there was still a large number of messages for the dhcservice queue to be processed (several thousand). Were there any changes made to the DHCService message queue\', \'Comment 96: as it was already 0 on the processing list before 2pm?Also function activity monitor was permanently paused for login dhbp. Can we get access to activity monitor for DHC databases? Or for my domain account\', ""Comment 97: thank you.\'"", ""Comment 98: \'Whether additional processes were running that could have caused mass changes to the data?I see that after 9 am messages began to be processed in very large quantities and are still growing for DHCService !screenshot-3! \'"", \'Comment 99: ""Other users from Kotrak could run activity monitor\', ""Comment 100: you were not listed there because it\'s the first time you need it. Access granted"", \'Comment 101: verify.User dhbp is an application user\', ""Comment 102: so it should not have additional privileges like for example activity monitor - its not good practice. On other servers you probably also won\'t run any activity monitor using application user like masterplant"", \'Comment 103: dhbp and similar.""\', ""Comment 104: \'I have asked and nobody told me about any other source of problems that could cause this amount of changed data. Long time ago we had same problem"", ""Comment 105: just look back in requests. Analysis was done and you fixed something.\'"", ""Comment 106: \'Brak tras w DHP (wszystkie zamówienia są w DHP)T-2808/23/DT-4450/23/MT-4120/23/ŁT-5647/23/L\'"", ""Comment 107: \'Przykład do analizy ( załadunek na 16:00) T-5767/23/G\'"", ""Comment 108: \'Brak: ZS-983/04/23/L i T-5708/23/L\'"", ""Comment 109: \'Kolejka komunikatów niby pusta a synchro leży....\'"", ""Comment 110: \'We vt-kach brakuje spięcia z zamówieniami !image-2!\'"", ""Comment 111: \'!image-3!\'"", ""Comment 112: \'Brak : T-3519/23/S\'"", ""Comment 113: \'Brak w DHPT-2512/23/IPotwierdzona o 9:12!image-4!\'"", ""Comment 114: \'Brak: T-4435/23/M\'"", ""Comment 115: \'We are collecting data for analysis.It is not currently necessary to send a new examples.In order for the trips to be process you need to resent the order earlier.I will try to provide more information tomorrow - the results of the analysis.\'"", ""Comment 116: \'hello"", \'Comment 117: as for the amount of changes\', ""Comment 118: this was already a issue:DGS-6103operator TSSROBO These operators currently perform the most changes. !screenshot-4!  !screenshot-5! \'"", ""Comment 119: \'ilość zamówień jakie były modyfikowane.{code:java}SELECT count(*) as ilosc_zmian,ZaN_OpeNumerMod,o.Ope_Nazwisko      --[ZaN_OpeNumerMod]          --,cdn.tstodate([ZaN_LastMod],2)        FROM [CDNXL_DEHEUS].[CDN].[ZamNag] z  join cdn.OpeKarty o on o.Ope_GIDNumer=z.ZaN_OpeNumerMod  where [ZaN_LastMod]>=1050120000 group by ZaN_OpeNumerMod ,o.Ope_Nazwisko order by count(*) desc{code} !screenshot-6! \'"", ""Comment 120: \'In DGS-6103 issue has been resolved. It seems to be something similar"", ""Comment 121: but we had no details what caused this problem with sync before.Could you explain what fixed problem reported in DGS-6103? I think you have some notes because it has been resolved temporarily last time.\'"", ""Comment 122: \'There are two issues - one problem with orders in dhcservice - this is being analyzedand the second message queue on DHCServiceAs for the number of messages for order changes and operators described above. If there are so many changes for orders the messages must be processed.Currently"", ""Comment 123: there are no such problems as in the task mentioned earlier - I only indicated why there are so many messages on the DHCService queue.\'"", ""Comment 124: \'PiotrCh będzie rozmawiał z Łukaszem Grodzkim\'"", ""Comment 125: \'[Przesyłanie Order/zamówień i tras /ShippingNotice - brak elementów zamówień w DHCService|onenote:https://kotrak.sharepoint.com/sites/erpasysta/Shared%20Documents/Baza%20wiedzy/Baza%20Wiedzy%20-%20ERPSD/Klienci/DEHEUS/DEHEUS%20APPLICATIONS/Polska/Baza%20wiedzy/DHC.one#Przesy%C5%82anie%20Order/zam%C3%B3wie%C5%84%20i%20tras%20/ShippingNotice%20-%20brak%20element%C3%B3w&section-id=\\\\\\\\{7D50734F-49D8-4579-83B9-E51158168A8F}&page-id=\\\\\\\\{F79626AC-B068-431D-BAC5-C6AAFA54C428}&end] ([Widok sieci Web|https://kotrak.sharepoint.com/sites/erpasysta/_layouts/OneNote.aspx?id=%2Fsites%2Ferpasysta%2FShared%20Documents%2FBaza%20wiedzy%2FBaza%20Wiedzy%20-%20ERPSD&wd=target%28Klienci%2FDEHEUS%2FDEHEUS%20APPLICATIONS%2FPolska%2FBaza%20wiedzy%2FDHC.one%7C7D50734F-49D8-4579-83B9-E51158168A8F%2FPrzesy%C5%82anie%20Order%5C%2Fzam%C3%B3wie%C5%84%20i%20tras%20%5C%2FShippingNotice%20-%20brak%20element%C3%B3w%7CF79626AC-B068-431D-BAC5-C6AAFA54C428%2F%29]) naprawa przypadków.\'"", ""Comment 126: \'Naprawiłam 9 przypadków\'"", ""Comment 127: \'Kolejki puste"", ""Comment 128: zamówień 24 - przesłano!image-2023-04-14-19-05-22-715.png!!image-2023-04-14-19-04-58-252.png!\'"", ""Comment 129: \'!image-2023-04-15-11-14-54-457.png|width=512,height=436!dzisiaj pusto\'"", \'Comment 130: ""HI\', \'Comment 131: please check after today\\\'s ugrade how the synchronization working and send a feedback.Thank you.""\', ""Comment 132: \'Please let me know if there are currently any problems described in the issue?Thank you.\'"", ""Comment 133: \'We need a little more time until orders made after last update will be processed - there are still some cases with orders made before the update.\'"", ""Comment 134: \'We will wait for final confirmation.\']""]\nRelated Issues:\n[\'DGS-8879\', \'DGS-8965\', \'DGS-8914\']\n\n### End'}"
152,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8880\n\n### Instruction:\nWe tried to weight one truck in unit 2 but for VT from unit 1 but the weight is not available.\r\nCould you check why is not working?\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Dispatch weight : 88860kg!MicrosoftTeams-image (61)!\'"", ""Comment 3: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 4: \'Hi,I can see bothe scales are running and VT-1906 is already closed. Do you have any similar example?Regards\'"", ""Comment 5: \'!image-2023-04-03-11-06-39-563.png!\'"", ""Comment 6: \'!image-2023-04-03-11-07-01-561.png!\'"", \'Comment 7: ""Hi [~Aleksandra.Przybylek@kotrak.com]Unfortunately we don\\\'t have any other example.You can close this task.Thank you very much!""\', ""Comment 8: \'Thank you.Regards\']""]\nRelated Issues:\n[]\n\n### End'}"
153,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8879\n\n### Instruction:\nPo wczorajszej aktualizacji ERP integratora nasili się problem z synchronizacją tras z DHC do DHP, np:\r\n5041/23/L\r\n\r\n5059/23/G\r\n\r\n2040/23/P\r\n\r\n2224/23/I\r\n\r\n2225/23I\r\n\r\n1039/23/J\r\n\r\nPo wygenerowaniu VT poprzez podpięcie ZS w DHC generują sie elementy bez powiązania z ZS, np. \r\n\r\nVT 4237/P, 4279/P, 4280/P, 6124/M, 6289/G\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Ewelina jeszcze dzwoniła"", \'Comment 3: że ze swojej strony przeanalizowali wszystko. Na zamówieniach nie było nic ruszane\', \'Comment 4: żadne dane.Odnośnie tej części:{color:#0747a6}_Po wygenerowaniu VT poprzez podpięcie ZS w DHC generują sie elementy bez powiązania z ZS\', \'Comment 5: np._{color}{color:#0747a6}_VT 4237/P\', \'Comment 6: 4279/P\', \'Comment 7: 4280/P\', \'Comment 8: 6124/M\', \'Comment 9: 6289/G_{color}Ewelina mówi\', \'Comment 10: że w ten sposób sobie radzili\', ""Comment 11: ale ilość dokumentów wzrasta bardzo szybko\'"", ""Comment 12: \'Z ERP Integratora"", \'Comment 13: są dwa rodzaje błędów\', \'Comment 14: dla change message:{code:java}System.InvalidOperationException: Cannot find Order element for specific OrderElementId = 029de345-296b-449b-a0a9-b84a34015907    at Evolution.DHCService.Dhc30.Handlers.ShippingNoticeChangedMessageHandler.MapOrders(ShippingNoticeElementEntity shippingNoticeElementEntity\', \'Comment 15: List`1 orderMessageElemenets) in E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\31916033\\\\\\\\DHAPPSV3-DHCSER538-JOB1\\\\\\\\Evolution.DHCService\\\\\\\\Evolution.DHCService.Dhc30\\\\\\\\Handlers\\\\\\\\ShippingNoticeChangedMessageHandler.cs:line 95   at Evolution.DHCService.Dhc30.Handlers.ShippingNoticeChangedMessageHandler.FillEntity(ShippingNoticeChangedMessage message\', \'Comment 16: ShippingNoticeEntity entity) in E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\31916033\\\\\\\\DHAPPSV3-DHCSER538-JOB1\\\\\\\\Evolution.DHCService\\\\\\\\Evolution.DHCService.Dhc30\\\\\\\\Handlers\\\\\\\\ShippingNoticeChangedMessageHandler.cs:line 74   at Evolution.DHCService.Dhc30.Handlers.BaseMessageHandler`2.Handle(TMessage message) in E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\31916033\\\\\\\\DHAPPSV3-DHCSER538-JOB1\\\\\\\\Evolution.DHCService\\\\\\\\Evolution.DHCService.Dhc30\\\\\\\\Handlers\\\\\\\\BaseMessageHandler.cs:line 56   at lambda_method(Closure \', \'Comment 17: Object \', \'Comment 18: Object )   at NServiceBus.Unicast.MessageHandlerRegistry.Invoke(Object handler\', \'Comment 19: Object message\', \'Comment 20: Dictionary`2 dictionary) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Unicast\\\\\\\\MessageHandlerRegistry.cs:line 126   at NServiceBus.Unicast.MessageHandlerRegistry.InvokeHandle(Object handler\', \'Comment 21: Object message) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Unicast\\\\\\\\MessageHandlerRegistry.cs:line 84   at NServiceBus.LoadHandlersBehavior.<Invoke>b__1(Object handlerInstance\', \'Comment 22: Object message) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Unicast\\\\\\\\Behaviors\\\\\\\\LoadHandlersBehavior.cs:line 40   at NServiceBus.InvokeHandlersBehavior.Invoke(IncomingContext context\', \'Comment 23: Action next) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Unicast\\\\\\\\Behaviors\\\\\\\\InvokeHandlersBehavior.cs:line 24   at NServiceBus.BehaviorChain`1.InvokeNext(T context) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 107   at NServiceBus.BehaviorChain`1.<>c__DisplayClass5.<InvokeNext>b__2() in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 94   at NServiceBus.SetCurrentMessageBeingHandledBehavior.Invoke(IncomingContext context\', \'Comment 24: Action next) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Unicast\\\\\\\\Behaviors\\\\\\\\SetCurrentMessageBeingHandledBehavior.cs:line 17   at NServiceBus.BehaviorChain`1.InvokeNext(T context) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 107   at NServiceBus.BehaviorChain`1.<>c__DisplayClass5.<InvokeNext>b__2() in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 94   at NServiceBus.LoadHandlersBehavior.Invoke(IncomingContext context\', \'Comment 25: Action next) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Unicast\\\\\\\\Behaviors\\\\\\\\LoadHandlersBehavior.cs:line 45   at NServiceBus.BehaviorChain`1.InvokeNext(T context) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 107   at NServiceBus.BehaviorChain`1.<>c__DisplayClass5.<InvokeNext>b__2() in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 94   at NServiceBus.Transports.SQLServer.ReadIncomingCallbackAddressBehavior.Invoke(IncomingContext context\', \'Comment 26: Action next) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\888dd942b44bad5a\\\\\\\\src\\\\\\\\NServiceBus.SqlServer\\\\\\\\ReadIncomingCallbackAddressBehavior.cs:line 17   at NServiceBus.BehaviorChain`1.InvokeNext(T context) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 107   at NServiceBus.BehaviorChain`1.<>c__DisplayClass5.<InvokeNext>b__2() in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 94   at NServiceBus.ApplyIncomingMessageMutatorsBehavior.Invoke(IncomingContext context\', \'Comment 27: Action next) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\MessageMutator\\\\\\\\ApplyIncomingMessageMutatorsBehavior.cs:line 23   at NServiceBus.BehaviorChain`1.InvokeNext(T context) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 107   at NServiceBus.BehaviorChain`1.<>c__DisplayClass5.<InvokeNext>b__2() in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 94   at NServiceBus.ExecuteLogicalMessagesBehavior.Invoke(IncomingContext context\', \'Comment 28: Action next) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Unicast\\\\\\\\Messages\\\\\\\\ExecuteLogicalMessagesBehavior.cs:line 24   at NServiceBus.BehaviorChain`1.InvokeNext(T context) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 107   at NServiceBus.BehaviorChain`1.<>c__DisplayClass5.<InvokeNext>b__2() in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 94   at NServiceBus.CallbackInvocationBehavior.Invoke(IncomingContext context\', \'Comment 29: Action next) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Unicast\\\\\\\\Behaviors\\\\\\\\CallbackInvocationBehavior.cs:line 22   at NServiceBus.BehaviorChain`1.InvokeNext(T context) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 107   at NServiceBus.BehaviorChain`1.<>c__DisplayClass5.<InvokeNext>b__2() in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 94   at NServiceBus.DeserializeLogicalMessagesBehavior.Invoke(IncomingContext context\', \'Comment 30: Action next) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Unicast\\\\\\\\Messages\\\\\\\\DeserializeLogicalMessagesBehavior.cs:line 47   at NServiceBus.BehaviorChain`1.InvokeNext(T context) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 107   at NServiceBus.BehaviorChain`1.<>c__DisplayClass5.<InvokeNext>b__2() in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 94   at NServiceBus.ApplyIncomingTransportMessageMutatorsBehavior.Invoke(IncomingContext context\', \'Comment 31: Action next) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\MessageMutator\\\\\\\\ApplyIncomingTransportMessageMutatorsBehavior.cs:line 20   at NServiceBus.BehaviorChain`1.InvokeNext(T context) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 107   at NServiceBus.BehaviorChain`1.<>c__DisplayClass5.<InvokeNext>b__2() in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 94   at NServiceBus.SubscriptionReceiverBehavior.Invoke(IncomingContext context\', \'Comment 32: Action next) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Unicast\\\\\\\\Subscriptions\\\\\\\\MessageDrivenSubscriptions\\\\\\\\SubscriptionReceiverBehavior.cs:line 31   at NServiceBus.BehaviorChain`1.InvokeNext(T context) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 107   at NServiceBus.BehaviorChain`1.<>c__DisplayClass5.<InvokeNext>b__2() in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 94   at NServiceBus.UnitOfWorkBehavior.Invoke(IncomingContext context\', \'Comment 33: Action next) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\UnitOfWork\\\\\\\\UnitOfWorkBehavior.cs:line 42   at NServiceBus.BehaviorChain`1.InvokeNext(T context) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 107   at NServiceBus.BehaviorChain`1.<>c__DisplayClass5.<InvokeNext>b__2() in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 94   at NServiceBus.ChildContainerBehavior.Invoke(IncomingContext context\', \'Comment 34: Action next) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Unicast\\\\\\\\Behaviors\\\\\\\\ChildContainerBehavior.cs:line 17   at NServiceBus.BehaviorChain`1.InvokeNext(T context) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 107   at NServiceBus.BehaviorChain`1.<>c__DisplayClass5.<InvokeNext>b__2() in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 94   at NServiceBus.ProcessingStatisticsBehavior.Invoke(IncomingContext context\', \'Comment 35: Action next) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Monitoring\\\\\\\\ProcessingStatisticsBehavior.cs:line 23   at NServiceBus.BehaviorChain`1.InvokeNext(T context) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 107   at NServiceBus.BehaviorChain`1.Invoke() in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 52   at NServiceBus.Pipeline.PipelineExecutor.Execute[T](BehaviorChain`1 pipelineAction\', \'Comment 36: T context) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\PipelineExecutor.cs:line 129   at NServiceBus.Pipeline.PipelineExecutor.InvokePipeline[TContext](IEnumerable`1 behaviors\', \'Comment 37: TContext context) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\PipelineExecutor.cs:line 85   at NServiceBus.Pipeline.PipelineExecutor.InvokeReceivePhysicalMessagePipeline() in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\PipelineExecutor.cs:line 102   at NServiceBus.Unicast.UnicastBus.TransportMessageReceived(Object sender\', ""Comment 38: TransportMessageReceivedEventArgs e) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Unicast\\\\\\\\UnicastBus.cs:line 826   at NServiceBus.Unicast.Transport.TransportReceiver.OnTransportMessageReceived(TransportMessage msg) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Unicast\\\\\\\\Transport\\\\\\\\TransportReceiver.cs:line 411   at NServiceBus.Unicast.Transport.TransportReceiver.ProcessMessage(TransportMessage message) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Unicast\\\\\\\\Transport\\\\\\\\TransportReceiver.cs:line 344   at NServiceBus.Unicast.Transport.TransportReceiver.TryProcess(TransportMessage message) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Unicast\\\\\\\\Transport\\\\\\\\TransportReceiver.cs:line 228   at NServiceBus.Transports.SQLServer.AmbientTransactionReceiveStrategy.TryReceiveFrom(TableBasedQueue queue) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\888dd942b44bad5a\\\\\\\\src\\\\\\\\NServiceBus.SqlServer\\\\\\\\AmbientTransactionReceiveStrategy.cs:line 57{code}\'"", ""Comment 39: \'I dla change element message :{code:java}System.NullReferenceException: Object reference not set to an instance of an object.   at Evolution.DHCService.Dhc30.Handlers.ShippingNoticeElementChangedMessageHandler.FillEntity(ShippingNoticeElementChangedMessage message"", \'Comment 40: ShippingNoticeElementEntity entity) in E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\31916033\\\\\\\\DHAPPSV3-DHCSER538-JOB1\\\\\\\\Evolution.DHCService\\\\\\\\Evolution.DHCService.Dhc30\\\\\\\\Handlers\\\\\\\\ShippingNoticeElementChangedMessageHandler.cs:line 43   at Evolution.DHCService.Dhc30.Handlers.BaseMessageHandler`2.Handle(TMessage message) in E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\31916033\\\\\\\\DHAPPSV3-DHCSER538-JOB1\\\\\\\\Evolution.DHCService\\\\\\\\Evolution.DHCService.Dhc30\\\\\\\\Handlers\\\\\\\\BaseMessageHandler.cs:line 56   at lambda_method(Closure \', \'Comment 41: Object \', \'Comment 42: Object )   at NServiceBus.Unicast.MessageHandlerRegistry.Invoke(Object handler\', \'Comment 43: Object message\', \'Comment 44: Dictionary`2 dictionary) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Unicast\\\\\\\\MessageHandlerRegistry.cs:line 126   at NServiceBus.Unicast.MessageHandlerRegistry.InvokeHandle(Object handler\', \'Comment 45: Object message) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Unicast\\\\\\\\MessageHandlerRegistry.cs:line 84   at NServiceBus.LoadHandlersBehavior.<Invoke>b__1(Object handlerInstance\', \'Comment 46: Object message) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Unicast\\\\\\\\Behaviors\\\\\\\\LoadHandlersBehavior.cs:line 40   at NServiceBus.InvokeHandlersBehavior.Invoke(IncomingContext context\', \'Comment 47: Action next) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Unicast\\\\\\\\Behaviors\\\\\\\\InvokeHandlersBehavior.cs:line 24   at NServiceBus.BehaviorChain`1.InvokeNext(T context) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 107   at NServiceBus.BehaviorChain`1.<>c__DisplayClass5.<InvokeNext>b__2() in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 94   at NServiceBus.SetCurrentMessageBeingHandledBehavior.Invoke(IncomingContext context\', \'Comment 48: Action next) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Unicast\\\\\\\\Behaviors\\\\\\\\SetCurrentMessageBeingHandledBehavior.cs:line 17   at NServiceBus.BehaviorChain`1.InvokeNext(T context) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 107   at NServiceBus.BehaviorChain`1.<>c__DisplayClass5.<InvokeNext>b__2() in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 94   at NServiceBus.LoadHandlersBehavior.Invoke(IncomingContext context\', \'Comment 49: Action next) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Unicast\\\\\\\\Behaviors\\\\\\\\LoadHandlersBehavior.cs:line 45   at NServiceBus.BehaviorChain`1.InvokeNext(T context) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 107   at NServiceBus.BehaviorChain`1.<>c__DisplayClass5.<InvokeNext>b__2() in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 94   at NServiceBus.Transports.SQLServer.ReadIncomingCallbackAddressBehavior.Invoke(IncomingContext context\', \'Comment 50: Action next) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\888dd942b44bad5a\\\\\\\\src\\\\\\\\NServiceBus.SqlServer\\\\\\\\ReadIncomingCallbackAddressBehavior.cs:line 17   at NServiceBus.BehaviorChain`1.InvokeNext(T context) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 107   at NServiceBus.BehaviorChain`1.<>c__DisplayClass5.<InvokeNext>b__2() in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 94   at NServiceBus.ApplyIncomingMessageMutatorsBehavior.Invoke(IncomingContext context\', \'Comment 51: Action next) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\MessageMutator\\\\\\\\ApplyIncomingMessageMutatorsBehavior.cs:line 23   at NServiceBus.BehaviorChain`1.InvokeNext(T context) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 107   at NServiceBus.BehaviorChain`1.<>c__DisplayClass5.<InvokeNext>b__2() in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 94   at NServiceBus.ExecuteLogicalMessagesBehavior.Invoke(IncomingContext context\', \'Comment 52: Action next) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Unicast\\\\\\\\Messages\\\\\\\\ExecuteLogicalMessagesBehavior.cs:line 24   at NServiceBus.BehaviorChain`1.InvokeNext(T context) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 107   at NServiceBus.BehaviorChain`1.<>c__DisplayClass5.<InvokeNext>b__2() in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 94   at NServiceBus.CallbackInvocationBehavior.Invoke(IncomingContext context\', \'Comment 53: Action next) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Unicast\\\\\\\\Behaviors\\\\\\\\CallbackInvocationBehavior.cs:line 22   at NServiceBus.BehaviorChain`1.InvokeNext(T context) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 107   at NServiceBus.BehaviorChain`1.<>c__DisplayClass5.<InvokeNext>b__2() in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 94   at NServiceBus.DeserializeLogicalMessagesBehavior.Invoke(IncomingContext context\', \'Comment 54: Action next) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Unicast\\\\\\\\Messages\\\\\\\\DeserializeLogicalMessagesBehavior.cs:line 47   at NServiceBus.BehaviorChain`1.InvokeNext(T context) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 107   at NServiceBus.BehaviorChain`1.<>c__DisplayClass5.<InvokeNext>b__2() in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 94   at NServiceBus.ApplyIncomingTransportMessageMutatorsBehavior.Invoke(IncomingContext context\', \'Comment 55: Action next) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\MessageMutator\\\\\\\\ApplyIncomingTransportMessageMutatorsBehavior.cs:line 20   at NServiceBus.BehaviorChain`1.InvokeNext(T context) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 107   at NServiceBus.BehaviorChain`1.<>c__DisplayClass5.<InvokeNext>b__2() in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 94   at NServiceBus.SubscriptionReceiverBehavior.Invoke(IncomingContext context\', \'Comment 56: Action next) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Unicast\\\\\\\\Subscriptions\\\\\\\\MessageDrivenSubscriptions\\\\\\\\SubscriptionReceiverBehavior.cs:line 31   at NServiceBus.BehaviorChain`1.InvokeNext(T context) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 107   at NServiceBus.BehaviorChain`1.<>c__DisplayClass5.<InvokeNext>b__2() in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 94   at NServiceBus.UnitOfWorkBehavior.Invoke(IncomingContext context\', \'Comment 57: Action next) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\UnitOfWork\\\\\\\\UnitOfWorkBehavior.cs:line 42   at NServiceBus.BehaviorChain`1.InvokeNext(T context) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 107   at NServiceBus.BehaviorChain`1.<>c__DisplayClass5.<InvokeNext>b__2() in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 94   at NServiceBus.ChildContainerBehavior.Invoke(IncomingContext context\', \'Comment 58: Action next) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Unicast\\\\\\\\Behaviors\\\\\\\\ChildContainerBehavior.cs:line 17   at NServiceBus.BehaviorChain`1.InvokeNext(T context) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 107   at NServiceBus.BehaviorChain`1.<>c__DisplayClass5.<InvokeNext>b__2() in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 94   at NServiceBus.ProcessingStatisticsBehavior.Invoke(IncomingContext context\', \'Comment 59: Action next) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Monitoring\\\\\\\\ProcessingStatisticsBehavior.cs:line 23   at NServiceBus.BehaviorChain`1.InvokeNext(T context) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 107   at NServiceBus.BehaviorChain`1.Invoke() in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\BehaviorChain.cs:line 52   at NServiceBus.Pipeline.PipelineExecutor.Execute[T](BehaviorChain`1 pipelineAction\', \'Comment 60: T context) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\PipelineExecutor.cs:line 129   at NServiceBus.Pipeline.PipelineExecutor.InvokePipeline[TContext](IEnumerable`1 behaviors\', \'Comment 61: TContext context) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\PipelineExecutor.cs:line 85   at NServiceBus.Pipeline.PipelineExecutor.InvokeReceivePhysicalMessagePipeline() in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Pipeline\\\\\\\\PipelineExecutor.cs:line 102   at NServiceBus.Unicast.UnicastBus.TransportMessageReceived(Object sender\', ""Comment 62: TransportMessageReceivedEventArgs e) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Unicast\\\\\\\\UnicastBus.cs:line 826   at NServiceBus.Unicast.Transport.TransportReceiver.OnTransportMessageReceived(TransportMessage msg) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Unicast\\\\\\\\Transport\\\\\\\\TransportReceiver.cs:line 411   at NServiceBus.Unicast.Transport.TransportReceiver.ProcessMessage(TransportMessage message) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Unicast\\\\\\\\Transport\\\\\\\\TransportReceiver.cs:line 344   at NServiceBus.Unicast.Transport.TransportReceiver.TryProcess(TransportMessage message) in c:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\3206e2123f54fce4\\\\\\\\src\\\\\\\\NServiceBus.Core\\\\\\\\Unicast\\\\\\\\Transport\\\\\\\\TransportReceiver.cs:line 228   at NServiceBus.Transports.SQLServer.AmbientTransactionReceiveStrategy.TryReceiveFrom(TableBasedQueue queue) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\888dd942b44bad5a\\\\\\\\src\\\\\\\\NServiceBus.SqlServer\\\\\\\\AmbientTransactionReceiveStrategy.cs:line 57{code}\'"", ""Comment 63: \'Te błedy lecą praktycznie od wczoraj!image-2023-03-30-18-45-37-204.png!\'"", ""Comment 64: \'Hi Ewelina,Are mentioned ASNs the only ones that requires immediate repairing? Today"", \'Comment 65: we will unblock the process but it needs to be investigated in RCA tas tomorrow morning.Please\', ""Comment 66: let us know if there are more examples to correct.Regards\'"", \'Comment 67: ""*Dla\\\'T-5041/23/L\\\'* ZW-130/03/23/D ZW-137/03/23/D*Dla T-5059/23/G*ZS-1640/03/23/G*Dla T-2040/23/P*ZS-953/03/23/P ZS-950/03/23/P ZS-951/03/23/P*Dla\\\'T-2224/23/I\\\'* ZS-1076/03/23/I ZS-1077/03/23/I*Dla\\\'T-2225/23/I\\\'*ZS-1076/03/23/IZS-1077/03/23/I""\', ""Comment 68: \'SN-1202900/2023\'"", ""Comment 69: \'Can you explain which process has been unlocked to drain synchro ? \'"", ""Comment 70: \'Some of the orders have been resent and so the trips. An entries in the DHC Service database were missing for orders"", ""Comment 71: trips.list:T-2034/23/PT-2992/23/ST-120/23/JST-2994/23/ST-3775/23/MT-4997/23/LT-3567/23/ŁT-2039/23/PT-4992/23/LT-2040/23/PT-5026/23/GT-2226/23/IT-2041/23/PT-2176/23/IT-2453/23/DT-2453/23/DT-5059/23/GT-2201/23/ICan you verified again and send cases for current missing data.\'"", \'Comment 72: ""{code:java}  SELECT *  FROM [Evolution_DHCountry].[dbo].[ShippingNotices] sh  left join [Evolution_DHCService].[dbo].[ShippingNotices] shc on sh.id=shc.Id  where shc.id is  null and sh.IssueDate>=\\\'2023-03-29 00:00\\\' and sh.Status=3{code}{code:java}SELECT * FROM [Evolution_DHCountry].[dbo].[Orders] c left join [Evolution_DHCService].[dbo].[Orders] e on c.id=e.id  where c.CreateDate>=\\\'2023-03-25 00:00:00.000\\\' and e.id is null and c.DocumentNumerator_Year=2023 and c.DocumentNumerator_Month=3 and c.Status in(5,6) and c.OrderType=2{code}""\', ""Comment 73: \'What these shipping notices have in common and what caused problem with them? \'"", ""Comment 74: \'They were missing in DHCService"", ""Comment 75: and as for the reason RCA should be created for analysis.\'"", ""Comment 76: \'RCa is created under :DGS-8881\']""]\nRelated Issues:\n[\'DGS-8881\', \'DGS-8965\']\n\n### End'}"
154,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8878\n\n### Instruction:\nMigration files for customer 008093\n\n### Response:\n[""Comment 1: [\'[^AA - PAS_Migration_PURCHASEINVOICE_workfile_Faber.xlsx] _(126 kB)_[^AA - PAS_Migration_SALESINVOICE_workfile_Faber.xlsx] _(603 kB)_\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'[~mbovene@deheus.com],the invoices have been migrated into PROD Intense environment.You can verify it.Best regards,Grzegorz\'"", ""Comment 4: \'Can be closed.\']""]\nRelated Issues:\n[]\n\n### End'}"
155,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8877\n\n### Instruction:\nThere is analysis of procedure for calculating technical results in MAS NL (in MAS BE it\'s similar, but sequence of generating PI and SI from SR is different)\r\n \xa0[^Technical Results.xlsx]\r\n\r\n\xa0\r\n|\xa0|\xa0|Documents involved in calculations|\xa0Documents involved in calculations|\xa0Documents involved in calculations|\r\n|Name|Value selected from documents|SR|PI|SI|\r\n|Deliver date DOC\'s|PI, SI|\xa0|x|x|\r\n|Deliver day broilers first loaders|PI|x|x|x|\r\n|Delivery date all loaders|PI|x|x|x|\r\n|Average weight first loaders|SR, PI|x|x|x|\r\n|Weight of all loaders (in kg)|SR|x|\xa0|\xa0|\r\n|Disapproves all loaders (in kg)|SR|x|\xa0|\xa0|\r\n|Average weight all loaders|SR, PI|x|x|x|\r\n|Total value of all loaders|PI|x|x|x|\r\n|Numbers of all loaders (quantity)|SR|x|\xa0|\xa0|\r\n|m2|Customer card|\xa0|\xa0|\xa0|\r\n|Average weight in gram|SR, PI|x|x|x|\r\n|Number of DOC\'s|PI, SI|\xa0|x|x|\r\n|Total value of DOC\'s|PI, SI|\xa0|x|x|\r\n|Total weight Feed (in kg)|PI, SI, Feed sale|\xa0|x|x|\r\n|Total value Feed\xa0|PI, SI, Feed sale|\xa0|x|x|\r\n|Numbers of first loaders (quantity)|SR|x|\xa0|\xa0|\r\n|Weight of first loaders (in kg)|SR|x|\xa0|\xa0|\r\n|Disapproves first loaders (in kg)|SR|x|\xa0|\xa0|\r\n|Total value of first loaders|PI|x|x|x|\r\n|Delivery date previous round|PI|x|x|x|\r\n|Dropout percentage|SR, PI, SI|x|x|x|\r\n|Feed conversion netto|SR, PI, SI, Feed sale|x|x|x|\r\n|Feed conversion 1.500 gram|SR, PI, SI, Feed sale|x|x|x|\r\n|Maximum days of living|PI, SI|x|x|x|\r\n|Average days of living|SR, PI, SI|x|x|x|\r\n|Growth per day (in grams):|SR, PI, SI|x|x|x|\r\n|Production number|SR, PI, SI|x|x|x|\r\n|Feed profit per broiler|SR, PI, SI, Feed sale|x|x|x|\r\n|First Load percentage|SR|x|\xa0|\xa0|\r\n|Average price delivered DOC\'s|PI, SI|\xa0|x|x|\r\n|Average price delivered broilers|PI, SR|x|x|x|\r\n|Average price feed per 100 kg|PI, SI, Feed sale|\xa0|x|x|\r\n|Feedcost / kg. broilers bruto 1500 gr|SR, PI, SI, Feed sale|x|x|x|\r\n|Feedcost / kg. broilers netto|SR, PI, SI, Feed sale|x|x|x|\r\n|Feedcost / kg. broilers netto|SR, PI, SI, Feed sale|x|x|x|\r\n|Feed use per delivered broiler per gram per day|SR, PI, SI, Feed sale|x|x|x|\r\n|Startfeed per delivered DOC\'s per gram|PI, SI, Feed sale|\xa0|x|x|\r\n|Fase 2 feed per delivered DOC\'s per gram|PI, SI, Feed sale|\xa0|x|x|\r\n|Fase 3 feed per delivered DOC\'s per gram|PI, SI, Feed sale|\xa0|x|x|\r\n|Fase 4 feed per delivered DOC\'s per gram|PI, SI, Feed sale|\xa0|x|x|\r\n|Percentage Wheat|PI, SI, Feed sale|\xa0|x|x|\r\n|Amount of DOC\'s per m2|PI, SI, Customer card|\xa0|x|x|\r\n|Net Weight per delivered broilers per m2|SR, Customer card|x|\xa0|\xa0|\r\n|Saldo per m2|PI, SI, Feed sale, Loan payment, Customer card|\xa0|x|x|\r\n|Saldo /\xa0 m2 / day|SR, PI, SI, Feed sale, Loan payment, Customer card|x|x|x|\r\n|Feed Profit / m2 / day|PI, SI, Feed sale|\xa0|x|x|\r\n|Percentage Corn|PI, SI, Feed sale|\xa0|x|x|\r\n|Average price delivered broilers per kg|PI, SR|x|x|x|\r\n|Net weight per delivered broilers m2 AL|SR, Customer card|x|\xa0|\xa0|\r\n|Age first loaders|SR|x|\xa0|\xa0|\r\n|Age all loaders|SR|x|\xa0|\xa0|\r\n|Hakdermatitus|SR|x|\xa0|\xa0|\r\n|Voerprogramma|Round|\xa0|\xa0|\xa0|\r\n|Feed profit|PI, SI, Feed sale|x|x|x|\n\n### Response:\n[""Comment 1: [\'[^Technical Results.xlsx]\']""]\nRelated Issues:\n[\'DGS-8732\', \'DGS-8883\', \'DGS-8215\', \'DGS-8325\', \'DGS-8641\', \'DGS-8675\', \'DGS-8714\']\n\n### End'}"
156,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8876\n\n### Instruction:\nProśba o usunięcie dokumentu AM 00004/2023/03 – za duża liczba rekordów.\r\n\r\nCzy mamy jakieś rozwiązanie z poziomu usera na tego typu błędy na przyszłość?\n\n### Response:\n[""Comment 1: [\'Documenthas been discarded\'"", ""Comment 2: \'What about 2nd question?\'"", ""Comment 3: \'we will back with answer. Can I lower the priority ?\'"", ""Comment 4: \'Ofcourse \'"", ""Comment 5: \'Unfortunatelly there is no solution from user side. Only from database.\'"", ""Comment 6: \'Could you please confirm if we can close this task?Regards\'"", ""Comment 7: \'Sure\']""]\nRelated Issues:\n[]\n\n### End'}"
157,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8875\n\n### Instruction:\nPlease remove/disable additional technology SN506159 from DHC Compound.\r\n\r\nPlease do the same for SN506247, as requested in ticket DGS-8867, this is getting urgent.\r\n\r\nRegards,\r\nRob.\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Hi Rob,I have increased Priority for DGS-8867,so working on both.Regards\'"", ""Comment 3: \'SN506159 has been deactivated"", ""Comment 4: please verify.Regards\'"", ""Comment 5: \'Thank you for your support"", ""Comment 6: the ticket can be closed.Regards,Rob.\'"", ""Comment 7: \'This additional tech is in hindsight still active.Could you please have another look at it?Regards,Rob.\'"", ""Comment 8: \'Please"", ""Comment 9: check now.Regards\'"", ""Comment 10: \'Great"", ""Comment 11: is inactive now.Thanks again for the support.\']""]\nRelated Issues:\n[]\n\n### End'}"
158,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8874\n\n### Instruction:\nGood morning, since middle of March the integration of the data between ERP and DHC is not working properly, we cannot sent the data from ERP to DH Apps: orders and master data, please check and fix the communication. We are getting the following message from the interface AIS:\r\nPlugin return message: ERROR sending datacontract to webmethods.io. Details : Http status 500 (Internal Server Error): failed parsing retrieved response object. -\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 3: ""Calling: DhpWEBUI...System.NotSupportedException: The response content cannot be parsed because the Internet Explorer engine is not available\', \'Comment 4: or Internet Explorer\\\'s first-launch configuration is not complete. Specify the UseBasicParsing parameter and try again. at Microsoft.PowerShell.Commands.WebRequestPSCmdlet.VerifyInternetExplorerAvailable(Boolean checkComObject) at Microsoft.PowerShell.Commands.InvokeWebRequestCommand.ProcessResponse(WebResponse response) at Microsoft.PowerShell.Commands.WebRequestPSCmdlet.ProcessRecord()PS D:\\\\\\\\kotrak>""\', ""Comment 5: \'Dear Katarzyna,Please"", ""Comment 6: verify if it is working now.Regards\'"", ""Comment 7: \'Hello"", ""Comment 8: can you inform what was not working? In meantime we will push data to synchronise. \'"", ""Comment 9: \'Report server was stopped again and not connected to db.Please"", ""Comment 10: let me know if synchronisation is working now\'"", ""Comment 11: \'Hi"", \'Comment 12: we have verified if the data/documents are sent to DHC\', \'Comment 13: and unfortunately they are not. We still have SO/PO documents stuck in the integration\', ""Comment 14: and the message is: Plugin return message: ERROR sending datacontract to webmethods.io. Details : Http status 500 (Internal Server Error): failed parsing retrieved response object. -  As example: SO000417/SO000455/SO000432/SO000420/SO259. PO000423/PO000421/PO000413/PO000427... !image-1!\'"", ""Comment 15: \'it is not working \'"", \'Comment 16: ""DlaPO000423 i PO000421{code:java}<PurchOrder>PO000423</PurchOrder> <PurchOrder>PO000423</PurchOrder> Line 8074: <SourceInfo>Intake_20235228105223000_PO000423</SourceInfo> Line 8078: ObjectType: OrderObject\', \'Comment 17: Id: Id: PO000423\', \'Comment 18: FieldName: OrderType\', ""Comment 19: Message: Realization date can\'t be earlier than issue date Line 8081: ObjectType: OrderObject"", \'Comment 20: Id: Id: PO000423\', \'Comment 21: FieldName: OrderType\', ""Comment 22: Message: Realization date can\'t be earlier than issue date Line 8084: ObjectType: OrderObject"", \'Comment 23: Id: Id: PO000423\', \'Comment 24: FieldName: OrderType\', ""Comment 25: Message: Realization date can\'t be earlier than issue date Line 16217:   <PurchOrder>PO000423</PurchOrder>{code}{code:java}2023-03-30 13:11:49,649 [28] DEBUG Evolution.DHCERPService.ImplementationRestWoW.Savers.DataContractSaver`2 [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\18317313\\\\\\\\DHAPPSV3-DHCER400-JOB1\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.ImplementationRestWoW\\\\\\\\Savers\\\\\\\\DataContractSaver.cs:39] - Saving IntakeDataContractDeHeusWoW2023-03-30 13:11:49,664 [28] ERROR Evolution.DHCERPService.Service.BaseSaveService`1 [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\18317313\\\\\\\\DHAPPSV3-DHCER400-JOB1\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.Service\\\\\\\\BaseSaveService.cs:66] - Validation Exception:Exception of type \'Evolution.DHCERPService.Service.Interface.ExceptionHandling.DataValidationException\' was thrown.ObjectType: OrderObject"", \'Comment 26: Id: Id: PO000423\', \'Comment 27: FieldName: OrderType\', ""Comment 28: Message: Realization date can\'t be earlier than issue date2023-03-30 13:11:49,664 [28] ERROR Evolution.DHCERPService.Service.BaseSaveService`1 [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\18317313\\\\\\\\DHAPPSV3-DHCER400-JOB1\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.Service\\\\\\\\BaseSaveService.cs:75] - Validation Exception:Exception of type \'Evolution.DHCERPService.Service.Interface.ExceptionHandling.DataValidationException\' was thrown.ObjectType: OrderObject"", \'Comment 29: Id: Id: PO000423\', \'Comment 30: FieldName: OrderType\', ""Comment 31: Message: Realization date can\'t be earlier than issue date2023-03-30 13:11:49,664 [28] ERROR Evolution.DHCERPService.ImplementationRestWoW.Savers.DataContractSaver`2 [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\18317313\\\\\\\\DHAPPSV3-DHCER400-JOB1\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.ImplementationRestWoW\\\\\\\\Savers\\\\\\\\DataContractSaver.cs:49] - Validation Exception:Exception of type \'Evolution.DHCERPService.Service.Interface.ExceptionHandling.DataValidationException\' was thrown.ObjectType: OrderObject"", \'Comment 32: Id: Id: PO000423\', \'Comment 33: FieldName: OrderType\', \'Comment 34: Message: Realization date can\\\'t be earlier than issue date{code}""\', \'Comment 35: ""These are in DHC and DHP now after restart of Business Platform: PO000423/PO000421/PO000413However\', ""Comment 36: there are dozens Ordres that do not arrive to Pant with error message:Realization date can\'t be earlier than issue datefor example: PO000438"", \'Comment 37: 446\', \'Comment 38: 442\', \'Comment 39: 448\', \'Comment 40: 447\', \'Comment 41: 449\', \'Comment 42: 443\', \'Comment 43: 441\', \'Comment 44: 439\', \'Comment 45: etcNo wonder if we have examples like that!image-2023-03-30-17-29-43-216.png!That is why validation failed for Purchase Orders [^image-2023-03-30-17-29-43-216.png]As I already mentioned\', \'Comment 46: I have restarted business platform. Found nothing unusual in logs so far. Could you please\', \'Comment 47: resend Sales Order from ERP to DHC once again?Regards""\', ""Comment 48: \'Tylko to jest dziwne"", ""Comment 49: bo Sales Ordery z tak zrobionymi datami puszcza:!image-2023-03-30-17-58-46-571.png!!image-2023-03-30-17-58-23-953.png!\'"", ""Comment 50: \'We are fixing the issue on ERP side \'"", ""Comment 51: \'Shall we close this task?\'"", ""Comment 52: \'Actually you can close this ticket"", \'Comment 53: but currently I have problem with only one PO-368 - error 500 occurs still. If you can help to resolve that PO-368 within\', ""Comment 54:  then we can close the task. \'"", ""Comment 55: \'Hi,Are you sure that it isPO-368? I cannot see this document in both appsRegards!image-2023-04-20-08-16-26-353.png!!image-2023-04-20-08-17-03-161.png!\'"", ""Comment 56: \'!image-2023-04-20-08-21-27-821.png!\'"", ""Comment 57: \'indeed the PO-368 is not in DH Apps"", \'Comment 58: and we do not know why\', \'Comment 59: the message Error-500 does not explain too much\', \'Comment 60: can you investigate deeper\', \'Comment 61: please\', ""Comment 62: or shall we look inside ERP? \'"", \'Comment 63: ""Hi,Could you please resendPO-368 and provide me with it\\\'s created date and issue date?Regards""]\']\nRelated Issues:\n[]\n\n### End'}"
159,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8873\n\n### Instruction:\nFor order SOBE000018737 the one-time recipes are not created in DHC: As far we can see orders are send with additions from Webmethods. Please check\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Please resent an order from ERP.\'"", ""Comment 3: \'Just resend 702260\'"", ""Comment 4: \'Sorry"", ""Comment 5: just resend \'"", ""Comment 6: \'SOBE000018737 \'"", ""Comment 7: \'!afbeelding!\'"", ""Comment 8: \' !screenshot-1! \'"", ""Comment 9: \'Please resent an order from ERP.In dhc were two the same additional technology with product definition=1one of them has been archived. !screenshot-2! \'"", \'Comment 10: ""Oke\', \'Comment 11: I understand; Order was now cancelled and a new order will be created. i\\\'ll check that one if it is processed correct""\', ""Comment 12: \'Thank you.\'"", ""Comment 13: \'[[DHC 3.0] missing one-time/onetime recipe for SO"", ""Comment 14: brak onetime receptury dla zamówienia. |onenote:https://kotrak.sharepoint.com/sites/erpasysta/Shared%20Documents/Baza%20wiedzy/Baza%20Wiedzy%20-%20ERPSD/Klienci/DEHEUS/DEHEUS%20APPLICATIONS/Holandia%20Premix%20i%20AS400/Baz%20wiedzy%20z%20AS400.one#%5bDHC%203.0%5d%20missing%20one-time/onetime%20recipe%20for&section-id=\\\\\\\\{9BB564BA-0B58-4580-B9E0-F3CF9D6D80A7}&page-id=\\\\\\\\{DEE5C2FD-8FB2-4F3E-88D7-1E04278DDE76}&end] ([Widok sieci Web|https://kotrak.sharepoint.com/sites/erpasysta/_layouts/OneNote.aspx?id=%2Fsites%2Ferpasysta%2FShared%20Documents%2FBaza%20wiedzy%2FBaza%20Wiedzy%20-%20ERPSD&wd=target%28Klienci%2FDEHEUS%2FDEHEUS%20APPLICATIONS%2FHolandia%20Premix%20i%20AS400%2FBaz%20wiedzy%20z%20AS400.one%7C9BB564BA-0B58-4580-B9E0-F3CF9D6D80A7%2F%5BDHC%203.0%5D%20missing%20one-time%5C%2Fonetime%20recipe%20for%7CDEE5C2FD-8FB2-4F3E-88D7-1E04278DDE76%2F%29])\'"", ""Comment 15: \'ticket can be closed\']""]\nRelated Issues:\n[]\n\n### End'}"
160,"{'prompt': ""Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8872\n\n### Instruction:\nDear ,\r\n\r\nPlease help to check this issue in Hai Phong 2 plant (0436) . PLR 4361240323076 receipt both bulk and batch.\r\n\n\n### Response:\n['Comment 1: []']\nRelated Issues:\n['DGS-8829']\n\n### End""}"
161,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8871\n\n### Instruction:\nGood morning, since middle of March the integration of the data between ERP and DHC is not working properly, we cannot sent the data from ERP to DH Apps: orders and master data, please check and fix the communication. We are getting the following message from the interface AIS: \r\nPlugin return message: ERROR sending datacontract to webmethods.io. Details : Http status 500 (Internal Server Error): failed parsing retrieved response object. - \r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'hi"", \'Comment 4: any news? this is urgent\', \'Comment 5: people are waiting for the Sales Orders\', ""Comment 6: adn Purchase Orders to register daily operations. \'"", \'Comment 7: ""Hi,Issue has been reported as a service request with Priority P3. If this is really urgent as commented below\', ""Comment 8: why didn\'t you raise an Incident with highier Priority from the very beginning?AsDGS-8874 has been raised right now"", \'Comment 9: I am closing SR.Regards""\', ""Comment 10: \'Thank you"", ""Comment 11: please close this ticket. \']""]\nRelated Issues:\n[]\n\n### End'}"
162,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8870\n\n### Instruction:\nHi,\r\nPlease help to check this issue in Can Tho Plant ( 0437) .\r\nCan not release this lot ( 140123L00123-271022CHN-MEN ).\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 3: \\\'2023-03-30 08:16:45 (00d6e63e-fc48-49bf-8425-e725e9a0a83d/Plant.WMS.BusinessLogic/VNPCT-TS01/35264/224) [Error] Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware - Error during request{ ""scheme"": ""http""\', \'Comment 4: ""host"": { ""Value"": ""10.84.165.11:85""\', \'Comment 5: ""HasValue"": true\', \'Comment 6: ""Host"": ""10.84.165.11""\', \'Comment 7: ""Port"": 85 }\', \'Comment 8: ""path"": ""/api/WarehouseStocktaking/registerUnitLoadStocktaking""\', \'Comment 9: ""queryString"": []\', \'Comment 10: ""requestBody"": ""\\\\\\\\{\\\\\\\\""unitLoadStocktakingData\\\\\\\\"":[{\\\\\\\\""unitLoadId\\\\\\\\"":\\\\\\\\""6566df10-c81f-4057-aa0d-0c1071ac8d1f\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":0}}]}""}.Refit.ApiException: Response status code does not indicate success: 500 (Internal Server Error).\\\'\', ""Comment 11: \'could you please verify it that problem still occurs?\'"", ""Comment 12: \'Hello,Yes"", ""Comment 13: this problem still occurs. User can not stocktaking this lot .\'"", ""Comment 14: \'Hi,tomorrow will stock count"", ""Comment 15: so please solve this error today. Thank u.\'"", ""Comment 16: \'!image-2023-03-31-15-25-33-690.png!\'"", ""Comment 17: \'{code:java}2023-03-31 20:31:38 (bff12ead-5bd7-4ba7-a19b-65fb990f62e5/Plant.Stock.BusinessLogic/VNPCT-TS01/37472/254) [Error] Kotrak.Common.Infrastructure.ICommandRunEnvironment - Error during Void Run[CompensateRegisterStockUnitStocktakingCommand](Plant.Stock.BusinessLogic.Application.Interfaces.Stocktaking.Commands.CompensateRegisterStockUnitStocktakingCommand) methodSystem.ArgumentNullException: Value cannot be null.Parameter name: value at Newtonsoft.Json.JsonConvert.DeserializeObject(String value"", \'Comment 18: Type type\', \'Comment 19: JsonSerializerSettings settings) at Newtonsoft.Json.JsonConvert.DeserializeObject[T](String value\', \'Comment 20: JsonSerializerSettings settings) at Plant.Stock.BusinessLogic.Application.Stocktaking.StocktakingService.CompensateRegisterStockUnitStocktaking(Guid correlationId) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Application\\\\\\\\Stocktaking\\\\\\\\StocktakingService.cs:line 274 at Plant.Stock.BusinessLogic.Application.Stocktaking.CommandHandlers.CompensateRegisterStockUnitStocktakingCommandHandler.Handle(CompensateRegisterStockUnitStocktakingCommand command) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Application\\\\\\\\Stocktaking\\\\\\\\CommandHandlers\\\\\\\\CompensateRegisterStockUnitStocktakingCommandHandler.cs:line 38 at Kotrak.Common.Infrastructure.Commands.CommandEnvironment.Run[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.IntercontextEventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.EventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.ValidationCommandEnvironmentDecorator.Run[TCommand](TCommand command) at Castle.DynamicProxy.AbstractInvocation.Proceed() at Kotrak.Common.Infrastructure.Interceptors.LoggingInterceptor`1.Intercept(IInvocation invocation)2023-03-31 20:31:38 (null/Plant.Stock.BusinessLogic/VNPCT-TS01/37472/237) [Error] Serilog.AspNetCore.RequestLoggingMiddleware - HTTP ""POST"" ""/api/stocktaking/compensateRegisterStockUnitStocktaking"" responded 500 in 20.4732 ms{code}\\\'\', \'Comment 21: \\\'Request WMSA{code:java}2023-03-31 20:31:38 (bff12ead-5bd7-4ba7-a19b-65fb990f62e5/Plant.WMS.BusinessLogic/VNPCT-TS01/39200/247) [Error] Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware - Error during request{  ""scheme"": ""http""\', \'Comment 22:  ""host"": {    ""Value"": ""10.84.165.11:85""\', \'Comment 23:    ""HasValue"": true\', \'Comment 24:    ""Host"": ""10.84.165.11""\', \'Comment 25:    ""Port"": 85  }\', \'Comment 26:  ""path"": ""/api/WarehouseStocktaking/registerUnitLoadStocktaking""\', \'Comment 27:  ""queryString"": []\', \'Comment 28:  ""requestBody"": ""{\\\\\\\\""unitLoadStocktakingData\\\\\\\\"":[{\\\\\\\\""unitLoadId\\\\\\\\"":\\\\\\\\""6566df10-c81f-4057-aa0d-0c1071ac8d1f\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":0}}]}""}.Refit.ApiException: Response status code does not indicate success: 500 (Internal Server Error).   at Refit.RequestBuilderImplementation.<>c__DisplayClass20_0.<<BuildVoidTaskFuncForMethod>b__0>d.MoveNext() in d:\\\\\\\\a\\\\\\\\1\\\\\\\\s\\\\\\\\Refit\\\\\\\\RequestBuilderImplementation.cs:line 773--- End of stack trace from previous location where exception was thrown ---   at Plant.WMS.BusinessLogic.Infrastructure.ContextIntegration.ApiServices.StockEngine.StockEngineExternalApi.CompensateRegisterStockUnitStocktaking(Guid correlationId) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Infrastructure.ContextIntegration\\\\\\\\ApiServices\\\\\\\\StockEngine\\\\\\\\StockEngineExternalApi.cs:line 91   at Castle.Proxies.Invocations.IStockEngineExternalApi_CompensateRegisterStockUnitStocktaking.InvokeMethodOnTarget()   at Castle.DynamicProxy.AbstractInvocation.Proceed()   at Kotrak.Common.Infrastructure.Interceptors.ApiReferenceExceptionInterceptor.Intercept(IInvocation invocation)   at Castle.DynamicProxy.AbstractInvocation.Proceed()   at Plant.WMS.BusinessLogic.Application.WarehouseStocktaking.Handlers.RegisterUnitLoadStocktakingCommandHandler.<>c__DisplayClass6_0.<Handle>b__2() in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Application\\\\\\\\WarehouseStocktaking\\\\\\\\Handlers\\\\\\\\RegisterUnitLoadStocktakingCommandHandler.cs:line 52   at Plant.WMS.BusinessLogic.Application.Workflows.WorkflowRunner.Run(Workflow workflow) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Application\\\\\\\\Workflows\\\\\\\\WorkflowRunner.cs:line 21   at Plant.WMS.BusinessLogic.Application.WarehouseStocktaking.Handlers.RegisterUnitLoadStocktakingCommandHandler.Handle(RegisterUnitLoadStocktakingCommand command) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Application\\\\\\\\WarehouseStocktaking\\\\\\\\Handlers\\\\\\\\RegisterUnitLoadStocktakingCommandHandler.cs:line 60   at Kotrak.Common.Infrastructure.Commands.CommandEnvironment.Run[TCommand](TCommand command)   at Kotrak.Common.Infrastructure.Commands.Decorators.IntercontextEventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command)   at Kotrak.Common.Infrastructure.Commands.Decorators.EventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command)   at Kotrak.Common.Infrastructure.Commands.Decorators.ValidationCommandEnvironmentDecorator.Run[TCommand](TCommand command)   at Castle.DynamicProxy.AbstractInvocation.Proceed()   at Kotrak.Common.Infrastructure.Interceptors.LoggingInterceptor`1.Intercept(IInvocation invocation)   at Castle.DynamicProxy.AbstractInvocation.Proceed()   at Kotrak.Common.Infrastructure.Commands.Decorators.HistoryGateDecorator.Dispatch[TCommand](TCommand command)   at Plant.WMS.BusinessLogic.Infrastructure.Api.Controllers.WarehouseStocktakingController.RegisterUnitLoadStocktaking(RegisterUnitLoadStocktakingViewModel viewModel) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Infrastructure.Api\\\\\\\\Controllers\\\\\\\\WarehouseStocktakingController.cs:line 151   at lambda_method(Closure \', \'Comment 29: Object \', \'Comment 30: Object[] )   at Microsoft.Extensions.Internal.ObjectMethodExecutor.Execute(Object target\', \'Comment 31: Object[] parameters)   at Microsoft.AspNetCore.Mvc.Internal.ActionMethodExecutor.SyncActionResultExecutor.Execute(IActionResultTypeMapper mapper\', \'Comment 32: ObjectMethodExecutor executor\', \'Comment 33: Object controller\', \'Comment 34: Object[] arguments)   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.InvokeActionMethodAsync()   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.InvokeNextActionFilterAsync()   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.Rethrow(ActionExecutedContext context)   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.Next(State& next\', \'Comment 35: Scope& scope\', \'Comment 36: Object& state\', \'Comment 37: Boolean& isCompleted)   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.InvokeInnerFilterAsync()   at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.InvokeNextResourceFilter()   at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.Rethrow(ResourceExecutedContext context)   at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.Next(State& next\', \'Comment 38: Scope& scope\', \'Comment 39: Object& state\', ""Comment 40: Boolean& isCompleted)   at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.InvokeFilterPipelineAsync()   at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.InvokeAsync()   at Microsoft.AspNetCore.Builder.RouterMiddleware.Invoke(HttpContext httpContext)   at Microsoft.AspNetCore.StaticFiles.StaticFileMiddleware.Invoke(HttpContext context)   at Swashbuckle.AspNetCore.SwaggerUI.SwaggerUIIndexMiddleware.Invoke(HttpContext httpContext)   at Swashbuckle.AspNetCore.Swagger.SwaggerMiddleware.Invoke(HttpContext httpContext)   at Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware.Invoke(HttpContext httpContext){code}\'"", \'Comment 41: \\\'LOG LOG WMSa{code:java}2023-03-31 20:31:38 (bff12ead-5bd7-4ba7-a19b-65fb990f62e5/Plant.WMS.BusinessLogic/VNPCT-TS01/39200/247) [Error] Kotrak.Common.Infrastructure.ICommandRunEnvironment - Error during Void Run[RegisterUnitLoadStocktakingCommand](Plant.WMS.BusinessLogic.Application.Interfaces.WarehouseStocktaking.RegisterUnitLoadStocktakingCommand) methodRefit.ApiException: Response status code does not indicate success: 500 (Internal Server Error).   at Refit.RequestBuilderImplementation.<>c__DisplayClass20_0.<<BuildVoidTaskFuncForMethod>b__0>d.MoveNext() in d:\\\\\\\\a\\\\\\\\1\\\\\\\\s\\\\\\\\Refit\\\\\\\\RequestBuilderImplementation.cs:line 773--- End of stack trace from previous location where exception was thrown ---   at Plant.WMS.BusinessLogic.Infrastructure.ContextIntegration.ApiServices.StockEngine.StockEngineExternalApi.CompensateRegisterStockUnitStocktaking(Guid correlationId) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Infrastructure.ContextIntegration\\\\\\\\ApiServices\\\\\\\\StockEngine\\\\\\\\StockEngineExternalApi.cs:line 91   at Castle.Proxies.Invocations.IStockEngineExternalApi_CompensateRegisterStockUnitStocktaking.InvokeMethodOnTarget()   at Castle.DynamicProxy.AbstractInvocation.Proceed()   at Kotrak.Common.Infrastructure.Interceptors.ApiReferenceExceptionInterceptor.Intercept(IInvocation invocation)   at Castle.DynamicProxy.AbstractInvocation.Proceed()   at Plant.WMS.BusinessLogic.Application.WarehouseStocktaking.Handlers.RegisterUnitLoadStocktakingCommandHandler.<>c__DisplayClass6_0.<Handle>b__2() in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Application\\\\\\\\WarehouseStocktaking\\\\\\\\Handlers\\\\\\\\RegisterUnitLoadStocktakingCommandHandler.cs:line 52   at Plant.WMS.BusinessLogic.Application.Workflows.WorkflowRunner.Run(Workflow workflow) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Application\\\\\\\\Workflows\\\\\\\\WorkflowRunner.cs:line 21   at Plant.WMS.BusinessLogic.Application.WarehouseStocktaking.Handlers.RegisterUnitLoadStocktakingCommandHandler.Handle(RegisterUnitLoadStocktakingCommand command) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Application\\\\\\\\WarehouseStocktaking\\\\\\\\Handlers\\\\\\\\RegisterUnitLoadStocktakingCommandHandler.cs:line 60   at Kotrak.Common.Infrastructure.Commands.CommandEnvironment.Run[TCommand](TCommand command)   at Kotrak.Common.Infrastructure.Commands.Decorators.IntercontextEventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command)   at Kotrak.Common.Infrastructure.Commands.Decorators.EventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command)   at Kotrak.Common.Infrastructure.Commands.Decorators.ValidationCommandEnvironmentDecorator.Run[TCommand](TCommand command)   at Castle.DynamicProxy.AbstractInvocation.Proceed()   at Kotrak.Common.Infrastructure.Interceptors.LoggingInterceptor`1.Intercept(IInvocation invocation)2023-03-31 20:31:38 (null/Plant.WMS.BusinessLogic/VNPCT-TS01/39200/178) [Error] Serilog.AspNetCore.RequestLoggingMiddleware - HTTP ""POST"" ""/api/WarehouseStocktaking/registerUnitLoadStocktaking"" responded 500 in 58.6384 ms{code}\\\'\', ""Comment 42: \'!image-2023-03-31-16-31-26-661.png!!image-2023-03-31-16-32-16-068.png!!image-2023-03-31-16-32-34-850.png!\'"", ""Comment 43: \'[[DHP 3.0] Brak unit loadu"", ""Comment 44: na stocku jest|onenote:https://kotrak.sharepoint.com/sites/erpasysta/Shared%20Documents/Baza%20wiedzy/Baza%20Wiedzy%20-%20ERPSD/Klienci/DEHEUS/DEHEUS%20APPLICATIONS/Brazil/Baza%20wiedzy.one#%5bDHP%203.0%5d%20Brak%20unit%20loadu,%20na%20stocku%20jest&section-id=\\\\\\\\{05DF1439-683C-45FE-8260-61E2EC66DC91}&page-id=\\\\\\\\{961E2282-2E7C-47A8-B946-33764D357518}&end] ([Widok sieci Web|https://kotrak.sharepoint.com/sites/erpasysta/_layouts/OneNote.aspx?id=%2Fsites%2Ferpasysta%2FShared%20Documents%2FBaza%20wiedzy%2FBaza%20Wiedzy%20-%20ERPSD&wd=target%28Klienci%2FDEHEUS%2FDEHEUS%20APPLICATIONS%2FBrazil%2FBaza%20wiedzy.one%7C05DF1439-683C-45FE-8260-61E2EC66DC91%2F%5BDHP%203.0%5D%20Brak%20unit%20loadu%2C%20na%20stocku%20jest%7C961E2282-2E7C-47A8-B946-33764D357518%2F%29])\'"", ""Comment 45: \'Please"", ""Comment 46: try to release now.Regards\'"", ""Comment 47: \'Hi,Today"", ""Comment 48: we are still facing this problem with the two lots below. So how to fix it?Lot number : 030223L00323-311223CHN-EPP and 070323L00523-230123CHN-EPP!image-1!\'"", ""Comment 49: \'437-W0023G!image-2023-04-03-07-36-20-333.png!437-W0020V!image-2023-04-03-07-37-52-645.png!\'"", ""Comment 50: \'!image-2023-04-03-07-48-37-070.png!!image-2023-04-03-07-49-09-330.png!\'"", ""Comment 51: \'8CD999E9-1565-4AC3-A772-93936E9F3B9A\'"", ""Comment 52: \'For barcode437-W0023G please try to release"", ""Comment 53: it should be fine now.\'"", ""Comment 54: \'Regarding production070323L00523-230123CHN-EPP"", \'Comment 55: barcode 437-W0020V\', \'Comment 56: I cannot recreate error\', ""Comment 57: could you please send a screenshot?Regards\'"", ""Comment 58: \'Hi.I tried to increase /or decrease this lot"", ""Comment 59: but the system gave an error!image-2!!image-3!\'"", ""Comment 60: \'!image-2023-04-03-10-08-21-755.png!\'"", \'Comment 61: \\\'2023-04-03 14:16:46 (null/Plant.WMS.BusinessLogic/VNPCT-TS01/24492/201) [Error] Serilog.AspNetCore.RequestLoggingMiddleware - HTTP ""POST"" ""/api/WarehouseStocktaking/registerUnitLoadStocktaking"" responded 500 in 37.4843 ms\\\'\', ""Comment 62: \'!image-2023-04-03-10-22-43-091.png!\'"", ""Comment 63: \'!image-2023-04-03-10-48-00-280.png!\'"", ""Comment 64: \'na stocku barcode jest do itema widocznego na delivery!image-2023-04-03-10-50-50-396.png!\'"", \'Comment 65: ""w wmsselect itemid,* from UnitLoads where barcode like \\\'437-W0020v\\\' and ItemId=\\\'DA4A7DD7-BE1A-4E66-AB93-4DAF680C29EC\\\'ten barcode jest przypisany do innegoitema niz jest na deliveryi inny niz dla barcode na stocku""\', ""Comment 66: \'Could you please provide more details barcode 437-w0020v on WMS module is linked to 91C5006-05/8-B40not for item3201050. ( in stock it is correct)Could you bring back infoamtion how it was proceed"", \'Comment 67: did you changed something from database\', ""Comment 68: if this barcode should be realeted to3201050 so what about this item91C5006-05/8-B40?\'"", ""Comment 69: \'prośba o pomoc w analizie"", ""Comment 70: po stand up - prośba też Macieja.Nie da się wydać stocka na zero - barcode 437-W0020v\'"", \'Comment 71: ""To był barcode \\\'437-W002{color:#de350b}O{color}V\\\' a nie \\\'437-W002{color:#de350b}0{color}V\\\'. I tak jak w przypadku poprzednich UL\', \'Comment 72: nie ma go w WMSie.!screenshot-1!{code:java}SELECT  * FROM [DHPlantStockBusinessLogicMain].[dbo].[StockUnits]  where barcode = \\\'437-W002OV\\\'  SELECT  * FROM [DHPlantWMSBusinessLogicMain].[dbo].[UnitLoads]  where barcode = \\\'437-W002OV\\\'   SELECT  * FROM [DHPlantWMSBusinessLogicMain].[dbo].[Items]  where id = \\\'DA4A7DD7-BE1A-4E66-AB93-4DAF680C29EC\\\'{code}""\', \'Comment 73: ""Good day\', ""Comment 74: regarding the code 437-W002OV\' I unintentionally misled you"", \'Comment 75: the data has been corrected please check.""\', \'Comment 76: ""HiIt\\\'s working.Please close the ticket . Thank you.""]\']\nRelated Issues:\n[]\n\n### End'}"
163,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8869\n\n### Instruction:\nwe need to create production order for medicated feed but system is showing exceeded quantity. I checked the system and we already created one PRO and PLR, we cancelled PLR but was not possible cancel PRO, and we need to create new PRO because they changed the recipe version.\r\n\r\nPRO-1046 - please cancel\r\nItem SUC6687-MD-S20\r\nOrder SO-638075442/23/PED\r\n\r\nCould you cancel PRO-1046 to be possible create new one?\r\n\r\nThank you\n\n### Response:\n[""Comment 1: [\'!MicrosoftTeams-image (60)!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 3: "" !screenshot-1! Medicated production order\\\'s and production lots quantity cannot exceed the sum of all attached order element remaining quantities""\', ""Comment 4: \'Changing this options in the configuration it should be possible to generate a document despite the confirmed PrO. !screenshot-2! Another option is a new medicated production set up in DHC.As for PrO cancellation developers analysis is required - unfortunately analyzed in the morning.Please let me know whether to change the configuration or whether this ticket  can be processed in the morning.\'"", ""Comment 5: \'klient nie odpisał na wczorajszy komentarz.\'"", ""Comment 6: \'PRO zostało usunięte. Sum of production requests na medicated production controls = 0.Mimo"", \'Comment 7: że użytkownik posiadał uprawnienie do usuwania potwierdzonych PRO\', \'Comment 8: to opcja była nieaktywna w przypadku\', ""Comment 9: gdy PLR został już utworzony i anulowany. DAP-13495 - zostanie to poprawione w werji 8.6.Żeby usunąć PRO należy:1. Tymczasowo usunąć ProductionOrderId z usuniętego PLRa w  [dbo].[ProductionLots]2. W DHP usunąć PRO (po odpięciu PLRa z PRO opcja stanie się dostępna)3. Uzupełnić ProductionOrderId usuniętego PLRa w  [dbo].[ProductionLots]!PRO_cancelled! !Medicated!\'"", ""Comment 10: \'Hello. PrO has been removed. In case a PLR has been created and canceled there will be a change in the application to make canceling the PrO available as well. For version 8.6.\'"", ""Comment 11: \'Hello Piotr,we checked and now we can create new PrO. Thank you.\'"", ""Comment 12: \'[[DHP 3.0] Usunięcie PrO"", ""Comment 13: productionorder.|onenote:https://kotrak.sharepoint.com/sites/erpasysta/Shared%20Documents/Baza%20wiedzy/Baza%20Wiedzy%20-%20ERPSD/Klienci/DEHEUS/DEHEUS%20APPLICATIONS/Brazil/Baza%20wiedzy.one#%5bDHP%203.0%5d%20Usuni%C4%99cie%20PrO,%20productionorder.&section-id=\\\\\\\\{05DF1439-683C-45FE-8260-61E2EC66DC91}&page-id=\\\\\\\\{0A3DBF1B-FFDB-47DD-B672-6C10C1152EE7}&end] ([Widok sieci Web|https://kotrak.sharepoint.com/sites/erpasysta/_layouts/OneNote.aspx?id=%2Fsites%2Ferpasysta%2FShared%20Documents%2FBaza%20wiedzy%2FBaza%20Wiedzy%20-%20ERPSD&wd=target%28Klienci%2FDEHEUS%2FDEHEUS%20APPLICATIONS%2FBrazil%2FBaza%20wiedzy.one%7C05DF1439-683C-45FE-8260-61E2EC66DC91%2F%5BDHP%203.0%5D%20Usuni%C4%99cie%20PrO%2C%20productionorder.%7C0A3DBF1B-FFDB-47DD-B672-6C10C1152EE7%2F%29])\']""]\nRelated Issues:\n[\'DGS-8887\', \'DAP-13495\']\n\n### End'}"
164,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8868\n\n### Instruction:\nDear !\r\n\r\nPlease help to check this issue. Can not create sample from PLRs with reason that recipes could not be found.\r\nPLR 4371290323005 item 91C5006-03 Ver 24\r\nPLR 4373290323005  item  91C5007A-05 Ver 32\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'!image-2023-03-29-18-48-15-493.png!!image-2023-03-29-18-48-48-361.png!\'"", ""Comment 4: \'Pomimo resenda"", ""Comment 5: technologia w module QAM dalej niedostępna!image-2023-03-29-18-53-04-851.png!\'"", ""Comment 6: \'!image-2023-03-29-19-08-32-089.png!\'"", ""Comment 7: \'!image-2023-03-29-19-23-27-592.png!!image-2023-03-29-19-24-07-544.png!\'"", ""Comment 8: \'!image-2023-03-29-19-34-46-628.png!\'"", \'Comment 9: ""{code:java}023-03-29 23:14:34 (489a5719-653f-4eca-9f66-578f2b95a81e/Plant.QAM.BusinessLogic/VNPCT-TS01/32984/198) [Error] Kotrak.Common.Infrastructure.ICommandRunEnvironment - Error during Void Run[CreateInternalSampleForProductionLotReportPromiseCommand](Plant.QAM.BusinessLogic.Application.Interfaces.Samples.Internal.Commands.CreateInternalSampleForProductionLotReportPromiseCommand) methodKotrak.Common.Application.Exceptions.BusinessLogicException: Technology of ID \\\'5c0c7b1d-b9ae-48fe-b145-8be48f0d60da\\\' was not found ---> Kotrak.Common.Application.Exceptions.BusinessLogicException: TechnologyByIdNotFoundMessageTemplate at Plant.QAM.BusinessLogic.Application.Technologies.TechnologyRepositoryExtensions.GetOrThrow(ITechnologyRepository repository\', \'Comment 10: AggregateId id) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\b95b691ba186b1c9\\\\\\\\Plant.QAM.BusinessLogic\\\\\\\\Application\\\\\\\\Technologies\\\\\\\\TechnologyRespositoryExtensions.cs:line 10 at Plant.QAM.BusinessLogic.Application.Samples.InternalSampleService.<>c__DisplayClass19_0.<UpdateInternalSample>b__3(AggregateId technologyId) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\b95b691ba186b1c9\\\\\\\\Plant.QAM.BusinessLogic\\\\\\\\Application\\\\\\\\Samples\\\\\\\\InternalSampleService.cs:line 169 at Plant.QAM.BusinessLogic.PublishedLanguage.ActionExtensions.<>c__DisplayClass3_0`1.<ToVoidFunc>b__0(T arg) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\b95b691ba186b1c9\\\\\\\\Plant.QAM.BusinessLogic\\\\\\\\PublishedLanguage\\\\\\\\ActionExtensions.cs:line 29 at Plant.QAM.BusinessLogic.PublishedLanguage.Monads.EitherExtensions.<>c__DisplayClass5_0`4.<Match>b__0(Either`2 e) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\b95b691ba186b1c9\\\\\\\\Plant.QAM.BusinessLogic\\\\\\\\PublishedLanguage\\\\\\\\Monads\\\\\\\\EitherExtensions.cs:line 50 at Plant.QAM.BusinessLogic.PublishedLanguage.Monads.Either`2.Match[T](Func`2 left\', \'Comment 11: Func`2 right) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\b95b691ba186b1c9\\\\\\\\Plant.QAM.BusinessLogic\\\\\\\\PublishedLanguage\\\\\\\\Monads\\\\\\\\Either.cs:line 31 at Plant.QAM.BusinessLogic.PublishedLanguage.Monads.EitherExtensions.Match[TLeft,TMiddle,TRight,TResult](Either`2 either\', \'Comment 12: Func`2 left\', \'Comment 13: Func`2 middle\', \'Comment 14: Func`2 right) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\b95b691ba186b1c9\\\\\\\\Plant.QAM.BusinessLogic\\\\\\\\PublishedLanguage\\\\\\\\Monads\\\\\\\\EitherExtensions.cs:line 49 at Plant.QAM.BusinessLogic.Application.Interfaces.Tolerances.ToleranceSource.<>c__DisplayClass2_0`1.<Match>b__1(Either`2 e) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\b95b691ba186b1c9\\\\\\\\Plant.QAM.BusinessLogic\\\\\\\\Application.Interfaces\\\\\\\\Tolerances\\\\\\\\ToleranceSource.cs:line 31 at Plant.QAM.BusinessLogic.PublishedLanguage.Monads.Either`2.Match[T](Func`2 left\', \'Comment 15: Func`2 right) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\b95b691ba186b1c9\\\\\\\\Plant.QAM.BusinessLogic\\\\\\\\PublishedLanguage\\\\\\\\Monads\\\\\\\\Either.cs:line 31 at Plant.QAM.BusinessLogic.Application.Interfaces.Tolerances.ToleranceSource.Match[TResult](Func`2 itemQualityNorm\', \'Comment 16: Func`2 rawMaterialVersion\', \'Comment 17: Func`1 latestRawMaterial\', \'Comment 18: Func`2 technology\', \'Comment 19: Func`3 productVersion\', \'Comment 20: Func`1 latestProduct) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\b95b691ba186b1c9\\\\\\\\Plant.QAM.BusinessLogic\\\\\\\\Application.Interfaces\\\\\\\\Tolerances\\\\\\\\ToleranceSource.cs:line 26 at Plant.QAM.BusinessLogic.Application.Interfaces.Tolerances.ToleranceSource.Act(Action`1 itemQualityNorm\', \'Comment 21: Action`1 rawMaterialVersion\', \'Comment 22: Action latestRawMaterial\', \'Comment 23: Action`1 technology\', \'Comment 24: Action`2 productVersion\', \'Comment 25: Action latestProduct) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\b95b691ba186b1c9\\\\\\\\Plant.QAM.BusinessLogic\\\\\\\\Application.Interfaces\\\\\\\\Tolerances\\\\\\\\ToleranceSource.cs:line 43 at Plant.QAM.BusinessLogic.Application.Samples.InternalSampleService.<>c__DisplayClass19_0.<UpdateInternalSample>b__0(ToleranceSource toleranceSource) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\b95b691ba186b1c9\\\\\\\\Plant.QAM.BusinessLogic\\\\\\\\Application\\\\\\\\Samples\\\\\\\\InternalSampleService.cs:line 156 at Plant.QAM.BusinessLogic.PublishedLanguage.ActionExtensions.<>c__DisplayClass3_0`1.<ToVoidFunc>b__0(T arg) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\b95b691ba186b1c9\\\\\\\\Plant.QAM.BusinessLogic\\\\\\\\PublishedLanguage\\\\\\\\ActionExtensions.cs:line 29 at Plant.QAM.BusinessLogic.PublishedLanguage.DataStructures.EditableValue`1.Match[TResult](Func`2 update\', \'Comment 26: Func`1 noAction) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\b95b691ba186b1c9\\\\\\\\Plant.QAM.BusinessLogic\\\\\\\\PublishedLanguage\\\\\\\\DataStructures\\\\\\\\EditableValue.cs:line 24 at Plant.QAM.BusinessLogic.Application.Samples.InternalSampleService.UpdateInternalSample(AggregateId id\', \'Comment 27: UpdateInternalSampleDataStructure updateData) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\b95b691ba186b1c9\\\\\\\\Plant.QAM.BusinessLogic\\\\\\\\Application\\\\\\\\Samples\\\\\\\\InternalSampleService.cs:line 155 at Kotrak.Common.Infrastructure.Commands.CommandEnvironment.Run[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.IntercontextEventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.EventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.ValidationCommandEnvironmentDecorator.Run[TCommand](TCommand command) at Castle.DynamicProxy.AbstractInvocation.Proceed() at Kotrak.Common.Infrastructure.Interceptors.LoggingInterceptor`1.Intercept(IInvocation invocation) --- End of inner exception stack trace ---{code}""\', \'Comment 28: ""wiszą  messages dla QAM: tj wolno schodzą. !screenshot-1! {code:java}SELECT *update iset createdate=\\\'2023-03-29 21:00\\\',processdate=\\\'2023-03-29 21:00\\\'  FROM [DHPlantQAMBusinessLogicIntercontext].[dbo].[InboundMessages] iwhere messagetype like \\\'%item%\\\'SELECT *update iset createdate=\\\'2023-03-29 21:00\\\',processdate=\\\'2023-03-29 21:00\\\'  FROM [DHPlantQAMBusinessLogicIntercontext].[dbo].[InboundMessages] iwhere messagetype like \\\'%recipe%\\\'{code}!image-2023-03-29-20-39-39-468!""\', ""Comment 29: \'Please check again: !screenshot-2! there are still messages to be processed for the QAM module \\\\\'LecoResultRegisteredEvent\\\\\' so there may be delays - I will let you know when all messages will be processed.If there is still a lack of technology"", \'Comment 30: please let me know. !screenshot-3! {code:java}Deadlock dla modułu QAM.2023-03-29 14:08:33 (20cb75fc-c751-4230-8f3e-34957e4a670e/Plant.QAM.BusinessLogic/VNPCT-TS01/13904/12) [Error] Microsoft.EntityFrameworkCore.Query - An exception occurred in the database while iterating the results of a query for context type \\\\\\\'""Plant.QAM.BusinessLogic.Infrastructure.EF.QamContext""\\\\\\\'.""""""System.InvalidOperationException: An exception has been raised that is likely due to a transient failure. Consider enabling transient error resiliency by adding \\\\\\\'EnableRetryOnFailure()\\\\\\\' to the \\\\\\\'UseSqlServer\\\\\\\' call. ---> System.Data.SqlClient.SqlException: Transaction (Process ID 121) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception\', \'Comment 31: Boolean breakConnection\', \'Comment 32: Action`1 wrapCloseInAction)   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj\', \'Comment 33: Boolean callerHasConnectionLock\', \'Comment 34: Boolean asyncClose)   at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior\', \'Comment 35: SqlCommand cmdHandler\', \'Comment 36: SqlDataReader dataStream\', \'Comment 37: BulkCopySimpleResultSet bulkCopyHandler\', \'Comment 38: TdsParserStateObject stateObj\', \'Comment 39: Boolean& dataReady)   at System.Data.SqlClient.SqlDataReader.TryHasMoreRows(Boolean& moreRows)   at System.Data.SqlClient.SqlDataReader.TryReadInternal(Boolean setTimeout\', \'Comment 40: Boolean& more)   at System.Data.SqlClient.SqlDataReader.Read()   at Microsoft.EntityFrameworkCore.Storage.RelationalDataReader.Read()   at Microsoft.EntityFrameworkCore.Query.Internal.QueryingEnumerable`1.Enumerator.BufferlessMoveNext(DbContext _\', \'Comment 41: Boolean buffer)   at Microsoft.EntityFrameworkCore.SqlServer.Storage.Internal.SqlServerExecutionStrategy.Execute[TState,TResult](TState state\', \'Comment 42: Func`3 operation\', \'Comment 43: Func`3 verifySucceeded)   --- End of inner exception stack trace ---   at Microsoft.EntityFrameworkCore.SqlServer.Storage.Internal.SqlServerExecutionStrategy.Execute[TState,TResult](TState state\', \'Comment 44: Func`3 operation\', \'Comment 45: Func`3 verifySucceeded)   at Microsoft.EntityFrameworkCore.Query.Internal.QueryingEnumerable`1.Enumerator.MoveNext()   at Microsoft.EntityFrameworkCore.Query.Internal.QueryBuffer.IncludeCollection[TEntity,TRelated,TElement](Int32 includeId\', \'Comment 46: INavigation navigation\', \'Comment 47: INavigation inverseNavigation\', \'Comment 48: IEntityType targetEntityType\', \'Comment 49: IClrCollectionAccessor clrCollectionAccessor\', \'Comment 50: IClrPropertySetter inverseClrPropertySetter\', \'Comment 51: Boolean tracking\', \'Comment 52: TEntity entity\', \'Comment 53: Func`1 relatedEntitiesFactory\', \'Comment 54: Func`3 joinPredicate)   at lambda_method(Closure \', \'Comment 55: QueryContext \', \'Comment 56: ProductionLotReportEntity \', \'Comment 57: Object[] )   at Microsoft.EntityFrameworkCore.Query.Internal.IncludeCompiler._Include[TEntity](QueryContext queryContext\', \'Comment 58: TEntity entity\', \'Comment 59: Object[] included\', \'Comment 60: Action`3 fixup)   at lambda_method(Closure \', \'Comment 61: TransparentIdentifier`2 )   at System.Linq.Enumerable.SelectEnumerableIterator`2.MoveNext()   at System.Linq.Enumerable.SingleOrDefault[TSource](IEnumerable`1 source)   at Microsoft.EntityFrameworkCore.Query.Internal.LinqOperatorProvider.ResultEnumerable`1.GetEnumerator()   at Microsoft.EntityFrameworkCore.Query.Internal.LinqOperatorProvider.ExceptionInterceptor`1.EnumeratorExceptionInterceptor.MoveNext()""{code}\\\'\', \'Comment 62: ""it\\\'s working.please close the ticket""]\']\nRelated Issues:\n[]\n\n### End'}"
165,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8867\n\n### Instruction:\nPlease remove/deactivate additional technology SN506247 from DHC Compound.\r\n\r\nKind regards,\r\nRob.\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 2: "" Can this ticket\\\'s priority be set to P1.They would like to send the recipe now because the feed needs to be produced today.Regards,Rob.""\', ""Comment 3: \'Hi Rob,Changing priority now.Regards\'"", ""Comment 4: \'Thank you"", ""Comment 5: on behalf of the Formulation team :)\'"", ""Comment 6: \'SN506247 has been deactivated. Please"", ""Comment 7: verify.Regards\'"", ""Comment 8: \'Thank you for the support"", ""Comment 9: the ticket can be closed.\'"", ""Comment 10: \'Thank you.\']""]\nRelated Issues:\n[]\n\n### End'}"
166,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8866\n\n### Instruction:\nSystem not allow to change expiry date of item ENWINC52A, internal serial number WI-203/1/23-1, correct expiry date 30/01/2024. We can change expiry date but when we click to save, system shows an error message.\r\nCould you  check why we have this error?\r\n\r\nThank you\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 3: ""{code:java}2023-03-30 09:39:54 (8f1cebc5-9b69-46bc-a770-4dadb2025698/Plant.Stock.BusinessLogic/BR-8-SV-VM0102/2372/302) [Error] Kotrak.Common.Infrastructure.ICommandRunEnvironment - Error during Void Run[UpdateDeliveryDetailsCommand](Plant.Stock.BusinessLogic.Application.Interfaces.Deliveries.Commands.UpdateDeliveryDetailsCommand) methodMicrosoft.EntityFrameworkCore.DbUpdateException: An error occurred while saving the entity changes. See the inner exception for details. ---> Microsoft.Data.SqlClient.SqlException (0x80131904): Cannot insert duplicate key row in object \\\'dbo.Deliveries\\\' with unique index \\\'IX_Deliveries_SourceDocumentId_SourceDocumentNo_ItemId_SerialNumber_ExpiryDate_BagSize\\\'. The duplicate key value is (389626ef-2700-4539-9c70-235451c6a247\', \'Comment 4: <NULL>\', \'Comment 5: 603e3d81-5af9-45a9-b308-a7c7ec0695a2\', \'Comment 6: 118/23\', \'Comment 7: 2024-01-30 00:00:00.0000000\', \'Comment 8: 1.000000).The statement has been terminated.{code}""\', ""Comment 9: \'The error results from the limitation on the dbo.Deliveries table.There cannot be two entries with the same data for:SourceDocumentId,SourceDocumentNo,ItemId,SerialNumber,ExpiryDate,BagSizeI set it one day later and the change was saved.!image-2023-03-30-14-48-51-304.png!\'"", ""Comment 10: \'Hi Piotr,so do you mean that is not possible create 2 different internal serial number for the same VT intake with the same lot number and expiry date?What are the fields key to control the intake?\'"", ""Comment 11: \'For deliveries tabel is unigue index for columns:SourceDocumentId"", \'Comment 12: SourceDocumentNo\', \'Comment 13: ItemId\', \'Comment 14: SerialNumber\', \'Comment 15: ExpiryDate\', \'Comment 16: BagSize -if the second one is the same\', ""Comment 17: there will be a error in the application.\'"", \'Comment 18: ""Hi Piotr,it\\\'s clear\', \'Comment 19: you can close this task. Thank you.""\', ""Comment 20: \'Thank you.\']""]\nRelated Issues:\n[]\n\n### End'}"
167,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8865\n\n### Instruction:\nHi,\r\nPlease help check DHC. We can not open menu Recipes to accept recipes, event thought try with some filter\r\nNote: we already rebuild index system \n\n### Response:\n[""Comment 1: [\'!image!!image-1!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'!image-2023-03-29-16-30-02-551.png!\'"", ""Comment 4: \'_{color:#0747a6}Note: we already rebuild index system{color}_Aj dont tink soł:!image-2023-03-29-16-37-19-532.png!\'"", ""Comment 5: \'21 minut :D!image-2023-03-29-17-14-54-293.png!\'"", ""Comment 6: \'It works now:!image-2023-03-29-17-18-27-083.png!Please"", ""Comment 7: verify\'"", ""Comment 8: \'still error!image-2!\'"", ""Comment 9: \'I think this can be performance issue of the databse server that I cannot check:!image-2023-03-30-16-47-20-176.png|width=421,height=240!What I can advise for now is to filter Recipes"", \'Comment 10: for example\', ""Comment 11: you may filter by date or by Production area!image-2023-03-30-16-48-24-755.png|width=795,height=375!Regards\'"", ""Comment 12: \'!image-2023-03-30-16-49-02-328.png!\'"", ""Comment 13: \'please try\'"", \'Comment 14: ""Hi,Why don\\\'t you try to filter Recipes by Production area?!image-2023-04-03-12-33-50-803.png!""\', \'Comment 15: ""we have try with that: sometimes\\\'s ok sometime is not. i thinks it should be improve performnace by first defautl when login""\', ""Comment 16: \'hej [~przemyslaw.przybyszewski@kotrak.com] Przemku :)czy my coś jesteśmy w stanie z tym zrobić? tam co ok 3-4 dni fragmentacja sięga do 90 %. Wczoraj znowu na 70 paru rowach było 90% i więcej"", \'Comment 17: w sumie ok 170 rows było powyżej 30 % (wybacz\', ""Comment 18: nie śmieciłam screenem) plus używanie filtra podobno też nie zawsze jest rozwiązaniem dogodnym dla usera :P\'"", ""Comment 19: \'Please be informed that we have forwarded the issue to the development team in order to internal analysis.We are waiting for more details and will be back with further information as soon as possible.Regards\'"", ""Comment 20: \'Hi,When the Recipes are synchronized in the background"", \'Comment 21: the filter may not work. However\', ""Comment 22: we have also noticed that fragmentation of DHC indexes becomes very high every 4 days. You need to solve it on your side.Regards\'"", ""Comment 23: \'hi,we have schedule for rebuild index but not daily because performance and database volume. but Fragment have still like that after rebuild"", ""Comment 24: so it not related to fragment but related to data for recipes to high\'"", ""Comment 25: \'Hi,Yes"", \'Comment 26: but data for recipes does not depend on Kotrak. The issue with Recipes list occurs also in other countries whe synchronization of recipes goes in the background.In that case\', ""Comment 27: can we close this task?Regards\'"", ""Comment 28: \'DHC is place to store data. if as you mentioned: how can we login and accept recipes if error orrcurs like that\'"", \'Comment 29: \\\'The best way is to filter by date for example start date: today and filter by production area. And check ""show the lates version"" This should help.!image-2023-04-05-08-00-06-970.png!\\\'\', ""Comment 30: \'Hi,Is there anything else we can do for you?Regards\'"", ""Comment 31: \'it not working well. still have isssue now\']""]\nRelated Issues:\n[]\n\n### End'}"
168,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8864\n\n### Instruction:\nHi\r\n\r\nWe are facing some delay on light scan on motorola scanners (MC93 model).\r\nWhen we open the own motorola application and test the light scan, we pull the trigger and instantly the scanner light turns on.\r\nHowever, inside the DHP app, no matter the screen, it takes more than 10 seconds to turn on the scanner light.\r\n\r\nThis is happening since go live in Itaberaí (sep/2021), however the time of delay is increasing every new version. I was 3s, then 5s, now is more than 10s.\r\n\r\nCould you please check this?\r\n\r\nThank you very much\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Maicon,Please be informed that we have forwarded the issue to the development team in order to internal analysis.We are waiting for more details and will be back with further information as soon as possible.Regards\'"", \'Comment 3: ""[~mberbert@deheus.com] we have checked on our server and we didn\\\'t have the issue with delay as you have described. But we are using: https://www.zebra.com/us/en/products/spec-sheets/mobile-computers/handheld/tc52-tc57.html""\', \'Comment 4: ""Hi [~marcin.kleszcz@kotrak.comI\\\'ll make a video for you next time I visit the factory.Maybe it can help you to identify what happens.Thank you very much""]\']\nRelated Issues:\n[]\n\n### End'}"
169,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8863\n\n### Instruction:\nWe would like to have two daily lists (one with PI’s and one with SI’s) that contain:\r\n * All regular and financed invoices that were archived the day before\r\n * With the following colunms:\r\n * Customer Full-name\r\n * Archive date\r\n * Number\r\n * ERP number\r\n * Sector\r\n * Creator\r\n * State\r\n\r\n\xa0\r\n\r\nAre you able to automate the creation of such a list?\n\n### Response:\n[""Comment 1: [\'!email_list_of_invoices!\'"", ""Comment 2: \'Due to issues with emails described in taskhttps://helpdesk.kotrak.com/servicedesk/customer/portal/56/DGS-7649 temporary it will be 2 actions available from Lightning button in Inbox for these 2 reports.\'"", ""Comment 3: \'A report of archival invoices has been prepared"", ""Comment 4: available in inbox for Peter Moeliker\'"", ""Comment 5: \'[~tomasz.zygon@kotrak.com]Dodałem uprawnienia dla Petera Moelikera"", ""Comment 6: bo nie były jednak dodane.Na Test nie mamy tych akcji?\']""]\nRelated Issues:\n[\'DGS-7649\']\n\n### End'}"
170,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8862\n\n### Instruction:\nHi\r\n\r\nI\'d like to have the translation files for R8.6.\r\nThe untranslated and also *system_messages* files because it is being displayed in english, no matter the user\'s choice of language.\r\n\r\nThank you\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Maicon,Please be informed that we have forwarded the issue to the development team in order to internal analysis.We are waiting for more details and will be back with further information as soon as possible.Regards\'"", ""Comment 3: \'* Web* Mobile* SystemMessages (Web + Mobile)\']""]\nRelated Issues:\n[]\n\n### End'}"
171,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8861\n\n### Instruction:\nHi\r\n\r\nWe need to fix translations for R8.5. Could you please send me the fixed merged translation file and untranslated file for this release?\r\n\r\nThank you very much!\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Maicon,Please be informed that we have forwarded the issue to the development team in order to internal analysis.We are waiting for more details and will be back with further information as soon as possible.Regards\']""]\nRelated Issues:\n[]\n\n### End'}"
172,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8860\n\n### Instruction:\nAfter restarting the virtual machine RSAPP06 (10.100.3.73) I could not access DHP 3.0 Test through the browser. After that, I restarted ISS on RSAPP06, after that I can access the login page via a web browser, but it tells me that my username and password are incorrect. I am sure that my password is correct because I saved it and it worked until before the restart. Can you check what the problem is?\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \' !screenshot-1! \'"", ""Comment 4: \'Hello,what was done when you used the test environment and when you used this environment before? We need the address data for the database server.Regards\'"", \'Comment 5: ""I used it a month ago\', \'Comment 6: I can\\\'t remember exactly what I needed. Colleagues use it occasionally when they need to test something.rsdb09.emea.corp.deheus.com [10.100.3.75]""\', ""Comment 7: \'Rabbit po uruchomieniu od razu sie stopujewpisy z eventa!image-2023-03-30-14-21-19-687.png!RabbitMQ: Erlang machine stopped instantly (distribution name conflict?). The service is not restarted"", \'Comment 8: ignoring OnFail option.A corruption was discovered in the file system structure on volume D:.A corruption was found in a file system index structure. The file reference number is 0xc000000098f22. The name of the file is ""\\\\\\\\Kotrak\\\\\\\\dhp30_IIS\\\\\\\\rabbitmq\\\\\\\\data\\\\\\\\db\\\\\\\\rabbit@RSAPP06-plugins-expand\\\\\\\\rabbitmq_web_stomp-3.8.5\\\\\\\\ebin"". The corrupted index attribute is "":$I30:$INDEX_ALLOCATION"".!image-2023-03-30-14-20-55-025.png!\\\'\', ""Comment 9: \'Good morning"", \'Comment 10: As part of the DGs project we do not handle requests related to the test environment\', \'Comment 11: here exceptionally we wanted to verify \', \'Comment 12: the operation of the application after restarting the pool. Actually\', \'Comment 13: the problem is not your login credentials. Please set up task DHITs\', ""Comment 14: the problem is related to the operation of IIs services and mainly rabbit problem.May we close the task.\'"", ""Comment 15: \'Hello,regarding to our last comment we are closing this issue.Regards\']""]\nRelated Issues:\n[]\n\n### End'}"
173,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8859\n\n### Instruction:\nwe have problem in report TT, it\'s showing wrong customer name in the release field. Production SUC1230-MD-S25, lot number 0891280223014, VT dispatch VT-1178, correct customer Marcelo Valles Bento, but is showing Marina Nogueira\r\n\r\nCould you fix the report for all units?\r\n\r\nThank you\r\n\n\n### Response:\n[""Comment 1: [\'[^TrackAndTraceReadyProductReport (4).pdf] _(258 kB)_!tt error!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Nie wiem"", \'Comment 4: co zmienili\', ""Comment 5: ale chyba nie wyszłohttps://helpdesk.kotrak.com/browse/DHITS-745\'"", ""Comment 6: \'Please be informed that we have forwarded the issue to the development team in order to internal analysis.We are waiting for more details and will be back with further information as soon as possible.Regards\'"", ""Comment 7: \'[~marcin.kleszcz@kotrak.com]widziałam kilka DHITSów dla Rio Claro na wydruki TT"", \'Comment 8: tam zdaje się mieli coś sami zmieniać\', ""Comment 9: ale nie wyszło... dacie rade spojrzeć na to? :)z góry dzięks\'"", \'Comment 10: ""Dear Priscyla,Could ypu please clarify few things:>>{color:#0747a6}_in report TT\', ""Comment 11: it\'s showing wrong customer name in the release field -_ {color:#172b4d}does the issue occur for all Productions or only to thelot number 0891280223014?{color}{color}{color:#0747a6}{color:#172b4d}>>{color} _Could you fix the report for all units?_{color} - Do you mean all plants? If for all plants printout does not work correctly now"", \'Comment 12: and it worked few days ago\', \'Comment 13: could you please let us know if anything was changed on your side\', \'Comment 14: and\', \'Comment 15: if yes\', \'Comment 16: could you please let us know what was changed?Best regards""\', \'Comment 17: ""Aleksandra,we found this error till now only for this lot number. Do you know where is the error? If is in this production\', \'Comment 18: you need to fix only in this document\', ""Comment 19: but if it\'s in report"", \'Comment 20: you need to fix for this unit and how we have the same in all plants\', \'Comment 21: we need to have the correct report in all units.""\', ""Comment 22: \'!image-2023-03-31-18-55-12-022.png!\'"", ""Comment 23: \'!image-2023-03-31-18-55-41-202.png!\'"", ""Comment 24: \'!image-2023-03-31-18-56-18-932.png!\'"", \'Comment 25: ""{code:java}SELECT *SELECT * FROM [DHPlantStockBusinessLogicMain].[dbo].[Deliveries] where SourceDocumentNumber = \\\'0891280223014\\\' SELECT * FROM [DHPlantProdBusinessLogicMain].[dbo].[ProductionLots] where LotNumber = \\\'0891280223014\\\' SELECT * FROM [DHPlantProdBusinessLogicMain].[dbo].[ProductionOrders] where id = \\\'B477A8EA-3012-4651-A754-BF1DC6049527\\\' SELECT BP.Code\', ""Comment 26: BP.Name FROM [DHPlantProdBusinessLogicMain].dbo.ProductionLots PL INNER JOIN [DHPlantProdBusinessLogicMain].dbo.ProductionOrders PO ON PO.Id = PL.ProductionOrderId INNER JOIN [DHPlantProdBusinessLogicMain].dbo.BusinessPartners BP ON BP.Id = PO.BusinessPartnerId WHERE PL.ID = \'BEAE28C4-0E16-4970-AAF2-24D2901C519F\' SELECT R.ReleaseDate"", \'Comment 27: COALESCE(WOPD_Data.SourceDocumentNumber\', \'Comment 28: WD_Data.SourceDocumentNumber\', \'Comment 29: VC_Data.Document\', \'Comment 30: R.SourceDocumentNumber) AS Document\', \'Comment 31: COALESCE(WOPD_Data.Code\', \'Comment 32: WD_Data.Code\', \'Comment 33: VC_Data.Code\', \'Comment 34: PROD_Data.Code\', ""Comment 35: \'\') AS CustomerCode"", \'Comment 36: COALESCE(WOPD_Data.Name\', \'Comment 37: WD_Data.Name\', \'Comment 38: VC_Data.Name\', \'Comment 39: PROD_Data.Name\', ""Comment 40: \'\') AS CustomerName"", \'Comment 41: SUM(R.Quantity) AS ReleasedQuantity\', \'Comment 42: R.QuantityUnit AS ReleasedQuantityUnit\', \'Comment 43: COALESCE(WOPD_Data.ForeignDocumentInfo\', \'Comment 44: WD_Data.ForeignDocumentInfo\', \'Comment 45: VC_Data.ForeignDocumentInfo\', \'Comment 46: \\\'\\\') AS ForeignDocumentInfo FROM [DHPlantStockBusinessLogicMain].dbo.Deliveries D INNER JOIN [DHPlantStockBusinessLogicMain].dbo.StockUnits S ON S.DeliveryId = D.Id INNER JOIN [DHPlantStockBusinessLogicMain].dbo.StockUnitReleases R ON R.Id = S.Id where DeliveryId = \\\'6AF47AFF-6CB9-4DFC-9ED6-C23242245641\\\'{code}""\', ""Comment 47: \'!image-2023-03-31-19-00-57-691.png!\'"", \'Comment 48: ""{code:java}SELECT R.SourceDocumentId,WDE.Id\', \'Comment 49: BP.Code\', \'Comment 50: BP.Name\', \'Comment 51: WOE.SourceDocumentId\', \'Comment 52: WOE.SourceDocumentNo\', \'Comment 53: WOE.SourceDocumentNumber\', \'Comment 54: r.SourceDocumentId AS ReleaseSourceDocumentId\', \'Comment 55: VE.ForeignDocumentInfoSELECT R.SourceDocumentId,WDE.Id\', \'Comment 56: BP.Code\', \'Comment 57: BP.Name\', \'Comment 58: WOE.SourceDocumentId\', \'Comment 59: WOE.SourceDocumentNo\', \'Comment 60: WOE.SourceDocumentNumber\', \'Comment 61: r.SourceDocumentId AS ReleaseSourceDocumentId\', \'Comment 62: VE.ForeignDocumentInfo ,ve.Id,*,WOE.No,WDE.WarehouseOrderElementNo,VE.No,WOE.No FROM [DHPlantStockBusinessLogicMain].dbo.StockUnitReleases R left JOIN [DHPlantStockBusinessLogicMain].dbo.StockUnits S ON S.id =R.Id left JOIN [DHPlantWmsBusinessLogicMain].dbo.WarehouseDispatches WDE ON WDE.Id = R.SourceDocumentId left JOIN [DHPlantWmsBusinessLogicMain].dbo.WarehouseOrderElements WOE ON WOE.Id = WDE.WarehouseOrderId AND ISNULL(WOE.No\', \'Comment 63: 0) = ISNULL(WDE.WarehouseOrderElementNo\', \'Comment 64: 0) left JOIN [DHPlantVCBusinessLogicMain].dbo.VehicleTicketElements VE ON VE.Id = WOE.SourceDocumentId AND VE.No = WOE.No left JOIN [DHPlantProdBusinessLogicMain].dbo.BusinessPartners BP ON BP.Id = VE.MainBusinessPartnerId where R.SourceDocumentId = \\\'BD862CEE-A1AC-4E1E-AA3A-ADF502DC4C76\\\'{code}{code:java} --select MainBusinessPartnerId,* from [DHPlantVCBusinessLogicMain].dbo.VehicleTicketElements where id = \\\'17F0C1D5-559F-4F91-9E16-7B544CBCF205\\\' --select MainBusinessPartnerId,* from [DHPlantVCBusinessLogicMain].dbo.VehicleTicketElements where id = \\\'17F0C1D5-559F-4F91-9E16-7B544CBCF205\\\' --select * from [DHPlantVCBusinessLogicMain].dbo.VehicleTickets where id = \\\'17F0C1D5-559F-4F91-9E16-7B544CBCF205\\\'-- select * from Orders where id in (\\\'F611D5DF-C513-4FCE-AD95-12A84135925A\\\',\\\'33EFC4F0-A8CC-45B1-B22C-822C33308805\\\',\\\'B6290E56-A903-4BDF-AB77-578D9814D081\\\',--\\\'4F730F71-EDB3-4021-A62C-58CF4516593D\\\',\\\'5AB9A750-B44F-4DC7-8257-B5A1E19365DB\\\'){code}Zbiera dane z 16 elementu*!image-2023-04-03-15-04-24-858.png!*""\', ""Comment 65: \'Hej[~maciej.dobrzanski@kotrak.com]albo tu cos źle zbiera"", \'Comment 66: albo w danych jest coś nakopane. Dlaczego zbiera dane z 16 elementu? Kurde\', \'Comment 67: nie wiemy\', \'Comment 68: co dalej z tym fantem\', \'Comment 69: masz kogoś od wydruków? Ewentualnie podpowiedz\', ""Comment 70: co można jeszcze sprawdzić\'"", \'Comment 71: ""{code:java}select * from OrderElements where id in (\\\'F611D5DF-C513-4FCE-AD95-12A84135925A\\\',\\\'33EFC4F0-A8CC-45B1-B22C-822C33308805\\\',\\\'B6290E56-A903-4BDF-AB77-578D9814D081\\\',\\\'4F730F71-EDB3-4021-A62C-58CF4516593D\\\',\\\'5AB9A750-B44F-4DC7-8257-B5A1E19365DB\\\')--select * from BusinessPartners where id in (\\\'6094DA81-3573-4405-99FA-6239DD858C61\\\',\\\'8939635B-B045-434F-A248-B4F483F93EE0\\\',\\\'A7822B57-9072-4D49-BA83-0BE92C4C622A\\\')--select * from [DHPlantWmsBusinessLogicMain].dbo.WarehouseDispatches where id = \\\'BD862CEE-A1AC-4E1E-AA3A-ADF502DC4C76\\\'--select * from [DHPlantWmsBusinessLogicMain].dbo.WarehouseOrders where id = \\\'B35974F5-5F7C-48FB-B7F9-E299FEDA2F34\\\'{code}""\', ""Comment 72: \'[^KtrTrackAndTraceReadyProductReportReleases.sql]\'"", ""Comment 73: \'[~aleksandra.przybylek@kotrak.com] zmieniłem procedurę i podegrałem ją pod RC.Podegrajcie proszę nową wersję na wszystkie fabryki w BR.[~marcin.kleszcz@kotrak.com] wrzućcie sobie gdzieś do repozytorium tą procedurę. [^KtrTrackAndTraceReadyProductReportReleases.sql] \'"", ""Comment 74: \'[^TTReadyProductRelease_old.sql]\'"", ""Comment 75: \'[^TTReadyProductRelease_old.sql]\'"", ""Comment 76: \'Dear Priscyla,We have corrected the printout and deployed in all plants. But I can see"", \'Comment 77: inCaruaru it is not used.Please\', ""Comment 78: verify the printout and let me me know aboutCaruaru.Regards\'"", \'Comment 79: ""Dear Aleksandra,the report is correct. Could you add in Caruaru only for RM? Because we don\\\'t have production in this unit.Thank you""\', ""Comment 80: \'Dear Priscyla,For adding printout of raw material in Caruaru"", ""Comment 81: please raise a service request as this task concerns tt ready product release.Regards\'"", ""Comment 82: \'Hi Aleksandra,ok"", ""Comment 83: you can close this task. Thank you.\'"", ""Comment 84: \'Thank you\']""]\nRelated Issues:\n[\'DAP-13515\']\n\n### End'}"
174,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8858\n\n### Instruction:\nCan you add user Manon Straatman in Intense? She works for Mineral and manures and needs the same rights as Freddy Westrik. She will get her own projects and will add hours to this projects.\n\n### Response:\n[""Comment 1: [\'In progress.\'"", ""Comment 2: \'Done.\']""]\nRelated Issues:\n[]\n\n### End'}"
175,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8857\n\n### Instruction:\nCould you give permission to all sectors for:\r\nHattum, Pascal van <PHattum@deheus.com>\r\nLinde, Arthur van der <ALinde@deheus.com>\r\nDat, Darwin <DDat@deheus.com> (he has access to LAS, MAS NL & MAS BE)\n\n### Response:\n[""Comment 1: [\'Hello,\\\\rI will grant access.\'"", ""Comment 2: \'Hi [~mbovene@deheus.com],The accounts have been set up.Regards,Tomasz\']""]\nRelated Issues:\n[]\n\n### End'}"
176,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8856\n\n### Instruction:\nProduction operator by manual mistake confirmed PLR but the food is not produced and raw materials are not consumed, they actually confirmed in DHP production but the sole JO-3480-03-23-S is not confirmed. So please cancel JO. Thank you.\n\n### Response:\n[""Comment 1: [\'!JO-3480-03-23-S!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Hi,JO-348-03-23-S has been deleted with related IR- and IR+ documents.\'"", ""Comment 4: \'Thank you for your help. You can close the ticket now.\']""]\nRelated Issues:\n[]\n\n### End'}"
177,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8855\n\n### Instruction:\nHi,\r\nPlease help check DHP Hai Phong 2 can not login and show error as screenshot\n\n### Response:\n[""Comment 1: [\'!image!!image-1!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'hi,it working now. you no need to check now.thank you\']""]\nRelated Issues:\n[]\n\n### End'}"
178,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8854\n\n### Instruction:\nWe made inventory per location and when we tried to close, system shows an error message. We closed to continue the process, but we need to know why shows error message.\r\n\r\ncould you check it?\r\n\r\nThank you\n\n### Response:\n[""Comment 1: [\'!image (1)!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 3: ""Hello\', ""Comment 4: can I get the error time?I don\'t see any errors for this inventory in the logs.Currently"", \'Comment 5: the inventory is executed.Have any other changes been made in the meantime?Thank you and best regards.""\', ""Comment 6: \'Hello Piotr,the user tried to settle 30min after create the document"", \'Comment 7: but how was not working and they needed to use\', \'Comment 8: they executed. But we need to do inventory again\', ""Comment 9: and I need to know what heppened to avoid the error again.\'"", ""Comment 10: \'{code:java}2023-03-21 21:36:12 (2fc1dcfe-2f4a-4299-b4be-f675eb22ffa0/Plant.Stock.BusinessLogic/BR-3-SV-VM0202/1472/308) [Error] Kotrak.Common.Infrastructure.ICommandRunEnvironment - Error during Void Run[SettleStocktakingCommand](Plant.Stock.BusinessLogic.Application.Interfaces.Stocktaking.Commands.SettleStocktakingCommand) methodSystem.ArgumentException: Unit mismatch   at Kotrak.Common.SharedKernel.Quantity.ToCommonUnit(Quantity x1"", \'Comment 11: Quantity x2)   at Plant.Stock.BusinessLogic.Application.Stocktaking.StocktakingService.Settle(Stocktaking stocktaking\', ""Comment 12: IEnumerable`1 stockUnits) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Application\\\\\\\\Stocktaking\\\\\\\\StocktakingService.cs:line 443   at Plant.Stock.BusinessLogic.Application.Stocktaking.StocktakingService.SettleStocktaking(AggregateId stocktakingId) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Application\\\\\\\\Stocktaking\\\\\\\\StocktakingService.cs:line 171   at Plant.Stock.BusinessLogic.Application.Stocktaking.CommandHandlers.SettleStocktakingCommandHandler.Handle(SettleStocktakingCommand command) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Application\\\\\\\\Stocktaking\\\\\\\\CommandHandlers\\\\\\\\SettleStocktakingCommandHandler.cs:line 26   at Kotrak.Common.Infrastructure.Commands.CommandEnvironment.Run[TCommand](TCommand command)   at Kotrak.Common.Infrastructure.Commands.Decorators.IntercontextEventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command)   at Kotrak.Common.Infrastructure.Commands.Decorators.EventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command)   at Kotrak.Common.Infrastructure.Commands.Decorators.ValidationCommandEnvironmentDecorator.Run[TCommand](TCommand command)   at Castle.DynamicProxy.AbstractInvocation.Proceed(){code}\'"", ""Comment 13: \'There was a unit mismatch for these items0000816SCAAZE03USCCAZD05USCCVED04USCDEST26VSCDVER26U. I corrected them in the database - currently there should be no error for the inventory.\'"", ""Comment 14: \'Hi Piotr,what was the unit mismatch? It was in pcs and should be Pcs? Or kg and should be Pcs?\'"", \'Comment 15: ""For StockUnitsthe given barcodes had different units from the others,that\\\'s exactly what the differences in units between pcs and kg were about.""\', \'Comment 16: ""Hello Piotr,ok\', \'Comment 17: it\\\'s clear. You can close this task. Thank you.""\', ""Comment 18: \'Thank you.\']""]\nRelated Issues:\n[]\n\n### End'}"
179,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8853\n\n### Instruction:\nThe system display wrong information about deviation, the calculation is done based on item, but display deviation considering truck weight.\r\nWe added configuration with 2%, and system show deviation lower than this but lock to close  VT. \r\n\r\nExample on test database VT-83 , deviation is -1.73% and not allow to close. Deviation in weight -225kg, correct deviation 7,44%. The calculation is correct, but information displayed as deviation is wrong.\r\n\r\nCould you show the same and correct deviation that lock to close VT?\r\n\r\nThank you\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Dear Priscyla,Could you please confirm if this issue relates only to test environment or Prod is impacted as well??Regards\'"", ""Comment 4: \'Hello,we have problem in both"", \'Comment 5: I used example from test because we can simulate some scenarios\', ""Comment 6: but users asked help everyday because they have problem on production.\'"", ""Comment 7: \'Hi,Could you please provide us with specific example from Production environment?Regards\'"", ""Comment 8: \'Yes,VT-1906 plant RC1 - dispatch weight 88900kg"", \'Comment 9: system shows 0,552% of deviation\', \'Comment 10: but not allow to close (and is correct because we have high deviation).The problem is the deviation that system display is based on truck weight\', \'Comment 11: and the deviation that lock close vt is based on the item weight\', ""Comment 12: we need to see correct deviation.!vt19062.JPG|thumbnail!!vt1906.JPG|thumbnail!\'"", ""Comment 13: \'VT-1906 Total weight loaded (item+carrier unit) 12972kg Difference 488kgDeviation correct 3,76%\'"", ""Comment 14: \'Hej,[~maciej.dobrzanski@kotrak.com]czy jest szansa"", ""Comment 15: żeby to sprawdzić? :)!image-2023-04-03-12-45-09-649.png|width=228,height=152!\'"", \'Comment 16: ""Hi [~Aleksandra.Przybylek@kotrak.com]Could you please check Priscyla\\\'s last comment? Do you need anything else?Thank you""\', ""Comment 17: \'Hi [~mberbert@deheus.com],This task has been forwarded to Dev team. We will let you know about the result as soon as possible.Best regards\'"", ""Comment 18: \'Hi [~mberbert@deheus.com],We plan for this task to be analyzed tomorrow.\'"", \'Comment 19: ""[~psilva@deheus.com]Hello,which configuration with 2% do you mean? Percentage packed dispatch deviation field? Because that one is used to calculate the total weight deviation.In VT-1906 entered departure weight is above the upper limit but in VT-83 the weight is below the lower limit and that\\\'s why the weight control modal appears.Lower and upper limits are calculated as follows (for dispatch):lower = arrival weight + packed weight - total weight deviationupper = arrival weight + packed weight + total weight deviationtotal weight deviation = bulkWeightDeviation + packedWeightDeviation + pieceWeightDeviation + weighbridgeAccuracypacked weight deviation = Percentage packed dispatch deviation * packed weightThe deviation field on VT document displays only the deviation between the predicted weight and entered departure weight. [^weight control.xlsx] !VT_deviations_2-1!""\', ""Comment 20: \'Hi,Any feedback?\']""]\nRelated Issues:\n[]\n\n### End'}"
180,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8852\n\n### Instruction:\nThe following additional technologies for plant Helmond are not correct and must be removed/disabled:\r\nHE303300\r\nHE303306\r\nHE303436\r\n\r\nTo avoid issues with production, we wish to send new recipes directly after the additional technology is removed/disabled. This is planned on Thursday 30-03-2023 at 12:45\r\n(if additional technology is removed/disabled earlier, incorrect recipes will be send to PCS).\r\n\r\nCan you confirm that the additional technologies will be removed from DHC at 30-03-2023 12:45?\r\n\n\n### Response:\n[\'Comment 1: [""Hello Bob,I confirm. I will hand in this task to Piotr Gaczorek\', \'Comment 2: as he\\\'s working tomorrow morning shift.Regards""\', ""Comment 3: \'Hi Aleksandra"", \'Comment 4: ok\', \'Comment 5: thank you. Just to be sure: request is for Thursday\', ""Comment 6: not tomorrow\'"", ""Comment 7: \'Yes"", ""Comment 8: right. But Piotr is working all week morning shift. :)I have already asked him to plan this task for 12:45 on Thursday.Regards\'"", ""Comment 9: \'Hello"", ""Comment 10: changes for three additional technologies have been made.\'"", ""Comment 11: \'We still these additional technologies in DHC. Can you check again if they were removed?!image!\'"", ""Comment 12: \'Yes"", \'Comment 13: setProductDefinition = 0 for these should be enought\', ""Comment 14: but I changed their status to blocked and renamed them with arch.\'"", ""Comment 15: \'Ok"", ""Comment 16: thank you. At 14.00 we will send new recipes for these codes and recipes should then be sent to PCS (because ProductDefinition = 0). Is that correct?\'"", \'Comment 17: ""Yes\', \'Comment 18: that\\\'s right.So I am waiting for final confirmation.Thank you.""\', ""Comment 19: \'Goodmorning,Yesterday at 16:22 a sales order for 303436 with special was sent. 303436 is a code for which you archived the additional technology.The one time recipe is generated on the correct code (303436"", \'Comment 20: version 136 subversion 1\', ""Comment 21: This recipe is sent to DHP but it is not sent to PCS.Did you also archive the three additional technologies in DHP? Otherwise recipe sending is still blocked.Plant needs the recipe for productionCan you please check /fix these recipes.\'"", ""Comment 22: \'Hellofor when you need that recipe - today ? If yes what hour?\'"", ""Comment 23: \'Plant needs the recipe now for production. I have created a new ticket for this:  https://helpdesk.kotrak.com/servicedesk/customer/portal/56/DGS-8882\'"", ""Comment 24: \'It was procced at new task "", ""Comment 25: may we close this 1?\'"", ""Comment 26: \'Please perform same action for the other two codes as well (so that new recipes will be sent to PCS: 303300303306\'"", ""Comment 27: \'Sorry for the late reply"", ""Comment 28: I confirm that the changes have also been made for the others two.\'"", ""Comment 29: \'Thank you. This ticket can be closed.\']""]\nRelated Issues:\n[]\n\n### End'}"
181,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8851\n\n### Instruction:\nError closing  PO - CDN : PO-4/08/2018/RMP \r\nCould this PO be closed.\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Close:!image-2023-03-28-17-50-40-388.png!Yes:!image-2023-03-28-17-51-42-936.png!{code:java}Server stack trace:    at Kotrak.XLInterface.Orders.NewServices.ContractsService.TerminateContract(Int32 gidNumer"", \'Comment 4: OrderCloseMode orderCloseMode) in E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\18317313\\\\\\\\DHGUI-DHCDN982-JOB1\\\\\\\\DH CDN\\\\\\\\Kotrak.XLInterface.Orders\\\\\\\\NewServices\\\\\\\\ContractsService.cs:line 3144Exception rethrown at [0]:    at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg\', \'Comment 5: IMessage retMsg)   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData\', \'Comment 6: Int32 type)   at Kotrak.XLInterface.Orders.Contracts.IContractsService.TerminateContract(Int32 gidNumer\', ""Comment 7: OrderCloseMode orderCloseMode)   at Kotrak.XLInterface.Orders.Presentation.Forms.ContractsList.TerminateContract(OrderCloseMode orderCloseMode) in E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\18317313\\\\\\\\DHGUI-DHCDN982-JOB1\\\\\\\\DH CDN\\\\\\\\Kotrak.XLInterface.Orders.Presentation\\\\\\\\Contracts\\\\\\\\Forms\\\\\\\\ContractsList.cs:line 1669{code}!image-2023-03-28-17-51-42-936!\'"", ""Comment 8: \'Hi,PO is closed now.!image-2023-03-29-12-59-11-105.png!Regards\'"", ""Comment 9: \'I have asked if it is oke.\'"", ""Comment 10: \'Waiting for your feedback then.Regards\'"", ""Comment 11: \'Ticket can be closed\']""]\nRelated Issues:\n[]\n\n### End'}"
182,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8850\n\n### Instruction:\nProśba o uwzględnienie wznowienia naliczania amortyzacji dokumentu RN.\r\nŚrodek trwały do sprawdzenia MT/9126.\r\n\r\n(uzgodnione telefonicznie z Panią Moniką)\n\n### Response:\n[\'Comment 1: [\\\'Please verify after changes in two filters:""Bez dotacji"" and ""Bez dotacji grupa""\\\'\', ""Comment 2: \'Looks good - task to close :)\']""]\nRelated Issues:\n[]\n\n### End'}"
183,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8849\n\n### Instruction:\nFor item 140475, a new recipeversion was sent on 28-03-2023. Recipe is not arriving in PCS. Recipe is not available in recipe overview in DHP. It is available in masterdata overview. In DHC I found that item is linked, but on linking screen it does not show a base item (and DHC stops responding...). Can you check what is the issue with this item / relink it?\r\n\n\n### Response:\n[""Comment 1: [\'!image!!image-1!!image-3!\'"", ""Comment 2: \'Hello,\\\\r\\\\rWe are investigating your issue. We will inform you about the solution as soon as possible.\\\\r\\\\rRegards\\\\r\\\\r\'"", ""Comment 3: \'!image-2023-03-28-14-55-16-648.png!{code:java}2023-03-28 14:53:51 (/Plant.Prod.BusinessLogic/DHVD01AP175/3736/78) [Error] Kotrak.Common.Infrastructure.Integration.Filters.InboundMessagesProcessFilter - Error during process inbound messageKotrak.Common.Application.Exceptions.CommandValidationException`1[Plant.Prod.BusinessLogic.Application.Interfaces.Recipes.Commands.SynchronizeRecipeCommand]: Validation failed: -- RecipeNegativeElementQuantityMessage   at Kotrak.Common.Infrastructure.Gate.Filters.ValidateCommandFilter`1.Execute(CommandPipelineContext`1 input)   at Kotrak.Extensions.Pipeline.Pipeline`1.Execute(T input)   at Kotrak.Common.Infrastructure.Gate.StandardGate.DispatchCommand[TCommand](TCommand command)   at Kotrak.Common.Infrastructure.Integration.Filters.InboundMessageHandlerFilter.Execute(InternalStorageProcessContext`1 input)   at Kotrak.Extensions.Pipeline.Pipeline`1.Execute(T input)   at Kotrak.Common.Infrastructure.Integration.Filters.InboundMessagesProcessFilter.Execute(InternalStorageContext`1 input)2023-03-28 14:54:02 (/Plant.Prod.BusinessLogic/DHVD01AP175/3736/26) [Error] Kotrak.Common.Infrastructure.Integration.Filters.InboundMessagesProcessFilter - Error during process inbound messageKotrak.Common.Application.Exceptions.CommandValidationException`1[Plant.Prod.BusinessLogic.Application.Interfaces.Recipes.Commands.SynchronizeRecipeCommand]: Validation failed: -- RecipeNegativeElementQuantityMessage   at Kotrak.Common.Infrastructure.Gate.Filters.ValidateCommandFilter`1.Execute(CommandPipelineContext`1 input)   at Kotrak.Extensions.Pipeline.Pipeline`1.Execute(T input)   at Kotrak.Common.Infrastructure.Gate.StandardGate.DispatchCommand[TCommand](TCommand command)   at Kotrak.Common.Infrastructure.Integration.Filters.InboundMessageHandlerFilter.Execute(InternalStorageProcessContext`1 input)   at Kotrak.Extensions.Pipeline.Pipeline`1.Execute(T input)   at Kotrak.Common.Infrastructure.Integration.Filters.InboundMessagesProcessFilter.Execute(InternalStorageContext`1 input){code}\'"", ""Comment 4: \'Hi,Recipe with invalid quantity arrived from DHH!image-2023-03-28-15-01-23-372.png!!image-2023-03-28-15-02-08-484.png!You need to ask Holding to create correct one.Best regards\'"", ""Comment 5: \'Ok"", ""Comment 6: Thank you. I will check this with formulation.\'"", ""Comment 7: \'Thank you. Waiting for your feedback thenRegards\'"", ""Comment 8: \'Recipe was not correctly created in Allix. Correct version was sent and is now in DHP and sent to PCS. Would be better if the recipe with invalid composition is not accepted at all in DHC. I will propose this for the change list.This ticket can be closed.\'"", ""Comment 9: \'Thank you.Best regards\']""]\nRelated Issues:\n[]\n\n### End'}"
184,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8848\n\n### Instruction:\nHi, form Wiola.\r\n\r\n\r\n\r\nRafał Boniecki\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Czy chodzi o weryfikację przesłania do systemy XL i zaksięgowania wskazanych dodatków?jeśli tak"", \'Comment 3: to najlepszym sposobem jest utworzenie testowej listy plac na której zostanie naliczony tego typu składnik i przesłanie jej do systemu XL a następnie wykonanie weryfikacji dekretacji po stronie księgowej.Czy są już jakieś wytyczne co do dekretu\', ""Comment 4: na jakie kona powinien być on wykonany? Jeśli tak to proszę o informację.\'"", \'Comment 5: ""It\\\'s ok\', \'Comment 6: task to close\', \'Comment 7: thanks.""]\']\nRelated Issues:\n[]\n\n### End'}"
185,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8847\n\n### Instruction:\nThe image below is a print screen (CDN > Accounting > Documents > Documents) with an IPOR that needs to be posted. As shaded yellow you see that there is an amount on the line. \r\nWhen opening the line with double click and choose: Scheme: POR Internal, an amount should normally be entered here (this may differ from the amount in the line above) and I can adjust the ledger account and make the entry (bottom image) . But now nothing appears and I tried with multiple lines.\r\nThe problem is with both the PORC and SOR. When Richard Gans selects one for both POR and SOR, he will see the amounts.\r\nWijnen sees the amount zero.\r\n\r\nThe authorization for both users is the same\r\n\r\n\n\n### Response:\n[""Comment 1: [\'[^Gans.docx] _(137 kB)_!image!!image-1!!image-2!!image-3![^Wijnen.docx] _(136 kB)_\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'I do not repeat this kind of error on document even on exact permissions  like user Wijnen . Document IPOR-28/01/2023/VIMP is already posted. Do you have any fresh unposted document with the same problem on user Wijnen  where i can test?\'"", ""Comment 4: \'I do not repeat this kind of error on document even on exact permissions like user Wijnen . Document IPOR-28/01/2023/VIMP is already posted. Do you have any fresh unposted document with the same problem on user Wijnen where i can test?\'"", ""Comment 5: \'This is what user Wijnen does see.!image-4!\'"", ""Comment 6: \'User Wijnen has it with all IPOR files. User sees no values \\\\u200b\\\\u200bbut Richard Gans sees everything.For example number 4/04/2023/VIMP"", ""Comment 7: 71/03/2023/VIMP et cetera\'"", ""Comment 8: \'The first is Niels Wijnen and the second is Richard GansNiels see zero and Richard see !image-5!!image-6!\'"", ""Comment 9: \'Both user have the same parameters set in configuration"", \'Comment 10: Both are able to work in De Heus Premix B.V. and Headquaters.Bookkeeping permission center.!image-2023-04-06-15-54-12-359.png!There are some differences beetween those two contexts\', \'Comment 11: for example there are different add-ins running for those twopermission centers. !image-2023-04-06-15-56-40-388.png!Please check if when both operators are working in context of the same permission center\', ""Comment 12: results differs for IPOR-2/04/2023/VIMP document.IPOR-2/04/2023/VIMP document looks correct. There should be no difference when both operators work in context of the samepermission center.\'"", ""Comment 13: \'Both operators are working in context of the same permission center.!image-7!!image-8!\'"", ""Comment 14: \'Please check if both operators are working on the same database. Please ask operator Wijnen to log off and log on into the system and check if he can see values for IPOR documents.\'"", ""Comment 15: \'Please"", ""Comment 16: let me know if expect any additional actions from us regarding this issue? Can we close this ticket?\'"", ""Comment 17: \'Both users are not working with the same record at the same time. Niels calls up a record and sees the amount zero"", \'Comment 18: which he cannot use. If Richard calls it up\', \'Comment 19: he will see a number and can book it in. If Niels then calls up the record again\', ""Comment 20: he will see the numbers.IThey ara not working in the same time on the same record.\'"", ""Comment 21: \'We can not repeat this issue in any IPOR document. We need more informations.Please provide screenshot for full ERPXL module window for Accounting > Posting"", \'Comment 22: General and Header tab when this situations occurs.We need precise informations when (date and time) this happens for wich document.For test purpose plese check if\', \'Comment 23: when Ritchard Gans see ammount on IPOR document\', ""Comment 24: Niels Winjen can post it. Please ask Richard to witraw from posting such document and let Niels do this.\'"", ""Comment 25: \'When Richard consults the record he sees the ammount.When Niels consults the record he sees zeroes.\'"", ""Comment 26: \'Print screens of the differences have already been made and reported. This happens with all documents that Niels consults.!image-9!!image-10!\'"", \'Comment 27: ""If it\\\'s not clear yet\', \'Comment 28: maybe we should start a teams session so Richard and Niels can show the differences.""\', ""Comment 29: \'Provided print screen is cut that I cannot see all the details I need to check.Teams session would be a good idea.\'"", ""Comment 30: \'Here is a description of the authorization of the users\'"", ""Comment 31: \'[^Niels Wijnen.docx] _(192 kB)_[^Richard Gans.docx] _(183 kB)_\'"", \'Comment 32: ""Yes I\\\'ve seen that. Both users have the same configuration for theirs accounts in ERPXL.""\', ""Comment 33: \'Please try to connect to Richard Gans account on Niels Wijnen computer and toNiels Wijnen account onRichard Gans computer"", ""Comment 34: and verify if you are repeting this issue.\'"", \'Comment 35: ""According to information gathered from Niels Winjen\', \'Comment 36: this problem also occurs in his account on other computers.We would like to test one more thing. We will create an exact copy of Niels Winjen\\\'s ERPXL account with a modified ID. Then we will check if this problem still occurs. Please let me know if you accept this solution.""]\']\nRelated Issues:\n[]\n\n### End'}"
186,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8846\n\n### Instruction:\nWe are receiving the same labels (product, plant, version, language)\r\n3 or 4 times in MILAS from DHC.\r\nPlease check why this is happening. \r\n\r\nE.g today (28/3) we received a label for plant 9 recipes 111249 version 334 language nl 3 times withing the same minute.\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 2: \\\'W logu są trzy wpisy jeden po drugim DHERPServiceSendRequest.log.1{code:java}2023-03-28 08:17:17,689 [112] INFO  WcfSendRequestLogger [C:\\\\\\\\Projects\\\\\\\\evolution.dhcerpservice\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.Service\\\\\\\\Logging\\\\\\\\LoggingInspectorBehavior.cs:53] - Request:<s:Envelope xmlns:s=""http://schemas.xmlsoap.org/soap/envelope/"">  <s:Header>    <Action s:mustUnderstand=""1"" xmlns=""http://schemas.microsoft.com/ws/2005/05/addressing/none"">unit01_dhc_adapter_ws_provider_wsd_webMethods_DHC_Provider_Binder_insertLabel</Action>  </s:Header>  <s:Body xmlns:xsi=""http://www.w3.org/2001/XMLSchema-instance"" xmlns:xsd=""http://www.w3.org/2001/XMLSchema"">    <insertLabel xmlns=""http://deheus.com/unit01/DHC"">      <input xmlns="""">        <header>          <ReceivingSystem>Milas</ReceivingSystem>          <SendingSystem>DHC</SendingSystem>          <CreateDate xsi:nil=""true"" />          <CreateUser xsi:nil=""true"" />          <MessageID>29fabb38-ccfd-4427-ad77-f19fbf15fffe</MessageID>        </header>        <label>          <itemCode>111249</itemCode>          <creationDate>3/24/2023 9:12:54 PM</creationDate>          <plant>9</plant>          <recipeVersion>334</recipeVersion>  \\\\t\\\\t...\\\\t\\\\t\\\\t\\\\t2023-03-28 08:17:18,298 [112] INFO  WcfSendRequestLogger [C:\\\\\\\\Projects\\\\\\\\evolution.dhcerpservice\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.Service\\\\\\\\Logging\\\\\\\\LoggingInspectorBehavior.cs:53] - Request:<s:Envelope xmlns:s=""http://schemas.xmlsoap.org/soap/envelope/"">  <s:Header>    <Action s:mustUnderstand=""1"" xmlns=""http://schemas.microsoft.com/ws/2005/05/addressing/none"">unit01_dhc_adapter_ws_provider_wsd_webMethods_DHC_Provider_Binder_insertLabel</Action>  </s:Header>  <s:Body xmlns:xsi=""http://www.w3.org/2001/XMLSchema-instance"" xmlns:xsd=""http://www.w3.org/2001/XMLSchema"">    <insertLabel xmlns=""http://deheus.com/unit01/DHC"">      <input xmlns="""">        <header>          <ReceivingSystem>Milas</ReceivingSystem>          <SendingSystem>DHC</SendingSystem>          <CreateDate xsi:nil=""true"" />          <CreateUser xsi:nil=""true"" />          <MessageID>29fabb38-ccfd-4427-ad77-f19fbf15fffe</MessageID>        </header>        <label>          <itemCode>111249</itemCode>          <creationDate>3/24/2023 9:12:54 PM</creationDate>          <plant>9</plant>          <recipeVersion>334</recipeVersion>          <quantity>\\\\t\\\\t  ...\\\\t\\\\t  \\\\t\\\\t  2023-03-28 08:17:18,548 [81] INFO  WcfSendRequestLogger [C:\\\\\\\\Projects\\\\\\\\evolution.dhcerpservice\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.Service\\\\\\\\Logging\\\\\\\\LoggingInspectorBehavior.cs:53] - Request:<s:Envelope xmlns:s=""http://schemas.xmlsoap.org/soap/envelope/"">  <s:Header>    <Action s:mustUnderstand=""1"" xmlns=""http://schemas.microsoft.com/ws/2005/05/addressing/none"">unit01_dhc_adapter_ws_provider_wsd_webMethods_DHC_Provider_Binder_insertLabel</Action>  </s:Header>  <s:Body xmlns:xsi=""http://www.w3.org/2001/XMLSchema-instance"" xmlns:xsd=""http://www.w3.org/2001/XMLSchema"">    <insertLabel xmlns=""http://deheus.com/unit01/DHC"">      <input xmlns="""">        <header>          <ReceivingSystem>Milas</ReceivingSystem>          <SendingSystem>DHC</SendingSystem>          <CreateDate xsi:nil=""true"" />          <CreateUser xsi:nil=""true"" />          <MessageID>29fabb38-ccfd-4427-ad77-f19fbf15fffe</MessageID>        </header>        <label>          <itemCode>111249</itemCode>          <creationDate>3/24/2023 9:12:54 PM</creationDate>          <plant>9</plant>          <recipeVersion>334</recipeVersion>\\\\t\\\\t  ...{code}Cały fragment loga - jest różnica w godzinie i kończą się sukcesem.  [^DHERPServiceSendRequest.log.1 fragment.txt] W logu DHERPService też  jest trzy razy informacja o wysyłce:!image-2023-03-28-12-13-10-547!\\\'\', ""Comment 3: \'W ostatnim komentarzu jest info jak klient przekazał - przykładowa labelka jest trzy krotnie wysyłana"", ""Comment 4: prośba o pomoc w analizie z czego to może wynikać - dzięki.\'"", ""Comment 5: \'Hi"", ""Comment 6: DHCErpService has been changed to block multiple data sending described in the task.It will be required to be DHCErpService upgraded(upgrade date should be set with the PM).\'"", ""Comment 7: \'DHCErpService has been changed to block multiple data sending described in the task.\\\\rIt will be required to be DHCErpService upgraded(upgrade date should be set with the PM).\\\\rThis issue has been closed.\']""]\nRelated Issues:\n[]\n\n### End'}"
187,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8845\n\n### Instruction:\nHi\r\n\r\nWe are facing issues with Orders sync from DHC to DHP in Rio Claro.\r\nSeveral orders are integrated to DHC, no erros are reported and we can\'t find these orders in DHP.\r\nFor example, we have these examples:\r\n\r\n||Order||DocumentId||DHC integration||DHP integration\r\n|OVE-080259|5638073942|2023-03-08 14:17:53.120|2023-03-24 16:48:06.634|\r\n|OVE-080263|5638071657|2023-03-08 14:17:53.339|2023-03-24 16:48:06.767|\r\n|OVE-080271|5638073182|2023-03-08 14:37:54.235|2023-03-24 16:48:06.271|\r\n\r\nAs you can check in the log register, DHC had no error during ERP integration request.\r\n\r\nThis turned very critical because we are running out of time to buy raw materials and produce these items. We had the same situation with DGS-8776 and now we have these.\r\n\r\nNo other plants reported this issue. It is probably a version issue.\r\n\r\nCould you please check why is this happening?\r\n\r\nThank you very much!\n\n### Response:\n[""Comment 1: [\'logi erp service z 8mego :Line 1926: 2023-03-08 14:17:53,120[117]INFO Evolution.DHCERPService.Service.BaseSaveService`1[E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\18317313\\\\\\\\DHAPPSV3-DHCER401-JOB1\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.Service\\\\\\\\BaseSaveService.cs:79]- Saved: OrderObject with Id Company: 1 DocType:2 Id: 5638073942 Suffix PEDUnmapDeletedElements deletedElements.Count = 0!image-2023-03-27-19-21-14-094.png!!image-2023-03-27-19-21-14-094!ale wygląda to ok chyba ?Pytałam sie klienta czy poda namiar co nam było wysyłane 8mego ale nie ejst chetny. sprawdziłam że dhhitemy i itemy nie były ostatnio w ogóle edytowane.\'"", ""Comment 2: \'Please be informed that we have forwarded the issue to the development team in order to internal analysis.We are waiting for more details and will be back with further information as soon as possible.\'"", \'Comment 3: ""We are very sorry [~mberbert@deheus.com]that you are facing a problem with synchronization. However this isn\\\'t our job to monitor the status of your disks\', \'Comment 4: this is something that yous infrastructure team should do.!image-2023-03-31-13-37-16-800.png|width=1775,height=893!""\', \'Comment 5: ""HI [~Thank you for the analysis\', \'Comment 6: and you are right! It\\\'s our job to monitor the status of our disks. I\\\'ll request such monitoring to our IT team.I\\\'d like to understand why the transaction log of Evolution_DHCountry database is increasing so fast?Look the free space in disk server. Did you shrinked the files?Thank you!image!""\', ""Comment 7: \'Aktualnie jest tyle samo !screenshot-1! \']""]\nRelated Issues:\n[\'DGS-8842\']\n\n### End'}"
188,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8844\n\n### Instruction:\nHi\r\n\r\nWe want all plants with R8.5 (+GDC_2-3weeks) for:\r\n* Itaberaí\r\n* Apucarana\r\n* Toledo\r\n* Guararapes\r\n\r\nCould you please schedule the update untill 10am CEST for each plant?\r\nWhen is the next available date for you?\r\n\r\nThank you very much\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'HiDid you have the opportunity to check this request?Thank you\'"", ""Comment 3: \'Hi [~mberbert@deheus.com]Estimation for upgrade from *8.3* to *8.5* per plant: * *18h* - the most likely case * +20% - the worst case * Working hours: Monday-Friday 7:00-15:00 CEST * Hyper care recommended but not included in the estimation. To be discussed.Draft plan: * 12.04.2023: Apucarana / 7:00-11:00 CEST / * 13.04.2023: Toledo / 7:00-11:00 CEST / * 16.04.2023: Itaberai/ 7:00-11:00 CEST / * 17.04.2023: Guararapes/ 7:00-11:00 CEST /\'"", \'Comment 4: ""Hi [~marcin.kleszcz@kotrak.com]We had an internal request to do scheduled maintenance on the DHApps applications over the weekend.We have the following window of no activies in the factories:||Plant||Stops at||Starts at|||GUA|Saturday 11am CEST|Monday 11am CEST||ITA|Saturday 11am CEST|Monday 11am CEST||APU|Saturday 11am CEST|Monday 5am CEST||TOL|Sunday 4am CEST|Monday 10am CEST|We know about additional costs on Saturdays and Sundays. So I\\\'d like to propose:||Plant||Date||Time|||GUA|10.04.2023|07am-11am CEST||ITA|10.04.2023|07am-11am CEST||TOL|10.04.2023|07am-10am CEST||APU|15.04.2023|11am-03pm CEST|As default\', \'Comment 5: we need to test access in the Friday so IT team can assure that you have right access before.Is it possible to do it in this time?Thank you""\', \'Comment 6: ""[~mberbert@deheus.com]On Sunday and Monday in Poland we have Easter holidays. So\', \'Comment 7: on Monday we can\\\'t upgrade.""\', \'Comment 8: ""Hi [~Marcin.Kleszcz@kotrak.com]New proposal:||Plant||Date||Time|||*APU*|15.04.2023|11am-03pm CEST||*GUA*|17.04.2023|07am-11am CEST||*ITA*|17.04.2023|07am-11am CEST||*TOL*|17.04.2023|07am-10am CEST|We can\\\'t make these updates during the week because factories are running 24hs.Thank you very much!""\', ""Comment 9: \'[~mberbert@deheus.com]I discussed this planning internally.We can do upgrades of DHP from Mon to Fri"", ""Comment 10: working hours 7:00-16:00.17.04.2023 :* ITA* GUA22.04.2023:* APU* TO\'"", ""Comment 11: \'Hi [~mberbert@deheus.com]as we have discussed last evening"", ""Comment 12: I will let you next week. We will be back work on Tuesday and I will try to manage it. \'"", ""Comment 13: \'[~mberbert@deheus.com]New proposal:||Plant||Date||Time|||*ITA*|17.04.2023|07am-11am CEST||*TOL*|17.04.2023|06am-10am CEST||*APU*|21.04.2023|07am-11am CEST||*GUA*|21.04.2023|12pm-16pm CEST|Before upgrade we need to check Evenet DB (DGS-8827)We will start on Friday - we need to prepare the version before upgrade"", ""Comment 14: and we will check servers and queues.Do you need hyper care?Do you approve the estimation?\'"", \'Comment 15: ""Hi [~marcin.kleszcz@kotrak.com]Final dates/times:||Plant||Date||Time|||ITA|17.04.2023|07am-11am CEST||TOL|17.04.2023|06am-10am CEST||APU|21.04.2023|12pm-16pm CEST||GUA|21.04.2023|12pm-16pm CEST|About checking servers\', \'Comment 16: will you need admin access to these servers?To whom we need to grant access?We don\\\'t need hyper care.Estimation approved!Thank you""\', ""Comment 17: \'[~mberbert@deheus.com]admin access for:* Marcin Kleszcz* Maciej Buchacz* Wojciech Pyrlik* Maciej Dobrzanski\'"", ""Comment 18: \'[~piotr.gaczorek@kotrak.com] wszystkie fabryki (oczywiście oprócz Caruaru) podniesione z 8.3 do 8.5. Można zamknąć task.\'"", ""Comment 19: \'Plants:\\\\r * Itaberaí\\\\r * Apucarana\\\\r * Toledo\\\\r * Guararapes\\\\r\\\\rhave been updated to 8.5.\']""]\nRelated Issues:\n[\'DGS-8727\']\n\n### End'}"
189,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8843\n\n### Instruction:\nIt has been found out that the recipe 23VOL030 is incorrectly linked in DHP. It is linked with the recipe 23GVL0125 (see print screen) and now the 6th version of the recipe 23VOL030 is shown as the 6th version of the recipe 23GVL0125 in Production Module\r\n\r\nAll our efforts to unlink these two recipes are in vain, so it would be highly appreciated if you could help us with this issue.\r\n\n\n### Response:\n[""Comment 1: [\'!1.jpg|thumbnail!!2.jpg|thumbnail!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 3: \\\'good morning As far as I can see in DHc there is only base item with code similar to 23VOL030 is 23VOL030.25 do you wish set this as base item or you need to have code ""23VOL030""?\\\'\', ""Comment 4: \'We would like to have 23VOL030 as a base item and 23VOL030.25 as a sub-item\'"", ""Comment 5: \'there is no item23VOL030 in DHC could you please sent it ?\'"", ""Comment 6: \'do need to send the new version of the recipe from Bestmix or what do you mean?\'"", ""Comment 7: \'The new version for that recipe will be needed also"", ""Comment 8: but there is no item with code23VOL030 ( just that without no suffix) in your DHC. So I am unable to set it as base item. Could you send it from you ERP.\'"", ""Comment 9: \'code sent from ERP\'"", ""Comment 10: \'Ok please verify "", ""Comment 11: please resend new reciepes from dhh and send create new recipes and etc for that item.!image-2023-03-29-14-19-31-561.png!\'"", ""Comment 12: \'We checked"", ""Comment 13: everything is fine now\']""]\nRelated Issues:\n[]\n\n### End'}"
190,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8842\n\n### Instruction:\nHi\r\n\r\nWe are facing issues with Orders sync from DHC to DHP in Rio Claro.\r\nSeveral orders are integrated to DHC, no erros are reported and we can\'t find these orders in DHP.\r\nFor example, we have these examples:\r\n\r\n||Order||DocumentId||DHC integration||DHP integration\r\n|OVE-080259|5638073942|2023-03-08 14:17:53.120|2023-03-24 16:48:06.634|\r\n|OVE-080263|5638071657|2023-03-08 14:17:53.339|2023-03-24 16:48:06.767|\r\n|OVE-080271|5638073182|2023-03-08 14:37:54.235|2023-03-24 16:48:06.271|\r\n\r\nAs you can check in the log register, DHC had no error during ERP integration request.\r\n\r\nThis turned very critical because we are running out of time to buy raw materials and produce these items. We had the same situation with DGS-8776 and now we have these.\r\n\r\nNo other plants reported this issue. It is probably a version issue.\r\n\r\nCould you please check why is this happening?\r\n\r\nThank you very much!\n\n### Response:\n[""Comment 1: [\'[^DHERPService.log20230308] _(7,12 MB)_\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Are there any missing orders right now?If not kindly approve lowering priority of this task to P2 as P1 issues are only those with a critical or a blocking impact on business processes . This seems not to be the case in this issue so we suggest decreasing the issue priority.\'"", \'Comment 4: ""Hi AgnieszkaYou can lower the priority to P2\', \'Comment 5: but I need that this issue will be analysed tomorrow morining in the first time. We manually synchronized all Orders needed for today and tomorrow.However we are talking about a loss of R$ 100k per day. This is huge. That\\\'s why we need a quick solution.Thank you very much""\', \'Comment 6: ""create date na dhc service jest 16.47select i.UpdateDate,i.CreateDate,o.CreateDate\', \'Comment 7: o.UpdateDate,i.DhhItemId,* from OrderElements oejoin orders o on oe.orderid=o.id join items i on i.id=oe.ItemId where o.ForeignDocumentNumber in (\\\'OVE-080259\\\',\\\'OVE-080263\\\',\\\'OVE-080271\\\')!image-2023-03-27-19-08-50-500.png!""\', ""Comment 8: \'logi erp service z 8mego :Line 1926: 2023-03-08 14:17:53,120 [117] INFO Evolution.DHCERPService.Service.BaseSaveService`1 [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\18317313\\\\\\\\DHAPPSV3-DHCER401-JOB1\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.Service\\\\\\\\BaseSaveService.cs:79] - Saved: OrderObject with Id Company: 1 DocType:2 Id: 5638073942 Suffix PEDUnmapDeletedElements deletedElements.Count = 0!image-2023-03-27-19-21-14-094.png! !image-2023-03-27-19-21-14-094!ale wygląda to ok chyba ?\'"", ""Comment 9: \'Hello,If there is a need from your sideto investigate the reasonof the issue"", \'Comment 10: we may raise RootCause Analysis (RCA)task for you.Please\', ""Comment 11: let us knowhow you wish us to proceed.Also If you want us to verify what happens please provide us information: * what was send to us from YOUR ERP or Dynamics system - we do not have access how that orders look at that moment. * how it was proceed?\'"", \'Comment 12: ""HiYes\', \'Comment 13: please\', \'Comment 14: raise a RCA.I\\\'m attaching the Service received request log file from DHC with information about data sent to you. And you have the Service log file attached when opening this issue.It proceeded with normal flow as all other orders:# We send from ERP# It integrates to DHC# DHC returns a success (or error) message# Minutes later the order is present on DHP systemThank you very much[^DHERPServiceReceivedRequest.log20230308] _(4,60 MB)_""\', ""Comment 15: \'HiPlease"", ""Comment 16: also check DGS-8177Thank you\'"", ""Comment 17: \'RCa was created under dgs-8845"", ""Comment 18: may we close this task?\'"", \'Comment 19: ""HiYes! You can close this task.We\\\'ll follow on DGS-8845Thank you very much""]\']\nRelated Issues:\n[\'DGS-8845\']\n\n### End'}"
191,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8841\n\n### Instruction:\nwe just discovered that since the update of DHP to version 8.5, the webservice is rejecting batch reports for the reason: \'Production lot element quantity should be greater than 0\': This is a change compared to the previous versions, which wasn\'t expecting. For this reason now many batch reports are rejected and we running into issues with our finished product stock in the ERP: Can you please check this? I think we need a fix for this, we\'re missing quite some batch reports for all locations\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Hi [~TDankers@deheus.com],This validation in fact was added during the hyper care in Guararapes in Brasil.We will introduce the configuration for that.Since it is a SQL procedure we will remove this validation on production.\'"", ""Comment 3: \'Zmiana była zrealizowana w DAP-13108 i dotyczy 3 procedur. Wrzucam skrypty do aktualizacji tych procedur na bazie modułu PCS Main w wersji 8.5. Jeżeli zostaną podane wartości ujemne"", \'Comment 4: to wciąż poleci błąd. Dotyczy to ilości na elementach PLR i ELR oraz ilości na dostawach powiązanych z elementami PLR i ELR. Skrypty wrzucam w osobnych komentarzach\', \'Comment 5: bo Jira narzeka\', ""Comment 6: że jest za dużo tekstu.\'"", \'Comment 7: ""*api.RegisterBatchReport*:{code:sql}CREATE OR ALTER PROCEDURE api.RegisterBatchReport(\\\\t@PcsLotId BIGINT,\\\\t@PcsBatchId BIGINT,\\\\t@QuantityKg DECIMAL(18,6),\\\\t@IsBrokenBatch BIT = 0,\\\\t@ReworkItemId INT = NULL,\\\\t@StartBatchMixing DATETIME2 = NULL,\\\\t@FinishBatchMixing DATETIME2 = NULL)ASBEGIN\\\\tSET NOCOUNT ON;\\\\tBEGIN TRY\\\\t\\\\tBEGIN -- Logger\\\\t\\\\t\\\\tDECLARE @Parameters NVARCHAR(MAX) = (\\\\t\\\\t\\\\t\\\\tSELECT\\\\t\\\\t\\\\t\\\\t\\\\t@PcsLotId AS PcsLotId,\\\\t\\\\t\\\\t\\\\t\\\\t@PcsBatchId AS PcsBatchId,\\\\t\\\\t\\\\t\\\\t\\\\t@QuantityKg AS QuantityKg,\\\\t\\\\t\\\\t\\\\t\\\\t@IsBrokenBatch AS IsBrokenBatch,\\\\t\\\\t\\\\t\\\\t\\\\t@ReworkItemId AS ReworkItemId,\\\\t\\\\t\\\\t\\\\t\\\\t@StartBatchMixing AS StartBatchMixing,\\\\t\\\\t\\\\t\\\\t\\\\t@FinishBatchMixing AS FinishBatchMixing,\\\\t\\\\t\\\\t\\\\t\\\\t(\\\\t\\\\t\\\\t\\\\t\\\\t\\\\tSELECT Id\', \'Comment 8: PcsLotId\', \'Comment 9: PcsBatchId\', \'Comment 10: ItemId\', \'Comment 11: RecipeElementId\', \'Comment 12: QuantityKg,\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t(\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t\\\\tSELECT Id\', \'Comment 13: ElementId\', \'Comment 14: DeliveryId\', \'Comment 15: Barcode\', \'Comment 16: SiloCode\', \'Comment 17: QuantityKg\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t\\\\tFROM api.ProductionLotElementDeliveries APLED\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t\\\\tWHERE APLED.ElementId = APLE.Id\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t\\\\tFOR JSON AUTO\', \'Comment 18: INCLUDE_NULL_VALUES\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t) As Deliveries\\\\t\\\\t\\\\t\\\\t\\\\t\\\\tFROM api.ProductionLotElements APLE\\\\t\\\\t\\\\t\\\\t\\\\t\\\\tWHERE PcsLotId = @PcsLotId AND PcsBatchId = @PcsBatchId\\\\t\\\\t\\\\t\\\\t\\\\t\\\\tFOR JSON AUTO\', \'Comment 19: INCLUDE_NULL_VALUES\\\\t\\\\t\\\\t\\\\t\\\\t) AS Elements\\\\t\\\\t\\\\t\\\\tFOR JSON PATH\', \'Comment 20: INCLUDE_NULL_VALUES\', ""Comment 21: WITHOUT_ARRAY_WRAPPER)\\\\t\\\\t\\\\tDECLARE @RequestLogId BIGINT\\\\t\\\\t\\\\tEXEC dbo.SaveSqlApiRequest \'RegisterBatchReport\'"", \'Comment 22: @Parameters\', ""Comment 23: @RequestLogId OUTPUT\\\\t\\\\tEND -- Logger\\\\t\\\\t\\\\t\\\\tDECLARE @ConstFactoryObjectTypeDosingSilo INT = 1\\\\t\\\\tDECLARE @ConstBatchReportType INT = 1\\\\t\\\\tDECLARE @ConstBatchStatusFinished INT = 3\\\\t\\\\tDECLARE @ConstAllowStockRegisteringOnSilosKey INT = 3\\\\t\\\\tDECLARE @ConstAllowStockRegisteringOnSilosTrueValue NVARCHAR(4) = \'True\'\\\\t\\\\tDECLARE @ProductionLotAggregateId UNIQUEIDENTIFIER\\\\t\\\\tDECLARE @RecipeAggregateId UNIQUEIDENTIFIER\\\\t\\\\tDECLARE @ReworkItemAggregateId UNIQUEIDENTIFIER\\\\t\\\\tDECLARE @AllowStockRegisteringOnSilos BIT\\\\t\\\\tDECLARE @ConstUndefinedBrokenBatchStatus INT = 0\\\\t\\\\tDECLARE @ConstCreatedBrokenBatchStatus INT = 1\\\\t\\\\tDECLARE @ConstConfirmedBrokenBatchStatus INT = 2\\\\t\\\\tDECLARE @SetRequestedQuantityBasedOnQuantity BIT\\\\t\\\\tBEGIN -- Validation\\\\t\\\\t\\\\tIF (@PcsLotId IS NULL)\\\\t\\\\t\\\\t\\\\tTHROW 50000"", ""Comment 24: \'Parameter @PcsLotId cannot be null.\'"", \'Comment 25: 1;\\\\t\\\\t\\\\tIF (@PcsBatchId IS NULL)\\\\t\\\\t\\\\t\\\\tTHROW 50000\', ""Comment 26: \'Parameter @PcsBatchId cannot be null.\'"", \'Comment 27: 1;\\\\t\\\\t\\\\tIF (ISNULL(@QuantityKg,0) <= 0)\\\\t\\\\t\\\\t\\\\tTHROW 50000\', ""Comment 28: \'Parameter @QuantityKg cannot be null and should be greater than 0.\'"", \'Comment 29: 1;\\\\t\\\\t\\\\tSET @ProductionLotAggregateId = (SELECT Id FROM dbo.ProductionLots WHERE PcsLotId = @PcsLotId)\\\\t\\\\t\\\\tIF (@ProductionLotAggregateId IS NULL)\\\\t\\\\t\\\\t\\\\tTHROW 50000\', ""Comment 30: \'Production lot does not exist.\'"", \'Comment 31: 1;\\\\t\\\\t\\\\tIF (SELECT BrokenBatchStatus FROM dbo.Batches WHERE Id = @ProductionLotAggregateId AND PcsBatchId = @PcsBatchId) = @ConstConfirmedBrokenBatchStatus\\\\t\\\\t\\\\t\\\\tTHROW 50000\', ""Comment 32: \'Cannot update batch report for confirmed broken batch\'"", \'Comment 33: 1;\\\\t\\\\t\\\\tIF EXISTS (\\\\t\\\\t\\\\t\\\\tSELECT *\\\\t\\\\t\\\\t\\\\tFROM api.ProductionLotElements APLE\\\\t\\\\t\\\\t\\\\tWHERE APLE.PcsLotId = @PcsLotId AND APLE.PcsBatchId = @PcsBatchId AND APLE.QuantityKg < 0\\\\t\\\\t\\\\t)\\\\t\\\\t\\\\t\\\\tTHROW 50000\', ""Comment 34: \'Production lot element quantity cannot be negative.\'"", \'Comment 35: 1;\\\\t\\\\t\\\\t\\\\t\\\\t\\\\tSET @RecipeAggregateId = (SELECT RecipeId FROM dbo.ProductionLots WHERE Id = @ProductionLotAggregateId)\\\\t\\\\t\\\\tIF EXISTS (\\\\t\\\\t\\\\t\\\\tSELECT *\\\\t\\\\t\\\\t\\\\tFROM api.ProductionLotElements APLE\\\\t\\\\t\\\\t\\\\tLEFT JOIN dbo.RecipeElements RE ON APLE.RecipeElementId = RE.EntityId\\\\t\\\\t\\\\t\\\\tWHERE APLE.PcsLotId = @PcsLotId AND APLE.PcsBatchId = @PcsBatchId AND APLE.RecipeElementId IS NOT NULL AND (RE.Id IS NULL OR RE.Id != @RecipeAggregateId)\\\\t\\\\t\\\\t)\\\\t\\\\t\\\\t\\\\tTHROW 50000\', ""Comment 36: \'Recipe element in report does not belong to recipe related to current production.\'"", \'Comment 37: 1;\\\\t\\\\t\\\\tIF EXISTS (\\\\t\\\\t\\\\t\\\\tSELECT *\\\\t\\\\t\\\\t\\\\tFROM api.ProductionLotElements APLE\\\\t\\\\t\\\\t\\\\tJOIN api.ProductionLotElementDeliveries APLED ON APLE.Id = APLED.ElementId\\\\t\\\\t\\\\t\\\\tWHERE APLE.PcsLotId = @PcsLotId AND APLE.PcsBatchId = @PcsBatchId AND APLED.QuantityKg < 0\\\\t\\\\t\\\\t)\\\\t\\\\t\\\\t\\\\tTHROW 50000\', ""Comment 38: \'Production lot element delivery quantity cannot be negative.\'"", \'Comment 39: 1;\\\\t\\\\t\\\\tIF EXISTS (\\\\t\\\\t\\\\t\\\\tSELECT *\\\\t\\\\t\\\\t\\\\tFROM api.ProductionLotElements APLE\\\\t\\\\t\\\\t\\\\tJOIN api.ProductionLotElementDeliveries APLED ON APLE.Id = APLED.ElementId\\\\t\\\\t\\\\t\\\\tLEFT JOIN dbo.StockUnits SU ON APLED.Barcode = SU.Barcode\\\\t\\\\t\\\\t\\\\tWHERE APLE.PcsLotId = @PcsLotId AND APLE.PcsBatchId = @PcsBatchId AND APLED.Barcode IS NOT NULL AND SU.Id IS NULL\\\\t\\\\t\\\\t)\\\\t\\\\t\\\\t\\\\tTHROW 50000\', ""Comment 40: \'Some stock unit barcodes do not exist.\'"", \'Comment 41: 1;\\\\t\\\\t\\\\tIF EXISTS (\\\\t\\\\t\\\\t\\\\tSELECT *\\\\t\\\\t\\\\t\\\\tFROM api.ProductionLotElements APLE\\\\t\\\\t\\\\t\\\\tJOIN api.ProductionLotElementDeliveries APLED ON APLE.Id = APLED.ElementId\\\\t\\\\t\\\\t\\\\tJOIN dbo.StockUnits SU ON APLED.Barcode = SU.Barcode\\\\t\\\\t\\\\t\\\\tJOIN dbo.Deliveries D ON APLED.DeliveryId = D.EntityId\\\\t\\\\t\\\\t\\\\tWHERE APLE.PcsLotId = @PcsLotId AND APLE.PcsBatchId = @PcsBatchId AND D.Id != SU.DeliveryId\\\\t\\\\t\\\\t)\\\\t\\\\t\\\\t\\\\tTHROW 50000\', ""Comment 42: \'Barcode delivery in report does not match stock unit delivery.\'"", \'Comment 43: 1;\\\\t\\\\t\\\\tIF (@IsBrokenBatch = 1 AND @ReworkItemId IS NOT NULL)\\\\t\\\\t\\\\tBEGIN\\\\t\\\\t\\\\t\\\\tSET @ReworkItemAggregateId = (SELECT Id FROM dbo.Items WHERE EntityId = @ReworkItemId)\\\\t\\\\t\\\\t\\\\tIF (@ReworkItemAggregateId IS NULL)\\\\t\\\\t\\\\t\\\\t\\\\tTHROW 50000\', ""Comment 44: \'Rework item does not exist.\'"", \'Comment 45: 1;\\\\t\\\\t\\\\tEND\\\\t\\\\t\\\\tSET @AllowStockRegisteringOnSilos = IIF((\\\\t\\\\t\\\\t\\\\tSELECT [Value]\\\\t\\\\t\\\\t\\\\tFROM dbo.Configuration\\\\t\\\\t\\\\t\\\\tWHERE [Key] = @ConstAllowStockRegisteringOnSilosKey) = @ConstAllowStockRegisteringOnSilosTrueValue,\\\\t\\\\t\\\\t\\\\t1,\\\\t\\\\t\\\\t\\\\t0)\\\\t\\\\t\\\\tIF (@AllowStockRegisteringOnSilos = 1)\\\\t\\\\t\\\\tBEGIN\\\\t\\\\t\\\\t\\\\tIF EXISTS (\\\\t\\\\t\\\\t\\\\t\\\\tSELECT *\\\\t\\\\t\\\\t\\\\t\\\\tFROM api.ProductionLotElements APLE\\\\t\\\\t\\\\t\\\\t\\\\tJOIN api.ProductionLotElementDeliveries APLED ON APLE.Id = APLED.ElementId\\\\t\\\\t\\\\t\\\\t\\\\tWHERE APLE.PcsLotId = @PcsLotId AND APLE.PcsBatchId = @PcsBatchId AND (APLED.DeliveryId IS NOT NULL OR APLED.Barcode IS NOT NULL) AND APLED.SiloCode IS NOT NULL\\\\t\\\\t\\\\t\\\\t)\\\\t\\\\t\\\\t\\\\t\\\\tTHROW 50000\', ""Comment 46: \'Element delivery cannot specify both delivery and silo.\'"", \'Comment 47: 1;\\\\t\\\\t\\\\t\\\\tIF EXISTS (\\\\t\\\\t\\\\t\\\\t\\\\tSELECT *\\\\t\\\\t\\\\t\\\\t\\\\tFROM api.ProductionLotElements APLE\\\\t\\\\t\\\\t\\\\t\\\\tJOIN api.ProductionLotElementDeliveries APLED ON APLE.Id = APLED.ElementId\\\\t\\\\t\\\\t\\\\t\\\\tJOIN dbo.FactoryObjects FO ON APLED.SiloCode = FO.PcsCode\\\\t\\\\t\\\\t\\\\t\\\\tWHERE APLE.PcsLotId = @PcsLotId AND APLE.PcsBatchId = @PcsBatchId AND FO.ObjectType != @ConstFactoryObjectTypeDosingSilo\\\\t\\\\t\\\\t\\\\t)\\\\t\\\\t\\\\t\\\\t\\\\tTHROW 50000\', ""Comment 48: \'Not all silos are of dosing silo type.\'"", \'Comment 49: 1;\\\\t\\\\t\\\\t\\\\tIF EXISTS (\\\\t\\\\t\\\\t\\\\t\\\\tSELECT *\\\\t\\\\t\\\\t\\\\t\\\\t\\\\tFROM api.ProductionLotElements APLE\\\\t\\\\t\\\\t\\\\t\\\\t\\\\tJOIN api.ProductionLotElementDeliveries APLED ON APLE.Id = APLED.ElementId\\\\t\\\\t\\\\t\\\\t\\\\t\\\\tJOIN dbo.FactoryObjects FO ON APLED.SiloCode = FO.PcsCode\\\\t\\\\t\\\\t\\\\t\\\\t\\\\tJOIN dbo.Items I ON I.EntityId = APLE.ItemId\\\\t\\\\t\\\\t\\\\t\\\\tWHERE APLE.PcsLotId = @PcsLotId AND APLE.PcsBatchId = @PcsBatchId AND (FO.ItemId IS NULL OR i.Id != FO.ItemId)\\\\t\\\\t\\\\t\\\\t)\\\\t\\\\t\\\\t\\\\t\\\\tTHROW 50000\', ""Comment 50: \'Raw material on silo does not match to raw material on element.\'"", \'Comment 51: 1;\\\\t\\\\t\\\\tEND\\\\t\\\\t\\\\tIF (@StartBatchMixing IS NULL)\\\\t\\\\t\\\\t\\\\tSET @StartBatchMixing = GETDATE()\\\\t\\\\t\\\\tIF (@FinishBatchMixing IS NULL)\\\\t\\\\t\\\\t\\\\tSET @FinishBatchMixing = GETDATE()\\\\t\\\\t\\\\tIF (@StartBatchMixing > @FinishBatchMixing)\\\\t\\\\t\\\\t\\\\tTHROW 50000\', ""Comment 52: \'Batch start date cannot be later than finish date.\'"", \'Comment 53: 1;\\\\t\\\\tEND -- Validation\\\\t\\\\t\\\\t\\\\tDECLARE @EmptyGuid UNIQUEIDENTIFIER = (SELECT CAST(0x0 AS UNIQUEIDENTIFIER))\\\\t\\\\tDECLARE @ElementsMappings TABLE (ApiElementId BIGINT NOT NULL\', \'Comment 54: ExecutionNo INT\', \'Comment 55: ElementNo INT\', \'Comment 56: Ratio DECIMAL(16,6) NOT NULL)\\\\t\\\\tDECLARE @ElementDeliveries TABLE (Id INT NOT NULL\', \'Comment 57: DeliveryAggregateId UNIQUEIDENTIFIER NOT NULL\', \'Comment 58: StockUnitAggregateId UNIQUEIDENTIFIER\', \'Comment 59: QuantityKg DECIMAL(18,6) NOT NULL\', \'Comment 60: ElementNo INT NOT NULL\', \'Comment 61: TotalStockUnitConsumption BIT NOT NULL)\\\\t\\\\tDECLARE @ExecutionElementDeliveries TABLE (Id INT NOT NULL\', \'Comment 62: DeliveryAggregateId UNIQUEIDENTIFIER NOT NULL\', \'Comment 63: StockUnitAggregateId UNIQUEIDENTIFIER\', \'Comment 64: QuantityKg DECIMAL(18,6) NOT NULL\', \'Comment 65: ExecutionNo INT NOT NULL\', \'Comment 66: ElementNo INT NOT NULL)\\\\t\\\\tDECLARE @TmpDosings TABLE (ElementId INT NOT NULL\', \'Comment 67: DeliveryAggregateId UNIQUEIDENTIFIER\', \'Comment 68: StockUnitAggregateId UNIQUEIDENTIFIER\', \'Comment 69: SiloAggregateId UNIQUEIDENTIFIER\', \'Comment 70: QuantityKg DECIMAL(18,6))\\\\t\\\\tBEGIN TRANSACTION\\\\t\\\\tBEGIN -- Validation\\\\t\\\\t\\\\tDECLARE @ConstProductionStatusInProgress INT = 2\\\\t\\\\t\\\\tIF (SELECT Status FROM dbo.ProductionLots WHERE Id = @ProductionLotAggregateId) != @ConstProductionStatusInProgress\\\\t\\\\t\\\\t\\\\tTHROW 50000\', ""Comment 71: \'Production lot is finished.\'"", \'Comment 72: 1;\\\\t\\\\t\\\\tIF (SELECT Type FROM dbo.Batches WHERE Id = @ProductionLotAggregateId AND PcsBatchId = @PcsBatchId) != @ConstBatchReportType\\\\t\\\\t\\\\t\\\\tTHROW 50000\', ""Comment 73: \'Invalid batch type.\'"", \'Comment 74: 1;\\\\t\\\\tEND -- Validation\\\\t\\\\tBEGIN -- Production lot quantity update\\\\t\\\\t\\\\tUPDATE dbo.ProductionLots\\\\t\\\\t\\\\tSET Quantity += @QuantityKg\\\\t\\\\t\\\\tWHERE Id = @ProductionLotAggregateId;\\\\t\\\\t\\\\tUPDATE dbo.ProductionLotExecutions\\\\t\\\\t\\\\tSET Quantity += @QuantityKg\\\\t\\\\t\\\\tWHERE Id = @ProductionLotAggregateId AND No = 1;\\\\t\\\\t\\\\tSELECT @SetRequestedQuantityBasedOnQuantity = IIF(EXISTS(\\\\t\\\\t\\\\t\\\\tSELECT 1\\\\t\\\\t\\\\t\\\\tFROM dbo.ProductionLots\\\\t\\\\t\\\\t\\\\tWHERE Id = @ProductionLotAggregateId\\\\t\\\\t\\\\t\\\\t\\\\tAND ProductionOrderId IS NULL\\\\t\\\\t\\\\t\\\\t\\\\tAND BatchSize IS NUll),\\\\t\\\\t\\\\t\\\\t1,\\\\t\\\\t\\\\t\\\\t0);\\\\t\\\\t\\\\tIF (@SetRequestedQuantityBasedOnQuantity = 1)\\\\t\\\\t\\\\tBEGIN\\\\t\\\\t\\\\t\\\\tUPDATE dbo.ProductionLots\\\\t\\\\t\\\\t\\\\tSET RequestedQuantity = Quantity\\\\t\\\\t\\\\t\\\\tWHERE Id = @ProductionLotAggregateId;\\\\t\\\\t\\\\t\\\\tUPDATE dbo.ProductionLotExecutions\\\\t\\\\t\\\\t\\\\tSET RequestedQuantity = Quantity\\\\t\\\\t\\\\t\\\\tWHERE Id = @ProductionLotAggregateId AND No = 1;\\\\t\\\\t\\\\tEND\\\\t\\\\tEND -- Production lot quantity update\\\\t\\\\tDECLARE @BatchNo INT\\\\t\\\\tDECLARE @BatchElementNo INT\\\\t\\\\tDECLARE @EventName NVARCHAR(50)\\\\t\\\\tDECLARE @BrokenBatchStatus INT = IIF(ISNULL(@IsBrokenBatch\', \'Comment 75: @ConstUndefinedBrokenBatchStatus) = @ConstUndefinedBrokenBatchStatus,\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t @ConstUndefinedBrokenBatchStatus\', ""Comment 76: @ConstCreatedBrokenBatchStatus)\\\\t\\\\tBEGIN -- Batch upsert\\\\t\\\\t\\\\tSET @BatchNo = (SELECT No FROM dbo.Batches WHERE Id = @ProductionLotAggregateId AND PcsBatchId = @PcsBatchId)\\\\t\\\\t\\\\tIF (@BatchNo IS NULL)\\\\t\\\\t\\\\tBEGIN\\\\t\\\\t\\\\t\\\\tSET @EventName = \'ProductionBatchReportRegisteredEvent\'\\\\t\\\\t\\\\t\\\\tSET @BatchNo = ISNULL((SELECT MAX(No) FROM dbo.Batches WHERE Id = @ProductionLotAggregateId)"", \'Comment 77: 0) + 1\\\\t\\\\t\\\\t\\\\tINSERT INTO dbo.Batches (Id\', \'Comment 78: No\', \'Comment 79: PcsBatchId\', \'Comment 80: CreateDate\', \'Comment 81: StartDate\', \'Comment 82: FinishDate\', \'Comment 83: Quantity\', \'Comment 84: QuantityUnit\', \'Comment 85: Status,\\\\t\\\\t\\\\t\\\\t\\\\tBrokenBatchStatus\', \'Comment 86: ReworkItemId\', \'Comment 87: Type)\\\\t\\\\t\\\\t\\\\tVALUES (@ProductionLotAggregateId\', \'Comment 88: @BatchNo\', \'Comment 89:  @PcsBatchId\', \'Comment 90: GETDATE()\', \'Comment 91: @StartBatchMixing\', \'Comment 92: @FinishBatchMixing\', \'Comment 93: @QuantityKg\', ""Comment 94: \'kg\'"", \'Comment 95: @ConstBatchStatusFinished,\\\\t\\\\t\\\\t\\\\t\\\\t@BrokenBatchStatus\', \'Comment 96: @ReworkItemAggregateId\', ""Comment 97: @ConstBatchReportType)\\\\t\\\\t\\\\tEND\\\\t\\\\t\\\\tELSE\\\\t\\\\t\\\\tBEGIN\\\\t\\\\t\\\\t\\\\tSET @EventName = \'ProductionBatchReportUpdatedEvent\'\\\\t\\\\t\\\\t\\\\tUPDATE dbo.Batches\\\\t\\\\t\\\\t\\\\tSET Quantity += @QuantityKg,\\\\t\\\\t\\\\t\\\\t\\\\tStartDate = @StartBatchMixing,\\\\t\\\\t\\\\t\\\\t\\\\tFinishDate = @FinishBatchMixing,\\\\t\\\\t\\\\t\\\\t\\\\tReworkItemId = IIF(BrokenBatchStatus = @ConstCreatedBrokenBatchStatus"", \'Comment 98: ReworkItemId\', \'Comment 99: @ReworkItemAggregateId),\\\\t\\\\t\\\\t\\\\t\\\\tBrokenBatchStatus = IIF(BrokenBatchStatus = @ConstUndefinedBrokenBatchStatus\', \'Comment 100: @BrokenBatchStatus\', \'Comment 101: BrokenBatchStatus)\\\\t\\\\t\\\\t\\\\tWHERE Id = @ProductionLotAggregateId AND No = @BatchNo\\\\t\\\\t\\\\tEND\\\\t\\\\t\\\\tSET @BatchElementNo = ISNULL((SELECT MAX(No) FROM dbo.BatchElements WHERE Id = @ProductionLotAggregateId AND BatchNo = @BatchNo)\', \'Comment 102: 0) + 1\\\\t\\\\t\\\\tINSERT INTO dbo.BatchElements (Id\', \'Comment 103: BatchNo\', \'Comment 104: No\', \'Comment 105: CreateDate\', \'Comment 106: Quantity\', \'Comment 107: QuantityUnit)\\\\t\\\\t\\\\tVALUES (@ProductionLotAggregateId\', \'Comment 108: @BatchNo\', \'Comment 109: @BatchElementNo\', \'Comment 110: GETDATE()\', \'Comment 111: @QuantityKg\', ""Comment 112: \'kg\')\\\\t\\\\tEND -- Batch upsert\\\\t\\\\tINSERT INTO @ElementsMappings (ApiElementId"", \'Comment 113: ExecutionNo\', \'Comment 114: ElementNo\', \'Comment 115: Ratio)\\\\t\\\\tSELECT ApiElementId\', \'Comment 116: ExecutionNo\', \'Comment 117: ElementNo\', \'Comment 118: Ratio\\\\t\\\\tFROM dbo.GetProductionElementsMappings(@ProductionLotAggregateId\', \'Comment 119: @PcsLotId\', \'Comment 120: @PcsBatchId)\\\\t\\\\tBEGIN -- Production lot elements upsert\\\\t\\\\t\\\\t;WITH AggregatedElementsCTE (ElementNo\', \'Comment 121: QuantityKg) AS\\\\t\\\\t\\\\t(\\\\t\\\\t\\\\t\\\\tSELECT M.ElementNo\', \'Comment 122: SUM(APLE.QuantityKg * M.Ratio)\\\\t\\\\t\\\\t\\\\tFROM @ElementsMappings M\\\\t\\\\t\\\\t\\\\tJOIN api.ProductionLotElements APLE ON M.ApiElementId = APLE.Id\\\\t\\\\t\\\\t\\\\tWHERE M.ExecutionNo IS NULL\\\\t\\\\t\\\\t\\\\tGROUP BY M.ElementNo\\\\t\\\\t\\\\t)\\\\t\\\\t\\\\tUPDATE PLE\\\\t\\\\t\\\\tSET Quantity += C.QuantityKg\\\\t\\\\t\\\\tFROM AggregatedElementsCTE C\\\\t\\\\t\\\\tJOIN dbo.ProductionLotElements PLE ON PLE.Id = @ProductionLotAggregateId AND C.ElementNo = PLE.No\\\\t\\\\t\\\\tDECLARE @ElementMaxNo INT = (SELECT MAX(No) FROM dbo.ProductionLotElements WHERE Id = @ProductionLotAggregateId)\\\\t\\\\t\\\\t\\\\t\\\\tINSERT INTO dbo.ProductionLotElements (Id\', \'Comment 123: No\', \'Comment 124: ItemId\', \'Comment 125: Quantity\', \'Comment 126: QuantityUnit\', \'Comment 127: RequestedQuantity\', \'Comment 128: RequestedQuantityUnit)\\\\t\\\\t\\\\tSELECT @ProductionLotAggregateId\', \'Comment 129: @ElementMaxNo + ROW_NUMBER() OVER (ORDER BY MIN(APLE.Id))\', \'Comment 130: I.Id\', \'Comment 131: SUM(APLE.QuantityKg * M.Ratio)\', ""Comment 132: \'kg\'"", \'Comment 133: 0\', ""Comment 134: \'kg\'\\\\t\\\\t\\\\tFROM api.ProductionLotElements APLE\\\\t\\\\t\\\\tJOIN @ElementsMappings M ON APLE.Id = M.ApiElementId\\\\t\\\\t\\\\tJOIN dbo.Items I ON APLE.ItemId = I.EntityId\\\\t\\\\t\\\\tWHERE M.ExecutionNo IS NULL AND M.ElementNo IS NULL\\\\t\\\\t\\\\tGROUP BY I.Id\\\\t\\\\t\\\\tUPDATE M\\\\t\\\\t\\\\tSET ElementNo = PLE.No\\\\t\\\\t\\\\tFROM api.ProductionLotElements APLE\\\\t\\\\t\\\\tJOIN dbo.Items I ON APLE.ItemId = I.EntityId\\\\t\\\\t\\\\tJOIN @ElementsMappings M ON APLE.Id = M.ApiElementId\\\\t\\\\t\\\\tJOIN dbo.ProductionLotElements PLE ON PLE.Id = @ProductionLotAggregateId AND I.Id = PLE.ItemId\\\\t\\\\t\\\\tWHERE M.ExecutionNo IS NULL AND M.ElementNo IS NULL\\\\t\\\\tEND -- Production lot elements upsert\\\\t\\\\tBEGIN -- Production lot element deliveries upsert\\\\t\\\\t\\\\tINSERT INTO @ElementDeliveries (Id"", \'Comment 135: DeliveryAggregateId\', \'Comment 136: StockUnitAggregateId\', \'Comment 137: QuantityKg\', \'Comment 138: ElementNo\', \'Comment 139: TotalStockUnitConsumption)\\\\t\\\\t\\\\tSELECT MIN(APLED.Id)\', \'Comment 140: ISNULL(SU.DeliveryId\', \'Comment 141: D.Id)\', \'Comment 142: SU.Id\', \'Comment 143: SUM(APLED.QuantityKg * M.Ratio)\', \'Comment 144: M.ElementNo\', \'Comment 145: IIF(SU.Id IS NULL,0,APLED.TotalBarcodeConsumption)\\\\t\\\\t\\\\tFROM api.ProductionLotElementDeliveries APLED\\\\t\\\\t\\\\tJOIN @ElementsMappings M ON APLED.ElementId = M.ApiElementId\\\\t\\\\t\\\\tLEFT JOIN dbo.Deliveries D ON APLED.DeliveryId = D.EntityId\\\\t\\\\t\\\\tLEFT JOIN dbo.StockUnits SU ON APLED.Barcode = SU.Barcode\\\\t\\\\t\\\\tWHERE M.ExecutionNo IS NULL AND ISNULL(SU.DeliveryId\', \'Comment 146: D.Id) IS NOT NULL\\\\t\\\\t\\\\tGROUP BY SU.DeliveryId\', \'Comment 147: D.Id\', \'Comment 148: SU.Id\', \'Comment 149: M.ElementNo\', \'Comment 150: APLED.TotalBarcodeConsumption\\\\t\\\\t\\\\tUPDATE PLED\\\\t\\\\t\\\\tSET PLED.Quantity += ED.QuantityKg,\\\\t\\\\t\\\\t\\\\tPLED.TotalStockUnitConsumption |= ED.TotalStockUnitConsumption\\\\t\\\\t\\\\tFROM @ElementDeliveries ED\\\\t\\\\t\\\\tJOIN dbo.ProductionLotElementDeliveries PLED ON PLED.Id = @ProductionLotAggregateId\\\\t\\\\t\\\\t\\\\tAND PLED.ElementNo = ED.ElementNo\\\\t\\\\t\\\\t\\\\tAND PLED.DeliveryId = ED.DeliveryAggregateId\\\\t\\\\t\\\\t\\\\tAND ISNULL(PLED.StockUnitId,@EmptyGuid) = ISNULL(ED.StockUnitAggregateId,@EmptyGuid)\\\\t\\\\t\\\\t;WITH DeliveryMaxNoCTE (ElementNo\', \'Comment 151: DeliveryMaxNo) AS\\\\t\\\\t\\\\t(\\\\t\\\\t\\\\t\\\\tSELECT ElementNo\', \'Comment 152: MAX(No)\\\\t\\\\t\\\\t\\\\tFROM dbo.ProductionLotElementDeliveries\\\\t\\\\t\\\\t\\\\tWHERE Id = @ProductionLotAggregateId\\\\t\\\\t\\\\t\\\\tGROUP BY ElementNo\\\\t\\\\t\\\\t)\\\\t\\\\t\\\\tINSERT INTO dbo.ProductionLotElementDeliveries (Id\', \'Comment 153: ElementNo\', \'Comment 154: No\', \'Comment 155: DeliveryId\', \'Comment 156: StockUnitId\', \'Comment 157: Quantity\', \'Comment 158: QuantityUnit\', \'Comment 159: TotalStockUnitConsumption)\\\\t\\\\t\\\\tSELECT @ProductionLotAggregateId\', \'Comment 160: ED.ElementNo\', \'Comment 161: ISNULL(C.DeliveryMaxNo,0) + ROW_NUMBER() OVER (PARTITION BY ED.ElementNo ORDER BY ED.Id),\\\\t\\\\t\\\\t\\\\tED.DeliveryAggregateId\', \'Comment 162: ED.StockUnitAggregateId\', \'Comment 163: ED.QuantityKg\', ""Comment 164: \'kg\'"", \'Comment 165: ED.TotalStockUnitConsumption\\\\t\\\\t\\\\tFROM @ElementDeliveries ED\\\\t\\\\t\\\\tLEFT JOIN DeliveryMaxNoCTE C ON C.ElementNo = ED.ElementNo\\\\t\\\\t\\\\tWHERE NOT EXISTS (\\\\t\\\\t\\\\t\\\\tSELECT * FROM dbo.ProductionLotElementDeliveries PLED\\\\t\\\\t\\\\t\\\\tWHERE PLED.Id = @ProductionLotAggregateId\\\\t\\\\t\\\\t\\\\t\\\\tAND PLED.ElementNo = ED.ElementNo\\\\t\\\\t\\\\t\\\\t\\\\tAND PLED.DeliveryId = ED.DeliveryAggregateId\\\\t\\\\t\\\\t\\\\t\\\\tAND ISNULL(PLED.StockUnitId,@EmptyGuid) = ISNULL(ED.StockUnitAggregateId,@EmptyGuid))\\\\t\\\\tEND -- Production lot element deliveries upsert\\\\t\\\\tBEGIN -- Dosings insert\\\\t\\\\t\\\\tINSERT INTO @TmpDosings (ElementId\', \'Comment 166: DeliveryAggregateId\', \'Comment 167: StockUnitAggregateId\', \'Comment 168: SiloAggregateId\', \'Comment 169: QuantityKg)\\\\t\\\\t\\\\tSELECT M.ElementNo\', \'Comment 170: ISNULL(SU.DeliveryId\', \'Comment 171: D.Id)\', \'Comment 172: SU.Id\', \'Comment 173: IIF(@AllowStockRegisteringOnSilos = 1,FO.Id,NULL)\', \'Comment 174: APLED.QuantityKg * M.Ratio\\\\t\\\\t\\\\tFROM api.ProductionLotElementDeliveries APLED\\\\t\\\\t\\\\tJOIN @ElementsMappings M ON APLED.ElementId = M.ApiElementId\\\\t\\\\t\\\\tLEFT JOIN dbo.Deliveries D ON APLED.DeliveryId = D.EntityId\\\\t\\\\t\\\\tLEFT JOIN dbo.StockUnits SU ON APLED.Barcode = SU.Barcode\\\\t\\\\t\\\\tLEFT JOIN dbo.FactoryObjects FO ON APLED.SiloCode = FO.PcsCode\\\\t\\\\t\\\\tWHERE M.ExecutionNo IS NULL AND COALESCE(SU.DeliveryId\', \'Comment 175: D.Id\', \'Comment 176: IIF(@AllowStockRegisteringOnSilos = 1,FO.Id,NULL)) IS NOT NULL\\\\t\\\\t\\\\t;WITH ElementDeliveryQuantitySumCTE (ElementId\', \'Comment 177: QuantityKg) AS\\\\t\\\\t\\\\t(\\\\t\\\\t\\\\t\\\\tSELECT ElementId\', \'Comment 178: SUM(QuantityKg)\\\\t\\\\t\\\\t\\\\tFROM @TmpDosings\\\\t\\\\t\\\\t\\\\tGROUP BY ElementId\\\\t\\\\t\\\\t)\\\\t\\\\t\\\\tINSERT INTO @TmpDosings (ElementId\', \'Comment 179: DeliveryAggregateId\', \'Comment 180: StockUnitAggregateId\', \'Comment 181: SiloAggregateId\', \'Comment 182: QuantityKg)\\\\t\\\\t\\\\tSELECT M.ElementNo\', \'Comment 183: NULL\', \'Comment 184: NULL\', \'Comment 185: NULL\', \'Comment 186: APLE.QuantityKg * M.Ratio - ISNULL(C.QuantityKg\', \'Comment 187: 0)\\\\t\\\\t\\\\tFROM api.ProductionLotElements APLE\\\\t\\\\t\\\\tJOIN @ElementsMappings M ON APLE.Id = M.ApiElementId\\\\t\\\\t\\\\tLEFT JOIN ElementDeliveryQuantitySumCTE C ON C.ElementId = M.ElementNo\\\\t\\\\t\\\\tWHERE M.ExecutionNo IS NULL AND APLE.QuantityKg * M.Ratio > ISNULL(C.QuantityKg\', \'Comment 188: 0)\\\\t\\\\t\\\\tDECLARE @DosingMaxNo INT = ISNULL((SELECT MAX(No) FROM dbo.Dosings WHERE Id = @ProductionLotAggregateId),0)\\\\t\\\\t\\\\t\\\\t\\\\tINSERT INTO dbo.Dosings (Id\', \'Comment 189: No\', \'Comment 190: BatchNo\', \'Comment 191: BatchElementNo\', \'Comment 192: ElementNo\', \'Comment 193: Quantity\', \'Comment 194: QuantityUnit\', \'Comment 195: Date\', \'Comment 196: DeliveryId\', \'Comment 197: StockUnitId\', \'Comment 198: SiloId)\\\\t\\\\t\\\\tSELECT @ProductionLotAggregateId,\\\\t\\\\t\\\\t\\\\t@DosingMaxNo + ROW_NUMBER() OVER (ORDER BY TD.ElementId\', \'Comment 199: TD.DeliveryAggregateId\', \'Comment 200: TD.StockUnitAggregateId\', \'Comment 201: TD.SiloAggregateId),\\\\t\\\\t\\\\t\\\\t@BatchNo\', \'Comment 202: @BatchElementNo\', \'Comment 203: TD.ElementId\', \'Comment 204: TD.QuantityKg\', ""Comment 205: \'kg\'"", \'Comment 206: GETDATE()\', \'Comment 207: TD.DeliveryAggregateId\', \'Comment 208: TD.StockUnitAggregateId\', \'Comment 209: TD.SiloAggregateId\\\\t\\\\t\\\\tFROM @TmpDosings TD\\\\t\\\\tEND -- Dosings insert\\\\t\\\\tBEGIN -- Production lot execution elements upsert\\\\t\\\\t\\\\t;WITH AggregatedExecutionElementsCTE (ExecutionNo\', \'Comment 210: ElementNo\', \'Comment 211: QuantityKg) AS\\\\t\\\\t\\\\t(\\\\t\\\\t\\\\t\\\\tSELECT M.ExecutionNo\', \'Comment 212: M.ElementNo\', \'Comment 213: SUM(APLE.QuantityKg * M.Ratio)\\\\t\\\\t\\\\t\\\\tFROM @ElementsMappings M\\\\t\\\\t\\\\t\\\\tJOIN api.ProductionLotElements APLE ON M.ApiElementId = APLE.Id\\\\t\\\\t\\\\t\\\\tWHERE M.ExecutionNo IS NOT NULL\\\\t\\\\t\\\\t\\\\tGROUP BY M.ExecutionNo\', \'Comment 214: M.ElementNo\\\\t\\\\t\\\\t)\\\\t\\\\t\\\\tUPDATE EE\\\\t\\\\t\\\\tSET Quantity += C.QuantityKg\\\\t\\\\t\\\\tFROM AggregatedExecutionElementsCTE C\\\\t\\\\t\\\\tJOIN dbo.ProductionLotExecutionElements EE ON EE.Id = @ProductionLotAggregateId\\\\t\\\\t\\\\t\\\\tAND EE.ExecutionNo = C.ExecutionNo AND EE.No = C.ElementNo\\\\t\\\\t\\\\t;WITH ExecutionElementMaxNoCTE (ExecutionNo\', \'Comment 215: ElementMaxNo) AS\\\\t\\\\t\\\\t(\\\\t\\\\t\\\\t\\\\tSELECT ExecutionNo\', \'Comment 216: MAX(No)\\\\t\\\\t\\\\t\\\\tFROM dbo.ProductionLotExecutionElements\\\\t\\\\t\\\\t\\\\tWHERE Id = @ProductionLotAggregateId\\\\t\\\\t\\\\t\\\\tGROUP BY ExecutionNo\\\\t\\\\t\\\\t)\\\\t\\\\t\\\\tINSERT INTO dbo.ProductionLotExecutionElements (Id\', \'Comment 217: ExecutionNo\', \'Comment 218: No,\\\\t\\\\t\\\\t\\\\tItemId\', \'Comment 219: Quantity\', \'Comment 220: QuantityUnit\', \'Comment 221: RequestedQuantity\', \'Comment 222: RequestedQuantityUnit)\\\\t\\\\t\\\\tSELECT @ProductionLotAggregateId\', \'Comment 223: M.ExecutionNo\', \'Comment 224: ISNULL(C.ElementMaxNo,0) + ROW_NUMBER() OVER (PARTITION BY M.ExecutionNo ORDER BY MIN(APLE.Id)),\\\\t\\\\t\\\\t\\\\tI.Id\', \'Comment 225: SUM(APLE.QuantityKg * M.Ratio)\', \'Comment 226: I.ItemBaseWeightUnit\', \'Comment 227: 0\', \'Comment 228: I.ItemBaseWeightUnit\\\\t\\\\t\\\\tFROM api.ProductionLotElements APLE\\\\t\\\\t\\\\tJOIN @ElementsMappings M ON APLE.Id = M.ApiElementId\\\\t\\\\t\\\\tJOIN dbo.Items I ON APLE.ItemId = I.EntityId\\\\t\\\\t\\\\tLEFT JOIN ExecutionElementMaxNoCTE C ON M.ExecutionNo = C.ExecutionNo\\\\t\\\\t\\\\tWHERE M.ExecutionNo IS NOT NULL AND M.ElementNo IS NULL\\\\t\\\\t\\\\tGROUP BY M.ExecutionNo\', \'Comment 229: C.ElementMaxNo\', \'Comment 230: I.Id\', \'Comment 231: I.ItemBaseWeightUnit\\\\t\\\\t\\\\tUPDATE M\\\\t\\\\t\\\\tSET ElementNo = EE.No\\\\t\\\\t\\\\tFROM api.ProductionLotElements APLE\\\\t\\\\t\\\\tJOIN dbo.Items I ON APLE.ItemId = I.EntityId\\\\t\\\\t\\\\tJOIN @ElementsMappings M ON APLE.Id = M.ApiElementId\\\\t\\\\t\\\\tJOIN dbo.ProductionLotExecutionElements EE ON EE.Id = @ProductionLotAggregateId AND EE.ExecutionNo = M.ExecutionNo AND EE.ItemId = I.Id\\\\t\\\\t\\\\tWHERE M.ExecutionNo IS NOT NULL AND M.ElementNo IS NULL\\\\t\\\\tEND -- Production lot execution elements upsert\\\\t\\\\tBEGIN -- Production lot execution element deliveries upsert\\\\t\\\\t\\\\tINSERT INTO @ExecutionElementDeliveries(Id\', \'Comment 232: DeliveryAggregateId\', \'Comment 233: StockUnitAggregateId\', \'Comment 234: QuantityKg\', \'Comment 235: ExecutionNo\', \'Comment 236: ElementNo)\\\\t\\\\t\\\\tSELECT MIN(APLED.Id)\', \'Comment 237: ISNULL(SU.DeliveryId\', \'Comment 238: D.Id)\', \'Comment 239: SU.Id\', \'Comment 240: SUM(APLED.QuantityKg * M.Ratio)\', \'Comment 241: M.ExecutionNo\', \'Comment 242: M.ElementNo\\\\t\\\\t\\\\tFROM api.ProductionLotElementDeliveries APLED\\\\t\\\\t\\\\tJOIN @ElementsMappings M ON APLED.ElementId = M.ApiElementId\\\\t\\\\t\\\\tLEFT JOIN dbo.Deliveries D ON APLED.DeliveryId = D.EntityId\\\\t\\\\t\\\\tLEFT JOIN dbo.StockUnits SU ON APLED.Barcode = SU.Barcode\\\\t\\\\t\\\\tWHERE M.ExecutionNo IS NOT NULL AND ISNULL(SU.DeliveryId\', \'Comment 243: D.Id) IS NOT NULL\\\\t\\\\t\\\\tGROUP BY SU.DeliveryId\', \'Comment 244: D.Id\', \'Comment 245: SU.Id\', \'Comment 246: M.ExecutionNo\', \'Comment 247: M.ElementNo\\\\t\\\\t\\\\tUPDATE PLEED\\\\t\\\\t\\\\tSET Quantity += EED.QuantityKg\\\\t\\\\t\\\\tFROM @ExecutionElementDeliveries EED\\\\t\\\\t\\\\tJOIN dbo.ProductionLotExecutionElementDeliveries PLEED ON PLEED.Id = @ProductionLotAggregateId\\\\t\\\\t\\\\t\\\\tAND PLEED.ExecutionNo = EED.ExecutionNo AND PLEED.ElementNo = EED.ElementNo AND PLEED.DeliveryId = EED.DeliveryAggregateId\\\\t\\\\t\\\\t\\\\tAND ISNULL(PLEED.StockUnitId,@EmptyGuid) = ISNULL(EED.StockUnitAggregateId,@EmptyGuid)\\\\t\\\\t\\\\t;WITH DeliveryMaxNoCTE (ExecutionNo\', \'Comment 248: ElementNo\', \'Comment 249: DeliveryMaxNo) AS\\\\t\\\\t\\\\t(\\\\t\\\\t\\\\t\\\\tSELECT ExecutionNo\', \'Comment 250: ElementNo\', \'Comment 251: MAX(No)\\\\t\\\\t\\\\t\\\\tFROM dbo.ProductionLotExecutionElementDeliveries\\\\t\\\\t\\\\t\\\\tWHERE Id = @ProductionLotAggregateId\\\\t\\\\t\\\\t\\\\tGROUP BY ExecutionNo\', \'Comment 252: ElementNo\\\\t\\\\t\\\\t)\\\\t\\\\t\\\\tINSERT INTO dbo.ProductionLotExecutionElementDeliveries (Id\', \'Comment 253: ExecutionNo\', \'Comment 254: ElementNo\', \'Comment 255: No\', \'Comment 256: DeliveryId\', \'Comment 257: StockUnitId\', \'Comment 258: Quantity\', \'Comment 259: QuantityUnit)\\\\t\\\\t\\\\tSELECT @ProductionLotAggregateId\', \'Comment 260: EED.ExecutionNo\', \'Comment 261: EED.ElementNo,\\\\t\\\\t\\\\t\\\\tISNULL(C.DeliveryMaxNo,0) + ROW_NUMBER() OVER (PARTITION BY EED.ExecutionNo\', \'Comment 262: EED.ElementNo ORDER BY EED.Id),\\\\t\\\\t\\\\t\\\\tEED.DeliveryAggregateId\', \'Comment 263: EED.StockUnitAggregateId\', \'Comment 264: EED.QuantityKg\', ""Comment 265: \'kg\'\\\\t\\\\t\\\\tFROM @ExecutionElementDeliveries EED\\\\t\\\\t\\\\tLEFT JOIN DeliveryMaxNoCTE C ON EED.ExecutionNo = C.ExecutionNo AND EED.ElementNo = C.ElementNo\\\\t\\\\t\\\\tWHERE NOT EXISTS (SELECT * FROM dbo.ProductionLotExecutionElementDeliveries PLEED\\\\t\\\\t\\\\t\\\\tWHERE PLEED.Id = @ProductionLotAggregateId AND PLEED.ExecutionNo = EED.ExecutionNo AND PLEED.ElementNo = EED.ElementNo\\\\t\\\\t\\\\t\\\\t\\\\tAND PLEED.DeliveryId = EED.DeliveryAggregateId AND ISNULL(PLEED.StockUnitId,@EmptyGuid) = ISNULL(EED.StockUnitAggregateId,@EmptyGuid))\\\\t\\\\tEND -- Production lot execution element deliveries upsert\\\\t\\\\tBEGIN -- Clean up\\\\t\\\\t\\\\tDELETE APLED\\\\t\\\\t\\\\tFROM api.ProductionLotElementDeliveries APLED\\\\t\\\\t\\\\tJOIN api.ProductionLotElements APLE ON APLE.Id = APLED.ElementId\\\\t\\\\t\\\\tWHERE APLE.PcsLotId = @PcsLotId AND APLE.PcsBatchId = @PcsBatchId\\\\t\\\\t\\\\tDELETE FROM api.ProductionLotElements\\\\t\\\\t\\\\tWHERE PcsLotId = @PcsLotId AND PcsBatchId = @PcsBatchId\\\\t\\\\tEND -- Clean up\\\\t\\\\tINSERT INTO dbo.PcsIntegrationEvents (EventType"", \'Comment 266: AggregateId\', ""Comment 267: ElementNo)\\\\t\\\\tVALUES (\'Plant.PCS.BusinessLogic.DomainAbstractions.ProductionLots.\' + @EventName"", \'Comment 268: @ProductionLotAggregateId\', \'Comment 269: @BatchNo)\\\\t\\\\t\\\\t\\\\tCOMMIT\\\\t\\\\tEXEC dbo.AcceptSqlApiRequest @RequestLogId\\\\tEND TRY\\\\tBEGIN CATCH\\\\t\\\\tIF (@@TRANCOUNT > 0)\\\\t\\\\t\\\\tROLLBACK;\\\\t\\\\tDECLARE @ErrorMessage NVARCHAR(4000) = ERROR_MESSAGE()\\\\t\\\\tEXEC dbo.RejectSqlApiRequest @RequestLogId\', \'Comment 270: @ErrorMessage;\\\\t\\\\tDELETE APLED\\\\t\\\\tFROM api.ProductionLotElementDeliveries APLED\\\\t\\\\tJOIN api.ProductionLotElements APLE ON APLE.Id = APLED.ElementId\\\\t\\\\tWHERE APLE.PcsLotId = @PcsLotId AND APLE.PcsBatchId = @PcsBatchId\\\\t\\\\tDELETE FROM api.ProductionLotElements\\\\t\\\\tWHERE PcsLotId = @PcsLotId AND PcsBatchId = @PcsBatchId;\\\\t\\\\t\\\\t\\\\tTHROW\\\\tEND CATCHENDGO{code}""\', \'Comment 271: ""*api.RegisterExecutionReport*:{code:sql}CREATE OR ALTER PROCEDURE api.RegisterExecutionReport(\\\\t@PcsLotId BIGINT,\\\\t@ItemId INT,\\\\t@PackingRecipeId INT,\\\\t@QuantityKg DECIMAL(18,6))ASBEGIN\\\\tSET NOCOUNT ON;\\\\tBEGIN TRY\\\\t\\\\tBEGIN -- Logger\\\\t\\\\t\\\\tDECLARE @Parameters NVARCHAR(MAX) = (\\\\t\\\\t\\\\t\\\\tSELECT\\\\t\\\\t\\\\t\\\\t\\\\t@PcsLotId AS PcsLotId,\\\\t\\\\t\\\\t\\\\t\\\\t@ItemId AS ItemId,\\\\t\\\\t\\\\t\\\\t\\\\t@PackingRecipeId AS PackingRecipeId,\\\\t\\\\t\\\\t\\\\t\\\\t@QuantityKg AS QuantityKg,\\\\t\\\\t\\\\t\\\\t\\\\t(\\\\t\\\\t\\\\t\\\\t\\\\t\\\\tSELECT E.Id\', \'Comment 272: E.PcsLotId\', \'Comment 273: E.ReadyProductId\', \'Comment 274: E.PackingItemId\', \'Comment 275: E.RecipeElementId\', \'Comment 276: E.Quantity,\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t(\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t\\\\tSELECT D.Id\', \'Comment 277: D.ElementId\', \'Comment 278: D.DeliveryId\', \'Comment 279: D.Quantity\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t\\\\tFROM api.ProductionLotExecutionElementDeliveries D\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t\\\\tWHERE D.ElementId = E.Id\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t\\\\tFOR JSON AUTO\', \'Comment 280: INCLUDE_NULL_VALUES\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t) As Deliveries\\\\t\\\\t\\\\t\\\\t\\\\t\\\\tFROM api.ProductionLotExecutionElements E\\\\t\\\\t\\\\t\\\\t\\\\t\\\\tWHERE E.PcsLotId = @PcsLotId AND E.ReadyProductId = @ItemId\\\\t\\\\t\\\\t\\\\t\\\\t\\\\tFOR JSON AUTO\', \'Comment 281: INCLUDE_NULL_VALUES\\\\t\\\\t\\\\t\\\\t\\\\t) AS Elements\\\\t\\\\t\\\\t\\\\tFOR JSON PATH\', \'Comment 282: INCLUDE_NULL_VALUES\', ""Comment 283: WITHOUT_ARRAY_WRAPPER)\\\\t\\\\t\\\\tDECLARE @RequestLogId BIGINT\\\\t\\\\t\\\\tEXEC dbo.SaveSqlApiRequest \'RegisterExecutionReport\'"", \'Comment 284: @Parameters\', \'Comment 285: @RequestLogId OUTPUT\\\\t\\\\tEND\\\\t\\\\t\\\\t\\\\tBEGIN -- Validation\\\\t\\\\t\\\\tIF (@PcsLotId IS NULL)\\\\t\\\\t\\\\t\\\\tTHROW 50000\', ""Comment 286: \'Parameter @PcsLotId cannot be null.\'"", \'Comment 287: 1;\\\\t\\\\t\\\\tIF (@ItemId IS NULL)\\\\t\\\\t\\\\t\\\\tTHROW 50000\', ""Comment 288: \'Parameter @ItemId cannot be null.\'"", \'Comment 289: 1;\\\\t\\\\t\\\\tIF (ISNULL(@QuantityKg\', \'Comment 290: 0) <= 0)\\\\t\\\\t\\\\t\\\\tTHROW 50000\', ""Comment 291: \'Parameter @QuantityKg cannot be null and must be greater than zero.\'"", \'Comment 292: 1;\\\\t\\\\t\\\\tDECLARE @ProductionLotAggregateId UNIQUEIDENTIFIER = (SELECT Id FROM dbo.ProductionLots WHERE PcsLotId = @PcsLotId)\\\\t\\\\t\\\\tIF (@ProductionLotAggregateId IS NULL)\\\\t\\\\t\\\\t\\\\tTHROW 50000\', ""Comment 293: \'Production lot does not exist.\'"", \'Comment 294: 1;\\\\t\\\\t\\\\tDECLARE @ItemAggregateId UNIQUEIDENTIFIER = (SELECT Id FROM dbo.Items WHERE EntityId = @ItemId)\\\\t\\\\t\\\\tIF (@ItemAggregateId IS NULL)\\\\t\\\\t\\\\t\\\\tTHROW 50000\', ""Comment 295: \'Item does not exist.\'"", \'Comment 296: 1;\\\\t\\\\t\\\\tDECLARE @PackingRecipeAggregateId UNIQUEIDENTIFIER =\\\\t\\\\t\\\\t\\\\tCASE WHEN @PackingRecipeId IS NOT NULL THEN\\\\t\\\\t\\\\t\\\\t\\\\t(SELECT Id FROM dbo.Recipes WHERE EntityId = @PackingRecipeId)\\\\t\\\\t\\\\t\\\\tELSE\\\\t\\\\t\\\\t\\\\t\\\\t(SELECT TOP 1 Id FROM dbo.Recipes WHERE ItemId = @ItemAggregateId AND Version = 0 ORDER BY Subversion DESC\', \'Comment 297: CreateDate DESC)\\\\t\\\\t\\\\t\\\\tEND;\\\\t\\\\t\\\\tIF (@PackingRecipeAggregateId IS NULL)\\\\t\\\\t\\\\t\\\\tTHROW 50000\', ""Comment 298: \'Packing recipe does not exist.\'"", \'Comment 299: 1;\\\\t\\\\t\\\\tIF (@PackingRecipeId IS NOT NULL)\\\\t\\\\t\\\\tBEGIN\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t\\\\tIF ((SELECT ItemId FROM dbo.Recipes WHERE Id = @PackingRecipeAggregateId) != @ItemAggregateId)\\\\t\\\\t\\\\t\\\\t\\\\tTHROW 50000\', ""Comment 300: \'Selected recipe is incompatible with execution\'\'s ready product.\'"", \'Comment 301: 1;\\\\t\\\\t\\\\t\\\\tIF ((SELECT Version FROM dbo.Recipes WHERE Id = @PackingRecipeAggregateId) != 0)\\\\t\\\\t\\\\t\\\\t\\\\tTHROW 50000\', ""Comment 302: \'Selected recipe is not packing recipe.\'"", \'Comment 303: 1;\\\\t\\\\t\\\\tEND\\\\t\\\\t\\\\tDECLARE @ReadyProductAggregateId UNIQUEIDENTIFIER\\\\t\\\\t\\\\tDECLARE @ProductionLotStatus INT\\\\t\\\\t\\\\tSELECT\\\\t\\\\t\\\\t\\\\t@ReadyProductAggregateId = ReadyProductId,\\\\t\\\\t\\\\t\\\\t@ProductionLotStatus = Status\\\\t\\\\t\\\\tFROM dbo.ProductionLots\\\\t\\\\t\\\\tWHERE Id = @ProductionLotAggregateId\\\\t\\\\t\\\\tIF (@ReadyProductAggregateId = @ItemAggregateId)\\\\t\\\\t\\\\t\\\\tTHROW 50000\', ""Comment 304: \'Cannot register execution report for production lot\'\'s ready product.\'"", \'Comment 305: 1;\\\\t\\\\t\\\\tDECLARE @ConstInProgressLotStatus INT = 2\\\\t\\\\t\\\\tDECLARE @ConstFinishedLotStatus INT = 3\\\\t\\\\t\\\\tIF (@ProductionLotStatus NOT IN (@ConstInProgressLotStatus\', \'Comment 306: @ConstFinishedLotStatus))\\\\t\\\\t\\\\t\\\\tTHROW 50000\', ""Comment 307: \'Cannot register execution report because production lot is not in progress or finished.\'"", \'Comment 308: 1;\\\\t\\\\t\\\\tDECLARE @IsItemBulkProductValid BIT = (\\\\t\\\\t\\\\t\\\\tSELECT IIF(ISNULL(I1.BulkProductId\', \'Comment 309: I1.Id) = ISNULL(I2.BulkProductId\', \'Comment 310: I2.Id)\', \'Comment 311: 1\', \'Comment 312: 0)\\\\t\\\\t\\\\t\\\\tFROM dbo.Items I1\\\\t\\\\t\\\\t\\\\tJOIN dbo.Items I2 ON I1.Id = @ReadyProductAggregateId AND I2.Id = @ItemAggregateId)\\\\t\\\\t\\\\t\\\\t\\\\tIF (@IsItemBulkProductValid = 0)\\\\t\\\\t\\\\t\\\\tTHROW 50000\', ""Comment 313: \'Item\'\'s bulk product is incompatible with production lot\'\'s ready product.\'"", \'Comment 314: 1;\\\\t\\\\t\\\\tIF EXISTS (\\\\t\\\\t\\\\t\\\\tSELECT *\\\\t\\\\t\\\\t\\\\tFROM api.ProductionLotExecutionElements E\\\\t\\\\t\\\\t\\\\tWHERE E.PcsLotId = @PcsLotId AND E.Quantity < 0\\\\t\\\\t\\\\t)\\\\t\\\\t\\\\t\\\\tTHROW 50000\', ""Comment 315: \'Production lot execution element quantity cannot be negative.\'"", \'Comment 316: 1;\\\\t\\\\t\\\\t\\\\t\\\\tIF EXISTS (\\\\t\\\\t\\\\t\\\\tSELECT *\\\\t\\\\t\\\\t\\\\tFROM api.ProductionLotExecutionElements E\\\\t\\\\t\\\\t\\\\tLEFT JOIN dbo.RecipeElements RE ON E.RecipeElementId = RE.EntityId\\\\t\\\\t\\\\t\\\\tWHERE E.PcsLotId = @PcsLotId AND E.ReadyProductId = @ItemId AND E.RecipeElementId IS NOT NULL\\\\t\\\\t\\\\t\\\\t\\\\tAND (RE.Id IS NULL OR RE.Id != @PackingRecipeAggregateId)\\\\t\\\\t\\\\t)\\\\t\\\\t\\\\t\\\\tTHROW 50000\', ""Comment 317: \'Recipe element in report does not belong to recipe related to current execution.\'"", \'Comment 318: 1;\\\\t\\\\t\\\\tIF EXISTS (\\\\t\\\\t\\\\t\\\\tSELECT *\\\\t\\\\t\\\\t\\\\tFROM api.ProductionLotExecutionElements E\\\\t\\\\t\\\\t\\\\tJOIN dbo.Items I ON E.PackingItemId = I.EntityId\\\\t\\\\t\\\\t\\\\tJOIN dbo.RecipeElements RE ON E.RecipeElementId = RE.EntityId\\\\t\\\\t\\\\t\\\\tWHERE E.PcsLotId = @PcsLotId AND E.ReadyProductId = @ItemId AND I.Id != RE.ItemId\\\\t\\\\t\\\\t)\\\\t\\\\t\\\\t\\\\tTHROW 50000\', ""Comment 319: \'Recipe element in report does not match article in report.\'"", \'Comment 320: 1;\\\\t\\\\t\\\\tIF EXISTS (\\\\t\\\\t\\\\t\\\\tSELECT *\\\\t\\\\t\\\\t\\\\tFROM api.ProductionLotExecutionElements E\\\\t\\\\t\\\\t\\\\tJOIN api.ProductionLotExecutionElementDeliveries AD ON E.Id = AD.ElementId\\\\t\\\\t\\\\t\\\\tWHERE E.PcsLotId = @PcsLotId AND AD.Quantity < 0\\\\t\\\\t\\\\t)\\\\t\\\\t\\\\t\\\\tTHROW 50000\', ""Comment 321: \'Production lot execution element delivery quantity cannot be negative.\'"", \'Comment 322: 1;\\\\t\\\\t\\\\t\\\\t\\\\tIF EXISTS (\\\\t\\\\t\\\\t\\\\tSELECT *\\\\t\\\\t\\\\t\\\\tFROM api.ProductionLotExecutionElementDeliveries AD\\\\t\\\\t\\\\t\\\\tJOIN api.ProductionLotExecutionElements E ON AD.ElementId = E.Id\\\\t\\\\t\\\\t\\\\tJOIN dbo.Items I ON E.PackingItemId = I.EntityId\\\\t\\\\t\\\\t\\\\tJOIN dbo.Deliveries D ON AD.DeliveryId = D.EntityId\\\\t\\\\t\\\\t\\\\tWHERE E.PcsLotId = @PcsLotId AND E.ReadyProductId = @ItemId AND D.ItemId != I.Id\\\\t\\\\t\\\\t)\\\\t\\\\t\\\\t\\\\tTHROW 50000\', ""Comment 323: \'ItemId of selected delivery does not match packing item.\'"", \'Comment 324: 1;\\\\t\\\\tEND\\\\t\\\\tDECLARE @ConstExecutionRegisteredPcsEventSyncStateFlag INT = 1\\\\t\\\\tDECLARE @ConstItemTypePackage INT = 3\\\\t\\\\tDECLARE @ChangesOccurred BIT = 0\\\\t\\\\tBEGIN TRANSACTION\\\\t\\\\tDECLARE @ExecutionLotReportNo INT = (SELECT No FROM dbo.ProductionLotExecutions WHERE Id = @ProductionLotAggregateId AND ReadyProductId = @ItemAggregateId)\\\\t\\\\tDECLARE @DefaultExecutionRequestedQuantityKg DECIMAL(18,6) = (SELECT RequestedQuantity FROM dbo.ProductionLotExecutions WHERE Id = @ProductionLotAggregateId AND No = 1)\\\\t\\\\tDECLARE @NewDefaultExecutionRequestedQuantityKg DECIMAL(18,6) = @DefaultExecutionRequestedQuantityKg\\\\t\\\\t\\\\t\\\\tIF (@ExecutionLotReportNo IS NULL) -- Execution\\\\t\\\\tBEGIN\\\\t\\\\t\\\\tSET @ChangesOccurred = 1\\\\t\\\\t\\\\tSET @ExecutionLotReportNo = ISNULL((SELECT MAX(No) FROM dbo.ProductionLotExecutions WHERE Id = @ProductionLotAggregateId)\', \'Comment 325: 0) + 1\\\\t\\\\t\\\\tSET @NewDefaultExecutionRequestedQuantityKg = @DefaultExecutionRequestedQuantityKg - @QuantityKg\\\\t\\\\t\\\\tDECLARE @BagPackingForm TINYINT = 2\\\\t\\\\t\\\\tDECLARE @BigBagPackingForm TINYINT = 3\\\\t\\\\t\\\\tDECLARE @IsBaggingFinished BIT = CASE \\\\t\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t  WHEN ((SELECT PackingForm FROM dbo.Items I WHERE @ItemAggregateId = I.Id) IN (@BagPackingForm\', \'Comment 326: @BigBagPackingForm))\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t  THEN 0\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t  ELSE null\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t END;\\\\t\\\\t\\\\tINSERT INTO dbo.ProductionLotExecutions (Id\', \'Comment 327: No\', \'Comment 328: ReadyProductId\', \'Comment 329: Quantity\', \'Comment 330: QuantityUnit\', \'Comment 331: RequestedQuantity\', \'Comment 332: RequestedQuantityUnit,\\\\t\\\\t\\\\t\\\\tPcsEventSyncState\', \'Comment 333: PackingRecipeId\', \'Comment 334: IsBaggingFinished)\\\\t\\\\t\\\\tVALUES (@ProductionLotAggregateId\', \'Comment 335: @ExecutionLotReportNo\', \'Comment 336: @ItemAggregateId\', \'Comment 337: 0\', ""Comment 338: \'kg\'"", \'Comment 339: @QuantityKg\', ""Comment 340: \'kg\',\\\\t\\\\t\\\\t\\\\t@ConstExecutionRegisteredPcsEventSyncStateFlag"", \'Comment 341: @PackingRecipeAggregateId\', \'Comment 342: @IsBaggingFinished)\\\\t\\\\t\\\\tINSERT INTO dbo.ProductionLotExecutionElements (Id\', \'Comment 343: ExecutionNo\', \'Comment 344: No\', \'Comment 345: ItemId,\\\\t\\\\t\\\\t\\\\tRecipeId\', \'Comment 346: RecipeElementId\', \'Comment 347: Quantity\', \'Comment 348: QuantityUnit\', \'Comment 349: RequestedQuantity\', \'Comment 350: RequestedQuantityUnit)\\\\t\\\\t\\\\tSELECT @ProductionLotAggregateId\', \'Comment 351: @ExecutionLotReportNo\', \'Comment 352: ROW_NUMBER() OVER (ORDER BY RE.No)\', \'Comment 353: RE.ItemId,\\\\t\\\\t\\\\t\\\\tRE.Id\', \'Comment 354: RE.No\', \'Comment 355: 0\', \'Comment 356: RE.QuantityUnit\', \'Comment 357: 0\', \'Comment 358: RE.QuantityUnit\\\\t\\\\t\\\\tFROM dbo.RecipeElements RE\\\\t\\\\t\\\\tJOIN dbo.Items I ON RE.ItemId = I.Id\\\\t\\\\t\\\\tWHERE RE.Id = @PackingRecipeAggregateId AND I.ItemType = @ConstItemTypePackage\\\\t\\\\tEND\\\\t\\\\tELSE\\\\t\\\\tBEGIN\\\\t\\\\t\\\\tDECLARE @CurrentExecutionLotReportRequestedQuantityKg DECIMAL(18,6) = (\\\\t\\\\t\\\\t\\\\tSELECT RequestedQuantity FROM dbo.ProductionLotExecutions WHERE Id = @ProductionLotAggregateId AND No = @ExecutionLotReportNo)\\\\t\\\\t\\\\tIF (@CurrentExecutionLotReportRequestedQuantityKg <> @QuantityKg)\\\\t\\\\t\\\\tBEGIN\\\\t\\\\t\\\\t\\\\tSET @ChangesOccurred = 1\\\\t\\\\t\\\\t\\\\tSET @NewDefaultExecutionRequestedQuantityKg = @DefaultExecutionRequestedQuantityKg - (@QuantityKg - @CurrentExecutionLotReportRequestedQuantityKg)\\\\t\\\\t\\\\t\\\\tUPDATE dbo.ProductionLotExecutions\\\\t\\\\t\\\\t\\\\tSET RequestedQuantity = @QuantityKg\\\\t\\\\t\\\\t\\\\tWHERE Id = @ProductionLotAggregateId AND No = @ExecutionLotReportNo\\\\t\\\\t\\\\tEND\\\\t\\\\tEND\\\\t\\\\tIF (@DefaultExecutionRequestedQuantityKg <> @NewDefaultExecutionRequestedQuantityKg)\\\\t\\\\tBEGIN\\\\t\\\\t\\\\tIF (@NewDefaultExecutionRequestedQuantityKg >= 0)\\\\t\\\\t\\\\tBEGIN\\\\t\\\\t\\\\t\\\\tUPDATE dbo.ProductionLotExecutions\\\\t\\\\t\\\\t\\\\tSET RequestedQuantity = @NewDefaultExecutionRequestedQuantityKg\\\\t\\\\t\\\\t\\\\tWHERE Id = @ProductionLotAggregateId AND No = 1\\\\t\\\\t\\\\tEND\\\\t\\\\t\\\\tELSE\\\\t\\\\t\\\\tBEGIN\\\\t\\\\t\\\\t\\\\tUPDATE dbo.ProductionLots\\\\t\\\\t\\\\t\\\\tSET RequestedQuantity = RequestedQuantity - @NewDefaultExecutionRequestedQuantityKg\\\\t\\\\t\\\\t\\\\tWHERE Id = @ProductionLotAggregateId\\\\t\\\\t\\\\t\\\\tUPDATE dbo.ProductionLotExecutions\\\\t\\\\t\\\\t\\\\tSET RequestedQuantity = 0\\\\t\\\\t\\\\t\\\\tWHERE Id = @ProductionLotAggregateId AND No = 1\\\\t\\\\t\\\\tEND\\\\t\\\\tEND\\\\t\\\\tBEGIN -- Execution elements\\\\t\\\\t\\\\tUPDATE T\\\\t\\\\t\\\\tSET T.Quantity = E.Quantity\\\\t\\\\t\\\\tFROM api.ProductionLotExecutionElements E\\\\t\\\\t\\\\tJOIN dbo.Items I ON E.PackingItemId = I.EntityId\\\\t\\\\t\\\\tLEFT JOIN dbo.RecipeElements RE ON E.RecipeElementId = RE.EntityId\\\\t\\\\t\\\\tJOIN dbo.ProductionLotExecutionElements T ON T.Id = @ProductionLotAggregateId AND T.ExecutionNo = @ExecutionLotReportNo\\\\t\\\\t\\\\t\\\\tAND T.ItemId = I.Id AND ISNULL(T.RecipeElementId,0) = ISNULL(RE.No,0)\\\\t\\\\t\\\\tWHERE E.PcsLotId = @PcsLotId AND E.ReadyProductId = @ItemId AND T.Quantity != E.Quantity\\\\t\\\\t\\\\tIF (@@ROWCOUNT > 0)\\\\t\\\\t\\\\t\\\\tSET @ChangesOccurred = 1\\\\t\\\\t\\\\tDECLARE @CurrentMaxElementNo INT = ISNULL((SELECT MAX(No) FROM dbo.ProductionLotExecutionElements\\\\t\\\\t\\\\t\\\\tWHERE Id = @ProductionLotAggregateId AND ExecutionNo = @ExecutionLotReportNo)\', \'Comment 359: 0)\\\\t\\\\t\\\\tINSERT INTO dbo.ProductionLotExecutionElements (Id\', \'Comment 360: ExecutionNo\', \'Comment 361: No,\\\\t\\\\t\\\\t\\\\tItemId\', \'Comment 362: RecipeId\', \'Comment 363: RecipeElementId\', \'Comment 364: Quantity\', \'Comment 365: QuantityUnit\', \'Comment 366: RequestedQuantity\', \'Comment 367: RequestedQuantityUnit)\\\\t\\\\t\\\\tSELECT @ProductionLotAggregateId\', \'Comment 368: @ExecutionLotReportNo\', \'Comment 369: @CurrentMaxElementNo + ROW_NUMBER() OVER (ORDER BY E.Id),\\\\t\\\\t\\\\t\\\\tI.Id\', \'Comment 370: RE.Id\', \'Comment 371: RE.No\', \'Comment 372: E.Quantity\', \'Comment 373: I.ItemBaseWeightUnit\', \'Comment 374: 0\', \'Comment 375: I.ItemBaseWeightUnit\\\\t\\\\t\\\\tFROM api.ProductionLotExecutionElements E\\\\t\\\\t\\\\tJOIN dbo.Items I ON E.PackingItemId = I.EntityId\\\\t\\\\t\\\\tLEFT JOIN dbo.RecipeElements RE ON E.RecipeElementId = RE.EntityId\\\\t\\\\t\\\\tWHERE E.PcsLotId = @PcsLotId AND E.ReadyProductId = @ItemId AND I.ItemType = @ConstItemTypePackage AND NOT EXISTS\\\\t\\\\t\\\\t(\\\\t\\\\t\\\\t\\\\tSELECT *\\\\t\\\\t\\\\t\\\\tFROM dbo.ProductionLotExecutionElements T\\\\t\\\\t\\\\t\\\\tWHERE T.Id = @ProductionLotAggregateId AND T.ExecutionNo = @ExecutionLotReportNo\\\\t\\\\t\\\\t\\\\t\\\\tAND T.ItemId = I.Id AND ISNULL(T.RecipeElementId,0) = ISNULL(RE.No,0)\\\\t\\\\t\\\\t)\\\\t\\\\t\\\\tIF (@@ROWCOUNT > 0)\\\\t\\\\t\\\\t\\\\tSET @ChangesOccurred = 1\\\\t\\\\tEND\\\\t\\\\tBEGIN -- Execution element deliveries\\\\t\\\\t\\\\tDECLARE @TmpDeliveries TABLE (Id BIGINT NOT NULL\', \'Comment 376: ElementNo INT NOT NULL\', \'Comment 377: DeliveryId UNIQUEIDENTIFIER NOT NULL,\\\\t\\\\t\\\\t\\\\tQuantity DECIMAL(18,6) NOT NULL\', \'Comment 378: Unit NVARCHAR(10) NOT NULL)\\\\t\\\\t\\\\tINSERT INTO @TmpDeliveries (Id\', \'Comment 379: ElementNo\', \'Comment 380: DeliveryId\', \'Comment 381: Quantity\', \'Comment 382: Unit)\\\\t\\\\t\\\\tSELECT MIN(APLEED.Id)\', \'Comment 383: PLEE.No\', \'Comment 384: D.Id\', \'Comment 385: SUM(APLEED.Quantity)\', \'Comment 386: I.ItemBaseWeightUnit\\\\t\\\\t\\\\tFROM api.ProductionLotExecutionElementDeliveries APLEED\\\\t\\\\t\\\\tJOIN api.ProductionLotExecutionElements APLEE ON APLEED.ElementId = APLEE.Id\\\\t\\\\t\\\\tJOIN dbo.Items I ON APLEE.PackingItemId = I.EntityId\\\\t\\\\t\\\\tLEFT JOIN dbo.RecipeElements RE ON APLEE.RecipeElementId = RE.EntityId\\\\t\\\\t\\\\tJOIN dbo.ProductionLotExecutionElements PLEE ON PLEE.Id = @ProductionLotAggregateId AND PLEE.ExecutionNo = @ExecutionLotReportNo\\\\t\\\\t\\\\t\\\\tAND PLEE.ItemId = I.Id AND ISNULL(PLEE.RecipeElementId,0) = ISNULL(RE.No,0)\\\\t\\\\t\\\\tJOIN dbo.Deliveries D ON APLEED.DeliveryId = D.EntityId\\\\t\\\\t\\\\tGROUP BY PLEE.No\', \'Comment 387: D.Id\', \'Comment 388: I.ItemBaseWeightUnit\\\\t\\\\t\\\\tUPDATE PLEED\\\\t\\\\t\\\\tSET PLEED.Quantity = TD.Quantity\\\\t\\\\t\\\\tFROM @TmpDeliveries TD\\\\t\\\\t\\\\tJOIN dbo.ProductionLotExecutionElementDeliveries PLEED ON PLEED.Id = @ProductionLotAggregateId\\\\t\\\\t\\\\t\\\\tAND PLEED.ExecutionNo = @ExecutionLotReportNo AND PLEED.ElementNo = TD.ElementNo AND PLEED.DeliveryId = TD.DeliveryId\\\\t\\\\t\\\\tIF (@@ROWCOUNT > 0)\\\\t\\\\t\\\\t\\\\tSET @ChangesOccurred = 1\\\\t\\\\t\\\\t;WITH DeliveryMaxNoCTE (ElementNo\', \'Comment 389: MaxNo) AS\\\\t\\\\t\\\\t(\\\\t\\\\t\\\\t\\\\tSELECT ElementNo\', \'Comment 390: MAX(No)\\\\t\\\\t\\\\t\\\\tFROM dbo.ProductionLotExecutionElementDeliveries\\\\t\\\\t\\\\t\\\\tWHERE Id = @ProductionLotAggregateId AND ExecutionNo = @ExecutionLotReportNo\\\\t\\\\t\\\\t\\\\tGROUP BY ElementNo\\\\t\\\\t\\\\t)\\\\t\\\\t\\\\tINSERT INTO dbo.ProductionLotExecutionElementDeliveries (Id\', \'Comment 391: ExecutionNo\', \'Comment 392: ElementNo\', \'Comment 393: No\', \'Comment 394: DeliveryId\', \'Comment 395: Quantity\', \'Comment 396: QuantityUnit)\\\\t\\\\t\\\\tSELECT @ProductionLotAggregateId\', \'Comment 397: @ExecutionLotReportNo\', \'Comment 398: TD.ElementNo,\\\\t\\\\t\\\\t\\\\tISNULL(C.MaxNo,0) + ROW_NUMBER() OVER (PARTITION BY TD.ElementNo ORDER BY TD.Id)\', \'Comment 399: TD.DeliveryId\', \'Comment 400: TD.Quantity\', \'Comment 401: TD.Unit\\\\t\\\\t\\\\tFROM @TmpDeliveries TD\\\\t\\\\t\\\\tLEFT JOIN DeliveryMaxNoCTE C ON TD.ElementNo = C.ElementNo\\\\t\\\\t\\\\tWHERE NOT EXISTS\\\\t\\\\t\\\\t(\\\\t\\\\t\\\\t\\\\tSELECT *\\\\t\\\\t\\\\t\\\\tFROM dbo.ProductionLotExecutionElementDeliveries PLEED\\\\t\\\\t\\\\t\\\\tWHERE PLEED.Id = @ProductionLotAggregateId AND PLEED.ExecutionNo = @ExecutionLotReportNo\\\\t\\\\t\\\\t\\\\t\\\\tAND PLEED.ElementNo = TD.ElementNo AND PLEED.DeliveryId = TD.DeliveryId\\\\t\\\\t\\\\t)\\\\t\\\\t\\\\tIF (@@ROWCOUNT > 0)\\\\t\\\\t\\\\t\\\\tSET @ChangesOccurred = 1\\\\t\\\\tEND\\\\t\\\\tIF (@ChangesOccurred = 1) -- Event\\\\t\\\\tBEGIN\\\\t\\\\t\\\\tUPDATE dbo.ProductionLotExecutions\\\\t\\\\t\\\\tSET PcsEventSyncState |= @ConstExecutionRegisteredPcsEventSyncStateFlag\\\\t\\\\t\\\\tWHERE Id = @ProductionLotAggregateId AND No = @ExecutionLotReportNo\\\\t\\\\t\\\\tINSERT INTO dbo.PcsIntegrationEvents (EventType\', \'Comment 402: AggregateId\', ""Comment 403: ElementNo)\\\\t\\\\t\\\\tVALUES (\'Plant.PCS.BusinessLogic.DomainAbstractions.ProductionLots.ExecutionReportRegisteredEvent\'"", \'Comment 404: @ProductionLotAggregateId\', \'Comment 405: @ExecutionLotReportNo)\\\\t\\\\tEND\\\\t\\\\tCOMMIT\\\\t\\\\tEXEC dbo.AcceptSqlApiRequest @RequestLogId\\\\tEND TRY\\\\tBEGIN CATCH\\\\t\\\\tIF (@@TRANCOUNT > 0)\\\\t\\\\t\\\\tROLLBACK;\\\\t\\\\tDECLARE @ErrorMessage NVARCHAR(4000) = ERROR_MESSAGE()\\\\t\\\\tEXEC dbo.RejectSqlApiRequest @RequestLogId\', \'Comment 406: @ErrorMessage;\\\\t\\\\tTHROW\\\\tEND CATCHENDGO{code}""\', \'Comment 407: ""*dbo.SaveProductionReport*:{code:sql}CREATE OR ALTER PROCEDURE dbo.SaveProductionReport(\\\\t@ProductionLotAggregateId UNIQUEIDENTIFIER,\\\\t@QuantityKg DECIMAL(18,6))ASBEGIN\\\\tDECLARE @ConstProductionStatusInProgress INT = 2\\\\tDECLARE @ConstProductionStatusFinished INT = 3\\\\tDECLARE @ConstProductionReportRegisteredPcsEventSyncStateFlag INT = 4\\\\tDECLARE @RecipeAggregateId UNIQUEIDENTIFIER\', \'Comment 408: @ReadyProductAggregateId UNIQUEIDENTIFIER\', \'Comment 409: @ProductionOrderAggregateId UNIQUEIDENTIFIER\', \'Comment 410: @PcsLotId BIGINT\\\\tDECLARE @ElementsMappings TABLE (ApiElementId BIGINT NOT NULL\', \'Comment 411: ExecutionNo INT\', \'Comment 412: ElementNo INT\', \'Comment 413: Ratio DECIMAL(16,6) NOT NULL)\\\\tSELECT\\\\t\\\\t@RecipeAggregateId = RecipeId,\\\\t\\\\t@PcsLotId = PcsLotId,\\\\t\\\\t@ReadyProductAggregateId = ReadyProductId,\\\\t\\\\t@ProductionOrderAggregateId = ProductionOrderId\\\\tFROM dbo.ProductionLots\\\\tWHERE Id = @ProductionLotAggregateId\\\\t\\\\t\\\\tBEGIN -- Validation\\\\t\\\\tIF ((SELECT Status FROM dbo.ProductionLots WHERE Id = @ProductionLotAggregateId) != @ConstProductionStatusInProgress)\\\\t\\\\t\\\\tTHROW 50000\', ""Comment 414: \'Cannot register report in current production status.\'"", \'Comment 415: 1;\\\\t\\\\tIF EXISTS (\\\\t\\\\t\\\\tSELECT *\\\\t\\\\t\\\\tFROM api.ProductionLotElements A\\\\t\\\\t\\\\tWHERE A.PcsLotId = @PcsLotId AND A.QuantityKg < 0\\\\t\\\\t)\\\\t\\\\t\\\\tTHROW 50000\', ""Comment 416: \'Production lot element quantity cannot be negative.\'"", \'Comment 417: 1;\\\\t\\\\tIF EXISTS (\\\\t\\\\t\\\\tSELECT *\\\\t\\\\t\\\\tFROM api.ProductionLotElements A\\\\t\\\\t\\\\tLEFT JOIN dbo.RecipeElements E ON A.RecipeElementId = E.EntityId\\\\t\\\\t\\\\tWHERE A.PcsLotId = @PcsLotId AND A.RecipeElementId IS NOT NULL AND (E.Id IS NULL OR E.Id != @RecipeAggregateId)\\\\t\\\\t)\\\\t\\\\t\\\\tTHROW 50000\', ""Comment 418: \'Recipe element in report does not belong to recipe related to current production.\'"", \'Comment 419: 1;\\\\t\\\\tIF EXISTS (\\\\t\\\\t\\\\tSELECT *\\\\t\\\\t\\\\tFROM api.ProductionLotElements A\\\\t\\\\t\\\\tJOIN dbo.Items I ON A.ItemId = I.EntityId\\\\t\\\\t\\\\tLEFT JOIN dbo.RecipeElements E ON A.RecipeElementId = E.EntityId\\\\t\\\\t\\\\tWHERE A.PcsLotId = @PcsLotId AND I.Id != E.ItemId\\\\t\\\\t)\\\\t\\\\t\\\\tTHROW 50000\', ""Comment 420: \'Recipe element in report does not match article in report.\'"", \'Comment 421: 1;\\\\t\\\\tIF EXISTS (\\\\t\\\\t\\\\tSELECT *\\\\t\\\\t\\\\tFROM api.ProductionLotElements APLE\\\\t\\\\t\\\\tJOIN api.ProductionLotElementDeliveries APLED ON APLE.Id = APLED.ElementId\\\\t\\\\t\\\\tWHERE APLE.PcsLotId = @PcsLotId AND APLED.QuantityKg < 0\\\\t\\\\t)\\\\t\\\\t\\\\tTHROW 50000\', ""Comment 422: \'Production lot element delivery quantity cannot be negative.\'"", \'Comment 423: 1;\\\\t\\\\tIF EXISTS (\\\\t\\\\t\\\\tSELECT *\\\\t\\\\t\\\\tFROM api.ProductionLotElements APLE\\\\t\\\\t\\\\tJOIN api.ProductionLotElementDeliveries APLED ON APLE.Id = APLED.ElementId\\\\t\\\\t\\\\tLEFT JOIN dbo.StockUnits SU ON APLED.Barcode = SU.Barcode\\\\t\\\\t\\\\tWHERE APLE.PcsLotId = @PcsLotId AND APLED.Barcode IS NOT NULL AND SU.Id IS NULL\\\\t\\\\t)\\\\t\\\\t\\\\tTHROW 50000\', ""Comment 424: \'Some stock unit barcodes do not exist.\'"", \'Comment 425: 1;\\\\t\\\\tIF EXISTS (\\\\t\\\\t\\\\tSELECT *\\\\t\\\\t\\\\tFROM api.ProductionLotElements AE\\\\t\\\\t\\\\tJOIN api.ProductionLotElementDeliveries AD ON AE.Id = AD.ElementId\\\\t\\\\t\\\\tJOIN dbo.Deliveries D ON AD.DeliveryId = D.EntityId\\\\t\\\\t\\\\tJOIN dbo.StockUnits SU ON AD.Barcode = SU.Barcode\\\\t\\\\t\\\\tWHERE AE.PcsLotId = @PcsLotId AND D.Id != SU.DeliveryId\\\\t\\\\t)\\\\t\\\\t\\\\tTHROW 50000\', ""Comment 426: \'Barcode delivery in report does not match delivery id.\'"", \'Comment 427: 1;\\\\t\\\\tIF EXISTS (\\\\t\\\\t\\\\tSELECT *\\\\t\\\\t\\\\t\\\\tFROM api.ProductionLotElements APLE\\\\t\\\\t\\\\t\\\\tJOIN api.ProductionLotElementDeliveries APLED ON APLE.Id = APLED.ElementId\\\\t\\\\t\\\\t\\\\tJOIN dbo.FactoryObjects FO ON APLED.SiloCode = FO.PcsCode\\\\t\\\\t\\\\t\\\\tJOIN dbo.Items I ON I.EntityId = APLE.ItemId\\\\t\\\\t\\\\tWHERE APLE.PcsLotId = @PcsLotId AND (FO.ItemId IS NULL OR i.Id != FO.ItemId)\\\\t\\\\t)\\\\t\\\\t\\\\tTHROW 50000\', ""Comment 428: \'Raw material on silo does not match to raw material on element.\'"", \'Comment 429: 1;\\\\t\\\\tIF EXISTS (\\\\t\\\\t\\\\tSELECT *\\\\t\\\\t\\\\tFROM api.ProductionLotElements APLE\\\\t\\\\t\\\\tJOIN api.ProductionLotElementDeliveries APLED ON APLE.Id = APLED.ElementId\\\\t\\\\t\\\\tWHERE APLE.PcsLotId = @PcsLotId AND (APLED.DeliveryId IS NOT NULL OR APLED.Barcode IS NOT NULL) AND APLED.SiloCode IS NOT NULL\\\\t\\\\t)\\\\t\\\\t\\\\tTHROW 50000\', ""Comment 430: \'Element delivery cannot specify both delivery and silo.\'"", \'Comment 431: 1;\\\\tEND\\\\tUPDATE dbo.ProductionLots\\\\tSET Quantity = @QuantityKg,\\\\t\\\\tStatus = @ConstProductionStatusFinished,\\\\t\\\\tEndDate = GETDATE(),\\\\t\\\\tPcsEventSyncState |= @ConstProductionReportRegisteredPcsEventSyncStateFlag\\\\tWHERE Id = @ProductionLotAggregateId;\\\\tINSERT INTO @ElementsMappings (ApiElementId\', \'Comment 432: ExecutionNo\', \'Comment 433: ElementNo\', \'Comment 434: Ratio)\\\\tSELECT ApiElementId\', \'Comment 435: ExecutionNo\', \'Comment 436: ElementNo\', \'Comment 437: Ratio\\\\tFROM dbo.GetProductionElementsMappings(@ProductionLotAggregateId\', \'Comment 438: @PcsLotId\', ""Comment 439: NULL)\\\\t\\\\tBEGIN -- Elements\\\\t\\\\tDECLARE @ConstAllowStockRegisteringOnSilosKey INT = 3\\\\t\\\\tDECLARE @ConstAllowStockRegisteringOnSilosTrueValue NVARCHAR(4) = \'True\'\\\\t\\\\tDECLARE @AllowStockRegisteringOnSilos BIT = IIF((\\\\t\\\\t\\\\tSELECT [Value]\\\\t\\\\t\\\\tFROM dbo.Configuration\\\\t\\\\t\\\\tWHERE [Key] = @ConstAllowStockRegisteringOnSilosKey) = @ConstAllowStockRegisteringOnSilosTrueValue,\\\\t\\\\t\\\\t1,\\\\t\\\\t\\\\t0)\\\\t\\\\t;WITH AggregatedElementsCTE (ElementNo"", \'Comment 440: QuantityKg) AS\\\\t\\\\t(\\\\t\\\\t\\\\tSELECT M.ElementNo\', \'Comment 441: SUM(A.QuantityKg * M.Ratio)\\\\t\\\\t\\\\tFROM @ElementsMappings M\\\\t\\\\t\\\\tJOIN api.ProductionLotElements A ON M.ApiElementId = A.Id\\\\t\\\\t\\\\tWHERE M.ExecutionNo IS NULL\\\\t\\\\t\\\\tGROUP BY M.ElementNo\\\\t\\\\t)\\\\t\\\\tUPDATE E\\\\t\\\\tSET Quantity = C.QuantityKg\\\\t\\\\tFROM AggregatedElementsCTE C\\\\t\\\\tJOIN dbo.ProductionLotElements E ON E.Id = @ProductionLotAggregateId AND C.ElementNo = E.No\\\\t\\\\tDECLARE @MaxNo INT = (SELECT MAX(No) FROM dbo.ProductionLotElements WHERE Id = @ProductionLotAggregateId);\\\\t\\\\t\\\\t\\\\tINSERT INTO dbo.ProductionLotElements (Id\', \'Comment 442: No\', \'Comment 443: ItemId\', \'Comment 444: Quantity\', \'Comment 445: QuantityUnit\', \'Comment 446: RequestedQuantity\', \'Comment 447: RequestedQuantityUnit)\\\\t\\\\tSELECT @ProductionLotAggregateId\', \'Comment 448: @MaxNo + ROW_NUMBER() OVER (ORDER BY MIN(A.Id))\', \'Comment 449: I.Id\', \'Comment 450: SUM(A.QuantityKg * M.Ratio)\', ""Comment 451: \'kg\'"", \'Comment 452: 0\', ""Comment 453: \'kg\'\\\\t\\\\tFROM api.ProductionLotElements A\\\\t\\\\tJOIN @ElementsMappings M ON A.Id = M.ApiElementId\\\\t\\\\tJOIN dbo.Items I ON A.ItemId = I.EntityId\\\\t\\\\tWHERE M.ExecutionNo IS NULL AND M.ElementNo IS NULL\\\\t\\\\tGROUP BY I.Id\\\\t\\\\tUPDATE M\\\\t\\\\tSET ElementNo = E.No\\\\t\\\\tFROM api.ProductionLotElements A\\\\t\\\\tJOIN dbo.Items I ON A.ItemId = I.EntityId\\\\t\\\\tJOIN @ElementsMappings M ON A.Id = M.ApiElementId\\\\t\\\\tJOIN dbo.ProductionLotElements E ON E.Id = @ProductionLotAggregateId AND I.Id = E.ItemId\\\\t\\\\tWHERE M.ExecutionNo IS NULL AND M.ElementNo IS NULL\\\\t\\\\tINSERT INTO dbo.ProductionLotElementDeliveries (Id"", \'Comment 454: ElementNo\', \'Comment 455: No\', \'Comment 456: DeliveryId\', \'Comment 457: StockUnitId\', \'Comment 458: Quantity\', \'Comment 459: QuantityUnit\', \'Comment 460: TotalStockUnitConsumption)\\\\t\\\\tSELECT @ProductionLotAggregateId\', \'Comment 461: M.ElementNo\', \'Comment 462: ROW_NUMBER() OVER (PARTITION BY M.ElementNo ORDER BY MIN(APLED.Id)),\\\\t\\\\t\\\\tISNULL(SU.DeliveryId\', \'Comment 463: DD.Id)\', \'Comment 464: SU.Id\', \'Comment 465: SUM(APLED.QuantityKg) * M.Ratio\', ""Comment 466: \'kg\'"", \'Comment 467: IIF(SU.Id IS NULL,0,APLED.TotalBarcodeConsumption)\\\\t\\\\tFROM api.ProductionLotElementDeliveries APLED\\\\t\\\\tJOIN @ElementsMappings M ON APLED.ElementId = M.ApiElementId\\\\t\\\\tLEFT JOIN dbo.Deliveries DD ON APLED.DeliveryId = DD.EntityId\\\\t\\\\tLEFT JOIN dbo.StockUnits SU ON APLED.Barcode = SU.Barcode\\\\t\\\\tWHERE M.ExecutionNo IS NULL AND ISNULL(SU.DeliveryId\', \'Comment 468: DD.Id) IS NOT NULL\\\\t\\\\tGROUP BY M.ElementNo\', \'Comment 469: SU.DeliveryId\', \'Comment 470: DD.Id\', \'Comment 471: SU.Id\', \'Comment 472: M.Ratio\', \'Comment 473: APLED.TotalBarcodeConsumption\\\\t\\\\tDECLARE @DosingMaxNo INT = ISNULL((SELECT MAX(No) FROM dbo.Dosings WHERE Id = @ProductionLotAggregateId),0)\\\\t\\\\tDECLARE @TmpDosings TABLE (ElementNo INT NOT NULL\', \'Comment 474: DeliveryAggregateId UNIQUEIDENTIFIER\', \'Comment 475: StockUnitAggregateId UNIQUEIDENTIFIER\', \'Comment 476: SiloAggregateId UNIQUEIDENTIFIER\', \'Comment 477: QuantityKg DECIMAL(18,6))\\\\t\\\\t\\\\t\\\\tINSERT INTO @TmpDosings (ElementNo\', \'Comment 478: DeliveryAggregateId\', \'Comment 479: StockUnitAggregateId\', \'Comment 480: SiloAggregateId\', \'Comment 481: QuantityKg)\\\\t\\\\tSELECT M.ElementNo\', \'Comment 482: ISNULL(SU.DeliveryId\', \'Comment 483: D.Id)\', \'Comment 484: SU.Id\', \'Comment 485: IIF(@AllowStockRegisteringOnSilos = 1,FO.Id,NULL)\', \'Comment 486: APLED.QuantityKg * M.Ratio\\\\t\\\\tFROM api.ProductionLotElementDeliveries APLED\\\\t\\\\tJOIN @ElementsMappings M ON APLED.ElementId = M.ApiElementId\\\\t\\\\tLEFT JOIN dbo.Deliveries D ON APLED.DeliveryId = D.EntityId\\\\t\\\\tLEFT JOIN dbo.StockUnits SU ON APLED.Barcode = SU.Barcode\\\\t\\\\tLEFT JOIN dbo.FactoryObjects FO ON APLED.SiloCode = FO.PcsCode\\\\t\\\\tWHERE M.ExecutionNo IS NULL AND COALESCE(SU.DeliveryId\', \'Comment 487: D.Id\', \'Comment 488: IIF(@AllowStockRegisteringOnSilos = 1,FO.Id,NULL)) IS NOT NULL\\\\t\\\\t\\\\t\\\\tINSERT INTO dbo.Dosings (Id\', \'Comment 489: No\', \'Comment 490: BatchNo\', \'Comment 491: BatchElementNo\', \'Comment 492: ElementNo\', \'Comment 493: Quantity\', \'Comment 494: QuantityUnit\', \'Comment 495: Date\', \'Comment 496: DeliveryId\', \'Comment 497: StockUnitId\', \'Comment 498: SiloId)\\\\t\\\\tSELECT \\\\t\\\\t\\\\t@ProductionLotAggregateId,\\\\t\\\\t\\\\t@DosingMaxNo + ROW_NUMBER() OVER (ORDER BY TD.ElementNo\', \'Comment 499: TD.DeliveryAggregateId\', \'Comment 500: TD.StockUnitAggregateId\', \'Comment 501: TD.SiloAggregateId),\\\\t\\\\t\\\\tNULL\', \'Comment 502: \\\\t\\\\t\\\\tNULL\', \'Comment 503: \\\\t\\\\t\\\\tTD.ElementNo,\\\\t\\\\t\\\\tTD.QuantityKg\', ""Comment 504: \\\\t\\\\t\\\\t\'kg\'"", \'Comment 505: \\\\t\\\\t\\\\tGETDATE()\', \'Comment 506: \\\\t\\\\t\\\\tTD.DeliveryAggregateId\', \'Comment 507: \\\\t\\\\t\\\\tTD.StockUnitAggregateId\', \'Comment 508: \\\\t\\\\t\\\\tTD.SiloAggregateId\\\\t\\\\tFROM @TmpDosings TD\\\\tEND\\\\tBEGIN -- Executions\\\\t\\\\tUPDATE dbo.ProductionLotExecutions\\\\t\\\\tSET Quantity = @QuantityKg,\\\\t\\\\t\\\\tRequestedQuantity = IIF(@ProductionOrderAggregateId IS NULL\', \'Comment 509: @QuantityKg\', \'Comment 510: RequestedQuantity)\\\\t\\\\tWHERE Id = @ProductionLotAggregateId AND ReadyProductId = @ReadyProductAggregateId\\\\t\\\\tUPDATE dbo.ProductionLots\\\\t\\\\tSET RequestedQuantity = (SELECT SUM(RequestedQuantity) FROM dbo.ProductionLotExecutions WHERE Id = @ProductionLotAggregateId)\\\\t\\\\tWHERE Id = @ProductionLotAggregateId;\\\\tEND\\\\tBEGIN -- Execution elements\\\\t\\\\t;WITH AggregatedExecutionElementsCTE (ExecutionNo\', \'Comment 511: ElementNo\', \'Comment 512: QuantityKg) AS\\\\t\\\\t(\\\\t\\\\t\\\\tSELECT M.ExecutionNo\', \'Comment 513: M.ElementNo\', \'Comment 514: SUM(A.QuantityKg * M.Ratio)\\\\t\\\\t\\\\tFROM @ElementsMappings M\\\\t\\\\t\\\\tJOIN api.ProductionLotElements A ON M.ApiElementId = A.Id\\\\t\\\\t\\\\tWHERE M.ExecutionNo IS NOT NULL\\\\t\\\\t\\\\tGROUP BY M.ExecutionNo\', \'Comment 515: M.ElementNo\\\\t\\\\t)\\\\t\\\\tUPDATE EE\\\\t\\\\tSET Quantity = C.QuantityKg\\\\t\\\\tFROM AggregatedExecutionElementsCTE C\\\\t\\\\tJOIN dbo.ProductionLotExecutionElements EE ON EE.Id = @ProductionLotAggregateId\\\\t\\\\t\\\\tAND EE.ExecutionNo = C.ExecutionNo AND EE.No = C.ElementNo\\\\t\\\\t;WITH ExecutionElementMaxNoCTE (ExecutionNo\', \'Comment 516: ElementMaxNo) AS\\\\t\\\\t(\\\\t\\\\t\\\\tSELECT ExecutionNo\', \'Comment 517: MAX(No)\\\\t\\\\t\\\\tFROM dbo.ProductionLotExecutionElements\\\\t\\\\t\\\\tWHERE Id = @ProductionLotAggregateId\\\\t\\\\t\\\\tGROUP BY ExecutionNo\\\\t\\\\t)\\\\t\\\\tINSERT INTO dbo.ProductionLotExecutionElements (Id\', \'Comment 518: ExecutionNo\', \'Comment 519: No,\\\\t\\\\t\\\\tItemId\', \'Comment 520: Quantity\', \'Comment 521: QuantityUnit\', \'Comment 522: RequestedQuantity\', \'Comment 523: RequestedQuantityUnit)\\\\t\\\\tSELECT @ProductionLotAggregateId\', \'Comment 524: M.ExecutionNo\', \'Comment 525: ISNULL(C.ElementMaxNo,0) + ROW_NUMBER() OVER (PARTITION BY M.ExecutionNo ORDER BY MIN(A.Id)),\\\\t\\\\t\\\\tI.Id\', \'Comment 526: SUM(A.QuantityKg * M.Ratio)\', \'Comment 527: I.ItemBaseWeightUnit\', \'Comment 528: 0\', \'Comment 529: I.ItemBaseWeightUnit\\\\t\\\\tFROM api.ProductionLotElements A\\\\t\\\\tJOIN @ElementsMappings M ON A.Id = M.ApiElementId\\\\t\\\\tJOIN dbo.Items I ON A.ItemId = I.EntityId\\\\t\\\\tLEFT JOIN ExecutionElementMaxNoCTE C ON M.ExecutionNo = C.ExecutionNo\\\\t\\\\tWHERE M.ExecutionNo IS NOT NULL AND M.ElementNo IS NULL\\\\t\\\\tGROUP BY M.ExecutionNo\', \'Comment 530: C.ElementMaxNo\', \'Comment 531: I.Id\', \'Comment 532: I.ItemBaseWeightUnit\\\\t\\\\tUPDATE M\\\\t\\\\tSET ElementNo = EE.No\\\\t\\\\tFROM api.ProductionLotElements A\\\\t\\\\tJOIN dbo.Items I ON A.ItemId = I.EntityId\\\\t\\\\tJOIN @ElementsMappings M ON A.Id = M.ApiElementId\\\\t\\\\tJOIN dbo.ProductionLotExecutionElements EE ON EE.Id = @ProductionLotAggregateId AND EE.ExecutionNo = M.ExecutionNo AND EE.ItemId = I.Id\\\\t\\\\tWHERE M.ExecutionNo IS NOT NULL AND M.ElementNo IS NULL\\\\t\\\\tINSERT INTO dbo.ProductionLotExecutionElementDeliveries (Id\', \'Comment 533: ExecutionNo\', \'Comment 534: ElementNo\', \'Comment 535: No\', \'Comment 536: DeliveryId\', \'Comment 537: StockUnitId\', \'Comment 538: Quantity\', \'Comment 539: QuantityUnit)\\\\t\\\\tSELECT @ProductionLotAggregateId\', \'Comment 540: M.ExecutionNo\', \'Comment 541: M.ElementNo\', \'Comment 542: ROW_NUMBER() OVER (PARTITION BY M.ExecutionNo\', \'Comment 543: M.ElementNo ORDER BY MIN(APLED.Id)),\\\\t\\\\t\\\\tISNULL(SU.DeliveryId\', \'Comment 544: DD.Id)\', \'Comment 545: SU.Id\', \'Comment 546: SUM(APLED.QuantityKg * M.Ratio)\', ""Comment 547: \'kg\'\\\\t\\\\tFROM api.ProductionLotElementDeliveries APLED\\\\t\\\\tJOIN @ElementsMappings M ON APLED.ElementId = M.ApiElementId\\\\t\\\\tLEFT JOIN dbo.Deliveries DD ON APLED.DeliveryId = DD.EntityId\\\\t\\\\tLEFT JOIN dbo.StockUnits SU ON APLED.Barcode = SU.Barcode\\\\t\\\\tWHERE M.ExecutionNo IS NOT NULL AND ISNULL(SU.DeliveryId"", \'Comment 548: DD.Id) IS NOT NULL\\\\t\\\\tGROUP BY M.ExecutionNo\', \'Comment 549: M.ElementNo\', \'Comment 550: SU.DeliveryId\', \'Comment 551: DD.Id\', \'Comment 552: SU.Id\\\\tEND\\\\tDELETE APLED\\\\tFROM api.ProductionLotElementDeliveries APLED\\\\tJOIN api.ProductionLotElements APLE ON APLE.Id = APLED.ElementId\\\\tWHERE APLE.PcsLotId = @PcsLotId\\\\tDELETE FROM api.ProductionLotElements\\\\tWHERE PcsLotId = @PcsLotId\\\\tINSERT INTO dbo.PcsIntegrationEvents (EventType\', ""Comment 553: AggregateId)\\\\tVALUES (\'Plant.PCS.BusinessLogic.DomainAbstractions.ProductionLots.ProductionReportRegisteredEvent\'"", \'Comment 554: @ProductionLotAggregateId)ENDGO{code}""\', ""Comment 555: \'On all plants have been removed the mentioned validations from the database level"", ""Comment 556: the problem should no longer occur.\'"", ""Comment 557: \'Oke"", ""Comment 558: thanks for now: ticket can be closed\'"", ""Comment 559: \'Thank you\']""]\nRelated Issues:\n[]\n\n### End'}"
192,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8840\n\n### Instruction:\nPlease, change the status of the Production Report from Canceled to Finished. Production Report number: 0742150323001\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Dear,According to the service agreement this task should be categorized as a service request.Kindly approve change of the type of this task.Regards\'"", ""Comment 4: \'please change the category of the task\'"", \'Comment 5: ""id=2806eca0-57b6-4100-a5c2-8fdfc07cfe5d — id plrPLR nie ma w DHC.nie ma w bazie pcdlogicmainjest w bazie stock i prod\', \'Comment 6: wms!image-2023-04-04-10-53-44-477.png|width=826,height=123!na wydarzeniach user pcs edytował to ale użytwkonik Admin anulował to 17.03select * from ProductionLots where AggregateId=\\\'2806eca0-57b6-4100-a5c2-8fdfc07cfe5d\\\' !image-2023-04-04-10-53-44-477!""\', ""Comment 7: \'Good morning I see that currently there is no this PLR in the PCs database"", \'Comment 8: it has not been sent to DHC. Do you expect it to go to DHC and ERP? Why should its status be changed\', \'Comment 9: has this shipment been created and what about the stocks in this situation?Should they be created as for a normal PLR\', ""Comment 10: or have they already been consumed,Regarding the creation of stock have you considered stocktaking?\'"", ""Comment 11: \'We have analyzed the situation and in the given situation we ask you to create a new plr"", ""Comment 12: recommended.May we close the task?\'"", ""Comment 13: \'May we close the task?\']""]\nRelated Issues:\n[]\n\n### End'}"
193,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8839\n\n### Instruction:\nItemcode 257551 not sync to DHP\r\n\r\nError Log :\r\n2023-03-27 11:06:56,177 [14] ERROR Evolution.DHCService.Dhc30.Handlers.ItemChangedMessageHandler [E:\\BambooHome\\xml-data\\build-dir\\4292609\\DHAPPSV3-DHCSER411-JOB1\\Evolution.DHCService\\Evolution.DHCService.Dhc30\\Handlers\\BaseMessageHandler.cs:56] - System.Data.Entity.Infrastructure.DbUpdateException: An error occurred while updating the entries. See the inner exception for details. ---> System.Data.Entity.Core.UpdateException: An error occurred while updating the entries. See the inner exception for details. ---> System.Data.SqlClient.SqlException: The INSERT statement conflicted with the FOREIGN KEY constraint ""FK_dbo.Items_dbo.DhhItems_DhhItemId"". The conflict occurred in database ""Evolution_DHCService_IND"", table ""dbo.DhhItems"", column \'Id\'.\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Data has been corrected"", ""Comment 3: please verify and send a feedback.\'"", ""Comment 4: \'OK data has been sync"", ""Comment 5: thank you\'"", ""Comment 6: \'hi"", ""Comment 7: could you tell us the route cause of this issue? Did it come from user input or what?\'"", ""Comment 8: \'Yes"", ""Comment 9: the reason was missing DHHItem in DhcService database which was fixed in DHC version 3.0.60.\']""]\nRelated Issues:\n[]\n\n### End'}"
194,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8838\n\n### Instruction:\nPlease import additional technologies for plant Helmond (9) in DHC test and DHC prod as listed in attached excel, tab Import sheet.\r\n\r\nSee tab README in the excel for more details.\n\n### Response:\n[""Comment 1: [\'[^20230327_DHC_Helmond_additional_technology.xlsx] _(1,19 MB)_\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Dear,According to the service agreement this task should be categorized as a service request.Kindly approve change of the type of this task.Regards\'"", ""Comment 4: \'You are correct. Please update the type to service request.\'"", ""Comment 5: \'Hej Przemku zadanie chyba dla Ciebie.\'"", ""Comment 6: \'Import:!image-2023-03-30-11-37-01-524.png!!image-2023-03-30-11-37-01-524!\'"", ""Comment 7: \'Import has be done"", ""Comment 8: please verify.\'"", ""Comment 9: \'Thank you. Import was done correctly. This ticket can be closed\']""]\nRelated Issues:\n[]\n\n### End'}"
195,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8837\n\n### Instruction:\nHello,\r\n\r\ncan you please investigate trip 00996605: There are two VT\'s connected: one for bulk and one for the packed goods: It should\'t be possible to create 2 VT\'s connected to one trip in our configuration: Can you please investigate how this can happen and how to prevent?\n\n### Response:\n[""Comment 1: [\'!afbeelding!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'!image-2023-03-28-15-52-23-230.png!Tego jednego nie ma w DHC!image-2023-03-28-16-25-37-875.png!\'"", ""Comment 4: \'!image-2023-03-28-16-29-14-320.png!\'"", ""Comment 5: \'Wygląda na to"", ""Comment 6: że VT były zakładane jednocześnie:!image-2023-03-28-16-59-25-952.png!Ten PCSowy jest closed i ma mapowanie:!image-2023-03-28-17-00-06-590.png!\'"", ""Comment 7: \'!image-2023-03-28-17-03-48-015.png!\'"", ""Comment 8: \'Na każdym VT są i packed i bulk"", \'Comment 9: nie ża na jednym VT jedno\', ""Comment 10: a na drugim drugie!image-2023-03-28-17-14-38-680.png!\'"", ""Comment 11: \'I zastanawiam się czy to nie jest ten element configu!image-2023-03-28-17-15-29-030.png!\'"", ""Comment 12: \'No i stety lub nie"", ""Comment 13: oba VT mają elementy released:!image-2023-03-28-17-17-17-757.png!!image-2023-03-28-17-17-36-985.png!\'"", ""Comment 14: \'!image-2023-03-28-17-24-37-558.png!\'"", ""Comment 15: \'Zgodnie z rozmową Teams\'"", ""Comment 16: \'Hi Thomas,We need to consult your configuration issue with dev team. We will let you know about the result as soon as possible.Regards\'"", \'Comment 17: ""1. PCS wysyła loading report(/) Tworzy się VT\', ""Comment 18: ilości dla bulków są rejestrowane2. Prawie w tym samym czasie użytkownik \'produtrecht\' klika na opcję tworzenia VT. Ponieważ lista tripów nie została odświeżona"", ""Comment 19: to dalej miał dostępną opcję \'create VT\'. Gdyby lista została odświeżona"", \'Comment 20: to opcja \\\'create VT\\\' byłaby nieaktywna.: [^2 vt_trip.mp4]Utworzony DAP: DAP-13496 (realizacja w 8.6) !image-2023-03-29-13-24-35-050!""\', ""Comment 21: \'Dear Thomas,We can confirm that PCS sent loading report"", \'Comment 22: then VT has been created and quantities for bulk are registered. 3 seconds later\', \'Comment 23: userprodutrecht has clicked ""create vt"". As Trip list has not been refreshed\', \'Comment 24: produtrech had opition ""cretae vt"" available. As a resultprodutrech created VT-1459. All quantities forpacked bulkare registered on VT-1458 so we think VT-1459 could be cancelled (now it is in progress).Regards\\\'\', ""Comment 25: \'Yes it is indeed: But I think a change is needed to prevent this situation from happening?\'"", ""Comment 26: \'We have raised a task to prevent such situation. It will be fixed in 8.6 version.Please"", ""Comment 27: let me know if we should cancelVT-1459.Regards\'"", ""Comment 28: \'Yes you can cancel 1459\'"", ""Comment 29: \'Done.Can we close this task then?Regards\'"", ""Comment 30: \'!image-2023-04-03-11-27-46-854.png!\'"", ""Comment 31: \'can be closed\'"", ""Comment 32: \'Thank you\']""]\nRelated Issues:\n[\'DAP-13496\']\n\n### End'}"
196,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8836\n\n### Instruction:\nHello, \n\n\xa0 \n\nI’m resending this email to you, because I got automatic answer from Marta that she isn’t in office today. \n\nCould you please look at our DHC client why is it not working? \n\n\xa0 \n\nMore details bellow. \n\n\xa0 \n\nThank you. \n\n\xa0 \n| \n| \n| \n| \n|{color:blue}{color} !http://www.energyshobby.cz/_email/ENG/body_it.jpg!{color:blue}{color} <[http://www.energyshobby.cz/_email/ENG/body_url_it.htm]> |  \n\n{color:black}Best regards\n \n  *Michal Polacek*\n IT administrator\n Mobile nr.:\xa0+420 775 862 755{color}\n [{color:blue}mpolacek@deheus.com{color}|mailto:mpolacek@deheus.com]{color:black}{color} \n| \n| \n| !http://www.energyshobby.cz/_email/ENG/line.jpg! | \n| \n| \n| !http://www.energyshobby.cz/_email/ENG/royal_eng.png! | \n| \n| \n|{color:blue}{color} !http://www.energyshobby.cz/_email/ENG/logo.png!{color:blue}{color} <[http://www.deheus.com/]> |  \n\n  *{color:#2181C0} *De Heus a.s.*{color}*{color:#2181C0}\n Marefy 144, 685 01 Bucovice, Czech Republic\n REG nr.: 25321498, VAT nr.: CZ25321498\n Tel.: +420 517 307 701, Fax: +420 517 307 702{color}\n [{color:blue}info@deheus.cz{color}|mailto:info@deheus.cz%20%20]{color:#2181C0}\xa0/\xa0{color}[{color:blue}www.deheus.cz{color}|http://www.deheus.cz]{color:#2181C0}{color} \n  \n\n\xa0 \n  \n\n *From:* Poláček, Michal \n  *Sent:* Monday, March 27, 2023 12:40 PM\n  *To:* Marta Litkie <marta.litkie@kotrak.com>\n  *Cc:* Svoboda, Petr <PSvoboda@deheus.com>; Adamcik, Michal <madamcik@deheus.com>; Horáková, Lucie <lhorakova@deheus.com>; Blazek, Oldrich <OBlazek@deheus.com>\n  *Subject:* DHC not working   \n\n\xa0 \n\nHello Marta, \n\n\xa0 \n\nOn Saturaday night I restarted DHC server 10.42.0.198 because there was windows update waiting for restart and today I needed restart PRODSQL server 10.42.0.195 where I think is database for DHC. \n\nHowever right now DHC is not working. I checked services and Business platform service is running. \n\n\xa0 \n\nCould you please look at that? \n\n\xa0 \n| \n| \n| \n| \n|{color:blue}{color} !http://www.energyshobby.cz/_email/ENG/body_it.jpg!{color:blue}{color} <[http://www.energyshobby.cz/_email/ENG/body_url_it.htm]> |  \n\n{color:black}Best regards\n \n  *Michal Polacek*\n IT administrator\n Mobile nr.:\xa0+420 775 862 755{color}\n [{color:blue}mpolacek@deheus.com{color}|mailto:mpolacek@deheus.com]{color:black}{color} \n| \n| \n| !http://www.energyshobby.cz/_email/ENG/line.jpg! | \n| \n| \n| !http://www.energyshobby.cz/_email/ENG/royal_eng.png! | \n| \n| \n|{color:blue}{color} !http://www.energyshobby.cz/_email/ENG/logo.png!{color:blue}{color} <[http://www.deheus.com/]> |  \n\n  *{color:#2181C0} *De Heus a.s.*{color}*{color:#2181C0}\n Marefy 144, 685 01 Bucovice, Czech Republic\n REG nr.: 25321498, VAT nr.: CZ25321498\n Tel.: +420 517 307 701, Fax: +420 517 307 702{color}\n [{color:blue}info@deheus.cz{color}|mailto:info@deheus.cz%20%20]{color:#2181C0}\xa0/\xa0{color}[{color:blue}www.deheus.cz{color}|http://www.deheus.cz]{color:#2181C0}{color} \n \n\n\xa0\n\n### Response:\n[""Comment 1: [\'Hi Michal,This should be reported as an incident via portal [https://helpdesk.kotrak.com/servicedesk/customer/portal/56]"", ""Comment 2: not directly via email to Marta.Regards\'"", ""Comment 3: \'Hello"", \'Comment 4:  Ok\', \'Comment 5: sorry. I will create an ticket on kotrak helpdesk righ now.  | | | | | !http://www.energyshobby.cz/_email/ENG/body_it.jpg! <[http://www.energyshobby.cz/_email/ENG/body_url_it.htm]> |  {color:black}Best regards   *Michal Polacek* IT administrator Mobile nr.:+420 775 862 755{color} [{color:black}mpolacek@deheus.com{color}|mailto:mpolacek@deheus.com]{color:black}{color} | | | !http://www.energyshobby.cz/_email/ENG/line.jpg! | | | | !http://www.energyshobby.cz/_email/ENG/royal_eng.png! | | | | !http://www.energyshobby.cz/_email/ENG/logo.png! <[http://www.deheus.com/]> |    *{color:#2181C0} *De Heus a.s.*{color}*{color:#2181C0} Marefy 144\', \'Comment 6: 685 01 Bucovice\', \'Comment 7: Czech Republic REG nr.: 25321498\', \'Comment 8: VAT nr.: CZ25321498 Tel.: +420 517 307 701\', \'Comment 9: Fax: +420 517 307 702{color} [{color:#2181C0}info@deheus.cz{color}|mailto:info@deheus.cz%20%20]{color:#2181C0}/{color}[{color:#2181C0}www.deheus.cz{color}|http://www.deheus.cz]{color:#2181C0}{color}       *From:* Aleksandra Przybyłek (Jira) <jira@kotrak.com>   *Sent:* Monday\', \'Comment 10: March 27\', \'Comment 11: 2023 1:14 PM  *To:* Poláček\', ""Comment 12: Michal <mpolacek@deheus.com>  *Subject:* EAS-17271 FW: DHC not working   \'"", ""Comment 13: \'Task to close. Issue realized under ticket DGS-8835\']""]\nRelated Issues:\n[]\n\n### End'}"
197,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8835\n\n### Instruction:\nHello,\r\nOn Saturaday night I restarted DHC server 10.42.0.198 because there was windows update waiting for restart and today I needed restart PRODSQL server 10.42.0.195 where I think is database for DHC.\r\nHowever right now DHC is not working. I checked services and Business platform service is running.\r\n\r\nCould you please look at that?\r\n\n\n### Response:\n[""Comment 1: [\'Hello,\\\\r\\\\rWe are investigating your issue. We will inform you about the solution as soon as possible.\\\\r\\\\rRegards\\\\r\\\\r\'"", ""Comment 2: \'Michal,DHC should work now. Please"", ""Comment 3: verify on your side.Regards\'"", ""Comment 4: \'Wszystkie trzy były stopped after crash!image-2023-03-27-13-22-33-115.png!\'"", ""Comment 5: \'!image-2023-03-27-13-23-15-407.png!\'"", ""Comment 6: \'Hi"", ""Comment 7: Yes it is working now.Thank you.\'"", ""Comment 8: \'No problem:)Regards\']""]\nRelated Issues:\n[]\n\n### End'}"
198,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8834\n\n### Instruction:\nHello,\r\n\r\nSOBE000018358 contains orderelements for item 111409: this is a composition and there is an additional technology for it. This AT was incorrect, with 0044 set to 20%, this is adjusted with a subversion and now it is set to 35%. However, order is still send with blendpercentage 20%: Can you please check and advise how to solve it? This is P1 because order needs to be procuced ASAP\r\n\r\n<ItemCodeBase>111409</ItemCodeBase><BlendItemCodeMain>111443</BlendItemCodeMain><BlendItemCodeAddition>0044</BlendItemCodeAddition><BlendPercentage>20</BlendPercentage>\n\n### Response:\n[""Comment 1: [\'!afbeelding!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 3: ""Hello\', \'Comment 4: I can confirm it\\\'s now synced correct. Ticket can be closed""]\']\nRelated Issues:\n[]\n\n### End'}"
199,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8833\n\n### Instruction:\nWe cannot start the app from RSTS01 server, documents are not syncronized. Can you please check asap?\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'!image-2023-03-27-12-18-31-745.png!!image-2023-03-27-12-26-35-129.png!!image-2023-03-27-12-26-35-129!\'"", ""Comment 4: \'Please"", ""Comment 5: check now. It should be running now. Reason: Business Platform was not running.Regards\'"", ""Comment 6: \'Tnx its working now. Can you tell me the exact name of the service"", \'Comment 7: because I looked for it in the list and could not find it? That is\', ""Comment 8: there is no bussines platform service in the list of Windows services. What is the path to that services? \'"", ""Comment 9: \'Business Platform. On DHC serverRSAPP08 – 10.100.3.54\'"", ""Comment 10: \'Ok"", ""Comment 11: thanks. You can close the ticket.\'"", ""Comment 12: \'Thank you\']""]\nRelated Issues:\n[]\n\n### End'}"
200,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8832\n\n### Instruction:\nHello,\r\n\r\nVT 481/3/23 cannot be cancelled in DHP: This is a VT for a bulk intake, but on the call off you can see this is a warehouse item, settlement is set to pcs: so I expect the intake to be done in the DHP warehouse module: can you see why this fails and cancel this VT so we can create a new correct VT?\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-03-27 12:47:32 (0883486c-2a82-4344-8613-d7185eeba8cc/Plant.VC.BusinessLogic/DHVD01AP184/3312/14) [Error] Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware - Error during request{  ""scheme"": ""http""\', \'Comment 3:  ""host"": {    ""Value"": ""dhvd01ap184:82""\', \'Comment 4:    ""HasValue"": true\', \'Comment 5:    ""Host"": ""dhvd01ap184""\', \'Comment 6:    ""Port"": 82  }\', \'Comment 7:  ""path"": ""/api/VehicleTicket/cancelVehicleTicket""\', \'Comment 8:  ""queryString"": []\', \'Comment 9:  ""requestBody"": ""{\\\\\\\\""vehicleTicketId\\\\\\\\"":\\\\\\\\""614d4c63-0a53-4fb2-862e-d35dc808e1dc\\\\\\\\"",\\\\\\\\""reactionReasonId\\\\\\\\"":\\\\\\\\""1a40ebe4-f74a-4969-ab9d-63b57ebbbfa9\\\\\\\\""}""}.AutoMapper.AutoMapperMappingException: Error mapping types.Mapping types:VehicleTicket -> VehicleTicketEntityPlant.VC.BusinessLogic.Domain.VehicleTickets.VehicleTicket -> Plant.VC.BusinessLogic.Infrastructure.Persistance.VehicleTickets.VehicleTicketEntityType Map configuration:VehicleTicket -> VehicleTicketEntityPlant.VC.BusinessLogic.Domain.VehicleTickets.VehicleTicket -> Plant.VC.BusinessLogic.Infrastructure.Persistance.VehicleTickets.VehicleTicketEntityDestination Member:BulkIntakeElements ---> AutoMapper.AutoMapperMappingException: Error mapping types.Mapping types:VehicleTicketBulkIntakeElement -> VehicleTicketBulkIntakeElementEntityPlant.VC.BusinessLogic.Domain.VehicleTickets.VehicleTicketBulkIntakeElement -> Plant.VC.BusinessLogic.Infrastructure.Persistance.VehicleTickets.VehicleTicketBulkIntakeElementEntityType Map configuration:VehicleTicketBulkIntakeElement -> VehicleTicketBulkIntakeElementEntityPlant.VC.BusinessLogic.Domain.VehicleTickets.VehicleTicketBulkIntakeElement -> Plant.VC.BusinessLogic.Infrastructure.Persistance.VehicleTickets.VehicleTicketBulkIntakeElementEntityDestination Member:WeightValue ---> System.ArgumentException: Unit mismatch   at Kotrak.Common.SharedKernel.Quantity.ToCommonUnit(Quantity x1\', \'Comment 10: Quantity x2)   at Plant.VC.BusinessLogic.Domain.VehicleTickets.VehicleTicketBulkIntakeElement.get_Weight() in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\67ba263564c33499\\\\\\\\Plant.VC.BusinessLogic\\\\\\\\Plant.VC.BusinessLogic.Domain\\\\\\\\VehicleTickets\\\\\\\\VehicleTicketBulkIntakeElement.cs:line 32   at lambda_method9444(Closure \', \'Comment 11: VehicleTicket \', \'Comment 12: VehicleTicketEntity \', \'Comment 13: ResolutionContext )   --- End of inner exception stack trace ---   at lambda_method9444(Closure \', \'Comment 14: VehicleTicket \', \'Comment 15: VehicleTicketEntity \', \'Comment 16: ResolutionContext )   --- End of inner exception stack trace ---   at lambda_method9444(Closure \', \'Comment 17: VehicleTicket \', \'Comment 18: VehicleTicketEntity \', \'Comment 19: ResolutionContext )   at lambda_method9446(Closure \', \'Comment 20: Object \', \'Comment 21: Object \', \'Comment 22: ResolutionContext )   at Kotrak.Extensions.Mapping.CompositeMapper.Mapper.Execute(Object source\', \'Comment 23: Object destination\', \'Comment 24: ICustomInjection[] customInjections\', \'Comment 25: Type sourceType\', \'Comment 26: Type targetType)   at Kotrak.Extensions.Mapping.CompositeMapper.Mapper.Map[TSource,TTarget](TSource source\', \'Comment 27: TTarget destination)   at Plant.VC.BusinessLogic.Infrastructure.Persistance.BaseVcAggregateRootRepository`2.MapAggregateToEntity(TAggregateRoot aggregateRoot\', \'Comment 28: TEntity entity) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\67ba263564c33499\\\\\\\\Plant.VC.BusinessLogic\\\\\\\\Plant.VC.BusinessLogic.Infrastructure.Persistance\\\\\\\\BaseVcAggregateRootRepository.cs:line 26   at Kotrak.Common.Infrastructure.Persistence.Repositories.AggregateRootRepository`2.Persist(TAggregateRoot root)   at Plant.VC.BusinessLogic.Application.VehicleTickets.Services.VehicleTicketService.CancelVehicleTicket(AggregateId vehicleTicketId\', \'Comment 29: AggregateId reactionReasonId) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\67ba263564c33499\\\\\\\\Plant.VC.BusinessLogic\\\\\\\\Plant.VC.BusinessLogic.Application\\\\\\\\VehicleTickets\\\\\\\\Services\\\\\\\\VehicleTicketService.cs:line 575   at Plant.VC.BusinessLogic.Application.VehicleTickets.CommandHandlers.CancelVehicleTicketCommandHandler.Handle(CancelVehicleTicketCommand command) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\67ba263564c33499\\\\\\\\Plant.VC.BusinessLogic\\\\\\\\Plant.VC.BusinessLogic.Application\\\\\\\\VehicleTickets\\\\\\\\CommandHandlers\\\\\\\\CancelVehicleTicketCommandHandler.cs:line 25   at Kotrak.Common.Infrastructure.Gate.CommandEnvironment.Run[TCommand](TCommand command)   at Castle.DynamicProxy.AbstractInvocation.Proceed()   at Kotrak.Common.Infrastructure.Interceptors.LoggingInterceptor`1.Intercept(IInvocation invocation)   at Castle.DynamicProxy.AbstractInvocation.Proceed()   at Kotrak.Common.Infrastructure.Gate.Filters.CommandProcessFilter`1.Execute(CommandPipelineContext`1 input)   at Kotrak.Extensions.Pipeline.PredefinedFilters.FilterDecorator`1.Execute(TContext input)   at Kotrak.Extensions.Pipeline.Pipeline`1.Execute(T input)   at Kotrak.Common.Infrastructure.Gate.StandardGate.DispatchCommand[TCommand](TCommand command)   at Plant.VC.BusinessLogic.Infrastructure.Api.Controllers.VehicleTicketController.Cancel(CancelVehicleTicketViewModel viewModel) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\67ba263564c33499\\\\\\\\Plant.VC.BusinessLogic\\\\\\\\Plant.VC.BusinessLogic.Infrastructure.Api\\\\\\\\Controllers\\\\\\\\VehicleTicketController.cs:line 685   at lambda_method19667(Closure \', \'Comment 30: Object \', \'Comment 31: Object[] )   at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor.SyncActionResultExecutor.Execute(IActionResultTypeMapper mapper\', \'Comment 32: ObjectMethodExecutor executor\', \'Comment 33: Object controller\', \'Comment 34: Object[] arguments)   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeActionMethodAsync()   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next\', \'Comment 35: Scope& scope\', \'Comment 36: Object& state\', \'Comment 37: 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 38: Scope& scope\', \'Comment 39: Object& state\', \'Comment 40: 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 41: Task lastTask\', \'Comment 42: State next\', \'Comment 43: Scope scope\', \'Comment 44: Object state\', \'Comment 45: Boolean isCompleted)   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker\', \'Comment 46: Task task\', \'Comment 47: IDisposable scope)   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker\', \'Comment 48: Task task\', \'Comment 49: IDisposable scope)   at Microsoft.AspNetCore.Routing.EndpointMiddleware.<Invoke>g__AwaitRequestTask|6_0(Endpoint endpoint\', \'Comment 50: Task requestTask\', \'Comment 51: ILogger logger)   at Swashbuckle.AspNetCore.SwaggerUI.SwaggerUIMiddleware.Invoke(HttpContext httpContext)   at Swashbuckle.AspNetCore.Swagger.SwaggerMiddleware.Invoke(HttpContext httpContext\', ""Comment 52: ISwaggerProvider swaggerProvider)   at Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware.Invoke(HttpContext httpContext){code}\'"", ""Comment 53: \'{code:java}2023-03-27 12:47:32 (0883486c-2a82-4344-8613-d7185eeba8cc/Plant.VC.BusinessLogic/DHVD01AP184/3312/14) [Error] Kotrak.Common.Infrastructure.ICommandRunEnvironment - Error during Void Run[CancelVehicleTicketCommand](Plant.VC.BusinessLogic.Application.Interfaces.VehicleTickets.Commands.CancelVehicleTicketCommand) methodAutoMapper.AutoMapperMappingException: Error mapping types.Mapping types:VehicleTicket -> VehicleTicketEntityPlant.VC.BusinessLogic.Domain.VehicleTickets.VehicleTicket -> Plant.VC.BusinessLogic.Infrastructure.Persistance.VehicleTickets.VehicleTicketEntityType Map configuration:VehicleTicket -> VehicleTicketEntityPlant.VC.BusinessLogic.Domain.VehicleTickets.VehicleTicket -> Plant.VC.BusinessLogic.Infrastructure.Persistance.VehicleTickets.VehicleTicketEntityDestination Member:BulkIntakeElements ---> AutoMapper.AutoMapperMappingException: Error mapping types.Mapping types:VehicleTicketBulkIntakeElement -> VehicleTicketBulkIntakeElementEntityPlant.VC.BusinessLogic.Domain.VehicleTickets.VehicleTicketBulkIntakeElement -> Plant.VC.BusinessLogic.Infrastructure.Persistance.VehicleTickets.VehicleTicketBulkIntakeElementEntityType Map configuration:VehicleTicketBulkIntakeElement -> VehicleTicketBulkIntakeElementEntityPlant.VC.BusinessLogic.Domain.VehicleTickets.VehicleTicketBulkIntakeElement -> Plant.VC.BusinessLogic.Infrastructure.Persistance.VehicleTickets.VehicleTicketBulkIntakeElementEntityDestination Member:WeightValue ---> System.ArgumentException: Unit mismatch   at Kotrak.Common.SharedKernel.Quantity.ToCommonUnit(Quantity x1"", \'Comment 54: Quantity x2)   at Plant.VC.BusinessLogic.Domain.VehicleTickets.VehicleTicketBulkIntakeElement.get_Weight() in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\67ba263564c33499\\\\\\\\Plant.VC.BusinessLogic\\\\\\\\Plant.VC.BusinessLogic.Domain\\\\\\\\VehicleTickets\\\\\\\\VehicleTicketBulkIntakeElement.cs:line 32   at lambda_method9444(Closure \', \'Comment 55: VehicleTicket \', \'Comment 56: VehicleTicketEntity \', \'Comment 57: ResolutionContext )   --- End of inner exception stack trace ---   at lambda_method9444(Closure \', \'Comment 58: VehicleTicket \', \'Comment 59: VehicleTicketEntity \', \'Comment 60: ResolutionContext )   --- End of inner exception stack trace ---   at lambda_method9444(Closure \', \'Comment 61: VehicleTicket \', \'Comment 62: VehicleTicketEntity \', \'Comment 63: ResolutionContext )   at lambda_method9446(Closure \', \'Comment 64: Object \', \'Comment 65: Object \', \'Comment 66: ResolutionContext )   at Kotrak.Extensions.Mapping.CompositeMapper.Mapper.Execute(Object source\', \'Comment 67: Object destination\', \'Comment 68: ICustomInjection[] customInjections\', \'Comment 69: Type sourceType\', \'Comment 70: Type targetType)   at Kotrak.Extensions.Mapping.CompositeMapper.Mapper.Map[TSource,TTarget](TSource source\', \'Comment 71: TTarget destination)   at Plant.VC.BusinessLogic.Infrastructure.Persistance.BaseVcAggregateRootRepository`2.MapAggregateToEntity(TAggregateRoot aggregateRoot\', \'Comment 72: TEntity entity) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\67ba263564c33499\\\\\\\\Plant.VC.BusinessLogic\\\\\\\\Plant.VC.BusinessLogic.Infrastructure.Persistance\\\\\\\\BaseVcAggregateRootRepository.cs:line 26   at Kotrak.Common.Infrastructure.Persistence.Repositories.AggregateRootRepository`2.Persist(TAggregateRoot root)   at Plant.VC.BusinessLogic.Application.VehicleTickets.Services.VehicleTicketService.CancelVehicleTicket(AggregateId vehicleTicketId\', \'Comment 73: AggregateId reactionReasonId) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\67ba263564c33499\\\\\\\\Plant.VC.BusinessLogic\\\\\\\\Plant.VC.BusinessLogic.Application\\\\\\\\VehicleTickets\\\\\\\\Services\\\\\\\\VehicleTicketService.cs:line 575   at Plant.VC.BusinessLogic.Application.VehicleTickets.CommandHandlers.CancelVehicleTicketCommandHandler.Handle(CancelVehicleTicketCommand command) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\67ba263564c33499\\\\\\\\Plant.VC.BusinessLogic\\\\\\\\Plant.VC.BusinessLogic.Application\\\\\\\\VehicleTickets\\\\\\\\CommandHandlers\\\\\\\\CancelVehicleTicketCommandHandler.cs:line 25   at Kotrak.Common.Infrastructure.Gate.CommandEnvironment.Run[TCommand](TCommand command)   at Castle.DynamicProxy.AbstractInvocation.Proceed()   at Kotrak.Common.Infrastructure.Interceptors.LoggingInterceptor`1.Intercept(IInvocation invocation)2023-03-27 12:47:32 (/Plant.VC.BusinessLogic/DHVD01AP184/3312/14) [Error] Serilog.AspNetCore.RequestLoggingMiddleware - HTTP ""POST"" ""/api/VehicleTicket/cancelVehicleTicket"" responded 500 in 123.7748 ms{code}\\\'\', ""Comment 74: \'Hi Thomas,VT 481/3/23 has been cancelled. Please"", ""Comment 75: let me know if this is fine and we can close both tasks.Regards\'"", ""Comment 76: \'Thanks you can close this\'"", ""Comment 77: \'Thank you.\']""]\nRelated Issues:\n[\'DGS-8773\']\n\n### End'}"
201,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8831\n\n### Instruction:\nDear\r\n\r\nPlease help to check VT-1134/3/23 in Hai Phong Plant.\r\nVT was closed , WO/WD was executed but still not released out of stock.\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: \'Aktualnie WO(PD)-508/3/23  58aa0821-5ede-4d3a-b186-5980f3f8bca0 jest executed przy resend jest błąd z uwagi na status: !screenshot-1! !image-2023-03-28-11-40-54-453!\'"", ""Comment 4: \'Hi!Please update information about this case. \'"", ""Comment 5: \' !screenshot-2! \'"", ""Comment 6: \'Hello"", \'Comment 7: data has been corrected. I do not see any more such cases. As to the reason we can create a RCA - if it is to be create\', ""Comment 8: please confirm. Thank you.\'"", ""Comment 9: \'this corrected from DB level? and may we solve it by ourself?\'"", ""Comment 10: \'Hi"", ""Comment 11: unfortunately before re-sending the message from the application level the status of WO and WD documents had to be changed due to the fact that they were already executed(from database level).\'"", ""Comment 12: \'There is GDC-849(concurrency mechanism).It should help to process the document from two sources / e.g. by two operators.Can we close this task?\']""]\nRelated Issues:\n[]\n\n### End'}"
202,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8830\n\n### Instruction:\nGood morning, there are many production reports pending in status ""In Progress"". Can you check what is the problem, please? Is it on PCS side (then I will report to PCS Supplier) or is it a DHP problem, or the communication/integration. Or is it a user oversight? I asked them to check, but so far not feedback. Many of the pending reports are from January and February, what looks strange.... Please call me, when you pick up the ticket. \n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'hi"", ""Comment 4: please do not investigate further. there was an issue of the operators. problem solved. please close the ticket\'"", ""Comment 5: \'Thank you.\']""]\nRelated Issues:\n[]\n\n### End'}"
203,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8829\n\n### Instruction:\nDear ,\r\n\r\nPlease help to check this issue in Hai Phong 2 plant (0436) . PLR 4361240323076 receipt both bulk and batch.\r\n\n\n### Response:\n[""Comment 1: [\'!image!!image-1!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'!image-2023-03-27-10-39-37-615.png|width=839,height=409!!image-2023-03-27-10-40-38-917.png|width=822,height=434!\'"", ""Comment 4: \'!image-2023-03-27-10-42-07-074.png|width=1319,height=637!\'"", ""Comment 5: \'!image-2023-03-27-10-52-14-706.png!\'"", ""Comment 6: \'Tylko StockUnit jest podwójny"", \'Comment 7: wygląda na to\', ""Comment 8: że user się pomylił!image-2023-03-27-11-09-26-800.png!!image-2023-03-27-10-55-33-572.png!!image-2023-03-27-11-09-26-800!\'"", ""Comment 9: \'WI jest w statusie executed!image-2023-03-27-12-04-05-981.png!\'"", \'Comment 10: ""Dokument WI- został utworzony na kod\\\'436-W0066U\\\' z id \\\'C77860F2-4B48-4DB2-BD5B-8FCD0D316D99\\\' zaraz po tym jak kod\\\'436-S00AZ6\\\' z id \\\'59917A9E-8C85-4BA6-BDC3-31FF086157F4\\\' wpadł w status released!image-2023-03-27-12-09-53-627.png!!image-2023-03-27-12-13-50-716.png!""\', \'Comment 11: ""{code:java}/****** Script for SelectTopNRows command from SSMS  ******/SELECT *  FROM [DHPlantWmsBusinessLogicMain].[dbo].[WarehouseIntakes] where document = \\\'WI-991/3/23\\\'  SELECT *  FROM [DHPlantWmsBusinessLogicMain].[dbo].[WarehouseIntakeElements] where SerialNumber = \\\'4361240323076\\\'SELECT       [Created]      ,[AggregateId]      ,[Event]      ,[EventType]            ,[UserName]        FROM [DHPlantWmsBusinessLogicEvents].[dbo].[WarehouseIntakes] where AggregateId = \\\'AEC402CF-2DAA-4FB6-9D95-D3222F2F9C61\\\' order by Created desc{code}{code:java}SELECT *  FROM [DHPlantWmsBusinessLogicMain].[dbo].[WarehouseIntakes] where document = \\\'WI-991/3/23\\\'  SELECT *  FROM [DHPlantWmsBusinessLogicMain].[dbo].[WarehouseIntakeElements] where SerialNumber = \\\'4361240323076\\\'{code}{code:java}SELECT       [AggregateId]      ,[Event]      ,[EventType]      ,[Created]      ,[UserName]        FROM [DHPlantStockBusinessLogicEvents].[dbo].[StockUnits] where AggregateId in (\\\'59917A9E-8C85-4BA6-BDC3-31FF086157F4\\\',\\\'C77860F2-4B48-4DB2-BD5B-8FCD0D316D99\\\') order by Created desc  \\\'436-S00AZ6\\\' - \\\'59917A9E-8C85-4BA6-BDC3-31FF086157F4\\\'  \\\'436-W0066U\\\' - \\\'C77860F2-4B48-4DB2-BD5B-8FCD0D316D99\\\'{code}{code:java}/****** Script for SelectTopNRows command from SSMS  ******/SELECT *  FROM [DHPlantStockBusinessLogicMain].[dbo].[ProductionLots] where LotNumber = \\\'4361240323076\\\'  SELECT *  FROM [DHPlantStockBusinessLogicMain].[dbo].[StockUnits] where barcode in (\\\'436-S00AZ6\\\'\', ""Comment 12: \'436-W0066U\')  SELECT *  FROM [DHPlantWmsBusinessLogicMain].[dbo].[UnitLoads] where barcode in (\'436-S00AZ6\'"", \'Comment 13: \\\'436-W0066U\\\')  SELECT *  FROM [DHPlantStockBusinessLogicMain].[dbo].[Deliveries] where SourceDocumentId = \\\'100EAEBE-E269-455E-A25B-0E4F56ED2FF5\\\'{code}""\', ""Comment 14: \'Piotrek G. sugeruje"", \'Comment 15: że to może być coś podobnego\', ""Comment 16: ale nie jestem pewnahttps://helpdesk.kotrak.com/browse/GDC-849\'"", ""Comment 17: \'Hi!Please update information about this case. \'"", ""Comment 18: \'Cześć,Proszę o konsultację:Wygląda"", \'Comment 19: jakby user się pomylił\', \'Comment 20: ale czy ktoś z Dev jest w stanie potwierdzić\', \'Comment 21: że tak mogło być? Podwójny jest tylko stock unit\', ""Comment 22: reszta nie ma dubla. Lub ewentualnie czy to nie jest kejs z tego GDC https://helpdesk.kotrak.com/browse/GDC-849 ? !https://statics.teams.cdn.office.net/evergreen-assets/personal-expressions/v2/assets/emoticons/smile/default/30_f.png?v=v81|width=20!\'"", ""Comment 23: \'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 24: \'hi,tomorrow will stock count. so please give us result and solution today.should put it in P1 now\'"", ""Comment 25: \'Hello"", ""Comment 26: the priority has been changed - we are working on it.We will reply as soon as possible.\'"", \'Comment 27: ""In P1 task\\\'s we have focused on clearingandunblocking the process.When it comes to duplicate stocks an inventory should be made.To investigate the reasonof the issue I will create (RCA)task for you.""\', ""Comment 28: \'DGS-8872 RCA has been created.As for the stock unit batch has already been sold"", ""Comment 29: should we corrected bulk one?\'"", \'Comment 30: ""Yes\', \'Comment 31: you \\\'re should correct bulk .""\', ""Comment 32: \'Stock Unit has been corrected to full release to 0kg.\'"", ""Comment 33: \'Hello . Thank you and please help close this ticket .\']""]\nRelated Issues:\n[\'DGS-8872\']\n\n### End'}"
204,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8828\n\n### Instruction:\nRecipe version 2 of product 140510 is not loaded in DHP and not sent to the PCS. The recipe does exists in DHC also as production recipe. Also in the communication log DHC says it is succesfully exported.\r\n\r\nPlease check why this recipe is not loaded in DHP and fix it ASAP as the factory must produce this feed early in the morning.\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 2: ""item 140510 also doesn\\\'t exist in Meppel. I have resent it from ERP\', \'Comment 3: but I don\\\'t see it in DHP yet""\', ""Comment 4: \'Recipe 140510 version 2 is avaible inMeppel DHP.!image-2023-03-24-21-21-58-671.png!Please check and let me know if i can close this ticket.\'"", \'Comment 5: ""Yes\', \'Comment 6: it\\\'s there now. What did you do the load the item and recipe?""\', ""Comment 7: \'I had to make some changes in database then I synchronised Item from DHH as well as recipe and production recipe from DHC.\'"", ""Comment 8: \'Thank you. What did you have to change? And in which database?\'"", ""Comment 9: \'There was an issue in DHC database with disallows to properly synchronized DHHItem between both DHC databases. I had to fix that first.\'"", ""Comment 10: \'Thanks for your support\'"", ""Comment 11: \'Could you please confirm if we can close this task?Regards\'"", ""Comment 12: \'The issue has been fixed on our side. Please"", ""Comment 13: verify if it is working fine for you and let us know if we can close this task.Regards\'"", ""Comment 14: \'This task can be closed\']""]\nRelated Issues:\n[]\n\n### End'}"
205,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8827\n\n### Instruction:\nHi\r\n\r\nBased on issue reported in DGS-8774, we need some workaround for it.\r\nCould you please prepare a job to clean old data in Events database?\r\nAll Events db in all plants with DHP 3.0.\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: \' !TO_DB-server_040402023! \'"", ""Comment 3: \'Changes done by Ludemila now: Local Disc E: 300GB\'"", ""Comment 4: \'Only a remark: the fix requested in this task is not only for Toledo"", ""Comment 5: but for all DB servers from other plants.Thank you\'"", ""Comment 6: \'Toledo"", ""Comment 7: 12.04.2023. Dodany timoutDo sprawdzenie za tydzień jak wygląda sytuacja z Events. !image-2023-04-12-14-09-04-782!\'"", ""Comment 8: \'Zmiana na niedzielę rano!image-2023-04-12-14-10-17-677!\'"", ""Comment 9: \'Dodanie timeout"", \'Comment 10: TOTrzeba dodać na innych bazach które mają największy przyrost na Events czy Intercontex\', ""Comment 11: oraz na innych fabrykach!image-2023-04-12-14-10-36-253!\'"", ""Comment 12: \'Przykład RC"", ""Comment 13: 12.04.2023!image-2023-04-12-14-11-43-861!\'"", ""Comment 14: \'Hello [~marcin.kleszcz@kotrak.com][~maciej.dobrzanski@kotrak.com]Could you please accelerate the process at least for Rio Claro.We are running out of space.This is very critical.Thank you\']""]\nRelated Issues:\n[\'DAP-13463\', \'DGS-8774\']\n\n### End'}"
206,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8826\n\n### Instruction:\nRecipe arrived in DHH. Can you check? It is urgent\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Thanks"", ""Comment 3: according to przemyslaw.przybyszewski@kotrak.com this is a issue: !image!\'"", ""Comment 4: \'do zamknięcia"", ""Comment 5: naprawiłem im to\'"", ""Comment 6: \'ok\']""]\nRelated Issues:\n[]\n\n### End'}"
207,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8825\n\n### Instruction:\nHi,\r\n\r\nThese orders are in DHC but not coming through to DHP:\r\n- SO000087783\r\n- SO000088096\r\n- SO000088094 \r\n\r\nThere is also the case that some PCS suppliers were informing us this morning that DHP servers were generating a \'500\' (internal error). This happens quite often. Is this somthing that is already known to you? \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: \'Dear Theo,We have already received task for Helmond underDGS-8824. Please"", ""Comment 3: let us know if we can proceed underDGS-8824 and closeDGS-8825.Best Regards\'"", ""Comment 4: \'I have restarted application pools"", ""Comment 5: orders seem to be arriving:!image-2023-03-24-11-53-12-707.png!!image-2023-03-24-11-53-34-648.png!!image-2023-03-24-11-53-57-164.png!\'"", ""Comment 6: \'Hi Aleksandra"", ""Comment 7: yes please close the task. It was duplicated\'"", ""Comment 8: \'No it is resolved also :)Thank you\'"", ""Comment 9: \'!image-2023-03-30-14-24-16-991.png!\']""]\nRelated Issues:\n[]\n\n### End'}"
208,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8824\n\n### Instruction:\nDHP Helmond does not receive orders of today. \r\n\r\nWeb UI is working fine, but communication doesn\'t. I have restarted IIS services, but that did not help.  \r\n\r\nCan you please check?\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'I have restarted application pools. Please"", ""Comment 3: check if missing Orders are arriving.Regards\'"", \'Comment 4: ""Yes\', ""Comment 5: they are. That\'s great"", \'Comment 6: thanks.I restarted IIS too\', \'Comment 7: by using that button. Was that not sufficient? !afbeelding!""\', ""Comment 8: \'I have restarted application pools with a script in PowerShell. I think IT department should have this procedure :)Option from your screenshot not always is sufficient.Regards\'"", ""Comment 9: \'Can you share that script with me please?\'"", ""Comment 10: \'[~marek.mamcarz@kotrak.com] możecie podać im tą instrukcję"", ""Comment 11: która była też dla RPA do restartowania tych pooli? Oni tego nie mają?\'"", ""Comment 12: \'In this task we have focused on clearingandunblocking the process. In order to get instruction"", ""Comment 13: please contact Project Manager - Marek Mamcarz.Regards\'"", ""Comment 14: \'Ok"", ""Comment 15: done! You can close this ticket.\'"", ""Comment 16: \'Thank you\'"", ""Comment 17: \'!image-2023-03-30-14-23-40-753.png!\']""]\nRelated Issues:\n[]\n\n### End'}"
209,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8823\n\n### Instruction:\nEven after re-sending the weights from PCS they don\'t arrive in DHP Utrecht.\r\nFor other orders everything is fully functional.\r\n\r\nSO000085033 and SO000087488.\r\n\r\nThey need the documents urgently.\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Can I get a detailed information what is not actuall"", ""Comment 3: is it about weights for VT based on orders?\'"", ""Comment 4: \'!image!\'"", ""Comment 5: \'they need the weights for the packing slip\'"", ""Comment 6: \'The checked field will have a value when the related VT documents will be closed.\'"", ""Comment 7: \'I asked the factory ppl. to do that\'"", ""Comment 8: \'CBK Utrecht commented:And how do we close it ? \'"", ""Comment 9: \'In the VT list select close"", ""Comment 10: !screenshot-2! but the stock for one item is missing. !screenshot-1! \'"", ""Comment 11: \'OK"", \'Comment 12: thank you for the support\', ""Comment 13: a packing slip is now generated.The ticket can be closed.\'"", ""Comment 14: \'Thank you for confirmation.\']""]\nRelated Issues:\n[]\n\n### End'}"
210,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8822\n\n### Instruction:\nDHP Premix does not start well. At first is starts very very slow, windows stays mostly blank, and the when it shows the application icons, the icons do not respond.\r\n\r\nI have restarted the application server, but that did not help.\r\n\r\nPlease check, thanks!\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: \'Po IP wpuściło"", ""Comment 4: po nazwie komunikat poniżej:!image-2023-03-24-08-48-50-533.png!\'"", ""Comment 5: \'DB server!image-2023-03-24-08-55-31-669.png!\'"", ""Comment 6: \'Dear Martijn,I think it should be fine now. Previously I have received error about issue with database"", \'Comment 7: few minutes later\', ""Comment 8: it was fine / recovered.Please verify!image-2023-03-24-08-57-50-888.png!Regards\'"", ""Comment 9: \'It is"", \'Comment 10: thanks! I have asked Valid about what happened to the databaseserver.There is one thing left\', ""Comment 11: I was told (shortly after 9 AM) an order was not yet arrived in DHP. But perhaps that needed some extra time?\'"", ""Comment 12: \'Thank you. According to DB"", \'Comment 13: please let me know if you managed to resolve the issue with Valid. Regarding the order\', \'Comment 14: we can wait a bit more\', \'Comment 15: but\', ""Comment 16: in order to verify I would need a document number.Regards\'"", ""Comment 17: \'Order is still not there: number is 450/03\'"", ""Comment 18: \'Additionally"", ""Comment 19: data entered in DHP does not arrive in PCS.Seems like DHP does not communicate yet with other applications?\'"", ""Comment 20: \'We have restarted services. Now we should wait a bit fo documents to sync.Please let us know in some time if documents arrived. Additionaly"", \'Comment 21: Orde450/03\', ""Comment 22: is it sales or purchase?Regards\'"", ""Comment 23: \'It is a Sales Order. It has not arrived yet.\'"", ""Comment 24: \'!image-2023-03-24-10-28-16-410.png!\'"", ""Comment 25: \'Could you please restart DHCService Service on DHP side?!image-2023-03-24-10-40-33-735.png!\'"", ""Comment 26: \'We managed to restart. No need on your side. Order in plant now!image-2023-03-24-10-52-20-320.png!\'"", \'Comment 27: ""Thanks\', \'Comment 28: order is there. Only communication with PCS is lacking\', \'Comment 29: we\\\'re looking into that with PCS supplier.""\', ""Comment 30: \'Please"", ""Comment 31: let us know if we can close this taskRegards\'"", ""Comment 32: \'PCS received the last data yesterday at 21:50. Nothing after that. Can you please check the communication with PCS from DHP side?\'"", ""Comment 33: \'We have restarted one more service"", ""Comment 34: please contact and check with PCS provider.Regards\'"", ""Comment 35: \' !screenshot-1! !image-2023-03-24-12-00-24-533! !image-2023-03-24-12-00-42-811!\'"", ""Comment 36: \'Fixed"", ""Comment 37: thanks. Which service was that?You can then close the ticket.\'"", ""Comment 38: \'Exchange Synchronisation Service.Regards\']""]\nRelated Issues:\n[]\n\n### End'}"
211,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8821\n\n### Instruction:\nwe have problem to register production for item SUN0896-T-S30, lot number, 0891140323030, we registered 5 unit loads, but in WMS order, we have only 3, and if we try to register again the barcode or new barcode, system shows an error message.\r\n\r\nBarcodes available in PLR but missing in WO(IP)-502/3/23:\r\n89-W00G6P\r\n89-W00G7C\r\n\r\nwe need to move urgent these barcodes, but system not allow. Could you fix WO(IP) and WMS/Stock?\r\n\r\nThank you\r\n\r\n\r\n\r\n\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'[~piotr.gaczorek@kotrak.com],Niestety ale brakuje nam logów. Mianowicie ktoś wyczyścił logi w WMS (te tekstowe) z 16.03. Z racji braków tych logów nie jestesmy w stanie na 100% potwierdzić przyczyny"", ""Comment 3: jednak wygląda na to że poleciał timeout podczas komunikacji miedzy WMS a Stock. Zostało to zmienione w wersji 8.6 (DAP-13378). tam ten timeout będzie można konfigurować.Na chwile obecną prosze uzywajcie skryptów do naprawy podanych w komentarzu: https://helpdesk.kotrak.com/browse/DGS-8808?focusedCommentId=1115392&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-1115392\'"", ""Comment 4: \'Hello"", ""Comment 5: after the changes in version 8.6 the problem should not occur. The theme of the changes is manageable response time between modules.Regards.\'"", \'Comment 6: ""Ok\', \'Comment 7: we\\\'ll wait new version to test.""\', ""Comment 8: \'This ticket has been closed.\']""]\nRelated Issues:\n[\'DGS-8778\', \'DAP-13378\', \'DGS-8808\']\n\n### End'}"
212,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8820\n\n### Instruction:\nHi\r\n\r\nWe have a Production recipe for GCN1392-T, version 1.0. However this version is not in DHP. Only version 0.0\r\n\r\nWhen we generate the subversion, then both version 1.0 and 1.1 goes to DHP.\r\nWe have another case too: GCN1390-T\r\n\r\nThis is happening to often. Could you please investigate why is this happening?\r\n\r\nThank you very much\n\n### Response:\n[""Comment 1: [\'!image-1!!image-2!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Hi,Can you please check the connection?Regards !image-2023-03-27-14-31-29-105.png!!image-2023-03-27-14-31-29-105!\'"", ""Comment 4: \'!image-2023-03-27-14-51-29-079.png!\'"", \'Comment 5: ""{code:java}/****** Script for SelectTopNRows command from SSMS  ******/SELECT *  FROM [Evolution_DHCountry].[dbo].[Recipes] where DhhItemId = \\\'CB95D066-CAC9-4D09-AC49-66D6F0230CD7\\\'  SELECT *  FROM [Evolution_DHCountry].[dbo].[Items] where code = \\\'GCN1390-T\\\'     SELECT *  FROM [Evolution_DHCountry].[dbo].[Technologies] where ProductionRecipeId = \\\'188F177F-AA5C-4B61-82FF-9369E84F26A9\\\'  SELECT *  FROM [Evolution_DHCountry].[dbo].[ProductionRecipes] where RecipeId = \\\'966E5367-3D54-4CF0-ADE0-4F761877EB54\\\'    SELECT *  FROM [Evolution_DHCService].[dbo].[TechnologyExportInfoes] where entityid in (  \\\'7B488436-1C85-4B09-B761-BD23C104E48B\\\',\\\'1A00AF93-0A40-4865-B8A3-CA7B79002CD3\\\'){code}""\', ""Comment 6: \'Hi [~lalmeida1@deheus.com]Could you please help Aleksandra on their access to the server?Thank you\'"", ""Comment 7: \'Hi! Done"", ""Comment 8: please test and let me know. Thanks\'"", ""Comment 9: \'Hi Maicon,We investigatedGCN1390-T. The issue is caused that Technology did not arrive do DHC Service. Subversion does not matter.I have resent technology and now it dropped. Please provide us a fresh example if possible.Regards\'"", \'Comment 10: ""Hi AleksandraNow GCN1390-T is there. thank you very much!Is there any reason why Technology didn\\\'t arrived to DHC Service?Factory reported this isn\\\'t the first case.Thank you""\', ""Comment 11: \'Hi,We need to have new example to investigate to confirm or deny our suspicions. Please"", \'Comment 12: ask factory to let you know when new case appear\', ""Comment 13: then we check it in this ask.Regards\'"", \'Comment 14: ""Hi AleksandraWe have new recipe with same situation: GCN1392-TI\\\'d like to add that DHCService is having some issues that you can check in other tasks\', \'Comment 15: like DGS-8776. In this case\', \'Comment 16: the Order was integrate to DHC one date\', \'Comment 17: and DHCService only registered it after we resend it from ERP.Thank you""\', \'Comment 18: ""I\\\'ve just clicked on Sync button for Recipes and Technologies for GCN1392-T because we needed to plan the production. And now\', \'Comment 19: the recipe is in the DHP3.0""\', ""Comment 20: \'Understood. If there will be a new case that does not require immediate processing and we can investigate under db"", ""Comment 21: I would be thankful.Regards :)\'"", \'Comment 22: ""HiWe have new case:* GCN1356-T-S30 didn\\\'t integrate to DHP of GuararapesThank you""\', ""Comment 23: \'Thank you\'"", ""Comment 24: \'Zaakceptowana 24 marca!image-2023-03-29-14-21-28-155.png!Production Recipe i Techno też są w DHC!image-2023-03-29-14-22-05-514.png!\'"", ""Comment 25: \'DHC:!image-2023-03-29-15-29-29-130.png!Service:!image-2023-03-29-15-29-55-692.png!Mapowanie:!image-2023-03-29-15-30-16-705.png!\'"", ""Comment 26: \'!image-2023-03-29-15-32-20-223.png!\'"", \'Comment 27: ""{code:java}SELECT * FROM [Evolution_DHCountry].[dbo].[Items] where DhhItemId in ( \\\'D409897A-A8E8-4084-8103-2BFA187D039F\\\'\', ""Comment 28: \'A7459878-B373-40C3-9165-F6E65B9574AF\'"", ""Comment 29: \'3316E2C5-72DC-4D45-AAF0-EE4D37CB8BA5\'"", ""Comment 30: \'42C5C97B-30A7-4698-8C93-73C6874B5051\'"", ""Comment 31: \'4740C3FE-ACC9-490C-90D9-4AEEB0CD8F5C\'"", ""Comment 32: \'2E5C2A8C-B01A-49B0-96D5-21FA6307365F\'"", ""Comment 33: \'480AA444-A51A-4E9F-9B9D-EA9C0A8C1ED4\'"", ""Comment 34: \'4CAF3583-D328-47C9-AC43-0097F3F2C6E0\'"", ""Comment 35: \'B8F61A34-AB49-4748-8D54-02230BC793A2\'"", ""Comment 36: \'C15AA2F7-3809-49D2-8CF9-256CFD9ADC06\'"", ""Comment 37: \'E9DD115F-DC93-4BE7-8901-6EE9991C538D\'"", ""Comment 38: \'4B7F36D8-FAF5-4CE4-B57D-F08E55133ADF\'"", ""Comment 39: \'29360B29-2184-4497-9C24-0081BA7E613A\'"", ""Comment 40: \'C27EECA7-8B4B-4B08-8C32-E3E7CD0B95E3\'"", ""Comment 41: \'DF41D07C-4985-4347-8EAB-64FCF7E8D7B0\'"", ""Comment 42: \'3692D1A7-0AB3-448E-92DB-A213F94BC501\'"", \'Comment 43: \\\'FF6B51D0-0027-471C-8B60-DEAB121F1B70\\\'){code}{code:java}SELECT *  FROM [Evolution_DHCountry].[dbo].[RecipeIngredients] where RecipeId = \\\'4155330F-0CC6-4F01-91D6-B5EA2D54807A\\\'{code}""\', \'Comment 44: \\\'Błąd z communication errors:{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_Recipes_Items_ItemId"". The conflict occurred in database ""DHPlantProdBusinessLogicMain""\', \'Comment 45: table ""dbo.Items""\', ""Comment 46: column \\\\\'Id\\\\\'.The statement has been terminated.{code}\'"", ""Comment 47: \'Boldem - składniki receptury z DHC"", \'Comment 48: ponieważ szukałam po DHHItem id\', \'Comment 49: więc były też inne. Wyglada na to\', ""Comment 50: że wszystkie itemy receptury są w planciePSIODO-B-S25*PSIODO-B**22016*-21034-PET-*21034*21034-MP*21175*-21175-MP-*21232**01978**21496**PSCON-CA-B*PSCON-CA-B-S20-21150-MP-*21150**21432*-21432-PET-21432-MP*21434**21372*-21372-PET-*21657**21333**21450**PSCOBAL-B*PSCOBAL-B-S25*21403*-21403-PET--21403-MP-\'"", \'Comment 51: \\\'W errorach{code:java}{""Id"":{""Id"":""67182ce5-ea4f-4795-9fda-210c106ed6c2""},""PlantId"":85,""ItemId"":{""Id"":""f6d92d69-d6db-456c-b69c-2596f82deac3""},""Version"":1,""SubVersion"":0,""PlantVersion"":0,""Value"":999.999995,""Unit"":""kg"",""Date"":""2023-03-24T14:02:38.24"",""Name"":""Fct:GU Cd:GCN1356-T Ver:0001 Date:3/24/2023"",""Coefficient"":0.0,""InclusionRate"":2.000000,""PercentageInComplement"":0.000000,""ProductSpecification"":null,""ContaminationCode"":null,""ExpirationPeriod"":180,""LabelTemplateId"":null,""LabelTemplateValue"":null,""OrderId"":null,""OrderElementNo"":null,""IsProductDefinition"":false,""IsBlockedForProduction"":false,""Ingredients"":[{""ElementNo"":1,""ItemId"":{""Id"":""e6693988-921d-489d-b9c6-f988f3d3f2b6""},""Value"":8.857142,""Unit"":""kg"",""PercentValue"":0.0,""IsSpecial"":false,""ScaleNumber"":1},{""ElementNo"":2,""ItemId"":{""Id"":""8c188fb1-4b2f-4a83-88da-0feb670b052a""},""Value"":3.140000,""Unit"":""kg"",""PercentValue"":0.0,""IsSpecial"":false,""ScaleNumber"":1},{""ElementNo"":3,""ItemId"":{""Id"":""625e705e-5326-4777-a279-275afa25ddba""},""Value"":126.670000,""Unit"":""kg"",""PercentValue"":0.0,""IsSpecial"":false,""ScaleNumber"":0},{""ElementNo"":4,""ItemId"":{""Id"":""a9083f5d-7235-4af6-9786-d1f078679dd9""},""Value"":0.255681,""Unit"":""kg"",""PercentValue"":0.0,""IsSpecial"":false,""ScaleNumber"":1},{""ElementNo"":5,""ItemId"":{""Id"":""0a7117d2-af9d-49de-bea8-eac393a15cf2""},""Value"":3.500000,""Unit"":""kg"",""PercentValue"":0.0,""IsSpecial"":false,""ScaleNumber"":1},{""ElementNo"":6,""ItemId"":{""Id"":""b87d7a51-449a-4acd-97a2-71859d0b3ff3""},""Value"":4.000000,""Unit"":""kg"",""PercentValue"":0.0,""IsSpecial"":false,""ScaleNumber"":1},{""ElementNo"":7,""ItemId"":{""Id"":""00fd40a9-033f-4cc7-a4a1-d1e0065ee3ca""},""Value"":0.139999,""Unit"":""kg"",""PercentValue"":0.0,""IsSpecial"":false,""ScaleNumber"":1},{""ElementNo"":8,""ItemId"":{""Id"":""eaa674c1-b274-4a02-8c4f-5a61b36a04a0""},""Value"":62.300000,""Unit"":""kg"",""PercentValue"":0.0,""IsSpecial"":false,""ScaleNumber"":1},{""ElementNo"":9,""ItemId"":{""Id"":""6f69291c-cb4a-44a7-8c3b-cabab71b2b9e""},""Value"":34.000000,""Unit"":""pcs"",""PercentValue"":0.0,""IsSpecial"":false,""ScaleNumber"":2},{""ElementNo"":10,""ItemId"":{""Id"":""2f85f44e-6c0e-4ee2-982e-31da1a537953""},""Value"":99.591550,""Unit"":""kg"",""PercentValue"":0.0,""IsSpecial"":false,""ScaleNumber"":0},{""ElementNo"":11,""ItemId"":{""Id"":""e974107c-5a6a-44ba-a5b7-5e36ea17e4e3""},""Value"":2.572727,""Unit"":""kg"",""PercentValue"":0.0,""IsSpecial"":false,""ScaleNumber"":1},{""ElementNo"":12,""ItemId"":{""Id"":""3756ce79-13e9-475f-a62e-e7aa356ab670""},""Value"":47.190167,""Unit"":""kg"",""PercentValue"":0.0,""IsSpecial"":false,""ScaleNumber"":1},{""ElementNo"":13,""ItemId"":{""Id"":""0755348d-3ed0-40eb-9088-d1dd7210a820""},""Value"":101.600000,""Unit"":""kg"",""PercentValue"":0.0,""IsSpecial"":false,""ScaleNumber"":1},{""ElementNo"":14,""ItemId"":{""Id"":""a2d0c549-07f0-4ed6-97d7-5c7e49c35318""},""Value"":2.560000,""Unit"":""kg"",""PercentValue"":0.0,""IsSpecial"":false,""ScaleNumber"":1},{""ElementNo"":15,""ItemId"":{""Id"":""54caaf24-ea3c-4653-8ce5-d611097db088""},""Value"":21.062000,""Unit"":""kg"",""PercentValue"":0.0,""IsSpecial"":false,""ScaleNumber"":1},{""ElementNo"":16,""ItemId"":{""Id"":""d8f36ac7-aec0-4cb9-8733-7b3de3bb664d""},""Value"":515.527396,""Unit"":""kg"",""PercentValue"":0.0,""IsSpecial"":false,""ScaleNumber"":0},{""ElementNo"":17,""ItemId"":{""Id"":""9890bb44-0e7e-4acb-aab8-2dedb1b28ffd""},""Value"":0.200000,""Unit"":""kg"",""PercentValue"":0.0,""IsSpecial"":false,""ScaleNumber"":1},{""ElementNo"":18,""ItemId"":{""Id"":""47a39a59-2d1e-4029-87f7-05f10646addb""},""Value"":0.833333,""Unit"":""kg"",""PercentValue"":0.0,""IsSpecial"":false,""ScaleNumber"":1}],""Nutrients"":[{""LaboratoryUnitId"":{""Id"":""ee58eb07-2e32-4a25-ad18-82e42ed865bb""},""NutrientId"":{""Id"":""811a6b3f-15a2-45cb-9f07-4c2834e4b76d""},""ExpectedValue"":88.252810,""TolerancePositiveWarning"":null,""ToleranceNegativeWarning"":null,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""ee58eb07-2e32-4a25-ad18-82e42ed865bb""},""NutrientId"":{""Id"":""ed17cb17-00ce-4677-a2cb-e816a1e5e6c6""},""ExpectedValue"":2.051509,""TolerancePositiveWarning"":null,""ToleranceNegativeWarning"":null,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""ee58eb07-2e32-4a25-ad18-82e42ed865bb""},""NutrientId"":{""Id"":""69912a95-ee17-435d-9403-3fb452cc1a17""},""ExpectedValue"":0.312490,""TolerancePositiveWarning"":null,""ToleranceNegativeWarning"":null,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""ee58eb07-2e32-4a25-ad18-82e42ed865bb""},""NutrientId"":{""Id"":""061fab34-4aa8-45ef-a0f5-71877451a6b7""},""ExpectedValue"":0.004512,""TolerancePositiveWarning"":null,""ToleranceNegativeWarning"":null,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""f43d93e8-a525-4af9-8098-d87d9de0fb0a""},""NutrientId"":{""Id"":""2b61052f-27f5-4d05-aa28-f7767745a9e7""},""ExpectedValue"":1537.021000,""TolerancePositiveWarning"":1690.723100,""ToleranceNegativeWarning"":1383.318900,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""ee58eb07-2e32-4a25-ad18-82e42ed865bb""},""NutrientId"":{""Id"":""3bba30d5-e79f-4e8a-9d1a-006e369b1b7c""},""ExpectedValue"":21.682880,""TolerancePositiveWarning"":null,""ToleranceNegativeWarning"":null,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""ee58eb07-2e32-4a25-ad18-82e42ed865bb""},""NutrientId"":{""Id"":""42183c24-41fd-4107-bd0a-bcff5e5532ca""},""ExpectedValue"":88.252810,""TolerancePositiveWarning"":null,""ToleranceNegativeWarning"":null,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""dddb23d0-a2e5-4fa4-a8ca-c65236e9220e""},""NutrientId"":{""Id"":""c65c7cee-39bd-4780-b5d8-911cfadd1c2e""},""ExpectedValue"":44.047010,""TolerancePositiveWarning"":null,""ToleranceNegativeWarning"":null,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""ee58eb07-2e32-4a25-ad18-82e42ed865bb""},""NutrientId"":{""Id"":""aaa470e6-9b70-48f6-a68f-327ec3dc5df4""},""ExpectedValue"":9.853322,""TolerancePositiveWarning"":9.953322,""ToleranceNegativeWarning"":9.753322,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""ee58eb07-2e32-4a25-ad18-82e42ed865bb""},""NutrientId"":{""Id"":""6d0f1ed2-5ae7-4fbc-820b-b8723eec4453""},""ExpectedValue"":0.420846,""TolerancePositiveWarning"":null,""ToleranceNegativeWarning"":null,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""ee58eb07-2e32-4a25-ad18-82e42ed865bb""},""NutrientId"":{""Id"":""29b2b775-d4e0-44a6-a47d-6684d18d0c24""},""ExpectedValue"":0.002828,""TolerancePositiveWarning"":null,""ToleranceNegativeWarning"":null,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""ee58eb07-2e32-4a25-ad18-82e42ed865bb""},""NutrientId"":{""Id"":""3cf1cdb8-0d32-4ca6-a462-a3371a1632bb""},""ExpectedValue"":1.052114,""TolerancePositiveWarning"":null,""ToleranceNegativeWarning"":null,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""f43d93e8-a525-4af9-8098-d87d9de0fb0a""},""NutrientId"":{""Id"":""90f65b37-d495-41d5-b2b6-718c0a1f6e28""},""ExpectedValue"":31.500000,""TolerancePositiveWarning"":null,""ToleranceNegativeWarning"":null,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""0e70a8ef-c88e-46ea-94c9-c7225ee3e59b""},""NutrientId"":{""Id"":""4bb8145e-7b52-4104-835a-39af307be92f""},""ExpectedValue"":0.940102,""TolerancePositiveWarning"":null,""ToleranceNegativeWarning"":null,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""7336bf72-ba50-4630-9690-fb989580be8e""},""NutrientId"":{""Id"":""5cd08288-11f2-4528-a893-bf169bbc1eab""},""ExpectedValue"":142.344100,""TolerancePositiveWarning"":null,""ToleranceNegativeWarning"":null,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""ee58eb07-2e32-4a25-ad18-82e42ed865bb""},""NutrientId"":{""Id"":""60408dd3-908d-48ec-894f-7229825cb49f""},""ExpectedValue"":2.051509,""TolerancePositiveWarning"":null,""ToleranceNegativeWarning"":null,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""f43d93e8-a525-4af9-8098-d87d9de0fb0a""},""NutrientId"":{""Id"":""3d0bfa81-082b-41ee-b03d-4bf109c8130a""},""ExpectedValue"":35.000000,""TolerancePositiveWarning"":null,""ToleranceNegativeWarning"":null,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""f43d93e8-a525-4af9-8098-d87d9de0fb0a""},""NutrientId"":{""Id"":""2024a529-4768-47c0-a58c-7c3f1de6a9ab""},""ExpectedValue"":14.000000,""TolerancePositiveWarning"":null,""ToleranceNegativeWarning"":null,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""f43d93e8-a525-4af9-8098-d87d9de0fb0a""},""NutrientId"":{""Id"":""ad9ff8ea-94cf-4a0e-946c-79b8524cd206""},""ExpectedValue"":17.000000,""TolerancePositiveWarning"":null,""ToleranceNegativeWarning"":null,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""ee58eb07-2e32-4a25-ad18-82e42ed865bb""},""NutrientId"":{""Id"":""13b46662-c20d-4d02-8839-6a9ca73e1f69""},""ExpectedValue"":0.000760,""TolerancePositiveWarning"":null,""ToleranceNegativeWarning"":null,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""ee58eb07-2e32-4a25-ad18-82e42ed865bb""},""NutrientId"":{""Id"":""467af9fd-d30e-4b6a-9c94-638f4626495e""},""ExpectedValue"":0.312490,""TolerancePositiveWarning"":null,""ToleranceNegativeWarning"":null,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""ee58eb07-2e32-4a25-ad18-82e42ed865bb""},""NutrientId"":{""Id"":""4231ba4a-df0a-486b-8b55-616da763c772""},""ExpectedValue"":0.132385,""TolerancePositiveWarning"":null,""ToleranceNegativeWarning"":null,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""ee58eb07-2e32-4a25-ad18-82e42ed865bb""},""NutrientId"":{""Id"":""f48a389e-d0a8-4e3a-839f-f325c37e1611""},""ExpectedValue"":0.000595,""TolerancePositiveWarning"":null,""ToleranceNegativeWarning"":null,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""dddb23d0-a2e5-4fa4-a8ca-c65236e9220e""},""NutrientId"":{""Id"":""1e5a70e5-9061-4ad9-87b1-97bd54a566ee""},""ExpectedValue"":38.388230,""TolerancePositiveWarning"":null,""ToleranceNegativeWarning"":null,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""ee58eb07-2e32-4a25-ad18-82e42ed865bb""},""NutrientId"":{""Id"":""727d1a59-fc42-4ab3-82d0-2792a31ee832""},""ExpectedValue"":0.000760,""TolerancePositiveWarning"":null,""ToleranceNegativeWarning"":null,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""ee58eb07-2e32-4a25-ad18-82e42ed865bb""},""NutrientId"":{""Id"":""e83533f0-ef20-484f-9920-adc636b7ed31""},""ExpectedValue"":3.200400,""TolerancePositiveWarning"":null,""ToleranceNegativeWarning"":null,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""ee58eb07-2e32-4a25-ad18-82e42ed865bb""},""NutrientId"":{""Id"":""96cc57d1-70f7-4e41-a47f-5f2893527c81""},""ExpectedValue"":20.002500,""TolerancePositiveWarning"":null,""ToleranceNegativeWarning"":null,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""f43d93e8-a525-4af9-8098-d87d9de0fb0a""},""NutrientId"":{""Id"":""b8456ad4-8599-48ea-aeda-a51c720b213d""},""ExpectedValue"":1415.000000,""TolerancePositiveWarning"":null,""ToleranceNegativeWarning"":null,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""ee58eb07-2e32-4a25-ad18-82e42ed865bb""},""NutrientId"":{""Id"":""68df8894-de78-47ae-8b19-98c47a730585""},""ExpectedValue"":0.113135,""TolerancePositiveWarning"":null,""ToleranceNegativeWarning"":null,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""ee58eb07-2e32-4a25-ad18-82e42ed865bb""},""NutrientId"":{""Id"":""5130f52d-386d-4f4e-91a6-607ef7b91ead""},""ExpectedValue"":0.003574,""TolerancePositiveWarning"":null,""ToleranceNegativeWarning"":null,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""f43d93e8-a525-4af9-8098-d87d9de0fb0a""},""NutrientId"":{""Id"":""cc3b7849-3fba-4d02-bcae-7f13d8226b69""},""ExpectedValue"":3100.000000,""TolerancePositiveWarning"":null,""ToleranceNegativeWarning"":null,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""68daa379-a660-40bd-b060-88dea14e8d85""},""NutrientId"":{""Id"":""644be01c-0ac4-4314-bd03-9a229544e140""},""ExpectedValue"":0.587898,""TolerancePositiveWarning"":null,""ToleranceNegativeWarning"":null,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""08d8a79e-2e49-48ca-b11b-b4b6721cc4ff""},""NutrientId"":{""Id"":""357f79c1-8c54-44b5-9d6a-386d09fc02bf""},""ExpectedValue"":0.877111,""TolerancePositiveWarning"":null,""ToleranceNegativeWarning"":null,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""ee58eb07-2e32-4a25-ad18-82e42ed865bb""},""NutrientId"":{""Id"":""c85590e5-c72e-40a0-98e3-fb38d34ec681""},""ExpectedValue"":1.404519,""TolerancePositiveWarning"":2.404519,""ToleranceNegativeWarning"":0.404519,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""ee58eb07-2e32-4a25-ad18-82e42ed865bb""},""NutrientId"":{""Id"":""94379a84-d23a-4ff3-8776-4793c898fa39""},""ExpectedValue"":2.000001,""TolerancePositiveWarning"":null,""ToleranceNegativeWarning"":null,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""f43d93e8-a525-4af9-8098-d87d9de0fb0a""},""NutrientId"":{""Id"":""b6e74369-a46c-4252-b192-389f352f8a34""},""ExpectedValue"":1415.000000,""TolerancePositiveWarning"":null,""ToleranceNegativeWarning"":null,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""f43d93e8-a525-4af9-8098-d87d9de0fb0a""},""NutrientId"":{""Id"":""67ebd482-b4dd-41f6-ae9b-4f362f7354b3""},""ExpectedValue"":1018.024000,""TolerancePositiveWarning"":null,""ToleranceNegativeWarning"":null,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""ee58eb07-2e32-4a25-ad18-82e42ed865bb""},""NutrientId"":{""Id"":""1fd51bcc-ada5-4acf-a66a-03165bb1b6d2""},""ExpectedValue"":1.404525,""TolerancePositiveWarning"":2.404525,""ToleranceNegativeWarning"":0.404525,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""ee58eb07-2e32-4a25-ad18-82e42ed865bb""},""NutrientId"":{""Id"":""47d3420c-9016-410b-8b61-cf8b0a175a33""},""ExpectedValue"":4.999844,""TolerancePositiveWarning"":5.099844,""ToleranceNegativeWarning"":4.899844,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""ee58eb07-2e32-4a25-ad18-82e42ed865bb""},""NutrientId"":{""Id"":""6fbb0227-bd0a-471f-a4e6-4167654d5143""},""ExpectedValue"":2.500002,""TolerancePositiveWarning"":null,""ToleranceNegativeWarning"":null,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""f43d93e8-a525-4af9-8098-d87d9de0fb0a""},""NutrientId"":{""Id"":""7b41f1cf-4e9e-4eec-a6c7-7851e07284ce""},""ExpectedValue"":35.000000,""TolerancePositiveWarning"":null,""ToleranceNegativeWarning"":null,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""ee58eb07-2e32-4a25-ad18-82e42ed865bb""},""NutrientId"":{""Id"":""40476cf3-0ccf-4136-8fbf-8f5abe205b68""},""ExpectedValue"":1.404525,""TolerancePositiveWarning"":2.404525,""ToleranceNegativeWarning"":0.404525,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""ee58eb07-2e32-4a25-ad18-82e42ed865bb""},""NutrientId"":{""Id"":""a47e31da-2462-46d6-91e2-5b7f9b895632""},""ExpectedValue"":0.007966,""TolerancePositiveWarning"":null,""ToleranceNegativeWarning"":null,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""ee58eb07-2e32-4a25-ad18-82e42ed865bb""},""NutrientId"":{""Id"":""d181ace7-ae56-442a-8b16-d4c73d774bcb""},""ExpectedValue"":0.000518,""TolerancePositiveWarning"":null,""ToleranceNegativeWarning"":null,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""ee58eb07-2e32-4a25-ad18-82e42ed865bb""},""NutrientId"":{""Id"":""b5697752-083b-4668-9b03-8ace7c0cb16c""},""ExpectedValue"":21.376550,""TolerancePositiveWarning"":22.876550,""ToleranceNegativeWarning"":19.876550,""TolerancePositiveError"":24.376550,""ToleranceNegativeError"":18.376550},{""LaboratoryUnitId"":{""Id"":""ee58eb07-2e32-4a25-ad18-82e42ed865bb""},""NutrientId"":{""Id"":""226286ef-506c-45a1-8ed5-faf1287e2951""},""ExpectedValue"":2.000046,""TolerancePositiveWarning"":null,""ToleranceNegativeWarning"":null,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""f43d93e8-a525-4af9-8098-d87d9de0fb0a""},""NutrientId"":{""Id"":""30cbcb74-c6ed-4aa1-bd76-513bc81b24cb""},""ExpectedValue"":14.000000,""TolerancePositiveWarning"":null,""ToleranceNegativeWarning"":null,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""ee58eb07-2e32-4a25-ad18-82e42ed865bb""},""NutrientId"":{""Id"":""2b74443e-49cd-434e-bc71-1b5c8eaec732""},""ExpectedValue"":21.682880,""TolerancePositiveWarning"":null,""ToleranceNegativeWarning"":null,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""ee58eb07-2e32-4a25-ad18-82e42ed865bb""},""NutrientId"":{""Id"":""2a79c8a0-96ef-4ae5-9bc0-786aeb35cb48""},""ExpectedValue"":0.312490,""TolerancePositiveWarning"":null,""ToleranceNegativeWarning"":null,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""ee58eb07-2e32-4a25-ad18-82e42ed865bb""},""NutrientId"":{""Id"":""2acbad34-773a-41cf-92c9-b844aee6459f""},""ExpectedValue"":0.001673,""TolerancePositiveWarning"":null,""ToleranceNegativeWarning"":null,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""ee58eb07-2e32-4a25-ad18-82e42ed865bb""},""NutrientId"":{""Id"":""5e5aaa9a-e95d-48bf-89cb-89f1ee3875ad""},""ExpectedValue"":0.002828,""TolerancePositiveWarning"":null,""ToleranceNegativeWarning"":null,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""ee58eb07-2e32-4a25-ad18-82e42ed865bb""},""NutrientId"":{""Id"":""28bcc3e7-f8ed-44c8-a00c-059464f332d4""},""ExpectedValue"":1.404525,""TolerancePositiveWarning"":2.404525,""ToleranceNegativeWarning"":0.404525,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""f43d93e8-a525-4af9-8098-d87d9de0fb0a""},""NutrientId"":{""Id"":""acd8181a-37b0-4921-97ff-3b2730466c91""},""ExpectedValue"":35.000000,""TolerancePositiveWarning"":null,""ToleranceNegativeWarning"":null,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""ee58eb07-2e32-4a25-ad18-82e42ed865bb""},""NutrientId"":{""Id"":""0aede4ce-93c3-4ccc-850d-95a4c56df510""},""ExpectedValue"":0.304800,""TolerancePositiveWarning"":null,""ToleranceNegativeWarning"":null,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""f43d93e8-a525-4af9-8098-d87d9de0fb0a""},""NutrientId"":{""Id"":""8c2435f4-f429-4d45-8663-c5826185d49f""},""ExpectedValue"":16.000000,""TolerancePositiveWarning"":null,""ToleranceNegativeWarning"":null,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""ee58eb07-2e32-4a25-ad18-82e42ed865bb""},""NutrientId"":{""Id"":""12b65d3f-a499-4812-be02-1a27f2acc560""},""ExpectedValue"":98.595470,""TolerancePositiveWarning"":null,""ToleranceNegativeWarning"":null,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""ee58eb07-2e32-4a25-ad18-82e42ed865bb""},""NutrientId"":{""Id"":""79798089-874d-4eb8-9f72-0291c4609f20""},""ExpectedValue"":21.376550,""TolerancePositiveWarning"":22.876550,""ToleranceNegativeWarning"":19.876550,""TolerancePositiveError"":24.376550,""ToleranceNegativeError"":18.376550},{""LaboratoryUnitId"":{""Id"":""ee58eb07-2e32-4a25-ad18-82e42ed865bb""},""NutrientId"":{""Id"":""c7317392-014b-4a34-b9b4-f84da6ff6441""},""ExpectedValue"":0.312490,""TolerancePositiveWarning"":null,""ToleranceNegativeWarning"":null,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""f43d93e8-a525-4af9-8098-d87d9de0fb0a""},""NutrientId"":{""Id"":""784e8af7-645d-42a5-82b1-ad7928218a58""},""ExpectedValue"":3100.000000,""TolerancePositiveWarning"":null,""ToleranceNegativeWarning"":null,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""ee58eb07-2e32-4a25-ad18-82e42ed865bb""},""NutrientId"":{""Id"":""8d0c1c9f-fb56-4bfa-a24c-dd708e7292b0""},""ExpectedValue"":0.343599,""TolerancePositiveWarning"":null,""ToleranceNegativeWarning"":null,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""ee58eb07-2e32-4a25-ad18-82e42ed865bb""},""NutrientId"":{""Id"":""47efec3c-04e0-4a69-b3ef-398db5a5836f""},""ExpectedValue"":0.001673,""TolerancePositiveWarning"":null,""ToleranceNegativeWarning"":null,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""ee58eb07-2e32-4a25-ad18-82e42ed865bb""},""NutrientId"":{""Id"":""77019b1a-b3b7-4eb4-8b8d-205b10ec4721""},""ExpectedValue"":0.200787,""TolerancePositiveWarning"":null,""ToleranceNegativeWarning"":null,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""ee58eb07-2e32-4a25-ad18-82e42ed865bb""},""NutrientId"":{""Id"":""83e99aaa-b618-4dce-bb8f-a8cb98b06640""},""ExpectedValue"":21.376550,""TolerancePositiveWarning"":22.876550,""ToleranceNegativeWarning"":19.876550,""TolerancePositiveError"":24.376550,""ToleranceNegativeError"":18.376550},{""LaboratoryUnitId"":{""Id"":""ee58eb07-2e32-4a25-ad18-82e42ed865bb""},""NutrientId"":{""Id"":""811dd25c-5f1c-471c-a27e-1f656754aa36""},""ExpectedValue"":9.853322,""TolerancePositiveWarning"":9.953322,""ToleranceNegativeWarning"":9.753322,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""ee58eb07-2e32-4a25-ad18-82e42ed865bb""},""NutrientId"":{""Id"":""256182ad-dab7-4cd7-aa02-fbebf40be5d2""},""ExpectedValue"":0.000400,""TolerancePositiveWarning"":null,""ToleranceNegativeWarning"":null,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""ee58eb07-2e32-4a25-ad18-82e42ed865bb""},""NutrientId"":{""Id"":""cdda334e-e008-4417-900e-df18effcc034""},""ExpectedValue"":2.500002,""TolerancePositiveWarning"":null,""ToleranceNegativeWarning"":null,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""ee58eb07-2e32-4a25-ad18-82e42ed865bb""},""NutrientId"":{""Id"":""8092a0fd-53ff-4a2e-a1b6-230bc51c83c3""},""ExpectedValue"":1.404525,""TolerancePositiveWarning"":2.404525,""ToleranceNegativeWarning"":0.404525,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""ee58eb07-2e32-4a25-ad18-82e42ed865bb""},""NutrientId"":{""Id"":""74921a3f-b52f-4c32-b230-a239e862fcba""},""ExpectedValue"":6.878320,""TolerancePositiveWarning"":null,""ToleranceNegativeWarning"":null,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""f43d93e8-a525-4af9-8098-d87d9de0fb0a""},""NutrientId"":{""Id"":""b1910eba-bac1-4dc3-879a-1993b754fb54""},""ExpectedValue"":700.000000,""TolerancePositiveWarning"":null,""ToleranceNegativeWarning"":null,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""ee58eb07-2e32-4a25-ad18-82e42ed865bb""},""NutrientId"":{""Id"":""912e3dde-1df4-4844-8f7d-5a1d8000ccd4""},""ExpectedValue"":21.376550,""TolerancePositiveWarning"":22.876550,""ToleranceNegativeWarning"":19.876550,""TolerancePositiveError"":24.376550,""ToleranceNegativeError"":18.376550},{""LaboratoryUnitId"":{""Id"":""ee58eb07-2e32-4a25-ad18-82e42ed865bb""},""NutrientId"":{""Id"":""5a6d014d-64a6-436b-868a-30f45adb860b""},""ExpectedValue"":1.930400,""TolerancePositiveWarning"":null,""ToleranceNegativeWarning"":null,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""ee58eb07-2e32-4a25-ad18-82e42ed865bb""},""NutrientId"":{""Id"":""e4d4afcf-287f-4564-8ba5-fb2a23e0877a""},""ExpectedValue"":0.000518,""TolerancePositiveWarning"":null,""ToleranceNegativeWarning"":null,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""ee58eb07-2e32-4a25-ad18-82e42ed865bb""},""NutrientId"":{""Id"":""8ab208eb-903d-42c6-86fe-a58f49e4cae5""},""ExpectedValue"":0.010160,""TolerancePositiveWarning"":null,""ToleranceNegativeWarning"":null,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""f43d93e8-a525-4af9-8098-d87d9de0fb0a""},""NutrientId"":{""Id"":""7b4ada03-00c0-4730-a029-7253ea852849""},""ExpectedValue"":1570.000000,""TolerancePositiveWarning"":null,""ToleranceNegativeWarning"":null,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""ee58eb07-2e32-4a25-ad18-82e42ed865bb""},""NutrientId"":{""Id"":""32149206-4dda-46c2-b270-3d89aeacc748""},""ExpectedValue"":0.000595,""TolerancePositiveWarning"":null,""ToleranceNegativeWarning"":null,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""f43d93e8-a525-4af9-8098-d87d9de0fb0a""},""NutrientId"":{""Id"":""cdfbeb28-3c5c-4b2d-804e-94d70656db4b""},""ExpectedValue"":640.000000,""TolerancePositiveWarning"":null,""ToleranceNegativeWarning"":null,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""ee58eb07-2e32-4a25-ad18-82e42ed865bb""},""NutrientId"":{""Id"":""ad2bee28-26e4-4c1e-8697-88d88dee710e""},""ExpectedValue"":0.001593,""TolerancePositiveWarning"":null,""ToleranceNegativeWarning"":null,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""f43d93e8-a525-4af9-8098-d87d9de0fb0a""},""NutrientId"":{""Id"":""e8e9df8e-d549-40b6-a231-12321d1120ea""},""ExpectedValue"":1570.000000,""TolerancePositiveWarning"":null,""ToleranceNegativeWarning"":null,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""ee58eb07-2e32-4a25-ad18-82e42ed865bb""},""NutrientId"":{""Id"":""7b5b85df-3b99-45cc-97c4-fd98a901aba5""},""ExpectedValue"":0.132385,""TolerancePositiveWarning"":null,""ToleranceNegativeWarning"":null,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""ee58eb07-2e32-4a25-ad18-82e42ed865bb""},""NutrientId"":{""Id"":""baae9262-75f3-4b21-a72c-e6bb57cfb9a7""},""ExpectedValue"":0.001593,""TolerancePositiveWarning"":null,""ToleranceNegativeWarning"":null,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""ee58eb07-2e32-4a25-ad18-82e42ed865bb""},""NutrientId"":{""Id"":""77c947a3-c7f9-4f21-b842-1e4a2db37810""},""ExpectedValue"":19.304000,""TolerancePositiveWarning"":null,""ToleranceNegativeWarning"":null,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""ee58eb07-2e32-4a25-ad18-82e42ed865bb""},""NutrientId"":{""Id"":""4622d602-f089-46c6-92cf-42808fd111d1""},""ExpectedValue"":3.607138,""TolerancePositiveWarning"":null,""ToleranceNegativeWarning"":null,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""f43d93e8-a525-4af9-8098-d87d9de0fb0a""},""NutrientId"":{""Id"":""4660b946-4a73-4e41-9629-7f2e129b6ca7""},""ExpectedValue"":19.400000,""TolerancePositiveWarning"":null,""ToleranceNegativeWarning"":null,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""f43d93e8-a525-4af9-8098-d87d9de0fb0a""},""NutrientId"":{""Id"":""82f4c0f8-e02e-40b5-ad4c-e0c7a5fe31ec""},""ExpectedValue"":31.500000,""TolerancePositiveWarning"":null,""ToleranceNegativeWarning"":null,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""f43d93e8-a525-4af9-8098-d87d9de0fb0a""},""NutrientId"":{""Id"":""e0bc88f8-42a3-4ca9-8426-1452a1c908bb""},""ExpectedValue"":14.000000,""TolerancePositiveWarning"":null,""ToleranceNegativeWarning"":null,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""f43d93e8-a525-4af9-8098-d87d9de0fb0a""},""NutrientId"":{""Id"":""8ce1e194-226b-4b7b-bbdd-b0c0a0921ef4""},""ExpectedValue"":640.000000,""TolerancePositiveWarning"":null,""ToleranceNegativeWarning"":null,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""ee58eb07-2e32-4a25-ad18-82e42ed865bb""},""NutrientId"":{""Id"":""5b6b3fb9-b826-4318-b8d0-853d5e330e8e""},""ExpectedValue"":2.000001,""TolerancePositiveWarning"":null,""ToleranceNegativeWarning"":null,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""ee58eb07-2e32-4a25-ad18-82e42ed865bb""},""NutrientId"":{""Id"":""f142b253-b802-4aa8-b5aa-1687e7bdc45d""},""ExpectedValue"":1.404525,""TolerancePositiveWarning"":2.404525,""ToleranceNegativeWarning"":0.404525,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""f43d93e8-a525-4af9-8098-d87d9de0fb0a""},""NutrientId"":{""Id"":""569162ae-e548-4f27-93ba-4bd564502166""},""ExpectedValue"":31.500000,""TolerancePositiveWarning"":null,""ToleranceNegativeWarning"":null,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""ee58eb07-2e32-4a25-ad18-82e42ed865bb""},""NutrientId"":{""Id"":""2111054c-b512-4c1a-a46e-24b0cb1f51aa""},""ExpectedValue"":0.002000,""TolerancePositiveWarning"":null,""ToleranceNegativeWarning"":null,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""f43d93e8-a525-4af9-8098-d87d9de0fb0a""},""NutrientId"":{""Id"":""fb3eb6a5-1da9-43bb-9e64-e8694b4906cd""},""ExpectedValue"":3121.523000,""TolerancePositiveWarning"":3433.675300,""ToleranceNegativeWarning"":2809.370700,""TolerancePositiveError"":null,""ToleranceNegativeError"":null},{""LaboratoryUnitId"":{""Id"":""f43d93e8-a525-4af9-8098-d87d9de0fb0a""},""NutrientId"":{""Id"":""08499628-7f09-4482-aead-9ea962631030""},""ExpectedValue"":670.800500,""TolerancePositiveWarning"":737.880550,""ToleranceNegativeWarning"":603.720450,""TolerancePositiveError"":null,""ToleranceNegativeError"":null}],""ContaminationNorms"":[],""ContaminationGroupIds"":[]}{code}{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_Recipes_Items_ItemId"". The conflict occurred in database ""DHPlantProdBusinessLogicMain""\', \'Comment 52: table ""dbo.Items""\', ""Comment 53: column \\\\\'Id\\\\\'.The statement has been terminated.{code}\'"", ""Comment 54: \'Hi,I have resent this recipe. And it is in plant now.!image-2023-03-29-17-24-52-540.png!I have collected some data. But still I need to have internal consultation on it.Regards\'"", \'Comment 55: ""Hi AleksandraThank you very much!We are very worried about this. We don\\\'t know if the new versions in DHC are integrating to DHP. New versions have new raw materials or new dosing values\', \'Comment 56: this can impact in the quality of our final products.Could you please put this task on a priority list? Thank you very much!""\', ""Comment 57: \'[~maciej.dobrzanski@kotrak.com]Przemek mówił"", \'Comment 58: że przeanalizował to z grubsza i mówi\', \'Comment 59: żeproblem jest w samym module produkcji i że pewnie nie dojdziemy do tego czemu nie było jakiś itemów na moment synchronizacji technologii no i w związku z tym potrzebujemy kogoś z planta najlepiej od produkcji\', ""Comment 60: Miałbyś kogoś? :P\'"", ""Comment 61: \'Hi Maicon,Please be informed that we have forwarded the issue to the development team in order to internal analysis.We are waiting for more details and will be back with further information as soon as possible.Regards\'"", ""Comment 62: \'[~aleksandra.przybylek@kotrak.com] a sprawdzaliście czy były jakieś błędy w DHP odnośnie problemów zapisu z item lub czy był on już przynajmniej zmapowany? A jaka byłą data export date? Może podczas uruchamiania DHP ten item nie został w ogóle wysłany?\'"", \'Comment 63: \\\'Dla receptur:GCN1356-T-S30{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_RecipeElements_Items_ItemId"". The conflict occurred in database ""DHPlantProdBusinessLogicMain""\', \'Comment 64: table ""dbo.Items""\', \'Comment 65: column \\\\\\\'Id\\\\\\\'.The statement has been terminated.{code}{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_Recipes_Items_ItemId"". The conflict occurred in database ""DHPlantProdBusinessLogicMain""\', \'Comment 66: table ""dbo.Items""\', \'Comment 67: column \\\\\\\'Id\\\\\\\'. The statement has been terminated.{code}GCN1390-T{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_Recipes_Items_ItemId"". The conflict occurred in database ""DHPlantProdBusinessLogicMain""\', \'Comment 68: table ""dbo.Items""\', \'Comment 69: column \\\\\\\'Id\\\\\\\'.The statement has been terminated.{code}{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_RecipeElements_Items_ItemId"". The conflict occurred in database ""DHPlantProdBusinessLogicMain""\', \'Comment 70: table ""dbo.Items""\', ""Comment 71: column \\\\\'Id\\\\\'.The statement has been terminated.{code}GCN1392-Tbłędów brak!image-2023-03-31-14-01-30-248.png!\'"", ""Comment 72: \'hej,spędziłem z Łukaszem i Michalem sporo czasu i niestety nie udało nam sie w 100% potwierdzić teorii.dodałem kolumne która pomoże nam pomóc w analizie nowego przypadku !newcolumn! Prześlijcie ponownie brakujące receptury i napiszcie do klienta że mamy dodatkowy tracing i niech zgłosi nowy przypadek jak zaistnieje\'"", ""Comment 73: \'Dear Maicon,We have additional tracing which should help us to verify issue. If new example appears"", ""Comment 74: please let us know and provide Recipe / ItemRegards\'"", ""Comment 75: \'tak"", \'Comment 76: te receptury\', \'Comment 77: które podał\', ""Comment 78: przesłaliśmy już wcześniej\'"", \'Comment 79: ""Hi [~Aleksandra.Przybylek@kotrak.com]I\\\'m receiving DHC notifications.If we have new cases I\\\'ll report to you.Thank you very much""\', ""Comment 80: \'Hi [~mberbert@deheus.com],I will put this task on hold untill new example arrive.Regards\'"", \'Comment 81: ""Hi [~@kotrak.com]We have new case for Rio Claro:# POP5390-T-S30# SUN7835-T-S20I raised new DGS-8967 because it\\\'s critical and we you asked another case to analyse.Thank you""\', ""Comment 82: \'Wpadło do tej tabeli ale to o to chodzi?!image-2023-04-13-17-51-16-394.png!\'"", \'Comment 83: ""{code:java}SELECT TOP 1000 [PlantId]      ,[LongId]      ,[StringId]      ,[GuidId]      ,[PlantIdNo]      ,[MappedDate]  FROM [DHPlantIntegrationDhcServiceIdentityMapping].[dbo].[ItemIdentityMappings] where PlantId in (  \\\'345CDE15-0B48-4598-BE69-0B3118FE9568\\\',\\\'0B586455-1136-4A86-ABB9-F0A161C063A9\\\'){code}{code:java}SELECT TOP 1000 [Id] ,[Code] ,[Name] ,[ItemType] ,[ItemForm] ,[PackingForm] ,[ItemBaseWeight] ,[ItemBaseWeightUnit] ,[IsMedicated] ,[BulkProductId] ,[IsArchived] ,[AnimalGroup] ,[ReworkItemId] ,[ProductGroup] ,[IsBlockedForProduction] ,[SettlementType] FROM [DHPlantProdBusinessLogicMain].[dbo].[Items] where code in ( \\\'POP5390-T-S30\\\'\', \'Comment 84: \\\'SUN7835-T-S20\\\'){code}""\', ""Comment 85: \'Hi [~mberbert@deheus.com],We have raised RCA task for this issue under DGS-8985 as this is reoccuring issue. Please"", ""Comment 86: let us know if you have access.Regards\'"", ""Comment 87: \'Hi[~mberbert@deheus.com],We have raised RCA task for this issue underDGS-8985as this is reoccuring issue. Please"", ""Comment 88: let us know if you have access.Regards\']""]\nRelated Issues:\n[\'DGS-8985\', \'DGS-8967\']\n\n### End'}"
213,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8819\n\n### Instruction:\nHi\r\n\r\nWe have around 2 thousand items that we need to insert Additional technologies to them.\r\nWe have an Excel file with the main item and its additional technologies with their quantities.\r\n\r\nCould you please estimate a task to:\r\n# Create Additional technologies base on a Excel file\r\n# Generate new subversion for these items\r\n# Generate technologies for this new subversion\r\n# Sync these new subversions/technologies to DHP\r\n# Sync these new subversions/technologies to ERP\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: \'Cześć [~przemyslaw.przybyszewski@kotrak.com]czy da się jakoś sprytnie dodać te dane? Jesteś w stanie Ty albo ktoś ogarnąć jakiś skrypt i /lub wycenić prośbę Maicona? :)\'"", ""Comment 3: \'mamy już importer który dodaje nam additional technologies z excela"", \'Comment 4: tylko musi być on utworzony w odpowiednim formacie. musieli by przesłać swojego excela w celu weryfikacji danych\', ""Comment 5: z reguły takie rzeczy robiliśmy przy uruchamianiu fabryki wiec subwersje nie były potrzebne. Jak podeślą dane to zweryfikujemy i wycenimy.\'"", ""Comment 6: \'ok"", ""Comment 7: dzięki :)\'"", ""Comment 8: \'Dear Maicon,Could you please send us excel file with your requested data so that we could verify the issue and to estimate your request?Regards\'"", \'Comment 9: ""Hi AleksandraI don\\\'t know if this is the file layout you need\', \'Comment 10: but here goes the excel file with some examples for the Packaging technoligies.Thank you very much[^AdditionalTechnologies_packagingtechnologies.xlsx] _(11 kB)_""\', ""Comment 11: \'Hi [~mberbert@deheus.com]"", ""Comment 12: we already have tool to import additional technologies based on specific layout. We need all data that you are planning to import to validate them before we proceed.\'"", ""Comment 13: \'[^Template.xlsx]\'"", \'Comment 14: ""Hi About template\', ""Comment 15: I have some questions. Could you please confirm or inform the right one:||Column||Description|||Code|Code of Additional Technology||Location|Production Area code?Name?ExernalId?||ItemCode|Final product Code||ItemName|Final product Name||FP itemcode|Final product code||FP percentage|Final product percentage||RM itemcode|Packaging Code||RM percentage|Packaging Percentage||Packing technology|True||Product definition|I don\'t know what this means||Value|Value of whom? FP"", \'Comment 16: RM?|Thank you very much""\', ""Comment 17: \'[~kacper.matuszek@kotrak.com]proszę zerknij na to i napisz w wewnętrznym komentarzy czy jest ok. wydaje mi się że można by zmienić FP ItemCode na Ingredient1 ItemCode"", ""Comment 18: RMItemCode na Ingredient2 ItemCode wtedy narzędzie było by bardziej uniwersalne i nie zawierało by bzdurnych naleciałości z Holandii.\'"", \'Comment 19: \\\'||Column||Description|||Code|Code of technology||Location|This location is paired with correct identifier. It means ExternalId. I will put legend in below this table||ItemCode|Final product code||ItemName|Final product name||FP itemcode|First ingredient code||FP percentage|First ingredient percentage||RM itemcode|Second ingredient code||RM percentage|Second ingredient percentage||PackingTechnology|True||ProductDefinition|You can fill True or False. It means system will create additional technology with flag ""product definition"" that contains 2 ingredient . (first final product\', \'Comment 20: second raw material)||Value|Technology percentage. Example:Fill 100 if your first ingredient percentage equals to 30% and second 70% etc.|Locations:||Location||ExternalId|||HE|9||GF|15||MB|11||AO|10||VE|8||UT|7||NY|6||AW|5||RA|4||ME|3||SN|2|If some locations are missing from the table\', \'Comment 21: you can specify your own location\', ""Comment 22: but you need to tell us which *external id* to pair with.\'"", ""Comment 23: \'Hi [~Przemyslaw.Przybyszewski@kotrak.com]Did you have opportunity to check my questions about purpose of the columns?I also want to know if we can upload the file by ourselfs. We are getting the list of addition technologies of items from each factory. We already have Apucarana and Toledo"", ""Comment 24: but other plants will take some time.Thank you very much\'"", ""Comment 25: \'Hi [~Przemyslaw.Przybyszewski@kotrak.com]Did you have opportunity to check my last comment?Thank you\'"", \'Comment 26: \\\'||Column||Description|||Code|Code of technology||Location|This location is paired with the correct identifier. It means ExternalId. I will put a legend below this table||ItemCode|Final product code||ItemName|Final product name||FP item code|First ingredient code||FP percentage|First ingredient percentage||RM item code|Second ingredient code||RM percentage|Second ingredient percentage||PackingTechnology|True||ProductDefinition|You can fill True or False. It means the system will create additional technology with the flag ""product definition"" that contains 2 ingredients. (first final product\', ""Comment 27: second raw material)||Value|Technology percentage.Example:Fill 100 if your first ingredient percentage equals to 30% and second 70% etc.|Locations:||Location||ExternalId|||HE|9||GF|15||MB|11||AO|10||VE|8||UT|7||NY|6||AW|5||RA|4||ME|3||SN|2|You can send us location codes and we will pair them with*external id*or you can send us some other proposals.\'"", ""Comment 28: \'Hi [~Przemyslaw.Przybyszewski@kotrak.com]Thank you for the Description of column.There are a lot of additional technologies which has more than 2 ingredients. For example"", ""Comment 29: you can find a lot of packaging items for MGC0001-S50 additional technology in Guararapes.How to manage this?Thank you\'"", \'Comment 30: ""[~mberbert@deheus.com]currently with a tool that we have it\\\'s not possible\', \'Comment 31: we will need to make some modifications for that\', ""Comment 32: that\'s why we asked for all technologies that you would like to migrate. Now I see that this migration will require a change in a tool that we have"", \'Comment 33: it would be better to move this task to the GDC project for better budget management (estimation\', \'Comment 34: approval\', \'Comment 35: etc.)""\', \'Comment 36: ""Hi [~Przemysław.Przybyszewski@kotrak.com]Thank you for this information.I\\\'ll raise a GDC for that.You can close this task""\', ""Comment 37: \'Thank you\'"", ""Comment 38: \'GDC-916 was raised.Thanks\']""]\nRelated Issues:\n[]\n\n### End'}"
214,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8818\n\n### Instruction:\nHello, recipe 506571 is not synced to DHP, in the meantime already 8 subversions are created, and also not visible in DHP. Please check and solve\n\n### Response:\n[""Comment 1: [\'recipe is visible in masterdata !2023-3-5-16-53-19-128!\'"", ""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: \'Could please provide more deatils what version or subersion you are missing I can see subversions from 0 to 9 are visible:!image-2023-03-23-17-09-40-245.png!\'"", ""Comment 4: \'I can see that the version 5,6 are in fact not sync to dhp"", ""Comment 5: but from I can check is that other subversion were created after the dhh item were updated. I try to resend them but with no results at this moment\'"", \'Comment 6: \\\'2023-03-23 18:37:57,068[5]ERROR Evolution.DHCService.Dhc30.Handlers.ProductionRecipeChangedMessageHandler[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.ProductionRecipes_dbo.Recipes_RecipeId"". The conflict occurred in database ""DHCService_NL_AS400_PROD""\', \'Comment 7: table ""dbo.Recipes""\', ""Comment 8: column \\\\\'Id\\\\\'.The statement has been terminated.\'"", \'Comment 9: ""Wskazuje że dla tych dwóch wersji nie może wysłać prod recipa do dhc service dziwny bład,Sam dhh item był przez nich edytowany mniej wiecej wtedy kiedy reszta receptu które przeszły,Linowanie wygląda ok\', \'Comment 10: restarty nie pomogły.select * from dhhitems where code like \\\'506571\\\'select * from Items where code like \\\'506571%\\\'integriendy i nutrienty sa wszystkie w dhcservice i dhccountryselect * from dhhitems where code like \\\'506571\\\'select * from Items where code like \\\'506571%\\\'select * from Recipes where DhhItemId=\\\'3CD3945C-D0A6-458E-9F7C-0B9D7FCD0043\\\' andversion=159select * from ProductionRecipes where RecipeId=\\\'5D985F9C-C439-4073-A47A-95BE27CBC175\\\' and Subversion in (5,6)""\', ""Comment 11: \'After deep analysis"", \'Comment 12: the problem is with two subversions 5,6.The problem is visible only for them \', ""Comment 13: the other versions synchronize truthfully. Have there been any changes made to linking dhhitem 506571?Are you whether subversions 7 and 8 are up to date and sufficient for current production? If so and for versions above 5.6 there are no problems can we lower the priority on p2?\'"", \'Comment 14: ""Thanks Agnieszka\', ""Comment 15: for now it\'s sufficient to continue production"", \'Comment 16: no longer P1.. But we tried sending the special over and over\', \'Comment 17: that\\\'s why 8 subversions where created.. And suddenly they all where there. question is what causes the delay? ""\', ""Comment 18: \'In the morning we will consult with programmers about the situation.\'"", \'Comment 19: ""Nie ma productionrecipe w DHCService dla subwersji 5,6 !screenshot-1! Przesłałem jedną z error i teraz brakuje tylko 6.{code:java}SELECT *  FROM [dbo].[ProductionRecipes]whereitemid=\\\'01960F89-997C-46CF-A9D9-DD49859CC65A\\\' and recipeid=\\\'5D985F9C-C439-4073-A47A-95BE27CBC175\\\'and version=159 and subversion in(4,5,6,7,8){code} !screenshot-2! Wysyłając z DHC nie ma wpisów że coś poszło do DHP dla onetime recipe (productionrecipe resent).""\', \'Comment 20: ""There was a problem with the recipe for the DHCService database - information about its lack.Subversion 5 was successfully sent\', ""Comment 21: is this subv. 6 needed? if subv. 6 is still required please send again the related order from erp.As for the cause it looks like yesterday\'s queue problem"", \'Comment 22: in version 3.0.60 it should no occur.""\', ""Comment 23: \'Oke"", ""Comment 24: ticket cna be closed\']""]\nRelated Issues:\n[]\n\n### End'}"
215,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8817\n\n### Instruction:\nTrip 2_L000165027 is visible in DHC, but not in DHP Sneek: Please check why not and if possible solve this\n\n### Response:\n[""Comment 1: [\'!afbeelding!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Te itemy nie wpadły do Service"", ""Comment 4: więc to nie to!image-2023-03-24-07-33-58-267.png!Zamówienie wygląda okay!image-2023-03-24-07-33-09-647.png!Zamówienie w plancie też jest!image-2023-03-24-07-40-45-393.png!\'"", \'Comment 5: ""Po resendzie:!image-2023-03-24-07-50-29-576.png!{code:java}2023-03-24 07:42:53,720 [104] ERROR Evolution.DHCService.Service.GetPackageDispatcher`1[[Evolution.DHCService.Contracts.ItemClassification\', \'Comment 6: Evolution.DHCService\', \'Comment 7: Version=3.2.0.0\', \'Comment 8: Culture=neutral\', ""Comment 9: PublicKeyToken=null]] [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\156434433\\\\\\\\DHAPPSV3-DHCSER534-JOB1\\\\\\\\Evolution.DHCService\\\\\\\\Evolution.DHCService.Service\\\\\\\\GetPackageDispatcher.cs:44] - System.Data.Entity.Core.EntityCommandExecutionException: An error occurred while reading from the store provider\'s data reader. See the inner exception for details. ---> System.Data.SqlClient.SqlException: Transaction (Process ID 89) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception"", \'Comment 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.TryHasMoreRows(Boolean& moreRows)   at System.Data.SqlClient.SqlDataReader.TryReadInternal(Boolean setTimeout\', \'Comment 21: Boolean& more)   at System.Data.SqlClient.SqlDataReader.Read()   at System.Data.Entity.Core.Common.Internal.Materialization.Shaper`1.StoreRead()   --- End of inner exception stack trace ---   at System.Data.Entity.Core.Common.Internal.Materialization.Shaper`1.HandleReaderException(Exception e)   at System.Data.Entity.Core.Common.Internal.Materialization.Shaper`1.StoreRead()   at System.Data.Entity.Core.Common.Internal.Materialization.Shaper`1.SimpleEnumerator.MoveNext()   at System.Data.Entity.Internal.LazyEnumerator`1.MoveNext()   at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection)   at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source)   at Evolution.DHCService.Dhc30.SynchronizationManager`2.CleanOutdated(Guid clientId) in E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\156434433\\\\\\\\DHAPPSV3-DHCSER534-JOB1\\\\\\\\Evolution.DHCService\\\\\\\\Evolution.DHCService.Dhc30\\\\\\\\SynchronizationManager.cs:line 62   at Evolution.DHCService.Dhc30.BaseGetService`1.GetPackage(Guid clientId\', \'Comment 22: Int32 packageSize) in E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\156434433\\\\\\\\DHAPPSV3-DHCSER534-JOB1\\\\\\\\Evolution.DHCService\\\\\\\\Evolution.DHCService.Dhc30\\\\\\\\BaseGetService.cs:line 35   at Evolution.DHCService.Service.GetPackageDispatcher`1.Get(PackageAcknowledge packageAcknowledge) in E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\156434433\\\\\\\\DHAPPSV3-DHCSER534-JOB1\\\\\\\\Evolution.DHCService\\\\\\\\Evolution.DHCService.Service\\\\\\\\GetPackageDispatcher.cs:line 382023-03-24 07:42:54,863 [104] INFO  Evolution.DHCService.Dhc30.ShippingNoticeService [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\156434433\\\\\\\\DHAPPSV3-DHCSER534-JOB1\\\\\\\\Evolution.DHCService\\\\\\\\Evolution.DHCService.Dhc30\\\\\\\\BaseGetService.cs:47] - [ClientId: (4230b275-1ba0-49f0-88f1-2e1154bb5dad)] Handling: (ShippingNotice) Package(c57faf84-8e16-46fb-8cf3-13ef5c515e15) Sending: 322023-03-24 07:42:57,048 [67] INFO  Evolution.DHCService.Dhc30.ItemClassificationService [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\156434433\\\\\\\\DHAPPSV3-DHCSER534-JOB1\\\\\\\\Evolution.DHCService\\\\\\\\Evolution.DHCService.Dhc30\\\\\\\\BaseGetService.cs:47] - [ClientId: (4d93e1b1-06e7-4cfe-9c18-3c234211565f)] Handling: (ItemClassification) Package(87376a01-5e40-48d5-9cd3-38e44b6217bc) Sending: 1002023-03-24 07:43:02,471 [50] INFO  Evolution.DHCService.Dhc30.ShippingNoticeService [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\156434433\\\\\\\\DHAPPSV3-DHCSER534-JOB1\\\\\\\\Evolution.DHCService\\\\\\\\Evolution.DHCService.Dhc30\\\\\\\\BaseGetService.cs:47] - [ClientId: (b9cabac7-c266-4c19-bafb-57e4324f7027)] Handling: (ShippingNotice) Package(b72a0ccd-4548-4095-b546-dd162e2a1105) Sending: 12023-03-24 07:43:02,518 [50] INFO  Evolution.DHCService.Dhc30.ShippingNoticeService [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\156434433\\\\\\\\DHAPPSV3-DHCSER534-JOB1\\\\\\\\Evolution.DHCService\\\\\\\\Evolution.DHCService.Dhc30\\\\\\\\BaseGetService.cs:64] - [ClientId: (b9cabac7-c266-4c19-bafb-57e4324f7027)] Handling: (ShippingNotice) Package(b72a0ccd-4548-4095-b546-dd162e2a1105) Confirming: 1{code}""\', ""Comment 23: \'z logów Planta:{code:java}2023-03-24 07:43:02 (/Plant.VC.BusinessLogic/DHVD01AP180/2840/3) [Error] Kotrak.Extensions.Pipeline.CatchPipeline - Pipeline execution errorSystem.NullReferenceException: Object reference not set to an instance of an object.   at Kotrak.Common.PublishedLanguage.User.Equals(User other)   at <>f__AnonymousType0`3.Equals(Object value)   at System.Linq.Lookup`2.GetGrouping(TKey key"", \'Comment 24: Boolean create)   at System.Linq.Lookup`2.Create(IEnumerable`1 source\', \'Comment 25: Func`2 keySelector\', ""Comment 26: IEqualityComparer`1 comparer)   at System.Linq.GroupedEnumerable`2.GetEnumerator()   at Kotrak.Common.Infrastructure.Integration.Filters.InboundMessageAcknowledgeHandlerFilter.Execute(InternalStorageContext`1 input)   at Kotrak.Extensions.Pipeline.Pipeline`1.Execute(T input)   at Kotrak.Extensions.Pipeline.CatchPipeline`1.Execute(TContext input){code}\'"", ""Comment 27: \'Hi,Order is in plant now:!image-2023-03-24-11-17-20-206.png!Regards\'"", ""Comment 28: \'Yes indeed"", ""Comment 29: what caused this?\'"", ""Comment 30: \'Hard to say"", \'Comment 31: because task was reported on Thursday late aftrernoon and I was investiagating on Friday morning\', \'Comment 32: I have just resent ShippingNotice from DHC Service and taht helped. In the past\', ""Comment 33: such cases were caused when some information in plant was missing (due to long synchronization etc). I have found deadlock errors in DHC Service logs.Regards\'"", ""Comment 34: \'Oke thanks. ticket can be closed\'"", ""Comment 35: \'Thank you\']""]\nRelated Issues:\n[]\n\n### End'}"
216,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8816\n\n### Instruction:\nThere are 2 production orders created and they are not synced to PCS. \r\ncan you check why and fix, if the problem is on DHP side? \r\nIf that is PCS, please inform ASAP, I will contact PCS developers. \n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'{code:java}2023-03-22 22:56:28 (/Plant.PCS.BusinessLogic/CIAPP04/3636/1) [Error] Kotrak.Common.Infrastructure.Hosting.BaseStartup - An error occurred while seeding the database.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) ---> System.ComponentModel.Win32Exception (53): The network path was not found.{code} !screenshot-1!  !screenshot-2! \'"", ""Comment 5: \'Yesterday evening there was a network problem with the connection to the database. After restarting the services messages for pcs were processed"", ""Comment 6: please check. Send a feedback.\'"", ""Comment 7: \'HI"", \'Comment 8: it works now\', \'Comment 9: please close the ticket\', ""Comment 10: Thank you very much Piotrek. \'"", ""Comment 11: \'Thank you for confirmation.\']""]\nRelated Issues:\n[]\n\n### End'}"
217,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8815\n\n### Instruction:\nFor item 140400 three Lot reports are created in DHP on 21/03/2023. \r\nThe Lot reports have status Confirmed but are not available in DHC. \r\nCan you check why these Lot reports are not in DHC\r\nCan you resend the Lot reports?\r\n\r\nLot reports:\r\n0112210323006\r\n0112210323007\r\n0112210323008\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Hello,\\\\r\\\\rWe are investigating your issue. We will inform you about the solution as soon as possible.\\\\r\\\\rRegards\\\\r\\\\r\'"", ""Comment 4: \'PRL were resend to DHC please verify.\'"", ""Comment 5: \'Lot reports are in DHC now. Thank yoo. This ticket can be closed.\']""]\nRelated Issues:\n[]\n\n### End'}"
218,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8814\n\n### Instruction:\nHi,\r\nWe 2 VTs(ID: 72c1826e-49e1-4e80-a986-116db65b2900,abc64336-4880-4f66-a8c9-22f6cfdb27f7) took Quatity from 1 PLR(43710210323007)\r\n1. check more information in attached\r\n2. Question that: why PLR canceled but VTs still taking data from that\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! {code:java}SELECT       [Created]         ,[Event]      ,[EventType]          ,[UserName]      ,[CorrelationId]  FROM [DHPlantProdBusinessLogicEvents].[dbo].[ProductionLots]  where AggregateId=\\\'1e4332a8-36e9-41e9-84d2-45dcbd54da10\\\'{code} !screenshot-2! To samo na teście :1. Dla utworzonego PLR\', \'Comment 4: po wystawieniu VT dispatch - pobierany jest  zasob.2. Potem anulujemy PLR\', \'Comment 5: przechodzi bez komunikatu o już wykorzystanych zasobach z dostawy.""\', ""Comment 6: \'Hello"", \'Comment 7: if PLR has been canceled after its resources have been released\', \'Comment 8: a change as GDC is required.If the system is to not allow such an operation\', ""Comment 9: or there is to be a warning.\'"", ""Comment 10: \'Hi,We are still facing this issue. Why does the system allow such an operation when the PLR has not been completed ? So how to fix it?**Please see attached file for details.[^Stock still take with PLR canceled -PCT.docx] _(708 kB)_\'"", \'Comment 11: ""Hi\', \'Comment 12: as I wrote before\', \'Comment 13: PLR\\\'s have been canceled after VT execution.Below are the dates. !screenshot-3! If the system is to not allow such an operation or there is to be a warning - a change as GDC is required.""\', \'Comment 14: ""{code:java}SELECT       p1.[Created],p2.lotnumber \', \'Comment 15:        p1.[EventType]      ,p1.[UserName]    FROM [DHPlantProdBusinessLogicEvents].[dbo].[ProductionLots] p1    join [DHPlantProdBusinessLogicMain].[dbo].[ProductionLots] p2 on p1.AggregateId=p2.Id    where p1.AggregateId  in(\\\'86A6FD48-DE71-4EA3-B2C0-90228C0E5DAE\\\',\\\'6D3BEF57-65DD-4FF8-BD44-E8DD865D6C41\\\') and p1.EventType like  \\\'%cancelled%\\\'{code}""\', ""Comment 16: \'hi,it mean1. issue from system2. it will be fix in next version?because:1. PLR still not finish but VT can take.2. Vt already took resource but still cancel it\'"", ""Comment 17: \'Yes"", \'Comment 18: but if stock is available on hand due to PLR\', ""Comment 19: then as VT will take the stock and then PLR is canceled - this is the current program operations.\'"", ""Comment 20: \'Hi. As described in my last comment this is how the application currently works.Is this a sufficient answer and can we close the task?\'"", ""Comment 21: \'The issue was explained in the task.\\\\rThis ticket has been closed.\']""]\nRelated Issues:\n[]\n\n### End'}"
219,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8813\n\n### Instruction:\nHello,\r\n\r\nPlease assist.\r\n\r\nin ERP there is a script that we use to change contracts (please see attached).\r\nWe are faced with a challenge, when it comes to changing contracts for imports (POs generated in foreign currency) the system updates the amounts on the POR and takes the PO amount in foreign instead.\r\nPlease see attached examples.\r\n\r\nCan you please update the script to accommodate foreign currency/exchange rate.\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: \'[~beata.kapturska@kotrak.com] sprawdź proszę"", ""Comment 4: czy powinniśmy ten skrypt modyfikować\'"", ""Comment 5: \'Hello NosiphoShould exchange rate always transfer from the PO document to  POR?\'"", \'Comment 6: ""For now I fixed this PORs on Nightly.Please\', \'Comment 7: confirm that these documents are correct\', \'Comment 8: I will do the same on Live and also I will fix costs on JOs.In the meantime I would like to check the script.I don\\\'t know how to create POR which is not linked with PO. When I try to do that I have information that I have to create PO first.""\', ""Comment 9: \'As per Teams.Can you please fix the script first. Purchasing is waiting to get a correct PO from Supplier"", ""Comment 10: we cant update PORs yet.\'"", ""Comment 11: \'For now I only change this PORs on NightlyIf you confirm that this documents are correct I will do this on Live and  fix costs on JOsthen I think that we will change the script\'"", \'Comment 12: ""I would like to check script for attaching POR with PO (on Nightly) but I don\\\'t know how to create POR that is not linked to PO?""\', ""Comment 13: \'Please see attached clip"", \'Comment 14: ""How to change contract""[^DGS-8813.mp4] _(1,20 MB)_\\\'\', \'Comment 15: ""I tested the script on POR-488/23/KLP (Nightly) databaseI unlinked POR from PO-1116/22/KLR and linked them againI don\\\'t know if the price on POR should be 985 USD or 1045 USD 985 + 60 = 1045 USD?Transport costs on PO = 60but I don\\\'t know - this value is 60 ZAR or 60 USD?""\', ""Comment 16: \'The transport cost on the item code is in ZAR\'"", ""Comment 17: \'All values on POR are calculated according to the POR exchange rate"", ""Comment 18: so the price on POR-488/23/KLP should be 988,27 USD / 18144,64 ZAR ? Exchange rate :18,36988,27  =  985 USD (price on PO) + 3,27 USD (Transport costs/POR exchange rate)Do you agree?\'"", ""Comment 19: \'Hi Beata"", \'Comment 20: the user confirmed the values to be correct\', ""Comment 21: please can you make the change on production. \'"", \'Comment 22: ""Can you confirm which values are correct?and what should I change now on production.I\\\'m not sure if the script works properly as I\\\'ve only tested it on one document.""\', ""Comment 23: \'The script has been transfered to the production database.\'"", ""Comment 24: \'Thanks.Please close this ticket \']""]\nRelated Issues:\n[]\n\n### End'}"
220,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8812\n\n### Instruction:\nWe would like to create an ( INT ) internal contract then we see an error message when we to save the contract:\r\n( ps. user already redid it once from scratch but got the same message )\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Could you please describe step by step how do you create internal contarct?\'"", ""Comment 3: \'Please"", ""Comment 4: let me know if you still face the same error message\'"", ""Comment 5: \'Dear,I have tried again and it seems solved now"", \'Comment 6: I could create and save a contract.Thank you for your assistance !Met vriendelijke groeten\', ""Comment 7: with kind regardsFrank BoersmaSupport Inkoop en Logistiek!image-1!\'"", ""Comment 8: \'Ticket can be closed\']""]\nRelated Issues:\n[\'DGS-8810\']\n\n### End'}"
221,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8811\n\n### Instruction:\nHello,\r\n\r\nPlease assist with the attached, these are the remaining items from this ticket.\r\nhttps://helpdesk.kotrak.com/servicedesk/customer/portal/56/DGS-8145\r\n\r\n\n\n### Response:\n[""Comment 1: [\'[^Creditors Clean Up - March.docx] _(178 kB)_\'"", ""Comment 2: \'Regarding to 010-40-10-01899The difference (8548,30) is caused by posting document PI-45/20/COSTRThis document was posted to 2020 after balance sheet transfer to 2021 !screenshot-1! There are two solutions:1. unposting document PI-45/20/COSTR in 2020 and posting in 2023or2. updating Opening Balance in periods 2021,2022"", ""Comment 3: 2023\'"", \'Comment 4: ""Regarding 010-40-10-01063Document PI-1634/17/COSTK was opened and reposted correctly.After this action the closing balance on this account in 2017 doesn\\\'t match with opening balance in 2018. !screenshot-2! So all changes need to be reverted and we must make correction in current period. Could I revert posting on Live database?""\', ""Comment 5: \'created Journal entry for correction 010-40-10-03365 !screenshot-3! Please"", ""Comment 6: check\'"", ""Comment 7: \'Fixed documents on 020-40-10-08527 - MC Petroleum - (nightly database)PI-115/20/MCOST"", \'Comment 8: PI-1315/17/MOM.Please\', ""Comment 9: check\']""]\nRelated Issues:\n[]\n\n### End'}"
222,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8810\n\n### Instruction:\nNot able to enter contracts into CDN at the moment. When we want to save the contract we get this error message. We dot need to put in a new contract quite urgently to be called off. \r\n\r\nBłąd podczas operacji na tabeli ObiektyObce\r\nXLZamknijDokumentZam: 8\r\n\r\nServer stack trace: \r\n   bij Kotrak.XLInterface.Orders.NewServices.ContractsService.CloseContract(Contract contract) in E:\\BambooHome\\xml-data\\build-dir\\18317313\\DHGUI-DHCDN982-JOB1\\DH CDN\\Kotrak.XLInterface.Orders\\NewServices\\ContractsService.cs:regel 1612\r\n   bij Kotrak.XLInterface.Orders.NewServices.ContractsService.SaveContract(LocalizableObject`1 locContract, LanguageIndentyfiers languageId, Boolean closeInApi) in E:\\BambooHome\\xml-data\\build-dir\\18317313\\DHGUI-DHCDN982-JOB1\\DH CDN\\Kotrak.XLInterface.Orders\\NewServices\\ContractsService.cs:regel 1703\r\n   bij Kotrak.XLInterface.Orders.NewServices.ContractsService.SaveAndConfirm(LocalizableObject`1 contract, LanguageIndentyfiers languageId) in E:\\BambooHome\\xml-data\\build-dir\\18317313\\DHGUI-DHCDN982-JOB1\\DH CDN\\Kotrak.XLInterface.Orders\\NewServices\\ContractsService.cs:regel 1630\r\n\r\nException rethrown at [0]: \r\n   bij System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)\r\n   bij System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)\r\n   bij Kotrak.XLInterface.Orders.Contracts.IContractsService.SaveAndConfirm(LocalizableObject`1 contract, LanguageIndentyfiers languageId)\r\n   bij Kotrak.XLInterface.Orders.Presentation.NewContracts.Forms.PurchaseEditModule.Save() in E:\\BambooHome\\xml-data\\build-dir\\18317313\\DHGUI-DHCDN982-JOB1\\DH CDN\\Kotrak.XLInterface.Orders.Presentation\\NewContracts\\Forms\\PurchaseEditModule.cs:regel 1174\r\n   bij Kotrak.XLInterface.Common.Forms.EditForm.OnSave() in E:\\BambooHome\\xml-data\\build-dir\\18317313\\DHGUI-DHCDN982-JOB1\\DH CDN\\Kotrak.XLInterface.Common\\Forms\\EditForm.cs:regel 245\r\n\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Is this language correct? Have you tried with English language? Also"", ""Comment 4: could you please provide me with user / operator context? I see this document on the list but it has completely different data!image-2023-03-23-11-05-21-316.png|width=1180,height=470!!image-2023-03-23-11-06-07-206.png!\'"", ""Comment 5: \'Plus"", \'Comment 6: did you copy the contract? Could you please check if when you use English language\', ""Comment 7: you receive the same error while saving?\'"", ""Comment 8: \'!image-2023-03-23-11-41-24-007.png!\'"", ""Comment 9: \'Please"", ""Comment 10: let me know if you still face the same error message\'"", ""Comment 11: \'!image-1!\'"", ""Comment 12: \'Ticket can be closed\'"", ""Comment 13: \'Thank you\']""]\nRelated Issues:\n[\'DGS-8812\']\n\n### End'}"
223,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8809\n\n### Instruction:\nThere are no lot reports coming through from DHP to DHC.\r\nFor example the 00714 that was produced last Monday.\r\nIt is not in DHC. Which results in no job orders being requested. As a result, the vehicle ticket cannot be continued.\r\n\r\nSometimes this works well and sometimes it doesn\'t.\r\nAlso with replanisment etc.\r\n\r\n\r\nPlease resolve as soon as possible. This greatly obstructs activities\r\n\n\n### Response:\n[""Comment 1: [\'!image-10!!image-7!!image-8!!image-9!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'870141170323239758701412003232401287014122032324061\'"", \'Comment 4: ""The given  documents were in DHC. When verifying\', ""Comment 5: please select PLRs list with the filter \'include message\'. They have been processed to XL"", \'Comment 6: please check again.""\', ""Comment 7: \'Ticket can be closed!image!\'"", ""Comment 8: \'!image-1!\'"", ""Comment 9: \'Ticket can be closed\']""]\nRelated Issues:\n[]\n\n### End'}"
224,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8808\n\n### Instruction:\nwe have problem in stock for item GCN3316-S25, lot number 0894140323004, barcode 89-W00G7A.\r\n\r\nIf we look stock screen, system is showing 1650kg but in WMS - Warehouse stocks is showing 675kg and the difference between screens is barcode 89-W00G7A.\r\n\r\nCould you please check what is correct quantity, why we have this error, and fix stock and wms?\r\n\r\nThank you\r\n\r\n\r\n\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!!image-1!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'!image-2023-03-23-08-39-18-186.png!!image-2023-03-23-08-38-53-790.png!!image-2023-03-23-08-39-41-524.png!\'"", \'Comment 4: \\\'{code:java}{""StockUnitId"":{""Id"":""e206590c-a19f-468c-a8f2-5009f9498f87""},""Barcode"":{""Code"":""89-W00G7A""},""CreatedDate"":""2023-03-16T01:15:06.3822649-03:00"",""ItemId"":{""Id"":""eccf3af5-a52b-4bfe-8bc9-6f5d5f6209e6""},""DeliveryId"":{""Id"":""05f7de1a-2d5d-4292-8459-09f89b36254c""},""Type"":20,""LocationId"":{""Id"":""91305d01-db70-4789-83fa-7547e04f0637""},""InitialQuantity"":{""Unit"":""kg"",""Value"":0.0},""Quantity"":{""Unit"":""kg"",""Value"":0.0},""QuantityOnHand"":{""Unit"":""kg"",""Value"":0.0},""LogisticStatus"":1,""QualityStatus"":1,""UnitLoadId"":{""Id"":""d58bf6ef-e529-443a-877a-9d25225fe038""},""OwnerId"":{""Id"":""d89f0a09-8bdb-4cd7-a726-1397adb096f0""},""RecreatedStockUnitId"":null,""IsLeftover"":false,""IsBrokenBatch"":false}{code}{code:java}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_UnitLoads_UnitLoadId"". The conflict occurred in database ""DHPlantWmsBusinessLogicMain""\', \'Comment 5: table ""dbo.UnitLoads""\', ""Comment 6: column \\\\\'Id\\\\\'. The statement has been terminated. at Microsoft.Data.SqlClient.SqlConnection.OnError(SqlException exception"", \'Comment 7: Boolean breakConnection\', \'Comment 8: Action`1 wrapCloseInAction) at Microsoft.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj\', \'Comment 9: Boolean callerHasConnectionLock\', \'Comment 10: Boolean asyncClose) at Microsoft.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior\', \'Comment 11: SqlCommand cmdHandler\', \'Comment 12: SqlDataReader dataStream\', \'Comment 13: BulkCopySimpleResultSet bulkCopyHandler\', \'Comment 14: TdsParserStateObject stateObj\', \'Comment 15: Boolean& dataReady) at Microsoft.Data.SqlClient.SqlDataReader.TryConsumeMetaData() at Microsoft.Data.SqlClient.SqlDataReader.get_MetaData() at Microsoft.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds\', \'Comment 16: RunBehavior runBehavior\', \'Comment 17: String resetOptionsString\', \'Comment 18: Boolean isInternal\', \'Comment 19: Boolean forDescribeParameterEncryption\', \'Comment 20: Boolean shouldCacheForAlwaysEncrypted) at Microsoft.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior\', \'Comment 21: RunBehavior runBehavior\', \'Comment 22: Boolean returnStream\', \'Comment 23: Boolean isAsync\', \'Comment 24: Int32 timeout\', \'Comment 25: Task& task\', \'Comment 26: Boolean asyncWrite\', \'Comment 27: Boolean inRetry\', \'Comment 28: SqlDataReader ds\', \'Comment 29: Boolean describeParameterEncryptionRequest) at Microsoft.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior\', \'Comment 30: RunBehavior runBehavior\', \'Comment 31: Boolean returnStream\', \'Comment 32: TaskCompletionSource`1 completion\', \'Comment 33: Int32 timeout\', \'Comment 34: Task& task\', \'Comment 35: Boolean& usedCache\', \'Comment 36: Boolean asyncWrite\', \'Comment 37: Boolean inRetry\', \'Comment 38: 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:5d03a108-5ce1-4379-a4ee-6ce585880c21 Error 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 39: IRelationalConnection connection) at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.StateManager.SaveChanges(IList`1 entriesToSave) at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.StateManager.SaveChanges(StateManager stateManager\', \'Comment 40: Boolean acceptAllChangesOnSuccess) at Microsoft.EntityFrameworkCore.SqlServer.Storage.Internal.SqlServerExecutionStrategy.Execute[TState,TResult](TState state\', \'Comment 41: Func`3 operation\', ""Comment 42: Func`3 verifySucceeded) at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.StateManager.SaveChanges(Boolean acceptAllChangesOnSuccess) at Microsoft.EntityFrameworkCore.DbContext.SaveChanges(Boolean acceptAllChangesOnSuccess) at Kotrak.Common.Infrastructure.EF.GenericRepositoryEf`1.Persist(TEntity entity) at Kotrak.Common.Infrastructure.Persistence.Repositories.AggregateRootRepository`2.Persist(TAggregateRoot root) at Plant.WMS.BusinessLogic.Application.StockUnits.StockUnitService.CreateStockUnit(CreateStockUnitDataStructure dataStructure) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Application\\\\\\\\StockUnits\\\\\\\\StockUnitService.cs:line 62 at Kotrak.Common.Infrastructure.Gate.CommandEnvironment.Run[TCommand](TCommand command) at Castle.DynamicProxy.AbstractInvocation.Proceed() at Kotrak.Common.Infrastructure.Interceptors.LoggingInterceptor`1.Intercept(IInvocation invocation) at Castle.DynamicProxy.AbstractInvocation.Proceed() at Kotrak.Common.Infrastructure.Gate.Filters.CommandProcessFilter`1.Execute(CommandPipelineContext`1 input) at Kotrak.Extensions.Pipeline.PredefinedFilters.FilterDecorator`1.Execute(TContext input) at Kotrak.Extensions.Pipeline.Pipeline`1.Execute(T input) at Kotrak.Common.Infrastructure.Gate.StandardGate.DispatchCommand[TCommand](TCommand command) at Plant.WMS.BusinessLogic.Infrastructure.ContextIntegration.IntercontextCommunication.Stock.StockUnitCreatedMessageHandler.Handle(StockUnitCreatedEvent message) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Infrastructure.ContextIntegration\\\\\\\\IntercontextCommunication\\\\\\\\Stock\\\\\\\\StockUnitCreatedMessageHandler.cs:line 28 at Kotrak.Common.Infrastructure.Integration.Filters.InboundMessageHandlerFilter.Execute(InternalStorageProcessContext`1 input) at Kotrak.Extensions.Pipeline.Pipeline`1.Execute(T input) at Kotrak.Common.Infrastructure.Integration.Filters.InboundMessagesProcessFilter.Execute(InternalStorageContext`1 input){code}\'"", ""Comment 43: \'Po resendzie messega z DHP{code:java}System.AggregateException: One or more errors occurred. (Response status code does not indicate success: 401 (Unauthorized).) ---> Refit.ApiException: Response status code does not indicate success: 401 (Unauthorized).   at Refit.RequestBuilderImplementation.<>c__DisplayClass14_0`2.<<BuildCancellableTaskFuncForMethod>b__0>d.MoveNext() in /_/Refit/RequestBuilderImplementation.cs:line 313   --- End of inner exception stack trace ---   at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions)   at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout"", ""Comment 44: CancellationToken cancellationToken)   at Plant.WMS.BusinessLogic.Infrastructure.ContextIntegration.ApiServices.StockEngine.StockEngineApplicationService.GetDeliverySourceDocuments(Guid deliveryId) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Infrastructure.ContextIntegration\\\\\\\\ApiServices\\\\\\\\StockEngine\\\\\\\\StockEngineApplicationService.cs:line 59   at Plant.WMS.BusinessLogic.Application.StockUnits.StockUnitService.CreateStockUnit(CreateStockUnitDataStructure dataStructure) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Application\\\\\\\\StockUnits\\\\\\\\StockUnitService.cs:line 62   at Kotrak.Common.Infrastructure.Gate.CommandEnvironment.Run[TCommand](TCommand command)   at Castle.DynamicProxy.AbstractInvocation.Proceed()   at Kotrak.Common.Infrastructure.Interceptors.LoggingInterceptor`1.Intercept(IInvocation invocation)   at Castle.DynamicProxy.AbstractInvocation.Proceed()   at Kotrak.Common.Infrastructure.Gate.Filters.CommandProcessFilter`1.Execute(CommandPipelineContext`1 input)   at Kotrak.Extensions.Pipeline.PredefinedFilters.FilterDecorator`1.Execute(TContext input)   at Kotrak.Extensions.Pipeline.Pipeline`1.Execute(T input)   at Kotrak.Common.Infrastructure.Gate.StandardGate.DispatchCommand[TCommand](TCommand command)   at Plant.WMS.BusinessLogic.Infrastructure.ContextIntegration.IntercontextCommunication.Stock.StockUnitCreatedMessageHandler.Handle(StockUnitCreatedEvent message) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Infrastructure.ContextIntegration\\\\\\\\IntercontextCommunication\\\\\\\\Stock\\\\\\\\StockUnitCreatedMessageHandler.cs:line 28   at Kotrak.Common.Infrastructure.Integration.Filters.InboundMessageHandlerFilter.Execute(InternalStorageProcessContext`1 input)   at Kotrak.Extensions.Pipeline.Pipeline`1.Execute(T input)   at Kotrak.Common.Infrastructure.Integration.Filters.InboundMessagesProcessFilter.Execute(InternalStorageContext`1 input){code}\'"", ""Comment 45: \'Prośba o wsparcie. Podobny temat już był w https://helpdesk.kotrak.com/browse/DGS-8778.Jest też RCA: https://helpdesk.kotrak.com/browse/DGS-8821Niestety nie mamy żadnych notatek odnośnie DGS-8778!image-2023-03-24-08-31-03-838.png|width=287,height=162!\'"", \'Comment 46: ""Stock unit i unit load zostaly dodane. Ponizej zalaczamy przydatne skrypty ;)!image-2023-03-24-12-49-45-759!{code:java}USE [DHPlantWmsBusinessLogicMain]GOINSERT INTO [dbo].[StockUnits]           ([Id]           ,[UnitLoadId]           ,[LogisticStatus]           ,[QualityStatus]           ,[SourceDocumentId]           ,[SourceDocumentNo]           ,[SourceDocumentNumber]           ,[SourceDocumentType]           ,[InitialSourceDocumentId]           ,[InitialSourceDocumentNo]           ,[InitialSourceDocumentNumber]           ,[InitialSourceDocumentType]           ,[InitialQuantityValue]           ,[InitialQuantityUnit]           ,[ReservedQuantityValue]           ,[ReservedQuantityUnit]           ,[QuantityOnHandValue]           ,[QuantityOnHandUnit]           ,[DeliveryId]           ,[InternalSerialNumber]           ,[ReservationSourceDocumentNumbers])\\\\t\\\\t   select s.id\', \'Comment 47: s.UnitLoadId\', \'Comment 48: s.LogisticStatus\', \'Comment 49: s.QualityStatus,\\\\t\\\\t   d.SourceDocumentId\', \'Comment 50: d.SourceDocumentNo\', \'Comment 51: d.SourceDocumentNumber\', \'Comment 52: d.SourceDocumentType,\\\\t\\\\t   d.InitialSourceDocumentId\', \'Comment 53: d.InitialSourceDocumentNo\', \'Comment 54: d.InitialSourceDocumentNumber,d.InitialSourceDocumentType,\\\\t\\\\t   s.InitialQuantity\', \'Comment 55: s.InitialQuantityUnit\', \'Comment 56: s.Quantity - s.QuantityOnHand\', \'Comment 57: s.InitialQuantityUnit,\\\\t\\\\t   s.QuantityOnHand\', \'Comment 58: s.QuantityOnHandUnit\', \'Comment 59: d.id\', \'Comment 60: d.InternalSerialNumber\', ""Comment 61: \'\'   FROM   [DHPlantStockBusinessLogicMain].dbo.StockUnits s   INNER JOIN [DHPlantStockBusinessLogicMain].dbo.Deliveries d on d.id = s.DeliveryId   where s.Barcode = \'89-W00g7a\'{code}{code:java}USE [DHPlantWmsBusinessLogicMain]GOINSERT INTO [dbo].[UnitLoads]           ([Id]           ,[Barcode]           ,[Type]           ,[LocationId]           ,[ParentUnitLoadId]           ,[QuantityValue]           ,[QuantityUnit]           ,[Ean]           ,[ExpiryDate]           ,[ForeignSerialNumber]           ,[ProducerId]           ,[SerialNumber]           ,[Status]           ,[ItemId]           ,[OwnerId]           ,[BagSizeUnit]           ,[BagSizeValue]           ,[CreatedDate]           ,[CreatedUserId]           ,[CreatedUserName]           ,[ModifiedDate]           ,[ModifiedUserId]           ,[ModifiedUserName]           ,[ReturnedUnitLoadId]           ,[IsIrregular]           ,[InternalSerialNumber]           ,[HeightUnit]           ,[HeightValue]           ,[RecreatedUnitLoadId])   SELECT s.UnitLoadId"", \'Comment 62: s.Barcode\', \'Comment 63: s.Type\', \'Comment 64: s.LocationId\', \'Comment 65: null\', \'Comment 66: s.Quantity\', \'Comment 67: s.QuantityUnit\', ""Comment 68:   \'\'"", \'Comment 69: d.ExpiryDate\', \'Comment 70: d.ForeignSerialNumber\', \'Comment 71: d.ProducerId\', \'Comment 72: d.SerialNumber\', \'Comment 73: 10\', \'Comment 74: S.ItemId\', \'Comment 75:   s.OwnerId\', \'Comment 76: D.BagSizeUnit\', \'Comment 77: d.BagSize\', \'Comment 78: s.CreatedDate\', ""Comment 79: (select id from [DHPlantAuthBusinessLogicMain].dbo.AspNetUsers where UserName = \'admin\')"", ""Comment 80: \'admin\'   "", \'Comment 81: s.CreatedDate\', ""Comment 82: (select id from [DHPlantAuthBusinessLogicMain].dbo.AspNetUsers where UserName = \'admin\')"", ""Comment 83: \'admin\'"", \'Comment 84: null\', \'Comment 85: 0 ,d.InternalSerialNumber\', ""Comment 86:   \'m\',1.500000"", \'Comment 87: null      FROM   [DHPlantStockBusinessLogicMain].dbo.StockUnits s   INNER JOIN [DHPlantStockBusinessLogicMain].dbo.Deliveries d on d.id = s.DeliveryId   where s.Barcode = \\\'89-W00g7a\\\'   select id from [DHPlantAuthBusinessLogicMain].dbo.AspNetUsers where UserName = \\\'admin\\\'{code}""\', \'Comment 88: ""[~aleksandra.masternak@kotrak.com] a to po co? :)bo w scrypcie widzę\', \'Comment 89: że user jest użyty\', \'Comment 90: a nie id :)** select id from [DHPlantAuthBusinessLogicMain].dbo.AspNetUsers where UserName = \\\'admin\\\' ""\', ""Comment 91: \'Dzięki wielkie :)\'"", ""Comment 92: \'Stock unit and unit load have been added.Please"", ""Comment 93: verify\'"", ""Comment 94: \'[~aleksandra.przybylek@kotrak.com] admin jest bo trzeba wrzucić jakiegoś user. w mojej opinii admin jest wszędzie wiec moze być.\'"", ""Comment 95: \'[~maciej.dobrzanski@kotrak.com]bardziej mi chodziło o to"", \'Comment 96: czy dodać ten wpis / selekta do procedury\', \'Comment 97: czy jest on do czegoś niezbędny oprócz tego miejsca (zakładam\', ""Comment 98: ze to zostaje na sztywno zatem)!image-2023-03-24-14-04-06-391.png!\'"", ""Comment 99: \'a ten końcowy nie nie jest potrzebny\'"", ""Comment 100: \'Hi Aleksandra,I checked and now is correct. You can close this task. Thank you.\'"", ""Comment 101: \'Thank you.\']""]\nRelated Issues:\n[\'DGS-8778\', \'DGS-8821\']\n\n### End'}"
225,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8807\n\n### Instruction:\nHi\r\n\r\nThe factory reported that Production Order Printout for PRO-657/3/23 (FCP5290-T-S24) version 1.0 didn\'t list all elements.\r\nLooking to the PrO and PLR, all items are there, however printout is not displaying it.\r\nI found the problem: the scale number on DHP for this recipe is NULL.\r\nHowever on DHC we have the right scale number.\r\n\r\nWhen we execute the following query, we find 32 registers with ScaleNumber = NULL.\r\n\r\n{noformat}\r\nSELECT * FROM DHPlantProdBusinessLogicMain.dbo.RecipeElements re WHERE ScaleNumber IS NULL\r\n{noformat}\r\n\r\nCould you please fix that?\r\n\r\nThank you very much\n\n### Response:\n[""Comment 1: [\'!image!!image-1!\'"", ""Comment 2: \'[^OrdemDeProducao_FCP5290-T-S24.pdf] _(333 kB)_\'"", ""Comment 3: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 4: ""select * FROM [Evolution_DHCService].[dbo].[TechnologyIngredients] where technologyid=\\\'FEACC42C-42F0-47BF-B72C-CA695503AA5D\\\'tutaj na bazie dhc service nie widać zadnych zmian czy updatów od 2022 roku,!image-2023-03-22-18-33-27-912.png!""\', \'Comment 5: ""select* from DHPlantIntegrationDhcServiceIdentityMapping.dbo.TechnologyIdentityMappings where plantid in  (SELECT id FROM DHPlantProdBusinessLogicMain.dbo.RecipeElements re WHERE ScaleNumber IS NULL)po id receptury nic tu nie znajduje FROM [DHPlantProdBusinessLogicIntercontext].[dbo].[Errors] ani na bazie maintponowna synchra z dhcservice nic nie zmieniliapoprzednio technologie szly roznie :!image-2023-03-22-19-09-13-511.png!dla przykładowej technology z taska w evenecie dla 2 pozycji jest scale number=1FROM [DHPlantProdBusinessLogicEvents].[dbo].[ReceivedRecipes]where CorrelationId=\\\'C96FBFB5-C905-443E-8BBA-D174EB1C5852\\\'!image-2023-03-22-19-28-45-412.png!tutaj mamy null:!image-2023-03-22-19-29-38-783.png! !image-2023-03-22-19-28-22-808!!image-2023-03-22-19-28-45-412! !image-2023-03-22-19-29-38-783!""\', \'Comment 6: ""SELECT * FROM DHPlantProdBusinessLogicMain.dbo.RecipeElements re WHERE ScaleNumber IS NULL and re.id=\\\'1FDA04B7-8D37-4D8A-AB90-B43E5E19FA06\\\'""\', \'Comment 7: ""update przyotowany ale nie puszczony :update DHPlantProdBusinessLogicMain.dbo.RecipeElements set scalenumber=1 WHERE ScaleNumber IS NULL and id=\\\'1FDA04B7-8D37-4D8A-AB90-B43E5E19FA06\\\'""\', ""Comment 8: \'[~agnieszka.januszewska@kotrak.com] uzgodnij prosze z klientem jakie mają być ustawione scale number i puść update\'"", ""Comment 9: \'Hej aktualnie jest 38 takich pozycji na 11 vtkach ( czyli przyrosło o 6) pytanie jak to uzupełnić "", \'Comment 10: bo okazuje się że nie mogę tego przelożyc 1:1 z tabeli w dhc service :np raz scalenumber w dhp to 0\', ""Comment 11: raz 1 a w dhc service dhc scale type to 2!image-2023-03-24-18-04-49-297.png!\'"", ""Comment 12: \'Jeśli chodzi o scale number to napisał"", \'Comment 13: że takie same jak w DHC\', ""Comment 14: Aga ma teraz inny problem.!image-2023-03-27-10-21-43-373.png!\'"", ""Comment 15: \'Dear Maicon,Could you please confirm scale number that is missing?Regards\'"", \'Comment 16: ""Hi AleksandraI\\\'m sorry! I did not understand your question..Thank you""\', ""Comment 17: \'I meant:_{color:#0747a6}the scale number on DHP for this recipe is NULL{color}_ - is it always the same number?Regards\'"", \'Comment 18: ""Well I don\\\'t have this answer.I think you need to check with the DHC x DHP integration expert.I can extract a list of items and scale number from DHC and make a relation with DHP\', \'Comment 19: however the list is increasing. Fix today and tomorrow will have more.This is an application issue\', \'Comment 20: I just did the analysis on the DB\', ""Comment 21: but I can\'t take responsibility for saying what data should be in the scale number"", \'Comment 22: because it must come from DHC.Thank you""\', ""Comment 23: \'Hi [~Aleksandra.Przybylek@kotrak.com]We have new case: SUC6687-MD-S20How is the status? This is becoming critical"", \'Comment 24: because the operator uses the PrO Printout to validate which RM they need to move to Production area\', ""Comment 25: and this missing scale type in the recipe elements is not being printed on the PrO Printout.Could you please raise this task to the list of priority tasks?Thank you\'"", ""Comment 26: \'Tak jak napisałem trzeba ustalić z klientem ewentualnie sprawdzić w dhc tak jak chce klient i zrobić update \'"", ""Comment 27: \'!dhcdhp!\'"", ""Comment 28: \'[~maciej.dobrzanski@kotrak.com]analizowałam i wysłałam to w komentarzu wew. wczesniej ale moze byl on niejasny:W bazie dhc i dhc serviece na tabeli z se skladnikami technologii nie ma kolumny scalenumber jest scale type :!image-2023-03-31-12-23-38-662.png!które przyjmuje wartości od 0 do 4w plancie oprócz nule jest to 0 "", \'Comment 29: 1\', \'Comment 30: 2\', \'Comment 31: 3więc to nie pzruyjmuje wartosci 1 do 1 dla wybranej jednej technologiitym przypadku z reguły jest to scale minus 1 ale jak wczensije patrzyłam było czas że wartos c 0 w dhc odpowiadała wartosci 1 lub 2 w dhp.więc pytanie jesli mamy zrobić update to wg jakiegio klucza!image-2023-03-31-13-12-08-983.png!tutajw komentrazu z 24.03 to widac że scaletype było 2 ( dhc)a scale number 0(dhp)!image-2023-03-31-13-02-20-806.png!więc co wstawiać w DHP ,ta informacja jest w evencie\', \'Comment 32: sprawdzenie każdego evenetu i update to jakies 5 minut aktualnie takich pozycji z nulem zwraca 55 pozycjiczyli poprawianie tego zajmie kilka godzin.rozumiem też ze aktualnie serwis bedzie raz w tygodniu edytował ok 20 takich wpisów ( tyle przybyło w tym miesiącu)Prosze o wskaznie jak się przekłada scaletype na sclae number\', ""Comment 33: albo na jakiej podstawie wstawiac te wartoscKlient nie wie jak wartosc ma byc na bazie.\'"", ""Comment 34: \'[~agnieszka.januszewska@kotrak.com],To mapowanie odbywa sie na poziomie dhc service i wygląda następująco:ing.ScaleNumber = (short)(ing.ScaleNumber == 0 ? ing.ScaleNumber : ing.ScaleNumber - 1);Czyli jak jest 0 wysyła 0 w przeciwnym wpadku bierze wartość z dhc service i odemuje 1\'"", ""Comment 35: \'Tutaj też spędziłem sporo czasu z Łukaszem i nie udało nam się znaleźć przyczyny.Poinformujcie klienta że przy kolejnym nowym przypadku załozymy RCA ponieważ na chwile obecną nie jesteśmy w stanie zlokalizować przyczyny.wygląda to na jakis trigger albo jakby ktoś zmieniał coś ręcznie\'"", ""Comment 36: \'Hello we update 63 position and filled the scale number,Please verify.If there is a need from your sideto investigate the reasonof the issue"", \'Comment 37: or you find new examples\', \'Comment 38: we may raise RootCause Analysis (RCA)task for you.Please\', ""Comment 39: let us knowhow you wish us to proceed.\'"", ""Comment 40: \'--select * from DHPlantIntegrationDhcServiceIdentityMapping.dbo.TechnologyIngredientIdentityMappings m--join dHPlantProdBusinessLogicMain.dbo.RecipeElements re on re.id=m.PlantId and re.no=m.PlantIdNo----join DHPlantIntegrationDhcServiceIdentityMapping.dbo.TechnologyIdentityMappings tm on tm.id=--WHERE re.ScaleNumber IS NULL\'"", ""Comment 41: \'Hi [~Agnieszka.Januszewska@kotrak.com]We now have more 3 recipes with elements with ScaleNumber = NULL:||Item||Version||Subversion|||FCP5271-T-S12|8|2||GLN2217-S25|59|0||SUN7500-S15|14|1|And yes"", \'Comment 42: please\', ""Comment 43: raise a RCAThank you very much!\'"", ""Comment 44: \'Hello"", ""Comment 45: the RCA task is underDGS-8949About last 3 examples do you wish to update scale number from db?\'"", ""Comment 46: \'Hi [~Agnieszka.Januszewska@kotrak.com]I prefer you to fix it.Thank you\'"", ""Comment 47: \'dla wszystkich elementów była 2 w dhc serwis wiec poszedl update na 1select ExternalId,ScaleType,* from TechnologyIngredients where ExternalId in (3475869,3475873,3475880,3516609,3516614,3521889,3521895,3521896)order by 1\'"", ""Comment 48: \'update dHPlantProdBusinessLogicMain.dbo.RecipeElementsset ScaleNumber=1 where scalenumber is null\'"", ""Comment 49: \'Data was update please check.\'"", \'Comment 50: ""Hi [~Agnieszka.Januszewska@kotrak.com]Now it\\\'s OK!What we do for new cases? Do I need to create new DGS or only insert the cases in RCA?You can close this task. Thank you""\', ""Comment 51: \'Yes please provide new cases under rcaDGS-8949.May we close this task?\'"", ""Comment 52: \'Hi [~Agnieszka.Januszewska@kotrak.com]You can close this task.Thank you very much!\']""]\nRelated Issues:\n[\'DGS-8949\']\n\n### End'}"
226,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8806\n\n### Instruction:\nHi\r\n\r\nWe are facing some issues with duplicated palletlabels in RC1 and U2 and we can\'t evidence who is printing it.\r\nSo we\'d like to know if we have an option to trace the user that printed a palletlabel.\r\n\r\nThank you\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'info od Marcina K: ten jest przez nich dodany raczej"", \'Comment 3: jeszcze są dwa DummyPallet\', \'Comment 4: one tez sa jako pallet labelPytanie\', \'Comment 5: czy da się wyciągnąć\', ""Comment 6: który user generuje wydruk i ewentualnie ile razy!image-2023-03-23-10-36-34-155.png!\'"", ""Comment 7: \'Czy da się w ogóle wyciągnąć usera? I ewentualnie dodać do wydruku i takie rozwiązanie zaproponować klientowi?\'"", ""Comment 8: \'Proszę o wycenę zmiany mechanizmu do wydruku"", ""Comment 9: plus info jakjak pole z informacją o userze jest wyciągane :)\'"", ""Comment 10: \'Hi Maicon,There is an option. But it requires a change under GDC project. Please"", ""Comment 11: raise a GDC task.Regards\'"", \'Comment 12: ""Hi AleksandraWe can raise a GDC task\', ""Comment 13: but I\'d like to understand what we already have.You mean we already have something on database"", \'Comment 14: but it demands a screen on DHP system to read it? Or is it a new functionality?For us\', \'Comment 15: only a sql query or an analysis in a _.log_ file is enought for now.Thank you""\', \'Comment 16: ""Hi,We\\\'d rather thought about changing a printout mechanism so that you would have information on a label who printed it. But we can also take into consideration your ideas - additional screen or something. But\', \'Comment 17: whatever we do - this would be a change. So please\', \'Comment 18: let us know what your decision is and let us know if you rased a GDC taskBest Regards""\', \'Comment 19: ""Hi AleksandraThank you for this answer.We\\\'ll think about the added value of this and raise a GDC.You can close this task.Thank you very much!""\', ""Comment 20: \'Thank youRegards\']""]\nRelated Issues:\n[]\n\n### End'}"
227,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8805\n\n### Instruction:\nNa pracowniku Weronika Jankiewicz występuje błąd atrybutu, prośba o weryfikację oraz naprawienie błędu.\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image![^szczególy_błędu.docx] _(16 kB)_\'"", ""Comment 2: \'[^DGS-8805_atrybuty.docx]\'"", ""Comment 3: \'Explanations in the attachment[^DGS-8805_atrybuty.docx]\'"", ""Comment 4: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 5: \'NOWAK_KAC - zatrudniony od 2021-06-01 / nie powinno być  określonej „daty do”UM-JANKIEWICZ_W – jest aktualizacja co miesiąc/ tnzn. Ostatni zapis powinien być od 2023.02.01 - do 2023.02.28\'"", ""Comment 6: \'The data has been corrected"", ""Comment 7: please verify.\'"", ""Comment 8: \'The changes helped"", ""Comment 9: task to close.\']""]\nRelated Issues:\n[]\n\n### End'}"
228,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8804\n\n### Instruction:\nI\'d like to come back to old reported error that fills DHCService.Client logs on TS06-20 in Leczyca.\r\nIt\'s around 150MB of logs daily, most of them are about SampleAnalysis save unability.\r\nPlease, take a look what cause this amount of logs.\r\n\r\n2023-03-22 12:59:12,194 [5] ERROR Evolution.DHCService.Client.Services.BaseFetchService`1 [E:\\BambooHome\\xml-data\\build-dir\\152764417\\DHAPPSV3-DHCSC25-JOB1\\Evolution.DHCService.Client\\Evolution.DHCService.Client\\Services\\BaseFetchService.cs:64] - Evolution.DHCService.Client.Exceptions.PersistenceException: Cannot store contract Id:[91540] ---> System.Data.SqlClient.SqlException: An error occured while SampleAnalysis save\r\n   w System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)\r\n   w System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)\r\n   w System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)\r\n   w System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)\r\n   w System.Data.SqlClient.SqlDataReader.TryConsumeMetaData()\r\n   w System.Data.SqlClient.SqlDataReader.get_MetaData()\r\n \n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'{code:java} SELECT s.DocumentNumber,s.DocumentMonth,s.DocumentYear,s.DocumentSeries,s.ExternalId   FROM [Evolution_DHCService].[dbo].[SampleAnalysisExportInfoes] se  inner join [Evolution_DHCService].[dbo].[SampleAnalyses] s  on s.id=se.EntityId  where se.CommitDate is null  order by s.ExternalId {code} !screenshot-1! {code:java}2023-03-28 09:50:54,925 [5] ERROR Evolution.DHCService.Client.Services.BaseFetchService`1 [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\152764417\\\\\\\\DHAPPSV3-DHCSC25-JOB1\\\\\\\\Evolution.DHCService.Client\\\\\\\\Evolution.DHCService.Client\\\\\\\\Services\\\\\\\\BaseFetchService.cs:64] - Evolution.DHCService.Client.Exceptions.PersistenceException: Cannot store contract Id:[75658] ---> System.Data.SqlClient.SqlException: An error occured while SampleAnalysis save   w System.Data.SqlClient.SqlConnection.OnError(SqlException exception"", \'Comment 4: Boolean breakConnection\', \'Comment 5: Action`1 wrapCloseInAction)   w System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception\', \'Comment 6: Boolean breakConnection\', \'Comment 7: Action`1 wrapCloseInAction)   w System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj\', \'Comment 8: Boolean callerHasConnectionLock\', \'Comment 9: Boolean asyncClose)   w System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior\', \'Comment 10: SqlCommand cmdHandler\', \'Comment 11: SqlDataReader dataStream\', \'Comment 12: BulkCopySimpleResultSet bulkCopyHandler\', \'Comment 13: TdsParserStateObject stateObj\', \'Comment 14: Boolean& dataReady)   w System.Data.SqlClient.SqlDataReader.TryConsumeMetaData()   w System.Data.SqlClient.SqlDataReader.get_MetaData()   w System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds\', \'Comment 15: RunBehavior runBehavior\', \'Comment 16: String resetOptionsString\', \'Comment 17: Boolean isInternal\', \'Comment 18: Boolean forDescribeParameterEncryption\', \'Comment 19: Boolean shouldCacheForAlwaysEncrypted)   w System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior\', \'Comment 20: RunBehavior runBehavior\', \'Comment 21: Boolean returnStream\', \'Comment 22: Boolean async\', \'Comment 23: Int32 timeout\', \'Comment 24: Task& task\', \'Comment 25: Boolean asyncWrite\', \'Comment 26: Boolean inRetry\', \'Comment 27: SqlDataReader ds\', \'Comment 28: Boolean describeParameterEncryptionRequest)   w System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior\', \'Comment 29: RunBehavior runBehavior\', \'Comment 30: Boolean returnStream\', \'Comment 31: String method\', \'Comment 32: TaskCompletionSource`1 completion\', \'Comment 33: Int32 timeout\', \'Comment 34: Task& task\', \'Comment 35: Boolean& usedCache\', \'Comment 36: Boolean asyncWrite\', \'Comment 37: Boolean inRetry)   w System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior\', \'Comment 38: RunBehavior runBehavior\', \'Comment 39: Boolean returnStream\', \'Comment 40: String method)   w System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior\', \'Comment 41: String method)   w System.Data.SqlClient.SqlCommand.ExecuteDbDataReader(CommandBehavior behavior)   w System.Data.Common.DbCommand.System.Data.IDbCommand.ExecuteReader(CommandBehavior behavior)   w Dapper.SqlMapper.ExecuteReaderWithFlagsFallback(IDbCommand cmd\', \'Comment 42: Boolean wasClosed\', \'Comment 43: CommandBehavior behavior)   w Dapper.SqlMapper.<QueryImpl>d__125`1.MoveNext()   w System.Collections.Generic.List`1..ctor(IEnumerable`1 collection)   w System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source)   w Dapper.SqlMapper.Query[T](IDbConnection cnn\', \'Comment 44: String sql\', \'Comment 45: Object param\', \'Comment 46: IDbTransaction transaction\', \'Comment 47: Boolean buffered\', \'Comment 48: Nullable`1 commandTimeout\', ""Comment 49: Nullable`1 commandType)   w Evolution.DHCService.Client27.Data.Repositories.SampleAnalysisSetRepository.Save(SampleAnalysis contract) w E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\152764417\\\\\\\\DHAPPSV3-DHCSC25-JOB1\\\\\\\\Evolution.DHCService.Client\\\\\\\\Evolution.DHCService.Client27.Data\\\\\\\\Repositories\\\\\\\\SampleAnalysisSetRepository.cs:wiersz 55   w Evolution.DHCService.Client.Data.Repositories.PersistenceExceptionSetRepositoryDecorator`1.Save(TContract contract) w E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\152764417\\\\\\\\DHAPPSV3-DHCSC25-JOB1\\\\\\\\Evolution.DHCService.Client\\\\\\\\Evolution.DHCService.Client.Data\\\\\\\\Repositories\\\\\\\\PersistenceExceptionSetRepositoryDecorator.cs:wiersz 23   --- Koniec śladu stosu wyjątków wewnętrznych ---   w Evolution.DHCService.Client.Data.Repositories.PersistenceExceptionSetRepositoryDecorator`1.Save(TContract contract) w E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\152764417\\\\\\\\DHAPPSV3-DHCSC25-JOB1\\\\\\\\Evolution.DHCService.Client\\\\\\\\Evolution.DHCService.Client.Data\\\\\\\\Repositories\\\\\\\\PersistenceExceptionSetRepositoryDecorator.cs:wiersz 27   w Evolution.DHCService.Client.Services.BaseFetchService`1.Fetch(IDhcService dhcService) w E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\152764417\\\\\\\\DHAPPSV3-DHCSC25-JOB1\\\\\\\\Evolution.DHCService.Client\\\\\\\\Evolution.DHCService.Client\\\\\\\\Services\\\\\\\\BaseFetchService.cs:wiersz 57{code}\'"", \'Comment 50: ""{code:java}update se --select p.City,bs.Name,bs2.name,s.DocumentNumber,s.DocumentMonth,s.DocumentYear,s.DocumentSeries,s.ExternalId,se.EntityId,se.SendDate,se.CommitDate  set se.CommitDate=se.SendDate  FROM [Evolution_DHCService].[dbo].[SampleAnalysisExportInfoes] se  inner join [Evolution_DHCService].[dbo].[SampleAnalyses] s   on s.id=se.EntityId    inner join [Evolution_DHCService].dbo.ProductionAreas p on p.Id=s.ProductionAreaId  inner join [Evolution_DHCService].dbo.BusinessStructures bs on bs.id=s.BusinessStructureId  inner  join [Evolution_DHCService].dbo.BusinessStructures bs2 on bs2.Id=se.clientid   where se.CommitDate is null --and s.BusinessStructureId=\\\'6EA82538-C12B-4FD1-8D72-88E3A3FDF1F3\\\'  and DocumentYear<=2022  order by s.ExternalId {code}!image-2023-04-03-17-01-23-777!Np. do łęczycy zamiast Mieściska26220810002 próbka - AO 10359/8/22/M.!image-2023-04-03-17-05-20-053!""\', ""Comment 51: \'Hello"", ""Comment 52: currently the problem should not occur from around 4:05 pm.The problem was the Analysis Orders that tried to import to the plant in Łęczyca.List below. [^AO.txt] \'"", ""Comment 53: \'The data has been corrected"", \'Comment 54: the issue has been closed.\\\\rIf problem with data synchronization occur again\', ""Comment 55: please create a new ticket.\']""]\nRelated Issues:\n[]\n\n### End'}"
229,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8803\n\n### Instruction:\nfor the PLR 4611150323003\r\nwhen i checked in log file and with Json, the item 6101150 is not existing.\n\n### Response:\n[""Comment 1: [\'[^4611150323003.json] _(5 kB)_!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: \'What is the exact issue with this PLR? Could you please clarify?Regards\'"", ""Comment 4: \'!image-2023-03-22-07-50-49-894.png!\'"", ""Comment 5: \'Production Lot jest cancelled!image-2023-03-22-07-51-43-631.png!a w plancie confirmed!image-2023-03-22-07-54-50-700.png!\'"", ""Comment 6: \'W obu aplikacjach ilość elementów na PLR się zgadza"", ""Comment 7: jest też wspomniany item!image-2023-03-22-07-56-34-025.png!!image-2023-03-22-07-58-20-263.png!\'"", ""Comment 8: \'you can see item code 6101150 in PLR in DHC"", \'Comment 9: but when PLR was sent to D365\', ""Comment 10: there was no item 6101150\'"", ""Comment 11: \'Do you have this item in Dynamics?\'"", ""Comment 12: \'please check in Json file which was exported from DHC to D365"", ""Comment 13: and we could not find this item in Json. that is the reason D365 can not receive it.\'"", ""Comment 14: \'Hi,We tried to resync but it will not work because on PLR we have informiation that JO"", \'Comment 15: IR+ and IR- documents have been already generated.What is needed to do is to cancelJO\', ""Comment 16: IR+ and IR- documents in D365 and let us know so that we could resynced.Regards\'"", ""Comment 17: \'Jak odpiszą"", \'Comment 18: że dokumenty cancelowane\', ""Comment 19: to:>> w miejscach zaznaczonych wstawić NULL i IsCanceled = 0!image-2023-03-22-11-50-06-282.png! >> usunąć mapowanie wg tej procedury:*[[DHC] PONOWNE WYSŁANIE VT DO MILAS|onenote:https://kotrak.sharepoint.com/sites/erpasysta/Shared%20Documents/Baza%20wiedzy/Baza%20Wiedzy%20-%20ERPSD/Klienci/DEHEUS/DEHEUS%20APPLICATIONS/Holandia%20Premix%20i%20AS400/Baz%20wiedzy%20z%20AS400.one#%5bDHC%5d%20PONOWNE%20WYS%C5%81ANIE%20VT%20DO%20MILAS&section-id=\\\\\\\\{9BB564BA-0B58-4580-B9E0-F3CF9D6D80A7}&page-id=\\\\\\\\{4EBEDAA7-0DC4-410F-A617-93B6B59B31B6}&end] ([Widok sieci Web|https://kotrak.sharepoint.com/sites/erpasysta/_layouts/OneNote.aspx?id=%2Fsites%2Ferpasysta%2FShared%20Documents%2FBaza%20wiedzy%2FBaza%20Wiedzy%20-%20ERPSD&wd=target%28Klienci%2FDEHEUS%2FDEHEUS%20APPLICATIONS%2FHolandia%20Premix%20i%20AS400%2FBaz%20wiedzy%20z%20AS400.one%7C9BB564BA-0B58-4580-B9E0-F3CF9D6D80A7%2F%5BDHC%5D%20PONOWNE%20WYS%C5%81ANIE%20VT%20DO%20MILAS%7C4EBEDAA7-0DC4-410F-A617-93B6B59B31B6%2F%29])*!image-2023-03-22-11-39-16-163.png!\']""]\nRelated Issues:\n[]\n\n### End'}"
230,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8802\n\n### Instruction:\nPlease help to check this case and solving in Hau Giang Plant -0434.\r\n\r\nPLR 4341180323044 could not be found in the Production Report module (Maybe, user deleted this PLR) . But release to stock with stock unit status is ""In progress"" . Please check and clear this stock unit . 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: \'Ofkors"", ""Comment 4: że usunięte!image-2023-03-22-08-32-45-217.png!\'"", ""Comment 5: \'Yes.PLR 4341180323044 has been deleted under db.Could you please clarify why users delete PLRs? If it is done by mistake they can cancel it in application. This is not the first task where it has been reported that user deletd PLR under DB...The stock is corrected.Regards\'"", ""Comment 6: \'[^dgs-8802.xlsx]\'"", \'Comment 7: ""[^dgs-8802.xlsx]{code:java}UPDATE DSET Status = 2\', \'Comment 8: Quantity = 0\', \'Comment 9: ExpiryDate = GETDATE()FROM DHPlantStockBusinessLogicMain.dbo.Deliveries DLEFT JOIN DHPlantStockBusinessLogicMain.dbo.StockUnits S ON S.DeliveryId = D.IdWHERE D.SourceDocumentId IN (\\\'CD49BD2A-CD45-4B9A-9A4C-3EDB1B4633BB\\\')UPDATE SSET Quantity=0,Quantityonhand = 0,logisticstatus=8FROM DHPlantStockBusinessLogicMain.dbo.Deliveries DLEFT JOIN DHPlantStockBusinessLogicMain.dbo.StockUnits S ON S.DeliveryId = D.IdWHERE D.SourceDocumentId IN (\\\'CD49BD2A-CD45-4B9A-9A4C-3EDB1B4633BB\\\'){code}""\', ""Comment 10: \'hi1. We have been tested it but can not delete it"", \'Comment 11: just only cancel2. User can not touch to DB. so\', ""Comment 12: impossible that user will delete it in DB level3. we have facing this with some Plants\'"", \'Comment 13: ""Well: # Exactly\', ""Comment 14: from application you can only cancel. That is how the application works.!image-2023-03-22-09-49-27-658.png!2 and 3Below screenshot shows two databases: Prod and Stock where information about each document is registered. If it hadn\'t been registered"", \'Comment 15: it would be not visible in other db. We can obviously see that Production Lot did not disappear just like that. As it exist still in database.!image-2023-03-22-09-52-20-908.png!""\', ""Comment 16: \'so conclusion that:1. not user delete"", ""Comment 17: this is application work?2. and you recommended that it will delete from DB side?3. and how to prevent for next time?\'"", ""Comment 18: \'{color:#0747a6}_1. not user delete"", \'Comment 19: this is application work? -_{color:#172b4d} yes\', \'Comment 20: you cannot delete document\', \'Comment 21: you may cancel it as you could see on the menu{color}{color} {color:#0747a6}_2. and you recommended that it will delete from DB side?_{color} - well\', \'Comment 22: we both agreed\', \'Comment 23: there is no option to delete it form the application{color:#0747a6}__3. and how to prevent for next time?_{color}{color:#0747a6}___{color}If there is a need because PLR is made by mistake\', ""Comment 24: just please cancel it in the application. I assume we can close this task?Regards\'"", ""Comment 25: \'thank"", ""Comment 26: please close the ticket\'"", ""Comment 27: \'Thank you.\']""]\nRelated Issues:\n[]\n\n### End'}"
231,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8801\n\n### Instruction:\nDear \r\nPlease help to check PLR 4322220323007, 4322220323006, 4322210323039, 4322210323036, 4322220323003 in Nghe An Plant (0432). \r\nThe PLRs \u200breleased to stock and automatically released out of stock after that.\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 looks like those PLR\\\'s created deliveries without any quantity.!image-2023-03-22-03-10-22-855.png!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: \'wyglada na to ze w wyniku prac z PLRem utworzono nieprawidłowe dostawy !image-2023-03-22-03-12-29-611.png!w logach nie widzę żadnych błędów z dzisiaj\'"", ""Comment 5: \'!image-2023-03-22-06-49-49-997.png!Intake i Release w przeciągu 10sekund.\'"", ""Comment 6: \' !pcs messages! \'"", ""Comment 7: \'Hi [~Hardy.huy@deheus.com],the problem is related to incorrect sending messages of production  by PCS.The api.StartProduction (informing about the start of production) and api.RegisterProductionReport (informing about the end of production with consumption information) are sent almost at the same time (at the end of production process):  !screenshot-1! This causes irregularities in the order in which these messages are processed in DHP"", \'Comment 8: which ultimately leads to zeroing out the stock of the finished product.Separating the start production and register production report messages makes sense only if the start will be sent at the beginning of the production process (the PLR and the delivery related to it will be established in the DHP)\', \'Comment 9: and the register production report at the end of the process (when the physical production process is completed and the information about the consumption and the final weight of the finished product is known). If the production information is sent only at the end of the production process\', \'Comment 10: it is enough to send api.RegisterProductionReport (it will set up the PLR with the delivery\', ""Comment 11: set the property quantity on the finished product and register the raw material consumption).\'"", ""Comment 12: \'hi,1. so what is conclusion for this? as i read from your comment that sending from PCS. but i not any change before and after update to new DHP version(8.2 to 8.5) and just some lot have issue2. and how to prevent for next time?\'"", ""Comment 13: \'My comment was intended to point out the cause of the problem and provide a solution. The cause of the problem is the incorrect sending of messages by the PCS (information about the start and end of production comes almost at the same time). The solution is to:* skip sending the start production message or * send it when the production process physically starts (the register production report message should be sent when the production process physically ends).Using one of these two ways to solve the problem will avoid errors in the future.\'"", \'Comment 14: ""It was agreed with Eric that PCS would currently stop using the method API.StartProduction.I\\\'m waiting for confirmation from Eric if this way of working will be enough for the DHVN and if the PCS can apply this change ASAP.""\', ""Comment 15: \'Agree"", ""Comment 16: so it should be close this ticket\'"", ""Comment 17: \'Thank you\'"", ""Comment 18: \'I got confirmation from Eric that PCS company changed the way they use the integration"", \'Comment 19: and now registration of PLR is based only on this one procedure. The DH VN team still should verify it with business users\', ""Comment 20: but it seems now works fine.\']""]\nRelated Issues:\n[\'DGS-8330\', \'DAP-13456\']\n\n### End'}"
232,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8800\n\n### Instruction:\nHi\r\n\r\nWe are going to shutdown the current DHP2.5/2.7 servers from plants.\r\nAll old DHP2.7 are already migrated to the new server: 10.55.9.201\r\nCaruaru, Apucarana, Guararapes and Toledo are OK! We migrated SQL DB and DHP files. All of them are operational, opening with no errors.\r\n\r\nWe also migrated DHP2.5 from Rio Claro to this new server, however when we try to open the DHP2.5 application an error message is displayed:\r\n_attached_file_\r\n\r\nOur IT team checked and the SQL version is the same from source server (10.55.9.32)\r\n\r\nI don\'t know if we need to install something on this new server to be able to open DHP2.5 with no errors.\r\nCould you please help us?\r\n\r\nThank you\n\n### Response:\n[""Comment 1: [\'!MicrosoftTeams-image (49)!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'[~mberbert@deheus.com]on new application server you are probably missing Server Management Object in correct version and probablySQLSysCLRTypes in correct version.\'"", ""Comment 4: \'Hi [~Przemyslaw.Przybyszewski@kotrak.com]You are right. After our IT team installed SMO and SQLSysCLRTypes from 2014 version"", ""Comment 5: everything worked.Thank you very much!You can close this task\'"", ""Comment 6: \'Thank you.\']""]\nRelated Issues:\n[]\n\n### End'}"
233,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8799\n\n### Instruction:\nDatacom to the Intense platform isn\'t working, all messages fail:\r\n\r\nnie można powtórnie utworzyć obiektu intensecontext. zawołaj funkcję logout() i spróbuj ponownie\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Hello,Could you specify when you get this error? Is it some message in Intense application?Could you send some screen or document when this message has shown?Regards\'"", ""Comment 3: \'It is an error we get when the datacommunication is trying to deliver any message to Intense. So not a message inside the Intense application"", ""Comment 4: en I doubt it a screenshot of our message broker system is of any help.Probably the web service part of Intense needs a reboot.\'"", ""Comment 5: \'!image!\'"", ""Comment 6: \'!image-1!\'"", ""Comment 7: \'Screenshots added.\'"", \'Comment 8: ""Hello Rob,I\\\'ve restarted Intense AgraSync service. I\\\'m waiting for possible reason of this error message and I will inform you ASAP.""\', ""Comment 9: \'I reprocessed all 110 messages with that error and almosta all are processed OK now.Exept for those in the print-screen"", \'Comment 10: they get the message ""wystąpił błąd podczas zapisu danych""!image-2!\\\'\', \'Comment 11: \\\'I get more and more of the ""wystąpił błąd podczas zapisu danych"" error\\\'\', ""Comment 12: \'this one is back as well: nie można powtórnie utworzyć obiektu intensecontext. zawołaj funkcję logout() i spróbuj ponownie\'"", \'Comment 13: ""Communication still isn\\\'t working.... still nie można powtórnie utworzyć obiektu intensecontext. zawołaj funkcję logout() i spróbuj ponownie""\', ""Comment 14: \'Synchronizer is working properly at this moment. We are verifying the cause of the error with the developers.\'"", ""Comment 15: \'Hi Tomasz"", ""Comment 16: I restarted the synchronizer 2x today. After restart it works for some time and then the errors recur.\'"", ""Comment 17: \'Hi Rob,Can we send a test packet of messages to the UAT environment? There was a big data import into Intense going on last night and that could have been the cause. We have the fix ready"", ""Comment 18: but would like to compare the results before and after installing it.\'"", ""Comment 19: \'Sure"", ""Comment 20: please do.But the problems began before last night. Yesterday morning Intense needed a restart as well.Could be there is a big import every night though.\'"", ""Comment 21: \'I asked Richard if he could send such a package to the test environment"", ""Comment 22: but there is a limitation in WebMethods and they are not able to perform such a test. So we can test the new version of the synchronizer and monitor whether it has resulted in an improvement.\'"", ""Comment 23: \'We are monitoring the status of the integration"", ""Comment 24: and at this point it looks like the problem has been resolved. Our developers team fixed several automatic actions that could cause deadlock on the SQL database.\'"", ""Comment 25: \'The problem has not returned tonight. I looked at the logs and everything looks good.\'"", ""Comment 26: \'The issue has been fixed on our side. Please"", ""Comment 27: verify if it is working fine for you and let us know if we can close this task.Regards\'"", ""Comment 28: \'After a week everything is still working fine"", ""Comment 29: the ticket can be closed.Thanks for the support,Rob.\']""]\nRelated Issues:\n[]\n\n### End'}"
234,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8798\n\n### Instruction:\nThe users who need to approve a PI need to be able to adjust the BP tax-group.\r\n\r\nNow it is only possible to send it back to entry. It is more efficient if the approver can adjust it right away.\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 has been adjusted in the system in all sectors.Now when PI document is in the state\\\'Waiting for approval\\\' it\\\'s also possible to change BP TAX Group on PI elements.It\\\'s done on test and production environment.Please verify and confirm that it\\\'s working properly.""\', ""Comment 4: \'This can be closed.\']""]\nRelated Issues:\n[]\n\n### End'}"
235,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8797\n\n### Instruction:\nFor at least two realised intakes from barges we have the data in DHC but it is missing in Webmethods/Milas. \r\n\r\n- Can you please check why the data was not exported from DHC to Milas?\r\n- Can you export the data from DHC to Milas (again)?\r\n- How can we check if data was exported? Can we export the data ourselves again\r\n\r\nVeghel:  CL000023714\r\nMaasbracht: CL000024184\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: \'!image-2023-03-21-11-28-29-901.png!\'"", ""Comment 4: \'!image-2023-03-21-11-36-34-915.png!\'"", ""Comment 5: \'Dear Bob,On our side I can see document are correctly mapped and sent to Milas. Please"", ""Comment 6: let me know what documents should be resent? Shipping Noticed or VTs or both?Regards\'"", \'Comment 7: ""Hello Aleksandra\', \'Comment 8: please resent the VT\\\'sAnd can you show me where I can check if data was sent from DHC to Milas?""\', \'Comment 9: ""I have resent VTs to Milas\', \'Comment 10: please verify if they arrived.Tocheck if data was sent from DHC to Milas\', ""Comment 11: I\'m running sql query under db. If DHC ID of the document has ERP id assigned"", \'Comment 12: that means data was sent.Regards""\', ""Comment 13: \'Goodmorning"", ""Comment 14: thank you for the explanatin. The intake data is now available in Milas. This ticket can be closed.\'"", ""Comment 15: \'Thank you Bob,Regards\']""]\nRelated Issues:\n[]\n\n### End'}"
236,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8796\n\n### Instruction:\nDHC doesn\'t accept messages;\r\n\r\nThe original error was an error occurred while updating the entries. see the inner exception for details\r\n\r\n\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Apparently a SQL log disk was full. Ticket can be closed.\'"", ""Comment 3: \'The service has been restarted"", ""Comment 4: Thank you for your patienceCould you verify and please give us a feedback.Regards\'"", ""Comment 5: \'DHC is working properly now.Thanks for the support.\']""]\nRelated Issues:\n[]\n\n### End'}"
237,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8795\n\n### Instruction:\nAsked : Change Main Target and customer of invoice: ESI.04.02.2023.VEXP to 0674 \r\n\r\nbut ESI.04.03.2023.VEXP has been changed\r\n\r\n(See also DGS-8672)\r\n\r\n\r\n\n\n### Response:\n[""Comment 1: [\'[^cz esi.04.02.2023.vexp.pdf] _(96 kB)_!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: \'Yes"", \'Comment 4: I agree\', ""Comment 5: my mistake. Could you please confirm customer code 5132 on document ESI.04.03.2023.VEXP to revert changes?\'"", ""Comment 6: \'Customer data has been changed on ESI.04.02.2023.VEXP!image-2023-03-21-09-28-27-074.png!\'"", ""Comment 7: \'Yes. Customer code 5132 on document ESI.04.03.2023.VEXP to revert changes\'"", ""Comment 8: \'Reverted:!image-2023-03-21-10-05-28-745.png!Once again"", ""Comment 9: I apology for my mistake.Reagrds\'"", ""Comment 10: \'Ticket can be closed\'"", ""Comment 11: \'[~asysta@kotrak.pl] a dlaczego ten ma przypisane account Rio Claro?\']""]\nRelated Issues:\n[]\n\n### End'}"
238,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8794\n\n### Instruction:\nHello, \r\nI have found a difference in data between DHC and DHP. Some shipping notices in DHC have status \'Accepted\' while in DHP the status is \'Cancelled\'. See the example in the attachments. Can you please look at it. The status should be accepted in DHP.\n\n### Response:\n[""Comment 1: [\'!Schermafbeelding 2023-03-20 163115!!Schermafbeelding 2023-03-20 163141!\'"", ""Comment 2: \'Hello,Kindly approve lowering priority of this task to P2 as P1 issues are only those with a critical or a blocking impact on business processes . This seems not to be the case in this issue so we suggest decreasing the issue priority.Regards\'"", ""Comment 3: \'Additionally"", \'Comment 4: you are comparing Shipping Notice Header view in DHC to Shipping Notice Elements view in DHP. The numbers of ASNs are not corresponding. You are showing elements which can be deleted\', ""Comment 5: that is why element is cancelled. Could you also please clarify why execution date is so far from present?!image-2023-03-20-17-12-06-888.png!\'"", ""Comment 6: \'Hello [~TKleinAvink@deheus.com],the execution date of the accepted trip is set to 1/1/1900 (this date is used in case of manually added trip in Milas).To display documents with that date"", ""Comment 7: you need to change the date range in the date filter. After that all documents will be displayed. !TRIP_headers!  !TRIP_Element view! \'"", \'Comment 8: ""Hi Aleksandra\', \'Comment 9: we have multiple cases in which the data in DHC and DHP doesn\\\'t seem to match. Will provide some extra cases today. Especially for Utrecht plant we see SN\\\'s in DHC that are not in DHP. ""\', ""Comment 10: \'Hi Theo,But should it really be P1 task? Please confirm.Waiting for your examples thenRegards\'"", \'Comment 11: ""You can leave it to P2\', ""Comment 12: but the situation is really concerning me. For example SN L000160259 is in DHC but not in DHP. In DHC there are dozens of cancelled trips and one with status accepted. But this one I cannot see in DHP...I am investigating why there are dozens of cancelled SN\'s"", \'Comment 13: but the one that is accepted should be in DHP""\', ""Comment 14: \'Thank you\'"", ""Comment 15: \'Ola"", ""Comment 16: Can you also share these with Maciej Dobrzanski? Perhaps you can share the files with me where you receive so many cancelled statusses?\'"", ""Comment 17: \'Problem jest z tym"", ""Comment 18: że po external number!image-2023-03-21-11-56-07-231.png!A dokładnie!image-2023-03-21-11-56-38-043.png!\'"", \'Comment 19: ""Sure Theo\', ""Comment 20: I\'m in constant conatct with Maciej :)when we find something"", \'Comment 21: we will let you know""\', \'Comment 22: ""Let\\\'s start with the one accepted regarding SN L000160259\', \'Comment 23: it is for Plant Andel and we can see it in Andel:!image-2023-03-21-12-22-53-207.png!!image-2023-03-21-12-22-07-271.png!We are checking with dev team what happened that so many SNs have status cancelled. Under DB I can see 347 documents with external number7_L000160259 but they have different SN number:!image-2023-03-21-12-34-03-614.png!""\', ""Comment 24: \'The same in plant!image-2023-03-21-12-36-59-513.png!\'"", ""Comment 25: \'I think it is the matter of Milas"", ""Comment 26: could you please check with them?Regards :)\'"", ""Comment 27: \'!image-2023-03-21-13-42-13-766.png!!image-2023-03-21-13-42-13-766!\'"", \'Comment 28: ""I see the Andel part is indeed in DHP but the Utrecht part of this SN still isn\\\'t(And again multiple cancelations. Perhaps it has something to do with two factories on one SN)!image!""\', ""Comment 29: \'I do not know what is going on but now it is cancelled ...!image-2023-03-21-14-27-49-363.png!\'"", ""Comment 30: \'!image-2023-03-21-14-41-32-523.png!\'"", ""Comment 31: \'Dear Theo,Do you have any trigger / procedure on Milas db? What I could notice is that ASNs related to document 7_L000160259 duplicate every 30 minutes (there are 13 duplicated every 13 minutes that arrive to our apps with status cancelled)I have restarted Business Platform"", ""Comment 32: but this does not help. Did something unusual happened yesterday?!image-2023-03-21-15-01-05-082.png!!image-2023-03-21-15-01-42-448.png!\'"", ""Comment 33: \'Wygląda na temat jak ten - https://helpdesk.kotrak.com/browse/DGS-8613\'"", ""Comment 34: \'Hi,Can we close this task?Regards\'"", ""Comment 35: \'Hi,Can we close this task?Regards\'"", ""Comment 36: \'Hi"", \'Comment 37:  Yes\', \'Comment 38: you can close this ticket.  | |{color:#000001} Kindregards,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Toon{color} |{color:#000001} {color} |{color:#000001} KleinAvink{color} | | | | |{color:windowtext}{color} !image001! <[https://www.deheus.com/]> | |  *{color:#006FB7} *DEHEUSANIMALNUTRITIONB.V.*{color}* | | | |{color:#000001} P.O.Box396 6710BJEde TheNetherlands{color} | |{color:#000001} Rubensstraat175 6717VEEde TheNetherlands{color} | |{color:#000001} CoC16011201{color} |   _{color:#000001} _Thise‑mailmessageanditsattachmentsaresubjecttothedisclaimer_ _publishedonthewebsiteof_{color}_{color:#000001} _+{color}[{color:#000001}{color}{color:#000001} _+ DeHeusAnimalNutrition+_{color}{color:#000001} {color}|https://www.deheus.com/disclaimer]{color:#000001} {color}+__{color:#000001} _._{color}_ | | !image002! <[https://www.facebook.com/deheusanimalnutrition]> | | !image003! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]> | | !image004! <[https://www.linkedin.com/company/royal-de-heus/mycompany/]> | | !image005! <[https://www.instagram.com/de_heus_animal_nutrition/]> |        *Van:* Aleksandra Przybyłek (Jira) <jira@kotrak.com>   *Verzonden:* dinsdag 25 april 2023 11:17  *Aan:* Klein Avink\', ""Comment 39: Toon <TKleinAvink@deheus.com>  *Onderwerp:* DGS-8794 Wrong data DHP shipping notices   \']""]\nRelated Issues:\n[]\n\n### End'}"
239,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8793\n\n### Instruction:\nWe have problem to close VT-1594, system shows an error message ""warehouse dispatch should be in progress..."" and not allow to close, checking the WO(PD)-225 we see the number 3 is duplicated, we know the VT was loaded by 2 different user, but system should allow.\r\n\r\nCould you check why we still have this error?\r\n\r\nThank you\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'!image-2023-03-22-14-33-03-009.png!\'"", ""Comment 3: \'!image-2023-03-22-14-35-06-118.png!\'"", ""Comment 4: \'!image-2023-03-22-14-50-15-811.png!\'"", ""Comment 5: \'Hej,[~maciej.dobrzanski@kotrak.com]prosimy o wsparcie i / lub wskazówki. Zastanawiamy się"", \'Comment 6: czy to nie podobny kejs: https://helpdesk.kotrak.com/browse/GDC-588,https://helpdesk.kotrak.com/browse/DHITS-571Tylko wygląda bardziej tak\', ""Comment 7: że dwóch userów w tym samym czasie robiło WD. System to obsługuje?\'"", ""Comment 8: \'Po konsultacji z [~aleksandra.masternak@kotrak.com] wnioski są następujące:GDC-588 miało właśnie na celu rozwiązanie problemu problemu przez ich samych na poziomie weba.To co powinni zrobić to wejść na web i usunąć sobie niepotrzebne WO.Co do odpowiedzi na pytanie czy system obsługuje realizacje przez dwóch użytkowników odpowiedź brzmi tak. Natomiast jeżeli cokolwiek pójdzie nie tak (np. użytkownik wyjdzie z tego elementu nie robiąc nic) to musi ręcznie poprawić to za pomocą nowej funkcjonalności z GDC-588\'"", ""Comment 9: \'Hi,It has been solved under GDC-588. You should be able to remove / cancel unwanted WO from the application level. It seems both users did the same WO simultaneously.Regards\'"", ""Comment 10: \'Hi,Can we close this task?Regards\'"", ""Comment 11: \'Hi,It has been solved underGDC-588. You should be able to remove / cancel unwanted WO from the application level. It seems both users did the same WO simultaneously.Regards\']""]\nRelated Issues:\n[\'DGS-8786\']\n\n### End'}"
240,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8792\n\n### Instruction:\nwe have problem in barcode 89-w00IPW, system is showing reservation but we don\'t have it on VT.\r\nCould you please remove this reservation?\r\n\r\nThank you\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Dear Priscyla,I have removed reservation. Please"", ""Comment 3: verify if this is fine for you.Regards\'"", ""Comment 4: \'The barcode is not available yet"", ""Comment 5: could you check it again?!image!\'"", ""Comment 6: \'Please"", ""Comment 7: check now!image-2023-03-20-18-26-20-606.png!\'"", ""Comment 8: \'now the status is correct but is still with reservation!image-1!\'"", ""Comment 9: \'we need to load this barcode to VT-1603"", \'Comment 10: so the reservation is correct\', ""Comment 11: but the barcode is not inside of WO(PD)-243/3/23. Could you remove reservation to be possible do the process again or could you add the barcode to VT?\'"", ""Comment 12: \'We are checking\'"", ""Comment 13: \'I think the best way would be to scan this barcode again. Please"", ""Comment 14: let me know.Regards\'"", ""Comment 15: \'[[DHP 3.0] Stocktaking - Reserved StockUnits"", \'Comment 16: rezerwacja na stockach\', ""Comment 17: wisi rezerwacja|onenote:https://kotrak.sharepoint.com/sites/erpasysta/Shared%20Documents/Baza%20wiedzy/Baza%20Wiedzy%20-%20ERPSD/Klienci/DEHEUS/DEHEUS%20APPLICATIONS/Brazil/Baza%20wiedzy.one#%5bDHP%203.0%5d%20Stocktaking%20-%20Reserved%20StockUnits,%20rezerwacja%20na&section-id=\\\\\\\\{05DF1439-683C-45FE-8260-61E2EC66DC91}&page-id=\\\\\\\\{F85E69B9-BC0D-4FAA-BDC2-3E89CD2E4917}&end] ([Widok sieci Web|https://kotrak.sharepoint.com/sites/erpasysta/_layouts/OneNote.aspx?id=%2Fsites%2Ferpasysta%2FShared%20Documents%2FBaza%20wiedzy%2FBaza%20Wiedzy%20-%20ERPSD&wd=target%28Klienci%2FDEHEUS%2FDEHEUS%20APPLICATIONS%2FBrazil%2FBaza%20wiedzy.one%7C05DF1439-683C-45FE-8260-61E2EC66DC91%2F%5BDHP%203.0%5D%20Stocktaking%20-%20Reserved%20StockUnits%2C%20rezerwacja%20na%7CF85E69B9-BC0D-4FAA-BDC2-3E89CD2E4917%2F%29])\'"", ""Comment 18: \'[Reservation"", \'Comment 19: Stocks\', ""Comment 20: Quantity on Hand. Różnie między modułami Stock i WMS.|onenote:https://kotrak.sharepoint.com/sites/erpasysta/Shared%20Documents/Baza%20wiedzy/Baza%20Wiedzy%20-%20ERPSD/Klienci/DEHEUS/DEHEUS%20APPLICATIONS/Brazil/Inwentaryzacja.one#Reservation,%20Stocks,%20Quantity%20on%20Hand.%20R%C3%B3%C5%BCnie%20mi%C4%99dzy%20modu%C5%82ami%20Stock%20i&section-id=\\\\\\\\{87963DA7-8D11-444D-B57D-B0C598028B43}&page-id=\\\\\\\\{D86D273B-BA75-442A-A9A5-71F8BC14A5F8}&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%2FInwentaryzacja.one%7C87963DA7-8D11-444D-B57D-B0C598028B43%2FReservation%2C%20Stocks%2C%20Quantity%20on%20Hand.%20R%C3%B3%C5%BCnie%20mi%C4%99dzy%20modu%C5%82ami%20Stock%20i%7CD86D273B-BA75-442A-A9A5-71F8BC14A5F8%2F%29])\'"", ""Comment 21: \'Dear [~psilva@deheus.com] Please"", \'Comment 22: ignore my last comment. Please\', ""Comment 23: let me know if now it is fine!image-2023-03-20-19-40-15-962.png!\'"", ""Comment 24: \'Hello"", \'Comment 25: now we loaded the barcode. You can close this task\', ""Comment 26: thank you.\'"", ""Comment 27: \'Thank you\'"", ""Comment 28: \'Ta sama sytuacja"", ""Comment 29: która została opisana w RCA:https://helpdesk.kotrak.com/browse/DGS-8715?focusedCommentId=1110190&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-1110190 !screenshot-1! \'"", ""Comment 30: \'The issue will be resolved in the GDC-849 (competitive handling).\']""]\nRelated Issues:\n[\'DGS-8715\']\n\n### End'}"
241,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8791\n\n### Instruction:\nnie można rozliczyć konta 238-04. \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: \'Positions have been settled"", ""Comment 4: please verify\'"", ""Comment 5: \'Could you please confirm if we can close this task?Regards\'"", ""Comment 6: \'Is correct. You can close this task. Thank you\']""]\nRelated Issues:\n[]\n\n### End'}"
242,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8790\n\n### Instruction:\nDears,\r\n\r\nin Order no. SO-23010380/3/23/KKF how come user was able to make dispatch for item 5335-B50 of 3,500KG while order QTY is only 2,500KG.\r\n\r\nit looks like there is no deviation control. \r\nplease check and advise.\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'!image-2023-03-21-07-32-54-091.png!\'"", ""Comment 4: \'!screenshot-1!\'"", ""Comment 5: \'!image-2023-03-21-11-07-13-521.png!\'"", ""Comment 6: \'!image-2023-03-21-11-08-14-777.png!!image-2023-03-21-11-08-47-801.png!\'"", ""Comment 7: \'Hi,The order elements has been used on two different VT documents!image-2023-03-21-11-11-12-597.png!Both of them are closed:!image-2023-03-21-11-11-36-597.png!\'"", ""Comment 8: \'Deviation control works but onWO(PD). Regards\'"", ""Comment 9: \'!image-2023-03-21-11-14-33-844.png!!image-2023-03-21-11-13-28-011.png!!image-2023-03-21-11-13-44-916.png!!image-2023-03-21-11-14-02-129.png!\'"", ""Comment 10: \'Hi,Is there anything else we can do for you?Regards\'"", ""Comment 11: \'Hi,Can we close this task?Regards\']""]\nRelated Issues:\n[]\n\n### End'}"
243,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8789\n\n### Instruction:\n don\'t see the purchase invoices on the round, it does have an ERP number\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: ""!image001!{color:black}{color} {color:black}{color} {color:black}It is this one{color} {color:black}{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} 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}!image002!{color:black} <[https://www.de-heus.nl/]>{color} | |  *{color:#006FB7} *DEHEUSVOEDERSB.V.*{color}* | | | |{color:#000001} Postbus396 6710BJEde \\\\u200b{color} | |{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} | | |{color:#000001} 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}_ | | !image003! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | | !image004! <[https://twitter.com/de_heus_voeders]>{color:black}{color} | | !image005! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image006! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} |        *Van:* De Heus Global Service Desk <jira@kotrak.com>   *Verzonden:* maandag 20 maart 2023 09:28  *Aan:* Dam\', ""Comment 4: Nancy van <NDam@deheus.com>  *Onderwerp:* DGS-8789 I don\'t see the purchase invoice on the round"", \'Comment 5: it does have an ERP Nummer   ""\', \'Comment 6: ""{color:black}Hello,{color} {color:black}{color} {color:black}It is not the one I have sendt but this one{color} {color:black}{color} !image001!{color:black}{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} 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}!image002!{color:black} <[https://www.de-heus.nl/]>{color} | |  *{color:#006FB7} *DEHEUSVOEDERSB.V.*{color}* | | | |{color:#000001} Postbus396 6710BJEde \\\\u200b{color} | |{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} | | |{color:#000001} 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}_ | | !image003! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | | !image004! <[https://twitter.com/de_heus_voeders]>{color:black}{color} | | !image005! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image006! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} |        *Van:* Adrian Kozak (Jira) <jira@kotrak.com>   *Verzonden:* maandag 20 maart 2023 09:30  *Aan:* Dam\', ""Comment 7: Nancy van <NDam@deheus.com>  *Onderwerp:* DGS-8789 I don\'t see the purchase invoice on the round"", \'Comment 8: it does have an ERP Nummer   ""\', ""Comment 9: \'Hello,This PI is not on the round because there is no scenario implemented in system for that kind of invoices for Expenses.System displays these scenarios on the Round and Financial Statement.Is this PI correct? Maybe it should be booked on one side?!image-2023-03-20-10-25-44-631.png!Regards\'"", \'Comment 10: ""{color:black}Yes it should be booked on one side{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} 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:* Damian Świstek (Jira) <jira@kotrak.com>   *Verzonden:* maandag 20 maart 2023 10:28  *Aan:* Dam\', ""Comment 11: Nancy van <NDam@deheus.com>  *Onderwerp:* DGS-8789 I don\'t see the purchase invoice on the round"", \'Comment 12: it does have an ERP Nummer   !image006-1!!image006!""\', \'Comment 13: ""Should we marked this checbox \\\'Booked on one side\\\'?Do you know why it is not marked?""\', \'Comment 14: ""{color:black}Yes{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} 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:* Damian Świstek (Jira) <jira@kotrak.com>   *Verzonden:* maandag 20 maart 2023 10:59  *Aan:* Dam\', ""Comment 15: Nancy van <NDam@deheus.com>  *Onderwerp:* DGS-8789 I don\'t see the purchase invoice on the round"", \'Comment 16: it does have an ERP Nummer   !image006!""\', \'Comment 17: ""I\\\'ve changed it\', \'Comment 18: now it\\\'s visible on Round.Please confirm that is correct right now and we can close task.!image-2023-03-20-11-22-52-291.png!!image-2023-03-20-11-22-33-725.png!""\', \'Comment 19: ""{color:black}Yes is correct you can close the task{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} 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:* Damian Świstek (Jira) <jira@kotrak.com>   *Verzonden:* maandag 20 maart 2023 11:32  *Aan:* Dam\', ""Comment 20: Nancy van <NDam@deheus.com>  *Onderwerp:* DGS-8789 I don\'t see the purchase invoice on the round"", \'Comment 21: it does have an ERP Nummer   !image006-2!!image007!!image006!""]\']\nRelated Issues:\n[]\n\n### End'}"
244,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8788\n\n### Instruction:\nDears,\r\n\r\nVT 482/3/23 is in DHC and not in ERP.\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: \'ok"", \'Comment 4: also the VT no. 487/3/23 have the same issue\', ""Comment 5: it is clear that all POR for this item is not working.\'"", ""Comment 6: \'!image-2023-03-20-10-00-51-902.png!\'"", ""Comment 7: \'Please verify.\'"", ""Comment 8: \'Both VTs are not in ERP\'"", ""Comment 9: \'Marta wygląda to a ten sam przypadek co tutaj :https://helpdesk.kotrak.com/browse/DGS-6852logi z dhc serviceOB1\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.PlatformApplication\\\\\\\\Application.cs:102] - DHCERPService Client Bootstrapper found [Evolution.DHCERPService.EGWebServiceClient.Bootstrapper]2023-03-20 10:59:06,082 [1] INFO Evolution.DHCERPService.PlatformApplication.Application [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\152764417\\\\\\\\DHAPPSV3-DHCER-JOB1\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.PlatformApplication\\\\\\\\Application.cs:110] - DHCERPService Registering completed2023-03-20 10:59:08,254 [1] INFO Evolution.DHCERPService.PlatformApplication.Application [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\152764417\\\\\\\\DHAPPSV3-DHCER-JOB1\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.PlatformApplication\\\\\\\\Application.cs:119] - DHCERPService Started2023-03-20 10:59:19,007 [16] ERROR Evolution.DHCERPService.Service.BaseQuery`2 [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\152764417\\\\\\\\DHAPPSV3-DHCER-JOB1\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.Service\\\\\\\\BaseQuery.cs:85] - System.Exception: Not all vehicle ticket elements are present.\'"", ""Comment 10: \'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 11: \'!image-2023-03-20-15-03-16-847.png!\'"", \'Comment 12: ""--update vehicletickets--set ExpectedIntakeElementsQuantity=1\', \'Comment 13: ExpectedDispatchElementsQuantity=0--where DocumentNumber like \\\'%482/3/2023%\\\'""\', \'Comment 14: ""[~przemyslaw.przybyszewski@kotrak.com]prośba o pomoc z vt 482/3/2023select ExpectedElementsQuantity\', ""Comment 15: ExpectedIntakeElementsQuantity,ExpectedDispatchElementsQuantity,* from vehicletickets where DocumentNumber like \'%482/3/2023%\' or DocumentNumber like \'%487/3/2023%\'dla obu błedy ale expected quantity sie zgadza.W bazie pośredniej jest item"", \'Comment 16: order i order element2023-03-21 00:05:39,013 [112] ERROR Evolution.DHCERPService.MessageSender.Actors.ClientServiceCallActor [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\152764417\\\\\\\\DHAPPSV3-DHCER-JOB1\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.MessageSender\\\\\\\\Actors\\\\\\\\ClientServiceCallActor.cs:86] - Message with command PurchaseOrderReceiptSave and object id 376563a9-769e-488a-8075-8ec9abdddc30 couldn\\\'t be processed. Exception occured:2023-03-21 00:05:39,013 [112] ERROR Evolution.DHCERPService.MessageSender.Actors.ClientServiceCallActor [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\152764417\\\\\\\\DHAPPSV3-DHCER-JOB1\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.MessageSender\\\\\\\\Actors\\\\\\\\ClientServiceCallActor.cs:87] - System.Exception: Internal server error. Problems witch getting object from database. at Evolution.DHCERPService.Service.BaseQuery`2.GetById(Guid Id) in E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\152764417\\\\\\\\DHAPPSV3-DHCER-JOB1\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.Service\\\\\\\\BaseQuery.cs:line 89 at Evolution.DHCERPService.EGWebServiceClient.Commands.PurchaseOrderReceiptSaveCommand.Execute(Guid id) in E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\152764417\\\\\\\\DHAPPSV3-DHCER-JOB1\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.EGWebServiceClient\\\\\\\\Commands\\\\\\\\PurchaseOrderReceiptSaveCommand.cs:line 42 at Evolution.DHCERPService.MessageSender.Actors.ClientServiceCallActor.CallClientService(ObjectChangedMessage message) in E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\152764417\\\\\\\\DHAPPSV3-DHCER-JOB1\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.MessageSender\\\\\\\\Actors\\\\\\\\ClientServiceCallActor.cs:line 592023-03-21 00:05:49,216 [132] ERROR Evolution.DHCERPService.Service.BaseQuery`2 [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\152764417\\\\\\\\DHAPPSV3-DHCER-JOB1\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.Service\\\\\\\\BaseQuery.cs:85] - System.Exception: Not all vehicle ticket elements are present.""\', ""Comment 17: \'[~agnieszka.januszewska@kotrak.com]skontaktuj się ze mną jak będziesz w pracy to obydwoje na to popatrzymy.\'"", ""Comment 18: \'Please check now.\'"", ""Comment 19: \'yes all is in ERP"", ""Comment 20: thanks!\']""]\nRelated Issues:\n[\'DGS-8962\', \'DGS-8936\']\n\n### End'}"
245,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8787\n\n### Instruction:\nHi\r\n\r\nWe need to migrate old DHC data from 10.55.9.25/10.55.9.32 server to new server: 10.55.9.201\r\n\r\nIn this new server we already have MSSQL SERVER installed and DHP 2.5/2.7 already migrated to this server.\r\n\r\nThe only thing that needs to be transported to it is the old DHC which has data before feb/2020.\r\n\r\nCould you please make this migration?\r\n\r\nThank you very much\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Please be informed that we have forwarded the issue to the development team in order to internal analysis.We are waiting for more details and will be back with further information as soon as possible.\'"", ""Comment 3: \'Dear Maicon,Could you please clarify?Server with ip10.55.9.32 is Rio Claro sql server before upgrade to DHP 3.0Is10.55.9.25 DHC server? Since I have been workin for Kotrak"", ""Comment 4: old DHC server was172.30.5.3. Did you have any older server?Wil server10.55.9.201 be a new DHC server? Or will it be just for your use?Regards\'"", ""Comment 5: \'Hi [~aleksandra.przybylek@kotrak.com]Plans have changed.You can cancel this task.Thank you\'"", ""Comment 6: \'Hi [~mberbert@deheus.com].Sure. Thank you for information\']""]\nRelated Issues:\n[]\n\n### End'}"
246,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8786\n\n### Instruction:\nWe have problem to close VT-1594, system shows an error message ""warehouse dispatch should be in progress..."" and not allow to close, checking the WO(PD)-225 we see the number 3 is duplicated, we know the VT was loaded by 2 different user, but system should allow.\r\n\r\nCould you check why we still have this error?\r\n\r\nThank you\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 3: "" !screenshot-1! {code:java}  FROM [DHPlantWmsBusinessLogicMain].[dbo].[WarehouseDispatches] where Documentin(\\\'WD-1964/3/23\\\',\\\'WD-1976/3/23\\\'){code}""\', ""Comment 4: \'!image-2023-03-17-20-30-18-036.png! We have changed status of this item to canceled.Please verify if it is ok.Please give us a feedback.\'"", ""Comment 5: \'Łukasz,we are trying to close VT"", ""Comment 6: but do you know why we have this error?\'"", ""Comment 7: \'Unfortunately"", \'Comment 8: the cause of the problem is unknown.In this task we have focused on clearingandunblocking the process.If there is a need from your sideto investigate the reasonof the issue\', \'Comment 9: we may raise RootCause Analysis (RCA)task for you.Please\', ""Comment 10: let us knowhow you wish us to proceed.\'"", ""Comment 11: \'Hi Łukasz ,yes"", \'Comment 12: we need a RCA\', \'Comment 13: could you create? You can close this task\', ""Comment 14: thank you.\'"", ""Comment 15: \'The RCA is underDGS-8793. Please check if you have access.Regards\']""]\nRelated Issues:\n[\'DGS-8793\']\n\n### End'}"
247,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8785\n\n### Instruction:\nwe have problem with reservation for unit load 89-W00G9U, it\'s not loaded in VT, but is reserved. We need use urgent. Could you please check and fix it?\r\n\r\nThank you\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Reservation has been removed "", ""Comment 4: please check and send a feedback. !screenshot-1! \'"", ""Comment 5: \'Hi Piotr,now is correct. Thank you.\']""]\nRelated Issues:\n[\'DGS-8715\']\n\n### End'}"
248,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8784\n\n### Instruction:\nHi\r\n\r\nI\'d like to have a quick meeting with you to understand the purpose of LogicEvents/Intercontext/Main databases\r\n\r\nI suppose that Main is where main data is stored\r\nI also think that LogicEvents will be used for logs functionality in 8.6 version\r\nBut Intercontext I don\'t have no idea\r\n\r\nCold you please schedule a meeting to explain it?\r\n\r\nThank you\n\n### Response:\n[""Comment 1: [\'!image-1!\'"", ""Comment 2: \'[~asysta@kotrak.pl] temat do mnie możecie przypisać.\'"", ""Comment 3: \'[~marcin.kleszcz@kotrak.com]ze mną jak z dzieckiem"", ""Comment 4: mówisz i masz :P\'"", ""Comment 5: \'Dear Maicon,I have received the information from Marcin that the issue has been discussed. Please"", ""Comment 6: let me know if I can close this task.Regards\'"", ""Comment 7: \'Hi AleksandraAfter our meeting I understand the purpose of Events and Intercontext databases"", ""Comment 8: and they will not be inserted in the backup routine.Now we must define which database is going to be included in our backup routine.Could you please inform what Type of backup we need to make for each database?||Databases||Type|||DHPlantAuthBusinessLogicMain|Full ?||DHPlantIntegrationDhcServiceIdentityMapping|Incremental ?||DHPlantIntegrationDhcServiceInternalStorage|...?||DHPlantIntegrationLabEquipmentInternalStorage| ||DHPlantIntegrationWeightbridgeInternalStorage| ||DHPlantIntegrationWeightbridgeMain| ||DHPlantMaintBusinessLogicMain| ||DHPlantMaintBusinessLogicMainAttachmentStorage| ||DHPlantPCSBusinessLogicMain| ||DHPlantPCSBusinessLogicMain2| ||DHPlantPrintoutMain| ||DHPlantProdBusinessLogicMain| ||DHPlantQAMBusinessLogicMain| ||DHPlantStockBusinessLogicMain| ||DHPlantVCBusinessLogicMain| ||DHPlantWmsBusinessLogicMain| ||master| ||ReportServer| ||ReportServerTempDB| |Thank you very much!\'"", ""Comment 9: \'Wstępnie mamy spotkanie wewnętrzne w tym temacie 03.04.2023. Więc w kolejnym tygodniu odpowiemy.\'"", \'Comment 10: ""Hi [~marcin.kleszcz@kotrak.com] [~maciej.dobrzanski@kotrak.com]Could you please check my last comment?We are having too much power supply issues on the factories because of storm/rain season. We are waiting your answer to fix backup routine and I\\\'m afraid of one of these power supply issues to crash our databases and we don\\\'t have the right backup files.Thank you very much""\', ""Comment 11: \'Hi [~Marcin.Kleszcz@kotrak.com] [~Maciej.Dobrzanski@kotrak.com]Thank you for the feedback!You can close this task\'"", ""Comment 12: \'Thank you\'"", ""Comment 13: \'[~mberbert@deheus.com]as we have discussed last Thursday evening - 06.04.2023. You need to identify your backup and recovery requirements.I think"", \'Comment 14: that the best way is the meeting with you (and Ludemila) and Kotrak (Maciej and our IT manager) to discuss the best practice\', ""Comment 15: if you need of course.\']""]\nRelated Issues:\n[\'DGS-8774\']\n\n### End'}"
249,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8783\n\n### Instruction:\nThe attached POR will not generate manually, i believe it has to do with the error message attached but kindly find attached the POR in DHC.\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Hi"", ""Comment 4: Purchase order PO-127/2023 realted with this vehicle ticket is already executed. Some of POR dokuments has been made by user not by erp integrator for example: !screenshot-1! \'"", ""Comment 5: \'ok please close\']""]\nRelated Issues:\n[]\n\n### End'}"
250,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8782\n\n### Instruction:\nActions not visible under button.\r\nDocument should be on round 017518/0005/0002\r\nID 106897\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Hi [~CJong@deheus.com],the action is not avaliable"", \'Comment 4: because the document is not in ""Archive"" status.I changed the round number on this PI. You can verify it.Best regards,Grzegorz\\\'\', ""Comment 5: \'{color:black}Thanks so much. Sorry I saw posting was just made.{color} {color:black}Thanks for moving to next round.{color}  {color:black}Is Bert still able to approve?{color} {color:black}{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Christinede{color} |{color:#000001} {color} |{color:#000001} Jong{color} |  {color:#000001}MedewerkerContractadministratie{color} | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.de-heus.nl/]>{color} | |  *{color:#006FB7} *DEHEUSVOEDERSB.V.*{color}* | | | |{color:#000001} Postbus396 6710BJEde \\\\u200b{color} | |{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} | | |{color:#000001} T:0318675567{color} |  {color:#000001}KvK14626985{color}   _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | | !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | | !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} | | !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} |        *Van:* Grzegorz Materla (Jira) <jira@kotrak.com>   *Verzonden:* vrijdag 17 maart 2023 11:43  *Aan:* Jong"", ""Comment 6: Christine de <CJong@deheus.com>  *Onderwerp:* DGS-8782 Not able to move document to next round   \'"", ""Comment 7: \'[~CJong@deheus.com],can we close the task?Best regards,Grzegorz\'"", ""Comment 8: \'{color:black}Yes please.{color} {color:black}Have a good weekend.{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Christinede{color} |{color:#000001} {color} |{color:#000001} Jong{color} |  {color:#000001}MedewerkerContractadministratie{color} | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.de-heus.nl/]>{color} | |  *{color:#006FB7} *DEHEUSVOEDERSB.V.*{color}* | | | |{color:#000001} Postbus396 6710BJEde \\\\u200b{color} | |{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} | | |{color:#000001} T:0318675567{color} |  {color:#000001}KvK14626985{color}   _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | | !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | | !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} | | !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} |        *Van:* Grzegorz Materla (Jira) <jira@kotrak.com>   *Verzonden:* vrijdag 17 maart 2023 12:18  *Aan:* Jong"", ""Comment 9: Christine de <CJong@deheus.com>  *Onderwerp:* DGS-8782 Not able to move document to next round   \'"", \'Comment 10: ""Thank you\', \'Comment 11: also\', \'Comment 12: have a nice weekend.I\\\'m closing the task.Best regards,Grzegorz""]\']\nRelated Issues:\n[]\n\n### End'}"
251,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8781\n\n### Instruction:\nj.w.\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: \'What kind of internal analysis? We only want to know how it works in DHC 3.0:)\'"", \'Comment 3: ""It\\\'s just a ready info\', \'Comment 4: that the task is passed to dev :)""\', ""Comment 5: \'[~ewardega@deheus.com]cost of training including the upfront checking of the environment and its configuration is 4h. Please let me know whether this cost is acceptable.\'"", ""Comment 6: \'It works with DHP 3.0 in other countries"", \'Comment 7: there is one DHC so what do you you want to check? and for 4h? we have the newest version for ERP interator\', ""Comment 8: it was already checked and tested by yourselves and paid by us. Could you specyfi more details\'"", \'Comment 9: ""date 10.04-14.04 it\\\'s OK for us\', \'Comment 10: we can accept the term!image!""\', ""Comment 11: \'Tematem szkolenia jest obsługa kierowców i samochodów w DHC3.0"", \'Comment 12: z maila zrozumiałem\', ""Comment 13: że działa Wam tylko spod bazy. Zatem musimy zweryfikować jak środowisko zostało skonfigurowane i przygotować dane do szkolenia.\'"", ""Comment 14: \'Ale to nie chodzi tylko o środowisko testowe"", \'Comment 15: ale generalnie o tą funkcjonalność. Nikt nam o tym wcześniej nie mówił\', \'Comment 16: wyszło przy okazji\', \'Comment 17: a skoro DHC obsługuje samochody to powinno to działać również na żywym środowisku. Na początek to pokażcie nam chociaż jak to działa\', ""Comment 18: max 0,5-1h i zobaczymy co dalej\'"", ""Comment 19: \'[~ewardega@deheus.com]opisz nam jakie scenariusze w DHC chciałabyś przejść podczas szkoelnia?\'"", ""Comment 20: \'Piotrku"", \'Comment 21: my po prostu chcemy wiedzieć jak działa ten parametr\', \'Comment 22: dopóki nie wiemy jak działa nie przygotuję Ci scenariusza. Tak jak już powiedziałam kilka razy\', \'Comment 23: temat ten wyszedł przy okazji\', \'Comment 24: dowiedzieliśmy się\', \'Comment 25: że coś takiego istnieje\', ""Comment 26: dlatego pokażcie nam proszę tę funkcjonalność:)\'"", ""Comment 27: \'A może macie jakiś manual"", ""Comment 28: który to uwzględnia? może dla jakiegoś innego kraju coś?\'"", ""Comment 29: \'[~ewardega@deheus.com]Pod tą zmianę nie powstał manual"", \'Comment 30: konfiguracja jest jednorazowa pod DHP3.0. Możemy taki dokument przygotować na przykładzie środowiska De Heus Polska \', ""Comment 31: wtedy szkolenie nie będzie potrzebne.\'"", ""Comment 32: \'Może być dokument"", ""Comment 33: chcemy się tylko dowiedzieć jak to działa. \'"", ""Comment 34: \'W takim razie"", ""Comment 35: w ramach wyceny przygotujemy dokument na bazie środowiska De Heus Polska\'"", \'Comment 36: ""Poniżej zamieszczam obiecany dokument z instrukcją konfiguracji atrybutu \\\'IsDriver\\\':[^Is Driver attribute - description.docx]""\', ""Comment 37: \'Is there anything else we can do for you?Regards\']""]\nRelated Issues:\n[]\n\n### End'}"
252,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8780\n\n### Instruction:\nWhen the S2P printout consists on two pages we see the header two times.\r\n\r\nWe would like to see it only once, only at the first page.\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: \'[~mbovene@deheus.com],the printout header has been changed on TEST and PROD environment.Best regards,Grzegorz\'"", ""Comment 4: \'Can be closed.\']""]\nRelated Issues:\n[]\n\n### End'}"
253,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8779\n\n### Instruction:\nHi\r\n\r\nWe had a situation in DHP that the operator selected the archive item ""."" (That\'s right: the name and code of the item is a dot character)\r\nHowever, this item is archived and the screen even not showing the select checkbox, still selecting the line and adding to the PLR.\r\n\r\nCould you please fix that?\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Please be informed that we have forwarded the issue to the development team in order to internal analysis.We are waiting for more details and will be back with further information as soon as possible.\'"", ""Comment 4: \'Hi [~mberbert@deheus.com],We will fix it under GDC-889.Regards\'"", ""Comment 5: \'Can we close this task in that case?Regards\'"", \'Comment 6: ""Hi Aleksandra and MaciejI see that the GDC don\\\'t have a estimation date for release.Do you have this information?Thank you""\', ""Comment 7: \'[~mberbert@deheus.com] R8.5\'"", ""Comment 8: \'Thank you very much![~aleksandra.przybylek@kotrka.com] you can close this taskThank you\'"", ""Comment 9: \'Thank you.\']""]\nRelated Issues:\n[\'DAP-13449\']\n\n### End'}"
254,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8778\n\n### Instruction:\nwe have problem to register production for item SUN0896-T-S30, lot number, 0891140323030, we registered 5 unit loads, but in WMS order, we have only 3, and if we try to register again the barcode or new barcode, system shows an error message.\r\n\r\nBarcodes available in PLR but missing in WO(IP)-502/3/23:\r\n89-W00G6P\r\n89-W00G7C\r\n\r\nwe need to move urgent these barcodes, but system not allow. Could you fix WO(IP) and WMS/Stock?\r\n\r\nThank you\r\n\r\n\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!!image-1!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 3: \\\'{code:java}2023-03-16 16:06:38 (f4ba2b34-a36f-4b1c-bf57-e98a91f7ff20/Plant.WMS.BusinessLogic/BR-1-SV-VM0702/11772/129) [Error] Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware - Error during request{  ""scheme"": ""http""\', \'Comment 4:  ""host"": {    ""Value"": ""br-1-sv-vm0702.deheusbrazil.com:85""\', \'Comment 5:    ""HasValue"": true\', \'Comment 6:    ""Host"": ""br-1-sv-vm0702.deheusbrazil.com""\', \'Comment 7:    ""Port"": 85  }\', \'Comment 8:  ""path"": ""/api/WarehouseIntake/registerMultipleIntakeFromProduction""\', \'Comment 9:  ""queryString"": []\', \'Comment 10:  ""requestBody"": ""{\\\\\\\\""warehouseOrderId\\\\\\\\"":\\\\\\\\""fe168aed-1aeb-4f8b-a3af-24ec65248118\\\\\\\\"",\\\\\\\\""warehouseOrderElementNo\\\\\\\\"":1,\\\\\\\\""bagSize\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":30},\\\\\\\\""unitLoads\\\\\\\\"":[{\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":1020},\\\\\\\\""unitLoadType\\\\\\\\"":20,\\\\\\\\""barcode\\\\\\\\"":{\\\\\\\\""code\\\\\\\\"":\\\\\\\\""89-W00G7C\\\\\\\\""}}]}""}.Kotrak.Common.Application.Exceptions.BusinessLogicException: Requested quantity for unit load exceeds available produced quantity. Unit load cannot be registered. ---> Kotrak.Common.Application.Exceptions.BusinessLogicException: Requested quantity for unit load exceeds available produced quantity. Unit load cannot be registered.   at Kotrak.Common.Infrastructure.Interceptors.ApiReferenceExceptionInterceptor.Intercept(IInvocation invocation)   at Castle.DynamicProxy.AbstractInvocation.Proceed()   at Plant.WMS.BusinessLogic.Domain.WarehouseIntakes.Services.IntakeFromProductionDomainService.RegisterMultipleIntakeFromProduction(RegisterMultipleIntakeFromProductionDomainDataStructure dataStructure) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Domain\\\\\\\\WarehouseIntakes\\\\\\\\Services\\\\\\\\IntakeFromProductionDomainService.cs:line 69   at Plant.WMS.BusinessLogic.Application.WarehouseIntake.WarehouseIntakeFromProductionService.RegisterMultipleIntakeFromProduction(RegisterMultipleIntakeFromProductionDataStructure dataStructure\', \'Comment 11: WarehouseOrder warehouseOrder\', \'Comment 12: WarehouseOrderElement warehouseOrderElement\', \'Comment 13: Owner owner) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Application\\\\\\\\WarehouseIntake\\\\\\\\WarehouseIntakeFromProductionService.cs:line 420   at Plant.WMS.BusinessLogic.Application.WarehouseIntake.WarehouseIntakeFromProductionService.RegisterMultipleIntakeFromProduction(RegisterMultipleIntakeFromProductionDataStructure dataStructure) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Application\\\\\\\\WarehouseIntake\\\\\\\\WarehouseIntakeFromProductionService.cs:line 119   at Plant.WMS.BusinessLogic.Application.WarehouseIntake.Handlers.RegisterMultipleIntakeFromProductionCommandHandler.Handle(RegisterMultipleIntakeFromProductionCommand command) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Application\\\\\\\\WarehouseIntake\\\\\\\\Handlers\\\\\\\\RegisterMultipleIntakeFromProductionCommandHandler.cs:line 37   at Kotrak.Common.Infrastructure.Gate.CommandEnvironment.Run[TCommand](TCommand command)   at Castle.DynamicProxy.AbstractInvocation.Proceed()   at Kotrak.Common.Infrastructure.Interceptors.LoggingInterceptor`1.Intercept(IInvocation invocation)   at Castle.DynamicProxy.AbstractInvocation.Proceed()   at Kotrak.Common.Infrastructure.Gate.Filters.CommandProcessFilter`1.Execute(CommandPipelineContext`1 input)   at Kotrak.Extensions.Pipeline.PredefinedFilters.FilterDecorator`1.Execute(TContext input)   at Kotrak.Extensions.Pipeline.Pipeline`1.Execute(T input)   at Kotrak.Common.Infrastructure.Gate.StandardGate.DispatchCommand[TCommand](TCommand command)   at Plant.WMS.BusinessLogic.Infrastructure.Api.Controllers.WarehouseIntakeController.RegisterMultipleIntakeFromProduction(RegisterMultipleIntakeFromProductionViewModel viewModel) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Infrastructure.Api\\\\\\\\Controllers\\\\\\\\WarehouseIntakeController.cs:line 328   at lambda_method6805(Closure \', \'Comment 14: Object \', \'Comment 15: Object[] )   at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor.SyncActionResultExecutor.Execute(IActionResultTypeMapper mapper\', \'Comment 16: ObjectMethodExecutor executor\', \'Comment 17: Object controller\', \'Comment 18: Object[] arguments)   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeActionMethodAsync()   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next\', \'Comment 19: Scope& scope\', \'Comment 20: Object& state\', \'Comment 21: 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 22: Scope& scope\', \'Comment 23: Object& state\', \'Comment 24: 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 25: Task lastTask\', \'Comment 26: State next\', \'Comment 27: Scope scope\', \'Comment 28: Object state\', \'Comment 29: Boolean isCompleted)   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker\', \'Comment 30: Task task\', \'Comment 31: IDisposable scope)   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker\', \'Comment 32: Task task\', \'Comment 33: IDisposable scope)   at Microsoft.AspNetCore.Routing.EndpointMiddleware.<Invoke>g__AwaitRequestTask|6_0(Endpoint endpoint\', \'Comment 34: Task requestTask\', \'Comment 35: ILogger logger)   at Swashbuckle.AspNetCore.SwaggerUI.SwaggerUIMiddleware.Invoke(HttpContext httpContext)   at Swashbuckle.AspNetCore.Swagger.SwaggerMiddleware.Invoke(HttpContext httpContext\', ""Comment 36: ISwaggerProvider swaggerProvider)   at Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware.Invoke(HttpContext httpContext)   --- End of inner exception stack trace ---{code}W logu jest informacja o braku unitloads !screenshot-1!  !screenshot-2! \'"", ""Comment 37: \'Hi [~psilva@deheus.com]Successfully added 2 new palettes. Unfortunately"", \'Comment 38: it was not possible to add those indicated in this task.If the locations do not match\', ""Comment 39: you have to move them manually.!image-2023-03-16-21-34-27-901.png!Please verify and please give us a feedback.\'"", ""Comment 40: \'Hi Łukasz ,now is correct. Thank you.\'"", ""Comment 41: \'Hello"", \'Comment 42: RCA has been created - DGS-8821\', ""Comment 43: this ticket has been closed.\']""]\nRelated Issues:\n[\'DGS-8821\', \'DGS-8808\']\n\n### End'}"
255,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8777\n\n### Instruction:\nLocation reports that since 14:00 no packing slips are printed from DHP: Please check whats going on,\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: \'Dispatch message respons doesnt look good!afbeelding!\'"", ""Comment 3: \' !screenshot-1! \'"", \'Comment 4: \\\'{code:java}2023-03-16 18:03:15 (228b8a31-538b-4890-bbc8-6ec160edff46/Plant.Integration.PCS.NL/DHVD01AP181/17736/17) [Error] Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware - Error during request{  ""scheme"": ""http""\', \'Comment 5:  ""host"": {    ""Value"": ""172.23.1.87:94""\', \'Comment 6:    ""HasValue"": true\', \'Comment 7:    ""Host"": ""172.23.1.87""\', \'Comment 8:    ""Port"": 94  }\', \'Comment 9:  ""path"": ""/api/bulk-dispatch/register-bulk-dispatches""\', \'Comment 10:  ""queryString"": []\', \'Comment 11:  ""requestBody"": ""<?xml version=\\\\\\\\""1.0\\\\\\\\"" encoding=\\\\\\\\""UTF-8\\\\\\\\""?>\\\\\\\\r\\\\<LoadingReport xmlns:xsi=\\\\\\\\""http://www.w3.org/2001/XMLSchema-instance\\\\\\\\"">\\\\\\\\r\\\\  <Trips>\\\\\\\\r\\\\    <Trip>\\\\\\\\r\\\\      <TripId>00992655</TripId>\\\\\\\\r\\\\      <LoadingDate>2023-03-16T09:54:42</LoadingDate>\\\\\\\\r\\\\      <SalesOrders>\\\\\\\\r\\\\        <SalesOrder>\\\\\\\\r\\\\          <SalesOrderNumber>SO-7162/3/23</SalesOrderNumber>\\\\\\\\r\\\\          <SalesOrderLines>\\\\\\\\r\\\\            <SalesOrderLine>\\\\\\\\r\\\\              <SalesOrderLineNumber>2</SalesOrderLineNumber>\\\\\\\\r\\\\              <ArticleCode>161613</ArticleCode>\\\\\\\\r\\\\              <RecipeId>35380</RecipeId>\\\\\\\\r\\\\              <Quantity>6026</Quantity>\\\\\\\\r\\\\              <Compartments>\\\\\\\\r\\\\                <Compartment>\\\\\\\\r\\\\                  <CompartmentNumber>4</CompartmentNumber>\\\\\\\\r\\\\                  <CompartmentWeight>3010</CompartmentWeight>\\\\\\\\r\\\\                </Compartment>\\\\\\\\r\\\\                <Compartment>\\\\\\\\r\\\\                  <CompartmentNumber>5</CompartmentNumber>\\\\\\\\r\\\\                  <CompartmentWeight>3016</CompartmentWeight>\\\\\\\\r\\\\                </Compartment>\\\\\\\\r\\\\              </Compartments>\\\\\\\\r\\\\            </SalesOrderLine>\\\\\\\\r\\\\            <SalesOrderLine>\\\\\\\\r\\\\              <SalesOrderLineNumber>1</SalesOrderLineNumber>\\\\\\\\r\\\\              <ArticleCode>161613</ArticleCode>\\\\\\\\r\\\\              <RecipeId>35380</RecipeId>\\\\\\\\r\\\\              <Quantity>23896</Quantity>\\\\\\\\r\\\\              <Compartments>\\\\\\\\r\\\\                <Compartment>\\\\\\\\r\\\\                  <CompartmentNumber>1</CompartmentNumber>\\\\\\\\r\\\\                  <CompartmentWeight>2126</CompartmentWeight>\\\\\\\\r\\\\                </Compartment>\\\\\\\\r\\\\                <Compartment>\\\\\\\\r\\\\                  <CompartmentNumber>2</CompartmentNumber>\\\\\\\\r\\\\                  <CompartmentWeight>2026</CompartmentWeight>\\\\\\\\r\\\\                </Compartment>\\\\\\\\r\\\\                <Compartment>\\\\\\\\r\\\\                  <CompartmentNumber>3</CompartmentNumber>\\\\\\\\r\\\\                  <CompartmentWeight>3556</CompartmentWeight>\\\\\\\\r\\\\                </Compartment>\\\\\\\\r\\\\                <Compartment>\\\\\\\\r\\\\                  <CompartmentNumber>6</CompartmentNumber>\\\\\\\\r\\\\                  <CompartmentWeight>2724</CompartmentWeight>\\\\\\\\r\\\\                </Compartment>\\\\\\\\r\\\\                <Compartment>\\\\\\\\r\\\\                  <CompartmentNumber>7</CompartmentNumber>\\\\\\\\r\\\\                  <CompartmentWeight>3316</CompartmentWeight>\\\\\\\\r\\\\                </Compartment>\\\\\\\\r\\\\                <Compartment>\\\\\\\\r\\\\                  <CompartmentNumber>8</CompartmentNumber>\\\\\\\\r\\\\                  <CompartmentWeight>3610</CompartmentWeight>\\\\\\\\r\\\\                </Compartment>\\\\\\\\r\\\\                <Compartment>\\\\\\\\r\\\\                  <CompartmentNumber>9</CompartmentNumber>\\\\\\\\r\\\\                  <CompartmentWeight>3226</CompartmentWeight>\\\\\\\\r\\\\                </Compartment>\\\\\\\\r\\\\                <Compartment>\\\\\\\\r\\\\                  <CompartmentNumber>10</CompartmentNumber>\\\\\\\\r\\\\                  <CompartmentWeight>3312</CompartmentWeight>\\\\\\\\r\\\\                </Compartment>\\\\\\\\r\\\\              </Compartments>\\\\\\\\r\\\\            </SalesOrderLine>\\\\\\\\r\\\\          </SalesOrderLines>\\\\\\\\r\\\\        </SalesOrder>\\\\\\\\r\\\\      </SalesOrders>\\\\\\\\r\\\\    </Trip>\\\\\\\\r\\\\  </Trips>\\\\\\\\r\\\\</LoadingReport>\\\\\\\\r\\\\""}.System.ArgumentException: An item with the same key has already been added. Key: 00992655   at System.Collections.Generic.Dictionary`2.TryInsert(TKey key\', \'Comment 12: TValue value\', \'Comment 13: InsertionBehavior behavior)   at System.Collections.Generic.Dictionary`2.Add(TKey key\', \'Comment 14: TValue value)   at System.Linq.Enumerable.ToDictionary[TSource,TKey](List`1 source\', \'Comment 15: Func`2 keySelector\', \'Comment 16: IEqualityComparer`1 comparer)   at System.Linq.Enumerable.ToDictionary[TSource,TKey](IEnumerable`1 source\', \'Comment 17: Func`2 keySelector\', \'Comment 18: IEqualityComparer`1 comparer)   at System.Linq.Enumerable.ToDictionary[TSource,TKey](IEnumerable`1 source\', \'Comment 19: Func`2 keySelector)   at Plant.Integration.PCS.NL.Application.Services.BulkDispatchService.GetShippingNoticesByTripDocumentNumber(RegisterBulkDispatchesActionDto actionDto) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\1b53a96170a797c0\\\\\\\\Plant.Integration.PCS.NL\\\\\\\\Plant.Integration.PCS.NL.Application\\\\\\\\Services\\\\\\\\BulkDispatchService.cs:line 87   at Plant.Integration.PCS.NL.Application.Services.BulkDispatchService.RegisterBulkDispatches(RegisterBulkDispatchesActionDto actionDto) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\1b53a96170a797c0\\\\\\\\Plant.Integration.PCS.NL\\\\\\\\Plant.Integration.PCS.NL.Application\\\\\\\\Services\\\\\\\\BulkDispatchService.cs:line 43   at Plant.Integration.PCS.NL.Infrastructure.Api.Controllers.BulkDispatchController.RegisterBulkDispatches(RegisterBulkDispatchesRequest request) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\1b53a96170a797c0\\\\\\\\Plant.Integration.PCS.NL\\\\\\\\Plant.Integration.PCS.NL.Infrastructure.Api\\\\\\\\Controllers\\\\\\\\BulkDispatchController.cs:line 33   at lambda_method544(Closure \', \'Comment 20: Object \', \'Comment 21: Object[] )   at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor.SyncObjectResultExecutor.Execute(IActionResultTypeMapper mapper\', \'Comment 22: ObjectMethodExecutor executor\', \'Comment 23: Object controller\', \'Comment 24: Object[] arguments)   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeActionMethodAsync()   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next\', \'Comment 25: Scope& scope\', \'Comment 26: Object& state\', \'Comment 27: Boolean& isCompleted)   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeNextActionFilterAsync()--- End of stack trace from previous location ---   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Rethrow(ActionExecutedContextSealed context)   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next\', \'Comment 28: Scope& scope\', \'Comment 29: Object& state\', \'Comment 30: Boolean& isCompleted)   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeInnerFilterAsync()--- End of stack trace from previous location ---   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeFilterPipelineAsync>g__Awaited|20_0(ResourceInvoker invoker\', \'Comment 31: Task lastTask\', \'Comment 32: State next\', \'Comment 33: Scope scope\', \'Comment 34: Object state\', \'Comment 35: Boolean isCompleted)   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker\', \'Comment 36: Task task\', \'Comment 37: IDisposable scope)   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker\', \'Comment 38: Task task\', \'Comment 39: IDisposable scope)   at Microsoft.AspNetCore.Routing.EndpointMiddleware.<Invoke>g__AwaitRequestTask|6_0(Endpoint endpoint\', \'Comment 40: Task requestTask\', \'Comment 41: ILogger logger)   at Swashbuckle.AspNetCore.SwaggerUI.SwaggerUIMiddleware.Invoke(HttpContext httpContext)   at Swashbuckle.AspNetCore.Swagger.SwaggerMiddleware.Invoke(HttpContext httpContext\', ""Comment 42: ISwaggerProvider swaggerProvider)   at Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware.Invoke(HttpContext httpContext){code}{code:java}  FROM [DHPlantPCSBusinessLogicMain].[dbo].[ShippingNotices]  where id=\\\\\'A69F31D3-2624-4F10-A655-6EC05AB566A3\\\\\'  or TripDocumentNumber=\\\\\'00992655\\\\\' or TripDocumentNumber=\\\\\'00992788\\\\\'{code}!image-2023-03-16-18-31-53-639!\'"", ""Comment 43: \'Problematic TripID - 00992655 try to be processed  !screenshot-2! for order SO-7162/3/23 and in DHP this Trip is 6_L000158760but in [DHPlantPCSBusinessLogicMain] database this ID 00992655 is related with trip 6_L000158444 !screenshot-3! Correct id for 6_L000158760 is 00992788.The best option would be to create a new trip.\'"", ""Comment 44: \'I think problem is also on the pcs side"", ""Comment 45: I see no new messages coming in\'"", ""Comment 46: \'and whether it will be consulted with the pcs provider?\'"", ""Comment 47: \'The people from production will consult pcs supplier\'"", \'Comment 48: ""I\\\'ve had contact with pcs supplier: problem is that they send a non existing trip but get no proper reply from dhp webservice\', \'Comment 49: instead a 500 error is send back""\', ""Comment 50: \'Have you tried create a new trip?\'"", \'Comment 51: ""That\\\'s not possible: trip is in pcs and already produced""\', \'Comment 52: ""Question is: why is DHP webservice sending 500 error when there the trip number is not known? that\\\'s just bad..!""\', ""Comment 53: \'Thomas,!image-2023-03-16-22-23-21-446.png!Our Plant sends error 500 because webservice does not expect more than one trip with the same ID. Maciej Dobrzański clarified you this issue in the past when such situation occured for the first time. You have been informed that there should be new Trip number in such situation.If you want to have application send error message back when one ID is assigned to more than one Trip number"", \'Comment 54: it should be reported as GDC because requires development in application. For now it is not to solve in priority 1 task.Please\', ""Comment 55: confirm if we can close it.\'"", ""Comment 56: \'For sure it will not be solved in the dgs ticket"", ""Comment 57: my apologies for last comment: was some frustration talking. Anyway the pcs supplier did find a workaround for now and will check further tomorrow. Ticket can be closed\'"", ""Comment 58: \'OK no problem. Thank you for response.I close this ticket\']""]\nRelated Issues:\n[]\n\n### End'}"
256,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8776\n\n### Instruction:\nHi\r\n\r\nThe Element *SUP7762-T-S24* from Sales Order *SO-638067989/23/PED* didn\'t integrate to DHP when it was integrated from ERP to DHC.\r\nOn DHC we received this order/element at 2023-03-02\r\nWe checked yesterday, this element wasn\'t on DHP, we resent from ERP and it integrated.\r\nWe need to know why this happened.\r\nThis is not the first case of this situation, but I don\'t remember which were the data of last case.\r\n\r\nThe problem is: we didn\'t produced this item because we didn\'t have it on DHP for Production planning reports.\r\n\r\nThis is really critical. Could you please check why this element didn\'t integrate to DHP right after it was integrated to DHC?\r\n\r\nThank you\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Could you please verify and provide number that is used in DHC already"", ""Comment 3: I was unable to found that order?\'"", ""Comment 4: \'Hi [~Agnieszka.Januszewska@kotrka.com]You can find it by OVE-079560 on DHC.Thank you\'"", \'Comment 5: \\\'Hello ,From what I can see the problem is caused by the fact that the item*SUP7762-T-S24*has created date in DHC Service database ""2023-03-09 08:24:13.700"" .When the order was send for the first time this Item was not in DHC service ( maybe not in DHC also )\', ""Comment 6: from what I can see also the DHHitemSUP7762-T was created in DHC Service database at this time.I verified it in DHH database and also this item seems to be missing until 9.03.. Are these explanations sufficient and may we close the task?\'"", ""Comment 7: \'!image-2023-03-20-08-24-51-877.png!\'"", ""Comment 8: \'Hi [~Agnieszka.Januszewska@kotrak.com]Your answer helps to identify the reason why the item weren\\\\\'t sent to DHP.However"", \'Comment 9: something is wrong. Look the order of facts:# Item was created in ""2023-03-01 13:42:07.614"" as you can see on the DHERPService.log/DHERPServiceReceivedRequest.log files# Sales Order was integrated in ""2023-03-02 12:37:54.968"".# Item was linked somewere in  ""2023-03-09 08:24:13.700""As far as I know\', \'Comment 10: if we have an Sales Order on DHC which one of its element  is not linked yet\', ""Comment 11: after the link DHC scans every Sales Order with that item and sends it to DHP integration.Can you check if this functionality is working properly? Maybe some configuration we need to check?Thank you\'"", ""Comment 12: \'I do not have historical information regarding the order itself"", \'Comment 13: i.e.\', \'Comment 14: whether it contained an unlinked item at an earlier integration. As a rule\', \'Comment 15: such an order does not go to the intermediate database,:DHC service\', \'Comment 16: i.e. also to DHP. This is a standard behavior of the system\', \'Comment 17: so it is most likely that the previously sent order did not contain this item and was modified in ERP and resubmitted\', \'Comment 18: and only after the item was integrated with DHC service it was resubmitted with a complete set of items to DHP. If there are more such cases we can prepare a RCA\', \'Comment 19: however\', \'Comment 20: then we need historical data for the order on the side of your ERP. here\', \'Comment 21: the resubmission of the order after the item was linked worked correctly\', ""Comment 22: so the incident itself has already been resolved by the user.\'"", ""Comment 23: \'Hi AgnieszkaI raise new DGS task when we find another case.Thank you very much! You can close this task\']""]\nRelated Issues:\n[]\n\n### End'}"
257,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8775\n\n### Instruction:\nItem needs to be produced, but the new version of the recipe does not go to DHC/DHP/PCS.\r\n\r\n\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Recipes are in the system but they have start dates from 2019 and 2020 as you can see!image-2023-03-16-15-06-58-034.png! !screenshot-1! \'"", \'Comment 3: ""{code:java}select *  FROM [DHCountry_NL_AS400_PROD].[dbo].[Recipes] where DhhItemId=\\\'C35FABC8-2C3C-4EC3-91EF-6894ABEA9BFC\\\'  and ProductionAreaId=\\\'9881BBC6-4D53-43C4-9A62-FA60F32BEC1C\\\'{code} !screenshot-2! ""\', ""Comment 4: \'They must be old artefacts from the as400 era.When formulation sends a new version 6"", \'Comment 5: will it overwrite the old one and send everything to DHC/DHP? If so\', ""Comment 6: you can close the ticket. \'"", ""Comment 7: \'If these recipes in version 3,4,5 from 2023 were done like that"", ""Comment 8: then yes.\']""]\nRelated Issues:\n[]\n\n### End'}"
258,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8774\n\n### Instruction:\nHi\r\n\r\nWe are facing issues on Databases backup routine in Toledo because of low disk space.\r\nWe found strange behavior in 3 files: Prod, QAM, Stock LogicEvents databases\r\nCould you please shrink these files?\r\n\r\nWe are rushing to buy more disk space asap, but that will take some time.\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: \'nie jest przerost loga  !screenshot-1!  !screenshot-2!  !screenshot-3! \'"", ""Comment 4: \'{code:java}select sys.objects.name"", \'Comment 5: sum(reserved_page_count) * 8.0 / 1024 [SizeInMB] from sys.dm_db_partition_stats\', ""Comment 6: sys.objects where sys.dm_db_partition_stats.object_id = sys.objects.object_id group by sys.objects.name order by sum(reserved_page_count) desc{code}qam !screenshot-7! prod  !screenshot-6! stock  !screenshot-8! bazy !screenshot-4! \'"", ""Comment 7: \'pojedyncze tabele w bazach eventowych zajmują tyle miejsca - jak wyżej.\'"", ""Comment 8: \'zgodnie z rozmową.\'"", ""Comment 9: \'Pomimo wykonania operacji shrink"", \'Comment 10: na bazie QAM\', \'Comment 11: jej rozmiar nie uległ znacznej zmianie. Ze wstępnej analizy\', \'Comment 12: wygląda na to\', \'Comment 13: że z jakiegoś powodu W/W moduły nie mogą usunąć/wyczyścić starych danych\', \'Comment 14: przez co w bazach/tabelach znajdują się stare dane. Konieczna jest analiza problemu przez developera\', \'Comment 15: oraz usunięcie danych zgodnie z ustalonym zakresem datPrzykład logów z w/w modułów:{code:java}2023-03-17 05:01:52 (/Plant.QAM.BusinessLogic/BR-4-SV-VM0204/14912/8) [Error] Microsoft.EntityFrameworkCore.Database.Command - Failed executing DbCommand (""204,988""ms) [Parameters=[""@p0=\\\\\\\'?\\\\\\\' (DbType = DateTime2)""]\', ""Comment 16: CommandType=\\\\\'Text\\\\\'"", \'Comment 17: CommandTimeout=\\\\\\\'200\\\\\\\']""""""DELETE FROM [dbo].[ProductionLotReports] WHERE Created <= @p0""2023-03-17 09:06:16 (/Plant.Prod.BusinessLogic/BR-4-SV-VM0204/8116/7) [Error] Microsoft.EntityFrameworkCore.Database.Command - Failed executing DbCommand (""205,005""ms) [Parameters=[""@p0=\\\\\\\'?\\\\\\\' (DbType = DateTime2)""]\', ""Comment 18: CommandType=\\\\\'Text\\\\\'"", \'Comment 19: CommandTimeout=\\\\\\\'200\\\\\\\']""""""DELETE FROM [dbo].[ProductionLots] WHERE Created <= @p0""2023-03-17 00:09:13 (/Plant.Stock.BusinessLogic/BR-4-SV-VM0204/10844/10) [Error] Microsoft.EntityFrameworkCore.Database.Command - Failed executing DbCommand (""204,998""ms) [Parameters=[""@p0=\\\\\\\'?\\\\\\\' (DbType = DateTime2)""]\', ""Comment 20: CommandType=\\\\\'Text\\\\\'"", \'Comment 21: CommandTimeout=\\\\\\\'200\\\\\\\']""""""DELETE FROM [dbo].[StockUnits] WHERE Created <= @p0""{code}\\\'\', ""Comment 22: \'Na spotkaniu z [~maciej.dobrzanski@kotrak.com],[~michal.kowal@kotrak.com]i [~marcin.kleszcz@kotrak.com] udało się usunąć stare dane dla baz QAM i Prod z tabeli dbo.ProductionLots (oraz wykonać operację shrink"", \'Comment 23: dzięki której przybyło 60gb miejsca na dysku). Udało się również znaleźć sposób na rozwiązanie takich problemów w przyszłości\', ""Comment 24: który będzie realizowany w projekcie.\'"", ""Comment 25: \'Hello"", \'Comment 26: our developers managed to remove old data for the QAM and Prod databases from the dbo.ProductionLots table (and to perform the shrink operation - 60gb of disk space was added). This is a permanent solution\', ""Comment 27: so the databases should no longer have such size (described tabels).\'"", ""Comment 28: \'Hello PiotrThank you for this shrink operation and disk saving.However we can see that in one week (between raising of this task and today) we have 1GB of growth in StockEvents file. Also ProdEvents file still too big.Can we wait one more week to check the behavior of these files?Thank you\'"", ""Comment 29: \'Do tego tematu Maicon założy jeszcze task. Aby zrobić rozwiązanie tymczasowe - job do czyszczenia nadmiarowych danych.A w kolejnej wersji 8.x będzie już poprawiony mechanizm"", ""Comment 30: więc job będzie tylko tymczasowy.\'"", ""Comment 31: \'According to information from Marcin Kleszcz this ticket has been closed. Permanent solution will be created in next version"", ""Comment 32: for now will be added additional job - new SR ticket will be needed.\'"", ""Comment 33: \'dga-8827\']""]\nRelated Issues:\n[\'DAP-13463\', \'DGS-8827\', \'DGS-8784\']\n\n### End'}"
259,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8773\n\n### Instruction:\nCL000022668 is a article in pieces, and should be taken in the DHP warehouse. However, checkbox warehouse is not marked. Please check what is going wrong here. The settlement of the item is set to Piece\n\n### Response:\n[""Comment 1: [\'!afbeelding-1!\'"", ""Comment 2: \'Also I tried to create VT for it"", ""Comment 3: please cancel this also\'"", ""Comment 4: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 5: \'!image-2023-03-16-14-32-05-191.png!\'"", ""Comment 6: \'Dear Thomas,I have cancelled VT for you. But please"", ""Comment 7: have a look. Here is the issue with packaging form. Now you need to cancel ASN and create it once again.Regards!image-2023-03-16-14-59-26-005.png!\'"", ""Comment 8: \'I see that"", \'Comment 9: but what is the packaging form you expect then? I checked another example\', \'Comment 10: please have a look: CL000022596 is also an intake for item with form pieces\', \'Comment 11: packaging form in DHC is 1\', ""Comment 12: exactly the same as for CL000022668: So I disagree that its created wrong: CL000022596 can be processed correct in DHP: !afbeelding-2!!afbeelding-3!\'"", ""Comment 13: \'CL000022668: !afbeelding-4!\'"", ""Comment 14: \'W DHC jest packing form 1 dla obu!image-2023-03-17-10-09-20-640.png|width=1297,height=488!A do Planta ten poprawny wpada z 3!image-2023-03-17-10-10-00-723.png!\'"", ""Comment 15: \'Na Itemie:poprawny item:!image-2023-03-17-10-27-34-350.png!Niepoprawny!image-2023-03-17-10-29-04-647.png!\'"", ""Comment 16: \'Na ASNach oba elementy mają packing form = 1!image-2023-03-17-10-57-20-464.png!!image-2023-03-17-10-59-18-843.png!I ten wpadł do Bulka z unitem PCS!image-2023-03-17-11-00-22-281.png!\'"", \'Comment 17: ""!image-2023-03-17-11-01-13-883.png!!image-2023-03-17-11-01-48-439.png!!image-2023-03-17-11-02-20-484.png!Wpadł do piece\\\'a""\', ""Comment 18: \'Hi Thomas,Could you please let me know if something was modified in Milas at about 13:00 - 13:30 yesterday on document: CL000022668?Under db and also in application we can see packing form - piece. That is why it has Warehouse checked. However"", \'Comment 19: the impacted document has packing form bulk which is incorrect.Under DHC service db I can see document CL000022596 was modified so it is highly possible something was done on ASN in Milas after it dropped do DHP.Please\', ""Comment 20: confirm if I can change packing form to piece on shipping notice element. Then you would be able to process.!image-2023-03-17-12-35-21-304.png!\'"", ""Comment 21: \'088112: - packaging w DHC i base unit: *STD"", \'Comment 22: pcs* - settlement type w DHP: *piece*!image-2023-03-17-10-27-34-350!088114: - packaging w DHC i base unit: *BLK\', \'Comment 23: KG* - settlement type w DHP: *bulk*!screenshot-2!!screenshot-1!Item 088114 ma niepoprawną konfigurację w DHC\', ""Comment 24: przez co jego settlement type w DHP = bulk. Z tego powodu na ASNie item ma packing form bulk.\'"", ""Comment 25: \'Please also check if item080114 is configured in DHC correctly - if the packing form is correct.\'"", ""Comment 26: \'Hi [~TDankers@deheus.com],Please look on detailed information about shipping notices provided below088112: - packaging in DHC base unit: *STD"", \'Comment 27: pcs* - settlement type in DHP: *piece*!image-2023-03-17-10-27-34-350!088114: - packaging in DHC base unit: *BLK\', \'Comment 28: KG* - settlement type in DHP: *bulk*!screenshot-2!!screenshot-1!In order to make an SN packing form piece the item in DHP has to have a settlement type: *Piece*. So\', ""Comment 29: it looks like Item 088114 has the wrong configuration in DHC.Regards\'"", ""Comment 30: \'I will check masterdata of this item in the ERPFor now can you change it on the ASN?\'"", ""Comment 31: \'Hi Thomas,Ready"", ""Comment 32: please verify!image-2023-03-23-07-40-42-476.png!Regards\'"", ""Comment 33: \'Still the connected VT needs to be cancelled now"", ""Comment 34: see ticket DGS-8832\'"", ""Comment 35: \'Hi Thomas,VT 481/3/23 has been cancelled. Please"", ""Comment 36: let me know if this is fine and we can close both tasks.Regards\'"", ""Comment 37: \'Thanks you can close this ticket also\'"", ""Comment 38: \'Thank you\']""]\nRelated Issues:\n[\'DGS-8832\']\n\n### End'}"
260,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8772\n\n### Instruction:\nRecipe 116441 does not arrive in Maasbracht\r\n\r\nI see it ended up in a DHC error message queue (see attachment) with a datetime error.  \r\n\r\nPlease investigate, thanks!\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-03-16-08-51-36-820.png!\'"", ""Comment 4: \'Dear Martijn,Recipe in Plant now. Please verify.Regards!image-2023-03-16-09-03-28-029.png!\'"", \'Comment 5: ""I\\\'m checking with the end-user""\', ""Comment 6: \'Waiting for your feedback then\'"", ""Comment 7: \'Got no response"", ""Comment 8: but I checked myself and see it is there. Thanks!You can close this ticket\'"", ""Comment 9: \'Thank you.\']""]\nRelated Issues:\n[]\n\n### End'}"
261,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8771\n\n### Instruction:\nHello,\r\n\r\nrecipe 506995 is send yesterday, production recipe is created in DHC, but its not in DHP Sneek. After resync its still not there: please check and solve this\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-03-16-08-51-48-729.png!\'"", ""Comment 4: \'Hi Thomas,Recipe in plant now. Please"", ""Comment 5: verify.Regards!image-2023-03-16-09-05-18-683.png!\'"", ""Comment 6: \'Yes it is thanks: is this a known issue and solved in a new version? We plan to upgrade to DHC 0.62 next week\'"", ""Comment 7: \'Yes"", ""Comment 8: exactly. This is this known issue. Waiting for the upgrade then :)Can we close this task?\'"", ""Comment 9: \'please close"", ""Comment 10: thanks for the help\'"", ""Comment 11: \'Thank you.BR\']""]\nRelated Issues:\n[]\n\n### End'}"
262,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8770\n\n### Instruction:\nPRL 4361150323079 was not found in the Production module (maybe, user deleted this PLR).\r\nCheck on ""item Delivery tracking"" and ""item history Module"" : Raw materials has been consumed for this lot .\r\n\n\n### Response:\n[""Comment 1: [\'!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: \'!image-2023-03-16-12-20-21-709.png!!image-2023-03-16-12-20-45-534.png!!image-2023-03-16-12-23-23-436.png!\'"", ""Comment 4: \'!image-2023-03-22-09-26-24-548.png!!image-2023-03-22-09-26-24-548!\'"", ""Comment 5: \'Start date PLR jest identyczna jak data założenia dostawy"", ""Comment 6: works as designed!image-2023-03-16-12-36-56-133.png!!image-2023-03-16-12-37-19-312.png!\'"", ""Comment 7: \'Hi,Delivery creates at the same time as the Item from PLR arrives / is registered in the system. Deleting PLR does not mean that delivery and item disappear from the system. In other words"", \'Comment 8: system works correctly.And yes\', \'Comment 9: PLR has been deleted. You still forgot that it is registered in more places\', \'Comment 10: not only in Production. In addition\', \'Comment 11: it has been deleted in status confirmed. In other words\', ""Comment 12: system works correctly.Regards\'"", ""Comment 13: \'note that: we can not delete PLR"", ""Comment 14: just allow cancel in UI. so it will not logically\'"", ""Comment 15: \'As I mentioned"", \'Comment 16: the PLR is vissible under db in other modules\', \'Comment 17: requested PLR is in status: confirmed. So if delivery arrived with ready product\', \'Comment 18: raw material was consumed for production before.Please\', \'Comment 19: provide us with information what should be the next step for this issue. In my opinion\', ""Comment 20: comprehensive explanation has been provided to your question.Regards\'"", ""Comment 21: \'hi Aleksandra"", ""Comment 22: i think question ia about to protect this situation later. There is about in-consistences between data of every module. Can we know the root cause of this?\'"", ""Comment 23: \'Hi,In incidents we focus on clearing and unblocking the process. To meet the rootcause we can raise RootCause Analysis (RCA)task task for you.Please"", ""Comment 24: let us know if you agree to raising RCA task.Regards\'"", ""Comment 25: \'Hi,In incidents we focus on clearing and unblocking the process. To meet the rootcause we can raise RootCause Analysis (RCA)task task for you.Please"", ""Comment 26: let us know if you agree to raising RCA task.Regards\']""]\nRelated Issues:\n[]\n\n### End'}"
263,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8769\n\n### Instruction:\nwe have problem in item reservation, the user remove item from VT but the barcode is with reservation yet. Now we need to load urgent in other VT and system not allow. Barcode 89-W00F3I, item SUN7540-S20.\r\n\r\nCould you please check why item is still reserved and fix it?\r\n\r\nThank you\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Reservation has been corrected"", ""Comment 4: please check and send a feedback.RCA is already created DGS-8715and related GDC-849\'"", ""Comment 5: \'[[DHP 3.0] Stocktaking - Reserved StockUnits"", \'Comment 6: rezerwacja na stockach\', ""Comment 7: wisi rezerwacja|onenote:https://kotrak.sharepoint.com/sites/erpasysta/Shared%20Documents/Baza%20wiedzy/Baza%20Wiedzy%20-%20ERPSD/Klienci/DEHEUS/DEHEUS%20APPLICATIONS/Brazil/Baza%20wiedzy.one#%5bDHP%203.0%5d%20Stocktaking%20-%20Reserved%20StockUnits,%20rezerwacja%20na&section-id=\\\\\\\\{05DF1439-683C-45FE-8260-61E2EC66DC91}&page-id=\\\\\\\\{F85E69B9-BC0D-4FAA-BDC2-3E89CD2E4917}&end] ([Widok sieci Web|https://kotrak.sharepoint.com/sites/erpasysta/_layouts/OneNote.aspx?id=%2Fsites%2Ferpasysta%2FShared%20Documents%2FBaza%20wiedzy%2FBaza%20Wiedzy%20-%20ERPSD&wd=target%28Klienci%2FDEHEUS%2FDEHEUS%20APPLICATIONS%2FBrazil%2FBaza%20wiedzy.one%7C05DF1439-683C-45FE-8260-61E2EC66DC91%2F%5BDHP%203.0%5D%20Stocktaking%20-%20Reserved%20StockUnits%2C%20rezerwacja%20na%7CF85E69B9-BC0D-4FAA-BDC2-3E89CD2E4917%2F%29])\'"", ""Comment 8: \'Piotr,now is correct. Thank you.\'"", ""Comment 9: \'Thank you for confirmation"", ""Comment 10: issue has been closed.\']""]\nRelated Issues:\n[]\n\n### End'}"
264,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8768\n\n### Instruction:\nThe production SUR7546-P-MD 0871090323029 was confirmed with wrong weight, the correct final weight is 13992kg. We need to fix in PLR to integrate with correct information and have correct costs and reports.\r\n\r\nCould you please fix production in PLR and stock screen, integrate again to DHC ?\r\n\r\nThank you\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Hello"", ""Comment 4: can you do an inventory in DHP to increase stocks ? But PLR itself will not change. The change itself for the PLR \\\\u200b\\\\u200bis a time-consuming process requiring changes in each of the DHP databases in which the PLR \\\\u200b\\\\u200bis located and related tables.Regards.\'"", ""Comment 5: \'Hello Piotr,I need to have the production fixed to integrete to ERP. If we made inventory"", \'Comment 6: the TT information will be wrong. If is it not possible fix in DHP\', ""Comment 7: could you fix in DHC?Thank you\'"", ""Comment 8: \'hej"", ""Comment 9: możemy im wycenić taką prośbę ? Chodzi że źle wybrali przecinek i zamiast 13 992 kg wyprodukowali 13,992kg.\\\\rChodzi o zmianę w DHC,plant to sobie zrobią inw.\\\\r\\\\r\'"", ""Comment 10: \'[~piotr.gaczorek@kotrak.com]wystarczy tylko pomnożyć przez 1000 nagłówek i elementy w DHC i DHC Service i niech wyślą sobie ponownie z DHC. nie wiem czy jest potrzebna jakaś wycena"", ""Comment 11: powinno to zająć mniej niż pół godziny.\'"", ""Comment 12: \'!image-2023-03-20-15-30-14-579.png!!image-2023-03-20-15-31-25-184.png!\'"", \'Comment 13: ""{code:java}SELECT Quantity\', \'Comment 14: ExpectedQuantity\', ""Comment 15: *  FROM [Evolution_DHCountry].[dbo].[ProductionLotReports] where LotNumber = \'0871090323029\'--  ExpectedQuantity--13999.950000SELECT Quantity"", \'Comment 16: *  FROM [Evolution_DHCountry].[dbo].[ProductionLotReportElements]   where ProductionLotReportId = \\\'22566FF6-E4F0-4A35-9E0E-04FE753503F1\\\'  select SUM (Quantity) from [Evolution_DHCountry].[dbo].[ProductionLotReportElements]   where ProductionLotReportId = \\\'22566FF6-E4F0-4A35-9E0E-04FE753503F1\\\'{code}""\', ""Comment 17: \'Hello"", ""Comment 18: production quantity for PLR has been corrected and synced again. !screenshot-1! Please verify and send a feedback.\'"", ""Comment 19: \'Hello Piotr,I checked and in DHC is correct. But we tried to do inventory in DHP and was not possible to fix.Could you fix quantity on stock in DHP?!image-1!\'"", ""Comment 20: \'Hello"", ""Comment 21: it has been corrected  !screenshot-2! \'"", ""Comment 22: \'Hi Piotr,ok"", ""Comment 23: you can close this task. Thank you.\']""]\nRelated Issues:\n[]\n\n### End'}"
265,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8767\n\n### Instruction:\nDear, \r\nI need to add new EAN code.\r\n\r\narticle: 1331, 20kg, 8594210721104\r\n\r\nCould you add it asap pls?\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 need an confirmation You want us to enter provided EAN number to 1331 item code!image-2023-03-15-14-07-39-871.png!Is that correct?You should be able to do this by yourself"", ""Comment 3: by filling EAN and choosing save !image-2023-03-15-14-09-19-781.png! . Is there any issue with that?\'"", ""Comment 4: \'Hi Bartek"", ""Comment 5: I don´t think that it is the same. e.g. for 1594 we already have EAN seen on the labels but in DHC place for EAN is empty. Maybe better to ask Marta Litkie for help. She will know.!image!\'"", ""Comment 6: \'It should be ok right now. Please check.\'"", ""Comment 7: \'[[DHP] new EAN|onenote:https://kotrak.sharepoint.com/sites/erpasysta/Shared%20Documents/Baza%20wiedzy/Baza%20Wiedzy%20-%20ERPSD/Klienci/DEHEUS/DEHEUS%20APPLICATIONS/Czechy/Baza%20wiedzy.one#%5bDHP%5d%20new%20EAN&section-id=\\\\\\\\{99A562FD-190B-49C6-9C6F-9AD69CEB250E}&page-id=\\\\\\\\{AE3EE499-0243-47E6-A0C7-4772BD91E7FF}&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%2FCzechy%2FBaza%20wiedzy.one%7C99A562FD-190B-49C6-9C6F-9AD69CEB250E%2F%5BDHP%5D%20new%20EAN%7CAE3EE499-0243-47E6-A0C7-4772BD91E7FF%2F%29])\'"", ""Comment 8: \'Bartek"", \'Comment 9: I´m so sorry. I made a mistake! It should be for the article 1310! Pls\', ""Comment 10: could you change it? \'"", ""Comment 11: \'Item code has been changed from 1331 to 1310. Please check.\'"", ""Comment 12: \'it´s okay.thx\']""]\nRelated Issues:\n[]\n\n### End'}"
266,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8766\n\n### Instruction:\nOrder SO000076365 was planned in trip 00988430 and loaded on VT-301/3/23. VT has status Closed.\r\nWe did not receive the XML for the packing slip in Transform. \r\nOrder contains 1 bulk and 1 packed item. Packed item does not seem to be loaded. \r\nTrip/VT also contains other orders. For these orders we received and XML for the packing slip in Tranform.\r\n\r\nCan you check why the packing slip is not generated? If the packed item was not loaded, how can the VT have status Closed?\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'!image-2023-03-17-14-35-34-342.png!\'"", ""Comment 4: \'In plant there is no realisation for item088345. We can see also on VT in DHC that this item is not there. Please"", ""Comment 5: verify!image-2023-03-17-14-36-49-885.png!\'"", ""Comment 6: \'The issue is that we do not have the packing slip for this order.Indeed"", \'Comment 7: no realisation for item 088345 (that is what I meant with ""item is not loaded""). However\', ""Comment 8: line is not cancelled. How is it possible that this VT is closed?\'"", ""Comment 9: \'Label content jest:!image-2023-03-21-09-41-18-869.png!Dla NL jest!image-2023-03-21-09-42-51-391.png!\'"", ""Comment 10: \'!image-2023-03-21-10-06-37-222.png!!image-2023-03-21-10-15-19-288.png!!image-2023-03-21-10-15-19-288!\'"", ""Comment 11: \'W plancie nie mamy receptury!image-2023-03-21-10-29-59-712.png!W DHC i Service tak!image-2023-03-21-10-31-14-671.png!\'"", ""Comment 12: \'!image-2023-03-21-10-54-25-813.png!!image-2023-03-21-10-54-25-813!\'"", ""Comment 13: \'[^SPS_admin_17032023_142703789_03854c85-8004-433e-9378-29aa1003d5d1.xml] [^SPS_admin_17032023_142703847_463e588d-8c4e-4af7-8305-c469468ebb54.xml] [^SPS_admin_17032023_142704020_f6d37b42-2038-46ef-a89c-1b9296ab808d.xml]\'"", ""Comment 14: \'Hi Rob,Sorry for my delay. These file in attach I have generated on Friday and they seems to be fine. Could you please confirm on your side? Also"", ""Comment 15: those files for me have below default path:!image-2023-03-22-09-46-13-670.png|width=533,height=247![^SPS_admin_17032023_142703789_03854c85-8004-433e-9378-29aa1003d5d1.xml]Could you please check it with user?\'"", ""Comment 16: \'This ticket can be closed\'"", ""Comment 17: \'Thank you\']""]\nRelated Issues:\n[]\n\n### End'}"
267,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8765\n\n### Instruction:\nBy Mistake, item 3102650 is linked to item 3103650 in DHC: Can you remove this link? Because in case of mistake this part of DHC is not that user friendly so we can do this ourselves ;) Or is it?\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 ThomasPlease send the item"", ""Comment 4: 3102650!image-2023-03-15-13-55-35-008.png|width=872,height=254!I will change the linkingRegards\'"", ""Comment 5: \'3102650 is now available\'"", ""Comment 6: \'Hello"", ""Comment 7: Thomas It should be fine now.Please verifyThe problem has been resolved? Regards\'"", ""Comment 8: \'Thanks"", ""Comment 9: problem is solved: ticket can be closed\']""]\nRelated Issues:\n[]\n\n### End'}"
268,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8764\n\n### Instruction:\nCPI-M/2023/0178 should be visible on the round but it is not.\r\n\r\nCan you tell us why and adjust the relationship table if needed?\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 [~mbovene@deheus.com],Expenses list on Round document"", ""Comment 4: display all PI\\\\\'s"", \'Comment 5: which are ""Regular purchase"" and ""Round Category"" - ""Expenses"" but without filled ""Leading doc"".As we see on this Credit Purchase Invoice the field ""Leading doc"" is not empty:!image-2023-03-15-13-36-57-591.png!In that case\', ""Comment 6: we need to make some adjustements in the relation table or on lists.Best regards,Grzegorz\'"", \'Comment 7: ""Ok. All CPI\\\'s and also CSI\\\'s that are created based on PI\\\'s and SI\\\'s that are on the round overview should be visible on the round as well.Please make the needed adjustments for this.""\', ""Comment 8: \'Wen do you think this is fixed?\'"", ""Comment 9: \'[~mbovene@deheus.com],the modification on Round will have an impact on other list like propably Financial Statement views.For safty"", ""Comment 10: we need to try change it first on test.Best regards,Grzegorz\'"", ""Comment 11: \'They should have an impact on the financial statement and calculations as well. But OK to have this on the test environment first.\'"", \'Comment 12: ""[~mbovene@deheus.com],we\\\'ve made changes in list views on Round\', \'Comment 13: Technical Results and S2P calculations. You can verify it on test Intense environment.Best regards,Grzegorz""\', ""Comment 14: \'Do sprawdzenia czy korekty faktur"", ""Comment 15: które nie powinny być wyświetlane na Rundzie pokazują się na niej. Korekty takich faktur nie powinny pokazywać się na rundzie.\'"", ""Comment 16: \'This is the task I was looking for. As I told to Damian today:All credit invoices should be booked on the Round and FS if the original invoices are on the round. See https://helpdesk.kotrak.com/servicedesk/customer/portal/56/DGS-8913. \'"", ""Comment 17: \'Zmiany wprowadzone w sekcji expense*było*and isnull(Doc_LeadingDocID,0) = 0*Jest*and (isnull(Doc_LeadingDocID,0) = 0 OR (isnull(Doc_LeadingDocID,0) != 0 and isnull(Doc_IntColumn2,0) = 1))RoundaMAS NL tabelka expenseLAS tabelka expenseNAS tabelka expenseVAS tabelka expenseFSMAS NL tabelka expense"", \'Comment 18: Details\', \'Comment 19: Wiersz sumującyLAS tabelka expense\', \'Comment 20: Details\', \'Comment 21: Wiersz sumującyNAS tabelka expense\', \'Comment 22: Details\', \'Comment 23: Wiersz sumującyVAS tabelka expense\', \'Comment 24: Details\', ""Comment 25: Wiersz sumującyProceduraKR_CalculateSaldo2PayVASKR_CalculateSaldo2PayNASKR_CalculateSaldo2PayLASKR_CalculateSaldo2PayKR_Printout_FS_TotalExpensesKR_Printout_FS_TotalExpenses_VASKR_Printout_FS_TotalExpenses_NASKR_Printout_FS_TotalExpenses_LASFunkcjaKR_FinancialStatementSaldoKR_FinancialStatementSaldo_NASKR_FinancialStatementSaldo_VASKR_FinancialStatementSaldo_LAS\'"", \'Comment 26: ""Changes have been made on TEST environment. You can verify them.In some sectors and sections displaying Credit invoices worked correctly before\', \'Comment 27: we\\\'ve made changes in Expenses sections.Changes that have been made in sectors on documents: * RoundMAS NL expenses sectionLAS expenses sectionNAS expenses sectionVAS expenses section * Financial StatementMAS NL expenses sectionLAS expenses sectionNAS expenses sectionVAS expenses section * Financial Statement printoutsMAS NLLASNASVAS * Saldo to PayMAS NLLASNASVAS""\', ""Comment 28: \'Can be moved to PROD\'"", ""Comment 29: \'[~tomasz.zygon@kotrak.com]do przerzucenia na Prod.\']""]\nRelated Issues:\n[\'DGS-8913\']\n\n### End'}"
269,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8763\n\n### Instruction:\nRelated to RCA: DGS-8703\r\n\r\nHello, please check: I can see this case now for\r\n multipe locations: I added screenshot for Veghel, Helmond, Maasbracht \r\nbut please check also other locations!\r\n\r\n\r\n\r\n\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!afbeelding!!afbeelding-1!!afbeelding-2!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 3: ""Hello from what we verified in RCA task ( sorry I didn\\\'t manage to pass this information there) the orders are in vt only error is that the table in masterdata shows wrong resultsexample from Helmond!image-2023-03-15-09-53-08-005.png|width=845,height=241!!image-2023-03-15-09-56-33-826.png!So please If you have some urgent order verify it in VT module directly and if it will be missing send a number.If in fact orders will be in the Vt module\', \'Comment 4: could we change it to p2?""\', ""Comment 5: \'select m.id,v.id"", ""Comment 6: m.ForeignDocument from DHPlantMaintBusinessLogicMain.dbo.orders m left join DHPlantVCBusinessLogicMain.dbo.orders v on m.id=v.idwhere m.year=2023 and m.month=3 and m.type =2 and IsInVehicleControl=0 and v.id is null\'"", ""Comment 7: \'Hi Agnieszka"", ""Comment 8: oke glad to hear it should be wrong display in the masterdata module. I will check and you can lower priority\'"", ""Comment 9: \'For Vehgel and Massbracht seems everythng is ok.For Helond only this order :SO000079784 is not sync. Which had this error:!image-2023-03-15-10-22-26-663.png!As I checked in the DHC for that orders with situation where address for Main BP is linked with diffrent BP.Please checked.!image-2023-03-15-10-30-34-076.png! !image-2023-03-15-10-22-26-663!!image-2023-03-15-10-30-34-076!\'"", ""Comment 10: \'Thanks"", ""Comment 11: I fixed the one for Helmond: you may close this ticket\']""]\nRelated Issues:\n[\'DGS-8703\']\n\n### End'}"
270,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8762\n\n### Instruction:\nHi, since few weeks, every time when I log in to DHP Im getting the error message, can you check what going on? \n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'the same when I preview VT!image-1!\'"", ""Comment 3: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 4: \'The same while opening the production order list !image-2!\'"", ""Comment 5: \'PLS change the priority to P2."", ""Comment 6: seems it is more important than I expected \'"", ""Comment 7: \'{code:java}2023-03-15 09:09:57 (/Plant.VC.BusinessLogic/CIAPP04/10836/1) [Warning] Microsoft.AspNetCore.DataProtection.Repositories.EphemeralXmlRepository - Using an in-memory repository. Keys will not be persisted to storage.2023-03-15 09:09:57 (/Plant.VC.BusinessLogic/CIAPP04/10836/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-03-15 09:09:57 (/Plant.VC.BusinessLogic/CIAPP04/10836/1) [Warning] Microsoft.AspNetCore.DataProtection.KeyManagement.XmlKeyManager - No XML encryptor configured. Key {a3f93166-beb8-4f3d-b3f9-74c3e4b49ae4} may be persisted to storage in unencrypted form.2023-03-15 09:14:00 (bb8db221-dc93-4385-9615-ab893a75620f/Plant.VC.BusinessLogic/CIAPP04/10836/168) [Warning] Microsoft.EntityFrameworkCore.Query - Compiling a query which loads related collections for more than one collection navigation"", ""Comment 8: either via \\\\\'Include\\\\\' or through projection"", ""Comment 9: but no \\\\\'QuerySplittingBehavior\\\\\' has been configured. By default"", ""Comment 10: Entity Framework will use \\\\\'QuerySplittingBehavior.SingleQuery\\\\\'"", \'Comment 11: 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}{code:java}2023-03-15 09:09:32 (/Plant.VC.BusinessLogic/CIAPP04/1672/194) [Warning] RawRabbit.Channel.ChannelFactory - Connection was shutdown by Application. ReplyText ""Connection close forced""{code}\\\'\', ""Comment 12: \'!image-2023-03-15-10-24-44-475.png!\'"", ""Comment 13: \'!image-2023-03-15-10-29-31-293.png!\'"", ""Comment 14: \'Po ponownym restarcie print server dalej nie wstaje!image-2023-03-15-10-42-42-820.png!\'"", ""Comment 15: \'It works now. Please"", ""Comment 16: check\'"", ""Comment 17: \'[[DHP 3.0] Ivory Coast: http failure response for (unknown url0: 0 unknowkn error|onenote:https://kotrak.sharepoint.com/sites/erpasysta/Shared%20Documents/Baza%20wiedzy/Baza%20Wiedzy%20-%20ERPSD/Klienci/DEHEUS/DEHEUS%20APPLICATIONS/Holandia%20Premix%20i%20AS400/Ivory%20Coast.one#%5bDHP%203.0%5d%20Ivory%20Coast%20http%20failure%20response%20for&section-id=\\\\\\\\{E3AAA30F-8947-45F7-BB97-B4D61E9F4374}&page-id=\\\\\\\\{CD6057C2-6FC1-499A-8ACB-A60F898BD426}&end] ([Widok sieci Web|https://kotrak.sharepoint.com/sites/erpasysta/_layouts/OneNote.aspx?id=%2Fsites%2Ferpasysta%2FShared%20Documents%2FBaza%20wiedzy%2FBaza%20Wiedzy%20-%20ERPSD&wd=target%28Klienci%2FDEHEUS%2FDEHEUS%20APPLICATIONS%2FHolandia%20Premix%20i%20AS400%2FIvory%20Coast.one%7CE3AAA30F-8947-45F7-BB97-B4D61E9F4374%2F%5BDHP%203.0%5D%20Ivory%20Coast%3A%20http%20failure%20response%20for%7CCD6057C2-6FC1-499A-8ACB-A60F898BD426%2F%29])\'"", ""Comment 18: \'Helo"", ""Comment 19: it seems it is OK. What was the issue? PLs explain. Can local IT resolve this type of problems? \'"", ""Comment 20: \'Hi,Report server was stopped. On plant db server there is report server configuration manager. I clicked start here:!image-2023-03-16-07-08-20-541.png!and the restarted service in iis:!image-2023-03-16-07-09-08-707.png!Please"", \'Comment 21: remember to browse website. When it shows 404 error\', ""Comment 22: it means it is working fine.Can we close this task?Regards\'"", ""Comment 23: \'Please close the ticket.\'"", ""Comment 24: \'Thank you.\']""]\nRelated Issues:\n[]\n\n### End'}"
271,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8761\n\n### Instruction:\nExample Lot No : \r\n0531150323515\r\n0531150323516\r\n0531150323517\r\netc....\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Hello"", ""Comment 3: We kindly inform you that wecurrentlyare processing another Priority1 task.We will revert to processing your task as soon as possible.Regards\'"", ""Comment 4: \'Hi.We have a problem accessing to server 103.60.180.254:5001.Could you check this and please give us a feedback.Same problem for all accounts!image-2023-03-15-06-05-38-136.png!!image-2023-03-15-06-06-13-386.png!Thank you\'"", ""Comment 5: \'Hi ,let me ask to infrastructure team first.\'"", ""Comment 6: \'OK thank you\'"", ""Comment 7: \'!image-2023-03-15-07-24-10-315.png!This same problem for Aleksandra Przybylek account\'"", ""Comment 8: \'Hi lukas,Please try to login again \'"", ""Comment 9: \'Z tej godziny"", \'Comment 10: ale i cały czas!image-2023-03-15-08-05-43-258.png!Są trzy rodzaje errorów w tabeli logów:{code:java}System.Data.SqlClient.SqlException (0x80131904): Execution Timeout Expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.Operation cancelled by user.The statement has been terminated. ---> System.ComponentModel.Win32Exception (0x80004005): The wait operation timed out   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception\', \'Comment 11: Boolean breakConnection\', \'Comment 12: Action`1 wrapCloseInAction)   at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception\', \'Comment 13: Boolean breakConnection\', \'Comment 14: Action`1 wrapCloseInAction)   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj\', \'Comment 15: Boolean callerHasConnectionLock\', \'Comment 16: Boolean asyncClose)   at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior\', \'Comment 17: SqlCommand cmdHandler\', \'Comment 18: SqlDataReader dataStream\', \'Comment 19: BulkCopySimpleResultSet bulkCopyHandler\', \'Comment 20: TdsParserStateObject stateObj\', \'Comment 21: Boolean& dataReady)   at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName\', \'Comment 22: Boolean async\', \'Comment 23: Int32 timeout\', \'Comment 24: Boolean asyncWrite)   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion\', \'Comment 25: String methodName\', \'Comment 26: Boolean sendToPipe\', \'Comment 27: Int32 timeout\', \'Comment 28: Boolean& usedCache\', \'Comment 29: Boolean asyncWrite\', \'Comment 30: Boolean inRetry)   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()   at System.Data.Linq.SqlClient.SqlProvider.Execute(Expression query\', \'Comment 31: QueryInfo queryInfo\', \'Comment 32: IObjectReaderFactory factory\', \'Comment 33: Object[] parentArgs\', \'Comment 34: Object[] userArgs\', \'Comment 35: ICompiledSubQuery[] subQueries\', \'Comment 36: Object lastResult)   at System.Data.Linq.SqlClient.SqlProvider.ExecuteAll(Expression query\', \'Comment 37: QueryInfo[] queryInfos\', \'Comment 38: IObjectReaderFactory factory\', \'Comment 39: Object[] userArguments\', \'Comment 40: ICompiledSubQuery[] subQueries)   at System.Data.Linq.SqlClient.SqlProvider.System.Data.Linq.Provider.IProvider.Execute(Expression query)   at System.Data.Linq.DataContext.ExecuteMethodCall(Object instance\', \'Comment 41: MethodInfo methodInfo\', \'Comment 42: Object[] parameters)   at System.Data.Linq.DataContext.ExecuteCommand(String command\', \'Comment 43: Object[] parameters)   at PCSIntegration.Controllers.ProductionLotReportController.ReleaseRawMaterialsForProduction(ProductionLotReport report\', \'Comment 44: Int32 pcsId\', \'Comment 45: DataContext dc) in E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\156434433\\\\\\\\DHAPPS25-PCSIT182-JOB1\\\\\\\\PCSIntegration\\\\\\\\Controllers\\\\\\\\ProductionLotReportController.cs:line 195   at PCSIntegration.Controllers.ProductionLotReportController.SavePcsProductionLotReport(ProductionLotReport report\', \'Comment 46: Int32 pcsId) in E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\156434433\\\\\\\\DHAPPS25-PCSIT182-JOB1\\\\\\\\PCSIntegration\\\\\\\\Controllers\\\\\\\\ProductionLotReportController.cs:line 40ClientConnectionId:6b599d7b-8c08-4aa9-be5b-8678e5e6deefError Number:-2,State:0,Class:11System.InvalidOperationException: The null value cannot be assigned to a member with type System.Int32 which is a non-nullable value type.   at Read_PendingDeliveryElement(ObjectMaterializer`1 )   at System.Data.Linq.SqlClient.ObjectReaderCompiler.ObjectReader`2.MoveNext()   at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection)   at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source)   at PCSIntegration.Controllers.PendingDeliveriesController.GetPendingDeliveriesFromDb(Guid newKey) in E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\156434433\\\\\\\\DHAPPS25-PCSIT182-JOB1\\\\\\\\PCSIntegration\\\\\\\\Controllers\\\\\\\\PendingDeliveriesController.cs:line 237   at PCSIntegration.Controllers.PendingDeliveriesController.GetPendingDeliveries(Int32 numbersOfTickets\', \'Comment 47: String key\', \'Comment 48: List`1 wrongList\', \'Comment 49: Int32 pcsId) in E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\156434433\\\\\\\\DHAPPS25-PCSIT182-JOB1\\\\\\\\PCSIntegration\\\\\\\\Controllers\\\\\\\\PendingDeliveriesController.cs:line 35System.Data.SqlClient.SqlException (0x80131904): Transaction (Process ID 57) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.   at PCSIntegration.Controllers.PendingDeliveriesController.InsertPendingDeliveriesImport(Int32 numbersOfTickets\', \'Comment 50: Guid newKey\', \'Comment 51: Int32 pcsId) in E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\156434433\\\\\\\\DHAPPS25-PCSIT182-JOB1\\\\\\\\PCSIntegration\\\\\\\\Controllers\\\\\\\\PendingDeliveriesController.cs:line 118   at PCSIntegration.Controllers.PendingDeliveriesController.GetPendingDeliveries(Int32 numbersOfTickets\', \'Comment 52: String key\', \'Comment 53: List`1 wrongList\', ""Comment 54: Int32 pcsId) in E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\156434433\\\\\\\\DHAPPS25-PCSIT182-JOB1\\\\\\\\PCSIntegration\\\\\\\\Controllers\\\\\\\\PendingDeliveriesController.cs:line 33ClientConnectionId:6b599d7b-8c08-4aa9-be5b-8678e5e6deefError Number:1205,State:51,Class:13{code}\'"", ""Comment 55: \'Hi,In errors I can see repeating message about timeouts and deadlocks in database. So probably restart of SQL could help.However"", \'Comment 56: there are also errors with nulls. For this case we need to run profiler but we do not have access...Please\', ""Comment 57: verifyRegards\'"", ""Comment 58: \'Hi do you mean we need to resatart sql services? and Is that permanent solving or temporary"", ""Comment 59: we afraid issue comes again after restart SQL. for profiler you need access from SQL Server side?\'"", \'Comment 60: ""You can retsart here (please\', ""Comment 61: see example)!image-2023-03-15-08-40-16-943.png!I\'m not able to ensure you for 100% that this will help forever.Below examples of timeout / deadlock errors{code:java}System.Data.SqlClient.SqlException (0x80131904): Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding.Operation cancelled by user.The statement has been terminated. ---> System.ComponentModel.Win32Exception (0x80004005): The wait operation timed out at System.Data.SqlClient.SqlConnection.OnError(SqlException exception"", \'Comment 62: Boolean breakConnection\', \'Comment 63: Action`1 wrapCloseInAction) at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception\', \'Comment 64: Boolean breakConnection\', \'Comment 65: Action`1 wrapCloseInAction) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj\', \'Comment 66: Boolean callerHasConnectionLock\', \'Comment 67: Boolean asyncClose) at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior\', \'Comment 68: SqlCommand cmdHandler\', \'Comment 69: SqlDataReader dataStream\', \'Comment 70: BulkCopySimpleResultSet bulkCopyHandler\', \'Comment 71: TdsParserStateObject stateObj\', \'Comment 72: Boolean& dataReady) at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName\', \'Comment 73: Boolean async\', \'Comment 74: Int32 timeout\', \'Comment 75: Boolean asyncWrite) at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion\', \'Comment 76: String methodName\', \'Comment 77: Boolean sendToPipe\', \'Comment 78: Int32 timeout\', \'Comment 79: Boolean& usedCache\', \'Comment 80: Boolean asyncWrite\', \'Comment 81: Boolean inRetry) at System.Data.SqlClient.SqlCommand.ExecuteNonQuery() at System.Data.Linq.SqlClient.SqlProvider.Execute(Expression query\', \'Comment 82: QueryInfo queryInfo\', \'Comment 83: IObjectReaderFactory factory\', \'Comment 84: Object[] parentArgs\', \'Comment 85: Object[] userArgs\', \'Comment 86: ICompiledSubQuery[] subQueries\', \'Comment 87: Object lastResult) at System.Data.Linq.SqlClient.SqlProvider.ExecuteAll(Expression query\', \'Comment 88: QueryInfo[] queryInfos\', \'Comment 89: IObjectReaderFactory factory\', \'Comment 90: Object[] userArguments\', \'Comment 91: ICompiledSubQuery[] subQueries) at System.Data.Linq.SqlClient.SqlProvider.System.Data.Linq.Provider.IProvider.Execute(Expression query) at System.Data.Linq.DataContext.ExecuteMethodCall(Object instance\', \'Comment 92: MethodInfo methodInfo\', \'Comment 93: Object[] parameters) at System.Data.Linq.DataContext.ExecuteCommand(String command\', \'Comment 94: Object[] parameters) at PCSIntegration.Controllers.ProductionLotReportController.ReleaseRawMaterialsForProduction(ProductionLotReport report\', \'Comment 95: Int32 pcsId\', \'Comment 96: DataContext dc) in E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\156434433\\\\\\\\DHAPPS25-PCSIT182-JOB1\\\\\\\\PCSIntegration\\\\\\\\Controllers\\\\\\\\ProductionLotReportController.cs:line 195 at PCSIntegration.Controllers.ProductionLotReportController.SavePcsProductionLotReport(ProductionLotReport report\', \'Comment 97: Int32 pcsId) in E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\156434433\\\\\\\\DHAPPS25-PCSIT182-JOB1\\\\\\\\PCSIntegration\\\\\\\\Controllers\\\\\\\\ProductionLotReportController.cs:line 40ClientConnectionId:6b599d7b-8c08-4aa9-be5b-8678e5e6deefError Number:-2,State:0,Class:11{code}{code:java}System.Data.SqlClient.SqlException (0x80131904): Transaction (Process ID 57) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. at PCSIntegration.Controllers.PendingDeliveriesController.InsertPendingDeliveriesImport(Int32 numbersOfTickets\', \'Comment 98: Guid newKey\', \'Comment 99: Int32 pcsId) in E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\156434433\\\\\\\\DHAPPS25-PCSIT182-JOB1\\\\\\\\PCSIntegration\\\\\\\\Controllers\\\\\\\\PendingDeliveriesController.cs:line 118 at PCSIntegration.Controllers.PendingDeliveriesController.GetPendingDeliveries(Int32 numbersOfTickets\', \'Comment 100: String key\', \'Comment 101: List`1 wrongList\', \'Comment 102: Int32 pcsId) in E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\156434433\\\\\\\\DHAPPS25-PCSIT182-JOB1\\\\\\\\PCSIntegration\\\\\\\\Controllers\\\\\\\\PendingDeliveriesController.cs:line 33ClientConnectionId:6b599d7b-8c08-4aa9-be5b-8678e5e6deefError Number:1205,State:51,Class:13{code}""\', ""Comment 103: \'is that exchange DB?in 10.62.1.6 we already restart sql but PLR still not sync to DHP\'"", ""Comment 104: \'Could you please provide us withconfig file of our PCS Agent?Regards\'"", ""Comment 105: \'[^confpcs.txt] _(4 kB)_\'"", ""Comment 106: \'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 107: \'hii assigned kotrak11 as sysadmin for SQLPls help to check\'"", ""Comment 108: \'Could you also please restart Plant Agent service?\'"", ""Comment 109: \'plant agent service already restarted\'"", ""Comment 110: \'And what are the credentials to Plant application in Bekasi?\'"", ""Comment 111: \'for the terminal server? you can use kotrak account or your account with domain apac\'"", ""Comment 112: \'no"", ""Comment 113: here!image-2023-03-15-09-57-46-819.png!\'"", ""Comment 114: \'you can this account"", ""Comment 115: i think that was kotrak engineer!image!\'"", ""Comment 116: \'!image-1!\'"", ""Comment 117: \'or you can use admin with no password!image-2!\'"", ""Comment 118: \'This is for admin!image-2023-03-15-10-36-39-340.png!\'"", ""Comment 119: \'Use this : User : aleksandraPass : alek2023\'"", ""Comment 120: \'hi,i see on PLR form"", \'Comment 121: there are a lot of PLR was coming\', ""Comment 122: do you found the route cause?\'"", ""Comment 123: \'Przesłany - rozliczony!image-2023-03-15-12-02-20-292.png!\'"", \'Comment 124: ""Yes. We found the root cause. These are timeouts. To process PLR\', \'Comment 125: usage of raw material has to be released. It is done by verification of deliveries. We can see you have a lot of Articles / Items that have even 8 thousands deliveries registered but not settled. No column name = number of deliveries:!image-2023-03-15-12-12-28-997.png!Taking for example article code6100312\', \'Comment 126: we can see a lot of historic deliveries and one delivery issued *4 years* *ago* for nearly one *billion* kg / tones (what is the measure for you?) we have *expiry date* that never comes\', \'Comment 127: some incorrect Serial number (not a regular number of PLR) and Last change date dated for *today* which means that weird delivery is in usage. Checking all those deliveries\', \'Comment 128: one PLR takes more than 30 seconds. Anticipating your question\', ""Comment 129: no. Adding RAMs to SQL server won\'t help. Or will help by 1-2 months. The only solution is to clean this mess with deliveries.For now I have pushed PLRs to plant. And executed manualy two of them"", \'Comment 130: each has taken about 32 second. *This means Timeout*. When you will confirm them\', \'Comment 131: they should settle. *But only when you do the cleaning with deliveries*. Otherwise\', \'Comment 132: the issue reappears. Soon.Regards""\', ""Comment 133: \'We can also as a workaround allow PLR to appear in DHP but again"", \'Comment 134: as I mentioned before\', \'Comment 135: until Deliveries are not cleaned\', ""Comment 136: every PLR Confirming will result in timeout.\'"", ""Comment 137: \'So what we need to do to handle the timeout and sync plr from pcs can back normal again?\'"", ""Comment 138: \'I have read you detail explanation bellow"", \'Comment 139: thank you for your advice\', ""Comment 140: i’ll discuss internally about cleaning delivery\'"", ""Comment 141: \'Clean up the mess with deliveries.Those numbers are deliveries with Stock greater than 0 kg. The mechanism verifies delivery by delivery.!image-2023-03-15-13-12-40-332.png!There are 166 iArticle with number of deliveries more than 100\'"", ""Comment 142: \'No issue"", \'Comment 143: please\', ""Comment 144: let us know if leave this task open and for instance lower the priority or we close it.BR\'"", ""Comment 145: \'One question"", \'Comment 146: about cleaning delivery.Do you mean whe need to clear data from the table or what? Because you also said about serial number and settle\', ""Comment 147: So clean delivery = clean table data orClean delivery = tidy up the data?\'"", ""Comment 148: \'Tidy up i mean stock count\'"", \'Comment 149: ""I mean stock count. I don\\\'t know if I\\\'m right\', \'Comment 150: but now it looks you have stocks with deliveries from 2019. I do not believe you still have those items. Maybe Inventory would be good idea""\', ""Comment 151: \'So this issue caused of delivery that make it huge of qty stock"", ""Comment 152: and we need to adjust back and do stock count.This issued not caused of number of row transaction.Am i right?\'"", ""Comment 153: \'Yes"", \'Comment 154: you are right. The issue is that one transaction takes a lot of time because procedure verify all deliveries greater than 0. After 30 seconds there is a timeout and information that transaction is stopped. And then next transaction arrives that takes to much time. Little workaround would be to add RAM into DB server\', ""Comment 155: but this would help for a month or two\'"", ""Comment 156: \'Hi aleksandra,Could we make a teams call for a minute"", ""Comment 157: just want to make it clear.\'"", ""Comment 158: \'sure\'"", ""Comment 159: \'hi alek,Please confirm and deliver if you finish the manual for inventory\'"", ""Comment 160: \'Hi,We have contacted with Eric to analize how to solve Inventory issue in the best way. We will inform you as soon as we get reply from Eric.Regards\'"", ""Comment 161: \'Hi,Have you done stock count? Can we close this task?Regards\'"", ""Comment 162: \'Hi,we have an discussion with eric about clean delivery topic"", ""Comment 163: may you can close this ticket please.\'"", ""Comment 164: \'Thank you.\']""]\nRelated Issues:\n[]\n\n### End'}"
272,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8760\n\n### Instruction:\nHi,\r\nwe need recipe 9645 Ver 23 sub x for produce but it can not send to DHP. we try to add more sub but still not. need this recipe so it should be P1\r\n\n\n### Response:\n[""Comment 1: [\'!image!!image-1!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Hi"", ""Comment 4: [~Hardy.huy@deheus.com]We are having problem with connecting to the DHP server in Bac Lieu.Could you verify and please give us a feedback.!image-2023-03-15-05-55-11-000.png!Same problem for server with DHC services!image-2023-03-15-05-56-42-652.png!\'"", ""Comment 5: \'Please try with user Kotrak11\'"", ""Comment 6: \'Login dhp: ADMIN"", ""Comment 7: Today@2023\'"", \'Comment 8: ""Now it\\\'s ok. Thank you!We are working on this issue.""\', ""Comment 9: \'[~Hardy.huy@deheus.com] Could you check access to server 113.161.145.252:3370 ?!image-2023-03-15-06-39-12-815.png!I understand that in DHP this recipe is ok?!image-2023-03-15-06-44-30-490.png!On server 10.84.1.22 we do not have access to the Kotrak folder!image-2023-03-15-06-45-04-971.png!\'"", ""Comment 10: \'if you want to use DHC"", ""Comment 11: you can try on 10.84.1.22. and you are admin on .1.22 now\'"", ""Comment 12: \'I have resynced recipes but please let me know if this recipe is the one requested:!image-2023-03-15-09-33-45-075.png!\'"", ""Comment 13: \'Could you please let us know where the service of plant agent is? Or could you please restart plant agent and let us know?Regards\'"", \'Comment 14: ""W dhcservice nie ma subwersji {code:java}SELECT pr.*  FROM [dbo].[ProductionRecipes] pr where id in(SELECT ProductionRecipeId  FROM [dbo].[Technologies]  where code like \\\'%9645%\\\'  and Version=23){code} !screenshot-1! nie ma towaru w dhcservice TC9645{code:java}SELECT pr.ItemId  FROM [Evolution_DHCService_VN].[dbo].[Items] i right join    [Evolution_DHCountry_VN].[dbo].[ProductionRecipeIngredients] pr on i.Id=pr.ItemId  where pr.ProductionRecipeId=\\\'214167DC-9DD8-459B-A5B6-CD1EEAE669D8\\\'  and i.code is null{code}""\', ""Comment 15: \'Hi"", \'Comment 16: the item TC9645 added to the subversion is not linked and missing for Bestmix items\', ""Comment 17: !screenshot-2! .When it will be linked you should send productionrecipes and then technology from the level of DHC.Thank you.\'"", ""Comment 18: \'after i linked item. it working"", ""Comment 19: please close ticketthank you\']""]\nRelated Issues:\n[]\n\n### End'}"
273,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8759\n\n### Instruction:\nError ID6370061 – Proszę o usunięcie problemu produkcja w toku.\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'The error is Production lot for this BOM already existslotnumber - 0272140323025pcslotid - 230314025BomHeaderID - 55190 for article 915916-W25"", ""Comment 4: I can cancel this message then production should start.\'"", ""Comment 5: \' !screenshot-1! \'"", ""Comment 6: \'Message has been canceled"", ""Comment 7: messages are now processing.\'"", ""Comment 8: \'Messages have been processed.\'"", ""Comment 9: \'Błąd jest anulowany"", ""Comment 10: ale na tą chwile kontenery jedzą w kółko\'"", ""Comment 11: \'I get information that it works now.\'"", ""Comment 12: \'Jest juz ok.Zgłoszenie do zamknięcia \']""]\nRelated Issues:\n[]\n\n### End'}"
274,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8758\n\n### Instruction:\nOn document PI-FNL/2023/0069 we have two lines. However only the first line is visible in the round.\r\n\r\nHow can we get the line with AANH on the round?\n\n### Response:\n[""Comment 1: [\'!image-1!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'But the BTWF is visble on the round. Could you give some more information?\'"", \'Comment 4: \\\'Hi[~bgeytenbeek@deheus.com],the type of purchase is propably wrong. We display only""Registered purchase"" Invoices on Round list.But the linked Sales Invoice have wrong round category:!image-2023-03-14-15-31-35-580.png!Best regards,Grzegorz\\\'\', ""Comment 5: \'Bert"", ""Comment 6: is this solved?\'"", ""Comment 7: \'Confirmed that can be closed\']""]\nRelated Issues:\n[]\n\n### End'}"
275,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8757\n\n### Instruction:\nPlease give us rights to start new process in NAS.\r\nIn this case reopen a round 817005/0018/0003.\r\nUs = Christine de Jong and Bert Geijtenbeek\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: \'WHat is the status of this?\'"", ""Comment 4: \'{color:black}Hi Mitch,{color} {color:black}{color} {color:black}I haven’t seen any action from Kotrak on this task.{color} {color:black}Issue still pending.{color} {color:black}{color} {color:black}{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Christinede{color} |{color:#000001} {color} |{color:#000001} Jong{color} |  {color:#000001}MedewerkerContractadministratie{color} | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.de-heus.nl/]>{color} | |  *{color:#006FB7} *DEHEUSVOEDERSB.V.*{color}* | | | |{color:#000001} Postbus396 6710BJEde \\\\u200b{color} | |{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} | | |{color:#000001} T:0318675567{color} |  {color:#000001}KvK14626985{color}   _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | | !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | | !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} | | !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} |        *Van:* Mitch van Bovene (Jira) <jira@kotrak.com>   *Verzonden:* dinsdag 21 maart 2023 11:38  *Aan:* Jong"", ""Comment 5: Christine de <CJong@deheus.com>  *Onderwerp:* DGS-8757 Rights to start new process   \'"", \'Comment 6: ""[~CJong@deheus.com]and Bert have added right\\\'s to start new proces now.""\', ""Comment 7: \'{color:black}Thanks Tomasz it works now{color} {color:black}😊{color}{color:black}{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Christinede{color} |{color:#000001} {color} |{color:#000001} Jong{color} |  {color:#000001}MedewerkerContractadministratie{color} | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.de-heus.nl/]>{color} | |  *{color:#006FB7} *DEHEUSVOEDERSB.V.*{color}* | | | |{color:#000001} Postbus396 6710BJEde \\\\u200b{color} | |{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} | | |{color:#000001} T:0318675567{color} |  {color:#000001}KvK14626985{color}   _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | | !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | | !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} | | !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} |        *Van:* Tomasz Zygoń (Jira) <jira@kotrak.com>   *Verzonden:* dinsdag 21 maart 2023 11:59  *Aan:* Jong"", ""Comment 8: Christine de <CJong@deheus.com>  *Onderwerp:* DGS-8757 Rights to start new process   \']""]\nRelated Issues:\n[]\n\n### End'}"
276,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8756\n\n### Instruction:\nDHC keeps throwing this error message for certain VT\'s when we regenerate the VT the error message eventually updates to the correct one. \r\n\r\nwe are also still experiencing issues with PLR\'s appearing as though they have not generated but are just not linked to their applicable Job Orders.\r\n\r\n\n\n### Response:\n[\'Comment 1: [\\\'Spędziliśmy sporo czasu z Pawłem nad tym tematem wDGS-8341. RCA dotyczy już samego błęduError: ""SystemOutOfMemory Exception""\', \'Comment 2: który powodowany jest wielokrotnym otwarciem ERP Inta. Co w dalszej perspektywie powoduje\', \'Comment 3: że dokumenty JO\', \'Comment 4: IR + i IR - nie przypisują się do PLRaZ naszej strony zostało sporo zrobione. Prosimy o wsparcie Dev w sprawie ERP Inta\', \'Comment 5: dlaczego nie potrafi się ""skillować"" :)Z góry ogromne dzięki :)\\\'\', ""Comment 6: \'Hi,Please be informed that this issue will be analized and verified by ou Dev Team to find root cause of the issue.We are waiting for more details and will be back with further information as soon as possible.Regards\'"", ""Comment 7: \'Hello"", ""Comment 8: any feedback? \'"", ""Comment 9: \'[~aleksandra.przybylek@kotrak.com]jaka jest wersja ERP INT w RPA?\'"", ""Comment 10: \'[~piotr.chmielarski@kotrak.com]:!image-2023-04-21-07-20-16-871.png!\']""]\nRelated Issues:\n[\'DGS-8341\']\n\n### End'}"
277,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8755\n\n### Instruction:\nHi\r\n\r\nWe started using integrated login, however, some users (aleatory) gets another user different of what is logged in on computer.\r\n\r\nImportant: the user that DHP displayed in profile, never logged in on this computer.\r\n\r\nThis task still happening a lot and is related to DHITS-715. You can check on it for more details\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: \'Hi [~mberbert@deheus.com],We need to perform some R&D in order to check if there is any option to make it work once the DHP is hosted on IIS because it can finally turn out that we cannot do anything since technology does not allow us.If you face trouble using integrated login please use a standard login method.\'"", ""Comment 4: \'Hi [~mberbert@deheus.com],I created a GDC-902 for the R&D.\']""]\nRelated Issues:\n[\'DAP-13359\']\n\n### End'}"
278,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8754\n\n### Instruction:\nwe have problem in production quantity, we closed productions, but when we look on the stock, we have total quantity dosade and not the final quantity added manually.\r\n\r\nExample 0871270223017 - SUR7562-P-MD, final quantity 6000kg, but on stock (barcode) 5995,318kg. I fixed by inventory to use, but we need to know why the quantity is wrong for some productions.\r\n\r\nIn the report is still wrong. Could you fix the final quantity for report? and Why do we have this error?\r\n\r\nThank you\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 3: \\\'Różnica 4,7 kgBo mamy kolumnę ""Quantity"" z całym stanen i ""Quantity on hand""\', \'Comment 4: która wyświetla dostępny stan\', ""Comment 5: czyli quantity - reservations\'"", ""Comment 6: \'!image-2023-03-14-11-39-07-036.png!!image-2023-03-14-11-39-31-136.png!\'"", ""Comment 7: \'!image-2023-03-14-13-34-34-797.png!\'"", ""Comment 8: \'Taka ilość przyszła z PCSa!image-2023-03-16-11-34-41-075.png!\'"", ""Comment 9: \'BR:Różne ilości w SE i w PROD. !TO! 153 R.8.51. Zrobiłam PLRa z PCSA 2000kg.2. Edytowałam PLRa (Finished) i zwiększyłam ilość na nagłówku.3. Zapisałam i potwierdziłam a w drugim przypadku od razu potwierdziłam(/) Ilości w prod"", ""Comment 10: se i na stock unitach są poprawne !170_8.5! \'"", ""Comment 11: \'hej [~aleksandra.przybylek@kotrak.com],rozmawiałem jeszcze dzisiaj z Olą Masternak i nie udało nam sie tego zreprodukować i nie bardzo wiemy co możemy z tym wiecej zrobić.Proponuje zamknać ticketa do momentu podobnego zgłoszenia. RCA tutaj w tym momencie na nic sie nie zda. \'"", ""Comment 12: \'[~maciej.dobrzanski@kotrak.com] [~aleksandra.masternak@kotrak.com] Jasne"", ""Comment 13: dzieki :)\'"", ""Comment 14: \'Dear [~psilva@deheus.com] We did not reproduce your issue. Our suggestion is to close this task and if issue reoccures"", ""Comment 15: we will try again.Regards\']""]\nRelated Issues:\n[]\n\n### End'}"
279,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8753\n\n### Instruction:\nThere is an pallet on EXP_23  in the background in the database. however, it has been loaded for a long time and was scanned properly at that time.\r\n\r\nWhat is the course this still exists is the question.\r\n\r\nHowever, this can result in an error message because the maximum number of pallets for this location has been exceeded. We can solve this problem by increasing this max number wich is not correct.\r\n\r\nIs it possible to remone the pallet so every thing is correct.\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 2: ""{code:java}  FROM [DHP_NL_PROD].[dbo].[WMSStorageElements]  where StE_Code=\\\'exp_23\\\'{code}""\', ""Comment 3: \'Can i get a problematic barcode?\'"", ""Comment 4: \'Hello"", \'Comment 5: any update here\', ""Comment 6: can i get a problematic barcode?\'"", ""Comment 7: \'!image!\'"", \'Comment 8: ""{code:java}select *  FROM [DHP_NL_PROD].[dbo].[WMSStorageElements]  where StE_Code=\\\'exp_23\\\'  or ste_id in(18034,101596)  select RgM_StEId,RgM_Quantity,RgM_IsActivated,RgM_IsReleased,* from dbo.RegisterMappings where RgM_StEId in(101593,101596)  or rgm_code=\\\'187190811000403490\\\'{code} !screenshot-1! ""\', ""Comment 9: \'The given code 187190811000403490 is assigned to the location - EXP_26. Is This code correct?May I ask for additional information:At exactly what operation on the scanner is this message(maximum number of pallets for this location has been exceeded)?The given code is already released"", ""Comment 10: a change can be created as GDC so that codes with the released status are not taken into account for capacity.\'"", ""Comment 11: \'Hi"", ""Comment 12: please send a feedback about our last comment. Thank you.\']""]\nRelated Issues:\n[]\n\n### End'}"
280,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8752\n\n### Instruction:\nPlease create a new Intense user for Hans van de Broek.\r\n\r\nSame permissions as Koen Huibers or Steffen Driesen. I selected ALL in the dropdown above, as I have no idea what the correct sector should be, but he works for the Belgian administration.\r\n\r\nThanks.\n\n### Response:\n[""Comment 1: [\'Hi,as I can see"", ""Comment 2: we have this user in Intense right now. I made changes on his settings yesterday. Link: https://helpdesk.kotrak.com/browse/DGS-8743Can we close this task?Best regards,Grzegorz\'"", ""Comment 3: \'{color:black}I have no access to that request"", \'Comment 4: but I’ll ask Hans if he can proceed.{color} {color:black}{color} {color:black}Thanks!{color} {color:black}{color} | |{color:#000001} Kindregards,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Martijn{color} |{color:#000001} {color} |{color:#000001} Meier{color} |  {color:#000001}ApplicationEngineer{color} | | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.deheus.com/]>{color} | |  *{color:#006FB7} *DEHEUSANIMALNUTRITIONB.V.*{color}* | | | |{color:#000001} P.O.Box396 6710BJEde TheNetherlands{color} | |{color:#000001} Rubensstraat175 6717VEEde TheNetherlands{color} | | |{color:#000001} M:{color}{color:#000001}{color}{color:#000001}+31621679216{color}{color:#000001} <tel:+31%206%2021%20679%20216>{color} |  {color:#000001}CoC16011201{color}   _{color:#000001} _Thise‑mailmessageanditsattachmentsaresubjecttothedisclaimer_ _publishedonthewebsiteof_{color}_{color:#000001} _+{color}[{color:#000001}{color}{color:#000001} _+ DeHeusAnimalNutrition+_{color}{color:#000001} {color}|https://www.deheus.com/disclaimer]{color:#000001} {color}+__{color:#000001} _._{color}_ | | !image002! <[https://www.facebook.com/deheusanimalnutrition]>{color:black}{color} | | !image003! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image004! <[https://www.linkedin.com/company/royal-de-heus/mycompany/]>{color:black}{color} | | !image005! <[https://www.instagram.com/de_heus_animal_nutrition/]>{color:black}{color} |        *From:* Grzegorz Materla (Jira) <jira@kotrak.com>   *Sent:* dinsdag 14 maart 2023 08:40  *To:* Meier\', ""Comment 5: Martijn <mmeier@deheus.com>  *Subject:* DGS-8752 New Intense user Hans Van De Broek   \'"", ""Comment 6: \'Can this be closed?\'"", ""Comment 7: \'Yes"", ""Comment 8: can be closed!\']""]\nRelated Issues:\n[\'DGS-8743\']\n\n### End'}"
281,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8751\n\n### Instruction:\nPRO 277/3/23 is not syncing to the exchange.\r\nSO, Business Partner, Item. Base Item, Recipe and technology synced and resent. \r\n\r\ninitial PROs were 256 and 259 after sync of elements PROs were cancelled and PRO 277 was created.\r\nthere are no error messages. services were restarted \n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'This document should be in !image-2023-03-13-15-55-14-065.png!Can you verify?\'"", \'Comment 3: ""{code:java}SELECT *  FROM [DHExchange70].[dbo].[SqlApiRequestLog]  where Parameters like \\\'%9800%\\\'  order by 1 desc{code}{code:java}  FROM [DHExchange70].[dbo].[ProductionOrders]  where CreateDate>\\\'2023-03-01 15:19:58.1423367\\\'  order by DocumentNumber desc{code}""\', ""Comment 4: \'Hello"", ""Comment 5: yes thank you task can be closed \']""]\nRelated Issues:\n[]\n\n### End'}"
282,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8750\n\n### Instruction:\nPlease remove/disable additional technologies for Andel, all AW967383* variants\r\n\r\nKind regards,\r\nRob.\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Hi Rob,I have disabled requested additional technologies.Regards\'"", ""Comment 3: \'Thank you Aleksandra"", ""Comment 4: the ticket can be closed.Kind regards,Rob.\'"", ""Comment 5: \'Thank you.Regards\']""]\nRelated Issues:\n[]\n\n### End'}"
283,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8749\n\n### Instruction:\nReipes 970187 and 970186 are in DHC Compound but not in DHP Helmond.\r\nThere were some issues (not linked etc.) that I fixed, but still no success.\r\n\r\nRecipes should have been in Helmond thursday last week.\r\n\r\nKind regards,\r\nRob.\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'But in DHC they are for Utrecht:!image-2023-03-13-14-19-53-071.png!!image-2023-03-13-14-20-28-899.png!!image-2023-03-13-14-22-12-696.png!Please"", ""Comment 3: advise.Regards!image-2023-03-13-14-22-12-696!\'"", ""Comment 4: \'That explains why they are not in DHP Helmond.My bad. Sorry for wasting your time.Multitasking is not easy for a man :(The recipes are in Utrecht"", ""Comment 5: the ticket can be closed.Kind regard,Rob.\'"", ""Comment 6: \'No issue Rob.Regards\']""]\nRelated Issues:\n[]\n\n### End'}"
284,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8748\n\n### Instruction:\nWe are dealing more and more with collective invoices and reports from slaughteries. This means we need to adjust the way of registering the Hakdermatitis and Footsolescores a bit. We need to be able to calculate the weighted average scores.\r\n\r\nWhat needs to be changed to the table:\r\n* In the table ""Footsolescore"" on the tab other conditions in the SR we need to add a column called ""Quantity"". In this field the user can manually enter the number of animals that were in the stable at that time.\r\n* The label of the table ""Footsolescore"" can be removed. We will use this table for feedsalescores and the hakdermatitis.\r\n* We need to add a column called ""Hakdermatitis"" in the table.\r\n\r\n* Below the field ""Hakdermatitis"" we need to add a field called ""Footsolescore"".\r\n* In this new field we need to calculate and show the weighted average of the Footscolescores. The calculation is in the attachment. The black text is visible on screen, the red text are calculations in the background. \r\n* In the current fields ""Hakdermatitis"" we should show the weighted average of the Hakdermatitis. The calculation method is similar, but then we should take the values from the new column ""Hakdermatitis"" in the table.\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: \'Prepared on a testing server.!image-2023-04-03-10-12-23-032.png!\'"", ""Comment 4: \'First picture:•\\\\tPlease rename “Score” into “Footsole score”.•\\\\tThe Hakdermatitis should be a percentage.Second picture:•\\\\tWhy is the Name of the stable empty every time? I would expect a name or stable number in here.•\\\\tWe should have a multiple for Hakderm.*Quantity as well. Third picture:The footsolescore is calculated correct. We should have the same calculation for the Hakdermatitis and that can be shown above the Footsolescore in the current field “Hakdermatitis”.Are we able to define the default columns that all users see? Now relevant columns are hidden.!image-1!!image-2!!image-3!\'"", ""Comment 5: \'First picture * Please rename “Score” into “Footsole score”. *Done* * The Hakdermatitis should be a percentage. *Done*   !image-2023-04-04-15-02-39-708.png!Second picture: * Why is the Name of the stable empty every time? I would expect a name or stable number in here.To get anything in this label we need to add on a farmer some stables!image-2023-04-04-15-05-33-483.png!!image-2023-04-04-15-06-58-872.png! * We should have a multiple for Hakderm.Quantity as well. *Done**!image-2023-04-04-15-04-47-586.png!*Third picture: * The footsolescore is calculated correct. We should have the same calculation for the Hakdermatitis and that can be shown above the Footsolescore in the current field “Hakdermatitis”. *Done*Filed is now calculated ((sum(Hakderm.*Quantity)/ sum (Quantity))*100)\'"", ""Comment 6: \'It is not the name of the stable that is presented in the column"", \'Comment 7: it looks like the stable number. In that case please rename the stable number.Everything else looks perfect\', ""Comment 8: this can be moved to PROD.\'"", ""Comment 9: \'Moved to production\'"", ""Comment 10: \'[~tomasz.zygon@kotrak.com][~damian.swistek@kotrak.com]Do sprawdzenia zaokrąglanie wyliczanych wartości w tabelce oraz dzielenie przez zero.W powiązaniu z taskiem https://helpdesk.kotrak.com/browse/DGS-8636\'"", ""Comment 11: \'Uwzględniono zaokrąglenie jak i dzielenie przez zero.\']""]\nRelated Issues:\n[\'DGS-8636\']\n\n### End'}"
285,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8747\n\n### Instruction:\nFor plant Andel, two versions of additional technology was created for 967383. These are incorrect. Please remove these additional technologies.\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: \'Any update? Please change prio to 1. Plant needs the recipe for production.\'"", \'Comment 3: ""Hi Bob,Please let me know what is the exact case\', ""Comment 4: additional technology has been created incorrectly and it shouldn\'t be in the system or you just want to correct one of ingredioents in additional technology. If this is the case of ingredient"", \'Comment 5: plea eprovide me details.Regards""\', ""Comment 6: \'As per your comment"", ""Comment 7: I am raising priority\'"", ""Comment 8: \'Additional technology for 967383 is no longer valid and should not be in the system. User tried to make subversion with 967383 as ingredient"", \'Comment 9: but that is not working. Recipe for 967383 from Bestmix must be sent to PCSSo\', ""Comment 10: please remove both versions of additional technology 967383\'"", ""Comment 11: \'!image-2023-03-13-12-20-57-060.png!!image-2023-03-13-12-24-17-630.png!!image-2023-03-13-12-24-17-630!\'"", ""Comment 12: \'Done. Please"", ""Comment 13: verify on your side.Regards\'"", ""Comment 14: \'Thank you. Recipe is now sent to PCS. This ticket can be closed.\'"", ""Comment 15: \'Thank you\']""]\nRelated Issues:\n[]\n\n### End'}"
286,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8746\n\n### Instruction:\nlack of data from expedition after loading truck\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: \'{code:java}SELECT prl_id,PrL_Code,PrL_SimpleExpeditionMode,PrL_ExpeditionSiloStockEnabled  FROM [DHP_Grodzisk].[dbo].[PcsProductionLine]{code} !screenshot-2!  !screenshot-1! !image-2023-03-14-14-49-56-808!\'"", ""Comment 4: \'I just want to confirm that the problem was with the element for this VT and it generally works at the factory?\'"", ""Comment 5: \'This is only one of the examples"", ""Comment 6: there are more\'"", ""Comment 7: \'Hej"", ""Comment 8: potrzebna pomoc w analizie sychronizacji z pcs.Jak widać na przykładzie nie przypisują się dane z ekspedycji. Było już RCA DGS-5802 - ale widzę że dla Grodziska jest to aktywne. (ostatni komentarz nasz internal) [DHP_Grodzisk].[dbo].[PcsProductionLine].\'"", ""Comment 9: \'please put it on hold\'"", ""Comment 10: \'w pcs były robione zmiany - może po temacie. Ewelina da znać. \'"", ""Comment 11: \'Hello"", ""Comment 12: about this ticket - do you have any updates?Thank you.\']""]\nRelated Issues:\n[\'DGS-5802\']\n\n### End'}"
287,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8745\n\n### Instruction:\nDhp Johnson is not responding\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-03-13-09-30-38-746.png!\'"", ""Comment 3: \'Please check the application is already running.\'"", ""Comment 4: \'[^log20230313.txt]\'"", ""Comment 5: \'working"", ""Comment 6: kindly close\']""]\nRelated Issues:\n[]\n\n### End'}"
288,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8744\n\n### Instruction:\nCould you add ""payment method"" as column in Inbox?\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Is this done?\'"", ""Comment 3: \'Not yet"", ""Comment 4: could you specify to which documents it should be displayed?Only for Sales Invoices and Purchase Invoices?\'"", ""Comment 5: \'Yes please\'"", \'Comment 6: ""\\\'Payment method\\\' column has been added to Inbox view as a new column. It\\\'s available on header bar to choose as a new colum to add to view. The value is displayed for Purchase and Sales Invoices.Please verify - it\\\'s done on test and production environment.!image-2023-03-27-12-59-20-634.png!""\', ""Comment 7: \'This can be closed.\']""]\nRelated Issues:\n[]\n\n### End'}"
289,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8743\n\n### Instruction:\nOur new colleague Hans Van De Broek isn\'t able to login in Intense. On one side \'login NT\' isn\'t ticked and when he tries to login, he needs to update his password but the current password doesn\'t verify. Could you link his account to his domain login again?\n\n### Response:\n[""Comment 1: [\'Hi [~SDriesen@deheus.com],I made changes in user settings. Right now"", ""Comment 2: only Integrated login is set on.Can Hans try to log in again?He\\\\\'s need to remember"", \'Comment 3: that the ""Login NT"" checkbox is need to be marked in login window:!image-2023-03-13-09-13-31-312!Best regards,Grzegorz\\\'\', \'Comment 4: ""Hello Grzegorz,Now he has the \\\'Login NT\\\' ticked automatically\', \'Comment 5: so it works.Thank you.""\', \'Comment 6: ""Excellent\', \'Comment 7: so I\\\'m closing the task.Have a nice day,Best regards,Grzegorz""]\']\nRelated Issues:\n[\'DGS-8752\']\n\n### End'}"
290,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8742\n\n### Instruction:\nHi\r\n\r\nWe have a new project to change all domains of Brazil to LATAM.COM\r\nAt first we will start with Guararapes on 20 of March.\r\nIs there anything that we need to change on DHP/DHC side?\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: \'The subject has been forwarded to the developers. Regarding the domain change"", ""Comment 3: I understand that the login method will also change?Will only the domain change and the passwords and logins will not change?\'"", ""Comment 4: \'[~mberbert@deheus.com] are you going to change domain for users too?\'"", ""Comment 5: \'Hi [~marcin.kleszcz@kotrak.com]I think [~lalmeida1@deheus.com] is the best person to give you the answer.Ludemila"", ""Comment 6: could you please help us?Thank you\'"", ""Comment 7: \'On the DHP side"", \'Comment 8: you need to change the file with configuration because\', \'Comment 9: in the case of GU\', ""Comment 10: the domain is entered there.\'"", ""Comment 11: \'[~mberbert@deheus.com]* changes required:** DHP: YES - configuration (json)** DHC: YES/NO - depends on changes for users.\'"", ""Comment 12: \'Hi! I trie to resume the project:For the migration of the site from Guararapes to the new LATAM domain"", ""Comment 13: we have a few phases:1 - server domain change (March 17)2 - change of user login (weekend 27 to 31 of March).\'"", \'Comment 14: ""Hi [~marcin.kleszcz@kotrak.com]We\\\'ll do the configuration o JSON files by ourselfs. So you can close this task.Thank you very much""\', ""Comment 15: \'Hi [~mberbert@deheus.com]* you will change json files for DHP - ok* but when you will change user login (27-31.03.2023) please let know upfront to : [~przemyslaw.przybyszewski@kotrak.com]"", ""Comment 16:  DHC3.0\'"", ""Comment 17: \'Hi,Cold you please confirm if the only thing that changes will be the domain? In reference to login in to terminal and other servers"", ""Comment 18: will anything change? For example Our login and passwords?Regards\'"", ""Comment 19: \'[~lalmeida1@deheus.com]and what about IP addressess forGuararapes?Regards\']""]\nRelated Issues:\n[]\n\n### End'}"
291,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8741\n\n### Instruction:\nHi\r\n\r\nWe are planning to start DHP x PCS integration for Itaberaí on 15/April.\r\nWhat are the steps you need to take or should we do to accomplish this target?\r\nIs there any specific configuration we need to look at inside DHP?\r\nWe are already drawing new WMS locations and silos.\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: \'The task has been forwarded to the developers.\'"", \'Comment 3: ""[~mberbert@deheus.com]nice to hear that PCS integration will be started.Do you have any processes to be discuss with [~wojciech.wojerz@kotrak.com] and PCS supplier? Who is the supplier? I guess Marcio.For sure we don\\\'t have configuration done in DHP3.0 - PCS\', ""Comment 4: Production lines etc and we don\'t have masterdata in PCS db.On PCS side"", ""Comment 5: they have already PLR\'s created"", \'Comment 6: but I guess on DHP side we don\\\'t need to adjust any data (entityId) ? Do we need to include hyperCare?""\', ""Comment 7: \'Hi [~marcin.kleszcz@kotrak.com]The supplier is Marcio.Itaberaí has the same processes/scenario from Apucarana. No need to discuss new processes with Wojciech.What do you need to make the configuration in DHP3.0 - PCS: Production lines and what else more?Yes"", \'Comment 8: please\', ""Comment 9: incluse hyperCare.Thank you very much!\'"", ""Comment 10: \'[~mberbert@deheus.com]* We need to add** PCS** Production lines** Configuration in json for PCS* We need to synchronize masterdata to PCS DB.\'"", ""Comment 11: \'[~marcin.kleszcz@kotrak.com]I think we can start this before the integration starts"", ""Comment 12: right?Could you please estimate your hours to do it?PCS: SIGAFRAN (from Marcio)There will be two Production lines: PCS-1 and PCS-2You can follow with configuration in json and synchronization of masterdata to PCS DB.Thank you very much\'"", ""Comment 13: \'Hi [~marcin.kleszcz@kotrak.com]Did you have opportunity my last comment?Thank you\'"", \'Comment 14: ""Hello [~mberbert@deheus.com]estimation for PCS integration is:* 48h - the most likely case* +20% - the worst caseActivities include:* development for data migration to PCS* backup of DHP app and DB\\\'s in Itaberai* restore App and DB\\\'s on Kotrak test server* migration to PCS - test* Go live:** DHP configuration:*** PCS*** Production lines*** Configuration in json for PCS** Data migration to PCSNot include:* Consultations with PCS* Hyper care   ""\', ""Comment 15: \'Items Prod vs PCS!image-2023-03-30-14-50-31-800!\'"", ""Comment 16: \'Orders Prod vs PCS!image-2023-03-30-14-51-25-094!\'"", ""Comment 17: \'Stock units!image-2023-03-30-15-02-41-936!\'"", ""Comment 18: \'[~mberbert@deheus.com] as we discussed on the Teams - it looks that the estmation will be less than 48h. We have hours not used from the project for PCS integration in ITA"", ""Comment 19: so we can use these hours.\'"", ""Comment 20: \'Hi [~marcin.kleszcz@kotrak.com]Thank you for this information.Could you please proceed with the configuration?We are planning to integrate PCS and DHP in the middle of may. however we can to start the configuration and migration already.*When is it possible for you to do it?*Thank you\'"", ""Comment 21: \'[~mberbert@deheus.com]first we need to check the integration - next week. And after that we will set up configuration - first or second week in April.\'"", \'Comment 22: ""Hi [~mberbert@deheus.com]we have checked data on DB level\', \'Comment 23: and as you can see\', \'Comment 24: we have a differences between modules. This is only example for:* Items* Orders* SU !diff_PCS! Our proposal is to check in details data integrated to PCS module\', \'Comment 25: before we will start integration with PCS.Estimation for developer:* *16h* - the most likely case* +50% - the worst caseAfter that we can clarify missing data and decide the next step. We will check if we need to prepare scripts for:* insert* update* deleteand estimate hours needed to do these scripts and tests.At the moment we have a *remaining budget* from Itaberai implementation project\', ""Comment 26: so we don\'t need to estimate extra hours yet. Just let me know"", \'Comment 27: if you approve this proposal. If yes\', \'Comment 28: I will plan developer probably for 17-19.04.2023.""\', ""Comment 29: \'Hi [~marcin.kleszcz@kotrak.com]Approved! Do you need to stop the factory to make these tasks?If yes"", ""Comment 30: I need to schedule with the manager first.Thank you\'"", \'Comment 31: ""Hi [~mberbert@deheus.com] thank You for the answer.I will let you know if you need to stop the factory. Another idea is to restore DB\\\'s and App on Kotrak test server.""\', ""Comment 32: \'[~mberbert@deheus.com] * backups are done and downloaded* we will restore IT on our test server.\']""]\nRelated Issues:\n[]\n\n### End'}"
292,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8740\n\n### Instruction:\nHi, \r\n\r\nOur formulation department sent bestmix item for new code(s). However, I could not receive those items in DHC. Affected code(s) list in attached. \r\n\r\nBest Regards, \r\n\r\nClara\n\n### Response:\n[""Comment 1: [\'!DHC_Bestmix_1.PNG|thumbnail!!DHH_Sending.PNG|thumbnail!!image!\'"", ""Comment 2: \'items with code 61028xx witch are in DHH are avaipbe in DHC!image-2023-03-10-19-33-58-129.png!!image-2023-03-10-19-34-29-316.png!Please check.\'"", ""Comment 3: \'We do see them now. May I know what is fix?\'"", ""Comment 4: \'In the end"", \'Comment 5: after analysis\', ""Comment 6: I have resent items from DHH once again. That helped.May I close this ticket?\'"", ""Comment 7: \'yes"", ""Comment 8: please. Thank you\']""]\nRelated Issues:\n[]\n\n### End'}"
293,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8739\n\n### Instruction:\nGood afternoon,\r\n\r\nafter deployment yesterday on plant: Utrecht we have a problem with SPS.\r\nToo many orderlines with same item and other information.\r\n\r\nFor example: SO000075069 on plant: Utrecht.\r\n\r\nWhat\'s happend? Because before deployment we didn\'t have this problem.\r\n\r\nPlease could you investigate this and solve the problem?\r\n\r\nKind regards\r\n\r\nGerard Geerts\n\n### Response:\n[""Comment 1: [\'!MicrosoftTeams-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}exec spGetOrderPrintout \\\'84ACFEC0-F434-4135-8D8E-0338CA88E87F\\\'{code} !image-2023-03-13-10-59-23-139.png! gdzie!image-2023-03-13-10-59-51-935.png!poprawiono procedurespGetOrderPrintout. Informacja o zakresie modyfikacji zgodnie z konsultacją z Maciejem Dobrzańskim poszła do Oli Masternak""\', ""Comment 4: \'Printout should provide correct information. Please check.\'"", ""Comment 5: \'[~bartlomiej.brzek@kotrak.com] poprawiona wersja procedury tutaj:http://10.10.10.52:82/projects/PLA3/repos/dhp30implementations/browse/BASE/PRINTOUTS/NL/8.3.0/SQL/spGetOrderPrintout.sqlpodegrajcie proszę na wszystkie fabryki w NL\'"", ""Comment 6: \'Please"", ""Comment 7: let me know if expect any additional actions from us regarding this issue? Can we close this ticket?\'"", ""Comment 8: \'The issue has been fixed on our side. Please"", ""Comment 9: verify if it is working fine for you and let us know if we can close this task.Regards\'"", ""Comment 10: \'Thank you"", ""Comment 11: we will verify this.\'"", ""Comment 12: \'Please"", ""Comment 13: let me know if expect any additional actions from us regarding this issue? Can we close this ticket?\'"", ""Comment 14: \'Please"", ""Comment 15: let me know if expect any additional actions from us regarding this issue? Can we close this ticket?\'"", ""Comment 16: \'This ticket can be closed.\']""]\nRelated Issues:\n[\'DAP-13423\']\n\n### End'}"
294,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8738\n\n### Instruction:\nThis change has dependancies with Intense - WebMethods and Milas. \r\n\r\nPlease see and read the full requirement as enclosed.\r\n\r\nKr.\r\nRichard Rodrigus  \n\n### Response:\n[""Comment 1: [\'[^Requirements document Saldo to Pay_RFC_170223.docx] _(166 kB)_\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Hi Richard,When should these changes be implemented?Regards,Tomasz\'"", ""Comment 4: \'Latest version of requirement[^Requirements document Saldo to Pay_RFC_170223-1.docx]\']""]\nRelated Issues:\n[]\n\n### End'}"
295,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8737\n\n### Instruction:\nWe notice consumption of Pallets (Carrier Units) by VT dispatch, but some units exchange pallets, the truck comes with pallet and load item with pallet, so we don\'t remove from stock. Is it possible configure system to consider the pallet weight durint VT intake and dispatch but not make intake/ consumption?\r\n\r\nThank you\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Dear Priscyla,According to the service agreement this task should be categorized as a service request.Kindly approve change of the type of this task.Regards\'"", ""Comment 4: \'Hi [~psilva@deheus.com]we have a configuration on DHC level !CU in DHC! * Is carrier (true = will be shown on CarrierUnits window)* Is deposit (true = stock handling)* It is not possible to set up the same item in different way for intake and in different way for dispatch** you can set up isCarrier + isDeposit** you can set up isCarrier  !CU! \'"", ""Comment 5: \'Hi [~marcin.kleszcz@kotrak.com]we added only config carrier unit for PLGNAT17L but system is making consumption by VT dispatch"", ""Comment 6: so is it some error?!image!!image-1!\'"", \'Comment 7: ""SELECT IsCarrierUnit\', \'Comment 8: IsDeposit\', \'Comment 9: * FROM [Evolution_DHCountry].[dbo].[Items] where isdeposit = 0 and IsCarrierUnit = 1 and itemtype = 3 and AnimalGroupId = \\\'6B05B141-BB0F-4E2F-B26A-4E6274EF7540\\\'""\', ""Comment 10: \'Dear Priscyla,Under db I can see 18 pallets configured as carrier unit. Could you please confirm all examples that are configured carrier units and cause the issue?Regards\'"", ""Comment 11: \'{code:java}CodePLGNAT22QPLGNAT20IPLT-PRBPAL-MADPLGNAT19NPLGNAT19SPALETEX-0012PLGNAT17LPLGNAT19PPLGNAT19OPLGNAT17Y1140PLT-EUC7PLGNAT17ZPLT-EUCPLGNAT17XPLT-DESPLT-RIPADO{code}\'"", ""Comment 12: \'PLT-PRB!image-2!\'"", ""Comment 13: \'Hej [~aleksandra.przybylek@kotrak.com]"", ""Comment 14: [~marcin.kleszcz@kotrak.com]W razie takich pytań proszę przypisywać taska do mnie. Bo widzę że już zaczyna twierdzić że to jest błąd natomiast ta funkcjonalność nigdy tak na prawdę nie działała. Biorę ten temat na siebie\'"", ""Comment 15: \'[~maciej.dobrzanski@kotrak.com]<3\'"", \'Comment 16: \\\'Hi [~psilva@deheus.com]""we added only config carrier unit for PLGNAT17L but system is making consumption by VT dispatch\', \'Comment 17: so is it some error?""* for PLGNAT17L only isCarrier flag is set up* this item was added as separate WO(PI) element? I guess it was done in this way\', \'Comment 18: because you have a stock in the system* if you have the stock for this pallet in the system\', \'Comment 19: system will reduce stock during WO(PD) when you are choosing Pallet (isCarrier only) on Carrier unit window => it works in this way currently\', \'Comment 20: no additional configuration (PLR\', \'Comment 21: VT etc.)* proposal - if you need to keep stock for PLGNAT17L for PLR consumption\', ""Comment 22: I think you should use different pallet (but with the same weight) on WO(PD) process.\'"", ""Comment 23: \'Hi,Is there anything else we can do for you?Regards\'"", ""Comment 24: \'Hi Aleksandra,you can close this task. Thank you.\'"", ""Comment 25: \'Thank you.Regards\']""]\nRelated Issues:\n[]\n\n### End'}"
296,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8736\n\n### Instruction:\nwe are unable to edit/send Replacement Prices. \r\n\r\nbehavior)\r\n   at Dapper.SqlMapper.ExecuteReaderWithFlagsFallback(IDbCommand cmd, Boolean wasClosed, CommandBehavior behavior)\r\n   at Dapper.SqlMapper.<QueryImpl>d__136`1.MoveNext()\r\n   at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection)\r\n   at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source)\r\n   at Dapper.SqlMapper.Query[T](IDbConnection cnn, String sql, Object param, IDbTransaction transaction, Boolean buffered, Nullable`1 commandTimeout, Nullable`1 commandType)\r\n   at Kotrak.XLInterface.RMPrices.ERPXL2016.Queries.PriceForecastsQuery.GetPriceForecasts() in E:\\BambooHome\\xml-data\\build-dir\\152764417\\DHGUI-DHCDN1041-JOB1\\DHCDN.RMPrices\\Kotrak.XLInterface.RMPrices.ERPXL2016\\Queries\\PriceForecastsQuery.cs:line 37\r\n   at Kotrak.XLInterface.RMPrices.Presentation.Forms.ItemNonHistoricalPriceForecastsListModule.FillWithLastConfirmed(PriceForecast[] forecasts, Week week, IEntityId priceTypeId, IEntityId purchaserId) in E:\\BambooHome\\xml-data\\build-dir\\152764417\\DHGUI-DHCDN1041-JOB1\\DHCDN.RMPrices\\Kotrak.XLInterface.RMPrices.Presentation\\Forms\\ItemNonHistoricalPriceForecastsListModule.cs:line 683\r\n   at Kotrak.XLInterface.RMPrices.Presentation.Forms.ItemNonHistoricalPriceForecastsListModule.CreateAndSetupEditPricesView(IEnumerable`1 priceForecasts, SavePriceForecastMode savePriceForecastMode, Boolean forceDirectEdit) in E:\\BambooHome\\xml-data\\build-dir\\152764417\\DHGUI-DHCDN1041-JOB1\\DHCDN.RMPrices\\Kotrak.XLInterface.RMPrices.Presentation\\Forms\\ItemNonHistoricalPriceForecastsListModule.cs:line 658\r\n   at Kotrak.XLInterface.RMPrices.Presentation.Forms.ItemNonHistoricalPriceForecastsListModule.EditPrices(IEnumerable`1 priceForecasts) in E:\\BambooHome\\xml-data\\build-dir\\152764417\\DHGUI-DHCDN1041-JOB1\\DHCDN.RMPrices\\Kotrak.XLInterface.RMPrices.Presentation\\Forms\\ItemNonHistoricalPriceForecastsListModule.cs:line 544\r\n   at Kotrak.XLInterface.RMPrices.Presentation.Commands.BarItemUICommand`1.OnExecute() in E:\\BambooHome\\xml-data\\build-dir\\152764417\\DHGUI-DHCDN1041-JOB1\\DHCDN.RMPrices\\Kotrak.XLInterface.RMPrices.Presentation\\Commands\\BarItemUICommand.cs:line 45\r\n   at Kotrak.XLInterface.RMPrices.Presentation.Commands.UserInterfaceCommandBase.Execute() in E:\\BambooHome\\xml-data\\build-dir\\152764417\\DHGUI-DHCDN1041-JOB1\\DHCDN.RMPrices\\Kotrak.XLInterface.RMPrices.Presentation\\Commands\\UserInterfaceCommandBase.cs:line 22\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello"", ""Comment 3: We kindly inform you that wecurrentlyare processing another Priority1 task.We will revert to processing your task as soon as possible.Regards\'"", ""Comment 4: \'We have recreated lacking database object. Please check if that solved Your issue.\'"", ""Comment 5: \'Hello"", ""Comment 6: issue has been resolved thank you \'"", ""Comment 7: \'do wyzerowania\']""]\nRelated Issues:\n[]\n\n### End'}"
297,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8735\n\n### Instruction:\nFor sales order SO000080192 for Helmond, one time recipes for were missing in the PCS. \r\nThe order contains 6 lines of which 5 lines have one or more specials. \r\nFor item 303302, the one time recipes are sent to DHP / PCS.\r\nFor 303306 and 303436, the one time recipes are missing.\r\n\r\nOn the order in DHC, the version and subversion of the one time recipes is shown. In production recipes I cannot find these version/subversion combinations.\r\n\r\nCan you check \r\n- why these production recipes are not generated / sent? \r\n- if it happened for other recipes as well\r\n- how to prevent this from happening\r\n\r\nWithout the one time recipes, plants will produce incorrect feed (as was the case for this order)\r\n\r\nAttached images:\r\nSales order\r\nCorrect production recipes for 303302\r\nMissing production recipes for 303306\r\n\n\n### Response:\n[""Comment 1: [\'!image!!image-1!!image-2!\'"", ""Comment 2: \'Hi all"", \'Comment 3: On behalf of Gert Jan Schipper\', \'Comment 4: our Operational Director\', ""Comment 5: I want to upgrade this to a Prio1. At this moment they have too many doubts in Helmond to produce feed with additions.\'"", ""Comment 6: \'Hello,\\\\r\\\\rWe are investigating your issue. We will inform you about the solution as soon as possible.\\\\r\\\\rRegards\\\\r\\\\r\'"", ""Comment 7: \'!image-2023-03-10-14-25-16-219.png!\'"", \'Comment 8: ""Hello from what I checked the reason of that situation seem to be similar to the the reason of problem in this taskhttps://helpdesk.kotrak.com/browse/DGS-8609We found that there is problem with recipes and items :We analyzed the problem and it appears that for some VT items is assigned from pcs recipe to another item. Therefore\', ""Comment 9: the system does not retrieve information to the label in the case of order SO000068853 was assigned a recipe for the item 303641 and SO and VT refer to the item with the code 303436\'"", \'Comment 10: we can see that for 303436 such Vt is more. For the order of the item VT 695 we changed the recipe to the last one for the commodity 303436 and on the printout you can see the data about the label( attached xml). In this situation\', \'Comment 11: on the remaining reported in this and related shuffle\', \'Comment 12: do we change it recipe to VT? I also ask for verification on the pcs side\', \'Comment 13: as it is pcs that sends the information in RECIPE( last comment)In that case again we have a recipe related to that order but it is linked to other items :|itemid|itemonrecipe|CustomerItemCode|idonorder|No||75C01D04-F6F5-4BF5-B02D-2D56E4DE8A51|303631|303306|FFD01DC5-54F6-42AA-B3AF-E7D438F6F8D8|5||B5D79E83-9CDC-4771-A0DD-09462FD77F7C|303641|303436|08B78E4E-277B-4282-8154-FB338C827580|7||75C01D04-F6F5-4BF5-B02D-2D56E4DE8A51|303631|303306|FFD01DC5-54F6-42AA-B3AF-E7D438F6F8D8|14|We need to verify it.Could you bring information from PCS ( as I asked in previous task).""\', ""Comment 14: \'Could also provide a information where in what action"", \'Comment 15: object in dhp you are missing this items.Also from the screenshoot you added it is not looking like a one time recipes ( it has higher version then 0)Also\', \'Comment 16: It look like it is a bigger issue that need complex analysis\', ""Comment 17: are you have current production with and this iscritical or a blocking impact on business processes?If not we suggest decreasing the issue priority.Regards\'"", ""Comment 18: \'Hi Agnieszka"", \'Comment 19: we sure have blocking business processes as in plant Helmond the wrong feed are being produced. I have asked Bob to respons to you\', ""Comment 20: as he is more aware of this issue\'"", \'Comment 21: ""select * from DHPlantPCSBusinessLogicMain.dbo.OrderElements where id=\\\'133C691B-F955-4BB8-99BA-B3088F639B47\\\' and CustomerItemCode in (\\\'303306\\\',\\\'303436\\\',\\\'303631\\\')select *FROM DHPlantPCSBusinessLogicMain.dbo.Recipes where orderid=\\\'133C691B-F955-4BB8-99BA-B3088F639B47\\\' and OrderElementNo in (5,7,14)""\', ""Comment 22: \'I expect the one time recipes in:- DHC production recipes- DHP recipes- recipe message for PCSWith one time recipe I mean a recipe that is generated for an orderline with special. These recipes have regular version + subversion (numbers are shown also in order screen"", \'Comment 23: see screenprint).The screenshot 303302 shows the one time recipe in DHC. These ones are also sent to DHP and PCSThe screenshot 303306 shows only regular recipe versions (no values in column subversion). So\', \'Comment 24: the version that is shown in the order overview is missing. It is also missing in DHP recipes and not sent to PCS...The link with VT and PCS information I do not yet understand.As Theo responded\', \'Comment 25: generation and delivering one time recipes is really important for PCS. Without these recipes\', ""Comment 26: incorrect feed is produced.\'"", ""Comment 27: \'DHP recipes screenprints: 303302: expected one time recipes are present303306"", ""Comment 28: 303436: one time recipes are missing!image-3!!image-4!!image-5!\'"", ""Comment 29: \'Could you give me access to https://helpdesk.kotrak.com/browse/DGS-8609.\'"", ""Comment 30: \'For the comment about PCS response and VT: Just to be sure: this ticket is about the information that is sent to the PCS. In this case: the order + one time recipes.\'"", ""Comment 31: \'Please check if You have access toDGS-8609\'"", ""Comment 32: \'Thank you"", ""Comment 33: I now have access to DGS-8609\'"", ""Comment 34: \'technologies for 303306 and 303436 were created as product definitions.!image-2023-03-10-17-26-46-550.png!!image-2023-03-10-17-28-43-634.png!That means they are visible in PCSappropriately,for 303306 as 303631 and for 303436 as 303641.Please check.\'"", ""Comment 35: \'Przemek explained me why the one time recipes for the items in the order are missing: these are derived items (there are additional technologies defined with indication Product definition)"", ""Comment 36: so the one time recipe will be on the item to produce and not on the item ordered.I will now check if the one time recipes for the items to produce were delivered correctly t PCS\'"", ""Comment 37: \'Ok,please"", ""Comment 38: let me know if you expect any additional actions from us regarding this issue?\'"", ""Comment 39: \'On DHC/DHP side"", ""Comment 40: all seems to work correct. This task can be closed.\'"", ""Comment 41: \'[[PCS] Kiedy receptura wpada do PCS|onenote:https://kotrak.sharepoint.com/sites/erpasysta/Shared%20Documents/Baza%20wiedzy/Baza%20Wiedzy%20-%20ERPSD/Klienci/DEHEUS/DEHEUS%20APPLICATIONS/Holandia%20Premix%20i%20AS400/Baz%20wiedzy%20z%20AS400.one#%5bPCS%5d%20Kiedy%20receptura%20wpada%20do%20PCS&section-id=\\\\\\\\{9BB564BA-0B58-4580-B9E0-F3CF9D6D80A7}&page-id=\\\\\\\\{2C9B1A12-E95C-462F-BC73-662427EB18A0}&end] ([Widok sieci Web|https://kotrak.sharepoint.com/sites/erpasysta/_layouts/OneNote.aspx?id=%2Fsites%2Ferpasysta%2FShared%20Documents%2FBaza%20wiedzy%2FBaza%20Wiedzy%20-%20ERPSD&wd=target%28Klienci%2FDEHEUS%2FDEHEUS%20APPLICATIONS%2FHolandia%20Premix%20i%20AS400%2FBaz%20wiedzy%20z%20AS400.one%7C9BB564BA-0B58-4580-B9E0-F3CF9D6D80A7%2F%5BPCS%5D%20Kiedy%20receptura%20wpada%20do%20PCS%7C2C9B1A12-E95C-462F-BC73-662427EB18A0%2F%29])\']""]\nRelated Issues:\n[]\n\n### End'}"
298,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8734\n\n### Instruction:\nVT 230/3/23  has status closed but the WO\'s attached to it have opposing statuses which is cause an issue with stock availability. \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: \'[[DHP 3.0]Incorrect WO status|onenote:https://kotrak.sharepoint.com/sites/erpasysta/Shared%20Documents/Baza%20wiedzy/Baza%20Wiedzy%20-%20ERPSD/Klienci/DEHEUS/DEHEUS%20APPLICATIONS/RPA/Baza%20wiedzy.one#%5bDHP%203.0%5dIncorrect%20WO%20status&section-id=\\\\\\\\{A2F09CD6-A23A-42F3-92F5-ED66B521455B}&page-id=\\\\\\\\{325B9921-0AB5-4E36-A871-095DF356E2F1}&end] ([Widok sieci Web|https://kotrak.sharepoint.com/sites/erpasysta/_layouts/OneNote.aspx?id=%2Fsites%2Ferpasysta%2FShared%20Documents%2FBaza%20wiedzy%2FBaza%20Wiedzy%20-%20ERPSD&wd=target%28Klienci%2FDEHEUS%2FDEHEUS%20APPLICATIONS%2FRPA%2FBaza%20wiedzy.one%7CA2F09CD6-A23A-42F3-92F5-ED66B521455B%2F%5BDHP%203.0%5DIncorrect%20WO%20status%7C325B9921-0AB5-4E36-A871-095DF356E2F1%2F%29])\'"", ""Comment 4: \'puszczenia rabbita nie pomoglo\'"", \'Comment 5: "" Select w.id,w.CreatedDate,w.DocumentNumber,w.Document\', \'Comment 6: w.SourceDocumentId,w.SourceDocumentNumber,*  Select w.id,w.CreatedDate,w.DocumentNumber,w.Document\', \'Comment 7: w.SourceDocumentId,w.SourceDocumentNumber,*  FROM [DHPlantWmsBusinessLogicMain].[dbo].[WarehouseOrders] w left join dbo.WarehouseOrderElements we on we.id=w.Id where w.SourceDocumentNumber in (\\\'VT-230/3/23\\\') select top 100 * from VehicleTickets where DocumentNumber =230 and DocumentMonth=3 select top 10 * from [DHPlantWmsBusinessLogicMain].[dbo].[WarehouseOrders] w whereDocumentMonth= 3 and DocumentYear=2023 and DocumentNumber in (14,15)""\', \'Comment 8: ""oba elementy so na wo znowu in progress widac ze 13.03 ponownie owierali dokumentSELECT TOP (1000) [Id]* FROM [DHPlantWmsBusinessLogicEvents].[dbo].[WarehouseOrders] where AggregateId =\\\'33C1846E-54C1-4140-9293-0C2A55EDE573\\\'!image-2023-03-14-11-08-49-004.png!""\', ""Comment 9: \'Morning"", \'Comment 10: Currently both elements of the order are on in progress \', \'Comment 11: from what I checked on 13.03 about 5.19 am someone reopened also WOPI 15. The operation is assigned to ""WeighbridgeOperator"" in this situation do you set on this elements of this WOPI the status ending or will you still operate on this document?\\\'\', ""Comment 12: \'Hello"", ""Comment 13: the VT was closed on the 09/03/2023 user should not have been able to reopen the WO.  WO status for both elements should be executed\'"", ""Comment 14: \'status was fixed please verify :!image-2023-03-14-14-01-37-981.png!\'"", ""Comment 15: \'status is updated thank you. \']""]\nRelated Issues:\n[]\n\n### End'}"
299,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8733\n\n### Instruction:\nPlease remove additional tech SN506771 from DHC.\r\n\r\nKind regards,\r\nRob.\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'!image-2023-03-10-11-37-06-919.png!\'"", ""Comment 3: \'Hi Rob,Could you please let us know if you want to remove technology because it was created by mistake or there is a header / element on recipe that should be corrected.Regards\'"", \'Comment 4: ""The user is not very responsive. Let\\\'s assume they made it by mistake or got different ideas how to treat the item.""\', ""Comment 5: \'user feedback: the additional tech is not needed anymore.\'"", ""Comment 6: \'Sure"", ""Comment 7: thank you\'"", ""Comment 8: \'Hi Rob,Technology has been removed. Please verify.Regards\'"", ""Comment 9: \'I can still see it in DHC :(\'"", \'Comment 10: ""Yes\', \'Comment 11: it will be visible. Since taskDGS-8666\', \'Comment 12: Thomas and Theo together with our dev agreed that it should not be delete totally but only stopped from sending to PCS provider and it won\\\'t be treated as product definition.Regards""\', ""Comment 13: \'Ah"", \'Comment 14: I see... in that case thank you\', ""Comment 15: the ticket can be closed.Regards,Rob.\'"", ""Comment 16: \'Thank you.Regards\']""]\nRelated Issues:\n[]\n\n### End'}"
300,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8732\n\n### Instruction:\n\xa0\r\n\r\n\xa0\r\n\r\n\xa0\r\n\r\nTo adjust calculations for technical results and FS printout.\r\n\r\nFS-M/0682 (ID 104706) - IBIP_DH\r\n\r\nFinancial statement document and FS new printout have different values for \'Average weight in gram\' (technical results) and \'Gewicht (kg)\' on FS printout\r\n\r\n!image-2023-03-10-10-05-17-666.png!\r\n\r\nOn SR there is different value \'Average wieght in kg\' than on FS document and FS printout\r\n !image-2023-03-10-10-07-28-811.png!\r\n\r\n\xa0\r\n\r\nValues for FS new printout are retrieved from invoices\r\n !image-2023-03-10-10-09-20-432.png!\r\n\r\n\xa0\n\n### Response:\n[\'Comment 1: [""[~mbovene@deheus.com]please confirm how it should be adjusted in system. * _Technical results on Financial statement document_ - field\\\'Average weight in gram\\\' is calculated:AverageWeight = (KgOfBroilersAL - WeightBridgeCorrectionAL + KgOfBroilersFL- WeightBridgeCorrectionFL)/(NumberOfBroilersFL,+ NumberOfBroilersAL)|AverageWeight|KgOfBroilersAL|WeightBridgeCorrectionAL|KgOfBroilersFL|NumberOfBroilersFL|NumberOfBroilersFL|NumberOfBroilersAL||2281|42709.00|431.0000|0.00|0.00|0.00|18537.0000|*To change:* KgOfBroilersAL and KgOfBroilersFL should be value from \\\'Gross weight\\\' from Slaugtery Report documents instead of \\\'Net Weight\\\' * _Financial statement new printout_ - values in column \\\'Gewitcht\\\' is calculated from invoices (there is retrieved data from \\\'SLAC\\\' and \\\'VOER\\\') !image-2023-03-10-11-27-57-990.png!*To change:*Gewicht should be calculated as a sum of items \\\'SLAC\\\'\', \'Comment 2: \\\'VOER\\\' and also \\\'WGCO\\\'. * To confirm how should be treated value from Slaughtery Report \\\'Food discount in kg\\\'. ** Is this value included somewhere in invoices? (FS printout is based on invoices) ** Is this value should be included in technical results calculations: should be retrieved also in this calculationcurrent calcualtions:AverageWeight = (KgOfBroilersAL - WeightBridgeCorrectionAL + KgOfBroilersFL- WeightBridgeCorrectionFL)/(NumberOfBroilersFL,+ NumberOfBroilersAL)*To change:*AverageWeight = (KgOfBroilersAL - WeightBridgeCorrectionAL *- Food discount in kg AL*+ KgOfBroilersFL- WeightBridgeCorrectionFL *- Food discount in kg FL*)/(NumberOfBroilersFL,+ NumberOfBroilersAL)!image-2023-03-10-11-33-59-601.png!""\', \'Comment 3: ""[~mbovene@deheus.com],we\\\'ve made changes in prinouts and technical results SQL procedures in test Intense environment (MAS NL & MAS BE). You can feel free to test it.Best regards\', \'Comment 4: Grzegorz""\', ""Comment 5: \'Zmiana w procedurach:KR_Printout_FS2_Slaughtery,KR_Printout_FS2_Slaughtery_MAS_BE,KR_calculatetechresults,KR_calculatetechresults_MASBE.Opisane nazwą taska.\'"", \'Comment 6: \\\'I have added two SR\\\\\\\'s and calculated the technical results twice.The green squares are correct. The red ones are not correct.For the ""Aantal"" you should only look at the SLAC. The quantity should be 100.000 and not 100.001.As well the ""gewicht (kg)"" is slightly different with 2,463 after my second test than the 2,462 on the line. Could you explain the difference to me?The average weight of all loaders in Intense on the technical results is also wrong. The Food discount and Weight bridge deviation are not in this figure yet. !image!\\\'\', ""Comment 7: \'Hi [~mbovene@deheus.com],we made changes"", \'Comment 8: because in the first requirements\', ""Comment 9: we looked only for SLAC. Currently we are looking for \\\\\'SLAC\\\\\'"", \'Comment 10: \\\\\\\'VOER\\\\\\\' and \\\\\\\'WGCO\\\\\\\' for quantity - ""Aantal"":!image-2023-03-15-08-47-25-435.png!So the value of ""Aantal"" 100 001,00 is correctly.The ""Gem. gewitch"" value on the prinout is from field ""Average weight in gram"" from Technical results:!image-2023-03-15-08-53-21-449.png!We made changes for this field in TR calculationyesterday as on the screen below:!image-2023-03-15-08-54-21-830.png!As I understand you\', \'Comment 11: also we need to change ""Average weight FL"" and ""Average weight AL"".The current calculation for these two fields is as follow:_Average weight FL: GrossWeightFL - WeightBridgeCorrectionFL/UnitsDeliveredFL__Average weight AL: GrossWeightAL - WeightBridgeCorrectionAL/UnitsDeliveredAL_*To change*:_Average weight FL: GrossWeightFL - WeightBridgeCorrectionFL - *FoodDiscountInKgAL*/UnitsDeliveredFL__Average weight AL: GrossWeightAL - WeightBridgeCorrectionAL - *FoodDiscountInKgAL*/UnitsDeliveredAL_I\\\\\\\'m waiting for your reply.Best regards,Grzegorz\\\'\', ""Comment 12: \'You are completely right. You can make the changes as you propose.In addition: yesterday we came to the conclusion that we do not take the disapproves into account at the moment in the kg. This is new information for you. This means that the actual kg are a bit too high in the current calculations. To adjust this it must be something like:Average weight FL: (GrossWeightFL-AFKK-AFKO) - WeightBridgeCorrectionFL - FoodDiscountInKgAL/UnitsDeliveredFLAverage weight AL: (GrossWeightAL-AFKK-AFKO) - WeightBridgeCorrectionAL/UnitsDeliveredAL\'"", ""Comment 13: \'Ok"", \'Comment 14: good. Right now\', \'Comment 15: we take the GrossWeight valuefrom Slaughtery report to calculation Technical Results:!image-2023-03-15-11-03-47-862.png!So\', \'Comment 16: where do we collect the values of ""AFKK"" and ""AFKO""?\\\'\', \'Comment 17: ""It would be best if you can base it on the PI\\\'s with these codes (see the attachment). Is that possible?Please note that these weights already have a minus in front of them. So it this will be the approach than we should do it like:Average weight FL: (GrossWeightFL+AFKK+AFKO) - WeightBridgeCorrectionFL - FoodDiscountInKgAL/UnitsDeliveredFLAverage weight AL: (GrossWeightAL+AFKK+AFKO) - WeightBridgeCorrectionAL/UnitsDeliveredAL!image-1!""\', \'Comment 18: ""Ok\', \'Comment 19: If I correctly undestand\', \'Comment 20: we need to collect all elements from PI\\\'s with Item Code = \\\'AFKK\\\' / \\\'AFKO\\\' related to SR.I\\\'m working on it.""\', ""Comment 21: \'Yes indeed.\'"", ""Comment 22: \'[~mbovene@deheus.com],Could you look at the calculation again? I have some concerns. In the Financial Statement we had three Average weight: 1. Average weight first loaders"", \'Comment 23: with calculation: _(GrossWeightFL - WeightBridgeCorrectionFL)/UnitsDeliveredFL_ 2. Average weight all loaders\', \'Comment 24: with calculation: _(GrossWeightAL- WeightBridgeCorrectionAL)/UnitsDeliveredAL_ 3. Average weight in gram\', \'Comment 25: with calculation: _(KgOfBroilersAL-WeightBridgeCorrectionAL)+(KgOfBroilersFL-WeightBridgeCorrectionFL)/(NumberOfBroilersF+NumberOfBroilersAL)*1000_After modification\', \'Comment 26: we have: 1. Average weight first loaders\', \'Comment 27: with calculation: _((GrossWeightFL+*(AFKK+AFKO)*) - WeightBridgeCorrectionFL)-*FoodDiscountInKgFL*/UnitsDeliveredFL_ 2. Average weight all loaders\', \'Comment 28: with calculation: _((GrossWeightAL+*(AFKK+AFKO)*) - WeightBridgeCorrectionAL)/UnitsDeliveredAL_ 3. Average weight in gram\', \'Comment 29: with calculation: _(KgOfBroilersAL-WeightBridgeCorrectionAL-*FoodDiscountInKgAL*)+(KgOfBroilersFL-WeightBridgeCorrectionFL-*FoodDiscountInKgFL*)/(NumberOfBroilersF+NumberOfBroilersAL)*1000_ When I recalculated Technical Results\', \'Comment 30: the ""Average weight for first loaders"" have strange value.Best regards\', ""Comment 31: Grzegorz\'"", ""Comment 32: \'I think you are almost there. Some math brackets were not correct and you are missing the AFKK+AFKO in the total average weight in gram (please make sure that you do not extract (it are negative numbers) AFKK and AFKO twive"", \'Comment 33: this must be distinquished between FL and AL as well:1. Average weight first loaders\', \'Comment 34: with calculation:((GrossWeightFL+AFKK+AFKO)) - WeightBridgeCorrectionFL -FoodDiscountInKgFL)/UnitsDeliveredFL2. Average weight all loaders\', \'Comment 35: with calculation:((GrossWeightAL+AFKK+AFKO)) - WeightBridgeCorrectionAL -FoodDiscountInKgAL)/UnitsDeliveredAL3. Average weight in gram\', ""Comment 36: with calculation:(KgOfBroilersAL-WeightBridgeCorrectionAL-FoodDiscountInKgAL+AFKK+AFKO)+(KgOfBroilersFL-WeightBridgeCorrectionFL-FoodDiscountInKgFL+AFKK+AFKO)/ (NumberOfBroilersFL+NumberOfBroilersAL)*1000Normally the average weight should be between 2 and 2,5kg.\'"", ""Comment 37: \'[~mbovene@deheus.com],the calculation for technical results has been changed. You can feel free to verify it in test Intense environment.Best regards,Grzegorz\'"", \'Comment 38: \\\'Please see ID 79857:How can the Gewicht (kg) be 2,463 while the average from the table ""Aflevergegevens slachterij"" is 2,462. They should always be the same.Still the Aantal is 100.001 that should be 100.000..\\\'\', ""Comment 39: \'See ID 79866. The AFKK is not in the calculation yet....Average in this case should be (200.000 - 10.000)/100.000.Please fix this.\'"", \'Comment 40: ""[~mbovene@deheus.com],ok\', \'Comment 41: I\\\'ve made modificaiton. You can verify it one more time.Best regards,Grzegorz""\', ""Comment 42: \'I sitll see 2.000 as Average weight in gram and not 1.900.\'"", ""Comment 43: \'[~mbovene@deheus.com]the calculation model is look like:_(KgOfBroilersAL-WeightBridgeCorrectionAL-*FoodDiscountInKgAL*)+(KgOfBroilersFL-WeightBridgeCorrectionFL-*FoodDiscountInKgFL*)/(NumberOfBroilersF+NumberOfBroilersAL)*1000_the values in MS SQL by parameter:!image-2023-03-16-14-01-52-244.png!Best regards,Grzegorz\'"", \'Comment 44: ""You still don\\\'t take AFKK and AFKO into account. Please take a good look at the previous posts in this task.Mitch van Bovene2 uur geledenSee ID 79866. The AFKK is not in the calculation yet....Average in this case should be (200.000 - 10.000)/100.000.Please fix this.-----------Mitch van BoveneGisteren 15:39I think you are almost there. Some math brackets were not correct and you are missing the AFKK+AFKO in the total average weight in gram (please make sure that you do not extract (it are negative numbers) AFKK and AFKO twive\', \'Comment 45: this must be distinquished between FL and AL as well:1. Average weight first loaders\', \'Comment 46: with calculation:((GrossWeightFL+AFKK+AFKO)) - WeightBridgeCorrectionFL -FoodDiscountInKgFL)/UnitsDeliveredFL2. Average weight all loaders\', \'Comment 47: with calculation:((GrossWeightAL+AFKK+AFKO)) - WeightBridgeCorrectionAL -FoodDiscountInKgAL)/UnitsDeliveredAL3. Average weight in gram\', \'Comment 48: with calculation:(KgOfBroilersAL-WeightBridgeCorrectionAL-FoodDiscountInKgAL+AFKK+AFKO)+(KgOfBroilersFL-WeightBridgeCorrectionFL-FoodDiscountInKgFL+AFKK+AFKO)/ (NumberOfBroilersFL+NumberOfBroilersAL)*1000----------------------------------Grzegorz MaterlaGrzegorz MaterlaGisteren 11:37Ok\', \'Comment 49: If I correctly undestand\', \'Comment 50: we need to collect all elements from PI\\\'s with Item Code = \\\'AFKK\\\' / \\\'AFKO\\\' related to SR.I\\\'m working on it.""\', ""Comment 51: \'Yes"", \'Comment 52: you have right\', ""Comment 53: I was focused on Average weight FL and AL. The AFKK+AFKO parameter has been added to Average weight in gram and looks good.Changes made on both sector MAS NL and MAS BE.Best regards,Grzegorz\'"", ""Comment 54: \'Hi"", \'Comment 55:  The average weight is correct now “Gewicht (kg)” with 1,900.  However on the line on the FS 2 I still see gem. Gew. 2,000 on the line.  I will say it again: these numbers must match.  Regards\', \'Comment 56:  Mitch       *From:* Grzegorz Materla (Jira) <jira@kotrak.com>   *Sent:* donderdag 16 maart 2023 14:56  *To:* Bovene\', ""Comment 57: Mitch van <mbovene@deheus.com>  *Subject:* DGS-8732 Adjusting calculations and Financial statement (technical results) and FS printout   \'"", ""Comment 58: \'Hi [~mbovene@deheus.com],on the printout in Slaughtery section"", ""Comment 59: the calculation of Gem.gew. is[KgSLACSUM]/[QuantitySLACSUM] (Gewicht/Aantal).Exactly with numbers: 200 000/100 000 = 2.000:!image-2023-03-17-09-28-20-686.png!So how to calculate this in the Slaughtery area? Data which we calculate Technical Results is different than on printout.Best regards,Grzegorz\'"", \'Comment 60: \\\'The ""Kg afkeur"" needs to be distracted.So  (200 000 - 10 000)/100 000 = 1.900.\\\'\', ""Comment 61: \'We changed the calculation on printout. You can verify it.Best regards,Grzegorz\'"", ""Comment 62: \'Ok"", ""Comment 63: you can move this to PROD.\'"", ""Comment 64: \'[~mbovene@deheus.com],the printouts FS2 new and calculations of Technical Results for MAS NL and MAS BE have been moved into PROD Intense environment.Best regards"", ""Comment 65: Grzegorz\'"", ""Comment 66: \'Feed profit calculation adjustments with guarantees[^FW_ Foutieve berekening voerwinst.eml]\'"", ""Comment 67: \'Do kalkulacji Feed profit powinna być wliczana oryginalna wartość z faktur gwarancyjnych i powinno to wyglądać tak: (ABS(@AmountFL)+ABS(@AmountAL)) - ABS(@AmountOfFeed) -ABS(@AmountDOCNet) +*Suma faktur gwarancyjnych*\'"", ""Comment 68: \'Zrobione"", ""Comment 69: zgodnie zhttps://helpdesk.kotrak.com/browse/DGS-8641\'"", ""Comment 70: \'Do you expect something from us? I cannot open the attachment.\'"", ""Comment 71: \'{quote}Do you expect something from us? I cannot open the attachment.{quote}No"", \'Comment 72: it was only mail with some discussion about calculations of feed profit\', \'Comment 73: but it has been handled in this task\', ""Comment 74: https://helpdesk.kotrak.com/servicedesk/customer/portal/56/DGS-8641.Task is still open due to technical results changes and we can keep it open until we create new one or close linked tasks related to technical results.\'"", ""Comment 75: \'We need to change something on the new financial statement.On the old printout you can clearly see the unit price of 1.23. Hovewer on the new overview the unit prices are a bit lower. This is because the “Bedrag excl.” is divided by the “Kg afkeur””. However"", ""Comment 76: this amount also includes all disapproves (AFKK/Afkeur).The calculation of the prices must be the “Bedrag excl.” divided by the (“Gewicht”-“Kg afkeur” so that the unit price is € 1.23.!image-2!!image-3!\'"", \'Comment 77: ""I\\\'ve added this remarks to task with FS printout - [https://helpdesk.kotrak.com/servicedesk/customer/portal/56/DGS-8215]""\', ""Comment 78: \'Unfortunately"", \'Comment 79: the calculation for the average weight (""Gem. gew.) needs to be adjusted (again). No disapproves (AFKK) must be included in this.The calculation on the first line must be (69.200 / 35.411). Please make sure that also the calculation of the ""Gewicht (kg)"" in the technical results is changed. The AFKK needs to be excluded from this as well. !image-4!\\\'\', \'Comment 80: \\\'Another related change. In the column ""Kg afkeur"" we now see the kg\\\\\\\'s that are related to the AFKK (disapproves). Sometimes however De Heus compensates for this loss with the item code AFKH (disapproves for account of De Heus). In the column ""Kg afkeur"" we would like to see the weight related to (AFKK-AFKH). It is important that the AFKH always lowers the total weight for AFKK that the farmers needs to pay for.\\\'\', \'Comment 81: ""{quote} # Average weight first loaders\', \'Comment 82: with calculation:((GrossWeightFL+AFKK+AFKO)) - WeightBridgeCorrectionFL -FoodDiscountInKgFL)/UnitsDeliveredFL2. Average weight all loaders\', \'Comment 83: with calculation:((GrossWeightAL+AFKK+AFKO)) - WeightBridgeCorrectionAL -FoodDiscountInKgAL)/UnitsDeliveredAL3. Average weight in gram\', ""Comment 84: with calculation:(KgOfBroilersAL-WeightBridgeCorrectionAL-FoodDiscountInKgAL+AFKK+AFKO)+(KgOfBroilersFL-WeightBridgeCorrectionFL-FoodDiscountInKgFL+AFKK+AFKO)/ (NumberOfBroilersFL+NumberOfBroilersAL)*1000{quote}This calculations have been changed and AFKK are not included right now like below. It\'s done in MAS NL and MAS BE sectors on Test environment.Please veriy.1. Average weight first loaders"", \'Comment 85: with calculation:((GrossWeightFL{color:#de350b}-+AFKK-{color}+AFKO)) - WeightBridgeCorrectionFL -FoodDiscountInKgFL)/UnitsDeliveredFL2. Average weight all loaders\', \'Comment 86: with calculation:((GrossWeightAL{color:#de350b}-+AFKK-{color}+AFKO)) - WeightBridgeCorrectionAL -FoodDiscountInKgAL)/UnitsDeliveredAL3. Average weight in gram\', \'Comment 87: with calculation:(KgOfBroilersAL-WeightBridgeCorrectionAL-FoodDiscountInKgAL+AFKK+AFKO)+(KgOfBroilersFL-WeightBridgeCorrectionFL-FoodDiscountInKgFL{color:#de350b}-+AFKK-{color}+AFKO)/ (NumberOfBroilersFL+NumberOfBroilersAL)*1000""\', ""Comment 88: \'Zmodyfikowane wyliczanie w procedurach[dbo].[KR_calculatetechresults] i[dbo].[KR_calculatetechresults_MASBE] na bazie Testowej@WeightPISUMFL i @WeightPISUMAL!image-2023-04-07-13-23-41-722.png!\'"", \'Comment 89: ""After confirmation during today\\\'s call changes have been moved to production environmnent for MAS NL and MAS BE sectors.""\', ""Comment 90: \'can be closed\']""]\nRelated Issues:\n[\'DGS-8877\', \'DGS-8215\', \'DGS-8325\', \'DGS-8641\', \'DGS-8675\', \'DGS-8714\']\n\n### End'}"
301,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8731\n\n### Instruction:\nHi\r\nPlease help to check VT-6546/23 in Bien Hoa Plant. \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: \'HiPlease ignore this ticket .  Tks you.\']""]\nRelated Issues:\n[]\n\n### End'}"
302,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8730\n\n### Instruction:\nHi\r\nWe found a weird situation about a PrO that were integrated to PCS even with status Canceled.\r\n\r\nThis is the case of PrO *0891070323004*\r\nThis PrO were canceled but integrated. Looking with PCS supplier, no changes were done on PCS side.\r\nSo I decided to look through api.ProductionOrders and I found that the Status 3 (canceled) is present on the view. And Canceled PrO must not be imported to PCS.\r\n\r\nCould you please remove it from there? And all other plants?\r\n\r\nThank you very much!\n\n### Response:\n[""Comment 1: [\'!0891070323004_integration_evidence.jpg|thumbnail!!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Dear Maicon,I have consulted this case and application behaved correctly. Information that PrO is cancelled"", ""Comment 4: should be sent to PCS.Regards\'"", \'Comment 5: ""Hi AleksandraI\\\'m sorry. I didn\\\'t get it. Why a cancelled PrO Should be sent to PCS?It is cancelled\', \'Comment 6: no need to produce it. In the specific case we reported\', \'Comment 7: the PrO were never confirmed\', \'Comment 8: so never should be sent to PCS.Could you please enlighten me?Thank you""\', ""Comment 9: \'Hi Maicon,Sure.There is an option that allows to cancel PrO that are confirmed:!image-2023-03-10-13-53-39-766.png!We do not verify if cancelled PrO was canofirmed or not. That is why all events go to PCS. This is only a view.If you do not want to see cancelled PrO on the PCS list events"", ""Comment 10: a GDC task should be raised.Regards\'"", \'Comment 11: ""Hi AleksandraI still see this as a bug.Follow me: We have the configuration available: {{Sending unconfirmed PrO to PCS}}. *This one is unchecked*We also need thes {{ProdProductionOrderCancelConfirmed}} option to cancel confirmed PrO.But that is not the case of this DGS. The problem is that DHP configuration it\\\'s not working. DHP *IS indeed* sending unconfirmed PrO to PCS\', \'Comment 12: that is\', \'Comment 13: a mistake on DHP which is crashing cross configuration.Maybe [~wojciech.wojerz@kotrak.com] can help usThank you""\', ""Comment 14: \'I have asked Wojciech for his opinion. However"", ""Comment 15: initial case related to cancelled PrO that you can see in PCS view. And that was consulted :)\'"", \'Comment 16: \\\'[~mberbert@deheus.com],Even though you have unchecked the configuration entry ""Sending unconfirmed PrO to PCS"" are you able to see it in api.ProductionOrders in the PCS module?\\\'\', ""Comment 17: \'Hi [~maciej.dobrzanski@kotrak.com]In the case of reported PrO (0891070323004)"", \'Comment 18: yes! I can see it in api.ProductionOrders in the PCS module.I understand that once the PrO is confirmed\', \'Comment 19: it will be available in api.ProductionOrders\', \'Comment 20: even if it is cancelled later\', \'Comment 21: afterall it was confirmed before.However\', ""Comment 22: in the case of this 0891070323004 PrO was never confirmed as you can see in the attached screenshot of DHPlantPCSBusinessLogicEvents.dbo.ProductionOrdersThank you\'"", ""Comment 23: \'Z tego"", \'Comment 24: co mówił Wojtek to powinni mieć tą funkcję włączoną\', ""Comment 25: a nie mają. Przynajmniej dziś jak weszłam!image-2023-03-14-07-48-11-071.png!!image-2023-03-14-07-48-30-019.png!\'"", ""Comment 26: \'Requested PLR is in status Finished:!image-2023-03-14-08-09-43-570.png!Status 3 means finished"", ""Comment 27: cancelled for PLR is 5PrO is cancelled (status 3)!image-2023-03-14-08-30-03-498.png!Start Production był później niż cancel PrO!image-2023-03-14-08-36-17-056.png!!image-2023-03-14-08-33-20-007.png!\'"", ""Comment 28: \'!image-2023-03-14-10-25-18-805.png!!image-2023-03-14-10-26-15-302.png!!image-2023-03-14-10-28-17-687.png!\'"", ""Comment 29: \'Po PCSie eventy też poszły 7 marca!image-2023-03-14-13-55-02-272.png!!image-2023-03-14-13-58-13-389.png!\'"", ""Comment 30: \'Z tego"", \'Comment 31: co Wojtuś mówi\', \'Comment 32: to:_{color:#0747a6}bo pewnie event z cancelem założył PrO w module PCSa. PCS pobrał sobie to PrO\', \'Comment 33: nie patrząc\', \'Comment 34: że ma status canceled i zaraportował produkcję do niego.trzeba dodać zmianę polegającą na tym\', \'Comment 35: żeby to anulowanie PrO działało tak\', \'Comment 36: że jak nie ma PrO w module PCS to event nic nie robi (nie dodaje anulowanego PrO; powinien tylko aktualizować status PrO o ile to PrO w module PCS już było){color}_{color:#172b4d}do dalszej knsultacji\', ""Comment 37: czy będzie GDC{color}\'"", \'Comment 38: ""Po analizie widoku api.ProductioOrders: jest w nim warunek P.Status IN (2,3,4) OR (SELECT Value FROM dbo.Configuration WHERE [Key] = 4) = \\\'True\\\' \', \'Comment 39: który stwierdza\', \'Comment 40: że w widoku wystawiane są potwierdzone pro\', \'Comment 41: anulowane lub zmergowane albo wszystkie jeżeli konfiguracja na to pozwala.W ich przypadku założyli PrO\', \'Comment 42: trafiło ono do modułu PCS ale nie zostało wystawione w widoku. Po anulowaniu i zmianie statusu\', \'Comment 43: zgodnie z powyższym warunkiem zostało wystawione z flagą IsCancelled (flaga opisana w dokumentacji DHP3.0 - PCS_IntegrationCore. PCS zignorował tą flagę i utworzył na tej podstawie produkcję\', \'Comment 44: co jest błędem. Muszą walidować tą flagę po swojej stronie.""\', ""Comment 45: \'Hi [~mberbert@deheus.com],Mainly there are two conditions to display PrO in dbo.ProductionOrdersVIew# statuses: confirmed"", \'Comment 46: merged\', \'Comment 47: and canceled# in case configuration for all production orders is turned on then all PrO statuses are displayedIt looks like in this case that the production order was created and sent to PCS (and was not visible in View). Later on\', ""Comment 48: the production order was canceled and sent to PCS and available in the view with the flag IsCancelled=true (This flag is described in the documentation DHP3.0 - PCS_IntegrationCore). PCS ignored that flag and sent production.Our suggestion is to handle this flag in the PCS system in order to avoid such a situation in the future.If you want to change it somehow in the DHP please raise a GDC ticket for it.Regards\'"", \'Comment 49: ""Hi [~maciej.dobrzanski@kotrak.com]I still see this is a bug\', \'Comment 50: actually a conflict of integration rules.The reported PrO has never been confirmed. Even being cancelled the PrO still *unconfirmed*. So there is one rule being ignored.But OK! I\\\'ll ask for PCS supplier to change on their side.You can close this taskThank you""\', ""Comment 51: \'Hi Maicon,Thank you\']""]\nRelated Issues:\n[]\n\n### End'}"
303,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8729\n\n### Instruction:\nSome productions didn\'t integrated to DHC/ERP. We are missing productions:\r\nGLN2252-S30 0833070323006\r\nGLN2253-S30 0833070323007\r\nGLN2251-S15 0833070323008\r\n\r\nCould you check how many productions didn\'t integrated and fix integration?\r\nThank you\r\n\n\n### Response:\n[""Comment 1: [\'Hello,\\\\r\\\\rWe are investigating your issue. We will inform you about the solution as soon as possible.\\\\r\\\\rRegards\\\\r\\\\r\'"", ""Comment 2: \'I could not see that PRL in DHC"", \'Comment 3: I wanted to resend them from DHP but I cannot log to DHP and also server looks like it is not working\', \'Comment 4: could you please verify with your IT\', ""Comment 5: if there are any network.infrastructure problems.!image-2023-03-09-22-03-14-599.png!!image-2023-03-09-22-02-45-793.png!\'"", ""Comment 6: \'!image-2023-03-09-22-04-36-215.png!\'"", ""Comment 7: \'Hi AgnieszkaI now can see them on DHC.You can close this task.Thank you very much!!image!\']""]\nRelated Issues:\n[]\n\n### End'}"
304,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8728\n\n### Instruction:\nwe have problem in production integration of lot number 0882080323005 and 0882080323004. Any dosage integrated, I asked PCS help and they answered that any error was find in their side. Please check attached the file with PCS information.\r\n\r\nCould you check why we have this error?\r\n\r\nThank you\n\n### Response:\n[""Comment 1: [\'[^Cópia de 0882080323004 0882080323005.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: ""pcs lotid=0882080323005\', \'Comment 4: - 73129id =\\\'dbc429f4-8370-4606-823c-836af7871991\\\'""\', \'Comment 5: ""FROM [DHPlantPCSBusinessLogicMain].[dbo].[SqlApiRequestLog] where parameters like\\\'%73129%\\\'Production lot already exists. SELECT *FROM [DHPlantProdBusinessLogicIntercontext].[dbo].[Errors]where message like \\\'%DBC429F4-8370-4606-823C-836AF7871991%\\\'""\', ""Comment 6: \'!image-2023-03-10-10-35-10-822.png!\'"", \'Comment 7: ""brak stockunit na prodzie: select *FROM [DHPlantProdBusinessLogicMain].[dbo].[StockUnits] where id=\\\'09f525d4-e4aa-4811-a20e-4aa65483e2a7\\\'""\', \'Comment 8: ""Sytuacja wygglada tak że podany stock unit nie powstaje w module produkcja ponieważ wisi tam dla tego samego Barcode i Dostawy inny stock unit z inny datą i innym stockunitidFROM [DHPlantStockBusinessLogicMain].[dbo].[StockUnits] where id=\\\'09f525d4-e4aa-4811-a20e-4aa65483e2a7\\\'select *FROM [DHPlantProdBusinessLogicMain].[dbo].[StockUnits] where id=\\\'09f525d4-e4aa-4811-a20e-4aa65483e2a7\\\' or Barcode=\\\'88-W02781\\\'!image-2023-03-10-11-28-49-953.png!""\', ""Comment 9: \'!image-2023-03-10-11-30-27-253.png!\'"", ""Comment 10: \'!image-2023-03-10-11-37-05-230.png!\'"", ""Comment 11: \'Oba loty dotyczą tego samego stock unit :09f525d4-e4aa-4811-a20e-4aa65483e2a7.Powiązanie zhttps://helpdesk.kotrak.com/browse/DGS-8467\'"", ""Comment 12: \'HelloThe issue relates to recreated barcodes. Problematic barcodes are quite old"", ""Comment 13: befor the version 8.3 has been upgraded.It is already underanalysis in task dgs-8467.I will inform you if there be any news.\']""]\nRelated Issues:\n[\'DGS-8467\']\n\n### End'}"
305,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8727\n\n### Instruction:\nHi\r\n\r\nCould you please update GDC_2-3weeks for Rio Claro on test and later, after approval, on Prod server?\r\n\r\nThank you\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Dear [~mberbert@deheus.com] Estimation for the update to the latest *8.5* version – *12h*"", ""Comment 3: including: * Backups: DB + App + generation of dbo.configurationBackup * Deployment + configs json (including Ack) * Scripts execution for IIS pools permissions * Validation of configuration * DHP verifications * HyperCare by deployment team not included * Update RC test env. * Update RC prod env.\'"", ""Comment 4: \'Dear [~marcin.kleszcz@kotrak.com]Estimation approved!You can update as soon as possible.Thank you\'"", ""Comment 5: \'[~piotr.gaczorek@kotrak.com]task można zamknąć. Realizacja na DIM.\'"", ""Comment 6: \'SR will be process in other project. This DGS has been closed.\']""]\nRelated Issues:\n[\'DGS-8844\']\n\n### End'}"
306,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8726\n\n### Instruction:\nthe VT-1347/23 didn\'t integrated to DHC.\r\n\r\nCould you check and fix it?\r\n\r\nThank you\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Analiza wykazała że w dhcService i dhccountry znajdują się nagłowki dla danego dokuemntu"", ""Comment 3: brakuje natomiast jego elementów.Elementy jednego z zamówień zostały zarchiwizowane (status 20) i ponownie dodane do VT!image-2023-03-09-18-57-36-813.png!\'"", \'Comment 4: ""{code:java}select --distinct--o.MainBusinessPartnerId,o.TargetBusinessPartnerId,o.FinalBusinessPartnerId\', \'Comment 5: o.ForeignDocumentNumber,--oe.BusinessUnitId--,oe.No\', \'Comment 6: \\\'o\\\',o.*,\\\'oe\\\',oe.*,\\\'e\\\',e.* o.ForeignDocumentNumber,oe.no,e.No,e.Status,e.WeightValue,e.IsArchived,*from DHPlantVCBusinessLogicMain.dbo.OrderElements oe join DHPlantVCBusinessLogicMain.dbo.Orders o on o.id=oe.id right join DHPlantVCBusinessLogicMain.dbo.VehicleTicketElements e on e.orderid=oe.id and e.OrderNo=oe.no where e.Id = \\\'B8C6C5F6-9ABF-43C2-AA29-66F84D81B254\\\'order by 3{code}{code:java}select top 100 BusinessPartnerId,* from [Evolution_DHCountry].dbo.VehicleTickets where DocumentNumber like \\\'1347%2023/RC\\\'select top 100 * from Evolution_DHCService.dbo.VehicleTickets where DocumentNumber like \\\'1347%2023/RC\\\'{code}{code:java}select top 100 BusinessPartnerId,* from [Evolution_DHCountry].dbo.VehicleTicketElements where VehicleTicketId = \\\'45A4E3E0-D52C-48DE-853D-1A00BA9FA5FC\\\'select top 100 BusinessPartnerId,* from Evolution_DHCService.dbo.VehicleTicketElements where VehicleTicketId = \\\'45A4E3E0-D52C-48DE-853D-1A00BA9FA5FC\\\'{code}""\', \'Comment 7: ""Przesyłając z poziomu DHP jest sukces\', \'Comment 8: !screenshot-2! ale nie ma nadal elementów VT jak Bartek wskazał wcześniej{code:java}select *   FROM [Evolution_DHCService].[dbo].[VehicleTickets]   where ExternalId=\\\'5000269\\\'SELECT *  FROM [Evolution_DHCService].[dbo].[VehicleTicketElements]  where VehicleTicketId=\\\'45A4E3E0-D52C-48DE-853D-1A00BA9FA5FC\\\'  return foo;}{code} !screenshot-3! Już w Plancie jest mniej elementów w tabeli mapowań dla DHP:{code:java}SELECT *  FROM [DHPlantIntegrationDhcServiceIdentityMapping].[dbo].[VehicleTicketElementIdentityMappings]    where [PlantId]=\\\'B8C6C5F6-9ABF-43C2-AA29-66F84D81B254\\\'\\\\tSELECT *  FROM [DHPlantVCBusinessLogicMain].[dbo].[VehicleTicketPackedDispatchElements]  where id=\\\'B8C6C5F6-9ABF-43C2-AA29-66F84D81B254\\\'{code} !screenshot-1! ""\', ""Comment 9: \'VT is now in DHC  !screenshot-4! \'"", ""Comment 10: \'Hi Piotr ,now is correct"", ""Comment 11: thank you.\'"", ""Comment 12: \'Thank you for confirmation.\']""]\nRelated Issues:\n[\'DAP-13422\']\n\n### End'}"
307,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8725\n\n### Instruction:\nIt should not be possible to edit a feed sale document whenever it has the status Archived.\r\n\r\nNow still Milas feed sales are imported whenever there is no new round available yet. This should not be the case.\r\n\r\nAlso it is still possible to manually add own wheat. That should not be possible when the feed sale document is in archived status as well.\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: ""Hi Mitch,{quote}Now still Milas feed sales are imported whenever there is no new round available yet. This should not be the case.{quote}It will be needed to modify it in integration. If there will be some exported feed sales from Milas and Feed sale in Intense will be archived we can block importing this feed sales to Intense and report error in webmethods. Then in Milas it should be reported to user somehow.Should we do changes in integration like described above?----{quote}It should not be possible to edit a feed sale document whenever it has the status Archived.{quote}{quote}Also it is still possible to manually add own wheat. That should not be possible when the feed sale document is in archived status as well.{quote}In Intense we have role which allow users edit any document\', \'Comment 3: it means that if someone has this right\', ""Comment 4: can edit or adding some values on all documents (even archived).Now these users are in role \'Document edit\'.!image-2023-03-10-15-28-44-662.png!There is also second role which allows to edit documents in any state (there is you"", \'Comment 5: Theo\', \'Comment 6: Richard\', \'Comment 7: Roderick\', \'Comment 8: Bessel\', \'Comment 9: Peter Moeliker\', \'Comment 10: Tim van Drie\', \'Comment 11: Martijn Meier).In that case these users can edit any document in Intense\', \'Comment 12: so this is consequence of this role. It works for all documents if someone has this right.Regards""\', ""Comment 13: \'It will be needed to modify it in integration. If there will be some exported feed sales from Milas and Feed sale in Intense will be archived we can block importing this feed sales to Intense and report error in webmethods. Then in Milas it should be reported to user somehow.Should we do changes in integration like described above? --> It could happen that for instance round 2 is closed in the mean time but that there is still some feed send from Milas. Are we able to somehow post this on round 3 whenever round 3 is active?\'"", ""Comment 14: \'[~grzegorz.materla@kotrak.com]chwilowo przypisuje na Ciebie nie wiem na ile to moze poczekac n Damiana ktory wczesniej to ogladal\'"", \'Comment 15: ""{quote}It will be needed to modify it in integration. If there will be some exported feed sales from Milas and Feed sale in Intense will be archived we can block importing this feed sales to Intense and report error in webmethods. Then in Milas it should be reported to user somehow.Should we do changes in integration like described above?{color:#172b4d}--> It could happen that for instance round 2 is closed in the mean time but that there is still some feed send from Milas. Are we able to somehow post this on round 3 whenever round 3 is active?{color}{quote}Do you mean that information sent from Milas should be somehow saved and should wait in some kind of queue for creating new Round 3 and Feed sale 3 document in Intense?I don\\\'t think that it\\\'s a good solution\', ""Comment 16: because we don\'t have clear information if there will be in the future created Round 3 in Intense and we don\'t have some kind of temporary data which should be sent when something will happen in Intense (someone create Round 3). It will be needed to verify data in intense and xml files"", \'Comment 17: so it will be difficult.When we block this feed sale sent from Milas and integration will not allow to add it in Intense\', \'Comment 18: it will be immediately clear information for user (if it will be handled in webmethods <-> Milas).""\', ""Comment 19: \'!image-2023-03-21-13-36-37-537!Hi [~mbovene@deheus.com]"", ""Comment 20: please take a look at this diagram and confirm the requirements.\'"", ""Comment 21: \'Yes"", \'Comment 22: this is clear. In stead of ""Check for recent round numer for the same Contract"" we should maybe same ""Check for recent round numer for the same delivery customer"".It can be that one contact has ended but for a next contact a new round has been created. It that case the food should be booked on that specific round. \\\'\', ""Comment 23: \'Ok"", \'Comment 24: just for confirmation:If we receive a message with round number 016951/0007/0001\', \'Comment 25: which is already in the archive\', \'Comment 26: and 016951/*0007*/0002 does not exist\', \'Comment 27: but\', \'Comment 28: for example\', \'Comment 29: 016951/*0008*/0001 is active\', ""Comment 30: should we book a Feed on this round?\'"", ""Comment 31: \'Yes"", ""Comment 32: that is indeed the case.\'"", \'Comment 33: ""Hi [~mbovene@deheus.com],It\\\'s done. It can be tested on the IBIP_DH_TEST environment.""\', \'Comment 34: ""[~mbovene@deheus.com]we have an additional questions about some important details.1. What determine that Round is active? It should be status of document or that we have active processes (tasks) to this document?There is difference and these 2 parameters can be different. It can be case like this in this order:1 st process was closed and document has been sent to \\\'Archive\\\' 2 nd process has been started 3 rd process has been started 2 nd process wasclosed and document has been sent to \\\'Archive\\\'3 rd process is still open in Intense and document is possible to edit Status is \\\'Archive\\\' because field status is filled in when document is sent to \\\'Archive\\\' and last activity was sent document to Archive in 2 nd process.Example on IBIP_DH_TEST - round001056/0292/0001 !image-2023-04-03-10-51-27-904.png! !image-2023-04-03-10-51-52-679.png! 2.What should be done when someone feed sale will be sent from Milas to Intense and the same customer exists in other sectors.It could be case when there is no active rounds for customer with code807615 in MAS NL and there will be active round for customer807615 in OPPAS/PAS. In this case feed sale will be added to this round in Intense (last active round number for customer) When it will be based on customer from round number like 807615/0005/0001 \', \'Comment 35: first part of round is verified (customer code) and it will added to feed sale for this last round of this customer code.""\', ""Comment 36: \'1. Status of the document.2.What should be done when someone feed sale will be sent from Milas to Intense and the same customer exists in other sectors.  --> It will never happen.\'"", ""Comment 37: \'Here is case on Prod database with customer code 807615 in more than one sector!image-2023-04-03-11-57-45-045.png!\'"", ""Comment 38: \'List of customer codes in more than 1 sector[^CustomerCodesInFewSectors.xlsx]\'"", \'Comment 39: ""We need to know what should be done in case when we have the same customer code in different sectors.In this case if customer exists in few sectors system looks for recent round for this customer\', \'Comment 40: then it\\\'s possible that feed sale line will be added to different sector than someone expects. In XML file there is no information about sector and system looking for customer from 1st part of round number like 807615/0005/0001.""\', ""Comment 41: \'Can be moved to PROD.\'"", ""Comment 42: \'It can be moved"", ""Comment 43: need to plan deployment.\']""]\nRelated Issues:\n[]\n\n### End'}"
308,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8724\n\n### Instruction:\nWe see code (883486100011) balance of Transaction and balance of Warehouse release are not same. Please refer attached for more details. \r\n\r\nCould you please help check why those are not same? This is Feed CDN.\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: \'Difference is directly related with PW-00000004/01/23/Y1 document"", \'Comment 4: and chossen date in Transaction > Chronologically list.!image-2023-03-09-14-15-21-959.png!Document issue date is set to 1st of January 2023 and its intake date is set to 1st of November 2023!image-2023-03-09-14-17-56-269.png!Choosen filter is set to Date wystawienia what means release date.Transaction > Chronologically list is created based onissue date. That mean when You choose Date: Date of rel./recive in filter both lists will have the same documents\', \'Comment 5: and quantity will be consistent.Please\', ""Comment 6: let me know if the answer is sufficient for you. Do you expect any additional actions from us regarding this issue? Can we close this ticket?\'"", ""Comment 7: \'Hi"", ""Comment 8: I’m clear. Could we change date back 1st Nov 2023 to 1st Jan 2023 since date is wrong by user. Thanks\'"", ""Comment 9: \'Date has been changed. Please check.\'"", ""Comment 10: \'Now is ok. Please close the ticket. Thank you.\']""]\nRelated Issues:\n[]\n\n### End'}"
309,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8723\n\n### Instruction:\nWe didn\'t have opportunity to test it since the last request if it was changed properly until now so we need to change iban and swift code for all the Invoices for Kosovo just like in DGS-8547 request. Please check the screenshots. Thank you. \n\n### Response:\n[""Comment 1: [\'!image!!image-1!\'"", \'Comment 2: ""Hello\', \'Comment 3: the printout  is called \\\'KOSOVO Invoice test\\\' !screenshot-1! I added an entry as for the earlier printoutPlease check if it\\\'s supposed to look like this !screenshot-2! Regards.""\', ""Comment 4: \'Hello"", \'Comment 5: it should be on all the invoices just like this as well. Whatever bank is under PAYMENT on the left side (Raiffeisen\', \'Comment 6: Sberbank etc …)\', ""Comment 7: on all of them on the right side should be (AIK bank) as in the screenshot for all the Kosovo invoices.!image-2!\'"", ""Comment 8: \'Hello"", ""Comment 9: yes we will make the changes. Can i get the path as before then each printout to change?Like this: !screenshot-3! \'"", ""Comment 10: \'Your screenshot has correct path. Sales Export Invoice/Kosovo Invoice/View on the screen.\'"", ""Comment 11: \'Hi"", ""Comment 12: printout has been updated.\'"", ""Comment 13: \'Hi our invoicing dept has checked again and it is good path and the right side but they also want all the invoices on the left side under Payment to be the same AIK bank. We closed all the other bank accounts in other banks and now we need for them only this AIK banka data. Sorry for this inconvenience. \'"", \'Comment 14: ""Hi,sure I\\\'ll change it just now just move the bank account from right to left and leave one\', \'Comment 15: like below?Thank you. !screenshot-4! ""\', ""Comment 16: \'Yes on both sides the same AIK bank. Thank you!\'"", \'Comment 17: ""So only then will the left and right side be the same\', \'Comment 18: is this how the invoice should look like?Isn\\\'t one side enough? !screenshot-5! printout name for tests \\\'KOSOVO Invoice test\\\'""\', ""Comment 19: \'Hi Piotr"", ""Comment 20: Our Invoicing dept wants to use again Raiffeisen and AIK bank and they want it on all the Kosovo invoice. Next time I will make meeting with them prior to create request because they change a lot. So left Raiffeisen and on the right AIK on all Kosovo invoices on the path Sales Export Invoice/Kosovo Invoice/View on the screen. Check the screenshots and thank you for your patience! Best regards.!image-3!!image-4!\'"", ""Comment 21: \'Hi"", \'Comment 22: the printout has been modified as requested\', ""Comment 23: please check and send feedback.Regards.\'"", ""Comment 24: \'It is all OK now. Please close this request and thank you. Best regards!\'"", ""Comment 25: \'Thank you for confirmation"", ""Comment 26: have a nice weekend.\']""]\nRelated Issues:\n[]\n\n### End'}"
310,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8722\n\n### Instruction:\nHello, \r\n\r\nyesterday I found out that we are able to post a regular document without selecting a round number.\r\nI understood that for all sectors this should be obligatory for financed and regular documents.\r\n\r\nI heard that trade is different, no round selection there, but document flow is different too.\r\n\r\nKR,\r\nChristine\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 2: ""Hello,I\\\'ve chcecked configuration in Intense.Only for Purchase Invoices with Registered type can be processed little differently and you should be able to sent it without approval flow (directly from state Entry to Archive). For trade type of invoice flow is normal like other invoices.Indeed Full round number are not mandatory on SI and PI invoices. We can add some validation\', \'Comment 3: maybe the best will be validation when invoice is sent to Archive and if \\\'Full number\\\' (Round) will be empty we can block document and not allow sent it to Archive.@MitchShould we adjust system and make mandatory on invoices field with Round number (\\\'Full number\\\')?Maybe it should be also implemented some conditions when invoice should has filled Round number.I see a lot of invoices in MAS NL (PI or SI) that don\\\'t have filled this field - for now around 2500 form13800 invoices in total. Most of these 2500 are regular. I\\\'m not sure that is good solution to make mandatory this field on invoices and if this will be helpful and allow to avoid some situations.Regards""\', \'Comment 4: ""Should we adjust system and make mandatory on invoices field with Round number (\\\'Full number\\\')? --> Yes please. Indeed before we send them to archive they should have a full number.Let\\\'s investigate the empty ones. Can you send me a report? I would like to investigat e them and see why they do not have a full number on them.""\', ""Comment 5: \'The report should consist invoices from all other sectors as well.\'"", ""Comment 6: \'{color:black}Damian,{color}  {color:black}{color} {color:black}Thanks for your remark and check!{color} {color:black}For NAS all our regular postings should have a round number.{color} {color:black}{color} {color:black}I understood from the MAS colleagues that our BE (boer BE: 888888) transactions and trade transaction are the exception to the rule.{color} {color:black}But in all other transactions when a regular posting is created"", \'Comment 7: we have to select a round number. Otherwise posting will not appear on the round.{color} {color:black}{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Christinede{color} |{color:#000001} {color} |{color:#000001} Jong{color} |  {color:#000001}MedewerkerContractadministratie{color} | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.de-heus.nl/]>{color} | |  *{color:#006FB7} *DEHEUSVOEDERSB.V.*{color}* | | | |{color:#000001} Postbus396 6710BJEde \\\\u200b{color} | |{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} | | |{color:#000001} T:0318675567{color} |  {color:#000001}KvK14626985{color}   _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | | !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | | !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} | | !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} |        *Van:* Damian Świstek (Jira) <jira@kotrak.com>   *Verzonden:* vrijdag 10 maart 2023 13:09  *Aan:* Jong\', ""Comment 8: Christine de <CJong@deheus.com>  *Onderwerp:* DGS-8722 Round number selection should be obligatory   \'"", ""Comment 9: \'Do przygotowania raport z dokumentów faktur"", ""Comment 10: które nie mają uzupełnionych rund.Do dodania walidacja przy przesyłaniu faktur do archiwum.\'"", ""Comment 11: \'Is this closed?\'"", ""Comment 12: \'{color:black}Hi Mitch,{color} {color:black} No action seen from Kotrak after my remark from{color} {color:#707070}10/Mar/23 13:49{color} {color:black}{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Christinede{color} |{color:#000001} {color} |{color:#000001} Jong{color} |  {color:#000001}MedewerkerContractadministratie{color} | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.de-heus.nl/]>{color} | |  *{color:#006FB7} *DEHEUSVOEDERSB.V.*{color}* | | | |{color:#000001} Postbus396 6710BJEde \\\\u200b{color} | |{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} | | |{color:#000001} T:0318675567{color} |  {color:#000001}KvK14626985{color}   _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | | !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | | !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} | | !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} |        *Van:* Mitch van Bovene (Jira) <jira@kotrak.com>   *Verzonden:* dinsdag 21 maart 2023 11:46  *Aan:* Jong"", ""Comment 13: Christine de <CJong@deheus.com>  *Onderwerp:* DGS-8722 Round number selection should be obligatory   \'"", \'Comment 14: ""Only in NAS sector should be implemented validation when document SI or PI only with type \\\'Regular\\\' has empty Round number (\\\'Full number\\\')?Or it should be implemented to all invoices in all sectors and then should be verified and it shouldn\\\'t be possible to send to \\\'Archive\\\' whenRound number (\\\'Full number\\\') is empty?We\\\'ll prepare mentioned before report and it will be possible to analyse invoices.""\', \'Comment 15: ""[~tomasz.zygon@kotrak.com]do przygotowania raport spod bazy do Excela ze wszystkimi fakturami - SI i PI ze wszystkich sektorów\', \'Comment 16: które mają pustę rundę (\\\'Full number\\\').""\', ""Comment 17: \'{color:black}Hi Damian,{color} {color:black}{color} {color:black}Make it only for NAS. In MAS there are exceptions.{color} {color:black}Thanks for your action.{color} {color:black}{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Christinede{color} |{color:#000001} {color} |{color:#000001} Jong{color} |  {color:#000001}MedewerkerContractadministratie{color} | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.de-heus.nl/]>{color} | |  *{color:#006FB7} *DEHEUSVOEDERSB.V.*{color}* | | | |{color:#000001} Postbus396 6710BJEde \\\\u200b{color} | |{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} | | |{color:#000001} T:0318675567{color} |  {color:#000001}KvK14626985{color}   _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | | !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | | !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} | | !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} |        *Van:* Damian Świstek (Jira) <jira@kotrak.com>   *Verzonden:* dinsdag 21 maart 2023 12:52  *Aan:* Jong"", ""Comment 18: Christine de <CJong@deheus.com>  *Onderwerp:* DGS-8722 Round number selection should be obligatory   \'"", ""Comment 19: \'[^PI,SI without rounds-2.csv]\'"", ""Comment 20: \'select Doc_FullNumber ,doc_id AS ID,pi.DIC_SValue as [Type_Purchase],si.DIC_SValue as [Type_Sales],Frm_FullName AS SECTOR from Documents left join Firms on Doc_FrmID=frm_id left join dictionaries as pi on pi.dic_id=Doc_IntColumn10 left join dictionaries as si on si.dic_id=Doc_IntColumn11where Doc_DdfID in (13,14,24,25,28,29,42,43,51,52,57,58) and Doc_IntColumn12 is null\'"", ""Comment 21: \'{color:black}Please only make it obligatory in NAS.{color} {color:black}MAS has exceptions.{color} {color:black}{color} {color:black}This csv mostly shows MAS documents.{color} {color:black}I will change the NAS if not already done.{color} {color:black}{color} {color:black}{color} {color:black}{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Christinede{color} |{color:#000001} {color} |{color:#000001} Jong{color} |  {color:#000001}MedewerkerContractadministratie{color} | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.de-heus.nl/]>{color} | |  *{color:#006FB7} *DEHEUSVOEDERSB.V.*{color}* | | | |{color:#000001} Postbus396 6710BJEde \\\\u200b{color} | |{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} | | |{color:#000001} T:0318675567{color} |  {color:#000001}KvK14626985{color}   _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | | !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | | !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} | | !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} |        *Van:* Tomasz Zygoń (Jira) <jira@kotrak.com>   *Verzonden:* dinsdag 21 maart 2023 13:26  *Aan:* Jong"", ""Comment 22: Christine de <CJong@deheus.com>  *Onderwerp:* DGS-8722 Round number selection should be obligatory   !image006.gif!\'"", \'Comment 23: ""{color:#000000}Hi [~CJong@deheus.com],{color}{quote}{color:#000000}Make it only for NAS. In MAS there are exceptions.{color}{quote}{color:#000000}We can do a validation for NAS sector only for \\\'Regular\\\' types of PI\\\'s and SI\\\'s.Is it right condtion? {color}{color:#000000}It will be verified when document is sent to \\\'Archive\\\'.{color}[~mbovene@deheus.com]Should we do also validations to other sectors or do you need to analyse the report at first?Here is a report with invoices with empty rounds.[^PI,SI without rounds-2.csv]""\', ""Comment 24: \'{color:black}Hi Tomasz,{color} {color:black}{color} {color:black}I am not able to make corrections so this is what a checked.{color} |{color:black} Doc_fullnumber{color} |{color:black} Doc_id{color} |{color:black} Type of purchase{color} |{color:black} Type of sale{color} |{color:black} Sector{color} |{color:black} Remark{color} | |{color:black} PI-RLN/2022/0168{color} |{color:black} 34832{color} |{color:black} Regular purchase{color} |{color:black} NULL{color} |{color:black} NAS{color} |{color:black} Cancelled{color} | |{color:black} SI-RLN/2022/0181{color} |{color:black} 36658{color} |{color:black} NULL{color} |{color:black} Regular sale{color} |{color:black} NAS{color} |{color:black} Conversiepost?{color} | |{color:black} SI-RLN/2022/0185{color} |{color:black} 36662{color} |{color:black} NULL{color} |{color:black} Regular sale{color} |{color:black} NAS{color} |{color:black} Conversiepost?{color} | |{color:black} SI-RLN/2022/0186{color} |{color:black} 36663{color} |{color:black} NULL{color} |{color:black} Regular sale{color} |{color:black} NAS{color} |{color:black} Conversiepost?{color} | |{color:black} SI-RLN/2022/0193{color} |{color:black} 36670{color} |{color:black} NULL{color} |{color:black} Regular sale{color} |{color:black} NAS{color} |{color:black} Conversiepost?{color} | |{color:black} PI-RLN/2022/0368{color} |{color:black} 54130{color} |{color:black} Regular purchase{color} |{color:black} NULL{color} |{color:black} NAS{color} |{color:black} Cancelled{color} | |{color:black} PI-RLN/2022/0389{color} |{color:black} 56907{color} |{color:black} Regular purchase{color} |{color:black} NULL{color} |{color:black} NAS{color} |{color:black} Cancelled{color} | |{color:black} PI-RLN/2022/0396{color} |{color:black} 57265{color} |{color:black} Regular purchase{color} |{color:black} NULL{color} |{color:black} NAS{color} |{color:black} Cancelled{color} | |{color:black} SI-RTN/2022/0131{color} |{color:black} 57945{color} |{color:black} NULL{color} |{color:black} Registered sale{color} |{color:black} NAS{color} |{color:black} should be on 101662/0029/0001{color} | |{color:black} SI-RTN/2023/0216{color} |{color:black} 92252{color} |{color:black} NULL{color} |{color:black} Registered sale{color} |{color:black} NAS{color} |{color:black} should be on 100893/0012/0001{color} | |{color:black} PI-RLN/2023/0402{color} |{color:black} 107876{color} |{color:black} Regular purchase{color} |{color:black} NULL{color} |{color:black} NAS{color} |{color:black} is posted today on fictive customer with round number{color} | |{color:black} PI-RLN/2023/0403{color} |{color:black} 107877{color} |{color:black} Regular purchase{color} |{color:black} NULL{color} |{color:black} NAS{color} |{color:black} is posted today on round number 102079/0061/0001{color} |  {color:black}{color} {color:black}The cancelled ones should be disregard.{color} {color:black}Conversion post => Conversiepost.{color} [{color:black}@Bovene"", \'Comment 25: Mitch van{color}|mailto:mbovene@deheus.com]{color:black} is it correct that these are posted as regulars?{color} {color:black}{color} {color:black}Could you/or someone change my highlighted yellow 2 lines? It should be on the round mentioned in column remark.{color} {color:black}Thanks!{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:* Jong\', \'Comment 26: Christine de   *Verzonden:* dinsdag 21 maart 2023 13:41  *Aan:* dgs@help.kotrak.com  *Onderwerp:* RE: DGS-8722 Round number selection should be obligatory    {color:black}Please only make it obligatory in NAS.{color} {color:black}MAS has exceptions.{color} {color:black}{color} {color:black}This csv mostly shows MAS documents.{color} {color:black}I will change the NAS if not already done.{color} {color:black}{color} {color:black}{color} {color:black}{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Christinede{color} |{color:#000001} {color} |{color:#000001} Jong{color} |  {color:#000001}MedewerkerContractadministratie{color} | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.de-heus.nl/]>{color} | |  *{color:#006FB7} *DEHEUSVOEDERSB.V.*{color}* | | | |{color:#000001} Postbus396 6710BJEde \\\\u200b{color} | |{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} | | |{color:#000001} T:0318675567{color} |  {color:#000001}KvK14626985{color}   _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | | !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | | !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} | | !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} |        *Van:* Tomasz Zygoń (Jira) <[jira@kotrak.com|mailto:jira@kotrak.com]>   *Verzonden:* dinsdag 21 maart 2023 13:26  *Aan:* Jong\', ""Comment 27: Christine de <[CJong@deheus.com|mailto:CJong@deheus.com]>  *Onderwerp:* DGS-8722 Round number selection should be obligatory   !image006.gif!\'"", ""Comment 28: \'{color:black}Hi Damian,{color} {color:black}{color} {color:black}Yes"", \'Comment 29: but the registered should also be obligatory as the registration invoices are on the round in Intense.{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Christinede{color} |{color:#000001} {color} |{color:#000001} Jong{color} |  {color:#000001}MedewerkerContractadministratie{color} | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.de-heus.nl/]>{color} | |  *{color:#006FB7} *DEHEUSVOEDERSB.V.*{color}* | | | |{color:#000001} Postbus396 6710BJEde \\\\u200b{color} | |{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} | | |{color:#000001} T:0318675567{color} |  {color:#000001}KvK14626985{color}   _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | | !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | | !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} | | !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} |        *Van:* Damian Świstek (Jira) <jira@kotrak.com>   *Verzonden:* dinsdag 21 maart 2023 13:51  *Aan:* Jong\', ""Comment 30: Christine de <CJong@deheus.com>  *Onderwerp:* DGS-8722 Round number selection should be obligatory   !image006.gif!\'"", ""Comment 31: \'Hi Christine"", \'Comment 32:  I have no idea to be honest.  If you think they should have been financed than we need to change them.  Regards\', \'Comment 33:  Mitch     *Van:* Jong\', \'Comment 34: Christine de <CJong@deheus.com>   *Verzonden:* dinsdag 21 maart 2023 14:00  *Aan:* dgs@help.kotrak.com; Bovene\', \'Comment 35: Mitch van <mbovene@deheus.com>  *Onderwerp:* RE: DGS-8722 Round number selection should be obligatory    {color:black}Hi Tomasz,{color} {color:black}{color} {color:black}I am not able to make corrections so this is what a checked.{color} |{color:black} Doc_fullnumber{color} |{color:black} Doc_id{color} |{color:black} Type of purchase{color} |{color:black} Type of sale{color} |{color:black} Sector{color} |{color:black} Remark{color} | |{color:black} PI-RLN/2022/0168{color} |{color:black} 34832{color} |{color:black} Regular purchase{color} |{color:black} NULL{color} |{color:black} NAS{color} |{color:black} Cancelled{color} | |{color:black} SI-RLN/2022/0181{color} |{color:black} 36658{color} |{color:black} NULL{color} |{color:black} Regular sale{color} |{color:black} NAS{color} |{color:black} Conversiepost?{color} | |{color:black} SI-RLN/2022/0185{color} |{color:black} 36662{color} |{color:black} NULL{color} |{color:black} Regular sale{color} |{color:black} NAS{color} |{color:black} Conversiepost?{color} | |{color:black} SI-RLN/2022/0186{color} |{color:black} 36663{color} |{color:black} NULL{color} |{color:black} Regular sale{color} |{color:black} NAS{color} |{color:black} Conversiepost?{color} | |{color:black} SI-RLN/2022/0193{color} |{color:black} 36670{color} |{color:black} NULL{color} |{color:black} Regular sale{color} |{color:black} NAS{color} |{color:black} Conversiepost?{color} | |{color:black} PI-RLN/2022/0368{color} |{color:black} 54130{color} |{color:black} Regular purchase{color} |{color:black} NULL{color} |{color:black} NAS{color} |{color:black} Cancelled{color} | |{color:black} PI-RLN/2022/0389{color} |{color:black} 56907{color} |{color:black} Regular purchase{color} |{color:black} NULL{color} |{color:black} NAS{color} |{color:black} Cancelled{color} | |{color:black} PI-RLN/2022/0396{color} |{color:black} 57265{color} |{color:black} Regular purchase{color} |{color:black} NULL{color} |{color:black} NAS{color} |{color:black} Cancelled{color} | |{color:black} SI-RTN/2022/0131{color} |{color:black} 57945{color} |{color:black} NULL{color} |{color:black} Registered sale{color} |{color:black} NAS{color} |{color:black} should be on 101662/0029/0001{color} | |{color:black} SI-RTN/2023/0216{color} |{color:black} 92252{color} |{color:black} NULL{color} |{color:black} Registered sale{color} |{color:black} NAS{color} |{color:black} should be on 100893/0012/0001{color} | |{color:black} PI-RLN/2023/0402{color} |{color:black} 107876{color} |{color:black} Regular purchase{color} |{color:black} NULL{color} |{color:black} NAS{color} |{color:black} is posted today on fictive customer with round number{color} | |{color:black} PI-RLN/2023/0403{color} |{color:black} 107877{color} |{color:black} Regular purchase{color} |{color:black} NULL{color} |{color:black} NAS{color} |{color:black} is posted today on round number 102079/0061/0001{color} |  {color:black}{color} {color:black}The cancelled ones should be disregard.{color} {color:black}Conversion post => Conversiepost.{color} [{color:black}@Bovene\', \'Comment 36: Mitch van{color}|mailto:mbovene@deheus.com]{color:black} is it correct that these are posted as regulars?{color} {color:black}{color} {color:black}Could you/or someone change my highlighted yellow 2 lines? It should be on the round mentioned in column remark.{color} {color:black}Thanks!{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://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.de-heus.nl%2F&data=05%7C01%7Cmbovene%40deheus.com%7C84169882cda04349420008db2a0c2369%7C1004261bdfb74f37830f7438cb8a1b69%7C1%7C0%7C638150003838789815%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=55URh6sW8pQZOoZoQ3iYubesdl259DyS4eVG7YoMk5o%3D&reserved=0]>{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://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.de-heus.nl%2Fprivacy-beleid&data=05%7C01%7Cmbovene%40deheus.com%7C84169882cda04349420008db2a0c2369%7C1004261bdfb74f37830f7438cb8a1b69%7C1%7C0%7C638150003838789815%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=vDpzDgWUEyp4135EutBLC3zkle0sHatFHwLsb6f2aLc%3D&reserved=0]{color:#000001} _._{color}_ | | !image002! <[https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.facebook.com%2Fdeheusvoeders&data=05%7C01%7Cmbovene%40deheus.com%7C84169882cda04349420008db2a0c2369%7C1004261bdfb74f37830f7438cb8a1b69%7C1%7C0%7C638150003838946033%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=be2kCHcd3v8xGzO%2BuMvFn0LMQCMvpbGOlkpEJDpA%2B6c%3D&reserved=0]>{color:black}{color} | | !image003! <[https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftwitter.com%2Fde_heus_voeders&data=05%7C01%7Cmbovene%40deheus.com%7C84169882cda04349420008db2a0c2369%7C1004261bdfb74f37830f7438cb8a1b69%7C1%7C0%7C638150003838946033%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=f8GWbU8bOLYlY2fMVE8OG6GK4ODNihK7XbUoCf%2F5ZRE%3D&reserved=0]>{color:black}{color} | | !image004! <[https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.youtube.com%2Fchannel%2FUCqkrGebUlFowgumurz-abxQ&data=05%7C01%7Cmbovene%40deheus.com%7C84169882cda04349420008db2a0c2369%7C1004261bdfb74f37830f7438cb8a1b69%7C1%7C0%7C638150003838946033%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=u%2FyfPAOoVaGFvamj7lztslmOQfnixblyXcE4%2Fq5yv58%3D&reserved=0]>{color:black}{color} | | !image005! <[https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.linkedin.com%2Fcompany%2Fde-heus-voeders-b-v-%2F&data=05%7C01%7Cmbovene%40deheus.com%7C84169882cda04349420008db2a0c2369%7C1004261bdfb74f37830f7438cb8a1b69%7C1%7C0%7C638150003838946033%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=%2B5SBRV1Uv9A2hizJiwA%2BzSjb%2FCHL4%2FLZYIeAIn%2FiYnQ%3D&reserved=0]>{color:black}{color} |        *Van:* Jong\', \'Comment 37: Christine de   *Verzonden:* dinsdag 21 maart 2023 13:41  *Aan:* [dgs@help.kotrak.com|mailto:dgs@help.kotrak.com]  *Onderwerp:* RE: DGS-8722 Round number selection should be obligatory    {color:black}Please only make it obligatory in NAS.{color} {color:black}MAS has exceptions.{color} {color:black}{color} {color:black}This csv mostly shows MAS documents.{color} {color:black}I will change the NAS if not already done.{color} {color:black}{color} {color:black}{color} {color:black}{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Christinede{color} |{color:#000001} {color} |{color:#000001} Jong{color} |  {color:#000001}MedewerkerContractadministratie{color} | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.de-heus.nl%2F&data=05%7C01%7Cmbovene%40deheus.com%7C84169882cda04349420008db2a0c2369%7C1004261bdfb74f37830f7438cb8a1b69%7C1%7C0%7C638150003838946033%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=f4LhGvowIfaFCum%2Blou5d6VTxZNN8NQg%2BqfkFOrWnjo%3D&reserved=0]>{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://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.de-heus.nl%2Fprivacy-beleid&data=05%7C01%7Cmbovene%40deheus.com%7C84169882cda04349420008db2a0c2369%7C1004261bdfb74f37830f7438cb8a1b69%7C1%7C0%7C638150003838946033%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Q713OKBUL6iLEHUTIJf1i4%2FdY83qjcStAWJ76SBXn%2Bk%3D&reserved=0]{color:#000001} _._{color}_ | | !image002! <[https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.facebook.com%2Fdeheusvoeders&data=05%7C01%7Cmbovene%40deheus.com%7C84169882cda04349420008db2a0c2369%7C1004261bdfb74f37830f7438cb8a1b69%7C1%7C0%7C638150003838946033%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=be2kCHcd3v8xGzO%2BuMvFn0LMQCMvpbGOlkpEJDpA%2B6c%3D&reserved=0]>{color:black}{color} | | !image003! <[https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftwitter.com%2Fde_heus_voeders&data=05%7C01%7Cmbovene%40deheus.com%7C84169882cda04349420008db2a0c2369%7C1004261bdfb74f37830f7438cb8a1b69%7C1%7C0%7C638150003838946033%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=f8GWbU8bOLYlY2fMVE8OG6GK4ODNihK7XbUoCf%2F5ZRE%3D&reserved=0]>{color:black}{color} | | !image004! <[https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.youtube.com%2Fchannel%2FUCqkrGebUlFowgumurz-abxQ&data=05%7C01%7Cmbovene%40deheus.com%7C84169882cda04349420008db2a0c2369%7C1004261bdfb74f37830f7438cb8a1b69%7C1%7C0%7C638150003838946033%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=u%2FyfPAOoVaGFvamj7lztslmOQfnixblyXcE4%2Fq5yv58%3D&reserved=0]>{color:black}{color} | | !image005! <[https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.linkedin.com%2Fcompany%2Fde-heus-voeders-b-v-%2F&data=05%7C01%7Cmbovene%40deheus.com%7C84169882cda04349420008db2a0c2369%7C1004261bdfb74f37830f7438cb8a1b69%7C1%7C0%7C638150003838946033%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=%2B5SBRV1Uv9A2hizJiwA%2BzSjb%2FCHL4%2FLZYIeAIn%2FiYnQ%3D&reserved=0]>{color:black}{color} |        *Van:* Tomasz Zygoń (Jira) <[jira@kotrak.com|mailto:jira@kotrak.com]>   *Verzonden:* dinsdag 21 maart 2023 13:26  *Aan:* Jong\', ""Comment 38: Christine de <[CJong@deheus.com|mailto:CJong@deheus.com]>  *Onderwerp:* DGS-8722 Round number selection should be obligatory   !image006.gif!\'"", \'Comment 39: ""{color:#000000}Ok\', \'Comment 40: so the final condition for validation in NAS sector is:{color} * {color:#000000}SI/PI should has \\\'Full number\\\' if type of SI/PI = \\\'Regular\\\' or \\\'Registered\\\'{color}""\', ""Comment 41: \'{color:black}Yes! That’s correct{color} {color:black}😊{color}{color:black}{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Christinede{color} |{color:#000001} {color} |{color:#000001} Jong{color} |  {color:#000001}MedewerkerContractadministratie{color} | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.de-heus.nl/]>{color} | |  *{color:#006FB7} *DEHEUSVOEDERSB.V.*{color}* | | | |{color:#000001} Postbus396 6710BJEde \\\\u200b{color} | |{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} | | |{color:#000001} T:0318675567{color} |  {color:#000001}KvK14626985{color}   _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | | !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | | !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} | | !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} |        *Van:* Damian Świstek (Jira) <jira@kotrak.com>   *Verzonden:* dinsdag 21 maart 2023 14:15  *Aan:* Jong"", ""Comment 42: Christine de <CJong@deheus.com>  *Onderwerp:* DGS-8722 Round number selection should be obligatory   \'"", \'Comment 43: ""Here is a report with invoices with empty rounds:PI,SI without rounds-2.csvCould you please add the customer\', ""Comment 44: supplier and reference as columns to this list? I notice that in MAS NL many SI\'s with missing full numbers are related to SR\'s for Belgium customers. And indeed"", \'Comment 45: for these customers there are no rounds available in MAS NL.""\', ""Comment 46: \'{color:black}Hi Mitch,{color} {color:black}{color} {color:black}Already did this for NAS yesterday.{color}  {color:black}For MAS I lack the time. If there can be made a selection with customer number/name I can have a look.{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Christinede{color} |{color:#000001} {color} |{color:#000001} Jong{color} |  {color:#000001}MedewerkerContractadministratie{color} | | |{color:windowtext}{color} !image001! <[https://www.de-heus.nl/]>{color:black}{color} | |  *{color:#006FB7} *DEHEUSVOEDERSB.V.*{color}* | | | |{color:#000001} Postbus396 6710BJEde \\\\u200b{color} | |{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} | | |{color:#000001} T:0318675567{color} |  {color:#000001}KvK14626985{color}   _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_{color}_[ _{color:#000001} _DeHeusVoeders_{color}_|https://www.de-heus.nl/privacy-beleid] _{color:#000001} _._{color}_ | | !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | | !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} | | !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} |        *Van:* Mitch van Bovene (Jira) <jira@kotrak.com>   *Verzonden:* dinsdag 21 maart 2023 15:59  *Aan:* Jong"", ""Comment 47: Christine de <CJong@deheus.com>  *Onderwerp:* DGS-8722 Round number selection should be obligatory   \'"", ""Comment 48: \'Here is report with PI,SI without rounds with Customer"", \'Comment 49: Reference\', ""Comment 50: Supplier columns[^PI,SI without rounds.xlsx]\']""]\nRelated Issues:\n[]\n\n### End'}"
311,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8721\n\n### Instruction:\nPO 157/23 created in February is not showing in Johnson DHP\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'I do not see the linking of this item 960917"", ""Comment 3: !screenshot-1! Can you check?\'"", ""Comment 4: \'you are right. i will work on the linking. please close\']""]\nRelated Issues:\n[]\n\n### End'}"
312,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8720\n\n### Instruction:\nIn DHP, the rewok icon does not appear for this item. The recipe is available at DHC.\r\n\r\nCan you chek please?\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'!image-2023-03-09-14-51-43-839.png!\'"", \'Comment 4: ""{code:java}SELECT *  FROM [DHPlantProdBusinessLogicMain].[dbo].[Items] where code = \\\'31640140-B20\\\' or id = \\\'77DDCF8C-C538-4537-A0EF-1808AC8717F8\\\'SELECT *  FROM [DHPlantProdBusinessLogicMain].[dbo].[ProductionLots] where LotNumber = 0371080323005  select * from [DHPlantProdBusinessLogicMain].[dbo].[ProductionLotElements] where --RecipeId = \\\'AECC782F-D3F8-45BD-83D5-96A8DABA553B\\\'   ItemId in (  \\\'77DDCF8C-C538-4537-A0EF-1808AC8717F8\\\',\\\'7A82B2B7-0B5C-497A-9F2E-DBD5F6BC5CAC\\\'){code}""\', ""Comment 5: \'Warunki dla Broken Batcha!image-2023-03-10-08-07-51-818.png!W DHC brakuje additional technology dla tego itema!image-2023-03-10-08-06-46-398.png!!image-2023-03-10-08-10-11-348.png!!image-2023-03-10-08-10-11-348!\'"", ""Comment 6: \'!image-2023-03-10-08-13-36-241.png!\'"", ""Comment 7: \'Please"", \'Comment 8: verify\', ""Comment 9: the item is not the sameRegards!image-2023-03-10-08-24-19-177.png!!image-2023-03-10-08-41-10-206.png!\'"", ""Comment 10: \'[[DHP] Cannot create rework|onenote:https://kotrak.sharepoint.com/sites/erpasysta/Shared%20Documents/Baza%20wiedzy/Baza%20Wiedzy%20-%20ERPSD/Klienci/DEHEUS/DEHEUS%20APPLICATIONS/Serbia/Baza%20wiedzy.one#%5bDHP%5d%20Cannot%20create%20rework&section-id=\\\\\\\\{2D7CB55A-B2DD-4CFE-B5DC-732963C5C855}&page-id=\\\\\\\\{DA51F7E9-38C9-44AA-BFA1-C92D0B5BCD86}&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%2FSerbia%2FBaza%20wiedzy.one%7C2D7CB55A-B2DD-4CFE-B5DC-732963C5C855%2F%5BDHP%5D%20Cannot%20create%20rework%7CDA51F7E9-38C9-44AA-BFA1-C92D0B5BCD86%2F%29])\'"", ""Comment 11: \'Hi,Can we close this task?Regards\'"", ""Comment 12: \'Hello,We are closing this task as we haven’treceivedany replyfromyouforalong time. If the issueappearsagain"", ""Comment 13: please raise another task.Regards\']""]\nRelated Issues:\n[]\n\n### End'}"
313,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8719\n\n### Instruction:\nSOR-45/02/2023 : Change main/target to customer Coops to KR000000029\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: \'Changed. Please"", ""Comment 4: verify.Regards!image-2023-03-09-11-35-02-285.png!!image-2023-03-09-11-35-17-434.png!\'"", ""Comment 5: \'User did have an comment.They mentioned also an sales invoice.I have asked them to specify what is wanted,\'"", ""Comment 6: \'I did have an reponce.Please do the same with : si-55.02.2023.V \'"", ""Comment 7: \'Initially only SOR was requested.I have changed customer data on Invoice. Please"", ""Comment 8: verify!image-2023-03-17-09-33-14-933.png!Regards\'"", ""Comment 9: \'Ticket can be closed\']""]\nRelated Issues:\n[]\n\n### End'}"
314,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8718\n\n### Instruction:\nWe have problem with generating documents shipment.\r\nDatabase sql05-20\\upg \r\n\n\n### Response:\n[""Comment 1: [\'!image!!image-1!\'"", \'Comment 2: ""Hi Edyta\', \'Comment 3: please create issue in DHITS project because it\\\'s a problem with the test environment.""\', ""Comment 4: \'Hi Piotr"", ""Comment 5: Thank you for information. You can close this task.\']""]\nRelated Issues:\n[]\n\n### End'}"
315,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8717\n\n### Instruction:\nI tried to add/change conditions for a contract in MAS NL. I couldn\'t select a receiver, because it was hard coded on \'according to defined\'. Next, the contract was sent back to \'Administrator\' for changing the conditions. This inbox, I can\'t reach. Could you make sure that the person who does this handling in MAS NL is the one who receives the contract for modifying?\n\n### Response:\n[""Comment 1: [\'!image!\'"", \'Comment 2: ""Hello Steffen,Flow Add change conditions send documents to user who create this document and this is how it\\\'s configured right now. This CF comes from import\', \'Comment 3: so document went to Administrator\\\'s inbox because all documents from import have been created by Administrator.Should we send this documentCF-M/0040 to \\\'Waiting for approval\\\' to Bessel\\\'s inbox?Is there needed to make any changes in this flow Add/change conditions?!image-2023-03-09-09-28-39-507.png!!image-2023-03-09-09-26-39-405.png!""\', \'Comment 4: ""Hello Damian,Yes\', ""Comment 5: we can see Bessel\'s inbox so that would be an option. Administrator we can\'t and we couldn\'t manually send it to Bessel\'s inbox. I know that there is a totally different flow in MAS BE"", ""Comment 6: but I don\'t know if we could and should do this in MAS NL. We only need to be able to modify contracts from some inbox"", \'Comment 7: so this will happen more often.""\', \'Comment 8: ""I\\\'ve sentCF-M/0040 document to Bessel\\\'s inbox\', \'Comment 9: so I hope you can sent it to next flows and edit document. If not\', \'Comment 10: please let us know.Maybe we should think about some adjustments in process it it will be more cases like this.We can adjust it similar like in MAS BE - there is a role for it and document is sent to few users insted of one who created document.@Mitch do you think that it should be adjusted somehow in MAS NL?""\', ""Comment 11: \'So in the future all documents will go to the original creator?I am not sure how we want this to work. If it can be send to the head of the department it will be fine.\'"", \'Comment 12: ""The problem is that the contract goes automatically to administrator once we click \\\'add/change conditions\\\'. So everytime we do this the contract will go to administrator. I can\\\'t choose Bessel or myself or anyone else. Therefor in MAS BE there is a whole other flow for this process.""\', \'Comment 13: ""{quote}So in the future all documents will go to the original creator?{quote}Yes\', ""Comment 14: documents will go to the user who will create document. Now there are a lot of contracts from migration which we created as Administrator and flow sends these contracts to Administrator.At this moment it looks like that in MAS NL for Contract farmer documents. Everytime when someone will choose\'add/change conditions\' document will go to this user who created CF.!image-2023-03-09-13-38-28-527.png!{quote}I am not sure how we want this to work. If it can be send to the head of the department it will be fine.{quote}We can add some role or use existing (Senior contract administrator role is connected with state\'add/change conditions\') with users and then user can choose who should get this CF whenclick \'add/change conditions\'"", \'Comment 15: we need only list of users possible to select in this flow if it should be handle in that way.""\', \'Comment 16: ""Let\\\'s do it like that. Who needs to be in this option menu:MAS NL - Nancy\', \'Comment 17: Koen & Peter MAS BE - Koen & SteffenNAS - Christine & BertVAS - Bert & PeterPAS/OPPAS - Thelma & PeterLAS - Bert & Peter""\', ""Comment 18: \'Hello,I have 2 questions:1. What is the status of this? I have a few contracts I need to open and modify in MAS NL2. Is it possible that I will be added to the MAS NL list? (I discussed this with Koen)\'"", ""Comment 19: \'Update:The one you put in Bessel\\\\\'s inbox I modified and then approved the change. Now that it\\\\\'s active again"", \'Comment 20: the contract goes back to ""Administrator"".!image-1!\\\'\', \'Comment 21: ""Hi Steffen,We can add you also to this list in MAS NL for flow \\\'Add/change conditions\\\'.How we should handle it with flow \\\'Active (revised)\\\' - should we adjust it sismilar like in the flow\\\'Add/change conditions\\\'?What should we do with these document. We can send some documents to Add change conditions before changes if it\\\'s urgent and you need to work with these documents. Please let us know which documents should be possible to adjust by you or other users (In MAS NLNancy\', \'Comment 22: Koen\', \'Comment 23: Peter\', \'Comment 24: Steffen)Regards""\', \'Comment 25: ""I would indeed think that this named flow is sufficient for contract farmer\', \'Comment 26: so both for add/changing conditions\', \'Comment 27: approval and activation. Other documents like invoices\', \'Comment 28: rounds and feed sales we can re-open through \\\'start new proces\\\'.""\', ""Comment 29: \'Is there already an update on this? I should need to edit some contracts this week in MAS NL.\'"", ""Comment 30: \'Hello,What is the status of this topic?\'"", \'Comment 31: ""Hello,We\\\'re working on this topic and it should be ready on test environment today.We\\\'ll inform you in task when it will be ready to test.Regards""\', ""Comment 32: \'You can test it now on UAT.\'"", ""Comment 33: \'Hello,The flow to add/change conditions is fine.However"", \'Comment 34: when approving the changes (as specialist and as sector lead)\', ""Comment 35: can we be selected there as well?Now the contract will only still be in my inbox afterwards if I put myself as specialist and sector lead. !image-2!!image-3!\'"", ""Comment 36: \'I fix it"", ""Comment 37: You can test it again.\'"", \'Comment 38: ""I don\\\'t see it yet for starting the approval flow (screenshot 1)\', \'Comment 39: the first approval (screenshot 2) but I do for the last approval (screenshot 3). So if you can add those lists on screenshot 3 for phase 1 and 2 it will be perfect.!image-4!!image-5!!image-6!""\', \'Comment 40: ""[~SDriesen@deheus.com][~mbovene@deheus.com]In MAS NL sector when someone sent document to \\\'Waiting for approval\\\' state\', \'Comment 41: system everytime sent it to user from Document field \\\'Specialist\\\' or \\\'Sector lead\\\' (on screen below there are 3 flows with waiting for approval).It works from the beginning of the system like that.Please let us know that we indeed should change this flow/flows in MAS NL. Maybe you refer only to flow from \\\'Add/change conditions\\\' to \\\'Waiting for approval\\\' and here we should make changes and do it similar like for \\\'Add/change condition\\\' flow?!image-2023-03-27-11-35-55-947.png!""\', \'Comment 42: ""I think in MAS BE\', \'Comment 43: we select ourselves as specialist and sector lead when making the contract\', ""Comment 44: so we can approve it ourselves (you can\'t choose anyone else). Afterwards"", \'Comment 45: we add/change the conditions where we can send that task to ourselves\', \'Comment 46: and then we modify the sector lead and specialist to the correct persons\', \'Comment 47: because we ourselves can do the whole flow.""\', ""Comment 48: \'Damian"", \'Comment 49: to make it even more dynamic within De Heus they decided that the specialist and sector lead doesn\\\\\\\'t have to approve the contracts any more (at least in the Intense system).This means that the contract approval flow can be changed. The user must be able to manually select someone in the system to approve the contract. It can be reduced to one step (Draft - waiting for approval - approved --> active). It should not be send automatically to the persons that are set in Specialist and Sector lead fields.A similar process holds for the ""add/change conditions"" approval flow.Is this clear?\\\'\', ""Comment 50: \'Note: for all sectors.\'"", \'Comment 51: ""Does it means we don\\\'t need to use anymore approval flows in all sectors for Contract Farmer documents?How it is: # Regular process: Draft -> Waiting for approval -> Approved by specialist -> Active # Aadd/change conditions process: Active -> Add/change conditions -> Waiting for approval -> Approved by specialist -> Active (revised)To whom should be possible to sent document to Active? It should be users from role with this sector (all users from sector) or from other role/users?(Now when document is sent to Active is sent to user who create CF document).How it should be: # Regular process: Draft -> Active # Aadd/change conditions process: Active ->Add/change conditions -> Active (revised)To whom should be possible to sent document from Add/change conditions to Active? It should be users from role with this sector (all users from sector) or from other role/users?(Now when document is sent to Active is sent to user who create CF document).Could you confirm/add some remarks?""\', \'Comment 52: ""Does it means we don\\\'t need to use anymore approval flows in all sectors for Contract Farmer documents? --> NOBut now we have two steps: approved by specialst and approved by sector lead.The flow is guided automatically by the system.We would like to have one approval step\', \'Comment 53: and the user should be able to manually select the user to send the document to.""\', ""Comment 54: \'To whom should be possible to sent document from Add/change conditions to Active?  --> user should be able to select a collegue from their departmentIt should be users from role with this sector (all users from sector) or from other role/users? --> Contract administrator or Senior Contract administrator.\'"", \'Comment 55: ""Proces dla dokumentów CF we wszystkich sektorach powinien wyglądać tak:*Standardowy proces:*Draft -> Waiting for Approval -> ActivePrzy wysyłce do węzła \\\'Waiting for Approval\\\' powinno dać się wybrać jednego użytkownika\', \'Comment 56: do którego zostanie wysłany dokument - w zależności od sektora powinna tu być dostępna lista użytkowników\', ""Comment 57: którzy mają dostęp do danego sektora.Do dodania przepływ:Waiting for Approval -> Active*Proces ze zmianami w CF (Add/change conditions):*Active -> Add/change conditions -> Active (revised)Przy wysyłce z węzła\'Add/change conditions\' do\'Active (revised)\' powinna być dostępna lista użytkowników"", \'Comment 58: którzy są w rolachContract administrator i Senior Contract administrator.Do dodania przepływ:Add/change conditions -> Active (revised)------Pozostałe przepływy akceptacyjne\', \'Comment 59: które były do tej pory używane powinny być niedostępne.Należy pamiętać\', \'Comment 60: że jeżeli są dokumenty w węzłach biorących udział w starych procesach\', \'Comment 61: to należałoby zakończyć takie procesy zanim zmiana zostanie wprowadzona\', \'Comment 62: w innym wypadku może się okazać\', \'Comment 63: że niektórych dokumentów nie będzie się dało przeprocesować do końca.""\', ""Comment 64: \'Ok"", ""Comment 65: then processes will be: # Regular process:Draft -> Waiting for Approval -> Active # Add/change conditions process:Active -> Add/change conditions -> Active (revised)\'"", ""Comment 66: \'YES\'"", ""Comment 67: \'Created flows on the test environment according to guidelines\'"", ""Comment 68: \'I tested both and according to me both flows are good"", ""Comment 69: but maybe Mitch can have a look as well to confirm.\'"", \'Comment 70: \\\'Regular process (first picture): Draft -> Waiting for Approval -> ActiveThis works fine. However I am wondering why the approver needs to select another person in order to activate it. Will it be send to the inbox o the person in that selection?Add/change conditions process:Active -> Add/change conditions -> Active (revised)To whom is this contract send when I select ""Add/change conditions""? I cannot make any selection\', \'Comment 71: it is send according to the definition (second picture).  The same holds for the person who is receiving this contract in the status ""Add/change conditions"" state. I can\\\\\\\'t manually select who I would like to send this document to.!image-7!!image-8!\\\'\', \'Comment 72: \\\'Mitch,Regarding this: ""To whom is this contract send when I select ""Add/change conditions""? I cannot make any selection\', \'Comment 73: it is send according to the definition (second picture). The same holds for the person who is receiving this contract in the status ""Add/change conditions"" state. I can\\\\\\\'t manually select who I would like to send this document to."" --> In MAS BE\', ""Comment 74: I could select Koen or myself there.\'"", ""Comment 75: \'[~tomasz.zygon@kotrak.com]możesz to sprawdzić i odpowiedzieć na ostatnie komentarze?\'"", ""Comment 76: \'{quote}Regular process (first picture):Draft -> Waiting for Approval -> ActiveThis works fine. However I am wondering why the approver needs to select another person in order to activate it. Will it be send to the inbox o the person in that selection?{quote}Exactly"", \'Comment 77: document will be send to to inbox of user which you select (insted of user who created document).{quote}Mitch,Regarding this: ""To whom is this contract send when I select ""Add/change conditions""? I cannot make any selection\', \'Comment 78: it is send according to the definition (second picture). The same holds for the person who is receiving this contract in the status ""Add/change conditions"" state. I can\\\\\\\'t manually select who I would like to send this document to."" --> In MAS BE\', \'Comment 79: I could select Koen or myself there.{quote}Yes\', ""Comment 80: on test environment there is a list in each sector with users to whom will be sended document. Maybe you tried to do on Prod environment - it\\\\\'s not adjusted there yet.If process on test environment works properly we can move it to Production environment.Please confirm if we can move this to Prod.\'"", ""Comment 81: \'Hello Damian,I personally think it can be moved to PROD. For what I tested it"", ""Comment 82: it worked.\'"", ""Comment 83: \'Moved to production\'"", ""Comment 84: \'Can be closed\']""]\nRelated Issues:\n[]\n\n### End'}"
316,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8716\n\n### Instruction:\nBecause all items are send to all sectors right now (after the latest Intense update) we don\'t need the field ""Multisector"" anymore.\r\n\r\nCould this field be hidden?\n\n### Response:\n[""Comment 1: [\'!image-1!\'"", \'Comment 2: ""After change only Items sent from Milas with Item Group = \\\'Finish Product\\\' or \\\'Raw Materials\\\' are directly created as a Item Card and sent to all sectors\', \'Comment 3: but other items are sent as a New Item Card\', ""Comment 4: so I think this functionality with Multisector can be used for this cases when Item Group is different than\'Finish Product\' or \'Raw Materials\'.We can hide this if you\'re sure there won\'t be cases with items sent from Milas which are not needed to create in many sectors.For example there is some\'New Item Card\' in MAS NL sector right now on IBIP_DH and here are selected 5 sectors"", \'Comment 5: so it won\\\'t be possible in the future when we hide this option on New Item Card.Should we indeed hide this option from New Item Card?!image-2023-03-09-09-57-44-874.png!""\', \'Comment 6: ""You are right. For items that are not in the \\\'Finish Product\\\' or \\\'Raw Materials\\\' item groups we indeed need this functionality.It is an option to hide it when it is in the \\\'Finish Product\\\' or \\\'Raw Materials\\\' item groups?""\', ""Comment 7: \'Ok"", ""Comment 8: we will hide this fields as you wrote.\'"", ""Comment 9: \'Can be closed when this field is hidden.\'"", ""Comment 10: \'Can be closed\']""]\nRelated Issues:\n[]\n\n### End'}"
317,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8715\n\n### Instruction:\nWe have error in the VT-1342/23, item SUE1605-S25, we have reservation WD-919/3/23, we cancelled because quantity was wrong, but after cancel the item is reserved yet.\r\nCould you please remove reservation, it\'s urgent remove reservation, truck is waiting to load.\r\n\r\nThank you\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 2: ""HelloAs you can see by yourself in the query bellow\', \'Comment 3: we have around 50 UL with executed documents stuck on SU reservation:{noformat} SELECT \\\\tul.Barcode\', \'Comment 4: su.ReservedQuantityValue\', \'Comment 5: su.ReservedQuantityUnit\', \'Comment 6: su.ReservationSourceDocumentNumbers\', \'Comment 7: wd.Status  FROM DHPlantWmsBusinessLogicMain.dbo.UnitLoads ul \\\\tINNER JOIN DHPlantWmsBusinessLogicMain.dbo.StockUnits su ON su.UnitLoadId = ul.Id  \\\\tINNER JOIN DHPlantWmsBusinessLogicMain.dbo.WarehouseDispatches wd ON wd.Document = REPLACE(TRIM(su.ReservationSourceDocumentNumbers)\', ""Comment 8: \';\'"", \'Comment 9: \\\'\\\')WHERE su.ReservationSourceDocumentNumbers LIKE \\\'%WD%\\\'{noformat}Could you please fix that?Thank you""\', ""Comment 10: \'Hello"", \'Comment 11: only WD-886/3/23 has status=60.I corrected this one.For the rest\', ""Comment 12: the documents are still in progress:WO(PD)-98/3/23,WO(PD)-156/3/23.Please check after completion.\'"", \'Comment 13: ""{code:java}declare @barcode nvarchar(max) = \\\'89-W0088A\\\'delete sr--select  *from dbo.StockUnits sinner join dbo.StockUnitReservations sr on sr.Id = s.Idwhere s.Barcode = @barcodeupdate dbo.StockUNITSSET QuantityOnhand = Quantitywhere barcode = @barcodeupdate suset su.QuantityOnHandValue=880,su.ReservedQuantityValue=0,su.ReservationSourceDocumentNumbers=\\\'\\\' --select su.QuantityOnHandValue,su.ReservedQuantityValue,su.ReservationSourceDocumentNumbers,*  FROM [DHPlantWmsBusinessLogicMain].[dbo].[UnitLoads] ul  inner join [DHPlantWmsBusinessLogicMain].dbo.StockUnits su on ul.id=su.UnitLoadId  where ul.Barcode=@barcode{code}""\', \'Comment 14: ""Analizując ostatni przykład to w stock dla tego stockunit jest rezerwacja jako ostatnia{code:java}SELECT       [Event],[StoredAt]      ,[EventType]         ,[UserName]      ,[CorrelationId]      ,[CreatedAt]      ,[SentAt]  FROM [DHPlantStockBusinessLogicEvents].[dbo].[StockUnits]  where AggregateId=\\\'4FFA1A0F-15C4-4BF9-90B3-C5F3B9C3DB9A\\\'  order by StoredAt asc{code} !screenshot-2! Sprawdzając WD i anulację - operator rozpoczął dopiero po 18:10\', \'Comment 15: gdzie w stocku nie ma tego ujętego(to wyżej).{code:java}SELECT         [Event]\', \'Comment 16: [StoredAt]      ,[EventType]         ,[UserName]  FROM [DHPlantWmsBusinessLogicEvents].[dbo].[WarehouseDispatches]  where AggregateId=\\\'D7B488EF-C05E-4B9E-A194-9EC2CCD25CA9\\\'    order by StoredAt asc{code} !screenshot-3! ""\', ""Comment 17: \'zgodnie z rozmową "", ""Comment 18: dzięki.\'"", ""Comment 19: \'Sytuacja analogiczna do przypadku zgłoszonego w DGS-8450: https://helpdesk.kotrak.com/browse/DGS-8450?focusedCommentId=1098904&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-1098904Problem zostanie rozwiązany na  *GDC-849* ( obsługi konkurencyjności).*89-W0088A:* O 2023-03-07 17:57:29.3778171 WarehouseDispatchSubElementCreatedEvent -> 89-W0088A został zarezerwowany i zarejestrowany na WO(PD): dbo.WarehouseDispatchSubElements -> Element 2"", \'Comment 20: Subelement 540ms później o 2023-03-07 17:57:29.7504353 mamy kolejny event WarehouseDispatchSubElementCreatedEvent na ten sam WD element i subelement\', \'Comment 21: ale z kodem 89-W0086R. Kod zostaje zapisany w tabeli WarehouseDispatchSubElements ( Element 2\', \'Comment 22: Subelement 5)\', \'Comment 23: nadpisując 89-W0088A.Użytkownik usuwa dokument WD. Wszystkie rezerwacje zostały usunięte\', ""Comment 24: oprócz 89-W0088A - bo tego kod został nadpisany i nie ma na WD.!89-W0088A_WD element!!89-W0088A_created!\'"", ""Comment 25: \'The issue will be resolved in the GDC-849 (competitive handling).89-W0088A:At 2023-03-07 17:57:29.3778171 has been reserved and registered on WO(PD).40ms later at 2023-03-07 17:57:29.7504353 we have another WarehouseDispatchSubElementCreatedEvent event for the same WD element and subelement"", \'Comment 26: but with code 89-W0086R.The user deletes the WD document. All reservations have been deleted\', ""Comment 27: except for 89-W0088A - because this code has been overwritten and is not on WD.\'"", ""Comment 28: \'Ok"", ""Comment 29: we are waiting new version.\'"", ""Comment 30: \'This ticket has been closed.\']""]\nRelated Issues:\n[\'DGS-8712\', \'DGS-8450\', \'DGS-8792\', \'DAP-13479\', \'DGS-8640\', \'DGS-8646\', \'DGS-8785\']\n\n### End'}"
318,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8714\n\n### Instruction:\nWe would like to add a button and 8 fields on the Feed tab in the round. These 8 fields are related to ""Beginvoorraad"" and ""Eindvoorraad"". \r\n\r\nWe need two  fields per round for each of these (see mockup):\r\no\tBeginvoorraad voer\r\no\tBeginvoorraad tarwe\r\no\tEindvoorraad voer (weights should always be negative)\r\no\tEindvoorraad tarwe (weights should always be negative)\r\n\r\nOn the PDF in the Financial Statement, the 4 completed fields must be put in the right place. When this is done the current calculations that are done can still be made.\r\n\r\nPlease note: these lines may not come back to S2P, they are purely for registration purposes.\n\n### Response:\n[""Comment 1: [\'!image-1!!image-2!\'"", \'Comment 2: ""We can add these 8 fields and like it is on example we should take in the same way these values which are now displayed on FS new printout right?It should works like if somene will use button\', \'Comment 3: system will calculate values from Feed sale document based on BV\', ""Comment 4: EV columns and update these 8 new fields on round? Should these fields be not editable for users?Other option is to calculate these values automatically on document - it will be dynamic text instead of field in database and user don\'t need to use button everytime when values on feed sale will change (new lines will be marked as BV or EBV)- like for example this one!image-2023-03-09-11-03-34-163.png!How should be displayed in new fields on round values:{quote}Eindvoorraad voer (weights should always be negative)Eindvoorraad tarwe (weights should always be negative){quote}It doesn\'t matter what sign is on Feed sale line (negative or positive) and it should be always displayed as a negative values?What about the Net Value for \'Eindvoorraad voer\'"", ""Comment 5: \'Eindvoorraad tarwe\' - these values should be also always displayed as a negative values?Like it\'s on some example below on database there are values on Feed sale with negative values (but it could happen that this will be also positive)"", ""Comment 6: so that\'s why I\'m asking.To be sure - we distinguish values for Feed and Wheat (tarwe) on printout by the Item Group on Item Card"", ""Comment 7: so it means: * if Item has Item Group = \'Finished prodcut\' it\'s displayed as a \'Feed\' * if Item has Item Group = \'Raw Materials\' it\'s displayed as a \'Tarwe\'Is it a good approach and we need to calculate also values for this fields like on FS new printout"", \'Comment 8: right?!image-2023-03-09-10-42-51-867.png!""\', \'Comment 9: ""After our meeting there is a way how it should works:8 fields on Round should be added and should be editable\', \'Comment 10: users will manually add there values:For these 4 fields should be validation and users should be able to add only *positive* values: * BV feed Weight\', \'Comment 11: * BV feed Net Value\', \'Comment 12: * BV wheat Weight\', \'Comment 13: * BV wheat Net Value.For these 4 fields should be validation and users should be able to add only *negative* values: * EV feed Weight\', \'Comment 14: * EV feed Net Value\', \'Comment 15: * EV wheat Weight\', \'Comment 16: * EV wheat Net Value.These fields should be copied from old round to new round (when it is created) - *EV* values from old round should be copied to *BV* values for new round with opposite signs:||Round 1||Round 2|||*EV* feed Weight = -100|*BV* feed Weight = 100||*EV* feed Net Value = -3000|*BV* feed Net Value =3000||*EV* wheat Weight = -50|*BV* wheat Weight = 50||*EV* wheat Net Value = -1500|*BV* wheat Net Value = 1500|All values from this fields should be included in: * FS printout (new) - values should be retrieved straightly from these 8 fields to sections \\\'Beginvoorrad\\\' and \\\'Eindvoorrad\\\' on printout and should be also calculated in subtotal/totals. This values will be filled in only on Round document and it won\\\'t be included on Feed sale document.Values from Feed sales lines will be presented only in section \\\'Voerleveringen\\\' on printout.!image-2023-03-09-12-58-08-594.png! * Technical results - values from these 8 fields should be included in technical results calculations (e.g.Total weight Feed (in kg),Total value Feed) - to analyse which calculations should include also these values.""\', ""Comment 17: \'You are totally right.\'"", ""Comment 18: \'What is the status?\'"", \'Comment 19: ""It\\\'s related also to other tasks and it\\\'s needed to analyse and discuss to do it properly:[https://helpdesk.kotrak.com/servicedesk/customer/portal/56/DGS-8675][https://helpdesk.kotrak.com/servicedesk/customer/portal/56/DGS-8732]""\', \'Comment 20: ""[~mbovene@deheus.com]I have a question about including these new 8 fields to some calculations.We only need to include these values to technical results calculations\', ""Comment 21: right?I\'m asking because one of parameters from technical results \'Saldo per m2\' based on Saldo from Financial statement"", \'Comment 22: so this value shouldn\\\'t change?!image-2023-04-18-14-22-35-768.png!""\', ""Comment 23: \'The Saldo should change when we have BV (begin stock) or EV (end stock). These will change the feed costs for a specifc round"", \'Comment 24: so it will affect the saldo.So as a result the ""Saldo per m2"" should also change.\\\'\', ""Comment 25: \'[~grzegorz.materla@kotrak.com]możesz poprawić nowy wydruk FS"", ""Comment 26: póki co dla MAS NL.Nowe 8 pól powinno być wyświetlanych wprost z dokumentu Rundy zamiast pobierane z Feed sale.Przykładowy dokument na na IBIP_DH_TEST:FS77901Runda30400\'"", \'Comment 27: ""[~mbovene@deheus.com]but issue is that calculation of \\\'Saldo\\\' field on FS is based on Gross values from invoices and feed sales.On Round we have Net Values of BV and EV\', \'Comment 28: so should we include these net values to gross values from Saldo?We don\\\'t have any information about Gross Value of BV and EV!image-2023-04-19-13-08-40-729.png!!image-2023-04-19-13-07-28-053.png!""\', ""Comment 29: \'zmieniona proceduraKR_calculatetechresults"", ""Comment 30: funkcjaKR_FinancialStatementSaldo oraz nowy wydruk FS (Financial Statement 2) na IBIP_DH_TEST\'"", \'Comment 31: ""It\\\'s ready to test on Test environment in MAS NL sector.Values from new 8 fields will be on printout and will be included in calculations of technical results.These changes (after filled in these new 8 fields for BV and EV on Round) in technical results calculation will have impact on these parameters:|Total weight Feed (in kg)||Total value Feed||Feed conversion netto||Feed conversion 1.500 gram||Feed profit per broiler||Average price feed per 100 kg||Feedcost / kg. broilers bruto 1500 gr||Feedcost / kg. broilers netto||Feedcost / kg. broilers netto||Feed use per delivered broiler per gram per day||Percentage Wheat||Saldo per m2||Saldo / m2 / day||Feed Profit / m2 / day||Percentage Corn||Feed profit|For Financial Statement saldo there is also change of calculating - now there will be calculated net values from invoices and feed sales instead of gross values as it was before. (for now in MAS NL)!image-2023-04-19-15-34-35-707.png!""\', ""Comment 32: \'Move to PROD\'"", ""Comment 33: \'{color:black}Hello{color} {color:black}{color} {color:black}Is this already set to the PROD{color} {color:black}We can’t see this{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} Koen{color} |{color:#000001} {color} |{color:#000001} Huibers{color} |  {color:#000001}+31318675600{color} | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.de-heus.nl/]>{color} | |  *{color:#006FB7} *DEHEUSVOEDERSB.V.‑LOCATIEHELMOND*{color}* | | | |{color:#000001} Gerstdijk12 \\\\u200b5704RGHelmond{color} | | |{color:#000001} M:{color}{color:#000001}{color}{color:#000001}+32-11-546672{color}{color:#000001} <tel:+32%20-%2011%20-%2054%2066%2072>{color} |  {color:#000001}KvK14626985{color}   _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | | !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | | !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} | | !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} |        *Van:* Mitch van Bovene (Jira) <jira@kotrak.com>   *Verzonden:* donderdag 20 april 2023 14:32  *Aan:* Huibers"", ""Comment 34: Koen <khuibers@deheus.com>  *Onderwerp:* DGS-8714 Add button for BV & EV on round   \'"", \'Comment 35: ""Hello,We\\\'re moving it right now on PROD enviroment for *MAS NL*\', \'Comment 36: I\\\'ll let you know when it will be moved.For *MAS BE* we\\\'re making changes and it should be ready today to test on TEST environment. I\\\'ll let you know.""\', \'Comment 37: ""*MAS NL*Changes have been moved to Production environment.*MAS BE*It\\\'s ready to test on Test environment in MAS BL sector.Values from new 8 fields will be on printout and will be included in calculations of technical results.These changes (after filled in these new 8 fields for BV and EV on Round) in technical results calculation will have impact on these parameters:|Total weight Feed (in kg)||Total value Feed||Feed conversion netto||Feed conversion 1.500 gram||Feed profit per broiler||Average price feed per 100 kg||Feedcost / kg. broilers bruto 1500 gr||Feedcost / kg. broilers netto||Feedcost / kg. broilers netto||Feed use per delivered broiler per gram per day||Percentage Wheat||Saldo per m2||Saldo / m2 / day||Feed Profit / m2 / day||Percentage Corn||Feed profit|For Financial Statement saldo there is also change of calculating - now there will be calculated net values from invoices and feed sales instead of gross values as it was before. (for now in MAS BE)""\', ""Comment 38: \'[15:59] Driesens"", \'Comment 39: SteffenBV/EV fields and calculations in MAS BE test works\', ""Comment 40: so may be moved to PROD\'"", ""Comment 41: \'[~grzegorz.materla@kotrak.com]przeniesiesz na prod to dla MAS BE?\'"", \'Comment 42: ""Hi,we\\\'ve moved all functionality for MAS BE to PROD Intense environment. You can feel free to test it.Best regards\', \'Comment 43: Grzegorz""\', ""Comment 44: \'Zmiany dokonane zostały dla: - dokumentu Roundy"", \'Comment 45: dodanie pól na formularzu\', \'Comment 46: - zmiany procedury wydruku FS new\', \'Comment 47: - zmiany procedury saldo na FS\', ""Comment 48: - zmiany procedury kalkulacji FS.\']""]\nRelated Issues:\n[\'DGS-8215\', \'DGS-8732\', \'DGS-8877\', \'DGS-8994\']\n\n### End'}"
319,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8713\n\n### Instruction:\nThe codes below do not appear in DHC when exported from DHH:\xa0\r\n\r\n7900.0025 (new code)\r\n6700NM.025EN (new code)\r\n6900.025EN (12th version)\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\', \'Comment 3: I\\\'m using Kotrak1 account and I do not have an access to UAAPP03 (10.106.25.38) server!image-2023-03-08-16-41-19-769.png!I can only login intoUADB03 (10.106.25.32)and I see only test databases!image-2023-03-08-16-42-28-051.png!I can not open DHP as well!image-2023-03-08-16-44-42-122.png!To verify this issue I need access to DHC (App and Database) and DHP (App and DB).Please check.""\', ""Comment 4: \'Marta moved everything to other new working servers"", ""Comment 5: this was still at the beginning of January:DHP database - UADB02 10.106.25.31DHP application - UAAPP02 10.106.25.37 http://10.106.25.37/#/loginDHC database - UADB01 10.106.25.30DHC application - UAAPP01 10.106.25.36\'"", ""Comment 6: \'konfiguracja w dhh wydaje się być poprawna !image-2023-03-08-19-07-27-412.png!w logach synchronizacji dhc czystow logach BP brak komunikatów dot itemchange w kontekście badnych towarówponowne wysłanie itemów z dhh nic nie dajew logach z GatewayPlugin (C:\\\\\\\\Kotrak\\\\\\\\GatewayPlugin_Ukraine) jest komunikat błędu !image-2023-03-08-19-37-57-612.png! kolejka ma około 4600 messagyPo restarcie powoli schodzi\'"", ""Comment 7: \'Synchronization between DHP and DHP has hanged. It has been restarted. There is more then 4500 messages waiting to be synchronized. Items should be available when queue will end proceed.\'"", ""Comment 8: \'DHP and DHP ? What did you restart? Why did this happen?\'"", ""Comment 9: \'!image-2023-03-09-08-18-21-439.png!\'"", ""Comment 10: \'!image-2023-03-09-08-32-16-760.png!\'"", ""Comment 11: \'zrestartwana usluga ukraine.gatawey powoli skapuje\'"", ""Comment 12: \'It seemd that another queue - Ukraine.gateway -was hanged I restarted it and slowly messages are being synchrnized!image-2023-03-09-08-38-38-037.png!\'"", ""Comment 13: \'We are still waiting for Ukraine.gateway plugin queue to finish. Rest of Ukraine queues in DHH are done.!image-2023-03-09-19-10-36-156.png!\'"", ""Comment 14: \'How long does it take for this process to be completed?And what was the reason?\'"", ""Comment 15: \'Nadal na kolejka jest ok 3 tysiecu meassage ( 2960) ostatnie Recipe były importowane 05.03!image-2023-03-10-08-48-07-725.png|width=619,height=168!!image-2023-03-10-08-59-42-188.png!pingowanie z teraz sa timeouty na łączeniu z serwerem\'"", ""Comment 16: \'DHH gateway was configured for communication with both systems: production and test.Test system is not responding. Every message from DHH was waiting for response from test system for 30 seconds. We have disabled communiacation to test system in order to optymize synchronization between DHH and production DHC system.Items should be avaible in DHC. Please check.\'"", ""Comment 17: \'yes"", \'Comment 18: we checked and it looks like everything is fine\', ""Comment 19: Items now be available in DHC\'"", ""Comment 20: \'Could you please confirm if we can close this task?Regards\'"", ""Comment 21: \'yes"", ""Comment 22: you can close it task\']""]\nRelated Issues:\n[]\n\n### End'}"
320,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8712\n\n### Instruction:\nWe have error in the VT-1342/23, item SUE1605-S25, we have reservation WD-919/3/23, we cancelled because quantity was wrong, but after cancel the item is reserved yet.\r\nCould you please remove reservation, it\'s urgent remove reservation, truck is waiting to load.\r\n\r\nThank you\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 2: "" !screenshot-1! {code:java}declare @barcode nvarchar(max) = \\\'89-W00AZT\\\'delete srfrom dbo.StockUnits sinner join dbo.StockUnitReservations sr on sr.Id = s.Idwhere s.Barcode = @barcodeupdate dbo.StockUNITSSET QuantityOnhand = Quantitywhere barcode = @barcodeupdate suset su.QuantityOnHandValue=1000,su.ReservedQuantityValue=0,su.ReservationSourceDocumentNumbers=\\\'\\\'  FROM [DHPlantWmsBusinessLogicMain].[dbo].[UnitLoads] ul  inner join [DHPlantWmsBusinessLogicMain].dbo.StockUnits su on ul.id=su.UnitLoadId  where ul.Barcode in(\\\'89-W00AZT\\\')   i dla stocka w pcs.{code}""\', ""Comment 3: \'Stock unit has been corrected"", ""Comment 4: please check and send a feedback.\'"", ""Comment 5: \'I checked and now is correct. Do you know why we have this error? Thank you.\'"", ""Comment 6: \'DGS-8715 RCA has been created - further analysis will be on this task.Can we close this one?\'"", ""Comment 7: \'Hi PiotrI just inserted a comment on DGS-8715Can you check it please?Thank you\'"", ""Comment 8: \'Hello ,The other examples you arę mentioned on RCA task id IT a P1 issue now?Could we close this task or power its priority?\'"", ""Comment 9: \'Hello,you can close. Thank you.\']""]\nRelated Issues:\n[\'DGS-8715\']\n\n### End'}"
321,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8711\n\n### Instruction:\nDears,\r\n\r\nVT-135/3/23 is in DHP and not in DHC and ERP.\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: \'vte o tym numerze jest 3 razy 2 razy w statusie 1 brak elementów!image-2023-03-08-13-34-17-463.png!\'"", ""Comment 3: \'!image-2023-03-08-13-36-56-253.png!\'"", ""Comment 4: \'SELECT TOP (1000) [PlantId] ,[PlantIdNo] ,[LongId] ,[StringId] ,[GuidId] FROM [DHPlantIntegrationDhcServiceIdentityMapping].[dbo].[VehicleTicketIdentityMappings] where longid=108821\'"", \'Comment 5: ""@ widać tu nadamirowe wpisy 3 razy wszedł ten sam vt ale 2 razy niekompletnie\', \'Comment 6: jest ten sam externalid 3 razy pytanie czy powywalac te wpisy na których brak info o wadze itd ?dla tego id zrobiła update status na 1 z 2\', \'Comment 7: expected quantity z 0 na 1 ake pomimo puszcza wiaodmości rabitem nic sie nie pojawia na elementach.\', \'Comment 8: logów brakpodejrzewam że to że są 3 vt o tym samym externalid jets tu problememid VT w dhc na którym robiłam updaty=\\\'0391AF3B-2FA7-48F1-9A04-BCC227396EFC\\\'""\', ""Comment 9: \'!image-2023-03-08-15-04-55-590.png!\'"", ""Comment 10: \'Please verify it was renchronized to DHC.!image-2023-03-08-15-20-23-803.png!\'"", ""Comment 11: \'yes"", ""Comment 12: thanks!\']""]\nRelated Issues:\n[]\n\n### End'}"
322,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8710\n\n### Instruction:\nHi, task from Wiola:\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'[^limit_urlopowy_KAJDAS.docx]\'"", ""Comment 4: \'Explanations in the attachment[^limit_urlopowy_KAJDAS.docx]\'"", ""Comment 5: \'!image-1!\']""]\nRelated Issues:\n[]\n\n### End'}"
323,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8709\n\n### Instruction:\nBoth item variants and both recipes 302291 in DHC don\'t appear in DHP Nijkerk.\r\n\r\nIn DHC everything looks good.\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Dear Rob,Below is the list of items that should be resynced to DHC Service. Should I process them all?302291130170149999112122149998\'"", ""Comment 3: \'302291 is resynced and is in plant now.!image-2023-03-08-10-55-07-630.png!\'"", ""Comment 4: \'Thanks Aleksandra"", ""Comment 5: please process all of the items to sync. After that the ticket can be closed.Regards,Rob.\'"", ""Comment 6: \'Dear Rob,Helmond:!image-2023-03-08-11-17-29-220.png!Maasbracht:!image-2023-03-08-11-18-37-250.png!Recipe 149998 and 149999 are for plant Balgoji which is not supported by Kotrak. I have resynced them in DHC"", ""Comment 7: they are in DHC Service now.!image-2023-03-08-11-23-29-433.png!Regards\'"", ""Comment 8: \'Zrobiłam jeszcze restart BP"", ""Comment 9: bo cosik się przytykało znowu!image-2023-03-08-11-33-36-722.png!\'"", ""Comment 10: \'I can see the Balgoij items/recipes are picked up by WebMethods.Thanks for your support"", ""Comment 11: the ticket can be closed.Regards,Rob.\']""]\nRelated Issues:\n[]\n\n### End'}"
324,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8708\n\n### Instruction:\nOrders do not arrive in DHP Maasbracht anymore: examples:\r\nSOBE000016241\r\nSOBE000016242\r\n\r\nAlso shipping notices related to these orders do not arrive\r\nForeignNumber: L000150977\r\n\r\nCan you please check. They need to be loaded tomorrow morning first trip, so they must be in the plant before 22:00 tonight.\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: \'Both orders are avaible in DHP!image-2023-03-07-19-28-43-556.png!as well as SN!image-2023-03-07-19-31-47-963.png!Please check\'"", ""Comment 3: \'Yup"", ""Comment 4: they did arrive. The processing of messages in the DHC Queue was very slow.But you can close this ticket\']""]\nRelated Issues:\n[]\n\n### End'}"
325,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8707\n\n### Instruction:\nI tried to create opening balance for Andel_mest, but the process hangs in status processing: What is going wrong?\r\n\r\nAlternatively I can create stock on Andel-West and split it to Andel-Mest but in 8.5 I don\'t have this option?\n\n### Response:\n[""Comment 1: [\'!afbeelding!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'!image-2023-03-07-15-49-22-969.png!\'"", ""Comment 4: \'System.FormatException: Index (zero based) must be greater than or equal to zero and less than the size of the argument list.\'"", ""Comment 5: \'Could you please provide file you are using for OB?\'"", ""Comment 6: \'see attached[^Andel.xlsx] _(12 kB)_\'"", ""Comment 7: \'[~aleksandra.masternak@kotrak.com]hej Maciej mówił żebyś pomogła spojrzeć na ten plik"", \'Comment 8: co podeslał Thomas\', ""Comment 9: bo prawdopodobnie z nim jest problem\'"", ""Comment 10: \'[~agnieszka.januszewska@kotrak.com] W pliku załączonym przez Thomasa LocationCode jest lokalizacją należącą do Andel-Mest"", \'Comment 11: natomiast wpisany OwnerName i BusinessUnitName to Andel-West. Jeśli chce zrobić OB dla Andel-Mest\', \'Comment 12: to musi zmienić OwnerName i BusinessUnitName na ""098   Andel (fertilizer) NL"".!OB_2bu\\\\\\\'! !BU_location!\\\'\', \'Comment 13: ""any update\', \'Comment 14: it\\\'s causing delays now because orders cannot be finished""\', ""Comment 15: \'[~TDankers@deheus.com]Hello,in your OB file"", \'Comment 16: the entered location is from Andel-Mest but owner and BU is from Andel-West. !BU_location! Please change the OwnerName i BusinessUnitName to ""098   Andel (fertilizer) NL"" and it should work: [^Andel_98-1.xlsx]\\\'\', \'Comment 17: ""Thanks! this works\', \'Comment 18: I tried that combination before but I think I mist a space or sometinh in the BU name. anywhay\', ""Comment 19: it\'s solved. Additional question: why can\'t I move/split stock from andel-Mest to Andel-West or vice versa? For bulk this option is available"", \'Comment 20: for packed goods not""\', ""Comment 21: \'Fast movement and split of packed UL is available on the unit loads list in the WMS module. !screenshot-1! \'"", ""Comment 22: \'May we close the task?\'"", ""Comment 23: \'If I try to split I cannot select location Andel-MEst"", \'Comment 24: when I try Fast movement I get below error\', ""Comment 25: do we miss configuration again?!afbeelding-1!\'"", ""Comment 26: \'[~TDankers@deheus.com]Hi"", ""Comment 27: I added missing configuration for the 2nd BU. It should be possible now. !WMS_transfer location! \'"", ""Comment 28: \'It is all working now> May we close this task?\'"", \'Comment 29: ""It\\\'s oke now\', \'Comment 30: thanks""]\']\nRelated Issues:\n[]\n\n### End'}"
326,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8706\n\n### Instruction:\nHi\r\n\r\nWe created the VT-1320/23 we weighted the truck, however when Releasing for dispatch system shows an error message: *An unexpected error occurred. Please contact system help desk.*\r\n\r\nOne particular thing that happened with this VT is that when creating, the operator wrongly selected the Paking type = Bulk, but the item is packed. Then the operator detached the bulk item from VT and inserted it again as packed.\r\n\r\nCould you please help us?\r\n\r\nThe truck is waiting to load the items, but without releasing we can\'t open WO on mobile.\r\n\r\nThank you\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'We have the same error when we click in release for intake!image-1!\'"", ""Comment 4: \'od 2.marca nie loguje w module VC !screenshot-1! \'"", ""Comment 5: \'prośba o pomoc w ustaleniu przyczyny błędu"", ""Comment 6: np.w logach z VC nie loguje nic od 2.marca(mimo wywołania błędu).\'"", ""Comment 7: \'Guys"", ""Comment 8: any news?We have another VT intake VT-1366/23 with error to Complete the VTCould you please check?\'"", ""Comment 9: \'[~piotr.gaczorek@kotrak.com] Macka już nie ma w biurze. Nie pomoże nam dzisiaj\'"", ""Comment 10: \'[~piotr.gaczorek@kotrak.com] niech wystawią może nowe VT. Logami się Maciek jutro zajmie\'"", ""Comment 11: \'Analysis of this situation will take some time. An an workaround please generate new VT document.\'"", ""Comment 12: \'Hi BartłomiejThank you for your feedback!We created a new VT document and this new one worked perfect fine.But we need to find the reason why this VT-1320 crashed.Thank you\'"", ""Comment 13: \'Can we lower this issue priority to P2 then.\'"", ""Comment 14: \'Yes! You can\'"", ""Comment 15: \'[~mberbert@deheus.com] for this VT Arrival date is null.DHITS-721!image-2023-03-08-13-01-33-048!!image-2023-03-08-13-02-49-019!In this task we have 2 cases: 1) VT-1320 created status => DHITS-721 (DAP - update available in 8.6) ; 2) VT-1366 in progress status => we will check in DAP projectFor VT-1366 we have several users who worked on this document:* user tgrassi started to work on this document* next user isantos worked on this document!image-2023-03-08-15-49-25-930!* and when user isantos finished with this document"", \'Comment 16: after that user tgrassi finished too!image-2023-03-08-15-53-33-991!* as you know this the diff between 3.0 and 2.5 ; in 2.5 you had a sessionId on documents. Now\', \'Comment 17: you have web applications\', ""Comment 18: and several users can work on the same document in the same time (edit) \'"", ""Comment 19: \'[~piotr.gaczorek@kotrak.com] jeśli chodzi o brak logów to jest to związane z tym"", \'Comment 20: że w tasku DGS-8678 usunęli grupę users\', \'Comment 21: która miała dostęp do folderu IIS. Grupę tą potem dodaliśmy. Natomiast nie miała ona specjalnych uprawnień. Podczas instalacji i konfiguracji\', \'Comment 22: podczas uruchomienia IIS zostają dodane wszystkie potrzebne uprawnienia. Natomiast podczas ręcznego dodanie tej grupy\', ""Comment 23: uprawnienia specjalne nie zostały dodane (nie mamy takiej możliwości z UI). Stąd [~maciej.buchacz@kotrak.com] jutro rano doda te uprawnienia skryptem.\'"", \'Comment 24: ""Hi [~marcin.kleszcz@kotrak.com]That\\\'s weird because when you enter the VT document you can find the Arrival date in there!image-2!!image-3!""\', ""Comment 25: \'PLUS: What do we need to do to fix?We created new VT documento for VT-1320"", \'Comment 26: so it will be canceledBut for VT-1366 we are still waiting to complete\', ""Comment 27: PLRs is waiting to consume this SUCould you please fix that?thank you\'"", ""Comment 28: \'Hi"", ""Comment 29: date that is missing !screenshot-2! Corrected from ArrivalWeighingDate.\'"", \'Comment 30: ""[~mberbert@deheus.com] you are right\', \'Comment 31: you have ArrivalWeighingDate\', \'Comment 32: but you don\\\'t have ArrivalDate. ""\', ""Comment 33: \'[~piotr.gaczorek@kotrak.com]dzisiaj [~maciej.buchacz@kotrak.com] dodał odpowiednie uprawnienia do folderów dhp dla IIS. Restart IIS został dzisiaj rano po godz. 7 naszego czasu wykonany. Pliki logs tworzą się per moduł.\'"", ""Comment 34: \'Hello guysNow VT is closed!Thank you very much!You can close this task\'"", ""Comment 35: \'[~mberbert@deheus.com] fix will be available in 8.6.\']""]\nRelated Issues:\n[\'DGS-8678\', \'DAP-13410\']\n\n### End'}"
327,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8705\n\n### Instruction:\nMitch told us that in the upcoming days the functionality of automatically closing rounds, feed sales and financial statements once the saldo 2 pay is closed, will be introduced in PROD. In MAS BE, we do have most S2P\'s closed, but not every round+feed sale linked to this S2P and and no FS yet. Could you let all rounds, feed sales and financial statements (= all linked documents to these rounds) close for the S2P\'s that are archived yet?\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 Steffen,Indeed we will move soon to prod environment these changes - If the user sends S2P to Archive via flow\', \'Comment 3: others documents such as FS\', \'Comment 4: Round and Feed sale will also be in Archived status.We can prepare action to closing Financial Statement\', \'Comment 5: Round and Feed sale for Archived S2P documents.Should we sent all these documents for already Archived S2P\\\'s in MAS BE?@MitchShould we also sent these documents also in other sectors like in MAS BE?Regards""\', ""Comment 6: \'Should we also sent these documents also in other sectors like in MAS BE? --> yes please do it as well for MAS NL. \'"", ""Comment 7: \'Hi [~mbovene@deheus.com],the functionality of automatically closing Rounds"", \'Comment 8: Feed sales and Financial Statements for Saldo to pay has been moved into prod Intense environment.Also\', ""Comment 9: we\\\\\'ve cloned this functionality for all sectors in test Intense environment. You can verify it.Now"", \'Comment 10: we are focusing on second part of task - closing documents related to Saldo to pay document in ""Archived"" status.Best regards,Grzegorz\\\'\', \'Comment 11: ""Does the FS not archive automatically when S2P is archived? It seems to be an approval flow but can\\\'t it be a direct archive like the S2P?""\', \'Comment 12: ""And the same for Feed sales? The round was closed automatically\', \'Comment 13: but the feed sale (and financial statement) wasn\\\'t.""\', ""Comment 14: \'The FS and Feed sales should indeed be automatically closed as well.\'"", \'Comment 15: ""[~SDriesen@deheus.com],we\\\'ve missed new flows in process definition for Financial Statement. Right now\', \'Comment 16: everything is correctly. So you can try it again.Best regards,Grzegorz""\', ""Comment 17: \'Hello Grzegorz,This seems indeed to be working now.\'"", ""Comment 18: \'Przygotowane zapytania pod archiwizację dokumentów związanych niezarchiwizowanych.Do archiwizacji dokumenty historyczne.\'"", ""Comment 19: \'Is this fixed right now?\'"", \'Comment 20: ""On production environment right now is implemented this solution: If the user sends S2P to Archive via flow\', \'Comment 21: others documents such as FS\', \'Comment 22: Round and Feed sale will also be in Archived status.It\\\'s implemented in MAS NL and MAS BE sectors only as it was set before.The only thing left in this topic is to archive historical documents. We\\\'re working on it and we\\\'ll inform in task when it will be ready.When it will be done I think we can close this task and also linked to it https://helpdesk.kotrak.com/browse/DHNLC-1147""\', ""Comment 23: \'Wszystkie FS spięte z archiwalnymi S2P zostały przesłane do Archiwum.Do przesłania pozostały Roundy.\'"", \'Comment 24: ""All Financial statements in MAS NL and MAS BE right now have been sent to Archive when linked S2P have been sent to Archive.Only Round documents and Feed sale left and will be sent to Archive. We\\\'ll inform you when it\\\'s done.""\', ""Comment 25: \'Do wrzucenia selecty dla rundy i FS"", ""Comment 26: które służą do przesyłania dokumentów do archiwum.\'"", ""Comment 27: \'[^DGS-8705_SelectDataForAutomaticFlow(S2P,FS,Rounds).txt]\']""]\nRelated Issues:\n[\'DGS-8897\']\n\n### End'}"
328,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8704\n\n### Instruction:\nThe item 22064, lot number WI-88/1/23-1 is with reservation of production 0871260123017, but the production is already confirmed. Could you check why reservation didn\'t disappear?\r\n\r\nthank you\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 3: ""{code:java}update suset su.ReservationSourceDocumentNumbers=\\\'\\\'  FROM [DHPlantWmsBusinessLogicMain].[dbo].[UnitLoads] ul  inner join [DHPlantWmsBusinessLogicMain].dbo.StockUnits su on ul.id=su.UnitLoadId  where ul.Barcode in(\\\'87-W0020R\\\'){code}""\', ""Comment 4: \'Hello. Data has been corrected.According to  RCA DGS-8168 PLR reservations have been corrected for version 8.5\'"", ""Comment 5: \'Hello Piotr,Ok"", ""Comment 6: you can close this task. Thank you.\']""]\nRelated Issues:\n[]\n\n### End'}"
329,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8703\n\n### Instruction:\nHello,\r\n\r\nthese orders are not in VC-Module, but also I cannot find anything in the error log, so I\'m not sure whats going on and what needs to be done to fix this, please check\n\n### Response:\n[""Comment 1: [\'ogólnie nie było errów"", \'Comment 2: logi czyste po pownownej wysyłce do MAssbracht jeden wisiał był errorPonowna wysyłka i pomogło wczesniej 2023-03-06 15:38:48 (/Plant.VC.BusinessLogic/DHVD01AP178/14580/48)[Error]Kotrak.Extensions.Pipeline.CatchPipeline - Pipeline execution errorSystem.NullReferenceException: Object reference not set to an instance of an object.at Kotrak.Common.PublishedLanguage.User.Equals(User other)at <>f__AnonymousType0`3.Equals(Object value)at System.Linq.Lookup`2.GetGrouping(TKey key\', \'Comment 3: Boolean create)at System.Linq.Lookup`2.Create(IEnumerable`1 source\', \'Comment 4: Func`2 keySelector\', ""Comment 5: IEqualityComparer`1 comparer)at System.Linq.GroupedEnumerable`2.GetEnumerator()at Kotrak.Common.Infrastructure.Integration.Filters.InboundMessageAcknowledgeHandlerFilter.Execute(InternalStorageContext`1 input)at Kotrak.Extensions.Pipeline.Pipeline`1.Execute(T input)at Kotrak.Extensions.Pipeline.CatchPipeline`1.Execute(TContext input)Wysłany ponownie przeszedł.Pierowtnie jeśli chodzi o obie fabryki ordery szły do dhp o róznych godzinach i dniach więc raczej to nie kwestia jednorazowa.\'"", ""Comment 6: \'select*FROM [DHPlantMaintBusinessLogicMain].[dbo].[Orders] where year =2023 and IsInVehicleControl=0 and month=3 and type=2\'"", ""Comment 7: \'Masbracht stan na dziś!image-2023-03-09-13-32-22-179.png!\'"", ""Comment 8: \'nie w VC extarnelid208390 208748 207387 206487 207851 208832 208423 208678 208173Pierwotnie wysyłka w takich godzinach!image-2023-03-09-13-35-57-792.png!select *from OrderExportInfoes where entityid in ( select id from Orders where externalId in (208390,208748,207387,206487,207851,208832,208423,208678,208173))!image-2023-03-09-13-35-57-792!\'"", ""Comment 9: \'!image-2023-03-09-13-42-54-335.png|width=893,height=341!brak błędów\'"", \'Comment 10: ""na bazie intercontekstów też czysto tylko kilka errorw z 01.03.!image-2023-03-09-13-47-42-108.png!Przykład wybranego ordera na eventach : FROM [DHPlantVCBusinessLogicEvents].[dbo].[Orders] where AggregateId =\\\'C66329A4-FA5E-47BE-BE2C-33F7427F015D\\\'[~aleksandra.masternak@kotrak.com]prośba odemnie i Maciej o sprawdzenie co tam się dzieje.""\', ""Comment 11: \'Hello"", \'Comment 12: please check: I can see this case now for multipe locations: I added screenshot for Veghel\', \'Comment 13: Helmond\', ""Comment 14: Maasbracht but please check also other locations!!afbeelding-2!!afbeelding-3!!afbeelding-4!\'"", ""Comment 15: \'Problem z maintenance zgłoszony w DAP-13415!image-2023-03-15-10-03-50-960!\'"", ""Comment 16: \'Hello [~TDankers@deheus.com]as I informed you in other task problem is only with wrong information in the masterdate table - we are working on solution.\']""]\nRelated Issues:\n[\'DGS-8690\', \'DAP-13415\', \'DGS-8763\']\n\n### End'}"
330,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8702\n\n### Instruction:\nHello,\r\n\r\nuser tries to complete a WMO for Andel-Mest, but get message No default dispatch location configured: where can we do this? See screenshot. The Warehouse order = WO(PD)-40/3/23\n\n### Response:\n[""Comment 1: [\'!afbeelding!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'!image-2023-03-07-12-50-48-176.png!\'"", ""Comment 4: \'Dear Thomas,Please"", ""Comment 5: check now and let me know if this is correct:!image-2023-03-07-12-54-19-757.png!Regards\'"", ""Comment 6: \'I have consulted it and it should be truck:!image-2023-03-07-13-03-41-508.png|width=1176,height=289!But you need to configure truck here!image-2023-03-07-13-06-31-673.png!Like for West:!image-2023-03-07-13-07-06-713.png!It would be also fine to remember about release:!image-2023-03-07-13-08-22-091.png!Regards\'"", ""Comment 7: \'Thanks aleksandra"", ""Comment 8: so I should create a truck and release location for Andel-mest? Or do I misunderstand?\'"", ""Comment 9: \'Yes"", \'Comment 10: exactly. Create a truck and release location. Because it is highly possible that error about release location may appear. If you need any help\', \'Comment 11: please\', ""Comment 12: let us know :)\'"", ""Comment 13: \'Oke"", ""Comment 14: I;ve created those. Thanks for the help you can close the ticket\'"", ""Comment 15: \'Thank you.Regards\'"", \'Comment 16: ""Sorry I\\\'ve one additional question: since release 8.5 I cannot move stock from Andel_West to Andel_mest\', \'Comment 17: for example for these products: How to handle this\', \'Comment 18: because I need those on Andel Mest location!afbeelding-1!""\', ""Comment 19: \'It should be done from here - unit loads list"", ""Comment 20: not stock unit list :)!image-2023-03-07-14-44-48-414.png!\']""]\nRelated Issues:\n[]\n\n### End'}"
331,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8701\n\n### Instruction:\nIt\'s needed to add new relation in relation table and adjust in the system.\r\n\r\n!image-2023-03-07-11-23-19-479.png!\n\n### Response:\n[""Comment 1: [\'https://app.box.com/file/1002580990454?s=kf5ux29gz5g5k2ykm5a6fz47a75n7741Do poprawy w przypadku nieobsługiwania którejś kolumny w Tabeli Relacji (nie wszystkie punkty są wymagane dla każdego sektora):|1.|Round||2.|Round -> Create Financial Statement (Create Sales Invoice from Round)||+3.+|FS - General||4.|FS - Details Total||5.|FS - Details Table with invoice lines||6.|FS - saldo||7.|FS - Tech Results (Calculate Technical Results)||8.|FS -> Create Saldo to Pay||9.|FS - printouts procedures|\'"", ""Comment 2: \'!image-2023-04-17-09-44-22-647.png!\'"", ""Comment 3: \'New realtions added to test database.\'"", ""Comment 4: \'Can be moved to PROD\']""]\nRelated Issues:\n[]\n\n### End'}"
332,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8700\n\n### Instruction:\nMamy error ID6344142 nie jesteśmy w stanie odczytać czego on dotyczy. Dane przestały spływać do DHP. Temat Bardzo Pilny..!\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: \'Produkcja zatrzymana właśnie \'"", ""Comment 3: \'message that was blocked for pcsLotId=230307010there was no StartTransferu Not found open transfer for this route\'"", \'Comment 4: ""Now it\\\'s better""\', ""Comment 5: \'Thank you for confirmation.\']""]\nRelated Issues:\n[]\n\n### End'}"
333,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8699\n\n### Instruction:\nprośba o bezpośredni kontakt kogoś technicznego z Jarkiem w sprawie weryfikacji podłączenia wagi ekspedycyjnej w Golubiu, na ten moment odczyt jest poprawny, ale podczas przełączania się na inną wagę, albo zapisu system się zawiesza, Jarek ma jakiś pomysł\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: \'Problem z wagami - nie konfigurowane przez nas - robione na wzór Spytkowic gdzie Ewelina przekazała my konfigurowaliśmy ale to było lata temu.Problem jest przy przełączaniu wag z poziomu VT.Dzwoniłem na fabrykę dostałem tyle informacji że konwerter łączy z wagą i przy przełączeniu nie zrywa połączenia z wagą wcześniej wybraną.  \'"", ""Comment 3: \'Hi Ewelina"", ""Comment 4: the issue has been changed from incident to service request.\'"", ""Comment 5: \'podobna sytuacja z wagą ekspedycyjną jest w Spytkowicach"", \'Comment 6: tylko tam nawet nie ma odczytu\', \'Comment 7: zweryfikujcie to proszę\', \'Comment 8: bo w Spytkowicach była ustawiana jeszcze dawno dawno temu przez Was\', ""Comment 9: a w Golubiu sami próbowaliśmy to odwzorować\'"", ""Comment 10: \'Temat gdzie w zgłoszonym Golubiu konfigurowali wagi na wzór Spytkowic"", ""Comment 11: prośba o wsparcie w temacie.\\\\rW Spytkowicach też jest problem ale nie wiem jak się do tego odnieść jak to było robione lata temu co przekazała Ewelina.\'"", ""Comment 12: \'any news?\'"", ""Comment 13: \'any news?\'"", ""Comment 14: \'tak wygląda w Spytkowicach!image!\'"", ""Comment 15: \'!image-1!\'"", ""Comment 16: \'!image-2!\']""]\nRelated Issues:\n[]\n\n### End'}"
334,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8698\n\n### Instruction:\nCould you please migrate the three migration files in this task?\n\n### Response:\n[""Comment 1: [\'[^AA - NAS_Migration_PURCHASEINVOICE_workfile_007590.xlsx] _(127 kB)_[^AA - NAS_Migration_SALESINVOICE_workfile_007590.xlsx] _(610 kB)_[^Feed migration_NAS 007590.xlsx] _(112 kB)_\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 3: \\\'Hi [~mbovene@deheus.com],\\\\r\\\\rwe have missing values in column ""Amount ""in Feed migration file. Could you provide the correct values?\\\\r\\\\rBest regards,\\\\r Grzegorz\\\'\', \'Comment 4: ""What is the column name and what lines? I don\\\'t see any missing values in my file.Or don\\\'t you refer to the Feed migration file?""\', ""Comment 5: \'Sales and Purchase Invoices have been migrated to the Intense in prod environment.We are waiting for the correct Feed sale file.Best regards,Grzegorz\'"", \'Comment 6: \\\'[~mbovene@deheus.com],the ""Quantity"" column:!image-2023-03-13-13-23-51-931.png!\\\'\', ""Comment 7: \'I see. this is always 1. Could you change this for me?\'"", ""Comment 8: \'[~mbovene@deheus.com],thank you for the answer. Feed sale elements have been migrated too.Best regards,Grzegorz\'"", ""Comment 9: \'Hi [~mbovene@deheus.com],can we close the task?Best regards,Grzegorz\'"", ""Comment 10: \'Yes\'"", \'Comment 11: ""Thank you for your reply.I\\\'m closing the task.Best regards,Grzegorz""]\']\nRelated Issues:\n[]\n\n### End'}"
335,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8697\n\n### Instruction:\nSee SI Numbers\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,8 lines with these invoice numbersSI000038161"", \'Comment 4: SI000021521\', \'Comment 5: SI000055038\', ""Comment 6: SI000071217,SI000091258 have been moved to the feed saleFE-N/0109 (Round007590/0076/0001)!image-2023-03-07-11-39-31-353.png!Regards\'"", ""Comment 7: \'{color:black}Hello,{color} {color:black}{color} {color:black}Thankx"", \'Comment 8: you can close it.{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} Bert{color} |{color:#000001} {color} |{color:#000001} Geijtenbeek{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:0318675561{color} |  {color:#000001}KvK14626985{color}   _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | | !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | | !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} | | !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} |        *Van:* Damian Świstek (Jira) <jira@kotrak.com>   *Verzonden:* dinsdag 7 maart 2023 11:43  *Aan:* Geijtenbeek\', ""Comment 9: Bert <bgeytenbeek@deheus.com>  *Onderwerp:* DGS-8697 Move feed 807590/0045/0001 > 007590/0076/0001   !image006!\']""]\nRelated Issues:\n[]\n\n### End'}"
336,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8696\n\n### Instruction:\nHi\r\n\r\nWe have this *WO(IP)-152/3/23* with a lot UL generated and registered wrongly.\r\nThe user created the UL as BigBag, however this must be a pallet.\r\nWhen we try to remove the registered UL, system displays an error message: {color:red}*Warehouse intake should be in progress*{color}\r\n\r\nCould you please withdraw ALL the registered UL from this WO(IP)?\r\nThe truck is waiting for it.\r\n\r\nThank you very much\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Elements has been removed from WI-307/3/23 related to WO(IP)-152/3/23. Unfortunatly there id one barcode 89-W006LS that has been released on STK-159/3/23.!image-2023-03-06-17-14-22-169.png!!image-2023-03-06-17-15-56-077.png!That is why i can not remove it from WI-307/3/23.You can create one addidtional element related onWO(IP)-152/3/23 for this extra quantity. and correct it through stocktaking if nessesery.Please check an let us know if we can close this issue.\'"", ""Comment 4: \'Hi BartłomiejThank you very much!You can close this task\'"", \'Comment 5: ""weryfikacja{code:java}SELECT TOP (1000) * FROM [DHPlantWmsBusinessLogicMain].[dbo].WarehouseOrders where DocumentYear=2023 and DocumentMonth=3 and DocumentNumber=152select Status,* from dbo.WarehouseIntakes where DocumentNumber=307 and DocumentYear=2023select * from dbo.WarehouseIntakeElements where Id=\\\'A3E8C981-82B9-4155-8226-499496C3F13C\\\'select * from dbo.UnitLoads where Id in (\\\'3D3074DB-1C22-45C7-8C4F-0A039971B268\\\',\\\'D6A1F9B5-6323-4953-86BF-47ABAA0079B9\\\',\\\'329E416C-16FF-4B7A-86B0-5E458B23A0F6\\\',\\\'7140933B-33AB-42D1-976C-8520960E03F8\\\',\\\'931E3BE8-DE3F-422C-81D9-81A1257F7256\\\',\\\'19BEF811-6D16-493A-8AFC-2111C9531DFD\\\',\\\'FFD8D6A2-1D4F-4E6E-B670-1C1A013FB539\\\',\\\'06742CBC-F081-46D5-944A-D1D738B48397\\\')select * from dbo.StockUnits where UnitLoadId in (\\\'3D3074DB-1C22-45C7-8C4F-0A039971B268\\\',\\\'D6A1F9B5-6323-4953-86BF-47ABAA0079B9\\\',\\\'329E416C-16FF-4B7A-86B0-5E458B23A0F6\\\',\\\'7140933B-33AB-42D1-976C-8520960E03F8\\\',\\\'931E3BE8-DE3F-422C-81D9-81A1257F7256\\\',\\\'19BEF811-6D16-493A-8AFC-2111C9531DFD\\\',\\\'FFD8D6A2-1D4F-4E6E-B670-1C1A013FB539\\\',\\\'06742CBC-F081-46D5-944A-D1D738B48397\\\')SELECT TOP (1000) *  FROM [DHPlantWmsBusinessLogicMain].[dbo].[StockUnitReleases]  where Id = \\\'3B89A29C-2A29-4561-A808-B740A20D47F5\\\'{code}rozwiązanie tylko gdy nie ma powiązanych dokumentów{code:java}--update dbo.WarehouseIntakes set Status=30 where id = \\\'A3E8C981-82B9-4155-8226-499496C3F13C\\\'{code}""]\']\nRelated Issues:\n[]\n\n### End'}"
337,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8695\n\n### Instruction:\nFor some reason, round 2 became B001422/0172/0004, round 3 was correct (B001422/0172/0003) and round 4 became B001422/0172/0005. Could you adapt round 2 (B001422/0172/0004, ID 71622) to number B001422/0172/0002 and round 4 (B001422/0172/0005, ID 99850) to number B001422/0172/0004? So the round numbers are good, but the full round numbers are wrong.\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 Steffen,Yes\', ""Comment 4: it\'s strange that there is no number B001422/0172/0002 at all in Intense right now. Maybe there were some changes in customer on roundB001422/0172/0004 then Intense coul recalculate full number (originally probably was round 2 like order of ID\'s) because generally full number should be ascending like ID"", ""Comment 5: but in this case it\'s not. I think other documents for this rounds have good number round like this PI below!image-2023-03-07-11-55-23-870.png!!image-2023-03-07-12-04-39-186.png!We can update full round numbers"", \'Comment 6: so I\\\'ll let you know when it will be ready.Regards""\', ""Comment 7: \'Full round numbers have been updated"", ""Comment 8: so now round 2 and round 4 have good full numbers!image-2023-03-07-12-41-08-570.png!Please verify that everything is correct.Regards\'"", ""Comment 9: \'This seems perfect"", ""Comment 10: thank you!!image-2!\'"", ""Comment 11: \'Great"", ""Comment 12: so I close the task.\']""]\nRelated Issues:\n[]\n\n### End'}"
338,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8694\n\n### Instruction:\nPlease resend all lot reports with status confirmed for locations: Helmond, Ravenstein, Maasbracht, Veghel and Andel\r\n\r\nDue to missing configuration with release 8.5 the lot reports in this status are not send to DHC, while they should be. Discussed with Marek and he asked to create this ticket\n\n### Response:\n[\'Comment 1: [""sorry\', \'Comment 2: should be with status \\\'finished\\\'""\', ""Comment 3: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 4: \'Edit: wszystkie PLRy do wysłania w plikach excel. A było ich .... dużoHelmond - 60 Ravenstein - 9 Maasbracht - 115 Veghel - 8 Andel - 0------------------Razem: 192\'"", ""Comment 5: \'Do przesłania PLR w statusie Finished wygenerowane odpowiednio dla kolejnych fabryk pomiędzy:|*Date*|*Start time*|*Plant*||28-feb|09:00|Ravenstein||1-mrt|09:00|Maasbracht||2-mrt|09:00|Veghel||3-mrt|09:00|Andel|*a 07.03 - 14:55*\'"", ""Comment 6: \'zatem ilość się nie zmieni:Pa jeśli chodzi o Helmond"", \'Comment 7: to rozumiem\', ""Comment 8: że od samego początku czyli uruchomienia?\'"", ""Comment 9: \'0041060323025 - RavensteinTu chyba sami sobie je potwierdzili w czasie naszej rozkimny!image-2023-03-07-09-00-32-087.png!!image-2023-03-07-09-01-24-577.png! !image-2023-03-07-09-00-32-087!!image-2023-03-07-09-01-24-577!\'"", ""Comment 10: \'0081060323049 - Veghel\'"", ""Comment 11: \'Helmond - od uruchomienia 4 luty do 14 lutego 11:30 - potem został zmieniony config i PLR już wapdają\'"", ""Comment 12: \'[^DGS-8694.xlsx]\'"", ""Comment 13: \'[^DGS-8694.xlsx]\'"", ""Comment 14: \'Skrypt do przerobienia pod 8.5: http://10.10.10.52:82/projects/PLA3/repos/dhp30implementations/browse/NL%20AS400/Scripts/Resend%20draft%20production%20lots%20to%20DHC.sql\'"", ""Comment 15: \'Veghel:Wszystkie z wczorajszej listy z excela są w DHCW Veghel w plancie jest jeden z teraz:!image-2023-03-08-13-08-47-278.png!!image-2023-03-08-13-07-49-546.png!\'"", ""Comment 16: \'MAASBRACHT ostatni do przesłania na zółto:!image-2023-03-08-13-14-38-560.png!\'"", ""Comment 17: \'[^Thomas.xlsx]\'"", ""Comment 18: \'Dear Thomas,In attach"", ""Comment 19: here is the list of PLRs sent in the time frame provided by Marek[^Thomas.xlsx]Regards\'"", ""Comment 20: \'[^dgs-8694 v2.xlsx]\'"", ""Comment 21: \'[^dgs-8694 v2.xlsx]\'"", ""Comment 22: \'[^Resend draft production lots to DHC v8.5 (1).sql]\'"", ""Comment 23: \'[^Resend draft production lots to DHC v8.5 (1).sql]\'"", ""Comment 24: \'Thanks! ticket can be closed\'"", ""Comment 25: \'Thank you\']""]\nRelated Issues:\n[\'DGS-8884\']\n\n### End'}"
339,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8693\n\n### Instruction:\nHello,\r\n\r\nin Ravenstein I tried to close VT-36/3/23: added missing quanities and closed the ticket: AS you can see in the screenshot attached it did use the finished product, however status is still \'dispatch completed\' and now it has missing quantities of all orderlines..\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: \'Błąd dla stocka{code:java}Kotrak.Common.Application.Exceptions.BusinessLogicException: CannotCompleteBulkWhenRequestedQuantityGraterThanReservedQuantityEvenAutomaticStocktakingIsGeneratedMessage   at Plant.Stock.BusinessLogic.Application.Services.RegisterDispatchService.ThrowExceptionWhenCompleteBulkDispatchNotSatisfied(BulkDispatchValidationResult validationResult) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Application\\\\\\\\Services\\\\\\\\RegisterDispatchService.cs:line 421   at Plant.Stock.BusinessLogic.Application.Services.RegisterDispatchService.CompleteBulkDispatch(CompleteBulkDispatchDataStructure dataStructure) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Application\\\\\\\\Services\\\\\\\\RegisterDispatchService.cs:line 306   at Plant.Stock.BusinessLogic.Application.CommandHandlers.BulkDispatch.CompleteBulkDispatchCommandHandler.Handle(CompleteBulkDispatchCommand command) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Application\\\\\\\\CommandHandlers\\\\\\\\BulkDispatch\\\\\\\\CompleteBulkDispatchCommandHandler.cs:line 34   at Kotrak.Common.Infrastructure.Gate.CommandEnvironment.Run[TCommand](TCommand command)   at Castle.DynamicProxy.AbstractInvocation.Proceed()   at Kotrak.Common.Infrastructure.Interceptors.LoggingInterceptor`1.Intercept(IInvocation invocation)   at Castle.DynamicProxy.AbstractInvocation.Proceed()   at Kotrak.Common.Infrastructure.Gate.Filters.CommandProcessFilter`1.Execute(CommandPipelineContext`1 input)   at Kotrak.Extensions.Pipeline.PredefinedFilters.FilterDecorator`1.Execute(TContext input)   at Kotrak.Extensions.Pipeline.Pipeline`1.Execute(T input)   at Kotrak.Common.Infrastructure.Gate.StandardGate.DispatchCommand[TCommand](TCommand command)   at Kotrak.Common.Infrastructure.Integration.Filters.InboundMessageHandlerFilter.Execute(InternalStorageProcessContext`1 input)   at Kotrak.Extensions.Pipeline.Pipeline`1.Execute(T input)   at Kotrak.Common.Infrastructure.Integration.Filters.InboundMessagesProcessFilter.Execute(InternalStorageContext`1 input){code}id=53388af5-51f3-4c27-a8cc-5fd65a902392 162713\'"", ""Comment 4: \' !screenshot-1!  !screenshot-2!  !screenshot-3! \'"", ""Comment 5: \' !screenshot-4!  !screenshot-5!  !screenshot-6! \'"", ""Comment 6: \'trzymała rezerwacja  !screenshot-7! Aktualnie VT jest zamknięty.Rezerwacja była dla VT jeszcze z grudnia 2022.Powiązany DGS-8299teraz jest pobrane x2. !screenshot-9! \'"", ""Comment 7: \'Hello,I managed to close VT but x2 stocks have been released and they should be restored by inventory.As to the cause"", \'Comment 8: in order to determine the cause\', ""Comment 9: please accept RCA.\'"", ""Comment 10: \'Please close this ticket\']""]\nRelated Issues:\n[]\n\n### End'}"
340,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8692\n\n### Instruction:\nHi,\r\n\r\nCan you please explain me how these documents were created. Since the colleague whose name is written at the bottom of the document says that he never created this documents. Is it possible that the system itself creates these documents based on something/what?\n\n### Response:\n[""Comment 1: [\'[^IRC.pdf] _(1023 kB)_\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 3: ""Ive checked provided documents and they did not came from DHC. Those documents were created in ERP system by someone who logged into ERPXL through provided operators ID\\\'s: SIMIVLAS andVUKBAR. As I can see those operators do not have password set on their accounts\', \'Comment 4: so anybody who have go t access to ERP system have an ability to create documents in behalf on them.Please\', \'Comment 5: let me know if the answer is sufficient for you. Do you expect any additional actions from us regarding this issue? Can we close this ticket?""\', ""Comment 6: \'Hi"", \'Comment 7: thank you for the explanation. But still\', \'Comment 8: it is not clear to me why and how these documents were created. Before I sent initial request\', ""Comment 9: I already discuss with those colleagues and they claim that nothing is done differently than usual. This correction for certain SOR documents doubled or trippled COGS which made margins wrong.  \'"", ""Comment 10: \'As I wrote earlier"", ""Comment 11: those documents were created in ERPXL by someone who was logged in asSIMIVLAS or VUKBAR.Anyone who have access to ERP system can log into the system asSIMIVLAS or VUKBAR and create such documents.\'"", ""Comment 12: \'As I can see in the system logs in February 2023 in ERPXL"", \'Comment 13: the VUKBAR operator was logged in by users working on the following domain accounts: VBarjaktarovic\', \'Comment 14: MPETROVIC and ASTAMENKOVIC logged in to the RSTS01 terminal.Please\', ""Comment 15: let me know if the answer is sufficient for you. Do you expect any additional actions from us regarding this issue? Can we close this ticket?\'"", ""Comment 16: \'Please"", ""Comment 17: let me know if expect any additional actions from us regarding this issue? Can we close this ticket?\'"", ""Comment 18: \'Please"", ""Comment 19: let me know if expect any additional actions from us regarding this issue? Can we close this ticket?\'"", ""Comment 20: \'Not yet please. We just had meeting regarding this and DGS-8653 and we will have to have a video meeting from someone responsible for HelpDesk from KOTRAK to help our management clarify some thing and to se what will we do with that. Thank you for your patience. Best regards.\'"", ""Comment 21: \'Please"", ""Comment 22: let me know if expect any additional actions from us regarding this issue? Can we close this ticket?\'"", ""Comment 23: \'Could you please confirm if we can close this task?Regards\'"", ""Comment 24: \'Could you please confirm if we can close this task?Regards\']""]\nRelated Issues:\n[]\n\n### End'}"
341,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8691\n\n### Instruction:\nCześć,\r\n\r\nMamy już 2 loty na premixach, gdzie część zarejestrowanych worków nie przechodzi z pcsa do dhp. Temat pilny.\r\n\r\nRafał Boniecki\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!!image-1!\'"", ""Comment 2: \'Hello,\\\\r\\\\rWe are investigating your issue. We will inform you about the solution as soon as possible.\\\\r\\\\rRegards\'"", ""Comment 3: \'Czy mogę poprosić o numer lotów których brakuje?Could you bring missing lot numbers?\'"", ""Comment 4: \'problem dotyczy lotów 0272060323010 i 0272060323001. Ale chodzi o część niezarejestrowanych worków. Jest w screenach. Same loty przeszły do dhp.\'"", ""Comment 5: \'to numery z pcs"", ""Comment 6: z tego o widze w exchange jest takFROM [DH_Exchange].[dbo].[ProductionLotReportHeader]  -- order by PLH_Id desc  where PLH_LotNumber in ( 0201060323010,0201060323001)\'"", ""Comment 7: \'select * FROM [DHP_Leczyca].[dbo].[Delivery] where del_plhid in (164739,164755)- brak eanów na delivery\'"", ""Comment 8: \'!image-2023-03-06-15-59-04-085.png!\'"", ""Comment 9: \'Kolejny lot z tym błędem: !image-2!\'"", ""Comment 10: \'!image-3!\'"", ""Comment 11: \'[~marcin.block@kotrak.com]dasz radę spojrzeć co się tutaj im zaczęło dziać?\'"", ""Comment 12: \'[~rboniecki@deheus.com] I need to ask our developers for help with that issue.\'"", \'Comment 13: ""I hope that it won\\\'t take them too much time....""\', ""Comment 14: \'!image-2023-03-07-08-20-59-017.png!\'"", ""Comment 15: \'select* FROM [DHP_Leczyca].[dbo].[RegisterMappings] where rgm_delid in (274375,274409)\'"", ""Comment 16: \'We managed with this problem"", ""Comment 17: task to close. Thanks.\']""]\nRelated Issues:\n[]\n\n### End'}"
342,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8690\n\n### Instruction:\nHello,\r\n\r\nthese orders are not in VC-Module, but also I cannot find anything in the error log, so I\'m not sure whats going on and what needs to be done to fix this, please check\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Could you please provide numbers of orders that are missing in VC module?\'"", ""Comment 3: \'see attached list!afbeelding!\'"", ""Comment 4: \'select * FROM [DHPlantMaintBusinessLogicMain].[dbo].[Orders] where year =2023 and IsInVehicleControl=0 and month=3select * from OrderExportInfoes where entityid in ( select id from Orders where externalId in (205226,204069,205920,203880,204231,204944,206141,206234,204761,204202,204182,206075,205887,205264))adresy niby sie zgadzajaselect o.id,o.ExternalId,o.MainBusinessPartnerId as partneronorder,o.DocumentNumber,o.ForeignDocumentNumber"", ""Comment 5: o.MainBusinessPartnerAddressId as addressonorder,a.id as adressid,b.id as bpid from orders o join BusinessPartners b on b.id=o.MainBusinessPartnerIdjoin Addresses a on a.id=b.CurrentAddressIdwhere o. ExternalId in (205226,204069,205920,203880,204231,204944,206141,206234,204761,204202,204182,206075,205887,205264)\'"", ""Comment 6: \'Hello I resend 13 from 14 salesorder from march 2023"", ""Comment 7: that were not in VC!image-2023-03-06-15-35-46-185.png|width=1132,height=227!there were no error message for them.One still hanging.\'"", ""Comment 8: \'!image-2023-03-06-15-39-42-683.png!\'"", ""Comment 9: \'w lugu vt jest taki blad przy ponownym przesłaniu\'"", ""Comment 10: \'Ponowna wysyłka i pomogło wczesniej 2023-03-06 15:38:48 (/Plant.VC.BusinessLogic/DHVD01AP178/14580/48) [Error] Kotrak.Extensions.Pipeline.CatchPipeline - Pipeline execution errorSystem.NullReferenceException: Object reference not set to an instance of an object. at Kotrak.Common.PublishedLanguage.User.Equals(User other) at <>f__AnonymousType0`3.Equals(Object value) at System.Linq.Lookup`2.GetGrouping(TKey key"", \'Comment 11: Boolean create) at System.Linq.Lookup`2.Create(IEnumerable`1 source\', \'Comment 12: Func`2 keySelector\', ""Comment 13: IEqualityComparer`1 comparer) at System.Linq.GroupedEnumerable`2.GetEnumerator() at Kotrak.Common.Infrastructure.Integration.Filters.InboundMessageAcknowledgeHandlerFilter.Execute(InternalStorageContext`1 input) at Kotrak.Extensions.Pipeline.Pipeline`1.Execute(T input) at Kotrak.Extensions.Pipeline.CatchPipeline`1.Execute(TContext input)błedy jak wyzej\'"", ""Comment 14: \'please check all order were synchronized to VC module\'"", ""Comment 15: \'Thanks! any reason why this happened? due to update?\'"", ""Comment 16: \'Hello"", ""Comment 17: can you please check location Helmond? Same situation applies there!afbeelding-1!\'"", ""Comment 18: \'w helmond 12 orderów z marca select*FROM [DHPlantMaintBusinessLogicMain].[dbo].[Orders] where year =2023 and IsInVehicleControl=0 and month=3 and type=2!image-2023-03-07-10-47-18-764.png!\'"", ""Comment 19: \'Please check now in HelmondIn this task we have focused on clearingandunblocking the process.If there is a need from your sideto investigate the reasonof the issue"", \'Comment 20: we may raise RootCause Analysis (RCA)task for you.Please\', ""Comment 21: let us knowhow you wish us to proceed.\'"", ""Comment 22: \'Please create RCA"", ""Comment 23: then you can close this ticket\'"", ""Comment 24: \'here is a RCa taskDGS-8703\']""]\nRelated Issues:\n[\'DGS-8703\', \'DAP-13415\']\n\n### End'}"
343,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8689\n\n### Instruction:\nIn MAS BE, the SI\'s based on PI\'s from SR\'s, the sales invoice is hard coded for B005059 De Heus Voeders as supplier. For all customers, we need to use NB as payment method in Intense. This is all right for all customers on the customers, and also for B005059 as you can see in the first screenshot. However, due to the fact that these SI\'s are hard coded, \'Settlement\' keeps on showing as payment method in Intense as you can see in the second screenshot for example (SI-RLB/2023/1301, ID 103103). Can you modify this hard coded scenario and use \'NB\' as payment form Intense?\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: ""Update: because we want to finish this round I manually changed this invoice\\\'s payment method to NB. But I hope you understand my point and you will be able to modify this.!image-2!!image-3!""\', ""Comment 4: \'Hello,Do you have an update on this topic?\'"", \'Comment 5: ""Hi [~SDriesen@deheus.com],we\\\'ve made changes in test environment for NB payment form in the SI generation of SR process.You can feel free to test it.Best regards,Grzegorz""\', ""Comment 6: \'Zmiany w generacji:Create Sales Invoice (MAS BE) dla Payment Method.\'"", ""Comment 7: \'My SI automatically went to NB this time"", ""Comment 8: as we wanted. So this may be implemented in PROD in MAS BE. Thank you Grzegorz!!image-4!\'"", ""Comment 9: \'[~SDriesen@deheus.com],functionality has been moved into prod Intense environment.You can verify it.Best regards,Grzegorz\'"", ""Comment 10: \'This works now"", ""Comment 11: thank you!Regards,Steffen\'"", \'Comment 12: ""Excellent\', \'Comment 13: thank you.I\\\'m closing the task.Best regards,Grzegorz""]\']\nRelated Issues:\n[]\n\n### End'}"
344,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8688\n\n### Instruction:\nThe PCS sent the dosage and lot number, but DHP didn\'t reserved. \r\nItem PSMGC1235, lot number 0851020323023, ingredient 21405, lot number WI-276/2/23, quantity 1 837.555 kg, ingredient in production area.\r\n\r\nCould you check why system didn\'t reserved the quantity?\r\n\r\nThank you\n\n### Response:\n[""Comment 1: [\'!image!!image-1!!image-2!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Hello,\\\\r\\\\rWe are investigating your issue. We will inform you about the solution as soon as possible.\\\\r\\\\rRegards\\\\r\\\\r\'"", ""Comment 4: \'Could you please provide new password for my user for mubrasil domain?mubrasil\\\\\\\\ajanuszewska\'"", ""Comment 5: \'new password 123Change\'"", ""Comment 6: \'plr id=7c43f146-594f-420e-8772-1e5055822\'"", \'Comment 7: ""brak stockunitidSELECT TOP (1000) [Id] ,[No] ,[ItemId] ,[DeliveryId] ,[StockUnitId] ,[Quantity] ,[QuantityUnit] FROM [DHPlantStockBusinessLogicMain].[dbo].[ProductionLotReservations] where id=\\\'7C43F146-594F-420E-8772-1E5055822DCB\\\' and ItemId =\\\'BBFEEAD7-6160-4DBA-A768-76572A4991F5\\\'""\', \'Comment 8: ""select* FROM [DHPlantStockBusinessLogicMain].[dbo].[StockUnits] where DeliveryId=\\\'90907450-9EE3-48FC-BBDA-BA0B3E6A6EF3\\\'  and itemid=\\\'BBFEEAD7-6160-4DBA-A768-76572A4991F5\\\'!image-2023-03-07-09-41-57-320.png!""\', \'Comment 9: ""Jak wyżej w modul stock tabelaFROM[DHPlantStockBusinessLogicMain].[dbo].[ProductionLotReservations]where id=\\\'7C43F146-594F-420E-8772-1E5055822DCB\\\'and ItemId =\\\'BBFEEAD7-6160-4DBA-A768-76572A4991F5\\\'brak stockunitid dla podanego itemuporownujac quantityonhand dla stockunitachmamy SELECT ST.ID,W.ID,W.LogisticStatus,ST.BARCODE,ST.Quantity,ST.QuantityOnHand,ST.QuantityUnit\', \'Comment 10: ST.QuantityOnHandUnit\', ""Comment 11: W.LogisticStatus,W.QuantityOnHandUnit,W.QuantityOnHandValue ,W.ReservedQuantityUnit,W.ReservedQuantityValue FROM [DHPlantStockBusinessLogicMain].[dbo].[StockUnits] ST JOIN [DHPlantWmsBusinessLogicMain].[dbo].[StockUnits] W ON ST.ID=W.ID  where ST.DeliveryId=\'90907450-9EE3-48FC-BBDA-BA0B3E6A6EF3\'mamy dla 2 pozycji qunatotyon hand tyle że + - pokrywa to rezerwacje.pytanie jak to poprawić SELECT ST.ID,W.ID,W.LogisticStatus,ST.BARCODE,ST.Quantity,ST.QuantityOnHand,ST.QuantityUnit"", \'Comment 12: ST.QuantityOnHandUnit\', \'Comment 13: W.LogisticStatus,W.QuantityOnHandUnit,W.QuantityOnHandValue ,W.ReservedQuantityUnit,W.ReservedQuantityValue FROM [DHPlantStockBusinessLogicMain].[dbo].[StockUnits] ST JOIN [DHPlantWmsBusinessLogicMain].[dbo].[StockUnits] W ON ST.ID=W.ID  where ST.DeliveryId=\\\'90907450-9EE3-48FC-BBDA-BA0B3E6A6EF3\\\'!image-2023-03-07-10-02-24-944.png!""\', ""Comment 14: \'[~agnieszka.januszewska@kotrak.com] a nie macie skryptów do poprawy tego?\'"", ""Comment 15: \'Aktualnie brak wyników!image-2023-04-18-18-30-36-036.png!\'"", ""Comment 16: \'Could you verify if stocks are now ok"", ""Comment 17: may we close the task ?Did you have any more similar cases?\']""]\nRelated Issues:\n[]\n\n### End'}"
345,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8687\n\n### Instruction:\nHello,\r\n\r\nP1 issue! An order is send tp pcs Ravenstein, I can find the message in the requestlog, see attached.\r\n\r\nHowever, the order is NOT visible in DHP, also not in masterdata. This should be impossible, please check whats going on ASAP. SO number = SO000075533\n\n### Response:\n[""Comment 1: [\'[^SOSO000075533.json] _(4 kB)_\'"", ""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: \'Order nie wpadł tylko do modułu VC. W logach VC z dnia 28.02 pojawiały się informacje o problemach z rabbitem. Po ponownym przesynchronizowaniu ordera wpadł od do VC. Resendowałam też Tripa"", ""Comment 4: bo nie wpadł przez brak tego SO.!ORDER_ASN!\'"", ""Comment 5: \'Dear Thomas,Order is in DHP but not in VC module:!image-2023-03-06-12-35-03-459.png!There is a mess with addresses again. I hope"", ""Comment 6: I have marked it legibly. So>> in yellow we have main business and payer Business Partner>> but they have assigned the address id that belongs to Target Business Partner>> please ask Milas to correct it and resend the questioned Order.!image-2023-03-06-12-34-45-657.png!Regards\'"", \'Comment 7: ""Hi Aleksandra: Oke good to know\', ""Comment 8: because this I know how to fix :) So I\'m relieved"", \'Comment 9: I did not see the order in the masterdata of DHP\', \'Comment 10: so that\\\'s why I was confused. Do you know why it\\\'s not visible there?""\', \'Comment 11: ""Dev Team also reported some issues with Rabbit on 28th of February. They have resynced Order and resent Trip because it was also missing. Please check now. So to be honest now I\\\'m not sure if this is address issue or Rabbit issue. However\', \'Comment 12: there is some mess with addresses still...Regards""\', ""Comment 13: \'Hi,I think we can treat this issue now as incidental case. Can we close this task?Regards\'"", ""Comment 14: \'Ticket can be closed\'"", ""Comment 15: \'Thank you\']""]\nRelated Issues:\n[]\n\n### End'}"
346,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8686\n\n### Instruction:\nHello, \r\n\r\nlot report 0061270123041 is in status \'in progress\'. But there are two batches missing. I found those in the APIrequest log, but when I try to reprocess those, I got the message that the lot is already finished. The 2 missing batchreport xmls are added to the ticket. Can you investigate and make sure these are registered correctly? because produced quantity is not send to ERP and is leading to problems.\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue.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: \'PLR has been already confirmed and synchronized to ERP:!image-2023-04-20-13-35-41-414!The batches whose XML files were attached to the task were registered:!image-2023-04-20-13-39-38-210![~aleksandra.przybylek@kotrak.com]please confirm if the issue is still valid? (PLR was registered in January - we do not have logs from this period to determine why the batches were not registered)\'"", ""Comment 3: \'Dzięki Wojtek\'"", ""Comment 4: \'Hi,PLR has been already confirmed and synchronized to ERP:!image-2023-04-20-13-48-58-728.png|width=1092,height=528!The batches whose XML files were attached to the task were registered:!image-2023-04-20-13-49-20-439.png|width=1119,height=254!Please"", ""Comment 5: let us know if this is fine for you.Regards\']""]\nRelated Issues:\n[\'DGS-8443\', \'DGS-8604\']\n\n### End'}"
347,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8685\n\n### Instruction:\nHi\r\nPlease help to check this  case .\r\nCan\'t create Production order for item 66CC-43++-F-B25 with erros messege is ""No bags found for item66CC-43++-F-B25 "".\r\nChecked the recipe and item packaging (BPEC01170) are no problem.\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,Sorry\', \'Comment 4: but I\\\'m having a problem connecting.|115.75.177.45:3382|Regards""\', ""Comment 5: \'We are  checking"", ""Comment 6:  the connection works.\'"", ""Comment 7: \'What user name are you logging in with?\'"", \'Comment 8: "" !screenshot-1! {code:java}  FROM [DHPlantProdBusinessLogicMain].[dbo].[Items]  where code like \\\'66CC-43++-F%\\\'{code}!image-2023-03-06-08-55-17-535!""\', ""Comment 9: \'The item has been resent from DHC"", ""Comment 10: can you check again?\'"", ""Comment 11: \'Thanks u. Production order for this item already be created.U can close this ticket.\'"", ""Comment 12: \'Thank you for confirmation.\']""]\nRelated Issues:\n[]\n\n### End'}"
348,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8684\n\n### Instruction:\nPro from 104 to 117 missing from exchange.\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: ""I use this to check for missing items\', \'Comment 4: recipes\', \'Comment 5: orders\', \'Comment 6: and partners linked to a ProSELECT top 100           mpr.DocumentNumber as [Prod.PRP]    \', \'Comment 7:      mpr.CreateDate as [Prod.Created]    \', ""Comment 8:      case when pri.import is null then \'MISSING\' else \'Imported\' end as PCS_Production_Request    "", ""Comment 9:      case rci.import when null then mrc.Name                                     else \'Imported\' end as PCS_Recipe    "", ""Comment 10:      case when ord.import is null then mor.FullDocumentNumber                                        else \'Imported\' end as PCS_SO    "", ""Comment 11:      case iti.import when 0 then mit.Code                                  else \'Imported\' end as PCS_Item    "", \'Comment 12:      case when bpi.import = 0 then \\\'Imported\\\'                                    else mbp.Code end as PCS_Partner    FROM      [DHPlantProdBusinessLogicMain].[dbo].[ProductionOrders] mpr    LEFT JOIN [DHPlantProdBusinessLogicMain].[dbo].ProductionOrderOrderElements mpo ON mpo.id = mpr.Id    LEFT JOIN [DHPlantProdBusinessLogicMain].[dbo].Items mit ON mit.Id = mpr.ReadyProductId    LEFT JOIN [DHPlantProdBusinessLogicMain].[dbo].BusinessPartners mbp ON mbp.id = mpr.BusinessPartnerId    LEFT JOIN [DHPlantProdBusinessLogicMain].[dbo].Orders mor ON mor.id = mpo.OrderId    LEFT JOIN [DHPlantProdBusinessLogicMain].[dbo].Recipes mrc ON mrc.id = mpr.RecipeId    --Produciton Order    left join [10.0.23.10].[DHExchange67].[dbo].[ProductionOrders] pro on pro.id = mpr.id    left join [10.0.23.10].[DHExchange67].[api].[ProductionOrdersImport] pri on pro.entityid = pri.id    --Recipes    left join [10.0.23.10].[DHExchange67].[dbo].[Recipes] rch on rch.id = mpr.RecipeId    left join [10.0.23.10].[DHExchange67].[api].[RecipesImport] rci on rci.id = rch.[EntityId]    --Order    left join [10.0.23.10].[DHExchange67].[dbo].[Orders] orh ON orh.id = mpo.orderid    left join [10.0.23.10].[DHExchange67].[api].[OrdersImport] ord ON ord.id = orh.entityid    --Item    left join [10.0.23.10].[DHExchange67].[dbo].Items itm ON itm.id = mpr.ReadyProductId    LEFT JOIN [10.0.23.10].[DHExchange67].api.ItemsImport iti ON iti.id = itm.entityid    --Partner    LEFT JOIN [10.0.23.10].[DHExchange67].[dbo].[BusinessPartners] bpt ON bpt.id = mpr.BusinessPartnerId    LEFT JOIN [10.0.23.10].[DHExchange67].[api].[BusinessPartnersImport] bpi ON bpi.id = bpt.entityid\\\\t where pri.id is null    order by mpr.createdate descplease tell me if something else is blocking or missing that stops them from going through.""\', ""Comment 13: \'Wszystkie PrO są z 5 marca"", \'Comment 14: ostatni host log w tym dniu:{code:java}2023-03-05 13:51:33 (/Plant.PCS.BusinessLogic/SAKDSRV04/18088/1) [Fatal] Microsoft.AspNetCore.Hosting.Diagnostics - Application startup exceptionAutofac.Core.DependencyResolutionException: An exception was thrown while activating λ:Kotrak.Integration.IntegrationPluginCommon.MessageHandling.IIntercontextCommunicationSubscription[] -> Plant.PCS.BusinessLogic.Infrastructure.ContextIntegration.Subscriptions.WMS.WarehouseOrderElementReadyToProcess.WarehouseOrderElementReadyToProcessMessageSubscription -> Kotrak.Integration.RabbitMQClient.MessageBusClient -> RawRabbit.BusClient -> λ:RawRabbit.Channel.Abstraction.IChannelFactory. ---> RabbitMQ.Client.Exceptions.BrokerUnreachableException: None of the specified endpoints were reachable ---> RabbitMQ.Client.Exceptions.PossibleAuthenticationFailureException: Possibly caused by authentication failure ---> RabbitMQ.Client.Exceptions.OperationInterruptedException: The AMQP operation was interrupted: AMQP close-reason\', \'Comment 15: initiated by Library\', \'Comment 16: code=541\', \'Comment 17: text=""Unexpected Exception""\', \'Comment 18: classId=0\', \'Comment 19: methodId=0\', \'Comment 20: cause=System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.. ---> System.Net.Sockets.SocketException (10054): An existing connection was forcibly closed by the remote host.   at System.Net.Sockets.NetworkStream.Read(Byte[] buffer\', \'Comment 21: Int32 offset\', \'Comment 22: Int32 count)   --- End of inner exception stack trace ---   at RabbitMQ.Client.Impl.Frame.ReadFrom(NetworkBinaryReader reader)   at RabbitMQ.Client.Impl.SocketFrameHandler.ReadFrame()   at RabbitMQ.Client.Framing.Impl.Connection.MainLoopIteration()   at RabbitMQ.Client.Framing.Impl.Connection.MainLoop()   at RabbitMQ.Client.Impl.SimpleBlockingRpcContinuation.GetReply(TimeSpan timeout)   at RabbitMQ.Client.Impl.ModelBase.ConnectionStartOk(IDictionary`2 clientProperties\', \'Comment 23: String mechanism\', \'Comment 24: Byte[] response\', \'Comment 25: String locale)   at RabbitMQ.Client.Framing.Impl.Connection.StartAndTune()   --- End of inner exception stack trace ---   at RabbitMQ.Client.Framing.Impl.Connection.StartAndTune()   at RabbitMQ.Client.Framing.Impl.Connection.Open(Boolean insist)   at RabbitMQ.Client.Framing.Impl.Connection..ctor(IConnectionFactory factory\', \'Comment 26: Boolean insist\', \'Comment 27: IFrameHandler frameHandler\', \'Comment 28: String clientProvidedName)   at RabbitMQ.Client.Framing.Impl.AutorecoveringConnection.Init(IFrameHandler fh)   at RabbitMQ.Client.Framing.Impl.AutorecoveringConnection.Init(IEndpointResolver endpoints)   at RabbitMQ.Client.ConnectionFactory.CreateConnection(IEndpointResolver endpointResolver\', \'Comment 29: String clientProvidedName)   --- End of inner exception stack trace ---   at RabbitMQ.Client.ConnectionFactory.CreateConnection(IEndpointResolver endpointResolver\', \'Comment 30: String clientProvidedName)   at RabbitMQ.Client.ConnectionFactory.CreateConnection(IList`1 hostnames\', \'Comment 31: String clientProvidedName)   at RabbitMQ.Client.ConnectionFactory.CreateConnection(IList`1 hostnames)   at RawRabbit.Channel.ChannelFactory.ConnectAsync(CancellationToken token)   at RawRabbit.DependencyInjection.RawRabbitDependencyRegisterExtension.<>c.<AddRawRabbit>b__0_3(IDependencyResolver resolver)   at RawRabbit.DependencyInjection.Autofac.ContainerBuilderAdapter.<>c__DisplayClass5_0`2.<AddSingleton>b__0(IComponentContext context)   at Autofac.Builder.RegistrationBuilder.<>c__DisplayClass0_0`1.<ForDelegate>b__0(IComponentContext c\', \'Comment 32: IEnumerable`1 p)   at Autofac.Core.Activators.Delegate.DelegateActivator.ActivateInstance(IComponentContext context\', \'Comment 33: IEnumerable`1 parameters)   at Autofac.Core.Resolving.InstanceLookup.Activate(IEnumerable`1 parameters\', \'Comment 34: Object& decoratorTarget)   --- End of inner exception stack trace ---   at Autofac.Core.Resolving.InstanceLookup.Activate(IEnumerable`1 parameters\', \'Comment 35: Object& decoratorTarget)   at Autofac.Core.Resolving.InstanceLookup.Execute()   at Autofac.Core.Resolving.ResolveOperation.GetOrCreateInstance(ISharingLifetimeScope currentOperationScope\', \'Comment 36: IComponentRegistration registration\', \'Comment 37: IEnumerable`1 parameters)   at Autofac.Core.Resolving.ResolveOperation.Execute(IComponentRegistration registration\', \'Comment 38: IEnumerable`1 parameters)   at Autofac.ResolutionExtensions.TryResolveService(IComponentContext context\', \'Comment 39: Service service\', \'Comment 40: IEnumerable`1 parameters\', \'Comment 41: Object& instance)   at Autofac.ResolutionExtensions.ResolveService(IComponentContext context\', \'Comment 42: Service service\', \'Comment 43: IEnumerable`1 parameters)   at Autofac.ResolutionExtensions.Resolve(IComponentContext context\', \'Comment 44: Type serviceType)   at Autofac.Extensions.DependencyInjection.AutofacServiceProvider.GetRequiredService(Type serviceType)   at Microsoft.Extensions.DependencyInjection.ServiceProviderServiceExtensions.GetRequiredService[T](IServiceProvider provider)   at Microsoft.Extensions.DependencyInjection.ServiceProviderServiceExtensions.GetServices[T](IServiceProvider provider)   at Kotrak.Common.Infrastructure.Hosting.Extensions.ApplicationBuilderExtensions.UserIntercontextCommunicationSubscriptions(IApplicationBuilder builder)   at Kotrak.Common.Infrastructure.Hosting.CommonStartup`2.Configure(IApplicationBuilder app\', \'Comment 45: IHostApplicationLifetime applicationLifetime)   at Plant.PCS.BusinessLogic.Infrastructure.Startup.Configure(IApplicationBuilder app\', \'Comment 46: IHostApplicationLifetime applicationLifetime) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\9ecc36be9059f942\\\\\\\\Plant.PCS.BusinessLogic\\\\\\\\Infrastructure\\\\\\\\Startup.cs:line 25   at System.RuntimeMethodHandle.InvokeMethod(Object target\', \'Comment 47: Span`1& arguments\', \'Comment 48: Signature sig\', \'Comment 49: Boolean constructor\', \'Comment 50: Boolean wrapExceptions)   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj\', \'Comment 51: BindingFlags invokeAttr\', \'Comment 52: Binder binder\', \'Comment 53: Object[] parameters\', \'Comment 54: CultureInfo culture)   at Microsoft.AspNetCore.Hosting.ConfigureBuilder.Invoke(Object instance\', ""Comment 55: IApplicationBuilder builder)   at Microsoft.AspNetCore.Hosting.ConfigureBuilder.<>c__DisplayClass4_0.<Build>b__0(IApplicationBuilder builder)   at Microsoft.AspNetCore.Hosting.GenericWebHostBuilder.<>c__DisplayClass15_0.<UseStartup>b__1(IApplicationBuilder app)   at Microsoft.AspNetCore.Mvc.Filters.MiddlewareFilterBuilderStartupFilter.<>c__DisplayClass0_0.<Configure>g__MiddlewareFilterBuilder|0(IApplicationBuilder builder)   at Microsoft.AspNetCore.Server.IIS.Core.IISServerSetupFilter.<>c__DisplayClass2_0.<Configure>b__0(IApplicationBuilder app)   at Microsoft.AspNetCore.HostFilteringStartupFilter.<>c__DisplayClass0_0.<Configure>b__0(IApplicationBuilder app)   at Microsoft.AspNetCore.Hosting.GenericWebHostService.StartAsync(CancellationToken cancellationToken){code}\'"", ""Comment 56: \'Log log{code:java}2023-03-05 13:51:19 (/Plant.PCS.BusinessLogic/SAKDSRV04/18088/1) [Error] Kotrak.Common.Infrastructure.Hosting.BaseStartup - An error occurred while seeding the database.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 57: error: 40 - Could not open a connection to SQL Server) ---> System.ComponentModel.Win32Exception (53): The network path was not found.   at Microsoft.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception\', \'Comment 58: Boolean breakConnection\', \'Comment 59: Action`1 wrapCloseInAction)   at Microsoft.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj\', \'Comment 60: Boolean callerHasConnectionLock\', \'Comment 61: Boolean asyncClose)   at Microsoft.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo\', \'Comment 62: SqlInternalConnectionTds connHandler\', \'Comment 63: Boolean ignoreSniOpenTimeout\', \'Comment 64: Int64 timerExpire\', \'Comment 65: Boolean encrypt\', \'Comment 66: Boolean trustServerCert\', \'Comment 67: Boolean integratedSecurity\', \'Comment 68: Boolean withFailover\', \'Comment 69: SqlAuthenticationMethod authType)   at Microsoft.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo\', \'Comment 70: String newPassword\', \'Comment 71: SecureString newSecurePassword\', \'Comment 72: Boolean ignoreSniOpenTimeout\', \'Comment 73: TimeoutTimer timeout\', \'Comment 74: Boolean withFailover)   at Microsoft.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(ServerInfo serverInfo\', \'Comment 75: String newPassword\', \'Comment 76: SecureString newSecurePassword\', \'Comment 77: Boolean redirectedUserInstance\', \'Comment 78: SqlConnectionString connectionOptions\', \'Comment 79: SqlCredential credential\', \'Comment 80: TimeoutTimer timeout)   at Microsoft.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(TimeoutTimer timeout\', \'Comment 81: SqlConnectionString connectionOptions\', \'Comment 82: SqlCredential credential\', \'Comment 83: String newPassword\', \'Comment 84: SecureString newSecurePassword\', \'Comment 85: Boolean redirectedUserInstance)   at Microsoft.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity\', \'Comment 86: SqlConnectionString connectionOptions\', \'Comment 87: SqlCredential credential\', \'Comment 88: Object providerInfo\', \'Comment 89: String newPassword\', \'Comment 90: SecureString newSecurePassword\', \'Comment 91: Boolean redirectedUserInstance\', \'Comment 92: SqlConnectionString userConnectionOptions\', \'Comment 93: SessionData reconnectSessionData\', \'Comment 94: Boolean applyTransientFaultHandling\', \'Comment 95: String accessToken\', \'Comment 96: DbConnectionPool pool)   at Microsoft.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options\', \'Comment 97: DbConnectionPoolKey poolKey\', \'Comment 98: Object poolGroupProviderInfo\', \'Comment 99: DbConnectionPool pool\', \'Comment 100: DbConnection owningConnection\', \'Comment 101: DbConnectionOptions userOptions)   at Microsoft.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnectionPool pool\', \'Comment 102: DbConnection owningObject\', \'Comment 103: DbConnectionOptions options\', \'Comment 104: DbConnectionPoolKey poolKey\', \'Comment 105: DbConnectionOptions userOptions)   at Microsoft.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject\', \'Comment 106: DbConnectionOptions userOptions\', \'Comment 107: DbConnectionInternal oldConnection)   at Microsoft.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject\', \'Comment 108: DbConnectionOptions userOptions\', \'Comment 109: DbConnectionInternal oldConnection)   at Microsoft.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject\', \'Comment 110: UInt32 waitForMultipleObjectsTimeout\', \'Comment 111: Boolean allowCreate\', \'Comment 112: Boolean onlyOneCheckConnection\', \'Comment 113: DbConnectionOptions userOptions\', \'Comment 114: DbConnectionInternal& connection)   at Microsoft.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject\', \'Comment 115: TaskCompletionSource`1 retry\', \'Comment 116: DbConnectionOptions userOptions\', \'Comment 117: DbConnectionInternal& connection)   at Microsoft.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection\', \'Comment 118: TaskCompletionSource`1 retry\', \'Comment 119: DbConnectionOptions userOptions\', \'Comment 120: DbConnectionInternal oldConnection\', \'Comment 121: DbConnectionInternal& connection)   at Microsoft.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection\', \'Comment 122: DbConnectionFactory connectionFactory\', \'Comment 123: TaskCompletionSource`1 retry\', \'Comment 124: DbConnectionOptions userOptions)   at Microsoft.Data.ProviderBase.DbConnectionClosed.TryOpenConnection(DbConnection outerConnection\', \'Comment 125: DbConnectionFactory connectionFactory\', \'Comment 126: TaskCompletionSource`1 retry\', \'Comment 127: DbConnectionOptions userOptions)   at Microsoft.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry\', \'Comment 128: SqlConnectionOverrides overrides)   at Microsoft.Data.SqlClient.SqlConnection.Open(SqlConnectionOverrides overrides)   at Microsoft.EntityFrameworkCore.SqlServer.Storage.Internal.SqlServerConnection.OpenDbConnection(Boolean errorsExpected)   at Microsoft.EntityFrameworkCore.Storage.RelationalConnection.OpenInternal(Boolean errorsExpected)   at Microsoft.EntityFrameworkCore.Storage.RelationalConnection.Open(Boolean errorsExpected)   at Microsoft.EntityFrameworkCore.SqlServer.Storage.Internal.SqlServerDatabaseCreator.<>c__DisplayClass18_0.<Exists>b__0(DateTime giveUp)   at Microsoft.EntityFrameworkCore.ExecutionStrategyExtensions.<>c__DisplayClass12_0`2.<Execute>b__0(DbContext c\', \'Comment 129: TState s)   at Microsoft.EntityFrameworkCore.SqlServer.Storage.Internal.SqlServerExecutionStrategy.Execute[TState,TResult](TState state\', \'Comment 130: Func`3 operation\', \'Comment 131: Func`3 verifySucceeded)   at Microsoft.EntityFrameworkCore.ExecutionStrategyExtensions.Execute[TState,TResult](IExecutionStrategy strategy\', \'Comment 132: TState state\', \'Comment 133: Func`2 operation\', ""Comment 134: Func`2 verifySucceeded)   at Microsoft.EntityFrameworkCore.SqlServer.Storage.Internal.SqlServerDatabaseCreator.Exists(Boolean retryOnNotExists)   at Microsoft.EntityFrameworkCore.SqlServer.Storage.Internal.SqlServerDatabaseCreator.Exists()   at Microsoft.EntityFrameworkCore.Migrations.HistoryRepository.Exists()   at Microsoft.EntityFrameworkCore.Migrations.Internal.Migrator.Migrate(String targetMigration)   at Microsoft.EntityFrameworkCore.RelationalDatabaseFacadeExtensions.Migrate(DatabaseFacade databaseFacade)   at Kotrak.Common.Infrastructure.EF.DbInitializer.Init()   at Kotrak.Common.Infrastructure.Hosting.CommonStartup`1.OnSeedDatabase(IServiceProvider services)   at Kotrak.Common.Infrastructure.Hosting.CommonStartup`2.OnSeedDatabase(IServiceProvider services)   at Kotrak.Common.Infrastructure.Hosting.CommonStartup`3.OnSeedDatabase(IServiceProvider services)   at Kotrak.Common.Infrastructure.Hosting.BaseStartup.SeedDatabase(IApplicationBuilder builder)ClientConnectionId:00000000-0000-0000-0000-000000000000Error Number:53,State:0,Class:20{code}\'"", \'Comment 135: ""W ogóle to są ostatnie logi :D{code:java}2023-03-05 13:48:45 (/Plant.PCS.BusinessLogic/SAKDSRV04/5104/128) [Error] Kotrak.Integration.InternalStorage.IInternalStorageRepository - Error during System.Collections.Generic.IReadOnlyCollection`1[Kotrak.Integration.InternalStorage.EF.Entities.InboundEntity] Get(Int32) methodSystem.ObjectDisposedException: Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \\\'Dispose\\\' on the context instance\', \'Comment 136: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 137: you should let the dependency injection container take care of disposing context instances.Object name: \'IntercontextCommunicationDbContext\'.   at Microsoft.EntityFrameworkCore.DbContext.CheckDisposed()   at Microsoft.EntityFrameworkCore.DbContext.get_ContextServices()   at Microsoft.EntityFrameworkCore.DbContext.get_ChangeTracker()   at Microsoft.EntityFrameworkCore.Query.CompiledQueryCacheKeyGenerator.GenerateCacheKeyCore(Expression query"", \'Comment 138: Boolean async)   at Microsoft.EntityFrameworkCore.Query.RelationalCompiledQueryCacheKeyGenerator.GenerateCacheKeyCore(Expression query\', \'Comment 139: Boolean async)   at Microsoft.EntityFrameworkCore.SqlServer.Query.Internal.SqlServerCompiledQueryCacheKeyGenerator.GenerateCacheKey(Expression query\', ""Comment 140: Boolean async)   at Microsoft.EntityFrameworkCore.Query.Internal.QueryCompiler.Execute[TResult](Expression query)   at Microsoft.EntityFrameworkCore.Query.Internal.EntityQueryable`1.GetEnumerator()   at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection)   at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source)   at Castle.Proxies.Invocations.IInternalStorageRepository`1_Get_8.InvokeMethodOnTarget()   at Castle.DynamicProxy.AbstractInvocation.Proceed()   at Kotrak.Common.Infrastructure.Interceptors.LoggingInterceptor`1.Intercept(IInvocation invocation)2023-03-05 13:48:45 (/Plant.PCS.BusinessLogic/SAKDSRV04/5104/128) [Error] Kotrak.Integration.InternalStorage.IInternalStorageRepository - Error during System.Collections.Generic.IReadOnlyCollection`1[Kotrak.Integration.InternalStorage.EF.Entities.InboundEntity] Get(Int32) methodSystem.ObjectDisposedException: Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 141: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 142: you should let the dependency injection container take care of disposing context instances.Object name: \'IntercontextCommunicationDbContext\'.   at Microsoft.EntityFrameworkCore.DbContext.CheckDisposed()   at Microsoft.EntityFrameworkCore.DbContext.get_ContextServices()   at Microsoft.EntityFrameworkCore.DbContext.get_ChangeTracker()   at Microsoft.EntityFrameworkCore.Query.CompiledQueryCacheKeyGenerator.GenerateCacheKeyCore(Expression query"", \'Comment 143: Boolean async)   at Microsoft.EntityFrameworkCore.Query.RelationalCompiledQueryCacheKeyGenerator.GenerateCacheKeyCore(Expression query\', \'Comment 144: Boolean async)   at Microsoft.EntityFrameworkCore.SqlServer.Query.Internal.SqlServerCompiledQueryCacheKeyGenerator.GenerateCacheKey(Expression query\', \'Comment 145: Boolean async)   at Microsoft.EntityFrameworkCore.Query.Internal.QueryCompiler.Execute[TResult](Expression query)   at Microsoft.EntityFrameworkCore.Query.Internal.EntityQueryable`1.GetEnumerator()   at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection)   at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source)   at Castle.Proxies.Invocations.IInternalStorageRepository`1_Get_8.InvokeMethodOnTarget()   at Castle.DynamicProxy.AbstractInvocation.Proceed()   at Kotrak.Common.Infrastructure.Interceptors.LoggingInterceptor`1.Intercept(IInvocation invocation){code}""\', \'Comment 146: \\\'Druga linia nie odp!image-2023-03-05-18-59-23-028.png!{code:java}2023-03-04 15:26:19 (/Plant.PCS.BusinessLogic2/SAKDSRV04/13660/202) [Error] Microsoft.EntityFrameworkCore.Database.Connection - An error occurred using the connection to database \\\\\\\'""DHExchange70""\\\\\\\' on server \\\\\\\'""10.0.23.10""\\\\\\\'.2023-03-04 15:26:19 (/Plant.PCS.BusinessLogic2/SAKDSRV04/13660/202) [Error] Microsoft.EntityFrameworkCore.Query - An exception occurred while iterating over the results of a query for context type \\\\\\\'""Plant.PCS.BusinessLogic.Infrastructure.EF.PcsDbContext""\\\\\\\'.""""""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 147: error: 40 - Could not open a connection to SQL Server) ---> System.ComponentModel.Win32Exception (53): The network path was not found.   at Microsoft.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj\', \'Comment 148: Boolean callerHasConnectionLock\', \'Comment 149: Boolean asyncClose)   at Microsoft.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo\', \'Comment 150: SqlInternalConnectionTds connHandler\', \'Comment 151: Boolean ignoreSniOpenTimeout\', \'Comment 152: Int64 timerExpire\', \'Comment 153: Boolean encrypt\', \'Comment 154: Boolean trustServerCert\', \'Comment 155: Boolean integratedSecurity\', \'Comment 156: Boolean withFailover\', \'Comment 157: SqlAuthenticationMethod authType)   at Microsoft.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo\', \'Comment 158: String newPassword\', \'Comment 159: SecureString newSecurePassword\', \'Comment 160: Boolean ignoreSniOpenTimeout\', \'Comment 161: TimeoutTimer timeout\', \'Comment 162: Boolean withFailover)   at Microsoft.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(ServerInfo serverInfo\', \'Comment 163: String newPassword\', \'Comment 164: SecureString newSecurePassword\', \'Comment 165: Boolean redirectedUserInstance\', \'Comment 166: SqlConnectionString connectionOptions\', \'Comment 167: SqlCredential credential\', \'Comment 168: TimeoutTimer timeout)   at Microsoft.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(TimeoutTimer timeout\', \'Comment 169: SqlConnectionString connectionOptions\', \'Comment 170: SqlCredential credential\', \'Comment 171: String newPassword\', \'Comment 172: SecureString newSecurePassword\', \'Comment 173: Boolean redirectedUserInstance)   at Microsoft.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity\', \'Comment 174: SqlConnectionString connectionOptions\', \'Comment 175: SqlCredential credential\', \'Comment 176: Object providerInfo\', \'Comment 177: String newPassword\', \'Comment 178: SecureString newSecurePassword\', \'Comment 179: Boolean redirectedUserInstance\', \'Comment 180: SqlConnectionString userConnectionOptions\', \'Comment 181: SessionData reconnectSessionData\', \'Comment 182: Boolean applyTransientFaultHandling\', \'Comment 183: String accessToken\', \'Comment 184: DbConnectionPool pool)   at Microsoft.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options\', \'Comment 185: DbConnectionPoolKey poolKey\', \'Comment 186: Object poolGroupProviderInfo\', \'Comment 187: DbConnectionPool pool\', \'Comment 188: DbConnection owningConnection\', \'Comment 189: DbConnectionOptions userOptions)   at Microsoft.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnectionPool pool\', \'Comment 190: DbConnection owningObject\', \'Comment 191: DbConnectionOptions options\', \'Comment 192: DbConnectionPoolKey poolKey\', \'Comment 193: DbConnectionOptions userOptions)   at Microsoft.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject\', \'Comment 194: DbConnectionOptions userOptions\', \'Comment 195: DbConnectionInternal oldConnection)   at Microsoft.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject\', \'Comment 196: DbConnectionOptions userOptions\', \'Comment 197: DbConnectionInternal oldConnection)   at Microsoft.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject\', \'Comment 198: UInt32 waitForMultipleObjectsTimeout\', \'Comment 199: Boolean allowCreate\', \'Comment 200: Boolean onlyOneCheckConnection\', \'Comment 201: DbConnectionOptions userOptions\', \'Comment 202: DbConnectionInternal& connection)   at Microsoft.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject\', \'Comment 203: TaskCompletionSource`1 retry\', \'Comment 204: DbConnectionOptions userOptions\', \'Comment 205: DbConnectionInternal& connection)   at Microsoft.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection\', \'Comment 206: TaskCompletionSource`1 retry\', \'Comment 207: DbConnectionOptions userOptions\', \'Comment 208: DbConnectionInternal oldConnection\', \'Comment 209: DbConnectionInternal& connection)   at Microsoft.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection\', \'Comment 210: DbConnectionFactory connectionFactory\', \'Comment 211: TaskCompletionSource`1 retry\', \'Comment 212: DbConnectionOptions userOptions)   at Microsoft.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry\', \'Comment 213: SqlConnectionOverrides overrides)   at Microsoft.Data.SqlClient.SqlConnection.Open(SqlConnectionOverrides overrides)   at Microsoft.EntityFrameworkCore.Storage.RelationalConnection.OpenInternal(Boolean errorsExpected)   at Microsoft.EntityFrameworkCore.Storage.RelationalConnection.Open(Boolean errorsExpected)   at Microsoft.EntityFrameworkCore.Storage.RelationalCommand.ExecuteReader(RelationalCommandParameterObject parameterObject)   at Microsoft.EntityFrameworkCore.Query.Internal.FromSqlQueryingEnumerable`1.Enumerator.InitializeReader(Enumerator enumerator)   at Microsoft.EntityFrameworkCore.SqlServer.Storage.Internal.SqlServerExecutionStrategy.Execute[TState,TResult](TState state\', \'Comment 214: Func`3 operation\', \'Comment 215: Func`3 verifySucceeded)   at Microsoft.EntityFrameworkCore.Query.Internal.FromSqlQueryingEnumerable`1.Enumerator.MoveNext()ClientConnectionId:00000000-0000-0000-0000-000000000000Error Number:53,State:0,Class:20""Microsoft.Data.SqlClient.SqlException (0x80131904): A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider\', \'Comment 216: error: 40 - Could not open a connection to SQL Server) ---> System.ComponentModel.Win32Exception (53): The network path was not found.   at Microsoft.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj\', \'Comment 217: Boolean callerHasConnectionLock\', \'Comment 218: Boolean asyncClose)   at Microsoft.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo\', \'Comment 219: SqlInternalConnectionTds connHandler\', \'Comment 220: Boolean ignoreSniOpenTimeout\', \'Comment 221: Int64 timerExpire\', \'Comment 222: Boolean encrypt\', \'Comment 223: Boolean trustServerCert\', \'Comment 224: Boolean integratedSecurity\', \'Comment 225: Boolean withFailover\', \'Comment 226: SqlAuthenticationMethod authType)   at Microsoft.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo\', \'Comment 227: String newPassword\', \'Comment 228: SecureString newSecurePassword\', \'Comment 229: Boolean ignoreSniOpenTimeout\', \'Comment 230: TimeoutTimer timeout\', \'Comment 231: Boolean withFailover)   at Microsoft.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(ServerInfo serverInfo\', \'Comment 232: String newPassword\', \'Comment 233: SecureString newSecurePassword\', \'Comment 234: Boolean redirectedUserInstance\', \'Comment 235: SqlConnectionString connectionOptions\', \'Comment 236: SqlCredential credential\', \'Comment 237: TimeoutTimer timeout)   at Microsoft.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(TimeoutTimer timeout\', \'Comment 238: SqlConnectionString connectionOptions\', \'Comment 239: SqlCredential credential\', \'Comment 240: String newPassword\', \'Comment 241: SecureString newSecurePassword\', \'Comment 242: Boolean redirectedUserInstance)   at Microsoft.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity\', \'Comment 243: SqlConnectionString connectionOptions\', \'Comment 244: SqlCredential credential\', \'Comment 245: Object providerInfo\', \'Comment 246: String newPassword\', \'Comment 247: SecureString newSecurePassword\', \'Comment 248: Boolean redirectedUserInstance\', \'Comment 249: SqlConnectionString userConnectionOptions\', \'Comment 250: SessionData reconnectSessionData\', \'Comment 251: Boolean applyTransientFaultHandling\', \'Comment 252: String accessToken\', \'Comment 253: DbConnectionPool pool)   at Microsoft.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options\', \'Comment 254: DbConnectionPoolKey poolKey\', \'Comment 255: Object poolGroupProviderInfo\', \'Comment 256: DbConnectionPool pool\', \'Comment 257: DbConnection owningConnection\', \'Comment 258: DbConnectionOptions userOptions)   at Microsoft.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnectionPool pool\', \'Comment 259: DbConnection owningObject\', \'Comment 260: DbConnectionOptions options\', \'Comment 261: DbConnectionPoolKey poolKey\', \'Comment 262: DbConnectionOptions userOptions)   at Microsoft.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject\', \'Comment 263: DbConnectionOptions userOptions\', \'Comment 264: DbConnectionInternal oldConnection)   at Microsoft.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject\', \'Comment 265: DbConnectionOptions userOptions\', \'Comment 266: DbConnectionInternal oldConnection)   at Microsoft.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject\', \'Comment 267: UInt32 waitForMultipleObjectsTimeout\', \'Comment 268: Boolean allowCreate\', \'Comment 269: Boolean onlyOneCheckConnection\', \'Comment 270: DbConnectionOptions userOptions\', \'Comment 271: DbConnectionInternal& connection)   at Microsoft.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject\', \'Comment 272: TaskCompletionSource`1 retry\', \'Comment 273: DbConnectionOptions userOptions\', \'Comment 274: DbConnectionInternal& connection)   at Microsoft.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection\', \'Comment 275: TaskCompletionSource`1 retry\', \'Comment 276: DbConnectionOptions userOptions\', \'Comment 277: DbConnectionInternal oldConnection\', \'Comment 278: DbConnectionInternal& connection)   at Microsoft.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection\', \'Comment 279: DbConnectionFactory connectionFactory\', \'Comment 280: TaskCompletionSource`1 retry\', \'Comment 281: DbConnectionOptions userOptions)   at Microsoft.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry\', \'Comment 282: SqlConnectionOverrides overrides)   at Microsoft.Data.SqlClient.SqlConnection.Open(SqlConnectionOverrides overrides)   at Microsoft.EntityFrameworkCore.Storage.RelationalConnection.OpenInternal(Boolean errorsExpected)   at Microsoft.EntityFrameworkCore.Storage.RelationalConnection.Open(Boolean errorsExpected)   at Microsoft.EntityFrameworkCore.Storage.RelationalCommand.ExecuteReader(RelationalCommandParameterObject parameterObject)   at Microsoft.EntityFrameworkCore.Query.Internal.FromSqlQueryingEnumerable`1.Enumerator.InitializeReader(Enumerator enumerator)   at Microsoft.EntityFrameworkCore.SqlServer.Storage.Internal.SqlServerExecutionStrategy.Execute[TState,TResult](TState state\', \'Comment 283: Func`3 operation\', ""Comment 284: Func`3 verifySucceeded)   at Microsoft.EntityFrameworkCore.Query.Internal.FromSqlQueryingEnumerable`1.Enumerator.MoveNext()ClientConnectionId:00000000-0000-0000-0000-000000000000Error Number:53,State:0,Class:20{code}\'"", ""Comment 285: \'Ani Windows ani SQl authentication!image-2023-03-05-19-04-14-767.png!\'"", ""Comment 286: \'Hi ReyOn our side we see PCS issue connection"", \'Comment 287: it was not working since 13:45. Can you please check with PCS provider in the mean time? Additionally\', ""Comment 288: I cannot connect to exchange.Regards\'"", \'Comment 289: ""Servers where shutdown while factory wa not running.I\\\'m able to connect to the exchange !image-2!""\', ""Comment 290: \'I see the PrO are in the exchange Can you tell me what you did?!image-3!\'"", ""Comment 291: \'Yes"", ""Comment 292: now it is available for me as well and I can see Orders:!image-2023-03-05-19-35-38-435.png!\'"", ""Comment 293: \'Errors in logs indicated issue with connection. I just restarted application pools.Regards\'"", ""Comment 294: \'Rey"", ""Comment 295: please confirm if we can close this task :)\'"", ""Comment 296: \'Line 2 ruszył!image-2023-03-05-19-41-58-743.png!\'"", \'Comment 297: ""I\\\'m waiting for the factory to confirm.""\', ""Comment 298: \'Sure. Waiting for their feedback then\'"", ""Comment 299: \'All good. Thank you for the help. Ticket can be closed\'"", ""Comment 300: \'Thank you\']""]\nRelated Issues:\n[]\n\n### End'}"
349,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8683\n\n### Instruction:\nThe system is not locking automatically lot number expired, I checked the configuration and is enable.\r\n\r\n Could you check why is not working?\r\n\r\nThank you\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: \'https://helpdesk.kotrak.com/browse/DAP-13384\'"", ""Comment 4: \'HelloI can see that similar issue is alreadyprocessed according tohttps://helpdesk.kotrak.com/browse/DGS-8668Please be informed that we have forwarded the issue to the development team in order to internal analysis.May we close this task and work in this first task only ?\'"", \'Comment 5: ""Sorry Agnieszka\', ""Comment 6: I didn\'t see the task opened by Maicon. Yes"", \'Comment 7: you can close this one. Thank you""]\']\nRelated Issues:\n[\'DGS-8668\', \'DAP-13382\', \'DAP-13384\']\n\n### End'}"
350,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8682\n\n### Instruction:\nwe have problem in report MaterialRequirementPlaningForRawMaterials, system is not considering orders IO Out to calculate the report.\r\n\r\nexample IO IO-637782830/23/TRN\r\nitem 21560 - 2000kg - delivery date 16/March/2023\r\nit\'s not available in report\r\n\r\n\r\nCould you check why we have this error and fix it? It\'s urgent have correct information in this report, because we schedule purchase orders and transfers using this report.\r\n\r\n\r\nThank you\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!!image-1!!image-2![^List - 2023-03-03T134053.344.xlsx] _(17 kB)_\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Hello on your screen there was no warehouse src code"", \'Comment 4: by now it is :Could you check it again also\', ""Comment 5: what exact dates You use during report generation ?!image-2023-03-03-18-35-56-614.png!\'"", \'Comment 6: ""Hello,I was using view per element and in this screen is not whowing warehouse src code\', ""Comment 7: I don\'t know why"", ""Comment 8: do you know?about period I\'m using is 01/Feb/23 till 30/ March/23"", \'Comment 9: for check orders and generate report.""\', ""Comment 10: \'!image-3!\'"", ""Comment 11: \'Hello guysI think I found the error:The report lists only the RM that are in RawMaterials internal table on the procedure.So"", \'Comment 12: if there are any RM tht is not present in RawMaterials\', \'Comment 13: the query will not list it because of the JOINs.You can to check it using *MaterialRequirementPlaningForRawMaterials_2* from _2023-03-01_ to _2023-03-31_ and looking for item *21560*.We have some SO and IO for it\', ""Comment 14: but it is not being listed in the query result.Maybe this can help you.Thank you very much\'"", ""Comment 15: \'!image-2023-03-06-08-38-06-852.png!\'"", \'Comment 16: ""hej prośba o weryfikacja z tego co widze procedury lączenie ejst po tabelach z recepturami a podany io jak patrze nie ma recipe id na vt - ale może się mylę \', \'Comment 17: prosze o weryfikacje proceduryselect * from OrderElements where id=\\\'29E4A054-6ACD-4249-B6DA-57B6C8911E2B\\\' select * from OrderElements where id=\\\'29E4A054-6ACD-4249-B6DA-57B6C8911E2B\\\' select * from VehicleTicketBulkDispatchElements where OrderId=\\\'29E4A054-6ACD-4249-B6DA-57B6C8911E2B\\\'!image-2023-03-06-08-54-39-276.png!""\', \'Comment 18: ""Tak has been forwarded to the developers\\\' department""\', ""Comment 19: \'Raport ten w RC podobno jest już poprawiona. Procedura będzie miała dopisane BR w nazwie. Do sprawdzenia + wgrać poprawne procedury na innych fabrykach + dodać do Bitbucket.\'"", ""Comment 20: \'[~agnieszka.januszewska@kotrak.com]analizowałem ten temat z [~maciej.dobrzanski@kotrak.com]. Pan Maicon edytował istniejący SQL. Dokonał zmian których wcześniej nie było. Jeśli klientowi zwraca to odpowiednie wyniki to tak możemy zostawić. Na pozostałych fabrykach mają wersję 8.3 (więc pewnie zmieniony SQL też tam zadziała)"", \'Comment 21: natomiast w Caruaru jest 5.3 (tutaj mała szansa\', \'Comment 22: że będzie działać)._I teraz tak\', \'Comment 23: możesz ewentualnie napisać\', \'Comment 24: że zmienione procedury z RC możesz wgrać na inne fabryki oraz założymy task w projekcie DAP\', ""Comment 25: aby zaktualizować procedury w projekcie._\'"", ""Comment 26: \'From our analysis it appears that the request was modified by you"", ""Comment 27: if such a form works correctly in Rio Claro it can be uploaded in other factories. Can the ticket be closed?\'"", ""Comment 28: \'Can the ticket be closed?\'"", ""Comment 29: \'[~agnieszka.januszewska@kotrak.com] nie robiłaś rozumiem aktualizacji na innych fabrykach? Więc jeśli nie zmieniałaś"", ""Comment 30: trzeba też klienta poinformować że nic nie wykonaliśmy.Dodatkowo w ramach tego DGS przed jego zamknięciem trzeba założyć DAP - tutaj możesz się zgłosić do [~maciej.buchacz@kotrak.com] - i potrzebujemy dodać do Bitbucket te ich zmiany.\'"", \'Comment 31: ""Hi AgnieszkaWe modified only the report DHBR_... your we didn\\\'t.Can you please fix yours?Thank you""\', ""Comment 32: \'[~maciej.buchacz@kotrak.com]czy możesz założyć DAP do tego taska.\'"", ""Comment 33: \'We will create separate dap task for that.\'"", ""Comment 34: \'Procedury z DHBR"", \'Comment 35: to procedury pobrane od klienta\', \'Comment 36: natomiast procedury bez tego przedrostku zostały zmodyfikowane na podstawie otrzymanych procedur. Procedury zostały zaktualizowane na środowiskach: TO[Prod]\', ""Comment 37: IT[Prod],AP[Prod] i RC[Prod].GU[Prod] nie został zaktualizowany z uwagi na brak uprawnień do logowania na ten serwer[^DHBR_MaterialRequirementPlaningForRawMaterials.sql] [^DHBR_MaterialRequirementPlaningForRawMaterials_2.sql] [^DHBR_MaterialRequirementPlaningForReadyProducts.sql] [^DHBR_MaterialRequirementPlaningForReadyProducts_2.sql] [^MaterialRequirementPlaningForRawMaterials.sql] [^MaterialRequirementPlaningForRawMaterials_2.sql] [^MaterialRequirementPlaningForReadyProducts.sql] [^MaterialRequirementPlaningForReadyProducts_2.sql]\'"", ""Comment 38: \'wyglada na to ze na guarapes nie ma ver.2!image-2023-04-03-12-42-58-797.png!\'"", ""Comment 39: \'Procedures have been updated on the following servers: Toledo"", ""Comment 40: Iteberai,Guararapes,Rio Claro. The procedures we added are our procedures do not have the DHBR prefix.!image-2023-04-03-13-08-50-486.png!Please verify.\'"", ""Comment 41: \'[~marcin.kleszcz@kotrak.com]w gurarapes nie było procek w wersji v2. więc zmieniłam to co było i na wszelki w zrobiłam backup"", ""Comment 42: stworzyć 2 dodtakowe procki czy zostawić tak jak jest?!image-2023-04-03-13-10-48-120.png!\'"", ""Comment 43: \'[~agnieszka.januszewska@kotrak.com] v2 jest pod drugi BU w RC"", ""Comment 44: dlatego występuje tylko w RC.W tych procedurach należy podać odpowiedni BU id. W GU ustawiłaś odpowiedni?\'"", ""Comment 45: \'podmieniłam\'"", \'Comment 46: ""HiWell\', ""Comment 47: the update was only to copy and past our DHBR_ procedure to yours.The proof that this doesn\'t work is because you are setting VARCHAR value into DATETIME variable with no cast function"", \'Comment 48: which causes inconsistency in the result.OK! No problem.You can close this task.Thank you very much!!image-4!""]\']\nRelated Issues:\n[\'DAP-13502\']\n\n### End'}"
351,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8681\n\n### Instruction:\nRecipe 510016 is accepted in DHC but does not arrive in DHP Utrecht.\r\n\r\nI tried to re-send it with zero succes.\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: \'Recipe was synchronized - please verify.!image-2023-03-03-17-47-08-551.png!\'"", ""Comment 3: \'brakowało w dhc service dhhitema i itema[[DHC][DHCSERVICE] Brak DHHITemu w DHCService|onenote:https://kotrak.sharepoint.com/sites/erpasysta/Shared%20Documents/Baza%20wiedzy/Baza%20Wiedzy%20-%20ERPSD/Klienci/DEHEUS/DEHEUS%20APPLICATIONS/Holandia%20Premix%20i%20AS400/Baz%20wiedzy%20z%20AS400.one#%5bDHC%5d%5bDHCSERVICE%5d%20Brak%20DHHITemu%20w%20DHCService&section-id=\\\\\\\\{9BB564BA-0B58-4580-B9E0-F3CF9D6D80A7}&page-id=\\\\\\\\{8F28118E-19AC-49AA-BE70-8033239AB278}&end] ([Widok sieci Web|https://kotrak.sharepoint.com/sites/erpasysta/_layouts/OneNote.aspx?id=%2Fsites%2Ferpasysta%2FShared%20Documents%2FBaza%20wiedzy%2FBaza%20Wiedzy%20-%20ERPSD&wd=target%28Klienci%2FDEHEUS%2FDEHEUS%20APPLICATIONS%2FHolandia%20Premix%20i%20AS400%2FBaz%20wiedzy%20z%20AS400.one%7C9BB564BA-0B58-4580-B9E0-F3CF9D6D80A7%2F%5BDHC%5D%5BDHCSERVICE%5D%20Brak%20DHHITemu%20w%20DHCService%7C8F28118E-19AC-49AA-BE70-8033239AB278%2F%29])\'"", ""Comment 4: \'I noticed both versions of the recipe arrived in DHP.You can close the ticket"", ""Comment 5: thanks for the support.Regards,Rob\']""]\nRelated Issues:\n[]\n\n### End'}"
352,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8680\n\n### Instruction:\nI set \'tarwe\' and \'feed\' to the next round and on the line with \'tarwe\' the value = 0€, why?\r\n customer in MAS NL = 200244 round = 200244/0319/0001\r\n I will send a screenshot to Damian\r\n\r\n\xa0\r\n\r\n!image-2023-03-03-14-57-05-954.png!\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 2: ""Hello,On this Feed sale are lines without proper values\', \'Comment 3: there are no values in column \\\'Price\\\' and \\\'VAT Rate\\\' and system are not able to calculate moving feed.System calculate \\\'Weight to move\\\' * \\\'Price\\\' and also by \\\'VAT Rate\\\' to calculate VAT Value.!image-2023-03-03-15-12-46-541.png!Regards""\', ""Comment 4: \'Is this solved?\'"", \'Comment 5: ""It was caused by manually added line without values\', \'Comment 6: we didn\\\'t change anything in the system.[~khuibers@deheus.com]please inform us that everything is right and we can close this task.""\', ""Comment 7: \'[~khuibers@deheus.com]could we close the task?\'"", ""Comment 8: \'Yes can be closed\']""]\nRelated Issues:\n[]\n\n### End'}"
353,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8679\n\n### Instruction:\nWhen a credit is created it should just create a negative copy. Now it seems when the credit PI is created in Intense the system checks again the BP Tax Group (which has been changed in the mean time), but that should not be the case.\r\n\r\n\xa0\r\n\r\nCPI-M/2023/0148 !image-2023-03-03-11-29-14-074.png!\r\n\r\nPI-RLM/2023/0403\r\n\r\n!image-2023-03-03-11-28-57-185.png!\n\n### Response:\n[\'Comment 1: [""Wygląda na to\', \'Comment 2: że dokumenty są skorygowane przez akcję \\\'Create reverse SR\\\' i akcja \\\'Create PI from PI (Reverse SR)\\\' działa inaczej niż zwykła akcja do tworzenia korekty PI \\\'Create correction Invoice from PI (MAS NL)\\\' i niepotrzebnie przeliczane są niektóre wartości zamiast być skorygowane względem pierwotnego dokumentu.Do sprawdzaenia akcje korygowania dokumentów dla Reverse SR w MAS NL i MAS BE (zarówno korekty PI jak i SI)!image-2023-03-03-11-32-30-447.png! * Create PI from PI (Reverse SR)!image-2023-03-03-11-35-20-525.png! * Create correction Invoice from PI (MAS NL)!image-2023-03-03-11-34-41-372.png!""\', ""Comment 3: \'Do przygotowania zestawienie faktur korekt"", ""Comment 4: które mogą się różnić od oryginalnych faktury korygowanych i np. BP TAX Group jest inne na obu dokumentach.!image-2023-03-03-13-58-50-015.png!\'"", \'Comment 5: ""Functionality of reversing SR has been modified (like for invoices created not from SR\\\'s).Now when PI and SI is credited\', \'Comment 6: values of BP TAX Group and other values which should be always the same like on original invoice are copied for Credit invoice.This is implemented on test and production environment as well\', \'Comment 7: for MAS NL and MAS BE sector.You can verify it.We will prepare also report about credit and credited invoices where elements are different\', \'Comment 8: and we\\\'ll attach report to this task.Regards""\', ""Comment 9: \'Yes"", ""Comment 10: please show me the report.\'"", ""Comment 11: \'Here is a report with source invoices and credit invoices with different VAT Rate and BP TAX Group on elements.[^DGS-8679_credited_invoices_report.xlsx]Total there are 16 cases when this values are different.Please let us know that should we change VAT Rate and BP TAX Group for credit invoices.Regards\'"", \'Comment 12: ""zapytanie pod raport z ExcelaSELECT s.Doc_FullNumber AS \\\'Number source\\\',s.Doc_ID AS \\\'ID source\\\',c.Doc_FullNumber AS \\\'Number credit\\\',c.Doc_ID AS \\\'ID credit\\\',se.Del_SeqNo AS \\\'Elm No source\\\',ce.Del_SeqNo AS \\\'Elm No credit\\\',(SELECT Itm_Code FROM Items WHERE Itm_ID = se.Del_ItmID) AS \\\'Item source\\\',(SELECT Itm_Code FROM Items WHERE Itm_ID = ce.Del_ItmID) AS \\\'Item credit\\\',se.Del_VATRate AS \\\'VAT Rate source\\\',ce.Del_VATRate AS \\\'VAT Rate credit\\\',CASE WHEN se.Del_VATRate != ce.Del_VATRate THEN 1 END AS \\\'VAT Rate difference\\\',(SELECT DIC_Svalue FROM Dictionaries WHERE DIC_ID = se.Del_IntColumn14) AS \\\'BP TAX Group source\\\',(SELECT DIC_Svalue FROM Dictionaries WHERE DIC_ID =ce.Del_IntColumn14) AS \\\'BP TAX Group credit\\\',CASE WHEN se.Del_IntColumn14 != ce.Del_IntColumn14 THEN 1 END AS \\\'BP TAX GROUP difference\\\'FROM Documents AS s JOIN Documents AS c ON c.Doc_LeadingDocID = s.Doc_IDJOIN DocElems AS se ON s.Doc_ID = se.Del_DocIDJOIN DocElems AS ce ON c.Doc_ID = ce.Del_DocIDWHEREs.Doc_DdfID IN (13\', \'Comment 13: 14\', \'Comment 14: 42\', \'Comment 15: 43)AND c.Doc_DdfID IN (13\', \'Comment 16: 14\', \'Comment 17: 42\', \'Comment 18: 43)AND s.Doc_DdfID = c.Doc_DdfIDAND c.Doc_IntColumn2 = 1AND ABS(ce.Del_ItmID) = ABS(se.Del_ItmID)AND ABS(ISNULL(ce.Del_Weight,0)) = ABS(ISNULL(se.Del_Weight,0))AND ABS(ISNULL(ce.Del_Price\', \'Comment 19: 0)) = ABS(ISNULL(se.Del_Price,0))AND (se.Del_VATRate != ce.Del_VATRateOR se.Del_IntColumn14 != ce.Del_IntColumn14ORse.Del_IntColumn6 != ce.Del_IntColumn6ORse.Del_ShortStringColumn5 != ce.Del_ShortStringColumn5)ORDER BY [Number source]""\', ""Comment 20: \'Can be closed.\']""]\nRelated Issues:\n[]\n\n### End'}"
354,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8678\n\n### Instruction:\nHi\r\n\r\nDHP is out.\r\nWe found ajanuszewska logged in this server.\r\nNow everything is off.\r\n\r\nFactory is stopped\r\n\r\nPlease help\r\n\r\nThanks\n\n### Response:\n[""Comment 1: [\'!image!!image-1!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'!image-2!\'"", ""Comment 4: \'Please check it all work ok now,\'"", ""Comment 5: \'Hi AgnieszkaWe are testing reports"", ""Comment 6: but seems somethig is not working yet:!image-3!\'"", ""Comment 7: \'Now is working. Do you know why we have the error?\'"", ""Comment 8: \'Hi AgnieszkaSSRS are online too.We are now waiting for instructions about folder permissions.Thank you\'"", ""Comment 9: \'there were problems with permissions on folder Kotrak"", \'Comment 10: and DHP_IIS\', ""Comment 11: it also caused before that problem with generating xml files it seems to be the firstthere was not group users in this properties : !image-2023-03-02-18-56-00-746.png!\'"", ""Comment 12: \'May we close the task ?\'"", \'Comment 13: ""HiThat\\\'s weird. No folder permission were changed from our side.Well\', ""Comment 14: so there\'s nothing for me to do know about it"", \'Comment 15: right?In that case\', \'Comment 16: Yes! You can close this taskThank you very much""\', \'Comment 17: ""[~mberbert@deheus.com]  Probably IT shared main folder dhp3.0 instead of XML folder. During this option - Sharing - did IT delete permission for group \\\'Users\\\' ?!image-2023-03-03-12-36-51-930!!image-2023-03-03-12-42-04-919!""\', ""Comment 18: \'[[DHP 3.0] brak logów tekstowych dla modułów. Nieaktualne logi.|onenote:https://kotrak.sharepoint.com/sites/erpasysta/Shared%20Documents/Baza%20wiedzy/Baza%20Wiedzy%20-%20ERPSD/Klienci/DEHEUS/DEHEUS%20APPLICATIONS/Brazil/Baza%20wiedzy.one#%5bDHP%203.0%5d%20brak%20log%C3%B3w%20tekstowych%20dla%20modu%C5%82%C3%B3w.%20Nieaktualne&section-id=\\\\\\\\{05DF1439-683C-45FE-8260-61E2EC66DC91}&page-id=\\\\\\\\{91116E2F-1387-4F03-B87C-A3F9B99FF906}&end] ([Widok sieci Web|https://kotrak.sharepoint.com/sites/erpasysta/_layouts/OneNote.aspx?id=%2Fsites%2Ferpasysta%2FShared%20Documents%2FBaza%20wiedzy%2FBaza%20Wiedzy%20-%20ERPSD&wd=target%28Klienci%2FDEHEUS%2FDEHEUS%20APPLICATIONS%2FBrazil%2FBaza%20wiedzy.one%7C05DF1439-683C-45FE-8260-61E2EC66DC91%2F%5BDHP%203.0%5D%20brak%20log%C3%B3w%20tekstowych%20dla%20modu%C5%82%C3%B3w.%20Nieaktualne%7C91116E2F-1387-4F03-B87C-A3F9B99FF906%2F%29])\']""]\nRelated Issues:\n[\'DGS-8706\']\n\n### End'}"
355,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8677\n\n### Instruction:\nwe have problem to generate XML, system is showing error message when we click in Generate XML after add all information.\r\nAO-0002/03/23-90\r\n\r\nIt\'s urgent fix to send for customer the result.\r\n\n\n### Response:\n[""Comment 1: [\'!image!!MicrosoftTeams-image (55)!\'"", ""Comment 2: \'D:\\\\\\\\Kotrak\\\\\\\\dhp30_IIS\\\\\\\\XML\'"", \'Comment 3: \\\'2023-03-02 10:55:02 (ec169787-bcfe-4de8-b08f-bb25637081cd/Plant.QAM.BusinessLogic/BR-1-SV-VM0702/23916/74) [Error] Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware - Error during request{ ""scheme"": ""http""\', \'Comment 4: ""host"": { ""Value"": ""br-1-sv-vm0702:84""\', \'Comment 5: ""HasValue"": true\', \'Comment 6: ""Host"": ""br-1-sv-vm0702""\', \'Comment 7: ""Port"": 84 }\', \'Comment 8: ""path"": ""/api/analyses/order/exportXml""\', \'Comment 9: ""queryString"": []\', \'Comment 10: ""requestBody"": ""\\\\\\\\{\\\\\\\\""directoryPath\\\\\\\\"":\\\\\\\\""D:\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\Kotrak\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\dhp30_IIS\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\XML\\\\\\\\"",\\\\\\\\""package\\\\\\\\"":\\\\\\\\""PROFI\\\\\\\\"",\\\\\\\\""advice\\\\\\\\"":\\\\\\\\""Normal\\\\\\\\"",\\\\\\\\""toInvoice\\\\\\\\"":false,\\\\\\\\""grassCut\\\\\\\\"":\\\\\\\\""1\\\\\\\\"",\\\\\\\\""description\\\\\\\\"":\\\\\\\\""Silagem de Milho\\\\\\\\"",\\\\\\\\""farmerCompany\\\\\\\\"":\\\\\\\\""Marcelo Jose do Prado\\\\\\\\"",\\\\\\\\""farmerPoBox\\\\\\\\"":\\\\\\\\""-\\\\\\\\"",\\\\\\\\""farmerCity\\\\\\\\"":\\\\\\\\""Santa Rita D´Oeste\\\\\\\\"",\\\\\\\\""farmerTin\\\\\\\\"":\\\\\\\\""-\\\\\\\\"",\\\\\\\\""farmerStreet\\\\\\\\"":\\\\\\\\""Sitio NS Auxiliadora\\\\\\\\"",\\\\\\\\""lotPitField\\\\\\\\"":\\\\\\\\""Silo Compra\\\\\\\\"",\\\\\\\\""typeCultivar\\\\\\\\"":\\\\\\\\""Milho\\\\\\\\"",\\\\\\\\""cutDate\\\\\\\\"":\\\\\\\\""2023-02-01T03:00:00.000Z\\\\\\\\"",\\\\\\\\""harvestDate\\\\\\\\"":\\\\\\\\""2023-02-01T03:00:00.000Z\\\\\\\\"",\\\\\\\\""loggedUser\\\\\\\\"":{\\\\\\\\""id\\\\\\\\"":\\\\\\\\""250f7b61-a6ab-4922-af4d-8ef98f9ad569\\\\\\\\"",\\\\\\\\""userName\\\\\\\\"":\\\\\\\\""tbanin\\\\\\\\""},\\\\\\\\""employee\\\\\\\\"":\\\\\\\\{\\\\\\\\""id\\\\\\\\"":\\\\\\\\""43a1b7f5-fa38-416d-bca4-6c2cb2da404b\\\\\\\\"",\\\\\\\\""name\\\\\\\\"":\\\\\\\\""Sergio Meirelles\\\\\\\\"",\\\\\\\\""email\\\\\\\\"":\\\\\\\\""smeirelles@deheus.com\\\\\\\\""},\\\\\\\\""samplingDate\\\\\\\\"":\\\\\\\\""2023-02-22T03:00:00.000Z\\\\\\\\"",\\\\\\\\""analysisOrders\\\\\\\\"":[\\\\\\\\{\\\\\\\\""id\\\\\\\\"":\\\\\\\\""74fa0fa7-dc7b-4f64-991c-6ded543e2980\\\\\\\\"",\\\\\\\\""articleId\\\\\\\\"":\\\\\\\\""7418a724-cbd2-4fa9-9bd5-b8649ebdad49\\\\\\\\"",\\\\\\\\""articleCode\\\\\\\\"":\\\\\\\\""LX178\\\\\\\\"",\\\\\\\\""articleName\\\\\\\\"":\\\\\\\\""SILAGEM DE MILHO\\\\\\\\"",\\\\\\\\""sampleCode\\\\\\\\"":\\\\\\\\""90230302001\\\\\\\\"",\\\\\\\\""sampleItemCode\\\\\\\\"":\\\\\\\\""LX178\\\\\\\\"",\\\\\\\\""nutrients\\\\\\\\"":[{\\\\\\\\""nutrientCode\\\\\\\\"":\\\\\\\\""VCRDRYT\\\\\\\\"",\\\\\\\\""nutrientName\\\\\\\\"":\\\\\\\\""Dm Weight Terra\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":32.13},\\\\\\\\{\\\\\\\\""nutrientCode\\\\\\\\"":\\\\\\\\""VCRDRYI\\\\\\\\"",\\\\\\\\""nutrientName\\\\\\\\"":\\\\\\\\""Dm Weight In\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":270.58},\\\\\\\\{\\\\\\\\""nutrientCode\\\\\\\\"":\\\\\\\\""VCRDRYO\\\\\\\\"",\\\\\\\\""nutrientName\\\\\\\\"":\\\\\\\\""Dm Weight Out\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":95.38}]}]}""}.System.UnauthorizedAccessException: Access to the path \\\\\\\'D:\\\\\\\\Kotrak\\\\\\\\dhp30_IIS\\\\\\\\XML\\\\\\\\DHHIMP90010025.xml\\\\\\\' is denied.\\\'\', ""Comment 11: \'[^DHHIMP90010025.xml]\'"", ""Comment 12: \'[^DHHIMP90010025.xml]^Hello I can see that there is some problem with access to folder.^^I temporarly changed the path in configuration and create new folder.^^Please verify if document is correct^^and let me know if we may change priority to p2 ( tommorow someone from our developers will look at configuration).^^!image-2023-03-02-16-59-46-096.png!^\'"", ""Comment 13: \'I need to check"", ""Comment 14: but you can change for P2. Thank you.\'"", ""Comment 15: \'the fisrt problem with authentication occured at 10:55!image-2023-03-02-19-18-20-465.png!\'"", ""Comment 16: \'Please try to generate the xml again and check if the problem still occurs.\'"", ""Comment 17: \'Hi"", ""Comment 18: the error still occurs. Could you check it?\'"", ""Comment 19: \'[~agnieszka.januszewska@kotrak.com] ścieżka aktualnie jest taka jak poprzednio do XML folder. Folder xmltest został dzisiaj usunięty.\'"", ""Comment 20: \'Hello in today log I did not see the same error as yesterday "", \'Comment 21: could you provide more detailswhen you get an error? and for what AO?Maybe you may provide information what AO is printed and how to filI in the form\', ""Comment 22: that we may use this AO for test it?\'"", \'Comment 23: ""AgnieszkaI tested now with Tassia and it\\\'s working.Thank you""]\']\nRelated Issues:\n[]\n\n### End'}"
356,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8676\n\n### Instruction:\nHi\r\nPrzy kopiowaniu ZZ na nowy ZZ, który na pozycji ma ilość=0, nie ma możliwości zmiany ilości i kosztu transportu.\r\nJest błąd: Odwołanie do obiektu nie zostało ustawione na wystąpienie obiektu.\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: \'Looks like a problem with the document and not the functionality"", ""Comment 4: is it a copy from order 123/3/23?The items of this order start with number 2 !screenshot-1! Did these orders also look like this at the beginning of the ticket?\'"", \'Comment 5: ""No\', \'Comment 6: it\\\'s copy from ZZ-92""\', \'Comment 7: ""z profilera{code:java}declare @ContractId int=10033678--declare @ElementId int=1SELECT SUM(Quantity) QuantityFROMKotrak.calloffsWHEREContractId = @ContractId --AND ContractElementId = @ElementId AND--Status <> 6--\\\',N\\\'@ContractId int,@ElementId int\\\',@ContractId=10033678,@ElementId=2{code}{code:java}UPDATE N SET ZaN_Aktywny = 0FROM CDN.ZamNag NJOIN CDN.Sesje S ON (Zan_Aktywny <> 0) AND ZaN_Aktywny = S.SES_SesjaIDWHERE ZaN_GidNumer=@contractId AND (@force = 1 OR S.SES_Aktywna = 1 OR S.SES_Aktywna = 2)\\\',N\\\'@contractId int,@force int\\\',@contractId=9887385,@force=0{code}Problem dotyczy tylko tego zamówienia zz-92/02/2023 - edytując dowolny element. !screenshot-2! ""\', ""Comment 8: \'zgodnie z rozmową.\'"", ""Comment 9: \'Hello"", ""Comment 10: the problem is with this particular order and you just need to edit any element and there is this problem.Attempts to duplicate it on the test fail - please create a new contract not from a copy. In the test it is possible to create a new copy contract for elements with zero quantities.\'"", \'Comment 11: ""Hi\', ""Comment 12: we\'ve done like this when the problem occur"", \'Comment 13: but is there any chance to fix this error?""\', \'Comment 14: ""Hi\', \'Comment 15: are there more cases?Can\\\'t this contract be closed?Do we have a path to the error?It would make it easier to analyze.""\', \'Comment 16: ""For now it was 1 case with this error. We made a new ZZ manually. I think this task is to close. We\\\'ll analyze once more\', \'Comment 17: when problem return.""]\']\nRelated Issues:\n[]\n\n### End'}"
357,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8675\n\n### Instruction:\nThere are cases that we need to add an SR to Intense just for registration purposes. So just because we need to have correct technical results. We don\'t do anything financially with these slaughter reports.\r\n\r\nWe need to be able to register a SR registration:\r\n•\tOnly possibility to create registration PI from it \r\n•\tWe won’t use the pricing formula. We will manually give a price (on the invoice, registration purchase)\r\n•\tIt must be calculated within the technical results (we can also just create the registration PI, if this is enough to get these numbers in the technical calculations)\r\n\r\nCould you help us with this? \r\n\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 2: ""Now it\\\'s possible to manualy add Slaughtery Report in MAS NL and MAS BE.Is it sufficient or should we think to add some validations - to allow create only Purchase Invoices from SR?The process normally looks little differently in MAS NL and MAS BE\', \'Comment 3: so in both sectors it should be possible to create only PI from SR? * In MAS NL from SR is created SI * In MAS BE from SR is created PII think if SR will be connected with round and invoice will be also properly linked with SR values should be included in technical results\', ""Comment 4: but we should analyze it deeper.Is it needed to get values from this SR and PI to technical results but we don\'t want to include this invoice in all documents - Round"", \'Comment 5: Financial Statement\', \'Comment 6: Saldo to pay\', \'Comment 7: right?""\', \'Comment 8: ""Yes\', \'Comment 9: it should be an SR with a registration type somewhere.In case of registration indeed it should be only possible to create a registration PI. This registration can be included on the round and financial statement\', \'Comment 10: however it should indeed not be on the S2P (the same as all other registration PI\\\'s).""\', ""Comment 11: \'WHen do you think this is ready?\'"", ""Comment 12: \'Please note that in MAS NL we normally start the process with a SI"", ""Comment 13: but in case of a registration SR we only create a registration purchase invoice.\'"", \'Comment 14: ""{quote}Yes\', \'Comment 15: it should be an SR with a registration type somewhere.In case of registration indeed it should be only possible to create a registration PI.This registration can be included on the round and financial statement\', ""Comment 16: however it should indeed not be on the S2P (the same as all other registration PI\'s).{quote}Does it mean that we should add new field on Slaughtery Report - some checbox with label \'Registered\' or other distincion?We can add action to generate Purchase Invoice with Registered type from this kind of Slaughtery reports and other buttons to create invoices then will be hidden. Will it be sufficient?We need to verify all calculations in technical results procedure to handle it in right way"", \'Comment 17: because some calculation base on invoices which are linked in normal way (for MAS NL - SR -> SI -> PI\', \'Comment 18: for MAS BE - SR -> PI -> SI) or add to all calculations new type of slaughtery report (with checbox or orher distintinction).""\', \'Comment 19: ""Does it mean that we should add new field on Slaughtery Report - some checbox with label \\\'Registered\\\' or other distincion? --> YESWe can add action to generate Purchase Invoice with Registered type from this kind of Slaughtery reports and other buttons to create invoices then will be hidden. Will it be sufficient? --> YES""\', ""Comment 20: \'Slaughtery Report"", \'Comment 21: który będzie korektą oryginalnego powinien być tworzony w całości ręcznie przez użytkownika z Inboxa.Purchase Invoice\', \'Comment 22: który będzie generowany ze Slaughtery reportu powinien być liczony podobnie jak faktury PI/SI (w zależności od sektora). Przy tych generacjach są nasze procedury\', \'Comment 23: które wyliczają wartości na PI/SI - np. KR_CalculationSlaughteryReportToPurchaseInvoice i powinno być to wyliczane analogicznie\', ""Comment 24: jedynie bez danych z kontraktu i pricing formula. Ceny na fakturach PI powinny być wprowadzane ręcznie.\'"", ""Comment 25: \'For technical results values from PI should be most important.\'"", \'Comment 26: ""[~mbovene@deheus.com]We divided this task to 2 steps: # Functionality to creating SR with checkbox \\\'Registered\\\' and \\\'Create Purchase Invoice\\\' Button \\\'Create Purchase Invoice\\\' is visible when checkbox\\\'Registered\\\' on SR is marked. Other buttons for \\\'Create Sales Invoice\\\' shouldn\\\'t be visible then. # Handle calculating technical results from this kind of slaughtery reports and purchase invoicesFor now from step 1 functionality has been created on IBIP_DH_TEST and it\\\'s possible to test it. Now it\\\'s done in MAS NL sector only and you can verify it there and then we can implement it also in MAS BE.You can verify that it works properly\', \'Comment 27: especially if the Purchase Invoices gets all and proper elements and values from SR (we have used procedure for creating purchase invoice from normal process with SR).!image-2023-03-28-10-25-10-052.png!!image-2023-03-28-10-29-22-773.png!""\', \'Comment 28: ""Hello Damian,I checked it\', \'Comment 29: but I don\\\'t see the checkbox yet in DH TEST. Did I do something wrong?!image!""\', \'Comment 30: ""Hello Steffen,It\\\'s implemented in MAS NL sector so far.""\', \'Comment 31: \\\'We need to be able to somewhere include the price. Normally we use the pricing formula for this but for registration SR\\\\\\\'s we won\\\\\\\'t use it. When the checkbox ""Registered"" is marked we should see an additional field to put in the price.\\\'\', \'Comment 32: ""In my eyes\', \'Comment 33: the pricing formula may be used as well. Mostly it\\\'s that price that we are going to use anyways. Maybe I missed the clue earlier that this isn\\\'t an option?""\', \'Comment 34: \\\'{quote}We need to be able to somewhere include the price. Normally we use the pricing formula for this but for registration SR\\\\\\\'s we won\\\\\\\'t use it.When the checkbox ""Registered"" is marked we should see an additional field to put in the price.{quote}{quote}In my eyes\', ""Comment 35: the pricing formula may be used as well. Mostly it\\\\\'s that price that we are going to use anyways. Maybe I missed the clue earlier that this isn\\\\\'t an option?{quote}How would you like to put the price? it should be one field with price and it should be on SR or maybe it should be possible to put price on invoice?Maybe we can use somehow existing fields from SR or the same fields like in normal process?\'"", \'Comment 36: ""According to me\', ""Comment 37: it may be complete the same process as a regular/financed slaughter report (with the pricing formula). It just has to include these numbers also in the calculations of the technical results. But I\'ll let Mitch answer"", \'Comment 38: maybe he still has other insights.""\', ""Comment 39: \'Afte discussion I agree with Steffen. Please use the pricing formula for this just like in all other cases.\'"", ""Comment 40: \'All right"", \'Comment 41: then itshould works with pricing formula like in normal process\', ""Comment 42: you can verify that it works and prices are calculated.When you select round I think it will be possible to calculate values properly.Maybe only on IBIP_DH_TEST Price List is not filled for last months.Could you verify that is sufficient and this part of modification works properly?\'"", \'Comment 43: ""Prices are calculated (correctly it seems). However I didn\\\'t select \\\'registration\\\' somewhere on the slaughter report because there wasn\\\'t a field. Do I need to select \\\'regular purchase\\\' here and then switch the type in the invoice?!image-2!!image-3!""\', ""Comment 44: \'I have tested this as well and it looks good. I see the checkbox: !image-1!\'"", ""Comment 45: \'Oh yes"", \'Comment 46: my bad. Probably only was in MAS NL TEST. But if Mitch says it works\', ""Comment 47: I trust that.\'"", \'Comment 48: ""Ok\', \'Comment 49: it seems that works properly\', ""Comment 50: so we\'ll implement also this solution to MAS BE on Test environment.We\'ll inform you when it will be ready to tests.This will be 1 st part of this task"", \'Comment 51: 2 nd more complex will be about modifications in technical results calculations.Do you think that we should rather based in calculations on values from this Purchase Invoice or Slaughtery Report?On Purchase Invoice generated from this SR will be lines with items similar like on regular SR?As we discussed recently about changes in technical results calculations there was a statement that we should basedmore on PI than on SR (of course not all values can be collected from PI\', \'Comment 52: I refer to values which are on both documents PI and SR).""\', ""Comment 53: \'Do you think that we should rather based in calculations on values from this Purchase Invoice or Slaughtery Report? --> PIOn Purchase Invoice generated from this SR will be lines with items similar like on regular SR? --> YES\'"", ""Comment 54: \'Now"", ""Comment 55: we got similar situation in MAS BE like MAS NL. You can test it. We still work on second stepnamely * Handle calculating technical results from this kind of slaughtery reports and purchase invoices\'"", ""Comment 56: \'I can see the field in MAS BE test now as well"", ""Comment 57: yes.\'"", ""Comment 58: \'Could you specified in columns for records on yellow which technical results should be credited by new process and from which document should be selected values to correct original values.|Should correct technical result?|SR credit|PI generated from SR credit|Remarks|[^Technical Results.xlsx]\'"", ""Comment 59: \'{color:black}{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}SalutationsCordiales{color} | | | |{color:#000001} Koen{color} |{color:#000001} {color} |{color:#000001} Huibers{color} |  {color:#000001}+31318675600{color} | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.de-heus.nl/]>{color} | |  *{color:#006FB7} *DEHEUSVOEDERSBELGIEN.V.*{color}* | | |{color:black} {color} | |{color:#000001} LouisPasteurstraat11/201 \\\\u200b3920Lommel{color} | | |{color:#000001} M:{color}{color:#000001}{color}{color:#000001}+32-11-546672{color}{color:#000001} <tel:+32%20-%2011%20-%2054%2066%2072>{color} |  {color:#000001}Ondernemingsnummer:0437.737.739{color} |  _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | | | !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | | !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} | | !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} |        *Van:* Damian Świstek (Jira) <jira@kotrak.com>   *Verzonden:* woensdag 5 april 2023 8:56  *Aan:* Huibers"", ""Comment 60: Koen <khuibers@deheus.com>  *Onderwerp:* DGS-8675 Create SR registration   !image006.gif![^doc17951020230404161459.pdf] _(200 kB)_\'"", \'Comment 61: ""[~mbovene@deheus.com]it\\\'s ready to test in MAS NL sector on test environment with technical results calculations.""\', ""Comment 62: \'I tested a customer on round 014940/0006/0003 in MAS NL TEST. A few comments: 1. On the registration invoice"", \'Comment 63: code SRMT was automatically used for slaughtery revenue in stead of SLAC (screenshot 1)? 2. When I want to archive the SR\', \'Comment 64: the system gives me a warning there are no invoices created\', \'Comment 65: while I did already archive the registration PI (screenshot 2)? For the rest\', \'Comment 66: the the technical results seem good\', \'Comment 67: you can see in the last screenshot. So to me\', ""Comment 68: this can be moved to PROD (with attention to the 2 comments).!image-4!!image-5!!image-6!\'"", \'Comment 69: ""1. I\\\'ve checked procedure which creates PI from SR. Line with Item SRM has been generated on PI because condition for adding line with this item SRM was met Contract SlaughterIn this case on SR value \\\'Deviance\\\' is null\', \'Comment 70: in procedure when SR is linked to CS there is verification that value from CS other conditions 2\', ""Comment 71: from column \'Condition\' - here is <50 is less than deviation. Here it\'s not"", \'Comment 72: so in this case procedure calculate it like that:KGToPayToFarmer * Amount (47022 * 0,0050)\', \'Comment 73: so there was on invoice value = 235,11.2. Warning during flow performing has been implemented to normal process for Slaughtery Reports to avoid sending to Archive documents - here there are no SI like in normal proces\', ""Comment 74: that\'s why is warning. Verification is about SI and PI from SR. We can adjust it if it\'s needed and not display this warning.Should we do any improvements for this process right now"", \'Comment 75: do you need to test it on more cases or should we start moving this solution to Prod environment?!image-2023-04-07-13-47-10-761.png!!image-2023-04-07-13-47-26-357.png!""\', ""Comment 76: \'1. I hope Steffen can answer"", ""Comment 77: he knows more about the details of this example.2. This warning can be turned off. We will only create the PI. \'"", \'Comment 78: ""[~mbovene@deheus.com][~SDriesen@deheus.com]It\\\'s ready to test also in MAS BE sector on test environment with technical results calculations.As we discussed recently MAS NL can be move to prod environment\', \'Comment 79: then if in MAS BE also will be good and you confirm that it works properly\', \'Comment 80: we can move to Prod environment solution for both sectors.""\', \'Comment 81: ""[~tomasz.zygon@kotrak.com]do przeniesienia na Prod pierwsza część rozwiązania # {quote}Functionality to creating SR with checkbox \\\'Registered\\\' and \\\'Create Purchase Invoice\\\'Button \\\'Create Purchase Invoice\\\' is visible when checkbox\\\'Registered\\\' on SR is marked. Other buttons for \\\'Create Sales Invoice\\\' shouldn\\\'t be visible then.{quote}Jak potwierdzą nam\', \'Comment 82: że dla sektora MAS BE działa poprawnie na test przeliczanie Technical results\', \'Comment 83: to przeniosę 2 część tego taska na Prod.""\', ""Comment 84: \'I tested it in MAS BE and it worked. For me it can be moved to PROD. Thank you\'"", ""Comment 85: \'Solution has been moved to Production environment for MAS NL and MAS BE sectors.Please verify and confirm if everything works properly and then we can close task.\'"", \'Comment 86: ""I will test it now. Just one more question Damian\', ""Comment 87: old rounds where we used registrated SR\'s + invoices"", \'Comment 88: should they be adapted by now as well\', \'Comment 89: or does it only start now when we tick \\\'registered\\\' on the SR?""\', ""Comment 90: \'I actually just tested it myself. I opened a SR of a already finished round"", \'Comment 91: ticked ""registered"" and recalculated the technical results again. Afterwards the numbers modified. So to me\', ""Comment 92: it seems to be working.\'"", \'Comment 93: ""What do you meanregistrated SR\\\'s + invoices which you used? Did you use before this new functionality deployment some solution with SR + invoice to correct some values?Functionality of SR registered (with marked checkbox) will work from now.Technical results are calculated right now with new conditions (including values from this specific type of SR Registered + PI registered created from this registered SR).Nothing should change on old documents\', \'Comment 94: round\', \'Comment 95: calculated values for technical results if there will be no SR Registered (with new checbox)\', \'Comment 96: but if you add some SR registered (with checkbox) for old rounds and when you calculate technical results values will change.!image-2023-04-17-13-25-27-804.png!""\', ""Comment 97: \'Yes"", \'Comment 98: it is as you say. I had a round where the technical results were wrong because there was a registered PI\', \'Comment 99: but at that time\', \'Comment 100: the box was not yet on the SR. Now that it is\', \'Comment 101: I went back and ticked it\', ""Comment 102: and afterwards the values changed on the technical results as I hoped so. So that looks great!\'"", ""Comment 103: \'Great"", ""Comment 104: so we can leave this task open until you confirm that everything works properly in more cases or close the task if you decide that it works fine.\']""]\nRelated Issues:\n[\'DGS-8732\', \'DGS-8877\']\n\n### End'}"
358,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8674\n\n### Instruction:\nDH CDN is very slow.\r\nVery low responce.\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: \'!image-2023-03-02-14-20-09-918.png|width=1092,height=660!\'"", ""Comment 4: \'!image-2023-03-02-14-21-07-216.png|width=800,height=528!\'"", ""Comment 5: \'!image-2023-03-02-14-40-09-605.png!\'"", ""Comment 6: \'{code:java}ERRORS:|Cannot generate document \\\\x96 no license. (NowyDokument-81)   at Evolution.ErpIntegrator.CdnXL.CdnXL2016.Documents.ExternalOrderTransactions.CdnXL2016ExternalOrderTransactionRepository.CreateHeader(XLExternalOrderTransaction documentHeader) in C:\\\\\\\\TeamCity\\\\\\\\buildAgent\\\\\\\\work\\\\\\\\57a7e278b67a115c\\\\\\\\Evolution.ErpIntegrator\\\\\\\\CdnXL\\\\\\\\Evolution.ErpIntegrator.CdnXL.CdnXL2016\\\\\\\\Documents\\\\\\\\ExternalOrderTransactions\\\\\\\\CdnXL2016ExternalOrderTransactionRepository.cs:line 792023-03-02 10:15:48,966 [9] DEBUG Evolution.ErpIntegrator.DHC.DHC30.Database.DhcTransaction [(null)] - DHC transaction rollback staeted2023-03-02 10:15:48,966 [9] DEBUG Evolution.ErpIntegrator.DHC.DHC30.Database.DhcTransaction [(null)] - DHC transaction rollback finished2023-03-02 10:15:48,969 [9] ERROR Evolution.ErpIntegrator.CdnXL.CdnXL2016.Transactions.XLTransaction [(null)] - XL rollback error - possibly no transactionError of type Evolution.ErpIntegrator.CdnXL.CdnXL2016.XLApiException has been thrown (XLTransakcja - Rollback:-1).API Name - XLTransakcja - RollbackAPI Result - -12023-03-02 10:15:48,969 [9] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2016.Transactions.XLTransaction [(null)] - XL transaction rollbacked"", \'Comment 7: token ID - 8Q_ZTOCX5a[-Yi6SjF_e_=5---0kDM--2023-03-02 10:15:48,974 [9] DEBUG Evolution.ErpIntegrator.DHC.DHC30.Database.DhcTransaction [(null)] - DHC transaction rollback staeted2023-03-02 10:15:48,974 [9] DEBUG Evolution.ErpIntegrator.DHC.DHC30.Database.DhcTransaction [(null)] - DHC transaction rollback finished2023-03-02 10:15:48,976 [9] ERROR Evolution.ErpIntegrator.CdnXL.CdnXL2016.Transactions.XLTransaction [(null)] - XL rollback error - possibly no transactionError of type Evolution.ErpIntegrator.CdnXL.CdnXL2016.XLApiException has been thrown (XLTransakcja - Rollback:-1).API Name - XLTransakcja - RollbackAPI Result - -12023-03-02 10:15:48,976 [9] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2016.Transactions.XLTransaction [(null)] - XL transaction rollbacked\', ""Comment 8: token ID - 2023-03-02 10:15:49,035 [9] ERROR Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateSalesOrderRelease [(null)] - Error of type XLApiException has been thrown (XLNowyDokument:81).API Name - XLNowyDokumentAPI Result - 81ERRORS:|Cannot generate document \\\\x96 no license. (NowyDokument-81)Error of type Evolution.ErpIntegrator.CdnXL.CdnXL2016.XLApiException has been thrown (XLNowyDokument:81).API Name - XLNowyDokumentAPI Result - 81{code}\'"", ""Comment 9: \'Restart!image-2023-03-02-14-46-25-930.png!\'"", ""Comment 10: \'You have done something,Speed is better on this moment\'"", ""Comment 11: \'Just verified issue. Batch request was quite high"", ""Comment 12: now it is much lower\'"", ""Comment 13: \'Now it is normal. Close ticket\']""]\nRelated Issues:\n[]\n\n### End'}"
359,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8673\n\n### Instruction:\nHi, Peter should be able to add relevancy to all item codes.\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 Mitch,Peter Moeliker has rights for edit Relevant sectors on Item Card and he should be able to do it.I think your screen is from \\\'New Item Card\\\' document and there field \\\'Relevant sectors\\\' is disabled for all users. Should we adjust something in the system?Regards""\', ""Comment 4: \'Hi"", \'Comment 5: yes. PLease make it possible for all users who can create users from the ""new item card\\\\\\\' functionality. Here it should indeed be possible to select the relevant sectors as well.With the new functionalitities the multisector table we don\\\\\\\'t need anymore. All items will be send to all sectors\', ""Comment 6: right?\'"", \'Comment 7: ""Hi,Ok\', ""Comment 8: this field now is possible to edit for user who have this documents in Inbox or have access to others inbox and can edit other fields on \'New Item Card\' and can process these documents.Please verify that it\'s possible to edit this field - \'Relevant sectors\'{quote}With the new functionalitities the multisector table we don\'t need anymore. All items will be send to all sectors"", ""Comment 9: right?{quote}Items are created directly as a \'Item card\' in Intense"", ""Comment 10: but only for Item Group = \'Raw Materials\' and \'Finish products\'"", \'Comment 11: so for other items sent from Milas it apperas in Intense as a \\\'New Item Card\\\' and then it\\\'s possible to choose for which sectors it should be created.Then functionality still works I think.""\', ""Comment 12: \'Can be closed.\']""]\nRelated Issues:\n[]\n\n### End'}"
360,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8672\n\n### Instruction:\nChange Main Target and customer of invoice: ESI.04.02.2023.VEXP to 0674\r\n\n\n### Response:\n[""Comment 1: [\'[^cz esi.04.02.2023.vexp.pdf] _(96 kB)_\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Customer data has been changed as requested:!image-2023-03-02-13-10-48-587.png!Regards\'"", ""Comment 4: \'User is checking the change\'"", ""Comment 5: \'ok\'"", ""Comment 6: \'Ticket can be closed\']""]\nRelated Issues:\n[]\n\n### End'}"
361,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8671\n\n### Instruction:\nTask from Wiola:\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 message informs that remote work for this person has already been introduced on this day. Please provide a screenshot of this employee\\\'s work schedule""\', ""Comment 4: \'!image-2!\'"", ""Comment 5: \'[^Praca_zdalna.docx]\'"", ""Comment 6: \'Description in the attachment[^Praca_zdalna.docx]\'"", ""Comment 7: \'Could you please confirm if we can close this task?Regards\'"", ""Comment 8: \'Hi"", ""Comment 9: task to close. Thanks.\']""]\nRelated Issues:\n[]\n\n### End'}"
362,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8670\n\n### Instruction:\nHi, from Iwona:\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'If this task still actual?I see this payroll in the transfer list!image-2023-03-03-10-31-02-136.png!\'"", ""Comment 4: \'!image-1!\'"", ""Comment 5: \'Can I close this task?\'"", ""Comment 6: \'Yes"", ""Comment 7: task to close.\']""]\nRelated Issues:\n[]\n\n### End'}"
363,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8669\n\n### Instruction:\nHi, task from Wiola:\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'changes on report will take 8 rbg please accept costs.\'"", ""Comment 4: \'I accept costs.\'"", ""Comment 5: \'New report has been added in optima. Please verify  !screenshot-1! \'"", ""Comment 6: \'Can we close this issue?\'"", ""Comment 7: \'Still waiting for response from Wiola.\'"", ""Comment 8: \'!image-1!\'"", \'Comment 9: \\\'When printout parameters are set as below.  Employee UM-OSTROWSKA_M is not visible on it. Please let me know about parameters that you set up. !screenshot-2! About additional condition let me know more details.If printout should check only ""Zwolnienie chorobowe"" absence or another? And second if 31 days must be checked to current date or to date from parameters (below). Then we will sent pricing. !screenshot-3! \\\'\', ""Comment 10: \'!image-2!\'"", \'Comment 11: \\\'visibility in excel has been corrected. Please verifyAbout additional condition let me know more details.If printout should check only ""Zwolnienie chorobowe"" absence or another?And second if 31 days must be checked to current date or to date from parameters (below). Then we will sent pricing. !screenshot-3! \\\'\', ""Comment 12: \'!image-3!\'"", ""Comment 13: \'Hi"", ""Comment 14: can we reopen this task? !image-4!\'"", ""Comment 15: \'Task has been reopened .We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 16: \'Please provide filter and parameters You are generating this raport for.When I run this report for filter!image-2023-04-07-18-18-33-226.png!!image-2023-04-07-18-18-50-963.png!with parametes!image-2023-04-07-18-19-20-064.png!I do not see UM-OSTROWSKA_M on generated raport !image-2023-04-07-18-18-16-389.png!\'"", ""Comment 17: \'Please"", ""Comment 18: let me know if expect any additional actions from us regarding this issue? Can we close this ticket?\'"", ""Comment 19: \'!image-5!\'"", ""Comment 20: \'In summary"", \'Comment 21: the reported modification has been made and the report ""Limity nieobecności (dla zaznaczonych)"" is working properly.The continuation of the issue concerns ""Zestawienie wypłaconych premii"" report requiring modification.In this case\', \'Comment 22: please create a new issue\', \'Comment 23: the modification of the report will be valued and after receiving the approval of the costs\', ""Comment 24: we will proceed to implement the changes.Could you please confirm if we can close this task?Regards\'"", ""Comment 25: \'In summary"", \'Comment 26: the reported modification has been made and the report ""Limity nieobecności (dla zaznaczonych)"" is working properly.The continuation of the issue concerns ""Zestawienie wypłaconych premii"" report requiring modification.In this case\', \'Comment 27: please create a new issue\', \'Comment 28: the modification of the report will be valued and after receiving the approval of the costs\', ""Comment 29: we will proceed to implement the changes.Could you please confirm if we can close this task?Regards\'"", \'Comment 30: ""I\\\'m waiting for user response...""]\']\nRelated Issues:\n[]\n\n### End'}"
364,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8668\n\n### Instruction:\nHi\r\n\r\nWe have some deliveries that expired after go live and DHP didn\'t locked these ones automatically.\r\nWe need to enter manually and block each one.\r\nFor example: *FCP4431-S28*\r\n\r\nCould you please check it?\r\n\r\nThank you very much\n\n### Response:\n[""Comment 1: [\'!image!\'"", \'Comment 2: ""FYI:We already have this configuration set as true\', \'Comment 3: but it\\\'s not working!image-1!""\', ""Comment 4: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 5: ""{code:java}2023-03-01 00:15:30 (/Plant.Stock.BusinessLogic/BR-1-SV-VM0702/21920/46) [Error] Kotrak.Common.Infrastructure.IEventRunEnvironment - Error during Void Run[TimePassedEvent](Plant.Stock.BusinessLogic.Application.Interfaces.TimePassedEvent) methodSystem.AggregateException: One or more errors occurred. (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \\\'Dispose\\\' on the context instance\', \'Comment 6: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 7: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 8: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 9: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 10: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 11: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 12: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 13: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 14: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 15: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 16: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 17: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 18: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 19: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 20: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 21: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 22: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 23: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 24: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 25: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 26: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 27: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 28: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 29: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 30: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 31: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 32: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 33: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 34: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 35: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 36: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 37: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 38: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 39: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 40: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 41: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 42: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 43: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 44: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 45: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 46: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 47: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 48: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 49: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 50: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 51: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 52: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 53: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 54: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 55: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 56: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 57: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 58: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 59: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 60: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 61: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 62: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 63: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 64: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 65: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 66: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 67: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 68: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 69: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 70: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 71: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 72: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 73: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 74: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 75: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 76: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 77: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 78: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 79: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 80: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 81: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 82: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 83: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 84: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 85: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 86: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 87: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 88: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 89: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 90: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 91: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 92: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 93: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 94: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 95: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 96: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 97: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 98: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 99: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 100: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 101: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 102: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 103: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 104: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 105: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 106: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 107: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 108: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 109: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 110: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 111: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 112: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 113: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 114: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 115: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) ---> System.ObjectDisposedException: Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 116: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 117: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.   at Microsoft.EntityFrameworkCore.DbContext.CheckDisposed()   at Microsoft.EntityFrameworkCore.DbContext.get_Database()   at Kotrak.Common.Infrastructure.EF.TransactionEf..ctor(DbContext dbContext"", \'Comment 118: DbContext eventContext\', ""Comment 119: IsolationLevel isolationLevel)   at Plant.Stock.BusinessLogic.Infrastructure.Factories.TransactionFactory.CreateTransaction() in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Infrastructure\\\\\\\\Factories\\\\\\\\TransactionFactory.cs:line 23   at Plant.Stock.BusinessLogic.Application.Deliveries.Events.DeliveryExpirationByTimePassedEventHandler.Handle(TimePassedEvent event) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Application\\\\\\\\Deliveries\\\\\\\\Events\\\\\\\\DeliveryExpirationByTimePassedEventHandler.cs:line 45   --- End of inner exception stack trace ---   at Plant.Stock.BusinessLogic.Application.Deliveries.Events.DeliveryExpirationByTimePassedEventHandler.Handle(TimePassedEvent event) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Application\\\\\\\\Deliveries\\\\\\\\Events\\\\\\\\DeliveryExpirationByTimePassedEventHandler.cs:line 60   at Kotrak.Common.Infrastructure.Events.EventEnvironment.Run[TEvent](TEvent event)   at Castle.DynamicProxy.AbstractInvocation.Proceed()   at Kotrak.Common.Infrastructure.Interceptors.LoggingInterceptor`1.Intercept(IInvocation invocation) ---> (Inner Exception #1) System.ObjectDisposedException: Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 120: or wrapping it in a using statement. If you are using dependency injection\', \'Comment 121: you should let the dependency injection container take care of disposing context instances.Object name: \\\'StockContext\\\'.{code}""\', \'Comment 122: ""I cała impreza od początku:{code:java}---> (Inner Exception #54) System.ObjectDisposedException: Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \\\'Dispose\\\' on the context instance\', \'Comment 123: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 124: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.   at Microsoft.EntityFrameworkCore.DbContext.CheckDisposed()   at Microsoft.EntityFrameworkCore.DbContext.get_Database()   at Kotrak.Common.Infrastructure.EF.TransactionEf..ctor(DbContext dbContext"", \'Comment 125: DbContext eventContext\', ""Comment 126: IsolationLevel isolationLevel)   at Plant.Stock.BusinessLogic.Infrastructure.Factories.TransactionFactory.CreateTransaction() in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Infrastructure\\\\\\\\Factories\\\\\\\\TransactionFactory.cs:line 23   at Plant.Stock.BusinessLogic.Application.Deliveries.Events.DeliveryExpirationByTimePassedEventHandler.Handle(TimePassedEvent event) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Application\\\\\\\\Deliveries\\\\\\\\Events\\\\\\\\DeliveryExpirationByTimePassedEventHandler.cs:line 45<---2023-03-01 00:15:30 (/Plant.Stock.BusinessLogic/BR-1-SV-VM0702/21920/46) [Error] Plant.Stock.BusinessLogic.Infrastructure.Tasks.TimeIsPassingByTask - TimeIsPassingByTask exceptionSystem.AggregateException: One or more errors occurred. (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 127: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 128: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 129: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 130: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 131: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 132: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 133: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 134: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 135: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 136: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 137: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 138: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 139: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 140: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 141: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 142: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 143: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 144: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 145: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 146: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 147: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 148: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 149: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 150: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 151: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 152: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 153: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 154: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 155: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 156: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 157: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 158: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 159: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 160: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 161: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 162: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 163: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 164: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 165: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 166: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 167: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 168: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 169: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 170: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 171: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 172: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 173: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 174: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 175: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 176: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 177: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 178: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 179: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 180: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 181: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 182: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 183: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 184: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 185: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 186: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 187: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 188: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 189: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 190: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 191: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 192: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 193: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 194: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 195: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 196: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 197: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 198: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 199: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 200: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 201: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 202: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 203: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 204: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 205: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 206: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 207: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 208: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 209: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 210: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 211: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 212: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 213: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 214: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 215: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 216: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 217: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 218: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 219: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 220: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 221: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 222: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 223: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 224: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 225: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 226: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 227: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 228: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 229: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 230: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 231: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 232: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 233: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 234: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 235: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 236: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) ---> System.ObjectDisposedException: Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 237: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 238: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.   at Microsoft.EntityFrameworkCore.DbContext.CheckDisposed()   at Microsoft.EntityFrameworkCore.DbContext.get_Database()   at Kotrak.Common.Infrastructure.EF.TransactionEf..ctor(DbContext dbContext"", \'Comment 239: DbContext eventContext\', ""Comment 240: IsolationLevel isolationLevel)   at Plant.Stock.BusinessLogic.Infrastructure.Factories.TransactionFactory.CreateTransaction() in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Infrastructure\\\\\\\\Factories\\\\\\\\TransactionFactory.cs:line 23   at Plant.Stock.BusinessLogic.Application.Deliveries.Events.DeliveryExpirationByTimePassedEventHandler.Handle(TimePassedEvent event) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Application\\\\\\\\Deliveries\\\\\\\\Events\\\\\\\\DeliveryExpirationByTimePassedEventHandler.cs:line 45   --- End of inner exception stack trace ---   at Plant.Stock.BusinessLogic.Application.Deliveries.Events.DeliveryExpirationByTimePassedEventHandler.Handle(TimePassedEvent event) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Application\\\\\\\\Deliveries\\\\\\\\Events\\\\\\\\DeliveryExpirationByTimePassedEventHandler.cs:line 60   at Kotrak.Common.Infrastructure.Events.EventEnvironment.Run[TEvent](TEvent event)   at Castle.DynamicProxy.AbstractInvocation.Proceed()   at Kotrak.Common.Infrastructure.Interceptors.LoggingInterceptor`1.Intercept(IInvocation invocation)   at Castle.DynamicProxy.AbstractInvocation.Proceed()   at Castle.Proxies.IEventRunEnvironmentProxy.Run[TCommand](TCommand command)   at Plant.Stock.BusinessLogic.Infrastructure.Tasks.TimeIsPassingByTask.<ExecuteAsync>b__9_0() in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Infrastructure\\\\\\\\Tasks\\\\\\\\TimeIsPassingByTask.cs:line 41 ---> (Inner Exception #1) System.ObjectDisposedException: Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance"", \'Comment 241: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 242: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.   at Microsoft.EntityFrameworkCore.DbContext.CheckDisposed()   at Microsoft.EntityFrameworkCore.DbContext.get_Database()   at Kotrak.Common.Infrastructure.EF.TransactionEf..ctor(DbContext dbContext"", \'Comment 243: DbContext eventContext\', \'Comment 244: IsolationLevel isolationLevel)   at Plant.Stock.BusinessLogic.Infrastructure.Factories.TransactionFactory.CreateTransaction() in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Infrastructure\\\\\\\\Factories\\\\\\\\TransactionFactory.cs:line 23   at Plant.Stock.BusinessLogic.Application.Deliveries.Events.DeliveryExpirationByTimePassedEventHandler.Handle(TimePassedEvent event) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Application\\\\\\\\Deliveries\\\\\\\\Events\\\\\\\\DeliveryExpirationByTimePassedEventHandler.cs:line 45<---{code}""\', ""Comment 245: \'W appsettings jest wporzo!image-2023-03-02-09-09-44-345.png!\'"", ""Comment 246: \'Na naszym środowisku (170) SU/dostawy też nie są automatycznie lockowane. Pojawiają się te same błedy. Zgłosiłam DAP-13382.\'"", ""Comment 247: \'[~maciej.dobrzanski@kotrak.com]u nas na teście też nie działa"", ""Comment 248: Olcia sprawdziła :P\'"", ""Comment 249: \'Dzięki Olcia <3\'"", ""Comment 250: \'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 251: \'[~aleksandra.przybylek@kotrak.com] nie do końca niestety z tego co wiem. Jak drugi imp będzie zrealizowany to powiemy że jest działa.Wtedy napiszemy im w której wersji release 8.5 jest to poprawione.\'"", ""Comment 252: \'[~maciej.dobrzanski@kotrak.com]a teraz co im przekazać? jutro będą pewnie pytać\'"", ""Comment 253: \'Hi,This will be fixed in new version of DHP. For more details"", ""Comment 254: please contact Marcin Kleszcz.Regards\'"", \'Comment 255: ""Hi [~aleksandra.przybylek@kotrak.com]Thanks for this information. However other versions already have this functionality and this is having a huge impact for the factory and warehouse management. We can\\\'t wait for next version release! We don\\\'t have an estimated date yet.Dear [~marcin.kleszcz@kotrak.com] do you now which version is this fixed? 8.6? When will it get ready for release?Thank you""\', ""Comment 256: \'Hi [~mberbert@deheus.com]as I understood Maciej well"", ""Comment 257: this will be a fix deployed to the current 8.5 version. [~marcin.kleszcz@kotrak.com]could you please provide more detailed feedback?\'"", ""Comment 258: \'[~marcin.kleszcz@kotrak.com] odpiszesz mu coś albo skontaktujesz się z nim mailowo czy cóś? :)\'"", \'Comment 259: ""Hi [~mberbert@deheus.com]yes\', \'Comment 260: this fix was done to the latest 8.5.Currently we are working on GDC\\\'s for 8.5 version (2_3weeks).We can deploy versios with fix for Expiry together with changes from GDC\\\'s?""\', \'Comment 261: ""Hi [~aleksandra.przybylek@kotrak.com]I\\\'m relieved! I thought the *new version of DHP* would be 8.6ThanksHi [~marcin.kleszcz@kotrak.com]Is there any chance to update this fix sooner?Thank you very much!""\', \'Comment 262: ""Hi [~mberbert@deheus.com]yes\', ""Comment 263: I discussed with [~maciej.dobrzanski@kotrak.com] and version will be ready at the beginning of next week - with GDC\'s.Please create a DGS to make an estimation.I guess Maicon"", \'Comment 264: first we need to update RC Test. When you will approved\', \'Comment 265: we can plan an update on RC Prod?""\', ""Comment 266: \'[~marcin.kleszcz@kotrak.com]DGS-8727 was created to update GDC_2-3weeksThank you for the instructions.[~aleksandra.przybylek@kotrrak.com] you can close this taskThank you very much!\'"", ""Comment 267: \'Thank you [~mberbert@deheus.com]\']""]\nRelated Issues:\n[\'DGS-8683\', \'DAP-13382\', \'DAP-13384\']\n\n### End'}"
365,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8667\n\n### Instruction:\nHello,\r\n\r\nwe noticed for lot reports of packed goods, like Z20 variant, we got wrong lot reports in the ERP. We checked 0061270223024 from location Nijkerk, and we see 3 messages in the communication to the ERP: But as it seems, the first message that is processed is incorrect, with as produced item the bulk code, and as consumed item also the bulk code. Because of this the packed product is not added to ERP stock. Can you check from DHC side what messages are send to ERP for lot 0061270223024?\n\n### Response:\n[\'Comment 1: [""Hello @servicedesk\', ""Comment 2: I\'ve discussed this already with Przemek"", \'Comment 3: so ticket is for him to analyse and book hours\', \'Comment 4: thanks!""\', ""Comment 5: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.I am sending this task to Przemek.RegardsAgnieszka Januszewska\'"", \'Comment 6: \\\'<s:Header> <Action s:mustUnderstand=""1"" xmlns=""http://schemas.microsoft.com/ws/2005/05/addressing/none"">unit01_dhc_adapter_ws_provider_wsd_webMethods_DHC_Provider_Binder_insertProductionLotReport</Action> </s:Header> <s:Body xmlns:xsi=""http://www.w3.org/2001/XMLSchema-instance"" xmlns:xsd=""http://www.w3.org/2001/XMLSchema""> <insertProductionLotReport xmlns=""http://deheus.com/unit01/DHC""> <input xmlns=""""> <header> <ReceivingSystem>Milas</ReceivingSystem> <SendingSystem>DHC</SendingSystem> <CreateDate>2023-02-27T14:03:15.17</CreateDate> <CreateUser xsi:nil=""true"" /> <MessageID>3de88d0c-6088-43bb-a42a-c4cd91fcae93</MessageID> </header> <productionLotReport> <ProductionOrderReference>0061270223024</ProductionOrderReference> <ProducedItem>169900</ProducedItem> <ProducedQTY>2400.01</ProducedQTY> <ProducedQTYUOM>kg</ProducedQTYUOM> <Plant>6</Plant> <ProductionDateTime>2023-02-27T14:03:15.17</ProductionDateTime> <ProductionLotTypeIndicator>9</ProductionLotTypeIndicator> </productionLotReport> </input> </insertProductionLotReport> </s:Body></s:Envelope>\\\'\', \'Comment 7: \\\'<s:Header> <Action s:mustUnderstand=""1"" xmlns=""http://schemas.microsoft.com/ws/2005/05/addressing/none"">unit01_dhc_adapter_ws_provider_wsd_webMethods_DHC_Provider_Binder_insertProductionLotReport</Action> </s:Header> <s:Body xmlns:xsi=""http://www.w3.org/2001/XMLSchema-instance"" xmlns:xsd=""http://www.w3.org/2001/XMLSchema""> <insertProductionLotReport xmlns=""http://deheus.com/unit01/DHC""> <input xmlns=""""> <header> <ReceivingSystem>Milas</ReceivingSystem> <SendingSystem>DHC</SendingSystem> <CreateDate>2023-02-27T14:03:15.17</CreateDate> <CreateUser xsi:nil=""true"" /> <MessageID>7da1ab4c-7545-4c9f-bc1c-bce61e50bb3a</MessageID> </header> <productionLotReport> <ProductionOrderReference>0061270223024</ProductionOrderReference> <ProducedItem>169900-Z20</ProducedItem> <ProducedQTY>2400.01</ProducedQTY> <ProducedQTYUOM>kg</ProducedQTYUOM> <Plant>6</Plant> <ProductionDateTime>2023-02-27T14:03:15.17</ProductionDateTime> <ProductionLotTypeIndicator>1</ProductionLotTypeIndicator> <Lines> <ItemCode>169900</ItemCode> <ConsumedQTY>2400</ConsumedQTY> <ConsumedQTYUOM>KG</ConsumedQTYUOM> </Lines> </productionLotReport> </input> </insertProductionLotReport> </s:Body></s:Envelope>\\\'\', \'Comment 8: ""Hi [~TDankers@deheus.com]indeed at the begining are received draft PLR which was designed for starlims so it send Recipes (DHH bulk item). Also it was said during AS400 decommissioning project that its\\\' enough because you were planing to use only bulk products for those factories. I you would like to change it to use also packed products then we will need to make change in data communication. If you agree to such a change then please create GDC and we will estimate this change for you.""\', ""Comment 9: \'GDC-886 created"", ""Comment 10: ticket can be closed\'"", ""Comment 11: \'Thank you.\']""]\nRelated Issues:\n[]\n\n### End'}"
366,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8666\n\n### Instruction:\nPlease remove add tech VH303514\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: \'id technologii w plancie08E5D177-3FB2-4DC3-8A6E-DCAA8E569296\'"", ""Comment 4: \'Hello"", \'Comment 5: Can I ask why tan technology should be removed. It was added in September 2022 and more than 600 PRL were created from it. When deleting technologies\', \'Comment 6: we also remove PRL documents from several bases for DHP and DHC moduls\', \'Comment 7: but as a rule\', ""Comment 8: they were single objects.\'"", \'Comment 9: ""Select *--DELETE SFROM Recipes XLEFT JOIN ProductionLots P ON X.Id = P.RecipeIdLEFT JOIN DHPlantStockBusinessLogicMain.dbo.ProductionLots S ON S.Id = P.IdWHERE X.ItemId=\\\'9BA8FD4E-4CDF-4F2A-94C7-B59D629D70B2\\\' and Version=0to daje jakies 669 lotów""\', ""Comment 10: \'Hi agnieska"", \'Comment 11: I understand but this is an excellent example of why we need a archive functionaliity: This additional technology is made by mistake by someone from our formulation department. He/she did not inform IT so the technology stays in the system and lot reports are made: Lot reports coming from this produce and consume the same item as you can see in the tech\', ""Comment 12: so I gues you can call it a ghost technology because it doesnt do anything besides creating useless lot reports\'"", ""Comment 13: \'Ok I need to contact with dev for addituonal analisys"", \'Comment 14: cause beacuse this PRL were created since 2022 I do not want to make anyinconsistency of data resulting from such actions from the database side. As for new functionality\', ""Comment 15: please make such a GDc task if such a replacement if not priced.\'"", \'Comment 16: ""select * from ProductionLotReports where technologyid=\\\'D9FE29AB-3E5D-44C2-B542-20A7B65BE3B2\\\'( dhc service)""\', ""Comment 17: \'@Agnieszka"", \'Comment 18: I have planned a meeting Tuesday with Maciej\', ""Comment 19: Thomas and me to discuss this. Maciej told me you can stop spamming him about this subject :)\'"", \'Comment 20: ""Wrzucam skrypt sql do naprawienia archiwizacji receptury z product definition po stronie modułu PCS\', \'Comment 21: dla wersji R8.5:{code:sql}-- DGS-8666\', ""Comment 22: R8.5 workaround for product definition recipe archivization-- Set @RecipeId to desired guidDECLARE @RecipeId UNIQUEIDENTIFIER = \'00000000-0000-0000-0000-000000000000\';DECLARE @RecipeEntityId INT = (SELECT r.EntityId FROM dbo.Recipes r WHERE r.Id = @RecipeId);UPDATE dbo.Recipes\\\\tSET IsProductDefinition = 0WHERE Id = @RecipeId;DELETE FROM dbo.ExportRecipesWHERE EntityId = @RecipeEntityId;INSERT INTO dbo.ExportRecipes (PackageId"", \'Comment 23: SendDate\', \'Comment 24: ConfirmDate\', \'Comment 25: ExternalSystemId\', \'Comment 26: EntityId)SELECT NEWID()\', \'Comment 27: GETDATE()\', \'Comment 28: GETDATE()\', \'Comment 29: er.Id\', \'Comment 30: r.EntityIdFROM dbo.Recipes rJOIN dbo.ExternalSystems er ON 1 = 1WHERE r.Id = @RecipeId;{code}Skrypt można też znaleźć w repozytoriach:[[link]|http://10.10.10.52:82/projects/PLA3/repos/dhp30implementations/browse/BASE/8.5.0/SQL/PCS_RecipeArchivizationWorkaround.sql]""\', ""Comment 31: \'!image-2023-03-13-13-37-15-336.png!!image-2023-03-13-13-36-52-410.png!\'"", ""Comment 32: \'W PCS nie ma receptury"", \'Comment 33: więc luz\', ""Comment 34: pozostaje zmienić ProductDefinition = 0 w DHC i Service!image-2023-03-13-14-00-03-761.png!\'"", ""Comment 35: \'Hi,Additional TechnologyVH303514 has been prevented from sending to PCS and from another use in DHC.Regards\'"", \'Comment 36: ""Po konsultacji z Łukaszem jeszcze:update [DHPlantProdBusinessLogicMain].dbo.Recipes set IsProductDefinition = 0 --where Id = \\\'08E5D177-3FB2-4DC3-8A6E-DCAA8E569296\\\'""\', ""Comment 37: \'Thanks you can close the ticket\']""]\nRelated Issues:\n[]\n\n### End'}"
367,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8665\n\n### Instruction:\nZgłaszam problem z algorytmem umów 3*33 miesięcy. Przy wprowadzeniu danych dot. PPK nie mogę zapisać aktualizacji danych u pracownika Justyna Gąsiorowska. Pracownica ma umowę na czas nieokreślony od 01.09.2022.\r\n\r\nProszę o sprawdzenie poprawności działania algorytmu.\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: \'Istnieją zapisy na czas nieokreślony z brakiem końcowej daty : !screenshot-1! To jest przyczyna błędu\'"", ""Comment 4: \'Paulina przekazała mi"", ""Comment 5: że nie jest w stanie wprowadzić/uzupełnić tych zapisów - czy jesteśmy w stanie wyłączyć tą blokadę by mogła je uzupełnić? Lub czy jesteś w stanie je uzupełnić jeżeli Paulina poda mi poprawne dane ? \'"", ""Comment 6: \'Hi"", ""Comment 7: You can temporaily disable below trigger to fill missing data.  !screenshot-2! \'"", \'Comment 8: ""Ok\', \'Comment 9: that\\\'s works - task to close.""]\']\nRelated Issues:\n[]\n\n### End'}"
368,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8664\n\n### Instruction:\nHi,\r\n\r\nShipping Notice L000145524 isn\'t arriving in DHC. Also its orders SO000076185, SOBE000015497 and SOBE000015612 are not arriving.\r\nThey are succesfully processed according to the Communication Log, but I can\'t find them within the orders in DHC.\r\n\r\nCan you please check?\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Dear Theo,For what plant are mentioned Orders?Regards\'"", ""Comment 3: \'Those two are in DHC now"", ""Comment 4: checking the third one!image-2023-03-01-14-06-15-080.png!!image-2023-03-01-14-06-48-094.png!\'"", ""Comment 5: \'For what item wasSOBE000015612 and the shipping notice?\'"", ""Comment 6: \'Hi Aleksandra"", ""Comment 7: SOBE000015612 was for item 303225. I will export it again from ERP\'"", ""Comment 8: \'The plant was VeghelOnly see your question now\'"", ""Comment 9: \'Thank you\'"", ""Comment 10: \'Yes"", ""Comment 11: I have asked few questions :)\'"", ""Comment 12: \'I see that the other order is blocked by our ERP"", ""Comment 13: so I think that we can downgrade this one  to P3 and I even think we can close it already but I like to have the confirmation from our business first.Many thanks again Aleksandra!\'"", ""Comment 14: \'!image-2023-03-01-14-55-25-330.png!!image-2023-03-01-14-55-43-804.png!\'"", ""Comment 15: \'Dla Orderów są dwa mapowania"", ""Comment 16: i te dwa są już w DHC*!image-2023-03-01-14-59-48-967.png!*\'"", ""Comment 17: \'Nie ma kolejek!image-2023-03-01-15-02-21-095.png!!image-2023-03-01-15-02-45-780.png!\'"", ""Comment 18: \'Dear Theo,And what about Shipping Notice? I can see it is mapped with DHC. Is it blocked as well? Waiting for the confirmation from Business then\'"", \'Comment 19: ""I guess the planner has cancelled the shipping notices as the orders are not planned anymore. Let\\\'s close the task :)""\', ""Comment 20: \'Sure. Thank you.Have a nice afternoon :)\'"", ""Comment 21: \'Indeed tey are cancelled :) !image-2023-03-01-15-40-16-730.png!\']""]\nRelated Issues:\n[]\n\n### End'}"
369,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8663\n\n### Instruction:\nHi\r\n\r\nWe have some recipes approved and released from BESTMIX this morning, but they are not integrating to DHC.\r\nWe are trying to open DHH application but it closes automatically when loading the auth screen.\r\n\r\nCould you please help us? We have urgent recipes to accept on DHC and start production.\r\n\r\nNone of attached recipes is on DHC.\r\n\r\nThank you\n\n### Response:\n[""Comment 1: [\'!MicrosoftTeams-image (47)!!MicrosoftTeams-image (48)!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'DHH utraciło połaczenie z serwerem bazy danych i się zawiesiło około godziny 11:30"", ""Comment 4: o 13:33 uruchomiłem wszystko ponownie.\'"", ""Comment 5: \'DHH the connection from the database server dropped and hung"", ""Comment 6: resolved by developers.\'"", ""Comment 7: \'please check.\'"", ""Comment 8: \'Hi PiotrNow we can access DHH and see that the Recipes are there.However they are not in DHC yet. I can imagine that we need to wait the integration time from DHH to DHC"", ""Comment 9: right?Thank you very much!image!\'"", ""Comment 10: \'We are still verifying this issue.\'"", ""Comment 11: \' !screenshot-1! Recipes are processing.\'"", ""Comment 12: \'Hi PiotrNow we can see recipes on DHC. You can close this task.Thank you very much!\']""]\nRelated Issues:\n[]\n\n### End'}"
370,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8662\n\n### Instruction:\nHi,\r\n\r\nI am trying to create additional purchase costs, however, I cannot attach PORI-documents. Please assist\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: \'Could you please specify - send more and full screenshoots from function you start to use. Did you try to use more then one document? If yes please provide numbers.\'"", ""Comment 4: \'RegardsHello,We are closing this task as we haven’treceivedany replyfromyouforalong time. If the issueappearsagain"", ""Comment 5: please raise another task.BRAgnieszka Januszewska\'"", ""Comment 6: \'hi i wish to open this ticket\'"", ""Comment 7: \'!image-1!\'"", ""Comment 8: \'!image-2!!image-3!\'"", ""Comment 9: \'we cant add IPOR of Deliveries to the additional purchase cost\']""]\nRelated Issues:\n[]\n\n### End'}"
371,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8661\n\n### Instruction:\nCould you please give access to Intense for fnadirov@deheus.com?\r\n\r\nFarach Nadirov is her full name and she is replacing Janine Schellekens.\n\n### Response:\n[""Comment 1: [\'Hi,[~mbovene@deheus.com],Janine has been added in test and prod Intense environment.She can feel free to test log in.Best regards,Grzegorz\'"", ""Comment 2: \'Farach is as well?\'"", ""Comment 3: \'Yes"", ""Comment 4: Farach :).\'"", ""Comment 5: \'Can be closed.\'"", \'Comment 6: ""I\\\'m closing task.Best regards,Grzegorz""]\']\nRelated Issues:\n[]\n\n### End'}"
372,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8660\n\n### Instruction:\nPORs processed through Johnson DHP donot generate automatically unless i maually generate them in DHC. Help provide a permanent solution please.\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: \'Lista dokumentów do wygenerowania w DHC bez informacji o błędach,konfiguracja jest !screenshot-2! próba przesłania ręcznie działa - np. 4/3/2023/JN,5/3/2023/JNte z rana do błędy z erpintegratora przy pierwszej próbie:Vehicle Ticket with number 4/3/2023/JN has 0 elements - SKIPPED! !screenshot-1! \'"", ""Comment 3: \'Hej"", \'Comment 4: potrzebowalibyśmy wsparcia w temacie\', \'Comment 5: erpintegrator ma problem z generowaniem dokumentów z VT dla planta ze zgłoszenia \', ""Comment 6: z ręki się generują z poziomu dhc.\\\\rBłąd jaki jest to:\\\\r Vehicle Ticket with number 4/3/2023/JN has 0 elements - SKIPPED!\'"", ""Comment 7: \'DHCService dzieli VT na header i elementy.Najpierw przychodzi header i dodawany jest wpis do VehicleTicketForProcessingA później elementy.Erp integrator pobiera VT"", \'Comment 8: które mają wpis w VehicleTicketForProcessing\', \'Comment 9: jak nie ma elementów\', ""Comment 10: to usuwa wpis z VehicleTicketForProcessing i pomija VT.Dodałem fix i czekam na CR\'"", ""Comment 11: \'Hello"", ""Comment 12: our developers have determined the cause.I will let you know in this task.\'"", ""Comment 13: \'okay\'"", ""Comment 14: \'Michał Kordys zrobił fixa"", ""Comment 15: pytanie jak to będzie rozwiązane jako release czy hotfixem. \\\\rKlient dopytuje o termin i samą realizację.\\\\rAndrzej Roszak może ustalić termin z klientem.\'"", ""Comment 16: \'Hello"", ""Comment 17: ERP Integrator 3.46.0will include this fix.\'"", ""Comment 18: \'okay sir"", ""Comment 19: thank you.please close\']""]\nRelated Issues:\n[]\n\n### End'}"
373,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8659\n\n### Instruction:\nPlease help to check PLR 43710270223003 in CanTho Plant ( 0437) .\r\n\r\nProduction lot number 43710270223003 has item 6101607 consumes 5336,1 kg .But check on ""item history"" or ""Delivery tracking"" item 6101607 is releasing a difference quatity.\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: \'Whether the password to the admin account has been changed? standard does not authorize access. For plant Can Tho.\'"", ""Comment 4: \'i just reset the password: XNeu3R14RE. you can try to set password to standard \'"", \'Comment 5: ""Na plr się nie zgadza ilość z zasobu jest większa o kod 437-S007JJ{code:java}SELECT       [Created]     ,[AggregateType]        ,[Event]      ,[EventType]      ,[UserName]      ,[CorrelationId]  FROM [DHPlantProdBusinessLogicEvents].[dbo].[ProductionLots]  where AggregateId=\\\'a7eedd33-4de8-4aab-b3dd-3c3cc3d71edd\\\' --and Event like \\\'%5688%\\\'  order by Created{code}{code:java} SELECT      [Created]           ,[Event]      ,[EventType]      ,[UserName]      ,[CorrelationId]  FROM [DHPlantStockBusinessLogicEvents].[dbo].[StockUnits]  where AggregateId=\\\'F8DB1F99-6875-4CB7-9984-E8D94F815B41\\\'  order by Created{code}robił realizację PLR jeden user - TAJI !screenshot-1! StockUnits:9FBAEBC6-4C3B-47DC-B848-DEC2F2CB42915EDFD54D-904D-4104-827F-882E79B42F9E1F8F2E0C-86B3-4CBC-AF01-40579DB824DEF8DB1F99-6875-4CB7-9984-E8D94F815B41{code:java} FROM [DHPlantStockBusinessLogicMain].[dbo].[StockUnits]  where barcode=\\\'437-S007JJ\\\'  or Barcode=\\\'437-S007G1\\\'  or Barcode=\\\'437-S007H0\\\'    or Barcode=\\\'437-S007I4\\\'{code}!image-2023-03-03-12-12-45-405!""\', ""Comment 6: \'Hej"", \'Comment 7: ustalenia stand up\', ""Comment 8: proszę o pomoc w analizie - dzięki.\'"", ""Comment 9: \'[~piotr.gaczorek@kotrak.com]To jeszcze przydałyby się backupy DB: prod (main"", \'Comment 10: events\', \'Comment 11: intercontext) oraz stock (main\', \'Comment 12: events\', \'Comment 13: intercontext).Jeżeli backupów się nie da załatwić\', \'Comment 14: to proszę o instrukcję\', ""Comment 15: jak się dobrać do baz na tym środowisku.W przeciwnym razie nie mam jak rozpocząć jakiejkolwiek analizy.\'"", ""Comment 16: \'[~lukasz.furlepa@kotrak.com]Backupy baz https://cloud.kotrak.com/index.php/s/kqXGwgLBp9tQP2p\'"", ""Comment 17: \'[~piotr.gaczorek@kotrak.com] Dzięki wielkie :)Wrzucam plik z wynikiem analizy: [^analysis.txt] W wielkim skrócie zaszły 4 operacje: # PLR został utworzony (status Created) na 15000 kg # Następnie zaszła próba potwierdzenia"", \'Comment 18: ale się nie udało\', \'Comment 19: bo zabrakło stanu dla jednego z surowców (pozakładały się rezerwacje na tyle na ile mogły\', \'Comment 20: prawdopodobnie po FIFO) # Następnie zaszła edycja ilości\', \'Comment 21: na nagłówku na 15960 kg\', \'Comment 22: rezerwacje zaktualizowały się na tyle\', \'Comment 23: na ile mogły (tu już brakowało stanu dla dwóch surowców\', \'Comment 24: ale to nie było potwierdzanie PLR) # Na koniec zaszło udane potwierdzenie PLR\', \'Comment 25: ale ze zmienionymi ilościami\', \'Comment 26: na nagłówku na 14520 kg - coś tu się pokićkało przy rozliczaniu PLRa i się zużyło 352.8 kg jednego z surowców za dużoPatrząc w kod źródłowy\', \'Comment 27: to trochę ciężko wywnioskować dokładnie gdzie jest problem\', \'Comment 28: ale w każdym razie coś w StockEngine nie do końca dobrze aktualizuje rezerwacje\', \'Comment 29: możliwe że ma to związek z tymi ciągłymi zmianami ilości\', \'Comment 30: najpierw w górę\', \'Comment 31: a potem - przy potwierdzaniu - w dół. Ciężko też stwierdzić\', \'Comment 32: dlaczego ten błąd zaszedł tylko dla tego jednego\', \'Comment 33: konkretnego surowca.[~maciej.dobrzanski@kotrak.com] Może nasze asy QA byłyby w stanie wyklikać taki przypadek na którymś z naszych środowisk? Byłoby o wiele prościej dojść do tego\', \'Comment 34: gdzie dokładnie leży problem. Tyle że to jest R8.3. Wstępnie wydaje mi się\', \'Comment 35: że zaczyna się to [podczas rezerwowania SU zaraz przed potwierdzaniem PLR|http://10.10.10.52:82/projects/PLA3/repos/plant.stock.businesslogic/browse/Plant.Stock.BusinessLogic/Application/ProductionLots/ProductionLotService.cs?at=refs%2Fheads%2Fmaster#455]\', \'Comment 36: podczas [wyliczania różnic między aktualnymi rezerwacjami a porządanymi|http://10.10.10.52:82/projects/PLA3/repos/plant.stock.businesslogic/browse/Plant.Stock.BusinessLogic/Domain/Services/ReservationDomainService.cs?at=refs%2Fheads%2Fmaster#198]. Ciężko też powiedzieć\', \'Comment 37: czy w R8.5 jest to naprawione\', ""Comment 38: w każdym razie [różnic jest dość sporo|http://10.10.10.52:82/projects/PLA3/repos/plant.stock.businesslogic/compare/diff?targetBranch=refs%2Fheads%2Fmaster&sourceBranch=refs%2Fheads%2Frelease%2FMV20_R8.5&targetRepoId=539#Plant.Stock.BusinessLogic/Application/ProductionLots/ProductionLotService.cs]. Wrzucam również pełną historię zmian tego PLR:  [^Aggregate_A7EEDD334DE84AABB3DD3C3CC3D71EDD_20230309T092113.txt] Oraz historię zmian każdej z tych czterech opisanych wyżej operacji: # [^Correlation_E8615A1F405C4520BEC3C64B2699B7DD_20230309T121033.txt]  # [^Correlation_CF09CD9C7B824C0D84EC8D322ABA2958_20230309T122525.txt]  # [^Correlation_F9C198B09EAB48CFBDA24FD7069C7DAF_20230309T133531.txt]   # [^Correlation_C7A7B177F08F44ACBB9894F77637964D_20230309T093641.txt] \']""]\nRelated Issues:\n[]\n\n### End'}"
374,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8658\n\n### Instruction:\nThe mentioned document does not appear in the database for exchange (CDNPS_Exchange) between comarch and mpp (invoicing program).\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Kindly approve lowering priority of this task to P2 as P1 issues are only those with a critical or a blocking impact on business processes This seems not to be the case in this issue so we suggest decreasing the issue priority.Regards\'"", ""Comment 3: \'OK"", ""Comment 4: you can decrease priority to P2.\'"", ""Comment 5: \'!image-2023-03-01-11-37-40-994.png!\'"", ""Comment 6: \'2023-03-01 08:00:52,426 [14] INFO - Handled poison message after error. Original conversation ID=\\\\\'5d3186cb-feb7-ed11-8154-00155d030305\\\\\'"", ""Comment 7: error conversation ID=\\\\\'5e3186cb-feb7-ed11-8154-00155d030305\\\\\'"", ""Comment 8: error queue name \\\\\'CDN.TradeInvoiceQueue\\\\\'.2023-03-01 08:00:52,426 [14] INFO - Handled poison message after error. Original conversation ID=\\\\\'5d3186cb-feb7-ed11-8154-00155d030305\\\\\'"", ""Comment 9: error conversation ID=\\\\\'5e3186cb-feb7-ed11-8154-00155d030305\\\\\'"", \'Comment 10: error queue name \\\\\\\'CDN.TradeInvoiceQueue\\\\\\\'.2023-03-01 08:00:52,426 [14] ERROR - Exception occurred when executing task Bookkeeping.Exchange.TradeInvoices.TradeInvoicesSynchronizationTask.\\\\\\\\{""EntityValidationErrors"": [ ""0"": { ""Entity"": ""Bookkeeping.Exchange.TradeInvoices.TradeInvoice""\', \'Comment 11: ""ValidationErrors"": [ {""PropertyName"": ""Description""\', \'Comment 12: ""ErrorMessage"": ""The field Description must be a string or array type with a maximum length of \\\\\\\'200\\\\\\\'.""} ] }C:\\\\\\\\Applications\\\\\\\\Bookkeeping.Service\\\\\\\\Logs\\\'\', ""Comment 13: \'HelloI checked the log in synchronization service and structure of the [CDNPS_Exchange] database and the reason why this document was not synchronized is to long description!image-2023-03-01-12-01-51-924.png!It has 260 characters when system and database allowed max 200.I may change the description from database lelvel in erp xl.Let me know how I may change the description.!image-2023-03-01-12-01-51-924!\'"", ""Comment 14: \'Leave only the first EI complete. EI-2/02/23/CUEOn all others"", ""Comment 15: remove EI- and CUE from the name.\'"", \'Comment 16: ""trngidnumer=1688385update cdn.trnopisyset TnO_Opis=\\\'Popust 1% za rano placanje\', \'Comment 17: EI-2/02/23/CUE\', \'Comment 18: 5/02/23\', \'Comment 19: 6/02/23\', \'Comment 20: 9/02/23\', \'Comment 21: 12/02/23\', \'Comment 22: 15/02/23\', \'Comment 23: 16/02/23\', \'Comment 24: 22/02/23\', \'Comment 25: 24/02/23\', \'Comment 26: 25/02/23\', \'Comment 27: 26/02/23\', \'Comment 28: 29/02/23\', \'Comment 29: 32/02/23\', \'Comment 30: 35/02/23\\\'where TnO_TrnNumer=1688385""\', ""Comment 31: \'Please verify\'"", ""Comment 32: \'Still not resolved. Can you check the Exchange db because it appears that is still not synced with our invoicing application?\'"", ""Comment 33: \'Hello please verify again right know it is in the exchange db!image-2023-03-01-16-09-48-091.png!\'"", ""Comment 34: \'Now it is OK. Thank you.\']""]\nRelated Issues:\n[]\n\n### End'}"
375,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8657\n\n### Instruction:\nGood morning,\r\n\r\nwe have got on problem on DHC.\r\nPlease could you help us.\r\nThis is urgent while we also had an update on DHP location Maasbracht this morning.\r\n\r\nKind regards,\r\n\r\nGerard Geerts\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Hello,Synchronization is working for now"", \'Comment 3: please check.DHC Service now processes messages.There is a very large queue for reprocessing\', ""Comment 4: I will be back with information for you Regards\'"", ""Comment 5: \'!image-2023-03-01-09-03-42-472.png!\'"", ""Comment 6: \'Goodmorning Adrian,thanks for your support.Hopefully you can tell us about the problem.Regards,Gerard\'"", ""Comment 7: \'{code:java}2023-02-28 19:46:52,983 [10] INFO  Evolution.BusinessPlatform.Applications.PlatformApplication [(null)] - Application Evolution.DHCService.PlatformApplication has been stopped!2023-02-28 19:47:53,858 [6] INFO  Evolution.BusinessPlatform.Applications.PlatformApplication [(null)] - Starting application: Evolution.DHCService.PlatformApplication2023-02-28 19:47:53,858 [6] INFO  Evolution.BusinessPlatform.Applications.PlatformApplication [(null)] - Checking application Evolution.DHCService.PlatformApplication manifest file2023-02-28 19:48:00,967 [10] INFO  Evolution.BusinessPlatform.Applications.PlatformApplication [(null)] - Application Evolution.DHCService.PlatformApplication is running!2023-03-01 08:30:55,035 [4] INFO  Evolution.BusinessPlatform.Applications.PlatformApplication [(null)] - Stopping application Evolution.DHCService.PlatformApplication2023-03-01 08:30:55,035 [4] INFO  Evolution.BusinessPlatform.Applications.PlatformApplication [(null)] - Application Evolution.DHCService.PlatformApplication has been stopped!2023-03-01 08:34:21,888 [7] INFO  Evolution.BusinessPlatform.Applications.PlatformApplication [(null)] - Starting application: Evolution.DHCService.PlatformApplication2023-03-01 08:34:21,888 [7] INFO  Evolution.BusinessPlatform.Applications.PlatformApplication [(null)] - Checking application Evolution.DHCService.PlatformApplication manifest file2023-03-01 08:34:28,982 [10] INFO  Evolution.BusinessPlatform.Applications.PlatformApplication [(null)] - Application Evolution.DHCService.PlatformApplication is running!2023-03-01 08:39:23,114 [7] INFO  Evolution.BusinessPlatform.Applications.PlatformApplication [(null)] - Stopping application Evolution.DHCService.PlatformApplication2023-03-01 08:39:23,114 [7] INFO  Evolution.BusinessPlatform.Applications.PlatformApplication [(null)] - Application Evolution.DHCService.PlatformApplication has been stopped!2023-03-01 08:43:11,165 [5] INFO  Evolution.BusinessPlatform.Applications.PlatformApplication [(null)] - Starting application: Evolution.DHCService.PlatformApplication2023-03-01 08:43:11,165 [5] INFO  Evolution.BusinessPlatform.Applications.PlatformApplication [(null)] - Checking application Evolution.DHCService.PlatformApplication manifest file2023-03-01 08:43:18,274 [4] INFO  Evolution.BusinessPlatform.Applications.PlatformApplication [(null)] - Application Evolution.DHCService.PlatformApplication is running!2023-03-01 08:49:18,470 [7] INFO  Evolution.BusinessPlatform.Applications.PlatformApplication [(null)] - Stopping application Evolution.DHCService.PlatformApplication2023-03-01 08:49:18,470 [7] INFO  Evolution.BusinessPlatform.Applications.PlatformApplication [(null)] - Application Evolution.DHCService.PlatformApplication has been stopped!2023-03-01 08:52:19,995 [7] INFO  Evolution.BusinessPlatform.Applications.PlatformApplication [(null)] - Starting application: Evolution.DHCService.PlatformApplication2023-03-01 08:52:19,995 [7] INFO  Evolution.BusinessPlatform.Applications.PlatformApplication [(null)] - Checking application Evolution.DHCService.PlatformApplication manifest file2023-03-01 08:52:27,090 [5] INFO  Evolution.BusinessPlatform.Applications.PlatformApplication [(null)] - Application Evolution.DHCService.PlatformApplication is running!2023-03-01 08:58:15,672 [7] INFO  Evolution.BusinessPlatform.Applications.PlatformApplication [(null)] - Stopping application Evolution.DHCService.PlatformApplication2023-03-01 08:58:15,672 [7] INFO  Evolution.BusinessPlatform.Applications.PlatformApplication [(null)] - Application Evolution.DHCService.PlatformApplication has been stopped!2023-03-01 08:58:19,690 [6] INFO  Evolution.BusinessPlatform.Applications.PlatformApplication [(null)] - Starting application: Evolution.DHCService.PlatformApplication2023-03-01 08:58:19,690 [6] INFO  Evolution.BusinessPlatform.Applications.PlatformApplication [(null)] - Checking application Evolution.DHCService.PlatformApplication manifest file2023-03-01 08:58:26,750 [4] INFO  Evolution.BusinessPlatform.Applications.PlatformApplication [(null)] - Application Evolution.DHCService.PlatformApplication is running!2023-03-01 09:37:03,345 [4] INFO  Evolution.BusinessPlatform.Applications.PlatformApplication [(null)] - Stopping application Evolution.DHCService.PlatformApplication2023-03-01 09:37:03,345 [4] INFO  Evolution.BusinessPlatform.Applications.PlatformApplication [(null)] - Application Evolution.DHCService.PlatformApplication has been stopped!2023-03-01 09:38:42,780 [4] INFO  Evolution.BusinessPlatform.Applications.PlatformApplication [(null)] - Starting application: Evolution.DHCService.PlatformApplication2023-03-01 09:38:42,780 [4] INFO  Evolution.BusinessPlatform.Applications.PlatformApplication [(null)] - Checking application Evolution.DHCService.PlatformApplication manifest file2023-03-01 09:38:49,890 [7] INFO  Evolution.BusinessPlatform.Applications.PlatformApplication [(null)] - Application Evolution.DHCService.PlatformApplication is running!2023-03-01 09:52:35,535 [6] INFO  Evolution.BusinessPlatform.Applications.PlatformApplication [(null)] - Stopping application Evolution.DHCService.PlatformApplication2023-03-01 09:52:35,535 [6] INFO  Evolution.BusinessPlatform.Applications.PlatformApplication [(null)] - Application Evolution.DHCService.PlatformApplication has been stopped!2023-03-01 09:54:10,826 [5] INFO  Evolution.BusinessPlatform.Applications.PlatformApplication [(null)] - Starting application: Evolution.DHCService.PlatformApplication2023-03-01 09:54:10,826 [5] INFO  Evolution.BusinessPlatform.Applications.PlatformApplication [(null)] - Checking application Evolution.DHCService.PlatformApplication manifest file2023-03-01 09:54:17,950 [4] INFO  Evolution.BusinessPlatform.Applications.PlatformApplication [(null)] - Application Evolution.DHCService.PlatformApplication is running!2023-03-01 10:05:09,197 [10] INFO  Evolution.BusinessPlatform.Applications.PlatformApplication [(null)] - Stopping application Evolution.DHCService.PlatformApplication2023-03-01 10:05:09,197 [10] INFO  Evolution.BusinessPlatform.Applications.PlatformApplication [(null)] - Application Evolution.DHCService.PlatformApplication has been stopped!2023-03-01 10:06:43,522 [4] INFO  Evolution.BusinessPlatform.Applications.PlatformApplication [(null)] - Starting application: Evolution.DHCService.PlatformApplication2023-03-01 10:06:43,522 [4] INFO  Evolution.BusinessPlatform.Applications.PlatformApplication [(null)] - Checking application Evolution.DHCService.PlatformApplication manifest file2023-03-01 10:06:50,615 [10] INFO  Evolution.BusinessPlatform.Applications.PlatformApplication [(null)] - Application Evolution.DHCService.PlatformApplication is running!{code}\'"", ""Comment 8: \'Of course"", \'Comment 9: The application looped the process\', ""Comment 10: restarting the service solved the situation.So there is still processing on the application.See screen!image-2023-03-01-10-32-42-264.png|width=455,height=268!I will come back to you with the information once all the news has been reprocessed.\'"", ""Comment 11: \'HelloBack to you with the informationprocessing of the message has been completed !image-2023-03-01-13-07-41-286.png!Should i close your incident or do you need more informations? The problem has been resolved?  Regards\'"", ""Comment 12: \'Good morning Adrian,the problem has been resolved.Thanks for feedback and support on this.Please close this serviceticket.Kind regards,Gerard\']""]\nRelated Issues:\n[]\n\n### End'}"
376,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8656\n\n### Instruction:\nHi\r\n\r\nWe have VT-594/23 released for intake. The user complained that after performing ACCEPT action during bulk VT intake system was too slow, presented a message of error (""Contact system admin"") and now the VT has the wrong *Total weight* value.\r\nThe right value for *Total weight* is 28040\r\nWe don\'t have option to reverse IsAccepted status, and no option to fix the right value.\r\nAlso, when we try to COMPLETE the VT with the wrong value, a message ""Contact system admin"" is displayed\r\n\r\nCould you please fix that?\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: \\\'id:97141CDE-9641-4CE4-BE03-6292DBBBDBACNoooo poleciał timeoucik{code:java}2023-02-22 15:53:51 (8a5ef721-446b-4347-9e29-b9f6b77196a0/Plant.VC.BusinessLogic/BR-4-SV-VM0204/19260/205) [Error] Microsoft.EntityFrameworkCore.Query - An exception occurred while iterating over the results of a query for context type \\\\\\\'""Plant.VC.BusinessLogic.Infrastructure.EF.VCContext""\\\\\\\'.""""""Microsoft.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 (258): The wait operation timed out.   at Microsoft.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj\', \'Comment 4: Boolean callerHasConnectionLock\', \'Comment 5: Boolean asyncClose)   at Microsoft.Data.SqlClient.TdsParserStateObject.ThrowExceptionAndWarning(Boolean callerHasConnectionLock\', \'Comment 6: Boolean asyncClose)   at Microsoft.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject stateObj\', \'Comment 7: UInt32 error)   at Microsoft.Data.SqlClient.TdsParserStateObject.ReadSniSyncOverAsync()   at Microsoft.Data.SqlClient.TdsParserStateObject.TryReadNetworkPacket()   at Microsoft.Data.SqlClient.TdsParserStateObject.TryPrepareBuffer()   at Microsoft.Data.SqlClient.TdsParserStateObject.TryReadByte(Byte& value)   at Microsoft.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior\', \'Comment 8: SqlCommand cmdHandler\', \'Comment 9: SqlDataReader dataStream\', \'Comment 10: BulkCopySimpleResultSet bulkCopyHandler\', \'Comment 11: TdsParserStateObject stateObj\', \'Comment 12: Boolean& dataReady)   at Microsoft.Data.SqlClient.SqlDataReader.TryConsumeMetaData()   at Microsoft.Data.SqlClient.SqlDataReader.get_MetaData()   at Microsoft.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds\', \'Comment 13: RunBehavior runBehavior\', \'Comment 14: String resetOptionsString\', \'Comment 15: Boolean isInternal\', \'Comment 16: Boolean forDescribeParameterEncryption\', \'Comment 17: Boolean shouldCacheForAlwaysEncrypted)   at Microsoft.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior\', \'Comment 18: RunBehavior runBehavior\', \'Comment 19: Boolean returnStream\', \'Comment 20: Boolean isAsync\', \'Comment 21: Int32 timeout\', \'Comment 22: Task& task\', \'Comment 23: Boolean asyncWrite\', \'Comment 24: Boolean inRetry\', \'Comment 25: SqlDataReader ds\', \'Comment 26: Boolean describeParameterEncryptionRequest)   at Microsoft.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior\', \'Comment 27: RunBehavior runBehavior\', \'Comment 28: Boolean returnStream\', \'Comment 29: TaskCompletionSource`1 completion\', \'Comment 30: Int32 timeout\', \'Comment 31: Task& task\', \'Comment 32: Boolean& usedCache\', \'Comment 33: Boolean asyncWrite\', \'Comment 34: Boolean inRetry\', \'Comment 35: 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.Query.Internal.SingleQueryingEnumerable`1.Enumerator.InitializeReader(Enumerator enumerator)   at Microsoft.EntityFrameworkCore.SqlServer.Storage.Internal.SqlServerExecutionStrategy.Execute[TState,TResult](TState state\', \'Comment 36: Func`3 operation\', \'Comment 37: Func`3 verifySucceeded)   at Microsoft.EntityFrameworkCore.Query.Internal.SingleQueryingEnumerable`1.Enumerator.MoveNext()ClientConnectionId:23c5c591-641f-46b4-aa72-aab9f18ba26eError Number:-2,State:0,Class:11""Microsoft.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 (258): The wait operation timed out.   at Microsoft.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj\', \'Comment 38: Boolean callerHasConnectionLock\', \'Comment 39: Boolean asyncClose)   at Microsoft.Data.SqlClient.TdsParserStateObject.ThrowExceptionAndWarning(Boolean callerHasConnectionLock\', \'Comment 40: Boolean asyncClose)   at Microsoft.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject stateObj\', \'Comment 41: UInt32 error)   at Microsoft.Data.SqlClient.TdsParserStateObject.ReadSniSyncOverAsync()   at Microsoft.Data.SqlClient.TdsParserStateObject.TryReadNetworkPacket()   at Microsoft.Data.SqlClient.TdsParserStateObject.TryPrepareBuffer()   at Microsoft.Data.SqlClient.TdsParserStateObject.TryReadByte(Byte& value)   at Microsoft.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior\', \'Comment 42: SqlCommand cmdHandler\', \'Comment 43: SqlDataReader dataStream\', \'Comment 44: BulkCopySimpleResultSet bulkCopyHandler\', \'Comment 45: TdsParserStateObject stateObj\', \'Comment 46: Boolean& dataReady)   at Microsoft.Data.SqlClient.SqlDataReader.TryConsumeMetaData()   at Microsoft.Data.SqlClient.SqlDataReader.get_MetaData()   at Microsoft.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds\', \'Comment 47: RunBehavior runBehavior\', \'Comment 48: String resetOptionsString\', \'Comment 49: Boolean isInternal\', \'Comment 50: Boolean forDescribeParameterEncryption\', \'Comment 51: Boolean shouldCacheForAlwaysEncrypted)   at Microsoft.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior\', \'Comment 52: RunBehavior runBehavior\', \'Comment 53: Boolean returnStream\', \'Comment 54: Boolean isAsync\', \'Comment 55: Int32 timeout\', \'Comment 56: Task& task\', \'Comment 57: Boolean asyncWrite\', \'Comment 58: Boolean inRetry\', \'Comment 59: SqlDataReader ds\', \'Comment 60: Boolean describeParameterEncryptionRequest)   at Microsoft.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior\', \'Comment 61: RunBehavior runBehavior\', \'Comment 62: Boolean returnStream\', \'Comment 63: TaskCompletionSource`1 completion\', \'Comment 64: Int32 timeout\', \'Comment 65: Task& task\', \'Comment 66: Boolean& usedCache\', \'Comment 67: Boolean asyncWrite\', \'Comment 68: Boolean inRetry\', \'Comment 69: 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.Query.Internal.SingleQueryingEnumerable`1.Enumerator.InitializeReader(Enumerator enumerator)   at Microsoft.EntityFrameworkCore.SqlServer.Storage.Internal.SqlServerExecutionStrategy.Execute[TState,TResult](TState state\', \'Comment 70: Func`3 operation\', \'Comment 71: Func`3 verifySucceeded)   at Microsoft.EntityFrameworkCore.Query.Internal.SingleQueryingEnumerable`1.Enumerator.MoveNext()ClientConnectionId:23c5c591-641f-46b4-aa72-aab9f18ba26eError Number:-2,State:0,Class:112023-02-22 21:00:11 (/Plant.VC.BusinessLogic/BR-4-SV-VM0204/19260/9) [Error] Microsoft.EntityFrameworkCore.Database.Command - Failed executing DbCommand (""0""ms) [Parameters=[""""]\', ""Comment 72: CommandType=\\\\\'Text\\\\\'"", \'Comment 73: CommandTimeout=\\\\\\\'30\\\\\\\']""""""SELECT TOP 0 T.[Id] INTO [dbo].[InboundMessagesTempdfc59f5f] FROM [dbo].[InboundMessages] AS T LEFT JOIN [dbo].[InboundMessages] AS Source ON 1 = 0;""2023-02-22 21:00:46 (/Plant.VC.BusinessLogic/BR-4-SV-VM0204/19260/9) [Error] Microsoft.EntityFrameworkCore.Database.Command - Failed executing DbCommand (""0""ms) [Parameters=[""""]\', ""Comment 74: CommandType=\\\\\'Text\\\\\'"", \'Comment 75: CommandTimeout=\\\\\\\'30\\\\\\\']""""""SELECT TOP 0 T.[Id] INTO [dbo].[InboundMessagesTemp9dc27413] FROM [dbo].[InboundMessages] AS T LEFT JOIN [dbo].[InboundMessages] AS Source ON 1 = 0;""{code}\\\'\', ""Comment 76: \'!image-2023-03-01-08-25-17-358.png!!image-2023-03-01-08-50-14-982.png!!image-2023-03-01-08-50-14-982!\'"", ""Comment 77: \'Dear Maicon,I think better option would be cancel this vt as it is in progress and create a new one. Please"", ""Comment 78: let me know if it is fine for you.Regards!image-2023-03-01-10-44-47-073.png!\'"", ""Comment 79: \'Hi AleksandraIf we cancel his VT"", \'Comment 80: the new one will generate a new SU barcode\', \'Comment 81: right?We cannot cancel current SU barcode because the user already scanned it on PCS. And the consumption already started for it.Unless you keep the current SU barcode for the new VT document\', ""Comment 82: OK we could do it.Thank you\'"", ""Comment 83: \'Hi Maicon,Why are users scanning barcode and start consumption before VT is not copleted?Please"", \'Comment 84: check now\', ""Comment 85: you should complete itRegards\'"", \'Comment 86: ""Hi AleksandraThey used because we had this issue on DHP and they couldn\\\'t wait for the fix and started using it.When we click COMPLETE button\', \'Comment 87: the message appears.[:\\\'(]!image-1!""\', ""Comment 88: \'Please"", ""Comment 89: try again\'"", ""Comment 90: \'Hi Aleksandra Now I was able to close it.You can close this task.Thank you very much!\'"", ""Comment 91: \'Thank you\']""]\nRelated Issues:\n[]\n\n### End'}"
377,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8655\n\n### Instruction:\n This warehouse order should have had the status Executed\r\n\r\nVT has been closed.\r\nstatus of warehouse order then should be Executed\r\n\r\nwhat was going on here and can you change the status to Executed?\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: \'[[DHP 3.0]Incorrect WO status|onenote:https://kotrak.sharepoint.com/sites/erpasysta/Shared%20Documents/Baza%20wiedzy/Baza%20Wiedzy%20-%20ERPSD/Klienci/DEHEUS/DEHEUS%20APPLICATIONS/RPA/Baza%20wiedzy.one#%5bDHP%203.0%5dIncorrect%20WO%20status&section-id=\\\\\\\\{A2F09CD6-A23A-42F3-92F5-ED66B521455B}&page-id=\\\\\\\\{325B9921-0AB5-4E36-A871-095DF356E2F1}&end] ([Widok sieci Web|https://kotrak.sharepoint.com/sites/erpasysta/_layouts/OneNote.aspx?id=%2Fsites%2Ferpasysta%2FShared%20Documents%2FBaza%20wiedzy%2FBaza%20Wiedzy%20-%20ERPSD&wd=target%28Klienci%2FDEHEUS%2FDEHEUS%20APPLICATIONS%2FRPA%2FBaza%20wiedzy.one%7CA2F09CD6-A23A-42F3-92F5-ED66B521455B%2F%5BDHP%203.0%5DIncorrect%20WO%20status%7C325B9921-0AB5-4E36-A871-095DF356E2F1%2F%29])\'"", ""Comment 4: \'Status was fixed please verify!image-2023-02-28-19-48-33-363.png!\'"", ""Comment 5: \'I also check logs from the 9.01.2023 but could not see any error log.\'"", ""Comment 6: \'May we close the task?\'"", ""Comment 7: \'close the task\']""]\nRelated Issues:\n[]\n\n### End'}"
378,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8654\n\n### Instruction:\nHello,\r\n\r\nattached you find a list of lot report for which we miss the raw material consumptions in the ERP: It means that the quantity finished product is send, but after that the raw material consumption is not resend. Can you resend these lot reports from DHC. as there is no manual possibility to do this \n\n### Response:\n[""Comment 1: [\'[^Missing lot reports in ERP.xlsx] _(284 kB)_\'"", ""Comment 2: \'Due to the financially year-end closing"", ""Comment 3: this has high prio\'"", ""Comment 4: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 5: \'Dear,According to the service agreement this task should be categorized as a service request.Kindly approve change of the type of this task.Also this file include over 3000 plr"", ""Comment 6: it will be time consuming.For what date you need it to be resend? If it may wait until tomorrow pleaseapprove lowering priority of this task to P2 as P1 issues are only those with a critical or a blocking impact on business processes .BRAgnieszka Januszewska\'"", \'Comment 7: ""Hi Agnieska\', ""Comment 8: it\'s unclear if this is a service request: if these reports are missing in the ERP/Integration layer"", \'Comment 9: then it looks like they are not send\', \'Comment 10: hence being an application incident? Task can wait untill tomorrow\', \'Comment 11: but as said in the comment below\', \'Comment 12: due to the year-end closing over 2022 these reports are important and should be (re)send as soon as possible\', \'Comment 13: Agreed you can lower priority""\', ""Comment 14: \'Total to be resend is around 1500: only those with DHP lot number should be resend (I tried to filter on that)\'"", ""Comment 15: \'Thank you.I asked Przemysław to help with that issue"", ""Comment 16: he will look at this tommorow.\'"", ""Comment 17: \'[~przemyslaw.przybyszewski@kotrak.com]byłabym wdzięczna jakbyś to im wysłał"", ""Comment 18: możesz się też odnieśc do koncepcji Thomasa że to nasza wina.\'"", \'Comment 19: ""[~TDankers@deheus.com]I\\\'ve resend lot reports that were correct\', \'Comment 20: in[^Missing PLRs.xlsx]I\\\'ve prepared list of lot reports that couldn\\\'t be send to ERP.""\', \'Comment 21: ""Hi [~TDankers@deheus.com]\', \'Comment 22: remaining PLR\\\'s (case with missing technologies elements) has been resent.""\', ""Comment 23: \'Thanks"", ""Comment 24: we can close this ticket\'"", ""Comment 25: \'Thank you\']""]\nRelated Issues:\n[]\n\n### End'}"
379,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8653\n\n### Instruction:\nWe need to know what our users did and caused this to happened. Namely in the time period 01.01.2023 until today some PLR (23.-24./02/2023 probably) has been confirmed but we are not sure if the materials are on stock after production because we have missing quantity for Item No. 10420300. The amount in CDN is 5666.73 kg and it misses 12753.27 kg more to close VTs which is 18420 kg in total. The same problem we had last year with the same item. Can you please check this? Thank you. \n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Please clarify"", \'Comment 3: I checked the item from the pharmacy level in ERP XL no errors or reservations are shown\', \'Comment 4: what do I mean by ""and it misses 12753.27"" is this item physically in stock and not in the documents? I can see to vt not generatedI don\\\\\\\'t see such quantities or PLR in DHP either. On top of that the item given is a product not a material\', ""Comment 5: so it is not consumed to handle other goods.In DHC all PRL are generated.So please be more specific.\'"", \'Comment 6: ""vte nie jest spiety z zadnym deliveryselect * from VehicleTickets vt join VehicleTicketElements ve on ve.VehicleTicketId=vt.id where DocumentNumber like \\\'572/2/2023%\\\'""\', ""Comment 7: \'this item is already loaded and delivered to costumers. PLR is confirmed and also JO. i have checked every JO from beginning of the year and they are all in system. from some reason"", ""Comment 8: quantity for this item is not on stock in system.\'"", ""Comment 9: \'Do you need more info from Vukota or this is enough? Thanks.\'"", ""Comment 10: \'I so pierwtly verified if there are any discrepancies on the erp xl side. However"", \'Comment 11: from the documents the status is correct. Currently\', ""Comment 12: I see 2 SOR documents generated by another operator than ERPIntegrator for the amount of 5020 kg. SOR-1/01/23/SMSOR-2/01/23/SMWhich will cause a discrepancy between the comparison with documents created from dhc. Can I ask in what way you calculate the expected quantity ?Translated with www.DeepL.com/Translator (free version)\'"", \'Comment 13: ""select * from cdn.twrkarty where twr_kod =\\\'10420300\\\'select cdn.nazwaobiektu(trn_gidtyp,trn_gidnumer,1,2),TrN_OpeNumerW,tre_ilosc\', \'Comment 14: TrN_Stan,* from cdn.TraElem join cdn.TraNag on trn_gidnumer=tre_gidnumerwhere TrN_TrNRok>=2022 and tre_twrnumer=5211 and TrN_OpeNumerw<>13 and trn_gidtyp=2001select * from cdn.opekarty where ope_ident like \\\'erp%\\\' or ope_gidnumer=143""\', ""Comment 15: \'in attachment VT`s which is stuck in DHC. when I add up these quantities that have been loaded and subtract the current balance in the program"", ""Comment 16: i get the difference that is missing from the balance.!Screenshot_11!\'"", ""Comment 17: \'1.In ERP XL checked with a special function the state of goods whether there is no shortage and possibly repair the state ( for example"", ""Comment 18: when some document is not damaged.  In ERPXL there are no such errors for this commodity. 2. there are no stocks in DHC.  3. in ERP XL there are documents created from DHC and documents created by users - I gave an example.But for both VT I use generate options and there was error but after service restart I generated SORc for VT 562/2/2023!image-2023-03-08-10-57-59-184.png|width=1117,height=275!For VT 572/2for s warehouse there are 3726 ,73 kg for sale in erp xl on warehouse S!image-2023-03-08-11-00-56-768.png![^image-2023-03-08-10-57-59-184.png]!image-2023-03-08-11-00-50-156! !image-2023-03-08-11-00-56-768!\'"", ""Comment 19: \'!562.PNG|thumbnail! !draftplr.PNG|thumbnail! !jonorders.PNG|thumbnail!\'"", ""Comment 20: \'I also checked the since the 01.01.023 there is a lot of PRL in draft ( still not confirmed in DHP)So after confirm them in dhp"", \'Comment 21: sending PLR for missing plr to dhc and dhp\', ""Comment 22: the new delivery and IR+ document will be added.Also you may find in ERP XL Job Orders for that item that are not realized ( so the not new IR+ documents where created).So please verify what JO and PLR could be fullfield to create stocks for Item you are missing. !562.PNG!\'"", ""Comment 23: \'May we close the task?\'"", ""Comment 24: \'Hello,We are closing this task as we haven’treceivedany replyfromyouforalong time. If the issueappearsagain"", ""Comment 25: please raise another task.Regards\']""]\nRelated Issues:\n[]\n\n### End'}"
380,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8652\n\n### Instruction:\nWe have problem with xml, the information are genereated different, in attached I added some difference that I found. I sent the current format of xml but the lab not accept, the main problem is the code, should appear 178 but is showing LX178 on new xml.\r\nCould you fix it please?\r\n\n\n### Response:\n[""Comment 1: [\'[^DHHIMP90000001.xml] _(2 kB)_!XML!!XML2!\'"", ""Comment 2: \'old format[^DHHIMP90008640.xml] _(3 kB)_\'"", ""Comment 3: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 4: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 5: \'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 6: \'[~maciej.dobrzanski@kotrak.com]chyba potrzebujemy wsparcia w tym temacie :)\'"", ""Comment 7: \'[~maciej.dobrzanski@kotrak.com] dogrzebałam się to jakiegoś starego taska"", \'Comment 8: w którym była informacja o sample type: ""Sample Item Code (cutting-> only numbers\', \'Comment 9: NO LETTERS) DHP Item code- ONLY NUMBERS !!!"".Sprawdziłam na 170 i dla itema LX110 w sample type pojawia się *LX110*\', ""Comment 10: natomiast dla np. 7680OK-B10 jest poprawnie *768010*. Zgłosiłam DAP-13380.\'"", ""Comment 11: \'[~aleksandra.przybylek@kotrak.com]Ustalam z klientem jak dokładnie powinno to działać.\'"", ""Comment 12: \'[~maciej.dobrzanski@kotrak.com]pewka\'"", ""Comment 13: \'Dear Priscyla,Could you please precise how it should work now?We found that for example for itemLX110"", ""Comment 14: in sample type we have*LX110,*whereas for item7680OK-B10 we have correct*768010*.Regards\'"", ""Comment 15: \'Hi Aleksandra,I asked help for Bart and he explained the fields with problem are sampletype"", \'Comment 16: should appear 178\', \'Comment 17: but is showing LX178\', ""Comment 18: ArticleCode shoud appear 178 but is showing LX178 and the result should be with dot and is showing with comma. Could you fix it?Correct format:<sampletype>178</sampletype> <ArticleCode>178</ArticleCode><results>      <code>VCRDRYI</code>      <desc>Input DM weight in</desc>      <val>214.75</val>      <sign />      <date>2022-12-21</date>      <cnct>0</cnct>    </results>\'"", ""Comment 19: \'Thank you\'"", \'Comment 20: \\\'[~maciej.dobrzanski@kotrak.com] poza LX to jeszcze klient wspomina o ""should be with dot and is showing with comma""\\\'\', ""Comment 21: \'Rozmawiałem z [~piotr.chmielarski@kotrak.com] przekażemy ten temat do Theo niech on to ustali jak ma działać.\'"", ""Comment 22: \'Mebrate answer that one more field is wrong"", ""Comment 23:  <CountryId>BR</CountryId> should be  <CountryId>3</CountryId>Could you check this field too?\'"", ""Comment 24: \'ok\'"", ""Comment 25: \'@Priscyla"", \'Comment 26: I suggest a short meeting with Bart Lunenburg from the lab\', \'Comment 27: Mebrate\', \'Comment 28: Sharlene from South Africa and perhaps Joost Jansens from the R&D department to discuss how to approach this.it is currently working form RSA and CZ and I am affraid if we change things for you\', ""Comment 29: it impacts other Business Units as wellDo you agree?\'"", ""Comment 30: \'Hi Theo,yes"", ""Comment 31: I agree. Could you schedule the meeting?Thank you\'"", \'Comment 32: ""Hello GuysWe changed the configuration on QAM of country from string *BR* to  number *3*.We also requested to the operator to change its language from _pt-BR_ to _en-US_ when generating XML file.Let\\\'s see what happens.Thank you""\', \'Comment 33: ""HiTest with country configuration and language setup on the operator UI profile did work!However I\\\'d like to know why the users\\\'s language preference is interfering with the  XML generation. BLGG uses an international decimal separator!I see this as a bug on XML generation engine. Could you fix that\', \'Comment 34: please?Thank you""\', \'Comment 35: ""Hi,we tested current format of XML and it\\\'s working automatically. So we don\\\'t need to change the <sampletype> and <ArticleCode>. The Country ID is fixed too.So now is missing only Maicon request about the needs to change language to create correct XML.Thank you""\', \'Comment 36: ""Hi [~aleksandra.przybylek@kotrak.com]Did you have time to check Priscyla\\\'s last comment?Thank you""\', ""Comment 37: \'Dear Maicon,This task is under dev analysis so the most proper person to ask about the language change will by still [~maciej.dobrzanski@kotrak.com]. So we are waiting for Dev Team feedback then.Regards\'"", ""Comment 38: \'Hi [~mberbert@deheus.com]We can confirm that language is being considered while generating decimal values for XML files.This issue needs to have a GDC ticket created"", ""Comment 39: but first I need to speak with Theo.I will inform you about the output of the discussion.\'"", ""Comment 40: \'Thank you very much!\'"", ""Comment 41: \'Hi [~mberbert@deheus.com],I created a GDC-900 to solve the issue with the generation of decimals values\']""]\nRelated Issues:\n[\'DAP-7671\', \'DAP-6810\', \'DAP-13380\']\n\n### End'}"
381,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8651\n\n### Instruction:\nProblems clipping SOR-155/09/2022 with SORC-218.09\r\n\r\nSOR-155 was on invoice 9/460/2022 as zero. The thought off the user was to remove it and then sor-155/09/2022 will come back in the list, but that was not the case\r\n\r\nAfter clicking OK the last screen was shown\n\n### Response:\n[""Comment 1: [\'!image-2!!image-3!!image-4!!image-5!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'SOR-155/09/2022 is already clipped and booked at this document :!image-2023-02-28-17-44-49-607.png!Please try to cancel it (the clipped invoice) and then try agaian to creat clipped invoice\'"", ""Comment 4: \'!image!\'"", ""Comment 5: \'!relateddocs_1!\'"", ""Comment 6: \'HelloI see that the previous information was not clear I hope it will be clearer now.Invoice 460/09/2020 is cancelled.Previously I focused on SOR!image-2023-03-14-08-28-55-759.png|width=830,height=121!When you are looking at the message you send there is an info :!image-2023-03-14-08-33-17-027.png!The source document for SORC 218/09 is the SOR 1551.If you want to created clip invoice for pair of SOR and SORCthe SORC in to be at this clipped source document SOR2. You can only use one time a SOR/SORC document on clipped invoiceSo because the SOR 155 is already clipped"", \'Comment 7: when you are creating new clipped invoice it is skipped and then ERP XL is trying to create clip inoice only for SORC 218\', \'Comment 8: so you got this message.3. How to find related doucments on SOR\', ""Comment 9: SORCThere is few way to see if SOR is clipped already- by related documents buttom!relateddocs_1.png! * on document header!image-2023-03-14-08-55-34-901.png!So today I verified again documents and situation Is still the same.The SOR 155/09/2022 is clipped with visible on screenshots invoice 512/09/2022And solution is still the same * cancell this invoice * create new clipp document\'"", ""Comment 10: \'Hello,We are closing this task as we haven’treceivedany replyfromyouforalong time. If the issueappearsagain"", ""Comment 11: please raise another task.Regards\']""]\nRelated Issues:\n[]\n\n### End'}"
382,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8650\n\n### Instruction:\nClippen SOR 29/10/2022 not working with SOR 26+27+28/10/2022\r\n\r\nThe VAT amount of € 771.75 is not included\n\n### Response:\n[""Comment 1: [\'!image-2!!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: \'!t2.PNG|thumbnail!\'"", ""Comment 4: \'Reason for that situation is that in sor 29/9 there is diffrent value in that place:!t2.PNG!it should be the same in all documentsfor 27-29/10 we have type 21 - return of goods!image-2023-02-28-17-34-34-600.png!In that case you may clipped all the 3 sorc document"", ""Comment 5: Or if you ask we change them to type 11 via database.\'"", ""Comment 6: \'May we close the task?\'"", ""Comment 7: \'Hello,We are closing this task as we haven’treceivedany replyfromyouforalong time. If the issueappearsagain"", ""Comment 8: please raise another task.Regards\']""]\nRelated Issues:\n[]\n\n### End'}"
383,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8649\n\n### Instruction:\nThe report is not showing the correct quantity for orders. We have sales order for item SUP7159-T-S25 but the column for total sales order is empty.\r\nWe need this report working to schedule productions.\r\n\r\nCould you check, please?\r\n\r\nHi Maciej Dobrzański\r\nthe column Total ordered needs to show Total quantity of all order not checked by period, we need total integrated orders (without quantity loaded). In the column Order quantity for next days, system needs to consider quantity of days added inicially. So report is wrong, Could you fix it?\r\n\r\nWe notice that in column blocked system is adding reservation, is wrong too, reservation needs to be removed from Total ordered quantity and Order quantity for next days when VT is loaded. Could you fix this columns too?\r\n\r\nI attached the first request to explain better. We need to fix column blocked, total ordered, and Order for next days.\r\n(https://helpdesk.kotrak.com/browse/DHITS-722)\n\n### Response:\n[""Comment 1: [\'!image-2023-02-25-10-32-54-598!!image-2023-02-25-10-33-58-694![^IMPROVEMENT – PRODUCTION V3.pdf] _(1,18 MB)_\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Do przetestowania w GDC\'"", ""Comment 4: \'!ItemsSummary!\'"", ""Comment 5: \'!44! !75! !105!!Items summary_fields!\'"", \'Comment 6: \\\'Dear [~psilva@deheus.com]1. ""the column Total ordered needs to show Total quantity of all order not checked by period\', \'Comment 7: we need total integrated orders (without quantity loaded). In the column Order quantity for next days\', \'Comment 8: system needs to consider quantity of days added inicially. So report is wrong\', \'Comment 9: Could you fix it?""* please verify attached pictures from our tests on RC Prod server. Total ordered shows Total quantity of all orders. * ""we need total integrated orders (without quantity loaded)"" => what to do you mean? * ""In the column Order quantity for next days"" => system show a proper quantity based on value typed (number of days)2.""We notice that in column blocked system is adding reservation\', \'Comment 10: is wrong too\', \'Comment 11: reservation needs to be removed from Total ordered quantity and Order quantity for next days when VT is loaded. Could you fix this columns too?""* ""We notice that in column blocked system is adding reservation"" => yes. this quantity is on the truck\', \'Comment 12: but VT is not closed. This quantity is reserved. If we will exclude Reserved quantity from this column (Blocked)\', \'Comment 13: do you need to have a new column e.g. \\\\\\\'Reserved quantity\\\\\\\' ?  * ""reservation needs to be removed from Total ordered quantity and Order quantity for next days when"" => I don\\\\\\\'t understand. If quantity is reserved (VT is not closed) you want to remote it from these 2 columns? But in these 2 columns system shows quantity based on Order. But reservation is related to documents from DHP\', ""Comment 14: not from ERP. !44!  !75!  !105!  !Items summary_fields! \'"", ""Comment 15: \'[~asysta@kotrak.pl] przesuniecie status ? Niech teraz klient odpowie.\'"", ""Comment 16: \'Dear Marcin,What we need and the problems that we have:Current columns in DHP 3.0:1 - Stock:            1.1 Current functionality: is showing total quantity           1.2 Correct functionality: show the total quantity of productions closed (is showing production with pallet label confirmed)2 - Blocked:             2.1 Current functionality: is showing blocked items and with reservation            2.2 Correct functionality: show only blocked items (by warehouse and quality"", \'Comment 17: for production and sales)            *Suggestion: add new column with reservation\', \'Comment 18: and in orders is not change nothing3 - Real available:             2.1 Current functionality: is correct            2.2 Correct functionality:4 - Total Ordered quantity:             2.1 Current functionality: is showing all sales order            2.2 Correct functionality: needs to show total orders less reservation of items loaded            *Suggestion: add new column with reservation\', \'Comment 19: and in orders is not change nothing5 - Free quantity:             2.1 Current functionality: is correct            2.2 Correct functionality:6 - Ordered quantity for the next days:             2.1 Current functionality: is showing all orders per period            2.2 Correct functionality: show all orders per period less reservation of items loaded            *Suggestion: add new column with reservation\', \'Comment 20: and in orders is not change nothing7 - Production order in progress:             2.1 Current functionality: is showing all productions with Production order or PLR opened            2.2 Correct functionality: the functionality is correct if the Stock column will be fixed and not show confirmed barcodes. Because in this column is showing production opened and in stock we already have confirmed barcodes\', \'Comment 21: and is duplicationg information. Stock or Production order column should be fixed. If is not possible fix Stock\', \'Comment 22: this column should show only production with barcodes to be confirmed8 - Available stock:             2.1 Current functionality: is correct            2.2 Correct functionality: if create new column with reservation\', \'Comment 23: needs to include in calculationMarcin questions:""we need total integrated orders (without quantity loaded)"" => what to do you mean? In DHP 2.5\', \'Comment 24: system add all sales orders/internal orders\', \'Comment 25: and reduce quantity loaded in VT\', ""Comment 26: this is what we call of quantity to loaddo you need to have a new column e.g. \\\\\'Reserved quantity\\\\\' ? we had this reservation in previus question"", \'Comment 27: the calculation was in total order and order for next days\', \'Comment 28: but yes\', ""Comment 29: can be new column.\'"", \'Comment 30: ""Hi [~psilva@deheus.com]1 - Stock:1.1 Current functionality: is showing total quantity1.2 Correct functionality: show the total quantity of productions closed (is showing production with pallet label confirmed) [MK]=> so in column we should show all UL\\\'s with status OnStock from WO(IP) for which we have PLR NOT confirmed yet. And these UL\\\'s cannot be shown in colulmn \\\'Production order in progress\\\' ?2 - Blocked:2.1 Current functionality: is showing blocked items and with reservation2.2 Correct functionality: show only blocked items (by warehouse and quality\', \'Comment 31: for production and sales)*Suggestion: add new column with reservation\', \'Comment 32: and in orders is not change nothing[MK] => we should add new column Reserved ? and this reserved quantity should be included in column \\\'Real available\\\' or \\\'Available\\\'?""\', ""Comment 33: \'[~asysta@kotrak.pl] czy możecie przesunąć status taska? Czekamy aktualnie na odpowiedź klienta. Dzięki\'"", \'Comment 34: ""Hi Marcin1 - Stock:1.1 Current functionality: is showing total quantity1.2 Correct functionality: show the total quantity of productions closed (is showing production with pallet label confirmed)[MK]=> so in column we should show all UL\\\'s with status OnStock from WO(IP) for which we have PLR NOT confirmed yet.And these UL\\\'s cannot be shown in colulmn \\\'Production order in progress\\\' ?[PS] We need to have only one column with PLR in progress. We can\\\'t have productions not finished in column Stock. So column Stock shows only productions confirmed and column Production order in progress show Production order not started and PLR not confirmed.2 - Blocked:2.1 Current functionality: is showing blocked items and with reservation2.2 Correct functionality: show only blocked items (by warehouse and quality\', \'Comment 35: for production and sales)*Suggestion: add new column with reservation\', ""Comment 36: and in orders is not change nothing[MK] => we should add new column Reserved ? and this reserved quantity should be included in column \'Real available\' or \'Available\'?[PS] yes"", \'Comment 37: you need to add column Reserved. The column should be calculated in the Real available!items!""\', ""Comment 38: \'Ordered quantity for next days - rozmawiałem z Priscyla"", ""Comment 39: w DHP2.5 tutaj liczył również ilości z Orderów dla których data realizacja już jest w przeszłości 0 klient jeszcze nie odebrał\'"", ""Comment 40: \'[~psilva@deheus.com]"", \'Comment 41: I have discussed with [~maciej.dobrzanski@kotrak.com] about these changes in the report and after verification we agreed that it is not a bug\', \'Comment 42: but changes in the report. Please create GDC for this report. We will continue in new GDC.Remark: I think\', ""Comment 43: GDC-859 should be delivered after this new GDC will be finished.\'"", ""Comment 44: \'Dear [~psilva@deheus.com]Have you raised a GDC task? Can we close this task?Regards\'"", \'Comment 45: ""Marcin and Aleksandra,I\\\'m asking the same information from report available in DHP 2.5 and 2.7. In  GDC-859 we asked improvement (add more columns) but in report we asked the same that was available in old version. I disagree\', \'Comment 46: is not GDC. Can we talk about it?Thank you""]\']\nRelated Issues:\n[]\n\n### End'}"
384,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8648\n\n### Instruction:\nHello, this morning DHP is updated. User now reports that packing slips are not printed for dispatches. Please check and fix as soon as possible. Also pleasse check relation with release to avoid it coming days with other updates\r\n\r\nthanks\n\n### Response:\n[""Comment 1: [\'VT-614 and VT-628 are examples\'"", ""Comment 2: \'Both automatic as manually"", ""Comment 3: there is no xml send to transform\'"", ""Comment 4: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 5: \'po restarcie usługi printserver poszło.Wcześniej błędy:2023-02-28 14:10:41 (/Plant.Printout.Print.Server/DHVD01AP179/12756/31) [Error] Kotrak.Common.Infrastructure.Integration.Filters.InboundMessagesProcessFilter - Error during process inbound message\'"", ""Comment 6: \'plugin w config byl zly - poprawa dev.\'"", ""Comment 7: \'Please check should be working now.\'"", ""Comment 8: \'You can close the ticket\']""]\nRelated Issues:\n[]\n\n### End'}"
385,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8647\n\n### Instruction:\nUser is working from home and again he has problems with the screen for accounting.\r\nSometimes it goes wel and sometimes it goes wrong.\r\n\r\nSee also DGS-8637\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image-2!!image-3!\'"", ""Comment 2: \'SDNL-39660\'"", ""Comment 3: \'!image-4!\'"", ""Comment 4: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 5: \'*XL/974177*\'"", ""Comment 6: \'Dear Bert,I have few questions as all your tasks with integrated login and not working Accounting refers to one - the same user.So: 1. Does the issue only appears when user orks from home?2. If yes"", \'Comment 7: is user connected via VPN to domain?3. Does other modules behave the same way as Accounting? (if you do not know\', ""Comment 8: please ask user to check)4. Does user connect to Terminal Server or he has ERP XL installed on his desktop?Regards\'"", ""Comment 9: \'When first opening sales and orders and afther this accounting there is no problem.Very strange!image!\'"", ""Comment 10: \'1. Does the issue only appears when user orks from home?2. If yes"", ""Comment 11: is user connected via VPN to domain?3. Does user connect to Terminal Server or he has ERP XL installed on his desktop?\'"", ""Comment 12: \'It appears when he is working from home and on the office connected with kabel\'"", ""Comment 13: \'2. Is user connected via VPN to domain when working from home?3. Does user connect to Terminal Server or he has ERP XL installed on his desktop?\'"", ""Comment 14: \'User is always logging in using : Citrix\'"", ""Comment 15: \'Hello,I have consulted this issue with producer. They suggested one more thing to check. Please"", \'Comment 16: see their comment below:_{color:#0747a6}Problems with loading menus may rather be caused by cooperation with printers in the system.{color}__{color:#0747a6}Please verify how the login works if we set the default printer in Windows in the terminal session to the printer from the terminal server named: Microsoft Print to PDF and disable printer mapping when logging into the session.{color}_{color:#172b4d}Please\', ""Comment 17: check and let me know.{color}{color:#172b4d}Regards{color}\'"", ""Comment 18: \'I just reported : User is always logging in using : CitrixHow is it possible that sometimes things go well and sometimes not well?\'"", ""Comment 19: \'Have you checked printers?\'"", ""Comment 20: \'To day user can log in the system.There has nothing been changed.Conclusion : When it is an printer issue problem would be always be present. Other users in Citrix do not have any problem.There has also been problems with the response. Service BusinessPlatform had to be stopped and restarted after which the response was good again. This problem is more common.!image-1!\'"", ""Comment 21: \'!image-2023-03-07-12-23-36-693.png!!image-2023-03-07-12-25-05-141.png!\'"", \'Comment 22: ""When you restart Business Platform\', ""Comment 23: you restartErpintegrator and user\'s session is uploaded. That\'s all{color:#0747a6}_Conclusion : When it is an printer issue problem would be always be present. Other users in Citrix do not have any problem._{color}{color:#172b4d}Conclusion 2: This is not XL issue as other users also login via Citrix and do not have the same issue.{color}{color:#172b4d}Things to check:{color}{color:#172b4d}>> if user is in correct group"", \'Comment 24: in cmd or power shell please run on user\\\'s computer:whoami /groups{color}{color:#172b4d}>> please check if this SID agrees with the SID you will find by command:{color}{color:#172b4d}*wmic useraccount get name,sid* - when you want to verify all users in domain{color}{color:#172b4d}*whoami / user* - run on user\\\'s computer to check SID  !image-2023-03-07-12-30-22-075.png!  >> You may also verified if user has relevant hasp key in here:  !image-2023-03-07-12-31-18-271.png!{color}{color:#172b4d}Regards{color}""\', ""Comment 25: \'!image-5!\'"", \'Comment 26: ""When you restart Business Platform\', \'Comment 27: you restart Erpintegrator and user\\\'s session is uploaded. That\\\'s all This is needed when we have an very low responce. It cost a lot of time to book just one order. afther restart resounce is oke. This is an comman problem.""\', \'Comment 28: ""Regarding user NWIJ\', \'Comment 29: please check Bartłomiej\\\'s comment in task related underDGS-8620""\', ""Comment 30: \'!image-6!\'"", ""Comment 31: \'Did You try this solution?!image-2023-03-28-12-17-06-069.png!\'"", ""Comment 32: \'Conclusion: Every time we add an new user we do have to synchronise account of ERP operators\'"", ""Comment 33: \'Yes"", ""Comment 34: ERPXL has only information on user that has been synchronized. It do not have /do not use direct access to Active Directory data.\'"", ""Comment 35: \'Please"", ""Comment 36: let me know if expect any additional actions from us regarding this issue? Can we close this ticket?\'"", ""Comment 37: \'Ticket can be closed\']""]\nRelated Issues:\n[\'DGS-8620\']\n\n### End'}"
386,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8646\n\n### Instruction:\nwe have problem with item SUN0895-T-S30, WO(OB)-22/2/23, 89-OB35N, is with reservation but we cancelled the dispatch and quantity didn\'t back.\r\n\r\nCould you check why the stock didn\'t back?\r\n\r\nWe need to load\r\n\r\n\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Hi [~psilva@deheus.com],As [~marcin.kleszcz@kotrak.com]mentioned in the incident DGS-8640,we verified this option to cancel element and in our examples it worked. Could you please describe step by step how did you make this cancellation please?Regards\'"", ""Comment 3: \'Hi,Any feedback?Regards\'"", ""Comment 4: \'Hi Aleksandra[~psilva@deheus.com] will please provide a feedback for it asap.Thank you very much\'"", ""Comment 5: \'I think it could be the same example as DGS-8715\'"", ""Comment 6: \'Hi [~mberbert@deheus.com]"", \'Comment 7: [~psilva@deheus.com],This is the same issue as under RCA DGS-8715 and solved inGDC-849.Please\', ""Comment 8: confirm if we can close this task.Regards\'"", ""Comment 9: \'Hi [~Aleksandra.Przybylek@kotrak.com]You can close this task.Thank you very much\'"", ""Comment 10: \'Thank you.Regards\']""]\nRelated Issues:\n[\'DGS-8640\', \'DGS-8715\']\n\n### End'}"
387,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8645\n\n### Instruction:\nMany no license error messages in VT  \r\n\n\n### Response:\n[""Comment 1: [\'!image!!image-1!!image-2!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \' !screenshot-1! !image-2023-03-01-09-14-44-098!vt-1010/2vt-1014/2vt-402/1!image-2023-03-01-09-22-46-232!\'"", \'Comment 4: ""Hi\', \'Comment 5: there was a communication problem with the XL api - currently the documents are generated.In addition I corrected the data in XL for related orders in VT\\\'s:vt-1010/2,vt-1014/2,vt-402/1.""\', ""Comment 6: \'Problen seems to be soveld.!image-3!\'"", ""Comment 7: \'Ticket may be closed\'"", ""Comment 8: \'Thank you for confirmation.\']""]\nRelated Issues:\n[]\n\n### End'}"
388,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8644\n\n### Instruction:\nHi\r\n\r\nBoth weighbridges from Rio Claro (089) and Unit2 (090) had stop the continuous communication with DHP 3.0 since Thursday.\r\nSometimes is displays the value, sometimes not.\r\nWe checked with weighbridge supplier and there are no technical issue with weighbridges.\r\n\r\nCould you check it please?\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: \'Hello,It should be fine now"", ""Comment 3: The problem has been resolved?Regards\'"", \'Comment 4: ""Hi AdrianI\\\'ve just got the confirmation from weighbridge operators and now the weighbridge communication is stable.You can close this taskThank you very much!""\', ""Comment 5: \'(y)\'"", ""Comment 6: \'[~adrian.kozak@kotrak.com] tu już możesz zmienić status"", ""Comment 7: chyba nie jest potrzeby przesuwać do [~kacper.matuszek@kotrak.com] ?\']""]\nRelated Issues:\n[]\n\n### End'}"
389,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8643\n\n### Instruction:\nSince yesterday 27/02/2023 The production have done some production order and we cannot see them in PCS to start the production. Please can you help\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Hi,I have restarted application pools. Now I can see integration started working.Please"", ""Comment 3: check on your side and confirm.Regards\'"", \'Comment 4: ""Hi ALeksandra\', \'Comment 5: it\\\'s fine we can see the production order now. ThanksRegards""\', ""Comment 6: \'Thank you\'"", ""Comment 7: \'{code:java}2023-02-27 09:44:34 (/Plant.PCS.BusinessLogic/CIAPP04/2480/1) [Error] Plant.PCS.BusinessLogic.Infrastructure.Startup - An error occurred while seeding the database.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 8: error: 40 - Could not open a connection to SQL Server) ---> System.ComponentModel.Win32Exception (53): The network path was not found.   at Microsoft.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception\', \'Comment 9: Boolean breakConnection\', \'Comment 10: Action`1 wrapCloseInAction)   at Microsoft.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj\', \'Comment 11: Boolean callerHasConnectionLock\', \'Comment 12: Boolean asyncClose)   at Microsoft.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo\', \'Comment 13: SqlInternalConnectionTds connHandler\', \'Comment 14: Boolean ignoreSniOpenTimeout\', \'Comment 15: Int64 timerExpire\', \'Comment 16: Boolean encrypt\', \'Comment 17: Boolean trustServerCert\', \'Comment 18: Boolean integratedSecurity\', \'Comment 19: Boolean withFailover\', \'Comment 20: SqlAuthenticationMethod authType)   at Microsoft.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo\', \'Comment 21: String newPassword\', \'Comment 22: SecureString newSecurePassword\', \'Comment 23: Boolean ignoreSniOpenTimeout\', \'Comment 24: TimeoutTimer timeout\', \'Comment 25: Boolean withFailover)   at Microsoft.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(ServerInfo serverInfo\', \'Comment 26: String newPassword\', \'Comment 27: SecureString newSecurePassword\', \'Comment 28: Boolean redirectedUserInstance\', \'Comment 29: SqlConnectionString connectionOptions\', \'Comment 30: SqlCredential credential\', \'Comment 31: TimeoutTimer timeout)   at Microsoft.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(TimeoutTimer timeout\', \'Comment 32: SqlConnectionString connectionOptions\', \'Comment 33: SqlCredential credential\', \'Comment 34: String newPassword\', \'Comment 35: SecureString newSecurePassword\', \'Comment 36: Boolean redirectedUserInstance)   at Microsoft.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity\', \'Comment 37: SqlConnectionString connectionOptions\', \'Comment 38: SqlCredential credential\', \'Comment 39: Object providerInfo\', \'Comment 40: String newPassword\', \'Comment 41: SecureString newSecurePassword\', \'Comment 42: Boolean redirectedUserInstance\', \'Comment 43: SqlConnectionString userConnectionOptions\', \'Comment 44: SessionData reconnectSessionData\', \'Comment 45: Boolean applyTransientFaultHandling\', \'Comment 46: String accessToken\', \'Comment 47: DbConnectionPool pool)   at Microsoft.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options\', \'Comment 48: DbConnectionPoolKey poolKey\', \'Comment 49: Object poolGroupProviderInfo\', \'Comment 50: DbConnectionPool pool\', \'Comment 51: DbConnection owningConnection\', \'Comment 52: DbConnectionOptions userOptions)   at Microsoft.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnectionPool pool\', \'Comment 53: DbConnection owningObject\', \'Comment 54: DbConnectionOptions options\', \'Comment 55: DbConnectionPoolKey poolKey\', \'Comment 56: DbConnectionOptions userOptions)   at Microsoft.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject\', \'Comment 57: DbConnectionOptions userOptions\', \'Comment 58: DbConnectionInternal oldConnection)   at Microsoft.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject\', \'Comment 59: DbConnectionOptions userOptions\', \'Comment 60: DbConnectionInternal oldConnection)   at Microsoft.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject\', \'Comment 61: UInt32 waitForMultipleObjectsTimeout\', \'Comment 62: Boolean allowCreate\', \'Comment 63: Boolean onlyOneCheckConnection\', \'Comment 64: DbConnectionOptions userOptions\', \'Comment 65: DbConnectionInternal& connection)   at Microsoft.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject\', \'Comment 66: TaskCompletionSource`1 retry\', \'Comment 67: DbConnectionOptions userOptions\', \'Comment 68: DbConnectionInternal& connection)   at Microsoft.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection\', \'Comment 69: TaskCompletionSource`1 retry\', \'Comment 70: DbConnectionOptions userOptions\', \'Comment 71: DbConnectionInternal oldConnection\', \'Comment 72: DbConnectionInternal& connection)   at Microsoft.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection\', \'Comment 73: DbConnectionFactory connectionFactory\', \'Comment 74: TaskCompletionSource`1 retry\', \'Comment 75: DbConnectionOptions userOptions)   at Microsoft.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry\', \'Comment 76: SqlConnectionOverrides overrides)   at Microsoft.Data.SqlClient.SqlConnection.Open(SqlConnectionOverrides overrides)   at Microsoft.EntityFrameworkCore.Storage.RelationalConnection.OpenInternal(Boolean errorsExpected)   at Microsoft.EntityFrameworkCore.Storage.RelationalConnection.Open(Boolean errorsExpected)   at Microsoft.EntityFrameworkCore.SqlServer.Storage.Internal.SqlServerDatabaseCreator.<>c__DisplayClass18_0.<Exists>b__0(DateTime giveUp)   at Microsoft.EntityFrameworkCore.ExecutionStrategyExtensions.<>c__DisplayClass12_0`2.<Execute>b__0(DbContext c\', \'Comment 77: TState s)   at Microsoft.EntityFrameworkCore.SqlServer.Storage.Internal.SqlServerExecutionStrategy.Execute[TState,TResult](TState state\', \'Comment 78: Func`3 operation\', \'Comment 79: Func`3 verifySucceeded)   at Microsoft.EntityFrameworkCore.ExecutionStrategyExtensions.Execute[TState,TResult](IExecutionStrategy strategy\', \'Comment 80: TState state\', \'Comment 81: Func`2 operation\', ""Comment 82: Func`2 verifySucceeded)   at Microsoft.EntityFrameworkCore.SqlServer.Storage.Internal.SqlServerDatabaseCreator.Exists(Boolean retryOnNotExists)   at Microsoft.EntityFrameworkCore.SqlServer.Storage.Internal.SqlServerDatabaseCreator.Exists()   at Microsoft.EntityFrameworkCore.Migrations.HistoryRepository.Exists()   at Microsoft.EntityFrameworkCore.Migrations.Internal.Migrator.Migrate(String targetMigration)   at Microsoft.EntityFrameworkCore.RelationalDatabaseFacadeExtensions.Migrate(DatabaseFacade databaseFacade)   at Plant.PCS.BusinessLogic.Infrastructure.EF.BaseDbInitializer`1.Init() in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\9ecc36be9059f942\\\\\\\\Plant.PCS.BusinessLogic\\\\\\\\Infrastructure.EF\\\\\\\\BaseDbInitializer.cs:line 11   at Plant.PCS.BusinessLogic.Infrastructure.SeedingExtension.SeedDatabase(IApplicationBuilder builder) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\9ecc36be9059f942\\\\\\\\Plant.PCS.BusinessLogic\\\\\\\\Infrastructure\\\\\\\\SeedingExtension.cs:line 19ClientConnectionId:00000000-0000-0000-0000-000000000000Error Number:53,State:0,Class:20{code}\'"", \'Comment 83: ""{code:java}2023-02-27 09:44:41 (/Plant.PCS.BusinessLogic/CIAPP04/2480/10) [Error] Kotrak.Integration.InternalStorage.IInternalStorageRepository - Error during System.Collections.Generic.IReadOnlyCollection`1[Kotrak.Integration.InternalStorage.EF.Entities.OutboundEntity] Get(Int32) methodSystem.ObjectDisposedException: Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \\\'Dispose\\\' on the context instance\', \'Comment 84: or wrapping it in a using statement. If you are using dependency injection\', ""Comment 85: you should let the dependency injection container take care of disposing context instances.Object name: \'IntercontextCommunicationDbContext\'.   at Microsoft.EntityFrameworkCore.DbContext.CheckDisposed()   at Microsoft.EntityFrameworkCore.DbContext.get_ContextServices()   at Microsoft.EntityFrameworkCore.DbContext.get_ChangeTracker()   at Microsoft.EntityFrameworkCore.Query.CompiledQueryCacheKeyGenerator.GenerateCacheKeyCore(Expression query"", \'Comment 86: Boolean async)   at Microsoft.EntityFrameworkCore.Query.RelationalCompiledQueryCacheKeyGenerator.GenerateCacheKeyCore(Expression query\', \'Comment 87: Boolean async)   at Microsoft.EntityFrameworkCore.SqlServer.Query.Internal.SqlServerCompiledQueryCacheKeyGenerator.GenerateCacheKey(Expression query\', \'Comment 88: Boolean async)   at Microsoft.EntityFrameworkCore.Query.Internal.QueryCompiler.Execute[TResult](Expression query)   at Microsoft.EntityFrameworkCore.Query.Internal.EntityQueryable`1.GetEnumerator()   at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection)   at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source)   at Castle.Proxies.Invocations.IInternalStorageRepository`1_Get_2.InvokeMethodOnTarget()   at Castle.DynamicProxy.AbstractInvocation.Proceed()   at Kotrak.Common.Infrastructure.Interceptors.LoggingInterceptor`1.Intercept(IInvocation invocation){code}""\', ""Comment 89: \'[PCS - sprawdzenie co przeszło PLR"", \'Comment 90: sprawdzenie\', ""Comment 91: co powoduje error|onenote:https://kotrak.sharepoint.com/sites/erpasysta/Shared%20Documents/Baza%20wiedzy/Baza%20Wiedzy%20-%20ERPSD/Klienci/DEHEUS/DEHEUS%20APPLICATIONS/Egipt/Baza%20wiedzy.one#PCS%20-%20sprawdzenie%20co%20przesz%C5%82o%20PLR,%20sprawdzenie,%20co%20powoduje%20error&section-id=\\\\\\\\{145A51F6-5D2A-42D7-9D47-CB2FD0A15DC7}&page-id=\\\\\\\\{CB544F8A-92FA-47BF-BBB7-5ECB11257E4E}&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%2FEgipt%2FBaza%20wiedzy.one%7C145A51F6-5D2A-42D7-9D47-CB2FD0A15DC7%2FPCS%20-%20sprawdzenie%20co%20przesz%C5%82o%20PLR%2C%20sprawdzenie%2C%20co%20powoduje%20error%7CCB544F8A-92FA-47BF-BBB7-5ECB11257E4E%2F%29])\']""]\nRelated Issues:\n[]\n\n### End'}"
390,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8642\n\n### Instruction:\nGood morning,\r\n\r\nCan you please approve me to see all the incidents and requests created by anyone in Serbia? I have already asked for this (DGS-8533) and for the time being I had rights but now again I dont. For example I can not see DGS-8633 which is created by Nemanja Antonic and it is crucial but I can not see it. Check the screenshot. I should have all the rights just like Nemanja Antonic. Thank you.\n\n### Response:\n[""Comment 1: [\'!image-1!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Dear Miroslav"", \'Comment 4: In reference to your request I added You to all open Incidents. Additionally\', \'Comment 5: I added You to the request participants sections\', ""Comment 6: all new tickets from Serbia will be visible to You.\'"", ""Comment 7: \'It is OK now"", ""Comment 8: thank you !\']""]\nRelated Issues:\n[]\n\n### End'}"
391,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8641\n\n### Instruction:\n# On new Financial Statement printouts should be section Guarantees when there will be some invoices with Round Category = \'Guarantees\'.\r\nThis section should be displayed only when will be some invoices with this Round Category for the round, when there is no data in this section it shoudln\'t appear on printout.\r\n\r\n\r\n # Guarantees should be also included in Feed profit\xa0(it is an extra revenue) - to change technical results calculating procedure\r\n\r\n!image-2023-02-28-08-58-04-195.png!\r\n\r\n\xa0\n\n### Response:\n[""Comment 1: [\'[~mbovene@deheus.com]can you specify how should looks section of guarantees on printout.What columns should be on printout for this section"", ""Comment 2: on old printout it looks like that!image-2023-02-28-09-11-58-171.png!How should be calculated guarantees for feed profit. It should be always added to the Feed profit values?Should we take always absolute values (when it be positive or negative values of guarantees)?\'"", \'Comment 3: \\\'I can be almost the same columns as for the category ""Opzetgegevens"" above it:Datum (date)\', \'Comment 4: referentie (reference)\', \'Comment 5: aantal (quantity)\', \'Comment 6: gewicht (weight)\', ""Comment 7: prijs excl. VAT (price) and bedrag excl. BTW (net value)Guarantees can be positive or negative. When it is negative in the Financial Statement than it is a revenu (just like SLAC). In this case you can print it as positive on the PFD and add this amount to the feed profit.When it is positive in the Financial Statement you must print it as negative on the PDF and extract this from the feed profit (voerwinst). \'"", ""Comment 8: \'[~grzegorz.materla@kotrak.com]do zweryfikowania czy przeniesione i gotowe do testu/na prod.\'"", ""Comment 9: \'I made a positive guarantee invoice (3763,00 EUR)"", \'Comment 10: but it shows on the printout as negative (like the old printouts). 1. I know if this was the plan\', \'Comment 11: because on the new FS also the meat price amounts are positive? 2. For the calculations\', \'Comment 12: does it add up\', \'Comment 13: for the calculations down below? Because I would expect ""marge/m²"" (revenue/m²) to be 8.50 in stead of 7.79 when I add the guarantee amount to the rest. !image!\\\'\', \'Comment 14: ""The guarantees amount isn\\\'t included in the feed profit (marge). Therefor\', \'Comment 15: the revenue/m² (marge/m²) is wrong.""\', ""Comment 16: \'Please see mu note from March 1:Guarantees can be positive or negative. When it is negative in the Financial Statement than it is a revenu (just like SLAC). In this case you can print it as positive on the PFD and add this amount to the feed profit.When it is positive in the Financial Statement you must print it as negative on the PDF and extract this from the feed profit (voerwinst).\'"", ""Comment 17: \'Yes"", ""Comment 18: your explanation is correct Mitch. Could this be modified asap?\'"", ""Comment 19: \'Dla nowych wydruków FS pokazujemy faktyczną jej wartość z faktury (inaczej niż na dokumencie FS"", ""Comment 20: gdzie pokzywana jest wartość mnożona przez -1). Stare wydruki FS zostają niezmienione (tam pokazywana jest wartość taka jak na dokumencie FS).Do kalkulacji Feed profit powinna być wliczana oryginalna wartość z faktur i powinno to wyglądać tak: (ABS(@AmountFL)+ABS(@AmountAL)) - ABS(@AmountOfFeed) -ABS(@AmountDOCNet) +*Suma faktur gwarancyjnych*\'"", \'Comment 21: ""[~SDriesen@deheus.com],we\\\'ve made changes for Guarantees and Feed Profit calculation in test Intense environment. You can verify it.Best regards,Grzegorz""\', ""Comment 22: \'Hello Grzegorz,Something still seems off to me in the caclulations.When I do the manual calculation for this example I do:Feed profit = Slaughtery + Guarantee - Feed - Broilers--> 238.375,80 + 9.882,39 - 172.091,44 - 31.141,80 = 45.024,95 EURThe printout however shows 45.617,89 EURThis is a difference of 592,94 EURCould you see where this difference comes from?I took another example and there the difference was even bigger.!Example technical result calculation error.JPG|thumbnail!\'"", ""Comment 23: \'Hello [~SDriesen@deheus.com],we took the wrong value for guarantees - gross value. We adjusted it for net value. You can feel free to test the calulcation one more time.Best regards,Grzegorz\'"", ""Comment 24: \'Hello Grzegorz,I tested it and now it seems to be right indeed.You may move this to PROD"", ""Comment 25: thank you!\'"", ""Comment 26: \'[~SDriesen@deheus.com],we moved calulcation for Feed Profit into prod Intense environment. You can verify it.Best regards,Grzegorz\'"", \'Comment 27: \\\'Grzegorz,This is good now in PROD environment. I think you can close this.The last modifications on FS new and S2P will be handled in the other JIRA task I suppose?https://helpdesk.kotrak.com/servicedesk/customer/portal/56/DGS-8067""2. On FS new\', \'Comment 28: the entry stock and final stock are still in Dutch on French printouts""""One more question\', \'Comment 29: for feed lines we have ""voer\\\\\\\' as description on the S2P and for one sided SI\\\\\\\'s where the customer is both the supplier and the reference\', \'Comment 30: we have ""Salmonellafonds"" as description on the S2P. Could these fields be translated as well\', \'Comment 31: looking to the customer card for the correct translation?""\\\'\', ""Comment 32: \'I close this task.Yes"", ""Comment 33: translations will be handled in this task.https://helpdesk.kotrak.com/servicedesk/customer/portal/56/DGS-8067\']""]\nRelated Issues:\n[\'DGS-8215\', \'DGS-8732\', \'DGS-8877\']\n\n### End'}"
392,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8640\n\n### Instruction:\nwe have problem with item SUN0895-T-S30, WO(OB)-22/2/23, 89-OB35N, is with reservation but we cancelled the dispatch and quantity didn\'t back.\r\n\r\nCould you check why the stock didn\'t back?\r\n\r\nWe need to load\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello"", ""Comment 3: We kindly inform you that wecurrentlyare processing another Priority1 task.We will revert to processing your task as soon as possible.Regards\'"", ""Comment 4: \'Hello,Stock came back.In this task we have focused on clearingandunblocking the process.If there is a need from your sideto investigate the reasonof the issue"", \'Comment 5: we may raise RootCause Analysis (RCA)task for you.Please\', ""Comment 6: let us knowhow you wish us to proceed.Regards\'"", ""Comment 7: \'Hello Aleksandra,yes"", ""Comment 8: we need RCA. You can close this task. Thank you.\'"", ""Comment 9: \'The RCA task is underDGS-8646.Please"", ""Comment 10: let us know if you have access.Regards\'"", ""Comment 11: \'Dear [~psilva@deheus.com]we verified this option to cancel element and in our examples it worked. Could you please describe step by step how did you make this cancellation please?\'"", \'Comment 12: ""Marcin,we didn\\\'t cancel the element\', \'Comment 13: we cancelled the WD using option clear element.!image-1!""]\']\nRelated Issues:\n[\'DGS-8646\', \'DGS-8715\']\n\n### End'}"
393,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8639\n\n### Instruction:\nthe prouction 0871240223014 is closed on DHP but is not available in DHC. Could you check why? We need to invoice but it\'s not possible without integration.\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: \'id=1add05fd-f979-4c0c-80ad-427939754cc5!image-2023-02-27-20-44-11-521.png!\'"", \'Comment 4: ""{code:java}2023-02-24 12:49:41 (2e8b0cd0-a4dd-4846-951b-1bd01b4935a5/Plant.DHC.Integration/BR-4-SV-VM0204/18912/8) [Error] Plant.Integration.DhcService.Application.DhpToDhcMapFilter - Couldn\\\'t map dhp message Plant.QAM.BusinessLogic.DomainAbstractions.Quarantine.ProductionLotReportQuarantineSynchronizationEventKotrak.Integration.IdentityMapping.IdentityNotMappedException: Key of entity ProductionLotReportIdentityEntity was not mapped. Key value Id: 1add05fd-f979-4c0c-80ad-427939754cc5   at Kotrak.Integration.IdentityMapping.EF.GenericIdentityMappingRepository`1.GetExternalKey(GuidKey key)   at Plant.Integration.DhcService.Application.ProductionLotReports.ProductionLotReportQuarantineMapFilter.MapIds(ProductionLotReportQuarantineSynchronizationEvent message\', \'Comment 5: ProductionLotReportQuarantine externalObject) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\e810c04f78ab209c\\\\\\\\Plant.Integration.DhcService\\\\\\\\Plant.Integration.DhcService.Application\\\\\\\\ProductionLotReports\\\\\\\\ProductionLotReportQuarantineMapFilter.cs:line 28   at Plant.Integration.DhcService.Application.DhpToDhcMapFilter`2.Process(PackageIntegrationState input) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\e810c04f78ab209c\\\\\\\\Plant.Integration.DhcService\\\\\\\\Plant.Integration.DhcService.Application\\\\\\\\DhpToDhcMapFilter.cs:line 44{code}""\', ""Comment 6: \'!image-2023-02-27-21-10-10-961.png!!image-2023-02-27-21-13-01-804.png!\'"", ""Comment 7: \'Hi,The issue was caused that PLR used Recipe ver 14 which was not in DHC. I have resynced recipe from DHH"", \'Comment 8: it appeared in DHC. Now we need to resend PLR but it needs to be moved back to status finished and then again confirmed. But when we confirm it fromapplication\', \'Comment 9: we receive error:Current settlement configuration requires that deliveries are explicitly specified appears"". So we need to change configuration for a moment. Do you agree for that?Regards\\\'\', ""Comment 10: \'Co jest niepokojące"", \'Comment 11: w tabeli eventów dla Prod jest ponad 6800 eventów\', ""Comment 12: z czego 6652 wywołane przez PCSa!image-2023-02-28-07-45-46-813.png!!image-2023-02-28-07-46-14-311.png!\'"", \'Comment 13: \\\'Po wysłaniu messega z dhp{code:java}2023-02-27 17:17:36 (2e8b0cd0-a4dd-4846-951b-1bd01b4935a5/Plant.DHC.Integration/BR-4-SV-VM0204/15496/8) [Error] Kotrak.Integration.IntegrationPluginCommon.IntercontextCommunication.Inbound.InboundIntercontextErrorHandler - Error during handling message of type ""Plant.QAM.BusinessLogic.DomainAbstractions.Quarantine.ProductionLotReportQuarantineSynchronizationEvent""\', \'Comment 14: retry no 2Kotrak.Integration.IdentityMapping.IdentityNotMappedException: Key of entity ProductionLotReportIdentityEntity was not mapped. Key value Id: 1add05fd-f979-4c0c-80ad-427939754cc5   at Kotrak.Integration.IdentityMapping.EF.GenericIdentityMappingRepository`1.GetExternalKey(GuidKey key)   at Plant.Integration.DhcService.Application.IdentityMappingExtensions.GetMappedExternalLongKey[TEntity](IIdentityMappingRepository`1 identityMapper\', \'Comment 15: AggregateId id) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\e810c04f78ab209c\\\\\\\\Plant.Integration.DhcService\\\\\\\\Plant.Integration.DhcService.Application\\\\\\\\IdentityMappingExtensions.cs:line 20   at Plant.Integration.DhcService.Application.ProductionLotReports.ProductionLotReportQuarantineMapFilter.MapIds(ProductionLotReportQuarantineSynchronizationEvent message\', \'Comment 16: ProductionLotReportQuarantine externalObject) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\e810c04f78ab209c\\\\\\\\Plant.Integration.DhcService\\\\\\\\Plant.Integration.DhcService.Application\\\\\\\\ProductionLotReports\\\\\\\\ProductionLotReportQuarantineMapFilter.cs:line 26   at Plant.Integration.DhcService.Application.DhpToDhcMapFilter`2.Process(PackageIntegrationState input) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\e810c04f78ab209c\\\\\\\\Plant.Integration.DhcService\\\\\\\\Plant.Integration.DhcService.Application\\\\\\\\DhpToDhcMapFilter.cs:line 44   at Kotrak.Integration.Pipeline.PredefinedFilters.FilterBase`1.Execute(T input)   at Kotrak.Integration.Pipeline.Pipeline`1.Excecute(T input)   at Plant.Integration.DhcService.Application.BasePushPipelineExecutor`4.RunPipeline(IDhcService dhcService\', ""Comment 17: TMessage message) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\e810c04f78ab209c\\\\\\\\Plant.Integration.DhcService\\\\\\\\Plant.Integration.DhcService.Application\\\\\\\\BasePushPipelineExecutor.cs:line 29   at Plant.Integration.DhcService.Infrastructure.Handlers.BaseInboundMessageHandler`1.Handle(TEvent message) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\e810c04f78ab209c\\\\\\\\Plant.Integration.DhcService\\\\\\\\Plant.Integration.DhcService.Infrastructure\\\\\\\\Handlers\\\\\\\\BaseInboundMessageHandler.cs:line 37   at Kotrak.Integration.IntegrationPluginCommon.IntercontextCommunication.Inbound.IntercontextInboundHandler`2.Handle(InternalStorageDto message){code}\'"", ""Comment 18: \'!image-2023-02-28-08-50-49-661.png!\'"", ""Comment 19: \'Hi [~psilva@deheus.com],We have discussed this issue with Dev and the quickest option would be to do this PLR report in ERP system manually. Please"", ""Comment 20: let us know if this would be fine for you.Regards\'"", ""Comment 21: \'Hi Aleksandra,we need the integration. Why is not possible integrate?\'"", ""Comment 22: \'Hi,It is another incident"", ""Comment 23: the sam as in task DGS-8387. For further solution we need to pass this task to Dev Team. We will let you know about the solution as soon as possible.Regards\'"", \'Comment 24: ""Hi AleksandraAbout changing configuration from Delivery to Mixed or FIFO\', ""Comment 25: we do not accept this because this plant has special traceability from MAPA and I\'m afraid of this causing errors in consumption of wrong RM SerialNumber.About manual ajdustment on ERP"", \'Comment 26: will take some time\', \'Comment 27: but it\\\'s possible.However we need this PLR integrated to DHC because we have some BI Dashboards that gets data from DHC database.This PLR is important on the process.Thank you very much""\', \'Comment 28: ""Hi Maicon,We won\\\'t change configuration as it would cause another use of material. As I mentioned above\', \'Comment 29: I will pass this task to dev team. The issue is rather caused by short response time so we will decrease it. No need for RCA right now.Regards""\', ""Comment 30: \'[^production_lot_confirmed_event.txt]\'"", ""Comment 31: \'Lot Report in DHC now!image-2023-02-28-14-44-04-098.png!Regards\'"", ""Comment 32: \'Hello Aleksandra,the lot number is available in DHC. You can close this task. Thank you.\']""]\nRelated Issues:\n[]\n\n### End'}"
394,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8638\n\n### Instruction:\nApplication does not respond anymore.\r\n\r\nAll the time : Please wait\r\n\r\nCan not get out of application\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \' !screenshot-1! \'"", ""Comment 3: \'Please check there was a problem with the processes of the Erpintegrator service - after restarting service the applications should now run properly.\'"", ""Comment 4: \'Responce is beter. How to restart Erpintegrator service?What is the procedure to do this\'"", \'Comment 5: ""Hi,this task did not give an error in description or more details to analysis so you can see that yesterday there was a high process load on the service. !screenshot-2! As for restarting start BP !screenshot-4! and go to applications  !screenshot-3! select the stop and start option - checking if it started.keep in mind that this won\\\'t always help\', \'Comment 6: so in case of problems it\\\'s best to create a task.Regards.""\', ""Comment 7: \'Ticket can be closed\']""]\nRelated Issues:\n[]\n\n### End'}"
395,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8637\n\n### Instruction:\nNiels Wijnen has trouble in accounting screen in CDN.\r\n\r\nHe wants to get into Accounting using the button accounting. Then he gets the gray screen according screen shot. Last Thursday when he was in the office Veghel it went well. \r\nHe also can\'t close the gray screen which keeps him logged in and has to ask someone else to kick kim out.\r\n\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!!image-1!\'"", ""Comment 2: \'!image-2!\'"", ""Comment 3: \'Suddenly "", \'Comment 4: afther 5 hours\', ""Comment 5: it works again.Ticket can be closed.\'"", ""Comment 6: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 7: \'User has still problem with loging in DH-CDN!image-3!\'"", ""Comment 8: \'!image-4!\'"", ""Comment 9: \'I will open a new ticket for DH-CDN inlog problem.\']""]\nRelated Issues:\n[\'DGS-8620\']\n\n### End'}"
396,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8636\n\n### Instruction:\nCan we make the fields Hakdermatitus and the table for Footsole scores changeable even after the SR is archived? \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: ""Unfortunately it\\\'s hard to make possible some fields editable when document is archived. # In this case it\\\'s needed to allow users to modify documents in Archive (any field or table on documents) and give them rights to editing any document - it means that users will be able to edit all documents in Archive (now few users have this right). It could be dangerous if all users will have this rights. To avoid changing other documents by users there will be needed configure all fields on all documents and add edit condition for each of them and then we can set which field/tab will be editable (it could be editable for users in some role) even if document will be in Archive\', \'Comment 4: but it\\\'s a time-consuming solution. # Second option that we discussed internally is to create some action to update only these specific fields/tables for this type of document (in this case SR). We can make some mockup of this to visualize how could it works. It could be something like action from lightning button where we retrive actual data on popup window and user can modify some data and update these values.We can make some mockup of 2nd solution if you prefer this option.Regards""\', \'Comment 5: ""Indeed lets look at your proposal for the second option. The first option I don\\\'t want to have.""\', ""Comment 6: \'It could looks like that in this video [^SR_field_modifying.wmv]"", ""Comment 7: is it good and can we implement it on test environment?\'"", ""Comment 8: \'Can be moved to PROD and topic closed.\'"", ""Comment 9: \'Do dokończenie na test i później do przeniesienia na prod.\'"", \'Comment 10: \\\'[~mbovene@deheus.com],we\\\\\\\'ve adjusted and added MS SQL code for update in test environment. You can feel free to test it on Slaughtery Report in the ""Archive"" status.Best regards,Grzegorz\\\'\', ""Comment 11: \'Hi Grzegorz"", \'Comment 12:  It looks like I can edit all fields on the SR when it has the status Archive. That is not what we want.  Regards\', \'Comment 13:  Mitch     *Van:* Grzegorz Materla (Jira) <jira@kotrak.com>   *Verzonden:* maandag 17 april 2023 13:26  *Aan:* Bovene\', ""Comment 14: Mitch van <mbovene@deheus.com>  *Onderwerp:* DGS-8636 SR fields available after archive   \'"", ""Comment 15: \'Can we make the fields Hakdermatitus and the table for Footsole scores changeable even after the SR is archived?\'"", \'Comment 16: \\\'Hi Mitch,you can edit documents in ""Archive"" status\', \'Comment 17: because you have all rights on TEST environment.Others users can\\\\\\\'t do it. We made test on Anja Verdam and the SR in ""Archive"" was not editable.Best regards,Grzegorz\\\'\', ""Comment 18: \'Ah"", ""Comment 19: so that is the reason.It can be moved to PROD whenever that is the case.\']""]\nRelated Issues:\n[\'DGS-8748\']\n\n### End'}"
397,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8635\n\n### Instruction:\nwe create some XML from analysis order for BLGG but the file was not sent to ftp://blgg@ftp.deheus.com/DHImpData.\r\nI checked folder in internal server and file was create but not sent.\r\n\r\nCould you check if we have some error?\r\n\r\nThank you\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Hello,You need to configure / share XML folder with FTP server and this is to do on your side. We are not authorised"", \'Comment 4: what is more\', \'Comment 5: the password needs to be set up. If you do not know how to do that\', ""Comment 6: please contact IT in Netherlands. They are experienced.All new xml files will then drop to ftp. The below files need to be moved manually.Regards!image-2023-02-27-14-11-09-471.png!\'"", ""Comment 7: \'Hi Aleksandra,we are checking internally. You can close this task. Thank you.\'"", ""Comment 8: \'Thank you\']""]\nRelated Issues:\n[]\n\n### End'}"
398,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8634\n\n### Instruction:\nan automatic RM assignment is created. however, there are 2 times the same pallet in one order. When the employee scans the pallet, he receives an error message and cannot continue.\r\n\r\nWhen it reboots and starts again the same thing happens again.\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!!image-1!\'"", ""Comment 2: \'This is happening more often.!image-2!!image-3!\'"", ""Comment 3: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 4: \'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 5: \' !Log WMO 3282! !WMO RM 1895!\'"", ""Comment 6: \' !WMO RM 659-03-23! !image-2023-03-06-18-36-17-799!!image-2023-03-06-18-40-53-708!\'"", ""Comment 7: \'What is the status at this moment?\'"", ""Comment 8: \'Hi,This task is under dev investigation. We will let you know about the result as soon as possible.Regards\'"", ""Comment 9: \'Comment of user : It strikes me that this always concerns the pallets that are just NOT 500 kg\'"", ""Comment 10: \'!image-4!\']""]\nRelated Issues:\n[\'DGS-8560\']\n\n### End'}"
399,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8633\n\n### Instruction:\nWe need to add this item to stock also. \n\n### Response:\n[""Comment 1: [\'!vukota dodavanje 21.02.2023 (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!  !screenshot-2! 30410200-B20\'"", ""Comment 4: \'Hello"", \'Comment 5: the problem was a corrupted document in XL - !screenshot-3! After the repair\', ""Comment 6: the VT-126/02 element has been linked with correct element order. Elements from VT-126/02 have been generated.Currently you need to confirm this WMR+  !screenshot-4! then you will have a stock and you will be able to generate a document for VT-145.\'"", \'Comment 7: ""{code:java}/****** Script for SelectTopNRows command from SSMS  ******/SELECT top 100 *  FROM [DHCountry_DH_Sabac_Prod].[dbo].[VehicleTicketElementERPDocuments]  where VehicleTicketElementId in(select id   FROM [DHCountry_DH_Sabac_Prod].[dbo].[VehicleTicketElements]  where vehicleticketid=\\\'AAA30761-BF08-4687-B1A8-308FE608D710\\\'  )(select *  FROM [DHCountry_DH_Sabac_Prod].[dbo].[VehicleTicketElements]  where vehicleticketid=\\\'AAA30761-BF08-4687-B1A8-308FE608D710\\\'  and ItemId=\\\'EA03FDE0-094F-40BE-9993-D1D98E25AA72\\\')  SELECT *  FROM [DHCountry_DH_Sabac_Prod].[dbo].[VehicleTicketElementERPDocuments]  where VehicleTicketElementId in(select id   FROM [DHCountry_DH_Sabac_Prod].[dbo].[VehicleTicketElements]  where vehicleticketid=\\\'39BC4CCB-91F7-4B3F-89D5-0CCABF766DF0\\\'){code}""\', ""Comment 8: \'wmr+ is confirmed. thanks\'"", ""Comment 9: \'You can close this ticket now. Thank you.\'"", ""Comment 10: \'Thank you for confirmation.\']""]\nRelated Issues:\n[]\n\n### End'}"
400,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8632\n\n### Instruction:\nI\'ll write an e-mail\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Mail from Christine!image-2023-03-03-10-44-43-831.png!\'"", ""Comment 3: \'Hi Christine,These 4 lines have been deleted from Feed saleFE-N/0007.!image-2023-03-03-10-57-13-674.png!Please verify that is correct and if we can close the task.Regards\'"", ""Comment 4: \'{color:black}Thank you Damian{color} {color:black}😊{color}{color:black}{color} {color:black}All is well now.{color} {color:black}{color} {color:black}Have a great weekend!{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Christinede{color} |{color:#000001} {color} |{color:#000001} Jong{color} |  {color:#000001}MedewerkerContractadministratie{color} | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.de-heus.nl/]>{color} | |  *{color:#006FB7} *DEHEUSVOEDERSB.V.*{color}* | | | |{color:#000001} Postbus396 6710BJEde \\\\u200b{color} | |{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} | | |{color:#000001} T:0318675567{color} |  {color:#000001}KvK14626985{color}   _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | | !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | | !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} | | !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} |        *Van:* Damian Świstek (Jira) <jira@kotrak.com>   *Verzonden:* vrijdag 3 maart 2023 10:59  *Aan:* Jong"", ""Comment 5: Christine de <CJong@deheus.com>  *Onderwerp:* DGS-8632 Delete wrong feed sale registrations FE-N/0007   !image006!\']""]\nRelated Issues:\n[]\n\n### End'}"
401,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8631\n\n### Instruction:\nFind the below error in DHP Johnson\n\n### Response:\n[""Comment 1: [\'!IMG-20230227-WA0000.jpg|thumbnail!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Dear Solomon,I have restarted application pools. Now for me it seems to be working fine. Please"", ""Comment 4: verify and let me know.Regards\'"", ""Comment 5: \'It is working now but orders are not showing \'"", ""Comment 6: \'Let me check\'"", ""Comment 7: \'Could you please provide me an example of the Order (document number) that does not arrive to DHP?\'"", ""Comment 8: \'IO 788/23\'"", ""Comment 9: \'!image-2023-02-27-09-35-18-233.png!\'"", ""Comment 10: \'The order is in Plant now. The rest of the Orders as well. Could you please"", ""Comment 11: let me know if you restarted serevers or did you experience temporary lack of internet or electricity?\'"", ""Comment 12: \'Please close\'"", ""Comment 13: \'błędy w logach od momentu restartu app serwera tj.2/26/2023"", ""Comment 14: 2:54:24 AM\']""]\nRelated Issues:\n[]\n\n### End'}"
402,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8630\n\n### Instruction:\nwhen scanning at the final location of the replenishment, we get an error message.\r\n\r\nThey got this message several times\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Please be informed that we have forwarded the issue to the development team in order to internal analysis.We are waiting for more details and will be back with further information as soon as possible.\'"", ""Comment 4: \'Dziwny ten dokument jest :( !RM 3143 - 24.02.2023! ----Ostatnia próba generowania WMO RM z automatu jest 2023-01-27!image-2023-02-27-14-23-14-981!Log z 27-01-2023 dla WMO(RM)- 3941/01/23!image-2023-02-27-14-32-13-718!----Do ABM wpis z tym SN powstał 24.02.2023 10:49 (Id = 4771)!image-2023-02-27-14-24-47-116!Historia ABM dla towaru 00978!image-2023-02-27-14-27-22-380!\'"", ""Comment 5: \'[~aleksandra.masternak@kotrak.com] prosiłbym o próbę zreprodukowania błędu na naszym środowisku \'"", ""Comment 6: \'Hi,This issue will be fixed in new version. Please"", ""Comment 7: let us know if we can close this task.Regards\'"", ""Comment 8: \'New version off?When wil this new version been installed?\'"", ""Comment 9: \'[~bkremers@deheus.com] This deployment has been made today at night. I was discussing with Thomas Dankers about the upgrade of DHP Mobile"", ""Comment 10: which operators should do today in the morning. There is a newer build of the same Release you have had. DHP Desktop 2.7.1911.164 (previous version 2.7.1911.157)Newer Web Service for DHP Mobile based on the same release as DHP Desktop DHP Mobile version 2.7.1911.18 (previous 2.7.1911.16)\'"", ""Comment 11: \'May we close this task?Regards\']""]\nRelated Issues:\n[\'DGS-8560\']\n\n### End'}"
403,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8629\n\n### Instruction:\nPORs don\'t come into ERP automatically, i have to move them manually from DHC to ERP, can you please help identify the issue and solve. thank you\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'!image-2023-02-27-08-39-20-301.png!\'"", ""Comment 3: \'Dear Solomon,I have done reindexation of DB and updated statistics. Please"", \'Comment 4: let me know if it helped.If it did not help\', ""Comment 5: please provide me with examples of documents to invesigate further.Regards\'"", ""Comment 6: \'Okay thanks"", ""Comment 7: please close\'"", ""Comment 8: \'Thank you\']""]\nRelated Issues:\n[]\n\n### End'}"
404,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8628\n\n### Instruction:\nWZ-1360/02/G został wygenerowany przez automat w CDN, następnie został ""cofnięty"" do DHC\r\nW tym momencie w CDN WZ jest Anulowany\r\n\r\nVT-3839/2/2023/G zwraca błąd:\r\nBŁĘDY:|Zabrakło ilości (nie udało się pobrać towaru lub wymuszono realizacje całości). (DodajPozycje-17) - (DD0A2R00C-L4B)\r\n\r\nProśba o pomoc z ponownym wygenerowaniem WZ w CDN\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'!image-2023-02-27-11-16-42-754.png!!image-2023-02-27-11-16-59-429.png!!image-2023-02-27-11-17-49-394.png!!image-2023-02-27-11-19-13-795.png!\'"", ""Comment 4: \'Hi,For today I can see only 18 t available (6 is reserved from 24). And you need nearly 20.Please"", ""Comment 5: verify!image-2023-02-27-11-30-41-075.png!\'"", ""Comment 6: \'!image-2023-02-27-11-32-44-081.png!\'"", \'Comment 7: ""But I don\\\'t see this 6t reservation in history !image!""\', ""Comment 8: \'How was document SOR / WZ cancelled? In application or under db?\'"", ""Comment 9: \'from what i know - application\'"", ""Comment 10: \'you can close this task. WZ was generated\'"", ""Comment 11: \'We fixed the problem - task to close.\'"", ""Comment 12: \'ok\']""]\nRelated Issues:\n[]\n\n### End'}"
405,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8627\n\n### Instruction:\nRaw material 9114 is not arriving in DHC after several attempts.\r\nIt;s needed for several recipes that need to be in DHP by tomorrow morning.\r\n\r\n\r\nMessages in the communication log:\r\n\r\nDistributed transaction completed. Either enlist this session in a new transaction or the NULL transaction.\r\n\r\nThe transaction has aborted.\r\n\r\nThe transaction associated with the current connection has completed but has not been disposed.  The transaction must be disposed before the connection can be used to execute SQL statements.\r\n\r\nAnd several deadlocks.\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'!image-2023-02-24-18-38-52-512.png!\'"", \'Comment 3: ""Dear Rob,We ahve a deadlock here. Message queues were quite big. I have restarted services and now I\\\'m waiting till the queues will give 0 messages!image-2023-02-24-18-48-27-147.png!""\', ""Comment 4: \'I am waiting for that event as well. So we both suffer the same ;)\'"", ""Comment 5: \'19:04hThe transaction associated with the current connection has completed but has not been disposed.  The transaction must be disposed before the connection can be used to execute SQL statements.Transaction Timeout\'"", ""Comment 6: \'Restart usług"", ""Comment 7: zmiana kolejności wiadomości dla BP!image-2023-02-24-19-22-07-011.png!\'"", ""Comment 8: \'Yes"", ""Comment 9: messages queues are still not empty\'"", ""Comment 10: \'Queues are empty and I cannot see any errors anymore. But"", ""Comment 11: please confirm one thing. In Communiction log name looks a bit different than in DHH. Is that ok?!image-2023-02-24-19-50-49-495.png!!image-2023-02-24-19-51-10-692.png!\'"", ""Comment 12: \'Was this item sent from ERP to DHC? Please resent this item from ERP system.Regards\'"", ""Comment 13: \'I re-sent the item.Differences in description are not relevant I presume.\'"", ""Comment 14: \'Distributed transaction completed. Either enlist this session in a new transaction or the NULL transaction.The transaction associated with the current connection has completed but has not been disposed.  The transaction must be disposed before the connection can be used to execute SQL statements.\'"", ""Comment 15: \'The difference in description is a language thing"", ""Comment 16: both mean the same.\'"", ""Comment 17: \'Hi All recipes contains this item as a raw  item are made on plant 015 Balgoij and on this plant there is no DHP application. How do you want to produce on tahat plantThe problem was automatic acceptance of recipes on this plant. Can we turn off automatic acceptance of recipes for all plants where DHP application is not supported?Item is aleady in DHC and all recipes are accepted!image-2023-02-24-22-00-32-660!\'"", \'Comment 18: ""The recipes are exported to the plant itself\', \'Comment 19: they have their own systems to process them. I think automatic acceptance is still needed for them.If the users had exported the item before they created the recipes there wouldn\\\'t be a problem. I will instruct them to follow the right steps.""\', ""Comment 20: \'Item is aleady in DHC and all recipes are accepted. Can we close this issue?\'"", ""Comment 21: \'Yes you most certainly can. Thanks for your support"", ""Comment 22: have a nice weekend.\'"", ""Comment 23: \'Have a nice weekend for you too.\']""]\nRelated Issues:\n[]\n\n### End'}"
406,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8626\n\n### Instruction:\nId 6318595   start transfer error  \r\n\r\nProdukcja w trakcie - prośba o pilną interwencję.\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'!image-2023-02-24-15-40-02-094.png!\'"", ""Comment 3: \'This lot230224021 was in status finished. We have cancelled messages.Please"", ""Comment 4: verify.Regards\'"", ""Comment 5: \'Is correct - task to close.\'"", ""Comment 6: \'[[DHP] Production lot is already closed|onenote:https://kotrak.sharepoint.com/sites/erpasysta/Shared%20Documents/Baza%20wiedzy/Baza%20Wiedzy%20-%20ERPSD/Klienci/DEHEUS/DEHEUS%20APPLICATIONS/Polska/Baza%20wiedzy/DHP%20Produkcja.one#%5bDHP%5d%20Production%20lot%20is%20already%20closed&section-id=\\\\\\\\{CC5FB5C6-8E0D-42E5-8319-3DC0E80D8642}&page-id=\\\\\\\\{F78DF54D-8192-44F0-96D3-F7FC6B86DC74}&end] ([Widok sieci Web|https://kotrak.sharepoint.com/sites/erpasysta/_layouts/OneNote.aspx?id=%2Fsites%2Ferpasysta%2FShared%20Documents%2FBaza%20wiedzy%2FBaza%20Wiedzy%20-%20ERPSD&wd=target%28Klienci%2FDEHEUS%2FDEHEUS%20APPLICATIONS%2FPolska%2FBaza%20wiedzy%2FDHP%20Produkcja.one%7CCC5FB5C6-8E0D-42E5-8319-3DC0E80D8642%2F%5BDHP%5D%20Production%20lot%20is%20already%20closed%7CF78DF54D-8192-44F0-96D3-F7FC6B86DC74%2F%29])\']""]\nRelated Issues:\n[]\n\n### End'}"
407,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8625\n\n### Instruction:\nIn Ivory Coast there is problem with intake from production, in case the WO[IP] quantity is higher than produced one. It is hard to verify that because in the UI in WO[IP] production order quantity is displayed as produced quantity, what is confusing for the user, I would like you: 1.to check which quantity is really considered for the validation, 2. Change the UI display of WO[IP] in the column produced q-ty display q-ty produced, not ordered, 3. inform what is the tolerance of the validation between mentioned quantities on WO[IP] document \n\n### Response:\n[""Comment 1: [\'!image-1!!image-2!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Please be informed that we have forwarded the issue to the development team in order to internal analysis.We are waiting for more details and will be back with further information as soon as possible.\'"", ""Comment 4: \'Hi [~ktydrysz@deheus.pl],# Produced quantity is validated# I created a GDC-855 for this change# Tolerance quantity is available from the UI from R8.6 and can be configured here: !woipconfig! Regards\'"", ""Comment 5: \'We agreed with [~ktydrysz@deheus.pl] that since there is not so easy to change it we will change the description\'"", ""Comment 6: \'Please inform which version will contain the change. And close the ticket\'"", ""Comment 7: \'[~maciej.dobrzanski@kotrak.com]wersja 8.6?\'"", ""Comment 8: \'[~aleksandra.przybylek@kotrak.com] tak\'"", ""Comment 9: \'[~ktydrysz@deheus.pl]version 8.6.Regards\']""]\nRelated Issues:\n[\'DAP-13373\']\n\n### End'}"
408,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8624\n\n### Instruction:\nPlease set PI-RLB/2023/1084 back to entry\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Already done"", ""Comment 3: this can be closed.\'"", ""Comment 4: \'Thank you for information.\']""]\nRelated Issues:\n[]\n\n### End'}"
409,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8623\n\n### Instruction:\nHi, Recipe 111282 isn\'t arriving in DHP for Maasbracht (plant 12). \r\nIn DHC this is the error in the communication log:\r\n\r\nRecipeChangedMessage: Id=98ea2e12-154a-4bb9-8aaf-6a94d172ca0a Version=30 ProductionAreaId=06e2b435-8093-4eeb-a3b5-946c8c94181a DhhItemId=64902f3b-7f1a-40dd-a2bd-fd9e0423e6da StartDate=2/22/2023 12:00:00 AM EndDate=\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Dear Theo,Recipe is in plant now.!image-2023-02-23-19-31-45-688.png!Regards\'"", ""Comment 3: \'Thanks Aleksandra"", ""Comment 4: could you tell me what was wrong?\'"", \'Comment 5: ""Probably yesterday\\\'s issue with queues made that. Item111282 did not appear in DHC Service (it usually happens when too many messages are sent) so I needed to resent item\', \'Comment 6: resynced Recipe\', \'Comment 7: Production Recipe and Technology :)Regards""\', ""Comment 8: \'Can I close this task? :)\'"", ""Comment 9: \'Sure"", ""Comment 10: please close the task.Many thanks again. \']""]\nRelated Issues:\n[]\n\n### End'}"
410,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8622\n\n### Instruction:\nIt is impossible to link item 088452 to BM item 999999, I constantly get time-out situations when saving the changes.\r\n\r\nThere is a sales order and a calloff that are blocked now because the item is not linked.\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'I have linked these two items"", ""Comment 3: please verify and let me know.Regards\'"", ""Comment 4: \'Hi Aleksandra,the item was linked"", \'Comment 5: and I was able to link the other item variant needed myself.Thanks for the support\', ""Comment 6: the ticket can be closed.\']""]\nRelated Issues:\n[]\n\n### End'}"
411,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8621\n\n### Instruction:\nCould you please move all bookings to the respective category?\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 2: ""Hello,Which documents should be moved from851199 and881199 to customer051199?SI\\\'s and PI\\\'s or othere documents like Feed sale lines (there are some movements as I saw)!image-2023-02-24-12-10-13-203.png!!image-2023-02-24-12-10-33-852.png!""\', \'Comment 3: ""It is about the SI\\\'s and PI\\\'s\', \'Comment 4: The feed from the migration is already moved if it is correct.""\', \'Comment 5: ""Ok\', ""Comment 6: so all PI\'s and SI\'s from screens should be updated (and all calculated fields like on screen below)"", \'Comment 7: right?These invoices are archived\', \'Comment 8: so maybe there is needed also some changes in Milas.!image-2023-02-24-15-55-04-699.png!""\', ""Comment 9: \'Indeed"", \'Comment 10: these fields need to be changed except for the ones I made blue.These invoices are mostly registration I ecspect\', ""Comment 11: so they have no relation with Milas.  !image!\'"", ""Comment 12: \'All SI and PI documents from 851199 and881199 have been moved to051199.10 documents have been modified. * originally 851199:SI-RTV/2022/0021SI-RTV/2022/0018PI-RLV/2022/0016SI-RTV/2022/0016SI-RTV/2022/0007 * originally 881199:SI-RTV/2022/0022PI-RLV/2022/0018SI-RTV/2022/0020SI-RTV/2022/0015SI-RTV/2022/0006!image-2023-02-27-10-03-39-102.png!Please verify that is correct.Regards\'"", ""Comment 13: \'It is correct and almost complete. Also PI-RTV/2022/0003 and PI-RTV/2022/0010 should be moved from 851199 to 051199.\'"", ""Comment 14: \'PI-RTV/2022/0003 and PI-RTV/2022/0010 have been modified and are on round051199/0001/0001 for customer051199.Please verify that is correct.Regards\'"", ""Comment 15: \'Can be closed.\']""]\nRelated Issues:\n[]\n\n### End'}"
412,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8620\n\n### Instruction:\nIntegrated login has been disabled and saved once.\r\nLater it was switched on again and saved and it is no longer possible to log in integrated via CDNCL.\r\nAfter this, no more via DH CDN. The user BKRE is no longer in the selection menu so that it can no longer be selected.\r\n\r\nIf login different than integrated login is turned off, you can log in after first pressing Change password.\r\nThen the message Clear Password appears and you must answer the question to delete it with ""Yes"". You cannot enter a new password.\r\n\r\nAfter this you can log in to CDN CL by not using integrated login.\r\nAfter this you can log in again as a user BKRE integrated in DH CDN.\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!!image-1!!image-2!!image-4!\'"", ""Comment 2: \'Hi,I have replied you for this issue in DGS-8616. Please"", \'Comment 3: let me know if after any chnage on any user\', ""Comment 4: the user or you exited the system?Regards\'"", ""Comment 5: \'Using exit then the value NWIJ is default entered.Log in without password.Integrated login stil does not work.!image-5!\'"", ""Comment 6: \'Only those two users are impacted:NWIJ and PWIJ?Regards\'"", ""Comment 7: \'One more thing. Integrated login means you can login to the system withoud entering credentials only from your computer under your domain. Please"", ""Comment 8: let me know if usersNWIJ and PWIJ tried to login from their devices.Regards\'"", ""Comment 9: \'Logging in is done from my own device. I can no longer log in integrated. I tested once to no integrated log in. This did not work due to the password. For this"", ""Comment 10: clicked on change password where there was no option to change it. Only delete password. I could log in using BKRE. After this it is no longer possible to log in integrated. New users also cannot log in integrated.\'"", \'Comment 11: ""Niels Wijnen has again trouble logging into CDN.He wants to get into Accounting using the button accounting. Then he geta the gray screen according screen shot.  Last Thursday when he was in the office Veghel it went well. He also can\\\'t close the gray screen which keeps him logged in and has to ask someone else to kick kim out.""\', ""Comment 12: \'!image-3!\'"", ""Comment 13: \'When I at the office go to accounting there is no problem.!image-6!\'"", ""Comment 14: \'Niels is now working on the office in Ede. (Kabel)\'"", ""Comment 15: \'The system sees users assigned to domain (point 1)As we chekced"", \'Comment 16: only few users can login with integrated login (point 2). There are no users that you mentioned!image-2023-02-27-10-40-39-027.png!For example\', \'Comment 17: for Bob we can see what local group he is a member:!image-2023-02-27-10-41-50-650.png!Wherease for your user\', ""Comment 18: we can see you are not assigned to any group:!image-2023-02-27-10-43-08-251.png!I would advise to check a domain controller what went wrong.Regards\'"", ""Comment 19: \'The wright NT group and user is selected.!image-7!!image-8!\'"", ""Comment 20: \'!image-9!\'"", ""Comment 21: \'But as I send you screenshot from CMD"", ""Comment 22: they are not in the domain. So they need to be resynced in domain controller.Regards\'"", ""Comment 23: \'Why can other user who are not in your screen shot log in integrated?For example RGAN.!image-10!!image-11!\'"", ""Comment 24: \'Dear Bert,Let me be more clear. This is the issue of domain controller"", \'Comment 25: not ERP XL itself. When the policy will finally update\', ""Comment 26: no one will be able to login to xl with integrated login. You need to verify this issue from Active Directory side.Regards\'"", ""Comment 27: \'What action is expected of us. Our service desk sees all users in AD\'"", ""Comment 28: \'We have forwarded your issue to producer. We will let you know about the result as soon as possible. Till then"", ""Comment 29: I will put this task in On Hold status.Regards\'"", ""Comment 30: \'I think there is some missunderstand how integrated login works in ERPXL. To allow user to use integrated login there must be some conditions meet. * User have to be member of specified domain group. * This group have to be synchronized with ERPXL to match domain NTSID and NT account login with operator in ERP system. * Domain group synchtonization with ERPXL must be done when XL is run as administrator. * User has to got Use NT authorization for thos user parameter set. * User have to be login through correct domain account to Windows while login to ERPXL.If any of those conditions is not meet then You will not be able to log in using domain account.Operators PWIJ and NWIJ do not have NTSiD or domain account provided in ERPXL. Those account nas not been synchronized to ERPXL.Operator RGAN do have bothNTSiD anddomain account provided in ERPXL. That means it have been in proper domain group when synchronization occurs.In order to synchronize domain group with ERPXL You should run ERPXL as Admninistrator and run Synchronize accounts of ERP XL operators with NT group operation.!image-2023-03-07-19-46-37-786.png!Be aware that any mapped connections for operators that has been removed from provided domain group wil bee removed from ERPXL. Caution is advised.Please check.\'"", ""Comment 31: \'In the past i did login using AD.A new user could not login ussing AD.When i was testing login with my own name and pasword ( not using AD) i could login.Whwn i activated login usung AD it did not work anymore while in the past there was no problem..  \'"", ""Comment 32: \'Could you please confirm if all below steps have been done correctly: * User have to be member of specified domain group. * This group have to be synchronized with ERPXL to match domain NTSID and NT account login with operator in ERP system. * Domain group synchtonization with ERPXL must be done when XL is run as administrator. * User has to got Use NT authorization for thos user parameter set. * User have to be login through correct domain account to Windows while login to ERPXL.Regards\'"", \'Comment 33: ""Hi,I noticed in one of your screenshots you\\\'re looking at the group in the EMEA.corp.deheus.com domain. That\\\'s not where our user accounts reside (at the moment) that is the HEUS domain (de-heus.nl). In that domain there is a group with the same name\', \'Comment 34: but filled with the proper useraccounts.Please let the application refer to the HEUS domain. Thanks!""\', ""Comment 35: \'Zalogowałam się userem w domenie heus"", ""Comment 36: a dalej woła emea!image-2023-03-20-13-49-21-733.png!\'"", ""Comment 37: \'!image-2023-03-20-14-37-56-982.png!\'"", ""Comment 38: \'Dear Martijn,Yes"", \'Comment 39: because I have run a query with group assigned in XL and it looks this group is in emea\', ""Comment 40: not heus. Are you able to check how this group is named in Heus domain?!image-2023-03-21-08-30-12-977.png!Regards\'"", ""Comment 41: \'The group has the same name in HEUS: NL - Citrix - DH Premix Prod\'"", ""Comment 42: \'Any update to mention?\'"", ""Comment 43: \'Did You try update information on domain users in ERPXL according to my previous comment?!image-2023-03-28-12-15-29-605.png!\'"", \'Comment 44: ""Hi\', ""Comment 45: it\'s a bit unclear for me what information to take from that post. The users are member of a certain group. What exactly do you want me to change on that?The synchronization you mention"", \'Comment 46: is that a manual action that has to be done every now and then?""\', ""Comment 47: \'This action should be done every time when you add new member to specific domain group. This is not an automatic process.\'"", ""Comment 48: \'Please"", ""Comment 49: let me know if expect any additional actions from us regarding this issue? Can we close this ticket?\'"", ""Comment 50: \'All users are in the list for selecting user.But why do already syngronized user disappear and are only a few users present?\'"", ""Comment 51: \'only a few users present acording to Kotrak\'"", ""Comment 52: \'During synchronization"", ""Comment 53: the list of AD users related to ERP XL is refreshed according to the current content of the selected group.Do you expect any additional actions from us regarding this issue?\'"", \'Comment 54: \\\'Do we first have to click on ""NT Login"" at the bottom left of the screen?How long will it take for this to show a result. The screen does not show anny action for a very long time.Is this oke or is this wrong?If this is oke doe we have to click : Synchronize account of ERP-XL?!image-12!!image-13!!image-14!\\\'\', \'Comment 55: \\\'Use NT-integrated login parameter!image-2023-04-05-12-41-43-710.png!should be choosen when you want to set ""Use NT authorization for this operator"" paramenter on operator card.!image-2023-04-05-12-43-04-995.png!If You do not choose it then mentioned paramenter on operator card will not bee set during synchronization.Duration of synchronization depends on how many operators will be changed when process occurs. this process can take several minutes. Please run in while ERPXL (administrator module) is running as administrator.\\\'\', ""Comment 56: \'Please"", ""Comment 57: let me know if expect any additional actions from us regarding this issue? Can we close this ticket?\'"", \'Comment 58: ""Setting to integrated login is not enough. Users can be selected from the list\', \'Comment 59: but it still doesn\\\'t work. Please perform the necessary actions so that the integrated login works properly again.""\', ""Comment 60: \'Do users that have an issues with login into ERPXL through integrated login are wokning on theirs accounts in Windows domain. Is it the same domain as provided in ERP. Please an example of incorrect user configuration. Please provide information on witch account has he logon into windows account. Is there any message while user tries to login al integrated user into ERP system.\'"", ""Comment 61: \'For myself (Kremers) I have always been able to log in integrated (for years). After I removed integrated once and then put it back on integrated"", ""Comment 62: it suddenly stopped working. What happens at Synchronize Account. Will I only have a very limited amount of users left?!image-15!!image-16!!image-17!\'"", \'Comment 63: \\\'It looks like there is an issue with domain controllerIm running*net group /domain ""NL - Citrix - DH Premix Prod""* command in *HEUS* domain ant it has been proceed for*EMEA* domain. It gives information on limited number of domain group members.!image-2023-04-12-08-36-25-787.png!\\\'\', \'Comment 64: ""The server resides in the EMEA domain\', ""Comment 65: but the users in HEUS. So the group that is used should be HEUS\\\\\\\\NL - Citrix - DH Premix Prod.That\'s not an issue with the domain controller"", \'Comment 66: it is just a different group""\', \'Comment 67: \\\'Synchronization data in ERPXL contains information on opertor NT account and it\\\\\\\'s NT SID id.!image-2023-04-13-13-07-59-433.png!Unfortunately I do not have access to this information in AD regardless of whether I log in to the HEUS or EMEA domain. It is possible that data in ERPXL is outdated.Please try to resynchronize data in ERP system with""Use NT authorization for this operator"" paramenterset on and let me know if that solved this issue.\\\'\', \'Comment 68: \\\'I clicked on ""NT-Login"" and then the attached screen appeared after a few minutes.Do we now have to click on ""Synchronice accounts or ERP XL"" for further processing?!image-18!\\\'\', \'Comment 69: \\\'What is the status of this discussion?Bartłomiej Brzęk    Yesterday 08:41It looks like there is an issue with domain controllerIm running net group /domain ""NL - Citrix - DH Premix Prod"" command in HEUS domain ant it has been proceed for EMEA domain. It gives information on limited number of domain group members.Martijn Meier    Yesterday 14:36The server resides in the EMEA domain\', ""Comment 70: but the users in HEUS. So the group that is used should be HEUS\\\\\\\\NL - Citrix - DH Premix Prod.That\\\\\'s not an issue with the domain controller"", ""Comment 71: it is just a different group\'"", \'Comment 72: \\\'[~bkremers@deheus.com]Yes you shouldclick on ""Synchronice accounts or ERP XL"" for further processing\', \'Comment 73: byt be aware that all operators for selected domain group will be synchronized.Regarding the domain controller discussion.I do not have access to Heus domain\', \'Comment 74: I can not see any users in domain HEUS\', \'Comment 75: group ""NL - Citrix - DH Premix Prod"". I can not verify [~mmeier@deheus.com]information. I see that in EMEA domain for""NL - Citrix - DH Premix Prod"" group there is limited number of users assign to that group.If ""NL - Citrix - DH Premix Prod"" group on different domains exchange information between domains and users SID is changing then this could be an source of that issue.I\\\\\\\'m no expert on the AD controller and its configuration\', ""Comment 76: but it looks unusual.\'"", ""Comment 77: \'Hi"", \'Comment 78: as you can see in this attachment from a server in the HEUS domain\', \'Comment 79: the group contains almost 90 users. Can we click the ""Synchronize accounts..."" button in the application without breaking any existing account configuration?!afbeelding!\\\'\', \'Comment 80: ""As I wrote before\', \'Comment 81: I do not have access to this domain group. I can not confirm if those account are the same as accounts synchronized with ERPXL. I do not know if all accounts in ERPXL are still in provided domain group\', ""Comment 82: with the same NT SID id\'s. You shuld check if provided domain group conatains all users needed.After synchronization if there will be any issues with user that shuld have access to ERP system as integrated login"", \'Comment 83: You can always disable this feature for that one operator and let him login with user and password.""]\']\nRelated Issues:\n[\'DGS-8616\', \'DGS-8637\', \'DGS-8647\']\n\n### End'}"
413,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8619\n\n### Instruction:\nIntakes are not being sent from DHP to DHC.\r\nAn example we have more intakes that are not synchronized to DHC at all.\r\n\r\nFor example, we have ASN-104/01/2023 and ASN-105/01/2023. Which are identical but one isn’t in DHC and the other one is. \r\n\r\nASN-104/01-23 is done in Vt-381/01/23 and ASN-105/01/2023 is done in VT-380/1/23. Both are closed around the same time.  \r\n\r\n\n\n### Response:\n[""Comment 1: [\'Hi,we need 8 working hours for analysis. Please accept.Regards.\'"", ""Comment 2: \'accepted\'"", ""Comment 3: \'[~piotr.gaczorek@kotrak.com]"", ""Comment 4: [~marcin.block@kotrak.com],Tutaj development został zrobiony trzeba podegrac nowy DHC Service\'"", ""Comment 5: \'Hello,after the developers analysis a new version of DHC Service Client will be prepared and uploaded for the solution.Regards.\'"", ""Comment 6: \'Buduję nową aplikację i wgram im na produkcję.\'"", ""Comment 7: \'Is it known when the new version of DHC Service will be installed?\'"", ""Comment 8: \'Hej"", \'Comment 9: możemy przekazać termin klientowi\', ""Comment 10: dzięki.\']""]\nRelated Issues:\n[\'DGS-8410\']\n\n### End'}"
414,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8618\n\n### Instruction:\nAfter sales orders created with a transport expense ; The transport detail is not visible when a Vehicle ticket is created from the sales order ; the VT document doesn`t show the transport detail ; \r\nsee attached document SO 1015 showing trans but not VT 1168 ? \r\n\n\n### Response:\n[""Comment 1: [\'!image-3!!image-4!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Thanks very much for the quick response ;\'"", ""Comment 4: \'Could You please bring more detailsPlease send a screen-shoot of example oftransport detail visible in VT.I compare VT you mentioned and it is similar.I am not sure if you are asking for some change section for VT similar to SO?\'"", ""Comment 5: \'Hey dear  This problem just started since the day before yesterday . if you see all the VTs created from the SO which have transport ; they all show transport detail on documents ;  See this or on the attached documents all VTs ;  Because of the reason we print and give Customers the VT detail so when it is not visible couse a problem communicating with our sales workers    !image001!        *From:* Agnieszka Januszewska (Jira) <jira@kotrak.com>   *Sent:* Friday"", \'Comment 6: February 24\', ""Comment 7: 2023 15:30  *To:* Gemechis Terefe <gemechis@alemakoudijs.com>  *Subject:* DGS-8618 Sales orders created with Transport ; transport not visible on Vehicle ticket Document   !transport gemechis.PNG|thumbnail!\'"", ""Comment 8: \'Ok so item named trans2 is not visible on VT. I will check it.\'"", ""Comment 9: \'You can see the deference in SO 1013"", \'Comment 10: SO1014 and SO 1015 /   !image002!   !image001! !image004!  *This all VTs doesn`t have trans information when all the SO 1013,1014,1015 were all created with transport (Trans)*  *See above VT and this ones which Trans is visible where all the above 3 trans not visible*  ** !image003!  **  **  *From:* Gemechis Terefe   *Sent:* Friday\', \'Comment 11: February 24\', \'Comment 12: 2023 15:51  *To:* dgs@help.kotrak.com  *Subject:* RE: DGS-8618 Sales orders created with Transport ; transport not visible on Vehicle ticket Document    Hey dear  This problem just started since the day before yesterday . if you see all the VTs created from the SO which have transport ; they all show transport detail on documents ;  See this or on the attached documents all VTs ;  Because of the reason we print and give Customers the VT detail so when it is not visible couse a problem communicating with our sales workers    !image003!       *From:* Agnieszka Januszewska (Jira) <[jira@kotrak.com|mailto:jira@kotrak.com]>   *Sent:* Friday\', \'Comment 13: February 24\', ""Comment 14: 2023 15:30  *To:* Gemechis Terefe <[gemechis@alemakoudijs.com|mailto:gemechis@alemakoudijs.com]>  *Subject:* DGS-8618 Sales orders created with Transport ; transport not visible on Vehicle ticket Document   !image001-1!\'"", ""Comment 15: \'Yes please thanks !\'"", ""Comment 16: \'HelloI can see that someone use some procedure but there change on erp xl on article card the type was changed from type product to type cost.It was changed 22.02.2023 about 12.50Why it was changed ?!image-2023-02-27-14-03-49-848.png!\'"", ""Comment 17: \'Hey dear  As I tried to understand the situation happened at moments is ;- # A sales officer mistakengingly created a SO with a trans of 1 kuntal or 100 kg where she was supposed create 101 kunatal not 1 kuntal or 101,000 kg ; # Then they tried create a trans so just for the mistaken 100 kunatl left to include ? so since then the system revoked Showing trans item on VT even if the Trans is visible on SO  Since then they are revoked to create a SO with trans  Regards!image001-2!\'"", ""Comment 18: \'They just tried create a SO just for the mistake left 100 kuntal ; just another SO only for this purpose ;  Since it stopped allowing  Regards      *From:* Gemechis Terefe!image001-2!\'"", ""Comment 19: \'I asked you about changes on item with code TRANS2.Why the type of item was changed via database?\'"", \'Comment 20: ""SELECT * FROM [DHPlantVCBusinessLogicMain].[dbo].[VehicleTicketPackedDispatchElements] where id in  (\\\'7627D406-615F-45D7-9673-56FF9AE004B2\\\',\\\'9F4A44A3-C64D-41F9-B86B-9EAF58188D53\\\') --and ItemId=\\\'C6FCFBA4-A394-48BD-A9BE-1B64D8894D95\\\' select * from OrderElements where id=\\\'75DE5DFD-95B7-46A6-BFD8-C08BD723B1E6\\\'select cdn.TSToDate(Twr_LastModC,1),* from cdn.TwrKarty where twr_kod like \\\'trans2\\\'select top 100 * from cdn.HistoriaZmian where HIS_ObiNumer=\\\'7326\\\' or HIS_StaraWartosc=\\\'TRANS2\\\'select * from cdn.TwrGrupyselect cdn.TSToDate(1045918526,1)""\', ""Comment 21: \'!image-2023-02-27-17-22-43-744.png!\'"", ""Comment 22: \'Please check this item in dhp it is set as unhandled"", \'Comment 23: so the system is unable to put it to right VT element table. As I wrote before\', ""Comment 24: what was the reason that you changed this type few days ago? !image-2023-02-27-17-52-42-109.png!!image-2023-02-27-17-52-42-109!\'"", ""Comment 25: \'Hello Dear ; I am responsible for system setting changes if it is requested or suggested by the Deheus or the company but I don`t do any changes with out asking or discussing with our professionals like you guys Kotrak .  May be This is a mistake done by the other IT person that have access to our server Data base environment .  So please let me know who tried to change this ; whether to help the sales officers or mistaken ? Could you please also help us set this right and suggest me how to put control over this kind of mistakes not to happen again ;  Thanks !image001-3!!image002-1!\'"", ""Comment 26: \'Hello  Yes I checked this on DHP and it is like you mentioned on email ; it is unhandled for both ;  I still want to know who tried change via database ; so from now on "", \'Comment 27: the person must be aware of not doing changes with out discussing with the group ; and responsible for the problem happened dispatching ;  Regards     !image003!    *From:* Gemechis Terefe   *Sent:* Tuesday\', \'Comment 28: February 28\', \'Comment 29: 2023 07:58  *To:* dgs@help.kotrak.com  *Subject:* RE: DGS-8618 Sales orders created with Transport ; transport not visible on Vehicle ticket Document    Hello Dear ; I am responsible for system setting changes if it is requested or suggested by the Deheus or the company but I don`t do any changes with out asking or discussing with our professionals like you guys Kotrak .  May be This is a mistake done by the other IT person that have access to our server Data base environment .  So please let me know who tried to change this ; whether to help the sales officers or mistaken ? Could you please also help us set this right and suggest me how to put control over this kind of mistakes not to happen again ;  Thanks      *From:* Agnieszka Januszewska (Jira) <[jira@kotrak.com|mailto:jira@kotrak.com]>   *Sent:* Monday\', \'Comment 30: February 27\', ""Comment 31: 2023 19:54  *To:* Gemechis Terefe <[gemechis@alemakoudijs.com|mailto:gemechis@alemakoudijs.com]>  *Subject:* DGS-8618 Sales orders created with Transport ; transport not visible on Vehicle ticket Document   !image001-3!!image002-1!\'"", ""Comment 32: \'About solution I may set previous setting for items Trans2 and Trans in erpxl ( type product in erpxl)In this task we have focused on clearingandunblocking the process.If there is a need from your sideto investigate the reasonof the issue"", \'Comment 33: we may raise RootCause Analysis (RCA)task for you.Please\', ""Comment 34: let us knowhow you wish us to proceed.\'"", ""Comment 35: \'Hey Dear  We need the solution bro As soon as possible ; we need you set us to the pervious setting for both items (Tran & Tran2). Thanks  The only reason we asked to investigate was just to inform or warn and explain the consequences to the user . so this won`t happen again .  Thanks very much again  Regards\'"", ""Comment 36: \'!newsettings.PNG|thumbnail!\'"", ""Comment 37: \'Hello I set this to codes"", ""Comment 38: so in new vt it be working fine again.Please remember that for vt module in dhp types service and costs are unhandled.!newsettings.PNG!\'"", ""Comment 39: \'Hello Dear  I really want appreciate the effort and thanks very much ;   So now we have no problem of including Trans item in VT list Thanks again!image001-4!\']""]\nRelated Issues:\n[]\n\n### End'}"
415,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8617\n\n### Instruction:\nThe IPOR-00000009/23/YGM - USD Currency Fx-Rate is 2983 MMK. When we check the currencies table for Jan 2023. I could not find that rate. Could you please check?\n\n### Response:\n[""Comment 1: [\'[^Exchange Rate_CDN.xlsx] _(11 kB)_!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 3: "" !screenshot-1! {code:java}SELECT TOP (1000) [WaE_Symbol]      ,cdn.tstodate([WaE_KursTS],1)      ,[WaE_Lp]      ,[WaE_KursM]      ,[WaE_KursL]      ,[WaE_OpisKursu]  FROM [CDNXL_Myanmar].[CDN].[WalElem]  where WaE_Symbol=\\\'usd\\\' and WaE_KursL=\\\'2983.00\\\'  order by 2 desc{code}""\', \'Comment 4: ""This currency is from 12/30/2022 !screenshot-2! It was the last of this day in 2022\', \'Comment 5: the next one is from 03/01/2023 and that one should be on document.But it looks like it wasn\\\'t added then. Currently when checking the rate from 03/1/2023 is being added.Regards.""\', ""Comment 6: \'Hi"", \'Comment 7:         I have 2 questions:1) Do CDN system take ""system date""\', ""Comment 8: to get Fx-rate? Not server date to get Fx-Rate.2) I am not clear about 03-Jan-2023? Could you please elaborate more?\'"", ""Comment 9: \'Hello,the date is taken from XL & as for the date of January 3rd it was the last one before January 5th(looking now).\'"", ""Comment 10: \'Hi,I got it. Please close the Ticket. \']""]\nRelated Issues:\n[]\n\n### End'}"
416,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8616\n\n### Instruction:\nBatch off payments shows strange signs.\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'myślę"", ""Comment 4: że reset widoku okna powinien pomóc\'"", ""Comment 5: \'zapytam go"", \'Comment 6: za chwilę mam spotkanie z Ghaną\', ""Comment 7: to będzie musiał poczekać :Pw sprawie NAV\'"", ""Comment 8: \'Hello,Kindly approve lowering priority of this task to P2 as P1 issues are only those with a critical or a blocking impact on business processes . This seems not to be the case in this issue so we suggest decreasing the issue priority.Regards\'"", ""Comment 9: \'Making the last batch last week the batch was oke.A moment later displaying it again the same strange screen occurred.When making a new batch this week the same strange screen occures.\'"", ""Comment 10: \'Please restore the default view settings !image-2023-02-23-12-47-32-936.png|width=847,height=389!Regards\'"", ""Comment 11: \'But this does not have bloking impact on producing product or deliver product. So kindly approve lowering priority to P2.\'"", \'Comment 12: ""jak to nie pomoze to bedzie trzeba wyczyscic formatowanie list{code:java}---szukamy operatoraselect *from cdn.OpeKartywhere Ope_Ident = \\\'SKO\\\'--szukamy powiazane z nim formaty listselect *from cdn.FormatyListwhere FLS_IDOperatora = 22--zmieniamy powiazanie formatow na dowolnego nieustniejacego operatoraupdate cdn.FormatyListset FLS_IDOperatora = 888888where FLS_IDOperatora = 22--jesli wszystko gra i buczy to usuwamy wpisydelete from cdn.FormatyListwhere FLS_IDOperatora = 888888{code}""\', ""Comment 13: \'It is critical because we can not do anny paymentYour advice is restore the default view setting. My question is how to do this?Someting other strange thing appears.I had saved my own login.Afther warts i could not login and had to type in a password.Then the the message off integrated login was shown.Afther unlink : Block different than integrated login can work in the system without typing a password.!image-1!!image-2!!image-3!!image-4!\'"", ""Comment 14: \'Is there a problem with integrated login afher saving a user?Added new user PWIJ als can not get in the system\'"", ""Comment 15: \'User is NWIJ\'"", ""Comment 16: \'When i vieuw the screen there is no problem!image-5!\'"", ""Comment 17: \'To restore default sysstem settings"", ""Comment 18: please try!image-2023-02-23-14-17-55-072.png!\'"", ""Comment 19: \'Have exited system after each modification or just used Change Operator?!image-2023-02-23-14-37-59-087.png!\'"", ""Comment 20: \'Some onformation for ticket DGS-8620 about integrated login has been typed in this ticket"", ""Comment 21: Sorry for that. Integrated login is ticket dgs-8616.\'"", ""Comment 22: \'So what about batch of payments? Is it configured properly now? Have you reset the view?Regards\'"", ""Comment 23: \'Window Default Setting was the solution of the problem.Verry strange the setting disapeared. What can be the reason.\'"", ""Comment 24: \'You have very old version of ERP system"", \'Comment 25: this may be one of the reasons. For exact reason\', \'Comment 26: we may raise RCA task.Please\', ""Comment 27: let us know what would be next step.Regards\'"", ""Comment 28: \'Is : very old version of ERP system an general reason for lot of problems? Please Close ticketThank you\'"", ""Comment 29: \'I did not mention that for most / a lot of problems"", ""Comment 30: but for this particular one - it is highly possible.Thank you.Regards\']""]\nRelated Issues:\n[\'DGS-8620\']\n\n### End'}"
417,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8615\n\n### Instruction:\nSystem niepoprawnie naliczył ekwiwalent za urlop pracownikowi Filiński Karol. Wynagrodzenie zasadnicze nie zostało ujęte w podstawie.\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 2: ""Przy wyliczaniu ekwiwalentu należy zwrócić uwagę na kilka elementów:{color:#394754}Proszęzwrócić uwagę na jakiej liście płac zostaje naliczany ekwiwalent. Ekwiwalent powinien być naliczony na liście płac utworzonej za ostatni miesiąc zatrudnienia pracownika.{color}{color:#394754}  Dodatkowo pr{color}oszę zweryfikować czy poprawnie wprowadzono datę zwolnienia pracownika. Data zwolnienia powinna zostać odnotowana w bieżącym zapisie historycznym pracownika\', \'Comment 3: a nie poprzez aktualizację formularza danych kadrowych. Jeżeli zwolnienie pracownika zostało odnotowane poprzez aktualizację zapisu\', \'Comment 4: proszę usunąć zbędny zapis.{color:#494949}W kolejnym kroku\', ""Comment 5: w celu poprawnego wyliczenia składnika \'Ekwiwalent za niewykorzystany urlopu\'"", \'Comment 6: należy przeliczyć limity nieobecności pracownika. Limit / limity nieobecności na rok zwolnienia pracownika powinny mieć okres zawężony do daty zwolnienia pracownika. Jeżeli na liście limitów byłby limit zawierający niepoprawne dane (okres obowiązywania limitu po dacie zwolnienia pracownika)\', \'Comment 7: proszę usunąć limit / limity na bieżący rok i dodać go ponownie. {color}""\', ""Comment 8: \'Please close to task.\']""]\nRelated Issues:\n[]\n\n### End'}"
418,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8614\n\n### Instruction:\nI\'ll write an e-mail\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'What is the status of this?\'"", \'Comment 3: ""Hello,[~CJong@deheus.com]We didn\\\'t receive any email with details about this task\', \'Comment 4: can you verify is this task actual or send us information what should be done in this topic.Regards""\', ""Comment 5: \'{color:black}No actions seen here.{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Christinede{color} |{color:#000001} {color} |{color:#000001} Jong{color} |  {color:#000001}MedewerkerContractadministratie{color} | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.de-heus.nl/]>{color} | |  *{color:#006FB7} *DEHEUSVOEDERSB.V.*{color}* | | | |{color:#000001} Postbus396 6710BJEde \\\\u200b{color} | |{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} | | |{color:#000001} T:0318675567{color} |  {color:#000001}KvK14626985{color}   _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | | !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | | !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} | | !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} |        *Van:* Mitch van Bovene (Jira) <jira@kotrak.com>   *Verzonden:* dinsdag 21 maart 2023 11:50  *Aan:* Jong"", ""Comment 6: Christine de <CJong@deheus.com>  *Onderwerp:* DGS-8614 Registered document not visible on feedsale FE-N/0008   \'"", ""Comment 7: \'{color:black}Hi Damian,{color} {color:black}{color} {color:black}Resolve this as done.. I really don’t know what it was anymore.{color} {color:black}{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Christinede{color} |{color:#000001} {color} |{color:#000001} Jong{color} |  {color:#000001}MedewerkerContractadministratie{color} | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.de-heus.nl/]>{color} | |  *{color:#006FB7} *DEHEUSVOEDERSB.V.*{color}* | | | |{color:#000001} Postbus396 6710BJEde \\\\u200b{color} | |{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} | | |{color:#000001} T:0318675567{color} |  {color:#000001}KvK14626985{color}   _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | | !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | | !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} | | !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} |        *Van:* Damian Świstek (Jira) <jira@kotrak.com>   *Verzonden:* dinsdag 21 maart 2023 12:00  *Aan:* Jong"", ""Comment 8: Christine de <CJong@deheus.com>  *Onderwerp:* DGS-8614 Registered document not visible on feedsale FE-N/0008   \']""]\nRelated Issues:\n[]\n\n### End'}"
419,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8613\n\n### Instruction:\nSee attached example: I think this is an issue for the dev team: Due to some ERP bug, a delete message for a load is send multiple times (30x in this case). In DHP the load is multitimes created. As the loadnumber should be the key here, how is this possible? \n\n### Response:\n[""Comment 1: [\'!afbeelding!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 3: ""Jest tego więcej ale mają różne numery !screenshot-1!   !screenshot-2! {code:java}SELECT count(ForeignNumber),ForeignNumber  FROM [DHCountry_NL_AS400_PROD].[dbo].[ShippingNotices]   -- where ForeignNumber like \\\'8_L000133584\\\'  group by ForeignNumber  having count(ForeignNumber)>10{code}""\', ""Comment 4: \'The document appears so many times in the list because of the different numbers for the document - as seen in DHC: !screenshot-3! Was it correctly canceled from the ERP?\'"", ""Comment 5: \'It was incorrectly cancelled in TMS system. But why does DHC create multiple lines? Load number is not the key here?\'"", \'Comment 6: ""[~TDankers@deheus.com]after canceling order\', \'Comment 7: mapping key is deleted to avoid problem that we had in past with duplicated TransactionIDs on different order elements\', ""Comment 8: that\'s why if we canceled previous because of lack of order element"", \'Comment 9: and removed mapping and that why new mapping and new order is created""\', ""Comment 10: \'Thanks for explanation"", ""Comment 11: ticket can be closed\']""]\nRelated Issues:\n[]\n\n### End'}"
420,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8612\n\n### Instruction:\nHi, \r\n\r\nThe VT-6450/20/23 is ""dispatch VT"".  We have 2 weight-bridge. When the truck of VT-6450/20/23 weight on WB-1 for departure, we have another truck on WB2 for intake. While user close the VT-6450, user didn\'t encounter any issue. After some time user realized that VT-6450 VT header information is gone. I do see VT status change as ""Intake Inprogress"". Could you please check why that could happen?\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello"", \'Comment 3: is this a single case\', ""Comment 4: is the problem only with this VT?\'"", ""Comment 5: \'Hi"", ""Comment 6: So far we have 2 cases like that. first cases around 6 months ago.\'"", ""Comment 7: \'Change logging is disabled for VT"", ""Comment 8: we can run it and check for another case if it occurs.Change logging will be then active all the time.What about the current one can be canceled and reissued?\'"", ""Comment 9: \'{code:java} FROM [DHP_YAN].[dbo].[VehicleTicketHeader] v   where VtH_Id = 390632{code}\'"", ""Comment 10: \'On this case"", \'Comment 11: we will handle alternative solution for current VT.  If new case happen\', ""Comment 12: are we able to check our own?\'"", ""Comment 13: \'Hello"", ""Comment 14: yes change logging for the VT header has been started. We will have data for analysis.\'"", ""Comment 15: \'Hi"", ""Comment 16: Please close this ticket and I will raise new ticket if we encounter again.\']""]\nRelated Issues:\n[]\n\n### End'}"
421,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8611\n\n### Instruction:\nIt seems that ERP integration communication is broken.\r\nI see that orders are being delivered succesfully to the ERP integration service, but are not processed in DHC.\r\nAlso no entries in the communication logs. It look like something is not running.\r\nCan you please fix this ASAP. This is blocking our logistical processes\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'!image-2023-02-23-08-12-30-871.png!\'"", ""Comment 3: \'Hello"", \'Comment 4: Process is verified\', ""Comment 5: in another request DGS-8608.Regards\'"", \'Comment 6: ""I don\\\'t see that request. I think the problem is not solved""\', \'Comment 7: ""Hello\', \'Comment 8: Message processing is in progress ERP integration.I\\\'m asking you to being patient.Regards""\', ""Comment 9: \'Dear Wijnand,The Queues are empty now so DHC should work properly now. Please confirm and let me know if we can close this task and task related under DGS-8608Regards!image-2023-02-23-15-40-11-023.png!\'"", ""Comment 10: \'This task can be closed\']""]\nRelated Issues:\n[\'DGS-8608\']\n\n### End'}"
422,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8610\n\n### Instruction:\nGoodmorning,\r\n\r\nIn the xml file on DHP Veghel for Salesorder: SO000069460 there is missing some data. The product label information is missing.\r\nIt\'s important information for our customers.\r\n\r\nAs attachment hereby the xmldata that we recieved on DHP and the printscreen of the itemcode 318254 and itemcode 318547 and label that belongs to this itemcodes at DHP and DHC.\r\n\r\nPlease could you have a look at this problem?\r\nThis example is not the only one, at the moment, I got more questions about this type of issue.\r\n\r\nKind regards,\r\n\r\nGerard\n\n### Response:\n[""Comment 1: [\'[^Afleverbon_ve_SO000069460_6EE64133-5DB2-2B47-AB1B-3D344B06812F.xml] _(8 kB)_!DHC_Item_318254.PNG|thumbnail!!DHC_Item_318547.PNG|thumbnail!!DHP_Item_318254.PNG|thumbnail!!DHP_Item_318547.PNG|thumbnail!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 3: ""tu jest inna sytuacja dla podengo zgłoszenia nie ma rozbieżnosci miedzy recepotura na elemencie a na vteselect i.Code\', \'Comment 4: r.EntityId rc_EntityId\', \'Comment 5: r.Version\', \'Comment 6: r.Subversion ,--,i.ItemBaseWeight\', \'Comment 7: g.Code ,-- la.Value\', \'Comment 8: la.No\', \'Comment 9: la.Type\', \'Comment 10: la.LabelType\', \'Comment 11: la.Sequence,ln.Name\', \'Comment 12: ln.Quantity\', \'Comment 13: ln.QuantityUnit,lnt.Name\', \'Comment 14: lnt.Type\', \'Comment 15: ln.Description,ln.No\', \'Comment 16: ln.IsHeader\', \'Comment 17: ln.Ordinal\', \'Comment 18: lnt.*,lnt.Name,--,--lw.Code\', \'Comment 19: lw.Description,lt.Description,ltf.Translation --\', ""Comment 20: ltf.Idfrom [DHPlantPCSBusinessLogicMain].[dbo].Recipes rjoin [DHPlantPCSBusinessLogicMain].[dbo].Items i on i.id = r.ItemIdjoin [DHPlantProdBusinessLogicMain].[dbo].Labels l on l.ItemId = r.ItemId and l.VersionNo=r.Version and r.PlantId = l.PlantIdjoin [DHPlantProdBusinessLogicMain].[dbo].Languages g on g.Id = l.LanguageIdleft outer join [DHPlantProdBusinessLogicMain].[dbo].LabelNutrients ln on ln.id = l.Idleft outer join [DHPlantProdBusinessLogicMain].[dbo].LabelNutrientTypes lnt on lnt.Id=ln.LabelNutrientTypeId--left outer join [DHPlantProdBusinessLogicMain].[dbo].LabelWarnings lw on lw.Id=l.Id and lw.No=ln.Noleft outer join [DHPlantProdBusinessLogicMain].[dbo].LabelTranslations lt on lt.LanguageId = g.Idleft outer join [DHPlantProdBusinessLogicMain].[dbo].LabelTranslationFields ltf on ltf.Id=lt.Id and ltf.LabelNutrientTypeId=ln.LabelNutrientTypeId--and ltf.No=ln.Nowhere 1=1and ln.No > 0aND ln.IsHeader = 0--and r.Id in (\'8FC6DDFB-D79A-4F03-88F0-65F41AC40743\')--,\'9274CACB-B6D2-4603-BB2B-75BFFF335BAB\',\'DC3E0094-694A-4019-8726-73BFB4505B40\',----\'D16DF237-8B1F-47E0-A33C-422CF89826FA\',\'E9A39A85-600E-45EF-A6F6-396DE48BD141\')and--and l.Id=andi.Code = \'318254\'and g.Code = \'DE\'order by r.Version desc"", \'Comment 21: Subversion desc \', \'Comment 22: lnt.Type\', \'Comment 23: ln.Ordinalwyniki są ale plik jest bez zawartosci dla labelki""\', ""Comment 24: \'After analisys for orderSO000069460 we have diffrent situations then in linked dgs.Could please provide backup of plant databases with current data ( from yesterday)!image-2023-02-24-12-21-21-913.png!\'"", ""Comment 25: \'Good morning Agnieszka,Can you tell me which databases are involved?Regards,Gerard\'"", ""Comment 26: \'Thank you please provide bakcups for databaseDHPlantPCSBusinessLogicMain,DHPlantVCBusinessLogicMain,DHPlantWMSBusinessLogicMain,DHPlantStockBusinessLogicMain,DHPlantProdBusinessLogicMain\'"", ""Comment 27: \'Goodmorning Agnieszka,Question: are you able to connect to the DHVD01DB47 to access the backup?The backup is 14,1 Gb on: G:\\\\\\\\MSSQL\\\\\\\\Veghel\\\\\\\\Backup\\\\\\\\20230302 at the DHVD01DB47.RegardsGerard \'"", ""Comment 28: \'The IP serwer is :172.23.1.83?I can not log to these rdp nor with ip address nor with usingDHVD01DB47?Maybe You may add this to location when we have access f.e:172.23.1.67"", ""Comment 29: or172.23.1.88?\'"", ""Comment 30: \'Good morning Agnieszka,We added your account to a shared folder.Your colleque:  Maciej Dobrzanski has also the possibility and access to this share and the backup who is available in this share-folder.Please could yo try it again?Regards,Gerard \'"", ""Comment 31: \'Could you bring full path and ip for the server as I asked you beforeIs that172.23.1.67"", ""Comment 32: or172.23.1.88? Or any other IP?I tried to find in on172.23.1.88 via network!image-2023-03-06-12-14-59-115.png|width=481,height=172!\'"", ""Comment 33: \'Hi Agnieszka,hereby,\\\\\\\\\\\\\\\\DHVD02DB47\\\\\\\\20230302\\\\\\\\Regards,Gerard\'"", ""Comment 34: \'!image-2023-03-06-14-55-04-226.png!\'"", ""Comment 35: \'it works - thank you,\'"", ""Comment 36: \'!image-2023-03-13-13-29-39-553.png!\'"", \'Comment 37: ""select * from DHPlantProdBusinessLogicMain.dbo.Labels where ItemId in (\\\'E017E700-8694-4F78-8C3C-64CE79E8F713\\\',\\\'5A4BBFE2-1DE6-4C30-A3D4-0A649BDE7E1C\\\') and LanguageId = \\\'EA2B7C3F-6277-44A2-9143-B99AF97B34D2\\\'  select * from DHPlantProdBusinessLogicMain.dbo.Recipes where Id in (\\\'9C545083-6BE6-4B7A-91B4-C7C2215145A4\\\'\', \'Comment 38: \\\'972115A5-07A7-4E90-8681-D93C6BD5F44D\\\')""\', ""Comment 39: \'[^SPS_admin_13032023_141759677_40bf50b4-41e4-47f6-8358-5734b171a5e4.xml] [^SPS_admin_13032023_141759918_7b72a90c-9c0c-4a74-a571-c9eca251cb5b.xml] [^SPS_admin_13032023_141931502_f4ec70cf-9047-4c97-9155-87e6a6db8538.xml] [^SPS_admin_13032023_141931574_1e1ae686-d536-4587-bad4-8c3f45837575.xml]\'"", ""Comment 40: \'Hello,Right know the xml are generate with descriptions. In this case problem was with missing recipe version in VT module"", \'Comment 41: for that recipe and order version of labels 3 and 4 were used after resending them from dhc\', ""Comment 42: xml seems to be complete.BR\'"", ""Comment 43: \'May we close the task?\'"", ""Comment 44: \'Gooda afternoon Agnieszka,Thanks for support. You may close this ticket.Have a nice weekend.Kind regards,Gerard\']""]\nRelated Issues:\n[\'DGS-8609\']\n\n### End'}"
423,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8609\n\n### Instruction:\nGoodmorning,\r\n\r\nIn the xml file on DHP Veghel for Salesorder: SO000068853 there is missing some data. The product label information is missing.\r\nIt\'s important information for our customers.\r\n\r\nAs attachment hereby the xmldata that we recieved on DHP and the printscreen of the itemcode 303436 and label that belongs to this itemcode at DHP and DHC.\r\n\r\nPlease could you have a look at this problem?\r\nThis example is not the only one, at the moment,  I got more questions about this type of issue.\r\n\r\nKind regards,\r\n\r\nGerard\n\n### Response:\n[""Comment 1: [\'[^Afleverbon_ve_SO000068853_58B7D554-2FAC-4E47-B0B9-364B1D7C7914.xml] _(5 kB)_!DHC_Item_303436.PNG|thumbnail!!DHP_Item_303436.PNG|thumbnail!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Dla podanego przykładu brakuje sekcji dla nl<Field_Label> <Field_LabelProductionDate>15-02-2023</Field_LabelProductionDate> <Field_LabelExpirationDate>15-08-2023</Field_LabelExpirationDate> <Field_LabelReferenceCode>VE150223</Field_LabelReferenceCode> <Field_LabelPackingSize>0 KG</Field_LabelPackingSize> <Field_LabelLanguage>de</Field_LabelLanguage> </Field_Label>\'"", \'Comment 4: ""[~maciej.dobrzanski@kotrak.com]tego co widze dla towaru\\\'303436\\\' dla obu jezyków labalki saw module prod i pcs widzę że jakieś gdc na to będę wdzięczna jak zerknieszFROM [DHPlantMaintBusinessLogicMain].[dbo].[Labels] where id in ( \\\'B1D0A992-B3D3-451B-AB96-1DAAE5091080\\\'\', ""Comment 5: \'E4EAFCB0-7491-4B35-A779-35116DD03094\'"", ""Comment 6: \'9ED4AF5F-F559-4A40-A78C-3B62D6366C0E\'"", ""Comment 7: \'1A7858A2-530D-4041-B6CE-6CB0D2021B43\'"", ""Comment 8: \'6A032472-96C7-4CD9-997B-F51E49394236\'"", \'Comment 9: \\\'AA36CBD5-323B-4264-B74F-D58CF8AE85DC\\\')W logach nic nie widze.""\', \'Comment 10: ""select i.Code\', \'Comment 11: I.Name\', \'Comment 12: --\', \'Comment 13: r.Version\', \'Comment 14: r.Subversion,L.ProductDescription1 Label_ProductDescription1\', \'Comment 15: L.ProductDescription2 Label_ProductDescription2\', \'Comment 16: L.ProductDescription3 Label_ProductDescription3\', \'Comment 17: L.ProductType Label_ProductType--,l.Caution,,la.Value--,n.Code\', ""Comment 18: n.Name--,r.*--,l.FeedingGuide--,ltf.Translationfrom [DHPlantPCSBusinessLogicMain].[dbo].Recipes rjoin [DHPlantPCSBusinessLogicMain].[dbo].Items i on i.id = r.ItemIdjoin [DHPlantProdBusinessLogicMain].[dbo].Labels l on l.ItemId = r.ItemId and l.VersionNo=r.Version and r.PlantId = l.PlantIdjoin [DHPlantProdBusinessLogicMain].[dbo].Languages g on g.Id = l.LanguageId--left outer join [DHPlantProdBusinessLogicMain].[dbo].RecipeElements rn on rn.id=r.Id--left outer join [DHPlantProdBusinessLogicMain].[dbo].Items n on n.id=rn.ItemIdleft left outer join [DHPlantProdBusinessLogicMain].[dbo].LabelAdditionalTexts la on la.id=l.Id--left outer join [DHPlantProdBusinessLogicMain].[dbo].LabelNutrients ln on ln.id = l.Id--left outer join [DHPlantProdBusinessLogicMain].[dbo].LabelNutrientTypes lnt on lnt.Id=ln.LabelNutrientTypeId--left outer join [DHPlantProdBusinessLogicMain].[dbo].LabelWarnings lw on lw.Id=l.Id and lw.No=ln.No--left outer join [DHPlantProdBusinessLogicMain].[dbo].LabelTranslations lt on lt.LanguageId = g.Id --left outer join [DHPlantProdBusinessLogicMain].[dbo].LabelTranslationFields ltf on ltf.Id=lt.Id --and ltf.No=ln.No and ltf.LabelNutrientTypeId=ln.LabelNutrientTypeIdwhere 1=1--and r.Id=--and l.Id in (\'B1D0A992-B3D3-451B-AB96-1DAAE5091080\',\'E4EAFCB0-7491-4B35-A779-35116DD03094\',\'9ED4AF5F-F559-4A40-A78C-3B62D6366C0E\',\'1A7858A2-530D-4041-B6CE-6CB0D2021B43\',\'AA36CBD5-323B-4264-B74F-D58CF8AE85DC\',\'6A032472-96C7-4CD9-997B-F51E49394236\')--and i.Code = \'303436\'--and g.Code = \'NL\'order by r.Version desc"", \'Comment 19: Subversion desc--\', \'Comment 20: ln.Ordinal\', \'Comment 21: ln.No""\', ""Comment 22: \'!image-2023-02-23-15-00-11-800.png!\'"", \'Comment 23: ""select i.Code\', \'Comment 24: r.EntityId rc_EntityId\', \'Comment 25: r.Version\', \'Comment 26: r.Subversion --\', \'Comment 27: i.ItemBaseWeight--\', \'Comment 28: g.Code \', \'Comment 29: la.Value\', \'Comment 30: la.No\', \'Comment 31: la.Type\', \'Comment 32: la.LabelType\', \'Comment 33: la.Sequence\', \'Comment 34: ln.Name\', \'Comment 35: ln.Quantity\', \'Comment 36: ln.QuantityUnit,lnt.Name\', \'Comment 37: lnt.Type--\', \'Comment 38: ln.Description--,ln.No\', \'Comment 39: ln.IsHeader\', \'Comment 40: ln.Ordinal--\', \'Comment 41: lnt.*--,lnt.Name--,lw.Code\', \'Comment 42: lw.Description,,lt.Description,ltf.Translation --\', ""Comment 43: ltf.Idfrom [DHPlantPCSBusinessLogicMain].[dbo].Recipes rjoin [DHPlantPCSBusinessLogicMain].[dbo].Items i on i.id = r.ItemIdjoin [DHPlantProdBusinessLogicMain].[dbo].Labels l on l.ItemId = r.ItemId and l.VersionNo=r.Version and r.PlantId = l.PlantIdjoin [DHPlantProdBusinessLogicMain].[dbo].Languages g on g.Id = l.LanguageIdleft outer join [DHPlantProdBusinessLogicMain].[dbo].LabelNutrients ln on ln.id = l.Idleft outer join [DHPlantProdBusinessLogicMain].[dbo].LabelNutrientTypes lnt on lnt.Id=ln.LabelNutrientTypeId--left outer join [DHPlantProdBusinessLogicMain].[dbo].LabelWarnings lw on lw.Id=l.Id and lw.No=ln.No left outer join [DHPlantProdBusinessLogicMain].[dbo].LabelTranslations lt on lt.LanguageId = g.Id left outer join [DHPlantProdBusinessLogicMain].[dbo].LabelTranslationFields ltf on ltf.Id=lt.Id and ltf.LabelNutrientTypeId=ln.LabelNutrientTypeId--and ltf.No=ln.No where 1=1and ln.No > 0aND ln.IsHeader = 0and r.Id in (\'27772437-0268-4B71-A960-A943934FB1B5\')--,\'9274CACB-B6D2-4603-BB2B-75BFFF335BAB\',\'DC3E0094-694A-4019-8726-73BFB4505B40\',----\'D16DF237-8B1F-47E0-A33C-422CF89826FA\',\'E9A39A85-600E-45EF-A6F6-396DE48BD141\')and--and l.Id=and i.Code = \'303436\'and g.Code = \'DE\'order by r.Version desc"", \'Comment 44: Subversion desc \', \'Comment 45: lnt.Type\', \'Comment 46: ln.Ordinal""\', \'Comment 47: ""na bazie jestselect i.Code\', \'Comment 48: r.EntityId rc_EntityId\', \'Comment 49: r.Version\', \'Comment 50: r.Subversion ,--\', \'Comment 51: i.ItemBaseWeight\', \'Comment 52: g.Code ,-- la.Value\', \'Comment 53: la.No\', \'Comment 54: la.Type\', \'Comment 55: la.LabelType\', \'Comment 56: la.Sequence\', \'Comment 57: ln.Name\', \'Comment 58: ln.Quantity\', \'Comment 59: ln.QuantityUnit,lnt.Name\', \'Comment 60: lnt.Type--\', \'Comment 61: ln.Description--,ln.No\', \'Comment 62: ln.IsHeader\', \'Comment 63: ln.Ordinal--\', \'Comment 64: lnt.*--,lnt.Name--,lw.Code\', \'Comment 65: lw.Description,,lt.Description,ltf.Translation --\', ""Comment 66: ltf.Idfrom [DHPlantPCSBusinessLogicMain].[dbo].Recipes rjoin [DHPlantPCSBusinessLogicMain].[dbo].Items i on i.id = r.ItemIdjoin [DHPlantProdBusinessLogicMain].[dbo].Labels l on l.ItemId = r.ItemId and l.VersionNo=r.Version and r.PlantId = l.PlantIdjoin [DHPlantProdBusinessLogicMain].[dbo].Languages g on g.Id = l.LanguageIdleft outer join [DHPlantProdBusinessLogicMain].[dbo].LabelNutrients ln on ln.id = l.Idleft outer join [DHPlantProdBusinessLogicMain].[dbo].LabelNutrientTypes lnt on lnt.Id=ln.LabelNutrientTypeId--left outer join [DHPlantProdBusinessLogicMain].[dbo].LabelWarnings lw on lw.Id=l.Id and lw.No=ln.No left outer join [DHPlantProdBusinessLogicMain].[dbo].LabelTranslations lt on lt.LanguageId = g.Id left outer join [DHPlantProdBusinessLogicMain].[dbo].LabelTranslationFields ltf on ltf.Id=lt.Id and ltf.LabelNutrientTypeId=ln.LabelNutrientTypeId--and ltf.No=ln.No where 1=1and ln.No > 0aND ln.IsHeader = 0and r.Id in (\'27772437-0268-4B71-A960-A943934FB1B5\')--,\'9274CACB-B6D2-4603-BB2B-75BFFF335BAB\',\'DC3E0094-694A-4019-8726-73BFB4505B40\',----\'D16DF237-8B1F-47E0-A33C-422CF89826FA\',\'E9A39A85-600E-45EF-A6F6-396DE48BD141\')and--and l.Id=and i.Code = \'303436\'and g.Code = \'DE\'order by r.Version desc"", \'Comment 67: Subversion desc \', \'Comment 68: lnt.Type\', \'Comment 69: ln.Ordinal""\', ""Comment 70: \'!image-2023-02-23-15-28-58-028.png!\'"", ""Comment 71: \'[~maciej.dobrzanski@kotrak.com]od dla podanego przykładu zwraca wyniki ( select drugi)konfig się zgadza!image-2023-02-23-15-38-30-748.png!\'"", ""Comment 72: \'[~tomasz.kozmin@kotrak.com] poprozmawia z [~dominik.lorke@kotrak.com] jak można to zdebugować\'"", \'Comment 73: ""select ii.Code as itemcode\', \'Comment 74: o.DocumentNumber as salesordernumber\', \'Comment 75: o.ForeignDocument\', \'Comment 76: bp.Code as customercode\', \'Comment 77: e.No as linenumber\', ""Comment 78: (select top 1 r.EntityId rc_EntityIdfrom [DHPlantPcsBusinessLogicMain].[dbo].Recipes rjoin [DHPlantPcsBusinessLogicMain].[dbo].Items i on i.id = r.ItemIdjoin [DHPlantProdBusinessLogicMain].[dbo].Labels l on l.ItemId = r.ItemId and l.VersionNo=r.Version and r.PlantId = l.PlantIdjoin [DHPlantProdBusinessLogicMain].[dbo].Languages g on g.Id = l.LanguageIdwhere 1=1and i.id = ii.idand g.Code = \'DE\'order by r.Version desc"", \'Comment 79: Subversion desc) as recipeidfrom [DHPlantPcsBusinessLogicMain].dbo.Orders oinner join dbo.OrderElements e on e.id = o.idinner join dbo.items ii on ii.id = e.itemidinner join [DHPlantPcsBusinessLogicMain].dbo.BusinessPartners bp on bp.Id = o.TargetBusinessPartnerIdwhere o.ForeignDocument = \\\'SO000068853\\\'and ii.code = \\\'303436\\\'select * from [DHPlantPcsBusinessLogicMain].[dbo].Recipes where EntityId=55051select * from labels where itemid=\\\'2BA9DE6F-A5D0-41E6-882F-C2ED8D1DE942\\\' and VersionNo=348""\', ""Comment 80: \'[^SPS_admin_24022023_093103852_f862e1be-81de-4d99-b748-60822d573275.xml]\'"", \'Comment 81: ""wywgenerowany wydruk do folderu test \', \'Comment 82: ( vt 695)select * from Orders where ForeignDocumentNumber=\\\'SO000068853\\\'select top 10 * from VehicleTickets where id=\\\'FCA3DDA3-5F45-4B6B-AD1D-EFA42F468815\\\'select * from items where code =\\\'303436\\\'[^SPS_admin_24022023_093103852_f862e1be-81de-4d99-b748-60822d573275.xml]^osttania label i recipe doa tego itemu to aktualnie wersja 348^^recipeid r.Id=\\\'164BD6FE-FB6A-498C-9FCC-F9FFE274F93C^^wynik zwraca elementy^w xml jest tak!image-2023-02-24-09-39-03-794.png!""\', \'Comment 83: ""receptura na elemencie vt jest na inny itemselect * from Orders where ForeignDocumentNumber=\\\'SO000068853\\\'select top 10 * from VehicleTickets where id=\\\'FCA3DDA3-5F45-4B6B-AD1D-EFA42F468815\\\'select * from items where code =\\\'303436\\\'select RecipeId,* from VehicleTicketBulkDispatchElements where ItemId=\\\'2BA9DE6F-A5D0-41E6-882F-C2ED8D1DE942\\\' and OrderId=\\\'38B4566B-0765-4704-B733-65B707CB6FB5\\\'!image-2023-02-24-09-49-16-990.png!""\', ""Comment 84: \'[~maciej.dobrzanski@kotrak.com]ok więc dla podanego VT 695 jest z niewiadomych przyczyn użyta receptura na inny towar ( screeny powyzej) i wtedy nie ma takiej labelki:!image-2023-02-24-09-57-24-242.png!\'"", \'Comment 85: ""na szybko select na vt bulk elementy gdzie item z recipe id jest inne niż na vte.jest 64 takich receptur z 2023 rokuselect distinct(RecipeId),i2.code as itemforVT\', \'Comment 86: i.code as itemforrecipe from VehicleTicketBulkDispatchElements vte join [DHPlantProdBusinessLogicMain].[dbo].recipes r on vte.RecipeId=r.Id join Items i on i.id= r.ItemId join items i2 on i2.id=vte.ItemIdwhere vte.ItemId<>r.ItemId and r.ImportDate>\\\'2023-01-01 01:02:00.3918811\\\'""\', \'Comment 87: ""podmiana receptury na vt 695--update VehicleTicketBulkDispatchElements --set RecipeId=\\\'164BD6FE-FB6A-498C-9FCC-F9FFE274F93C\\\'--where ItemId=\\\'2BA9DE6F-A5D0-41E6-882F-C2ED8D1DE942\\\' --and OrderId=\\\'38B4566B-0765-4704-B733-65B707CB6FB5\\\'-- recipe na inny item-- 8FC6DDFB-D79A-4F03-88F0-65F41AC40743""\', ""Comment 88: \'[^SPS_admin_24022023_114702900_ffa731c1-ecfe-4371-bc33-be1e017001cf-1.xml]\'"", \'Comment 89: ""[^SPS_admin_24022023_114702900_ffa731c1-ecfe-4371-bc33-be1e017001cf.xml]HelloWe analyzed the problem and it appears that for some VT items is assigned from pcs recipe to another item. Therefore\', ""Comment 90: the system does not retrieve information to the label in the case of order SO000068853 was assigned a recipe for the item 303641 and SO and VT refer to the item with the code 303436\'"", \'Comment 91: we can see that for 303436 such Vt is more. For the order of the item VT 695 we changed the recipe to the last one for the commodity 303436 and on the printout you can see the data about the label( attached xml). In this situation\', \'Comment 92: on the remaining reported in this and related shuffle\', \'Comment 93: do we change it recipe to VT?I also ask for verification on the pcs side\', \'Comment 94: as it is pcs that sends the information in RECIPE!image-2023-02-24-12-00-07-320.png!""\', ""Comment 95: \'[https://kotrak.sharepoint.com/sites/erpasysta/_layouts/OneNote.aspx?id=%2Fsites%2Ferpasysta%2FShared%20Documents%2FBaza%20wiedzy%2FBaza%20Wiedzy%20-%20ERPSD&wd=target%28Klienci%2FDEHEUS%2FDEHEUS%20APPLICATIONS%2FHolandia%20Premix%20i%20AS400%2FBaz%20wiedzy%20z%20AS400.one%7C9BB564BA-0B58-4580-B9E0-F3CF9D6D80A7%2F%5BDHP%203.0%5D%20XML%20WERYFIKACJA%20WYDRUKU%20SPS%20SalesPackingSlip%7C2057108A-87BD-422C-84FB-79682EEDF1C9%2F%29]\'"", \'Comment 96: ""In Additional technologies I could not find it\', \'Comment 97: but at the time of the order\', \'Comment 98: there must have been an additional technology for this item:In order SO000068853 (SO-6269/2/23) the item 303436 was ordered (ItemCodeCustomer) but item 303641 was send to produce. See attached json for sales order to PCSTrip 00976953 was assigned. It contains 3 orders\', ""Comment 99: all for the same item. I found that PCS message for the dispatch message of this trip contained two different recipeId\'s for those three orders. See attached json from PCS. In case the plant produces and load another code then was ordered"", \'Comment 100: in the dispatch we expect the code that was ordered by the customer (303436) and the recipeId of the code that was produced (e.g. recipeId of 303641). This is as designed for derived items because the plant does not have a recipe for the item that was ordered.[^20230313_trip_00976953_from_PCS.json] _(1 kB)_""\', ""Comment 101: \'Attachement order sent to PCS[^20230313_order_SO000068853_to_PCS.json] _(4 kB)_\'"", ""Comment 102: \'Info od Tomka Koźmina:Tu by się przydało napisać takie spore zapytanie parametryzowane np. po numerze SO # co wpadło do DHC # co przeleciało do DHP # co poleciało do PCS # co zostało wyprodukowane # co poleciało spakowane - jeśli było # co poleciało na wydruki (baglabel i SPS) # co było na VTi to wszystko ze wskazaniem ItemCode"", \'Comment 103: ItemCodeCustomer\', \'Comment 104: RecipeID\', \'Comment 105: RecipeVersion\', \'Comment 106: etc.napisać raz\', ""Comment 107: udostępnić im jako raportin niech sami sobie to śledzą\'"", \'Comment 108: \\\'Hello  The original content of the task wasIn the xml file on DHP Veghel for Salesorder: SO000068853 there is missing some data. The product label information is missing. It\\\\\\\'s important information for our customers.As attachment hereby the xmldata that we recieved on DHP and the printscreen of the itemcode 303436 and label that belongs to this itemcode at DHP and DHC.And you send as xml and sreenshot where for that SO was a problem in that area of that printout : Field_LabelContents.!image-2023-02-24-09-39-03-794.png!We analyzed the code and procedure that generates these printouts.We see that what I response to you at 24,02.2023 that there are diffrent recipes and item in related objects in dhp,and send you an XML to verifyAnd then in your response at 13.03You are not bringing information about this XML printout if the description is correct:If yes may we close this task ?If not were it isincorrect?Your response to be about different topics more about this 2 ""problematic"" items.As I can see in Jira Both of this codes have some historyhttps://helpdesk.kotrak.com/browse/DGS-8196here we had situation were ""An additional technology VE303436 was created on 12 December for derived item 303436. Code to produce is 303641.\\\\\\\'as solution AT was removed \', \'Comment 109: AT was removed also here and product definition flag has been changed:https://helpdesk.kotrak.com/browse/DGS-8125,https://helpdesk.kotrak.com/browse/DGS-8127 And here where Bartłomiej and Przemek verify that codes and recipes again:https://helpdesk.kotrak.com/browse/DGS-8735So if there is a need to analyze recipes and codes in a given period of time for a specific commodity code\', \'Comment 110: please create a new Task. However\', ""Comment 111: if at this point AT has been deleted it may be very difficult due to the lack of key data.Could you please provide another task for that or you prefer to create an RCA in that matter?We could also create you some kind of useful procedure/report from database that will show youwhat was in the DHCwhat was sent to DHPwhat was sent to PCSwhat was producedwhat was bagged - (if any)what was printed (baglabel and SPS)what was on VTif you are interested in this type of report please create a SR ticket.\'"", ""Comment 112: \'Hello Agnieszka"", ""Comment 113: this ticket can be closed.\']""]\nRelated Issues:\n[\'DGS-8610\']\n\n### End'}"
424,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8608\n\n### Instruction:\nOrder SO000073172 is in DHC but is not arriving in DHP. In the communication log a deadlock is mentioned. \r\nCan you please help as this customer needs their feed tomorrow morning. \r\n\r\n\r\n\r\nOrderChangedMessage: Id=11c8b8c8-9110-4be2-9112-7d402edf8a8b DocumentNo=\'SO000073172\' DocNumeratorYear=2023 DocNumeratorMonth=2 DocNumeratorNumber=10498 DocNumeratorSeries= OrderType=2\r\nTransaction (Process ID 147) was deadlocked on lock | communication buffer resources with another process and has been chosen as the deadlock victim. Rerun the transaction\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Thank you Monika. It is quite urgent\'"", ""Comment 3: \'already some news? our planners have to plan this order and the factory needs to produce it... \'"", ""Comment 4: \'still under analysis\'"", ""Comment 5: \'has it something to do with the different recipe subversions?\'"", ""Comment 6: \'The reason is full queues  !screenshot-1! we need to wait until all messages will be overprocessed.\'"", ""Comment 7: \'we have some queries where we can prioritize the orders and shipping notes over recipes and labels\'"", ""Comment 8: \'did you make any scripts? couse some of queues are missing  !screenshot-2! \'"", \'Comment 9: ""No\', \'Comment 10: didn\\\'t make any script or something""\', ""Comment 11: \'status shouldnt be waiting for customer since i have replied ;)\'"", \'Comment 12: \\\'could you send me query that you mentioned here?""we have some queries where we can prioritize the orders and shipping notes over recipes and labels""\\\'\', \'Comment 13: ""Yes\', \'Comment 14: we have got this script from Przemek:--READ FIRST BEFORE USE OF THIS SCRIPT --STEP 1: On DHVD01AP174\', \'Comment 15: open the BusinessPlatform Management Console--STEP 2: Stop Evolution.DHCService.PlatformApplication service--STEP 3: After executing the script below\', ""Comment 16: start the Evolution.DHCService.PlatformApplication service againUSE Evolution_Messagingbegin trantruncate table dhcservice_tmpinsert into dhcservice_tmpSELECT * FROM DHCService D WITH (NOLOCK)where D.Body  like \'%RecipeChangedMessage%\'or D.Body  like \'%ProductionRecipeChangedMessage%\'or D.Body  like \'%TechnologyChangedMessage%\'or D.Body  like \'%LabelChangedMessage%\'delete D FROM DHCService Djoin dhcservice_tmp DS on DS.id= D.IdINSERT INTO [dbo].[DHCService]([Id],[CorrelationId],[ReplyToAddress],[Recoverable],[Expires],[Headers],[Body])select [Id],[CorrelationId],[ReplyToAddress],[Recoverable],[Expires],[Headers],[Body]  from dhcservice_tmporder by  charindex(\'.RecipeChangedMessage\'"", ""Comment 17: Headers) desc,charindex(\'.ProductionRecipeChangedMessage\'"", ""Comment 18: Headers) desc,charindex(\'.TechnologyChangedMessage\'"", ""Comment 19: Headers) desc,charindex(\'.LabelChangedMessage\'"", \'Comment 20: Headers) desccommit -- Now perform STEP 3.""\', \'Comment 21: ""RecipeChangedMessage\', \'Comment 22: ProductionRecipeChangedMessage\', \'Comment 23: TechnologyChangedMessage and LabelChangedMessage ane exacly wchich are dissapeared from queues. Please make restart of server 172.23.1.67. As I can see queues withiout RecipeChangedMessage\', \'Comment 24: ProductionRecipeChangedMessage\', \'Comment 25: TechnologyChangedMessage and LabelChangedMessage not decreasing anymore. If restart doesn\\\'t helps we need to disquss this issue with our dev team tommorow morning""\', \'Comment 26: ""Hi Monika\', \'Comment 27: I cannot restart this server as I don\\\'t have access to it... we have to pick it up tomorrow morning. Thanks for your help anyway""\', ""Comment 28: \' !screenshot-3! \'"", ""Comment 29: \'solved. Wijnand potwierdził ze teraz im działą\'"", ""Comment 30: \'Queues should decrease now. We need to wait until all messages will be overprocessed.\'"", ""Comment 31: \'All messages are processed. Please close the ticket. \'"", ""Comment 32: \'Thank you\']""]\nRelated Issues:\n[\'DGS-8611\']\n\n### End'}"
425,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8607\n\n### Instruction:\nLike to award relevant sector article\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 3: ""Hello,This field on Item Card is filled in when item is sent from Milas and is not editable right now in Intense.Is it wrong value for this item? Why it\\\'s needed to change this value?Generally it\\\'s important for items with ItemGroup = \\\'Raw Material\\\' or \\\'Finish product\\\' which are on Feed sale documents. It\\\'s possible to set this value on Feed sale element manually also in those cases.!image-2023-02-23-09-29-28-915.png!Regards""\', ""Comment 4: \'Hi Damian"", ""Comment 5: Bert would like to add this item to some different sectors. Bert could you give us the item code you refer to and also the sector in which it should be visible?\'"", ""Comment 6: \'I&RR should be made available to the NAS as wel. Could you do it?\'"", \'Comment 7: ""I\\\'ve marked NAS in Relevant sectors\', \'Comment 8: is it correct right now?!image-2023-02-23-15-22-03-027.png!""\', ""Comment 9: \'No"", \'Comment 10: it should be marked in het multisector as well.  I don’t think we can do it ourselves.     *Van:* Damian Świstek (Jira) <jira@kotrak.com>   *Verzonden:* donderdag 23 februari 2023 15:24  *Aan:* Bovene\', ""Comment 11: Mitch van <mbovene@deheus.com>  *Onderwerp:* DGS-8607 Artikel toekennen sector   !image001!\'"", ""Comment 12: \'Confirmed that is correct right now.\']""]\nRelated Issues:\n[]\n\n### End'}"
426,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8606\n\n### Instruction:\nProszę o poprawienie na karcie środków trwałych z listy poniżej współczynnika amortyzacji podatkowej, powinno być 1/1.\r\n\r\nJednocześnie prośba o poprawienie na wszystkich wygenerowanych dokumentach amortyzacji prawidłowych wartości miesięcznych.\n\n### Response:\n[""Comment 1: [\'!image![^Lista.xlsx] _(11 kB)_\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 3: ""Values on fixed assets has been corrected. Documents are already posted. Do you want to correct tax values on posted documents. This change shouldn\\\'t change postings?""\', ""Comment 4: \'Odp od usera:Amortyzację księgujemy wg wartości bilansowej.Podatkowa jest do skorygowania. \'"", ""Comment 5: \'Values has been corrected on documents. PLease verify \'"", ""Comment 6: \'Changes are correct - task to close - thanks for help.\']""]\nRelated Issues:\n[]\n\n### End'}"
427,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8605\n\n### Instruction:\nHello,\r\n\r\nsee attached screenshot, for IO000000898 and IO000001300 we cannot create VT: We get a unexpected error: Can you please check and solve this?\n\n### Response:\n[""Comment 1: [\'!afbeelding!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'{code:java}   at Kotrak.Integration.IntegrationPluginCommon.IntercontextCommunication.Inbound.IntercontextInboundHandler`2.Handle(InternalStorageDto message)2023-02-22 15:14:23 (142612de-f30e-487f-8dd1-3a629d76faf0/Plant.VC.BusinessLogic/DHVD01AP180/28812/219) [Error] Kotrak.Common.Infrastructure.ICommandRunEnvironment - Error during Void Run[CreateVehicleTicketFromShippingNoticeCommand](Plant.VC.BusinessLogic.Application.Interfaces.VehicleTickets.Commands.CreateVehicleTicketFromShippingNoticeCommand) methodAutoMapper.AutoMapperMappingException: Error mapping types.Mapping types:ShippingNoticeEntity -> ShippingNoticePlant.VC.BusinessLogic.Infrastructure.Persistance.ShippingNotices.ShippingNoticeEntity -> Plant.VC.BusinessLogic.Domain.ShippingNotices.ShippingNoticeType Map configuration:ShippingNoticeEntity -> ShippingNoticePlant.VC.BusinessLogic.Infrastructure.Persistance.ShippingNotices.ShippingNoticeEntity -> Plant.VC.BusinessLogic.Domain.ShippingNotices.ShippingNoticeDestination Member:Elements ---> AutoMapper.AutoMapperMappingException: Error mapping types.Mapping types:ShippingNoticeElementEntity -> ShippingNoticeElementPlant.VC.BusinessLogic.Infrastructure.Persistance.ShippingNotices.ShippingNoticeElementEntity -> Plant.VC.BusinessLogic.Domain.ShippingNotices.ShippingNoticeElementType Map configuration:ShippingNoticeElementEntity -> ShippingNoticeElementPlant.VC.BusinessLogic.Infrastructure.Persistance.ShippingNotices.ShippingNoticeElementEntity -> Plant.VC.BusinessLogic.Domain.ShippingNotices.ShippingNoticeElementDestination Member:PackingForm ---> System.ApplicationException: \\\\\'4\\\\\' is not a valid value in Plant.VC.BusinessLogic.Domain.ShippingNotices.Enumerations.ShippingNoticePackingForm   at Kotrak.Common.SharedKernel.Enumeration.Parse[T,K](K value"", \'Comment 4: String description\', \'Comment 5: Func`2 predicate)   at lambda_method7355(Closure \', \'Comment 6: ShippingNoticeEntity \', \'Comment 7: ShippingNotice \', \'Comment 8: ResolutionContext )   --- End of inner exception stack trace ---   at lambda_method7355(Closure \', \'Comment 9: ShippingNoticeEntity \', \'Comment 10: ShippingNotice \', \'Comment 11: ResolutionContext )   --- End of inner exception stack trace ---   at lambda_method7355(Closure \', \'Comment 12: ShippingNoticeEntity \', \'Comment 13: ShippingNotice \', \'Comment 14: ResolutionContext )   at lambda_method7357(Closure \', \'Comment 15: Object \', \'Comment 16: Object \', \'Comment 17: ResolutionContext )   at Kotrak.Extensions.Mapping.CompositeMapper.Mapper.Execute(Object source\', \'Comment 18: Object destination\', \'Comment 19: ICustomInjection[] customInjections\', \'Comment 20: Type sourceType\', \'Comment 21: Type targetType)   at Kotrak.Extensions.Mapping.CompositeMapper.Mapper.Map[TSource,TTarget](TSource source\', \'Comment 22: TTarget destination)   at Kotrak.Common.Infrastructure.Repositories.AggregateRootRepository`2.GetForEntity(TEntity entity)   at Kotrak.Common.Infrastructure.Repositories.AggregateRootRepository`2.Get(AggregateId id)   at Plant.VC.BusinessLogic.Application.VehicleTickets.Services.VehicleTicketService.CreateVehicleTicketFromShippingNotice(AggregateId vehicleTicketId\', \'Comment 23: AggregateId shippingNoticeId\', \'Comment 24: Boolean isPlanned) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\67ba263564c33499\\\\\\\\Plant.VC.BusinessLogic\\\\\\\\Plant.VC.BusinessLogic.Application\\\\\\\\VehicleTickets\\\\\\\\Services\\\\\\\\VehicleTicketService.cs:line 485   at Plant.VC.BusinessLogic.Application.VehicleTickets.CommandHandlers.CreateVehicleTicketFromShippingNoticeCommandHandler.Handle(CreateVehicleTicketFromShippingNoticeCommand command) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\67ba263564c33499\\\\\\\\Plant.VC.BusinessLogic\\\\\\\\Plant.VC.BusinessLogic.Application\\\\\\\\VehicleTickets\\\\\\\\CommandHandlers\\\\\\\\CreateVehicleTicketFromShippingNoticeCommandHandler.cs:line 21   at Kotrak.Common.Infrastructure.Commands.CommandEnvironment.Run[TCommand](TCommand command)   at Kotrak.Common.Infrastructure.Commands.Decorators.IntercontextEventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command)   at Kotrak.Common.Infrastructure.Commands.Decorators.EventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command)   at Kotrak.Common.Infrastructure.Commands.Decorators.ValidationCommandEnvironmentDecorator.Run[TCommand](TCommand command)   at Castle.DynamicProxy.AbstractInvocation.Proceed()   at Kotrak.Common.Infrastructure.Interceptors.LoggingInterceptor`1.Intercept(IInvocation invocation)2023-02-22 15:14:23 (/Plant.VC.BusinessLogic/DHVD01AP180/28812/248) [Error] Serilog.AspNetCore.RequestLoggingMiddleware - HTTP ""POST"" ""/api/VehicleTicket/createVehicleTicketFromShippingNotice"" responded 500 in 35.1744 ms{code}\\\'\', ""Comment 25: \'!image-2023-02-22-15-30-09-525.png!\'"", \'Comment 26: ""{code:java}select * FROM [DHPlantVCBusinessLogicMain].[dbo].[ShippingNotices] where Description like \\\'IO000000898\\\'  --select * FROM [DHPlantVCBusinessLogicMain].[dbo].[ShippingNoticeElements] where id = \\\'8B88312E-6842-4DBA-81F2-CD20A056C81A\\\'  --select * from [DHPlantVCBusinessLogicMain].[dbo].[Items] where code in (\\\'0162\\\',\\\'085618\\\',\\\'088107\\\')  select QuantityOnHandUnit,QuantityUnit,* from [DHPlantStockBusinessLogicMain].[dbo].[StockUnits]where ItemId in   (\\\'9CFC6B85-5D4D-4CF7-A0AE-F6A35F991D81\\\',\\\'B17CA009-71F1-4BBF-9700-3AFD4F7C30EC\\\',\\\'284304DA-527D-4EBA-A0C9-BDA28D293670\\\'){code}""\', ""Comment 27: \'6D805791-EE4B-41C6-A491-C334F19D74DC kgA82B6B8C-7331-4D81-8E19-80DCFDEC0999 pcs1DDADA9D-F221-4BD8-948D-4227CE6ECD4F pcs\'"", ""Comment 28: \'Zmiana PackingForm na 3 !image-2023-02-23-11-10-47-304.png!\'"", ""Comment 29: \'Hello Thomas"", \'Comment 30:  I have made a correction to the documents\', ""Comment 31:  IO000000898 and IO000001300  Causes in problems correct Description element  Please Verify  Regards,\'"", ""Comment 32: \'!image-2023-02-23-11-41-40-583.png!\'"", ""Comment 33: \'[[DHC 3.0] Item settlement type - related with VT. Destination site.|onenote:https://kotrak.sharepoint.com/sites/erpasysta/Shared%20Documents/Baza%20wiedzy/Baza%20Wiedzy%20-%20ERPSD/Klienci/DEHEUS/DEHEUS%20APPLICATIONS/Brazil/Baza%20wiedzy.one#%5bDHC%203.0%5d%20Item%20settlement%20type%20-%20related%20with&section-id=\\\\\\\\{05DF1439-683C-45FE-8260-61E2EC66DC91}&page-id=\\\\\\\\{76E90592-C95A-48F3-888C-4CBC948085DA}&end] ([Widok sieci Web|https://kotrak.sharepoint.com/sites/erpasysta/_layouts/OneNote.aspx?id=%2Fsites%2Ferpasysta%2FShared%20Documents%2FBaza%20wiedzy%2FBaza%20Wiedzy%20-%20ERPSD&wd=target%28Klienci%2FDEHEUS%2FDEHEUS%20APPLICATIONS%2FBrazil%2FBaza%20wiedzy.one%7C05DF1439-683C-45FE-8260-61E2EC66DC91%2F%5BDHC%203.0%5D%20Item%20settlement%20type%20-%20related%20with%7C76E90592-C95A-48F3-888C-4CBC948085DA%2F%29])\'"", ""Comment 34: \'ticket can be closed\']""]\nRelated Issues:\n[]\n\n### End'}"
428,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8604\n\n### Instruction:\nHello, can you please confirm PLR 0061020123050 in DHP Nijkerk? I get an unexpected error when I try to close it\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Is0061020123050 i correct number I do not see it in Nijerk"", ""Comment 3: could you also provide dates? !image-2023-02-22-15-22-34-536.png!\'"", \'Comment 4: ""it\\\'s there; if you search on active lot reports!afbeelding!""\', ""Comment 5: \'id=9748873a-889c-4c71-a467-94adaa3bf9b6 plr\'"", \'Comment 6: \\\'2023-02-22 15:46:33 (7fcb2146-9348-4fe0-881a-1b0182cbee63/Plant.Prod.BusinessLogic/DHVD01AP181/36416/57) [Error] Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware - Error during request{ ""scheme"": ""http""\', \'Comment 7: ""host"": { ""Value"": ""dhvd01ap181:83""\', \'Comment 8: ""HasValue"": true\', \'Comment 9: ""Host"": ""dhvd01ap181""\', \'Comment 10: ""Port"": 83 }\', \'Comment 11: ""path"": ""/api/productionLot/update""\', \'Comment 12: ""queryString"": []\', \'Comment 13: ""requestBody"": ""\\\\\\\\{\\\\\\\\""elements\\\\\\\\"":[{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":1,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""63fdb7ab-555d-419c-a8e4-f01a8e1ad96b\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":1448.3}},\\\\\\\\{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":2,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""ffe4c116-7723-46b5-a79b-a59a58943c32\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":69.176}},\\\\\\\\{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":3,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""871567c3-6a50-41c7-929f-5c23e683bcf7\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":12674.9}},\\\\\\\\{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":4,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""4b0c15ce-e19c-4223-b952-088f8c8c219d\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":776}},\\\\\\\\{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":5,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""f772c49d-1380-409c-bffe-71dd5df71fcc\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":22.3}},\\\\\\\\{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":6,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""3a6641d9-3287-4e54-9ddb-8978755f01e7\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":89.169}},\\\\\\\\{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":7,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""a77f17e1-76b7-4d1c-ba81-29d0f37d791d\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":82.549}},\\\\\\\\{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":8,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""ff864766-d77e-469a-a8e3-35956c46e9e0\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":376.4}},\\\\\\\\{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":9,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""157bddce-f0e1-4098-8718-479970100780\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":1107.296}},\\\\\\\\{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":10,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""dc713a02-689e-4549-a4d0-d0eb5252168b\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":104.765}},\\\\\\\\{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":11,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""d4bcb839-3d48-4346-ac48-391eb118096c\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":116.4}},\\\\\\\\{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":12,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""b0968ca7-eb58-4a22-911a-3a05d77c140e\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":68.53}},\\\\\\\\{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":13,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""449b8b7e-a2bd-48e6-8dd8-10347cf3a7eb\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":44.359}},\\\\\\\\{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":14,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""622189a3-8f08-4ad2-b9ad-907dbc641181\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":42.384}},\\\\\\\\{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":15,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""dc600dc2-416b-4ee2-85fc-2d9192812beb\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":320.339}},\\\\\\\\{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":16,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""25fe5b28-5b2e-4b20-86c4-f83293e2c37b\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":423.5}},\\\\\\\\{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":17,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""d162fa0a-5020-4451-ab73-5c7f9974db62\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":4541.801}},\\\\\\\\{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":18,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""eda1d707-8c10-475d-a7da-c2696ebf7890\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":4230.4}},\\\\\\\\{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":19,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""09be2508-e5cd-45b3-bce5-aa9ade358df2\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":1671.7}},\\\\\\\\{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":20,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""dc600dc2-416b-4ee2-85fc-2d9192812beb\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":3805.612}}],\\\\\\\\""executions\\\\\\\\"":[\\\\\\\\{\\\\\\\\""elements\\\\\\\\"":[],\\\\\\\\""readyProductId\\\\\\\\"":\\\\\\\\""406a617a-c70d-41d7-994b-b885a3cd6d9b\\\\\\\\"",\\\\\\\\""packingRecipeId\\\\\\\\"":null,\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":32015.887},\\\\\\\\""requestedQuantity\\\\\\\\"":\\\\\\\\{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":32015.887},\\\\\\\\""expiryDate\\\\\\\\"":\\\\\\\\""2023-04-02T20:31:07.660Z\\\\\\\\""}],\\\\\\\\""reservations\\\\\\\\"":[],\\\\\\\\""productionLotId\\\\\\\\"":\\\\\\\\""9748873a-889c-4c71-a467-94adaa3bf9b6\\\\\\\\"",\\\\\\\\""recipeId\\\\\\\\"":\\\\\\\\""019e2b35-bf9f-440f-8852-ca6202061b97\\\\\\\\"",\\\\\\\\""labelId\\\\\\\\"":null,\\\\\\\\""shiftNumberId\\\\\\\\"":null,\\\\\\\\""statusChange\\\\\\\\"":2}""}.System.AggregateException: One or more errors occurred. (Response status code does not indicate success: 400 (Bad Request).) ---> Refit.ApiException: Response status code does not indicate success: 400 (Bad Request).\\\'\', ""Comment 14: \'2023-02-22 15:46:33 (7fcb2146-9348-4fe0-881a-1b0182cbee63/Plant.Prod.BusinessLogic/DHVD01AP181/36416/57) [Error] Kotrak.Common.Infrastructure.ICommandRunEnvironment - Error during Void Run[UpdateProductionLotCommand](Plant.Prod.BusinessLogic.Application.Interfaces.ProductionLots.Commands.UpdateProductionLotCommand) methodSystem.AggregateException: One or more errors occurred. (Response status code does not indicate success: 400 (Bad Request).) ---> Refit.ApiException: Response status code does not indicate success: 400 (Bad Request). at Refit.RequestBuilderImplementation.<>c__DisplayClass14_0`2.<<BuildCancellableTaskFuncForMethod>b__0>d.MoveNext() in /_/Refit/RequestBuilderImplementation.cs:line 313 --- End of inner exception stack trace ---\'"", \'Comment 15: \\\'brakuje lota w module stock :2023-02-22 15:46:33 (7fcb2146-9348-4fe0-881a-1b0182cbee63/Plant.Stock.BusinessLogic/DHVD01AP181/37340/307) [Error] Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware - Error during request{ ""scheme"": ""http""\', \'Comment 16: ""host"": { ""Value"": ""dhvd01ap181:92""\', \'Comment 17: ""HasValue"": true\', \'Comment 18: ""Host"": ""dhvd01ap181""\', \'Comment 19: ""Port"": 92 }\', \'Comment 20: ""path"": ""/api/productionLot/updateReservationsAndConfirm""\', \'Comment 21: ""queryString"": [],Kotrak.Common.Application.Exceptions.BusinessLogicException: Production lot with id *9748873a-889c-4c71-a467-94adaa3bf9b6 was not found*\\\'\', ""Comment 22: \'!image-2023-02-22-18-16-47-852.png!\'"", ""Comment 23: \'Przesłałam eventy dotycząceutworzenia/aktualizacji production lota do modułu stock"", \'Comment 24: resent successfully\', ""Comment 25: ale nie wpada. Trza było popchać rabbitem!image-2023-02-22-18-33-38-681.png! !image-2023-02-22-18-33-38-681!\'"", ""Comment 26: \'Hi Thomas,Production lot is now confirmed. Please"", ""Comment 27: verify.!image-2023-02-22-19-20-59-840.png!Regards\'"", ""Comment 28: \'Thanks! ticket can be closed\']""]\nRelated Issues:\n[\'DGS-8686\']\n\n### End'}"
429,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8603\n\n### Instruction:\nHello,\r\n\r\nthe ASN element view in DHP 3 location Helmond doesn\'t show the correct data. For example, if we select all incoming ASNs for next week, in the header view I get 98 results, see screenshot.\r\n\r\nThen if I select the element view, first I get zero results.. If I select show all, I get also zero results: \r\n\r\nPlease check and fix this: Location uses the element view to make an overview of incoming intakes\n\n### Response:\n[""Comment 1: [\'!afbeelding!!afbeelding-1!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Problem z listą dla ASN"", ""Comment 4: Trip jest poprawnie  i tylko w tej wersji dla Sneek np działa.Przełączając się między widokami jest pusta lista dla elementów.\'"", ""Comment 5: \'ustalenia stand up do sprawdzenia czy to kwestia DHP 8.5\'"", ""Comment 6: \'Na liście elementów nie wyświetlają się ANSy/TRIPy"", ""Comment 7: które nie są zlinkowane z VT.Zgłoszone w DAP-13356 .!SN-no linked VT-2!\'"", ""Comment 8: \'Any update please?\'"", ""Comment 9: \'Hello"", ""Comment 10: we have found the problem - I will let you know how it will be solved and in what form.\'"", ""Comment 11: \'any update?\'"", ""Comment 12: \'Hello. So sorry for the lack of answers"", ""Comment 13: a fix has been prepared some time ago. As for the date of uploading on production for Helmond please contact directly with PM.Thank you and best regards.\'"", ""Comment 14: \'Hello"", ""Comment 15: a fix has been prepared some time ago. As for the date of uploading on production for applications please always contact directly with PM.\\\\rThank you and best regards.\\\\r\\\\rThis ticket has been closed.\']""]\nRelated Issues:\n[\'DAP-13356\']\n\n### End'}"
430,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8602\n\n### Instruction:\nSP-B/0554 back to entry\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 2: ""Hello Koen,Now you have rights for starting new process - it means that you should be able to put this document to entry status.Please try to do it and let us know that it\\\'s possible\', \'Comment 3: it should be available from document like on screen.!image-2023-02-22-08-40-31-700.png!Regards,Damian""\', ""Comment 4: \'Confirmed.!image-2023-02-22-13-21-07-476.png!\']""]\nRelated Issues:\n[]\n\n### End'}"
431,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8601\n\n### Instruction:\nHi, \r\nin DHC I need to link BMX code 1298 and code from our ERP system Integra 19807. I don´t see 19807 in the list.\r\nPls solve it asap. I need new recipes with this new RM.\r\nthx\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'!image-2023-02-21-17-27-50-357.png!!image-2023-02-21-17-28-40-418.png!\'"", ""Comment 4: \'Dear Lucie,I can see that item 19807 is linked to 01236. Please"", ""Comment 5: verify.Regards!image-2023-02-21-17-31-19-140.png!\'"", ""Comment 6: \'pls change it. I need to make new link.thx!\'"", ""Comment 7: \'Just to confirm"", ""Comment 8: should I unlink 19807 from bmx 01236?\'"", ""Comment 9: \'yes pls. We don´t use 01236 anymore.\'"", ""Comment 10: \'Please"", \'Comment 11: check. Now you should link items.Please\', ""Comment 12: verify!image-2023-02-21-17-46-07-970.png!\'"", ""Comment 13: \'I could select 19807 in teh list but it looks it still is not linked. !image-1!\'"", ""Comment 14: \'Please"", ""Comment 15: check!image-2023-02-21-17-59-24-074.png!\'"", ""Comment 16: \'it is okay nowthx\']""]\nRelated Issues:\n[]\n\n### End'}"
432,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8600\n\n### Instruction:\nHello,\r\n\r\nuser reported that the printout option is not available on VT preview screen: I checked and added different roles but it\'s not there. Can you please solve this?\n\n### Response:\n[""Comment 1: [\'!afbeelding!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'U mnie działa!image-2023-02-21-13-43-56-657.png!\'"", ""Comment 4: \'Dear Thomas,Please"", ""Comment 5: check now with user and let us know.Regards\'"", ""Comment 6: \'Edit user:!image-2023-02-21-14-03-38-106.png!Wybrać set business unit"", ""Comment 7: wybrać (w tym wypadku Helmond) i zapisać na business unicie i na powyższym ekranie\'"", \'Comment 8: ""Thanks\', \'Comment 9: I\\\'ll let him check""\', ""Comment 10: \'When you ave feedback from user"", \'Comment 11: please\', ""Comment 12: let me know if e can close this task.Regards\'"", ""Comment 13: \'Hi Thomas,Can we close this task?Regards\'"", ""Comment 14: \'Yes please\'"", ""Comment 15: \'Thank you\']""]\nRelated Issues:\n[]\n\n### End'}"
433,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8599\n\n### Instruction:\nWhen adjust import duty of Item code: 00828 to 6.5% in CDN, unfortunately, failed. \r\n\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Is it possible to complete the required fields from the list of attributes. !screenshot-1! If it is not on the list - please add for required ones and check if there is still a problem. !screenshot-2! \'"", ""Comment 4: \'Ticket can be closed.!image-1!\']""]\nRelated Issues:\n[]\n\n### End'}"
434,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8598\n\n### Instruction:\n Pallets from another lane are suddenly in a load order where they do not belong to\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!!image-1!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'In the scan there are still 4 pallets that should still be scanned in the loading order. in the application there are only 3 left and this is also correct.The last pallet in the scanner (187190811000313638) does not belong in this Trip at all.\'"", ""Comment 4: \'!image-2!\'"", ""Comment 5: \'Hereby an other recently example.!image-3!\'"", ""Comment 6: \'{code:java}SELECT * FROM [dbo].[WMSInternalDocumentOrderHeaders] HJoin [dbo].[WMSInternalDocumentOrderElements]E on E.WiE_HeaderId = H.WhI_Idwhere H.WhI_Id = 175795 or WiE_Id between 477547 and 477551{code}!image-2023-03-27-10-11-24-138!\'"", ""Comment 7: \'Wyjaśnione z Thomasem Dankersem. Po analizie wygląda na błędy kolejności procesowania wydań przez użytkowników na magazynie.\'"", ""Comment 8: \'Hi"", \'Comment 9: according to Marcin Block information\', ""Comment 10: this issue was explained with Thomas Dankers. After the analysis it looks like errors in the order of processing releases by users in the warehouse.This issue has been closed.\'"", ""Comment 11: \'This issue is closed by Kotrak.The problem did occur again.The user reports:he scan still contains 4 pallets that should still be scanned in the loading order. There are only 3 left in the application and this is also correct. The last pallet in the scanner (187190811000313638) does not belong in this Trip at all.!image-4!!image-5!\'"", ""Comment 12: \'Last remark was an old remark send by the user\'"", \'Comment 13: ""Hi Bert\', \'Comment 14: your last comment has the same examples that were originally in the issue - wasn\\\'t this already clarified with Marcin?Can we close this task?""]\']\nRelated Issues:\n[\'DGS-8560\']\n\n### End'}"
435,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8597\n\n### Instruction:\nSales Order missing from DHC, and therefore not sync\'ing to DHP. Needed for production.\r\n\n\n### Response:\n[""Comment 1: [\'https://helpdesk.kotrak.com/servicedesk/customer/portal/56/DGS-8594\'"", ""Comment 2: \'Widać w logach eprintegratora że adres poszedł wcześniej !screenshot-1! Historia zmian: !screenshot-2! z DHC: !screenshot-3! dla adresu  !screenshot-4! \'"", ""Comment 3: \'dodaliśmy do konfiguracji ERP Integratora wpis który załącza dosyłanie brakujących informacji.\'"", ""Comment 4: \'We have changed the ERP Integrator configuration that enables the sending of missing information.The problem should no longer occur.\'"", ""Comment 5: \'Does this resync all connected objects (Customer/Address/Recipe/Article)?\'"", ""Comment 6: \'Sending of missing information related to ERP XL"", \'Comment 7: so items\', ""Comment 8: customers and addresses.The recipes are from DHC.\'"", ""Comment 9: \'Ok"", ""Comment 10: thank you. The ticket can be closed.\']""]\nRelated Issues:\n[\'DGS-8594\']\n\n### End'}"
436,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8596\n\n### Instruction:\nBack to entry\r\nPI-RLB/2023/0999\r\nSI-RLB/2023/1047\r\nSRBe/2128\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Could you give Koen the rights to set these types of documents back to entry himself? Just like he can reopen rounds. Please move it to PROD.\'"", ""Comment 3: \'[~khuibers@deheus.com],all documents from list have been reply to your Inbox.[~mbovene@deheus.com],yes"", \'Comment 4: we can add rights for these types of documents for all users from role ""Start new process for document"":!image-2023-02-21-11-11-22-168.png!Best regards,Grzegorz\\\'\', ""Comment 5: \'{color:black}Hello{color} {color:black}{color} {color:black}All documents?{color} !image001!{color:black}{color} {color:black}I don’t see them in the inbox{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | | | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image002!{color:black} <[https://www.de-heus.nl/]>{color} | |  *{color:#006FB7} *DEHEUSVOEDERSB.V.‑LOCATIEHELMOND*{color}* | | | |{color:#000001} Gerstdijk12 \\\\u200b5704RGHelmond{color} | | |{color:#000001} M:{color}{color:#000001}{color}{color:#000001}+32-11-546672{color}{color:#000001} <tel:+32%20-%2011%20-%2054%2066%2072>{color} |  {color:#000001}KvK14626985{color}   _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | | !image003! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | | !image004! <[https://twitter.com/de_heus_voeders]>{color:black}{color} | | !image005! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image006! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} |        *Van:* Grzegorz Materla (Jira) <jira@kotrak.com>   *Verzonden:* dinsdag 21 februari 2023 11:13  *Aan:* Huibers"", ""Comment 6: Koen <khuibers@deheus.com>  *Onderwerp:* DGS-8596 Back to entry   !image007!\'"", ""Comment 7: \'{color:black}It’s ok"", \'Comment 8: I was in the wrong inbox{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | | | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image002!{color:black} <[https://www.de-heus.nl/]>{color} | |  *{color:#006FB7} *DEHEUSVOEDERSB.V.‑LOCATIEHELMOND*{color}* | | | |{color:#000001} Gerstdijk12 \\\\u200b5704RGHelmond{color} | | |{color:#000001} M:{color}{color:#000001}{color}{color:#000001}+32-11-546672{color}{color:#000001} <tel:+32%20-%2011%20-%2054%2066%2072>{color} |  {color:#000001}KvK14626985{color}   _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | | !image003! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | | !image004! <[https://twitter.com/de_heus_voeders]>{color:black}{color} | | !image005! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image006! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} |        *Van:* Huibers\', \'Comment 9: Koen   *Verzonden:* dinsdag 21 februari 2023 11:19  *Aan:* dgs@help.kotrak.com  *Onderwerp:* RE: DGS-8596 Back to entry    {color:black}Hello{color} {color:black}{color} {color:black}All documents?{color} !image008!{color:black}{color} {color:black}I don’t see them in the inbox{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | | | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image002!{color:black} <[https://www.de-heus.nl/]>{color} | |  *{color:#006FB7} *DEHEUSVOEDERSB.V.‑LOCATIEHELMOND*{color}* | | | |{color:#000001} Gerstdijk12 \\\\u200b5704RGHelmond{color} | | |{color:#000001} M:{color}{color:#000001}{color}{color:#000001}+32-11-546672{color}{color:#000001} <tel:+32%20-%2011%20-%2054%2066%2072>{color} |  {color:#000001}KvK14626985{color}   _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | | !image003! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | | !image004! <[https://twitter.com/de_heus_voeders]>{color:black}{color} | | !image005! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image006! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} |        *Van:* Grzegorz Materla (Jira) <[jira@kotrak.com|mailto:jira@kotrak.com]>   *Verzonden:* dinsdag 21 februari 2023 11:13  *Aan:* Huibers\', ""Comment 10: Koen <[khuibers@deheus.com|mailto:khuibers@deheus.com]>  *Onderwerp:* DGS-8596 Back to entry   !image001!!image007!\'"", \'Comment 11: ""[~khuibers@deheus.com],thank you for your reply.[~mbovene@deheus.com],I\\\'ve added posibility for all invoices for all sectors in test and prod environment. Only users with suitable rights can do it.Best regards\', \'Comment 12: Grzegorz""]\']\nRelated Issues:\n[]\n\n### End'}"
437,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8595\n\n### Instruction:\nsuddenly too many bags disconnected during replenishment and a negative line\r\n\n\n### Response:\n[""Comment 1: [\'!image!!image-1!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'next order from the same pallet gives the same problem!!image-2!\']""]\nRelated Issues:\n[\'DGS-8560\']\n\n### End'}"
438,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8594\n\n### Instruction:\nSales Order missing from DHC, and therefore not sync\'ing to DHP. Needed for production.\r\n\n\n### Response:\n[""Comment 1: [\'!image!!image-1!!image-2!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'order is now in DHC!screenshot-1! the order was missing due to the missing address for the customer"", ""Comment 4: the data has been sent.\'"", ""Comment 5: \'{code:java}  update k\\\\t  set kna_nazwa2=KnA_Nazwa2  FROM [CDNXL_DHFU].[CDN].[KntAdresy] k  where KnA_GIDNumer=32433\\\\t  update z\\\\t  set zan_stan=ZaN_Stan  FROM [CDNXL_DHFU].[CDN].[ZamNag] z  where ZaN_GIDNumer=797908{code}{code:java}2023-02-21 11:26:43,431 [47] DEBUG Evolution.ErpIntegrator.Services.DHC.DHCBusService.Handlers.Documents.Orders.OrderBusinessPartnerAddressIsNotSynchronizedMessageHandler [(null)] - Order OrderId: bfc4bdf5-52fb-4a5c-962c-130ce462f3af BusinessPartnerAddress: feca58ef-77d1-4e9d-be2b-2de15b5cb120S is not synchronized2023-02-21 11:26:43,431 [47] INFO  Evolution.ErpIntegrator.Services.DHC.DHCBusService.Handlers.Documents.Orders.OrderBusinessPartnerAddressIsNotSynchronizedMessageHandler [(null)] - ResynchronizeDataExtension is off - resynchronization skipped2023-02-21 11:26:43,431 [47] DEBUG Evolution.ErpIntegrator.Services.DHC.DHCBusService.Handlers.Documents.Orders.OrderBusinessPartnerAddressIsNotSynchronizedMessageHandler [(null)] - Order OrderId: bfc4bdf5-52fb-4a5c-962c-130ce462f3af BusinessPartnerAddress: feca58ef-77d1-4e9d-be2b-2de15b5cb120 is not synchronized2023-02-21 11:26:43,431 [47] INFO  Evolution.ErpIntegrator.Services.DHC.DHCBusService.Handlers.Documents.Orders.OrderBusinessPartnerAddressIsNotSynchronizedMessageHandler [(null)] - ResynchronizeDataExtension is off - resynchronization skipped{code}\'"", ""Comment 6: \'Thank you.Do we have an existing RCA open for this? \'"", ""Comment 7: \'Ok. I see one has been opened. You may close this ticket. Thanks.https://helpdesk.kotrak.com/servicedesk/customer/portal/56/DGS-8597 \'"", \'Comment 8: ""No\', \'Comment 9: we don\\\'t have it open. I have created RCA DGS-8597.""]\']\nRelated Issues:\n[\'DGS-8597\']\n\n### End'}"
439,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8593\n\n### Instruction:\nitem has just been replenished and a new replenishment immediately comes into the scan while this is not possible\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'What is the reason off immediately  a new replenishment?\'"", ""Comment 3: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 4: \' !WMO 2508! !image-2023-03-07-13-15-53-203!\'"", ""Comment 5: \'Od 22.12.2022 nie działała synchronizacja eventowa (Exchange - PCS"", ""Comment 6: Exchange - DHP). Powodem braku działania był brak wczytania konfiguracji. Po wykonaniu procedury reloadconfiguration synchronizacja eventowa zaczęła działać.\'"", ""Comment 7: \'Hello,after the developers analysis the reload configuration procedure was required to be processed.Synchronization for events has been verified.Please verify and send a feedback.\'"", ""Comment 8: \'{code:java}System.Data.SqlClient.SqlException (0x80131904): Transaction context in use by another session.   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception"", \'Comment 9: Boolean breakConnection\', \'Comment 10: Action`1 wrapCloseInAction)   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj\', \'Comment 11: Boolean callerHasConnectionLock\', \'Comment 12: Boolean asyncClose)   at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior\', \'Comment 13: SqlCommand cmdHandler\', \'Comment 14: SqlDataReader dataStream\', \'Comment 15: BulkCopySimpleResultSet bulkCopyHandler\', \'Comment 16: TdsParserStateObject stateObj\', \'Comment 17: Boolean& dataReady)   at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior\', \'Comment 18: SqlCommand cmdHandler\', \'Comment 19: SqlDataReader dataStream\', \'Comment 20: BulkCopySimpleResultSet bulkCopyHandler\', \'Comment 21: TdsParserStateObject stateObj)   at System.Data.SqlClient.TdsParser.TdsExecuteTransactionManagerRequest(Byte[] buffer\', \'Comment 22: TransactionManagerRequestType request\', \'Comment 23: String transactionName\', \'Comment 24: TransactionManagerIsolationLevel isoLevel\', \'Comment 25: Int32 timeout\', \'Comment 26: SqlInternalTransaction transaction\', \'Comment 27: TdsParserStateObject stateObj\', \'Comment 28: Boolean isDelegateControlRequest)   at System.Data.SqlClient.SqlInternalConnectionTds.PropagateTransactionCookie(Byte[] cookie)   at System.Data.SqlClient.SqlInternalConnection.EnlistNonNull(Transaction tx)   at System.Data.SqlClient.SqlInternalConnection.Enlist(Transaction tx)   at System.Data.ProviderBase.DbConnectionInternal.ActivateConnection(Transaction transaction)   at System.Data.ProviderBase.DbConnectionPool.PrepareConnection(DbConnection owningObject\', \'Comment 29: DbConnectionInternal obj\', \'Comment 30: Transaction transaction)   at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject\', \'Comment 31: UInt32 waitForMultipleObjectsTimeout\', \'Comment 32: Boolean allowCreate\', \'Comment 33: Boolean onlyOneCheckConnection\', \'Comment 34: DbConnectionOptions userOptions\', \'Comment 35: DbConnectionInternal& connection)   at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject\', \'Comment 36: TaskCompletionSource`1 retry\', \'Comment 37: DbConnectionOptions userOptions\', \'Comment 38: DbConnectionInternal& connection)   at System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection\', \'Comment 39: TaskCompletionSource`1 retry\', \'Comment 40: DbConnectionOptions userOptions\', \'Comment 41: DbConnectionInternal oldConnection\', \'Comment 42: DbConnectionInternal& connection)   at System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection\', \'Comment 43: DbConnectionFactory connectionFactory\', \'Comment 44: TaskCompletionSource`1 retry\', \'Comment 45: DbConnectionOptions userOptions)   at System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource`1 retry)   at System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry)   at System.Data.SqlClient.SqlConnection.Open()   at Exchange.Repository.SQL.AppCenter.OpenConnection()   at Exchange.Repository.SQL.Logger.Log(ExchangeLogType type\', \'Comment 46: String message\', \'Comment 47: LogCategory category\', \'Comment 48: Nullable`1 objectId)   at Exchange.Repository.SQL.Logger.Log(ExchangeLogType type\', \'Comment 49: String message\', ""Comment 50: LogCategory category)   at Exchange.EventBasedSynchronization.MainService.LoadConfiguration()   at Exchange.EventBasedSynchronization.MainService.LoadConfigurationIfEmpty()   at Exchange.EventBasedSynchronization.MainService.SynchronizeReplenishmentRequest()ClientConnectionId:4597b135-70f4-4fb8-b3be-0a92f7b05b6aError Number:3910,State:2,Class:16{code}!Exchange event base synchro stopped 2022-12-22!\'"", ""Comment 51: \'This issue has been resolved. Ticket has been closed.\']""]\nRelated Issues:\n[\'DGS-8560\']\n\n### End'}"
440,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8592\n\n### Instruction:\nItem and recipe for 515006 are not arriving in DHP Sneek, even after various synch and resend attempts.\r\n\r\nItem needs to be produced tonight for first shipment tomorrow, so it\'s urgent.\r\n\r\nPlease fix.\r\n\r\nRegards,\r\nRob.\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Item and recipe should be in DHP  now. Please verify.\'"", ""Comment 3: \'Verified!Both items and the recipe are in DHP Sneek. I informed the production manager.\'"", ""Comment 4: \'Ok. So I close this issue. Regards\'"", ""Comment 5: \'Thanks Monika.\']""]\nRelated Issues:\n[]\n\n### End'}"
441,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8591\n\n### Instruction:\nHi,\r\nMay you help check data: i found some SO sending 2 time in log file?\r\nis it still ok or we must fix it?\n\n### Response:\n[""Comment 1: [\'!image![^MNS Feed - Check duplicate SO (1).xlsx] _(3,66 MB)_\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'query that from DHC\'"", ""Comment 4: \'Dear Hardy,I have checked your query. You have made it by order elements"", \'Comment 5: that is why you can see duplicated sent date.But if you have a look for marked order numebr you can see that it refers to 4 different elements:!image-2023-02-20-14-52-03-467.png|width=910,height=533!After a little modification\', ""Comment 6: you can see there is only one order.!image-2023-02-20-14-54-55-651.png|width=914,height=533!Regards\'"", ""Comment 7: \'In DHP we can see one document:!image-2023-02-20-14-58-02-779.png!\'"", ""Comment 8: \'!image-2023-02-20-15-21-33-583.png!\'"", \'Comment 9: ""{code:java}select A.ID\', \'Comment 10: B.DocumentNumber\', \'Comment 11: B.IssueDate\', \'Comment 12: B.Status\', \'Comment 13: A.CommitDate as datapotw\', \'Comment 14: A.EntityIdfrom OrderExportInfoes ALEft JOIn Orders B On A.EntityId=B.Id--LEFT JOIN OrderElements C ON B.Id=C.OrderId--left join items D On C.ItemId=D.id--left join BusinessPartners E ON B.MainBusinessPartnerId =E.idwhere a.id in(\\\'C8D7E034-7981-4F5D-9C3A-0064FF705D76\\\',\\\'4A56B226-0CCB-402F-A2CD-D491F1CBC820\\\',\\\'C7075B41-A54F-4EE0-BF4D-31F1EAF7BB71\\\',\\\'EFA72E37-8CA0-4A3A-A64E-34EA754C7E53\\\',\\\'D3209B82-D8E6-4066-ADF0-8082081450FE\\\',\\\'E365E3E2-E89D-4381-B2B9-CF39848629A3\\\',\\\'EDDCB12E-8D0B-436A-8605-59C015F63771\\\',\\\'5C9E45F8-2E81-4D95-9AD3-E43ECC024250\\\',\\\'BA370AFF-3789-4C7C-9800-AABE5F36BD22\\\',\\\'515FECF7-394F-4413-81EC-3961301E4994\\\',\\\'C606FE7C-D2D1-49C0-89AF-5517937E5E44\\\',\\\'36BBCE71-29D1-4E3A-9518-8FF8369A6A3E\\\',\\\'9C0AB804-A606-43F9-9620-EBD041E58822\\\',\\\'AD5DD91A-9B47-41B9-8674-719DC171CDC5\\\',\\\'194C8278-90D3-4C33-9E8C-47DDCB051CD5\\\',\\\'239056A1-8A54-4BC7-BA83-EA9A7FA1ADB3\\\',\\\'9EFB4D5C-7633-4219-B5D1-E8AA41BF7DD3\\\',\\\'8A4D0147-73CF-4E17-9AFC-37B1A316BA3A\\\',\\\'78645BD9-E92E-4418-97CF-2ED85C712E91\\\',\\\'ED92A313-3CAE-4173-A4B7-2964E1C9965B\\\',\\\'C0305799-A6CC-4432-ABD3-A7879ACD1A7C\\\',\\\'714D9DD8-B722-42D5-99E4-2AF72707B124\\\',\\\'1233C2E3-0E23-4A75-8F4E-4607ABAD8C3A\\\',\\\'F0BBCF23-E057-4216-ABBA-68FADCA43229\\\',\\\'EB362139-8B64-4A9D-899D-4AD42E63D9FD\\\',\\\'145D54F0-C0CB-4144-8205-D0E0A4763EEF\\\',\\\'25582D46-7D82-4738-A622-5F2AA486A2F0\\\',\\\'89517F67-DDD7-4DD7-B9D5-D9DDAF3447E3\\\',\\\'3998B89A-51F5-4E03-A021-E11153960256\\\',\\\'7092E974-585F-4313-8696-25247B91EE31\\\',\\\'2FCE11D4-BF17-48BC-BBB4-35B63F525A52\\\',\\\'72939D64-B5D3-4BA0-99F5-E3154603D3BB\\\',\\\'FB0AAAD8-9970-4748-A2D3-9BB4F0608E34\\\',\\\'56EA6093-3BD7-4FD5-93F3-9200AD303AC4\\\',\\\'2F54C8B7-8F77-44B2-8214-C80B938278C2\\\',\\\'95EACB3A-8E84-46F3-9D23-43818F2672B8\\\',\\\'1065D408-ED41-421E-B5E3-AF11B92CBA3A\\\',\\\'087AFC78-AC54-4661-8249-54B27EF2F640\\\',\\\'968BE807-58E0-4198-8036-0F9251C60EB5\\\',\\\'ABB6993E-6AD3-456E-B21F-6A8D904CAFE9\\\',\\\'96989CEA-DA6D-40A9-ACF9-FF4402C48792\\\',\\\'E62DF455-F22A-43DB-9A69-E769D166C8FA\\\',\\\'1E67699C-03E3-4328-8EF7-BEADC809FF34\\\',\\\'3638A40D-42DB-4367-9A2C-72677C233AAD\\\',\\\'97E20ACF-4C51-44C3-92F2-63CAE19A9B9D\\\',\\\'94644FE6-8E2C-405D-B340-EA83FD0B73AE\\\',\\\'178F59A0-0700-49D9-9232-3A2935B7DFB0\\\',\\\'64DE7FFA-EC9B-402E-9A27-41F0617498E8\\\',\\\'8128EF5C-C5C3-49DA-9829-A28D4E5F38EE\\\',\\\'4287D615-03B5-44E0-96ED-B6F8428579E0\\\',\\\'57424739-095F-42FD-A18A-F75A44EC9BCD\\\',\\\'A2416ED6-84F6-49C0-B8CB-6F51C98A3E79\\\',\\\'7CFD8AA7-B76B-4312-9A06-989B7BAD1A8E\\\',\\\'BAE3005A-69DF-4F98-881E-ADB394EFF321\\\',\\\'1EDD8647-DECB-442C-AA85-9DD867CF8EFC\\\',\\\'775B06D1-719E-4AED-98DC-561EA5F2C86C\\\',\\\'2D408C91-A1C3-41B9-A752-CD8B9D00A56C\\\',\\\'0B3509C3-4A82-416C-8C6F-3AF36149E023\\\',\\\'04161A2F-1C47-4FC4-A27A-C2ED311035EF\\\',\\\'5111B600-5C56-43E2-AF92-05210D26F358\\\',\\\'62C979D7-8FA9-44A8-85EB-FB0CBEC84292\\\',\\\'743B4485-CD3B-45B2-9839-D55D63F4C9D4\\\',\\\'A40C02AF-4215-448C-ACA4-51F3706D2245\\\',\\\'54DF8DB4-305D-421F-953B-2193A4B9D79C\\\',\\\'F9F635E0-42BA-48E3-B300-E9429361A4A8\\\',\\\'697A611B-C8D3-4716-8AF7-EBCD5B2CE667\\\',\\\'2E33E509-4278-4235-929B-96EC82E76403\\\',\\\'147F959A-5438-4896-8D82-06FEB4E97E53\\\',\\\'29B69124-1388-4BE5-A534-6DDC509F6BB9\\\',\\\'8B5F9739-C7AF-4988-83BB-1197AEF3E285\\\',\\\'5740ACCD-2FE4-4C15-99B8-73C0F789CFB5\\\',\\\'1DECAB2A-CF6A-45AB-829D-1D94920FCBFE\\\',\\\'4029DA86-B40C-46CD-AF01-E78B1878F5A4\\\',\\\'93390ADD-C50B-4BD2-81C6-00E3B3AB5825\\\',\\\'4C9EB1E3-9525-48DB-A610-637ED22B36DC\\\',\\\'D7955DFE-D00B-4582-AAD7-9447E09C9D74\\\',\\\'39964473-0549-4F50-8508-F6E896D1151E\\\',\\\'8F988E7C-7EC1-4C63-81E8-2EC07C514D94\\\',\\\'9C149A4B-5D15-4300-8944-C0DFAB716FB8\\\',\\\'B8B96362-CF2A-4D97-B9D0-CBA1360E96C8\\\',\\\'1A21E196-8A8F-4F1B-837E-C6C63DC3965D\\\',\\\'13A2A582-3741-4696-8960-5E26831A0892\\\',\\\'AB6117BE-1326-40F0-93EC-876717662299\\\',\\\'6BE6E8FE-4C5F-4B5C-9239-8DD83A546EF1\\\',\\\'7CD3A0E1-8688-4B22-A47D-2C6B7FE35EF6\\\',\\\'07604816-7DC0-4A45-84C0-5F3A337A6A12\\\',\\\'E8D49B45-3CA8-4A61-A82A-D98B1F5E4FF4\\\',\\\'58377FBE-56F5-4414-89B5-91F95E205FC1\\\',\\\'6FB82146-8107-4ED1-B403-0328A347F328\\\',\\\'87086D51-5314-44A8-8EF8-C8E6917330F0\\\',\\\'E63B86B2-831A-4CD8-8779-8BB07B5B5BBF\\\',\\\'95239AF8-D9AA-4216-A950-7088FE69AF21\\\',\\\'16EBA4B1-B5FC-4FDD-B0BB-162B73881A27\\\',\\\'914154C0-41C9-4962-BD69-9A64C42665E8\\\'){code}""\', \'Comment 15: ""{code:java}select A.ID\', \'Comment 16: B.DocumentNumber\', \'Comment 17: B.IssueDate\', \'Comment 18: B.Status\', \'Comment 19: C.ItemCode\', \'Comment 20: C.Quantity\', \'Comment 21: E.Code\', \'Comment 22: A.CommitDate as datapotw\', \'Comment 23: A.EntityIdfrom OrderExportInfoes ALEft JOIn Orders B On A.EntityId=B.IdLEFT JOIN OrderElements C ON B.Id=C.OrderIdleft join items D On C.ItemId=D.idleft join BusinessPartners E ON B.MainBusinessPartnerId =E.idwhere a.id in(\\\'C8D7E034-7981-4F5D-9C3A-0064FF705D76\\\',\\\'4A56B226-0CCB-402F-A2CD-D491F1CBC820\\\',\\\'C7075B41-A54F-4EE0-BF4D-31F1EAF7BB71\\\',\\\'EFA72E37-8CA0-4A3A-A64E-34EA754C7E53\\\',\\\'D3209B82-D8E6-4066-ADF0-8082081450FE\\\',\\\'E365E3E2-E89D-4381-B2B9-CF39848629A3\\\',\\\'EDDCB12E-8D0B-436A-8605-59C015F63771\\\',\\\'5C9E45F8-2E81-4D95-9AD3-E43ECC024250\\\',\\\'BA370AFF-3789-4C7C-9800-AABE5F36BD22\\\',\\\'515FECF7-394F-4413-81EC-3961301E4994\\\',\\\'C606FE7C-D2D1-49C0-89AF-5517937E5E44\\\',\\\'36BBCE71-29D1-4E3A-9518-8FF8369A6A3E\\\',\\\'9C0AB804-A606-43F9-9620-EBD041E58822\\\',\\\'AD5DD91A-9B47-41B9-8674-719DC171CDC5\\\',\\\'194C8278-90D3-4C33-9E8C-47DDCB051CD5\\\',\\\'239056A1-8A54-4BC7-BA83-EA9A7FA1ADB3\\\',\\\'9EFB4D5C-7633-4219-B5D1-E8AA41BF7DD3\\\',\\\'8A4D0147-73CF-4E17-9AFC-37B1A316BA3A\\\',\\\'78645BD9-E92E-4418-97CF-2ED85C712E91\\\',\\\'ED92A313-3CAE-4173-A4B7-2964E1C9965B\\\',\\\'C0305799-A6CC-4432-ABD3-A7879ACD1A7C\\\',\\\'714D9DD8-B722-42D5-99E4-2AF72707B124\\\',\\\'1233C2E3-0E23-4A75-8F4E-4607ABAD8C3A\\\',\\\'F0BBCF23-E057-4216-ABBA-68FADCA43229\\\',\\\'EB362139-8B64-4A9D-899D-4AD42E63D9FD\\\',\\\'145D54F0-C0CB-4144-8205-D0E0A4763EEF\\\',\\\'25582D46-7D82-4738-A622-5F2AA486A2F0\\\',\\\'89517F67-DDD7-4DD7-B9D5-D9DDAF3447E3\\\',\\\'3998B89A-51F5-4E03-A021-E11153960256\\\',\\\'7092E974-585F-4313-8696-25247B91EE31\\\',\\\'2FCE11D4-BF17-48BC-BBB4-35B63F525A52\\\',\\\'72939D64-B5D3-4BA0-99F5-E3154603D3BB\\\',\\\'FB0AAAD8-9970-4748-A2D3-9BB4F0608E34\\\',\\\'56EA6093-3BD7-4FD5-93F3-9200AD303AC4\\\',\\\'2F54C8B7-8F77-44B2-8214-C80B938278C2\\\',\\\'95EACB3A-8E84-46F3-9D23-43818F2672B8\\\',\\\'1065D408-ED41-421E-B5E3-AF11B92CBA3A\\\',\\\'087AFC78-AC54-4661-8249-54B27EF2F640\\\',\\\'968BE807-58E0-4198-8036-0F9251C60EB5\\\',\\\'ABB6993E-6AD3-456E-B21F-6A8D904CAFE9\\\',\\\'96989CEA-DA6D-40A9-ACF9-FF4402C48792\\\',\\\'E62DF455-F22A-43DB-9A69-E769D166C8FA\\\',\\\'1E67699C-03E3-4328-8EF7-BEADC809FF34\\\',\\\'3638A40D-42DB-4367-9A2C-72677C233AAD\\\',\\\'97E20ACF-4C51-44C3-92F2-63CAE19A9B9D\\\',\\\'94644FE6-8E2C-405D-B340-EA83FD0B73AE\\\',\\\'178F59A0-0700-49D9-9232-3A2935B7DFB0\\\',\\\'64DE7FFA-EC9B-402E-9A27-41F0617498E8\\\',\\\'8128EF5C-C5C3-49DA-9829-A28D4E5F38EE\\\',\\\'4287D615-03B5-44E0-96ED-B6F8428579E0\\\',\\\'57424739-095F-42FD-A18A-F75A44EC9BCD\\\',\\\'A2416ED6-84F6-49C0-B8CB-6F51C98A3E79\\\',\\\'7CFD8AA7-B76B-4312-9A06-989B7BAD1A8E\\\',\\\'BAE3005A-69DF-4F98-881E-ADB394EFF321\\\',\\\'1EDD8647-DECB-442C-AA85-9DD867CF8EFC\\\',\\\'775B06D1-719E-4AED-98DC-561EA5F2C86C\\\',\\\'2D408C91-A1C3-41B9-A752-CD8B9D00A56C\\\',\\\'0B3509C3-4A82-416C-8C6F-3AF36149E023\\\',\\\'04161A2F-1C47-4FC4-A27A-C2ED311035EF\\\',\\\'5111B600-5C56-43E2-AF92-05210D26F358\\\',\\\'62C979D7-8FA9-44A8-85EB-FB0CBEC84292\\\',\\\'743B4485-CD3B-45B2-9839-D55D63F4C9D4\\\',\\\'A40C02AF-4215-448C-ACA4-51F3706D2245\\\',\\\'54DF8DB4-305D-421F-953B-2193A4B9D79C\\\',\\\'F9F635E0-42BA-48E3-B300-E9429361A4A8\\\',\\\'697A611B-C8D3-4716-8AF7-EBCD5B2CE667\\\',\\\'2E33E509-4278-4235-929B-96EC82E76403\\\',\\\'147F959A-5438-4896-8D82-06FEB4E97E53\\\',\\\'29B69124-1388-4BE5-A534-6DDC509F6BB9\\\',\\\'8B5F9739-C7AF-4988-83BB-1197AEF3E285\\\',\\\'5740ACCD-2FE4-4C15-99B8-73C0F789CFB5\\\',\\\'1DECAB2A-CF6A-45AB-829D-1D94920FCBFE\\\',\\\'4029DA86-B40C-46CD-AF01-E78B1878F5A4\\\',\\\'93390ADD-C50B-4BD2-81C6-00E3B3AB5825\\\',\\\'4C9EB1E3-9525-48DB-A610-637ED22B36DC\\\',\\\'D7955DFE-D00B-4582-AAD7-9447E09C9D74\\\',\\\'39964473-0549-4F50-8508-F6E896D1151E\\\',\\\'8F988E7C-7EC1-4C63-81E8-2EC07C514D94\\\',\\\'9C149A4B-5D15-4300-8944-C0DFAB716FB8\\\',\\\'B8B96362-CF2A-4D97-B9D0-CBA1360E96C8\\\',\\\'1A21E196-8A8F-4F1B-837E-C6C63DC3965D\\\',\\\'13A2A582-3741-4696-8960-5E26831A0892\\\',\\\'AB6117BE-1326-40F0-93EC-876717662299\\\',\\\'6BE6E8FE-4C5F-4B5C-9239-8DD83A546EF1\\\',\\\'7CD3A0E1-8688-4B22-A47D-2C6B7FE35EF6\\\',\\\'07604816-7DC0-4A45-84C0-5F3A337A6A12\\\',\\\'E8D49B45-3CA8-4A61-A82A-D98B1F5E4FF4\\\',\\\'58377FBE-56F5-4414-89B5-91F95E205FC1\\\',\\\'6FB82146-8107-4ED1-B403-0328A347F328\\\',\\\'87086D51-5314-44A8-8EF8-C8E6917330F0\\\',\\\'E63B86B2-831A-4CD8-8779-8BB07B5B5BBF\\\',\\\'95239AF8-D9AA-4216-A950-7088FE69AF21\\\',\\\'16EBA4B1-B5FC-4FDD-B0BB-162B73881A27\\\',\\\'914154C0-41C9-4962-BD69-9A64C42665E8\\\'){code}""\', ""Comment 24: \'Hi,You can see may query. 2 row for 1 order!image-1!!image-2!\'"", ""Comment 25: \'!image-2023-02-21-13-07-27-567.png!\'"", ""Comment 26: \'DHC:!image-2023-02-21-13-16-30-944.png!Service:!image-2023-02-21-13-17-04-415.png!\'"", ""Comment 27: \'Hi Hardy,We have checked and data from the Orders did not duplicate in DHC or DHP so in our opinion we should treat it as incidental case. Nothing critical.Regards\'"", ""Comment 28: \'thank you. you can close the ticket\'"", ""Comment 29: \'Thank you\']""]\nRelated Issues:\n[]\n\n### End'}"
442,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8590\n\n### Instruction:\nSystem should displays value \'Trade\' on invoices when there is value \'1\' in field Full number on SI and PI.\r\n\r\nIt can happen when invoices are generated from SR\'s (SR -> SI -> PI)\r\n\r\n\xa0\r\n\r\n\xa0\n\n### Response:\n[""Comment 1: [\'!image009!\'"", \'Comment 2: ""[~grzegorz.materla@kotrak.com]do ogarnięcia\', \'Comment 3: aby to zrobić tak\', ""Comment 4: że wyświetlamy w polu \'Full number\' (numer rundy) \'Trade\' jeżeli * jest to dokument SI"", ""Comment 5: który jest wygenerowany ze Slaughtery Report - pole \'Leading doc\'!image-2023-02-22-14-40-15-576.png! * jest to dokument PI"", \'Comment 6: który jest wygenerowany z PI\', \'Comment 7: a PI jest wygenerowane z SR. Ewentualnie można to oprzeć o powiązanie na PI w poli \\\'Go to Slaughtery Report\\\' !image-2023-02-22-14-39-52-979.png!Na SR wtedy w polu \\\'Full number\\\' będzie wartość \\\'Trade\\\'.!image-2023-02-22-14-44-03-798.png!Na SI i na PI w innych przypadkach (poza takimi SI i PI pochodzące z SR jak w przykładzie wyżej) nie powinna być możliwa do wybrania z lookupa wartość \\\'Trade\\\'.""\', \'Comment 8: \\\'[~mbovene@deheus.com],the modification has been added in field ""Full number"" for SI and PI MAS NL (include credit invoices) in test environment.You can feel free to test it.Best regards,Grzegorz\\\'\', ""Comment 9: \'Confirmed"", ""Comment 10: can be closed.\'"", ""Comment 11: \'[~mbovene@deheus.com],the modification has been moved in prod environment.You can feel free to test it.Best regards,Grzegorz\']""]\nRelated Issues:\n[]\n\n### End'}"
443,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8589\n\n### Instruction:\nwe still regularly see that a warehouse employee completes a replenishment order and a new order immediately comes in for the same number of big bags of the same item. Partly known that this is because an order is completed in DHP, when the stock is not yet known in the factory and the factory in the meantime makes a new request that this goes wrong.\r\n\r\nhowever, there is one thing we do not know for sure and we would like to know. namely: what happens if the assignment in DHP is “in progress” and a new request arrives in the meantime?\r\n\r\nwill this be ignored or will a new RM assignment be created?\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Out internal number : (SDNL-31532)\'"", ""Comment 4: \'Hi,We need to analize briefly your question.Please be informed that we have forwarded the issue to the development team in order to internal analysis.We are waiting for more details and will be back with further information as soon as possible.Regards\'"", ""Comment 5: \'After the analysis on Friday"", \'Comment 6: it turned out that the event-based integration had not worked since December 22\', \'Comment 7: 2022. Only the service based on timed synchronization calls every 5 minutes worked for over four months. Therefore\', \'Comment 8: this caused problems in transferring replenishment information\', \'Comment 9: pallet labels from production\', \'Comment 10: and many other delayed processes.Currently\', \'Comment 11: the event base synchronization is up and running. ---- Answering the question of  Bert:""what happens if the assignment in DHP is “in progress” and a new request arrives in the meantime?""This WMO\', \'Comment 12: which is in progress\', \'Comment 13: will proceed by the operator as it is\', ""Comment 14: and a new order will be generated for the excess quantity.\'"", ""Comment 15: \'[~asysta@kotrak.pl] Jak dla mnie task można procesować do zamknięcia.\'"", ""Comment 16: \'What exactly were the actions performed. Were any services not started or were services stopped and restarted? if yes"", ""Comment 17: which services were these?\'"", ""Comment 18: \'Kolega ma pytanie :P\']""]\nRelated Issues:\n[]\n\n### End'}"
444,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8588\n\n### Instruction:\nPlease unlink attached recipes in DHC. 4 for Veghel and 1 for Nijkerk\n\n### Response:\n[""Comment 1: [\'!afbeelding!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'We can remove them from DHC and DHP databases.Please confirm.\'"", ""Comment 4: \'Yes please!\'"", ""Comment 5: \'VE307499-1this technology has a subversion,!image-2023-02-20-14-22-58-051.png! should it be removed too?\'"", ""Comment 6: \'Yes"", ""Comment 7: please remove both versions. Thanks for asking!\'"", \'Comment 8: ""There are already so many PLRs generated for the technologiesnumber of PLR\\\'s | technology code76   NY303436 334  VE303436 may i know what is the reason for the change? because we will have to use a different solution""\', ""Comment 9: \'{color:black}Vivian"", \'Comment 10: can you please answer this question?{color} {color:black}{color} {color:black}(hope your answer will be directly available in the ticket){color} {color:black}{color} | |{color:#000001} Kindregards,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Martijn{color} |{color:#000001} {color} |{color:#000001} Meier{color} |  {color:#000001}ApplicationEngineer{color} | | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.deheus.com/]>{color} | |  *{color:#006FB7} *DEHEUSANIMALNUTRITIONB.V.*{color}* | | | |{color:#000001} P.O.Box396 6710BJEde TheNetherlands{color} | |{color:#000001} Rubensstraat175 6717VEEde TheNetherlands{color} | | |{color:#000001} M:{color}{color:#000001}{color}{color:#000001}+31621679216{color}{color:#000001} <tel:+31%206%2021%20679%20216>{color} |  {color:#000001}CoC16011201{color}   _{color:#000001} _Thise‑mailmessageanditsattachmentsaresubjecttothedisclaimer_ _publishedonthewebsiteof_{color}_{color:#000001} _+{color}[{color:#000001}{color}{color:#000001} _+ DeHeusAnimalNutrition+_{color}{color:#000001} {color}|https://www.deheus.com/disclaimer]{color:#000001} {color}+__{color:#000001} _._{color}_ | | !image002! <[https://www.facebook.com/deheusanimalnutrition]>{color:black}{color} | | !image003! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image004! <[https://www.linkedin.com/company/royal-de-heus/mycompany/]>{color:black}{color} | | !image005! <[https://www.instagram.com/de_heus_animal_nutrition/]>{color:black}{color} |        *From:* Piotr Gaczorek (Jira) <jira@kotrak.com>   *Sent:* maandag 20 februari 2023 14:39  *To:* Meier\', ""Comment 11: Martijn <mmeier@deheus.com>  *Subject:* DGS-8588 Unlinking of recipes   \'"", ""Comment 12: \'Dear Poitr and Martijn,Thank you for your help!What do you mean with PLR’s? The reason for the questionto remove these additional technologies is to change the link between therecipes.Now recipe A is linked torecipe B"", ""Comment 13: but in the new situation recipe B must be linked to A. I hope this answers yourquestion. Kind regards,Vivian van der NatFormulator\'"", ""Comment 14: \'[^plr_list.xlsx]\'"", ""Comment 15: \'We need to remove the associated PLR documents to remove the technologies themselves - I am sending a list of PLRs.Please confirm that they can be removed from the databases. [^plr_list.xlsx] \'"", ""Comment 16: \'Confirmed :)\'"", ""Comment 17: \'Thank you. I just wanted to mention the GDC-799 is for approval (additional technology- option to archive/disable and filter on latest version).\'"", \'Comment 18: ""In case you haven\\\'t removed the PLR\\\'s yet\', ""Comment 19: please don\'t do. I received additional feedback about it. It was strongly suggested not to remove PLR from after October 1st"", \'Comment 20: 2022.Is there an alternative way of unlinking the recipes without removeing the PLR\\\'s?""\', ""Comment 21: \'There are two technologies to remove:VE303436,NY303436To remove them I must also remove the PLRs.Now recipe A is linked torecipe B"", ""Comment 22: but in the new situation recipe B must be linked to A.Can i get an example after such a change?\'"", ""Comment 23: \'Hi Piotr"", ""Comment 24: please remove thoses technologies. the connected PLRs are only for the recoding to the customer item. Some times customer itemcode is no longer valid and then it should be cleaned to be used as normal De Heus item\'"", ""Comment 25: \'This is also the reason why a change is asked for to be able to archive such technologies\'"", ""Comment 26: \'Hello"", ""Comment 27: additional technologies have been removed.\'"", ""Comment 28: \'Ticket can be closed\']""]\nRelated Issues:\n[]\n\n### End'}"
445,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8587\n\n### Instruction:\nwe are trying to produce 7800-b50 but when we create a production order it shows up as bulk therefore unable to confirm production order. please help\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Hello"", ""Comment 3: Please make a new version of the recipe.The linked now have been corrected.Regards.\'"", ""Comment 4: \'okay\'"", ""Comment 5: \'Can we close this incident as the issue has been resolved ?Regards\'"", ""Comment 6: \'yes please\']""]\nRelated Issues:\n[]\n\n### End'}"
446,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8586\n\n### Instruction:\nHello,\r\n\r\nWe cant confirm PLR 0672180223004, the error message does not give an indication as to what the issue might be.\r\n\r\nwe have checked the logs around this date no error message related.\r\nno raw materials are archived.\r\nmaintenance shows that the order, recipe, item etc. are in every module they need to be in.\r\nwe restarted services IntegrationPCS and Production nothing.\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Hello"", ""Comment 4: Please verify connection!image-2023-02-20-10-38-37-621.png!Regards\'"", \'Comment 5: \\\'Exception has been thrown by the target of an invocation. -> An error occurred while saving the entity changes. See the inner exception for details. -> The INSERT statement conflicted with the FOREIGN KEY constraint ""FK_ProductionLots_Recipes_RecipeId"". The conflict occurred in database ""DHPlantStockBusinessLogicMain""\', \'Comment 6: table ""dbo.Recipes""\', ""Comment 7: column \\\\\'Id\\\\\'.The statement has been terminated.\'"", ""Comment 8: \'[[DHP 3.0] Unable to confirm PLR - Production lot with id 25117bcb-0486-4d8c-bf81-dcf8c74581d4 was not found|onenote:https://kotrak.sharepoint.com/sites/erpasysta/Shared%20Documents/Baza%20wiedzy/Baza%20Wiedzy%20-%20ERPSD/Klienci/DEHEUS/DEHEUS%20APPLICATIONS/RPA/Baza%20wiedzy.one#%5bDHP%203.0%5d%20Unable%20to%20confirm%20PLR%20-%20Production&section-id=\\\\\\\\{A2F09CD6-A23A-42F3-92F5-ED66B521455B}&page-id=\\\\\\\\{7ADC7B54-2063-46F7-A176-9F22E23993D5}&end] ([Widok sieci Web|https://kotrak.sharepoint.com/sites/erpasysta/_layouts/OneNote.aspx?id=%2Fsites%2Ferpasysta%2FShared%20Documents%2FBaza%20wiedzy%2FBaza%20Wiedzy%20-%20ERPSD&wd=target%28Klienci%2FDEHEUS%2FDEHEUS%20APPLICATIONS%2FRPA%2FBaza%20wiedzy.one%7CA2F09CD6-A23A-42F3-92F5-ED66B521455B%2F%5BDHP%203.0%5D%20Unable%20to%20confirm%20PLR%20-%20Production%7C7ADC7B54-2063-46F7-A176-9F22E23993D5%2F%29])\'"", ""Comment 9: \'!image-2023-02-20-11-26-39-216.png!\'"", ""Comment 10: \'Please try to confim it again.\'"", ""Comment 11: \'Resolved"", ""Comment 12: Thanks\']""]\nRelated Issues:\n[]\n\n### End'}"
447,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8585\n\n### Instruction:\nHello I have a problem with my own access rights in DHP CU. Namely it appears that somehow I inherited existence from the ex colleague with the same name as I. So the DHP CU says  that the user already exists even that my colleague from IT erased all the roles. Everything is OK in DHP Sabac just for DHP CU. Can you please create me as new user in DHP CU? Nemanja Antonic will expand my rights but just please create me as a user. Thank you.\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'This user required activation"", ""Comment 3: he is currently active - you can edit this account now.!image-2023-02-20-10-20-30-309.png!\'"", ""Comment 4: \'Hi it is now OK and thank you for your help. Best regards.\'"", ""Comment 5: \'Thank you for confirmation"", ""Comment 6: regards.\']""]\nRelated Issues:\n[]\n\n### End'}"
448,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8584\n\n### Instruction:\nPlease help to check PLR 4374190223005 in CanTho Plant ( 0437) .\r\n\r\nIn Production module : user created and confirmed lot number 374190223005 with 28 tons . But in WMS has delivery with 30 tons  .\r\n\n\n### Response:\n[""Comment 1: [\'!image!!image-1!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'!image-2023-02-20-15-11-08-325.png!\'"", \'Comment 4: ""robił ten sam user w WMS nie ma zmiany z 30t na 28t{code:java} FROM [DHPlantProdBusinessLogicEvents].[dbo].[ProductionLots]  where AggregateId=\\\'be308d6e-cd50-4e89-bc1c-7476911e8990\\\'  order by Created  FROM [DHPlantWmsBusinessLogicEvents].[dbo].[WarehouseOrders]  where AggregateId=\\\'9b573e79-92da-49b7-bfd6-44259f16a5e8\\\'  order by Created{code} !image-2023-02-20-15-20-41-349.png! ""\', ""Comment 5: \' !screenshot-1! \'"", ""Comment 6: \'{code:java}Validation failed: -- Warehouse order should be in created status -- Warehouse order should be in processable status -- Warehouse order should be in progress -- Warehouse order should be execution pending -> Validation failed: -- WarehouseOrderShouldBeCreatedMessage -- WarehouseOrderShouldBeProcessableMessage -- WarehouseOrderShouldBeInProgressMessage -- WarehouseOrderShouldBeExecutionPendingMessage{code}!image-2023-02-21-11-50-53-383!!image-2023-02-21-11-51-20-475!\'"", ""Comment 7: \'hi Any news for this issue\'"", ""Comment 8: \'ustalenia stand up.\'"", ""Comment 9: \'Hello"", ""Comment 10: please provide information on how the operator made the change for this PLR and what operations were performed on the WO - we need a scenario for the error.In the log there is information that the change in the amount of PLR will not be processed due to the status of the WO.\'"", ""Comment 11: \'hi"", ""Comment 12: we do not have information how they can do that. just guess they align quantity but system get quantity in initial request\'"", ""Comment 13: \' !screenshot-2! mają ustawione na true dla AutomaticWoIpExecution\'"", ""Comment 14: \'The error occurred once"", \'Comment 15: checking the logs there is no conclusive reason.The update did not pass to the WO due to the status of the document.If the problem recurs we can suggest RCA\', ""Comment 16: it should be treated as an incident.\'"", ""Comment 17: \'so"", ""Comment 18: what will be next? close and RCA?\'"", ""Comment 19: \'Hi.We suggest to create RCA if the situation repeats - for a new case. We can create rca now and suspend them if the problem is reproducible (until the next case).\'"", ""Comment 20: \'no need to create DCA And please close the ticket\']""]\nRelated Issues:\n[]\n\n### End'}"
449,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8583\n\n### Instruction:\nPlease help to check this issue in Dong Nai Plant ( 0461).\r\nVT-67/2/23 : WO(PD)-30/2/23 and WO(PD)-29/2/23 has canceled but stock unit has relaeased and can not pick . \n\n### Response:\n[""Comment 1: [\'!image!!image-1!!image-2!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Everything looks correct. Stock has been moved to Released location. You should move it to desire location Using WMS functionality.On provided WO(PD) documents destination location was set to location FG.Please"", ""Comment 4: let me know if you expect any additional actions from us regarding this issue?\'"", \'Comment 5: ""{code:java}select * from [WarehouseOrders] where DocumentPrefix = \\\'wo(pd)\\\' and DocumentNumber in (29,30) and DocumentMonth=2 and DocumentYear=2023select * from WarehouseOrderElements where id in (\\\'AF6579BB-9210-46B2-BB50-37B0A6C0E15A\\\',\\\'FD0AFFE2-46C2-439F-9AFB-E487376AC959\\\')select * from StorageLocations where id =\\\'19C7E203-C6AF-40F9-A928-23D0B721C41E\\\'select * from [dbo].[WarehouseDispatches] where WarehouseOrderDocumentNumber in (\\\'WO(PD)-29/2/23\\\',\\\'WO(PD)-30/2/23\\\') order by documentselect * from [dbo].[WarehouseDispatchElements] where id in (\\\'A147676A-8D79-4AEC-8E3A-0986F05331CB\\\',\\\'58937AE6-01C2-4FCD-80A6-15AEF7EF7042\\\',\\\'DC2A9023-FBCF-4036-93D0-1D76A8F62373\\\',\\\'F58B8972-49B6-47D6-85DD-24A9BB80DCC7\\\',\\\'E007842D-F61E-411B-B5A5-32CE10FD50F2\\\',\\\'E076C276-314E-4096-A00D-590B78140C03\\\',\\\'DB060C7A-2C21-4415-A5B4-81C44E23ACB1\\\',\\\'991988EC-87D7-446E-A384-BCEAAE4845AF\\\',\\\'9B01E892-BE41-47B6-95BD-D5C74151A3BF\\\',\\\'95A44B47-4B41-4F48-BDF8-DC7DBEEA59B4\\\'){code}""\', ""Comment 6: \'HiI understand. You can close this ticket. Thank u.\']""]\nRelated Issues:\n[]\n\n### End'}"
450,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8582\n\n### Instruction:\nWe have problem to close some warehouse order (IP), when we try to confirm, system shows an error message.\r\n\r\nWO(IP)-151/5/22\r\nWO(IP)-239/5/22\r\nWO(IP)-255/6/22\r\n\r\nCould you close ?\r\n\r\nThank you\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Nie ma już z taką datą.!image-2023-02-17-18-50-55-204.png!\'"", ""Comment 4: \'elementy są executed!image-2023-02-17-18-59-30-565.png!\'"", ""Comment 5: \'!image-2023-02-20-09-19-26-318.png!\'"", ""Comment 6: \'wszystko wydane już.\'"", \'Comment 7: ""{code:java}update w  set status=50 FROM [DHPlantWmsBusinessLogicMain].[dbo].[WarehouseOrders] w where Document in (\\\'WO(IP)-151/5/22\\\',\\\'WO(IP)-239/5/22\\\',\\\'WO(IP)-255/6/22\\\'){code}""\', ""Comment 8: \'HiPriscyla"", \'Comment 9: documents were verified and the status corrected to executed\', ""Comment 10: please check.\'"", ""Comment 11: \'Hello,can I count on an update of this ticket?Thank you and regards.\'"", ""Comment 12: \'Hello Piotr,I checked and documents now are correct. You can close this task.Thank you\'"", ""Comment 13: \'Hello"", ""Comment 14: Priscyla.\\\\rThank you for confirmation.\']""]\nRelated Issues:\n[]\n\n### End'}"
451,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8581\n\n### Instruction:\nsp-b/0541 BACK TO ENTRY\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 2: ""Hello,It\\\'s in Entry again.Regards""]\']\nRelated Issues:\n[]\n\n### End'}"
452,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8580\n\n### Instruction:\nI\'ll write an e-mail\r\n\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 2: ""Hi [~CJong@deheus.com],Is it actual? We didn\\\'t get any details in this topic.Regards""\', ""Comment 3: \'{color:black}Hi Damian,{color} {color:black}{color} {color:black}How irritating that my tickets are not communicated with you…{color} {color:black}See enclosed my message. Awaiting your feedback.{color}  {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Christinede{color} |{color:#000001} {color} |{color:#000001} Jong{color} |  {color:#000001}MedewerkerContractadministratie{color} | | |{color:windowtext}{color} !image001! <[https://www.de-heus.nl/]>{color:black}{color} | |  *{color:#006FB7} *DEHEUSVOEDERSB.V.*{color}* | | | |{color:#000001} Postbus396 6710BJEde \\\\u200b{color} | |{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} | | |{color:#000001} T:0318675567{color} |  {color:#000001}KvK14626985{color}   _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_{color}_[ _{color:#000001} _DeHeusVoeders_{color}_|https://www.de-heus.nl/privacy-beleid] _{color:#000001} _._{color}_ | | !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | | !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} | | !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} |        *Van:* Damian Świstek (Jira) <jira@kotrak.com>   *Verzonden:* dinsdag 21 februari 2023 10:02  *Aan:* Jong"", ""Comment 4: Christine de <CJong@deheus.com>  *Onderwerp:* DGS-8580 102038 Several customers visible in Feed Sale   Failed to add the following attachment to this issue because the file name is invalid.- 102038_Several_customers_visible_in_Feed_Sale___>_DGS_8580.eml\'"", ""Comment 5: \'Hi Christine,Unfortunately I still cannot see any attachment. Could you try enclose it by Jira directly from this link [https://helpdesk.kotrak.com/servicedesk/customer/portal/56/DGS-8580]? maybe name is not valid as I see in your last comment to this task. You can also send it to me by email.!image-2023-02-22-12-23-00-174.png!Regards\'"", ""Comment 6: \'{color:black}Hi Damian,{color} {color:black}{color} {color:black}Working well this new process of tickets{color} {color:black}☹{color}{color:black}{color} {color:black}Not up to you"", \'Comment 7: I know{color} {color:black}😊{color}{color:black}{color} {color:black}{color} {color:black}See below my mail{color} {color:black}😊{color}   *Van:* Jong\', \'Comment 8: Christine de   *Verzonden:* vrijdag 17 februari 2023 14:01  *Aan:* NL Servicedesk IT [nlservicedesk@deheus.com|mailto:nlservicedesk@deheus.com]  *CC:* Geijtenbeek\', \'Comment 9: Bert [BGeijtenbeek@deheus.com|mailto:BGeijtenbeek@deheus.com]  *Onderwerp:* 102038 Several customers visible in Feed Sale --> DGS-8580  {color:black}Hi,{color}{color:black}{color} {color:black}{color} {color:black}This should not happen..{color} {color:black}I am working in FE-N/0005 belonging to customer 102038.{color}{color:black}{color} !image001!{color:black}{color}{color:black}{color} {color:black}Feed movement to next round shows these round numbers?{color} {color:black}Only 102038/0042/0002 should be visible.{color} {color:black}{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Christinede{color} |{color:#000001} {color} |{color:#000001} Jong{color} |  {color:#000001}MedewerkerContractadministratie{color} | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image002!{color:black} <[https://www.de-heus.nl/]>{color} | |  *{color:#006FB7} *DEHEUSVOEDERSB.V.*{color}* | | | |{color:#000001} Postbus396 6710BJEde \\\\u200b{color} | |{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} | | |{color:#000001} T:0318675567{color} |  {color:#000001}KvK14626985{color}   _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | | !image003! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | | !image004! <[https://twitter.com/de_heus_voeders]>{color:black}{color} | | !image005! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image006! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} |        *Van:* Damian Świstek (Jira) <jira@kotrak.com>   *Verzonden:* woensdag 22 februari 2023 12:25  *Aan:* Jong\', ""Comment 10: Christine de <CJong@deheus.com>  *Onderwerp:* DGS-8580 102038 Several customers visible in Feed Sale   !image001-1!!image007!\'"", \'Comment 11: ""Hi Christine,It\\\'s quite new requirement modified in task[https://helpdesk.kotrak.com/servicedesk/customer/portal/56/DGS-8523] - \\\'Moving feed to different round on Feed sale - showing rounds also from invoice customer\\\'Now it\\\'s possible to choose also rounds for other customers if the same invoice customer is on both customers.For example if customer 102038 has the same Invoice customer = 004265 on Customer card like customer 014814 it\\\'s possible to choose rounds of this customer.!image-2023-02-22-15-17-39-753.png!!image-2023-02-22-15-17-32-219.png!Regards,Damian""\', ""Comment 12: \'{color:black}Good morning Damian,{color} {color:black}{color} {color:black}Ah okay{color} {color:black}😊{color}{color:black}{color} {color:black}It was for me the first time I saw this.{color} {color:black}{color} {color:black}No problem then there. Case solved{color} {color:black}😊{color}{color:black}{color} {color:black}{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Christinede{color} |{color:#000001} {color} |{color:#000001} Jong{color} |  {color:#000001}MedewerkerContractadministratie{color} | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.de-heus.nl/]>{color} | |  *{color:#006FB7} *DEHEUSVOEDERSB.V.*{color}* | | | |{color:#000001} Postbus396 6710BJEde \\\\u200b{color} | |{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} | | |{color:#000001} T:0318675567{color} |  {color:#000001}KvK14626985{color}   _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | | !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | | !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} | | !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} |        *Van:* Damian Świstek (Jira) <jira@kotrak.com>   *Verzonden:* woensdag 22 februari 2023 15:26  *Aan:* Jong"", ""Comment 13: Christine de <CJong@deheus.com>  *Onderwerp:* DGS-8580 102038 Several customers visible in Feed Sale   !image006!!image007-1!\'"", ""Comment 14: \'Damian,We reconsidered this. For NAS please only make visible the same customer number"", ""Comment 15: actual round and next round. No other customer numbers.This is error sensitive.Thanks for your help.Christine\']""]\nRelated Issues:\n[\'DGS-8523\']\n\n### End'}"
453,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8579\n\n### Instruction:\nI\'ll write an e-mail\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 2: ""Hi [~CJong@deheus.com],Is it actual? We didn\\\'t get any details in this topic.Regards""\', ""Comment 3: \'[~damian.swistek@kotrak.com] odpowiedź klienta która nie wpadła do portalu (bo była mailem..)*Onderwerp:* FW: DGS-8579 Migration document not on FS 100753/0039/0001Hi Damian,It is indeed actual. Don’t know why this is not communicated with you.We are working on closure of our NAS rounds. ID 35468 is not visible on the financial statement.This should be solved.||Metvriendelijkegroet,\\\\u200b\\\\u200b\\\\u200b\\\\u200b||||Christinede||Jong|||MedewerkerContractadministratie|||\'"", \'Comment 4: ""Hi [~CJong@deheus.com]It\\\'s caused by data on this PIThere is no Reference on this document\', ""Comment 5: is it correct?Wen reference will be filled in this invoice will appear on Financial statement.Please let us know if we should filled in Reference in this field (I\'m not sure that you can do it"", ""Comment 6: it\'s Archived and sent to Milas).Otherwise (if this invoice is right) we need to adjust displaying invoices on Financial statement"", ""Comment 7: it\'s little different than on Round"", ""Comment 8: then on Round it\'s visible"", ""Comment 9: but on Financial Statement it\'s not visible.!image-2023-03-06-12-38-48-484.png!Please add remarks and responses directly in tickets in Jira as a comments"", \'Comment 10: otherwise mails could stuck somewhere (when you sent information on e-mail adress jira@kotrak.com).Regards""\', \'Comment 11: ""Hi Damian\', \'Comment 12: I don\\\'t now why reference is not filled. Cause it s a migration post.You can add reference SL008146.I think it should not have been sent to MILAS.Please modify.Thanks!Christine""\', ""Comment 13: \'Hi Christine,Reference has been filled in and now PI is visible on Financial statement.Please verify that is correct.!image-2023-03-07-15-25-19-352.png!!image-2023-03-07-15-26-40-547.png!Regards\'"", ""Comment 14: \'Could we close the task?\'"", ""Comment 15: \'{color:black}Good morning!{color} {color:black}{color} {color:black}Yes Damian"", \'Comment 16: please mark it as done.{color} {color:black}{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Christinede{color} |{color:#000001} {color} |{color:#000001} Jong{color} |  {color:#000001}MedewerkerContractadministratie{color} | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.de-heus.nl/]>{color} | |  *{color:#006FB7} *DEHEUSVOEDERSB.V.*{color}* | | | |{color:#000001} Postbus396 6710BJEde \\\\u200b{color} | |{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} | | |{color:#000001} T:0318675567{color} |  {color:#000001}KvK14626985{color}   _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | | !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | | !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} | | !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} |        *Van:* Damian Świstek (Jira) <jira@kotrak.com>   *Verzonden:* maandag 27 maart 2023 13:47  *Aan:* Jong\', ""Comment 17: Christine de <CJong@deheus.com>  *Onderwerp:* DGS-8579 Migration document not on FS 100753/0039/0001   \']""]\nRelated Issues:\n[]\n\n### End'}"
454,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8578\n\n### Instruction:\nOrder not sync to DHP CIteurup from DHC,, Evolution Service is Running and BUsiness platform is running.\r\n\r\nCTP SO 26329 for example\n\n### Response:\n[""Comment 1: [\'!image-2!\'"", ""Comment 2: \'Hi,As per taskDGS-8575,currently we do not have access to DHP application server. Waiting for your feedback in email communication.Regards\'"", ""Comment 3: \'Currently"", ""Comment 4: my user also does not have access to below server to check DHC.Regards!image-2023-02-17-11-22-24-284.png!\'"", ""Comment 5: \'please wait"", ""Comment 6: my team will add your credential first\'"", ""Comment 7: \'Dostęp do servera DHC na credentialach Piotrka:!image-2023-02-17-11-31-07-977.png!\'"", ""Comment 8: \'Waiting for your feedback then\'"", ""Comment 9: \'Hi"", ""Comment 10: please try to connectApplication and Database DHP Welgro (10.62.15.13 and  10.62.15.6)\'"", ""Comment 11: \'What obout terminal server? Please"", ""Comment 12: see my reply via email\'"", ""Comment 13: \'Hi can we have teams call?\'"", ""Comment 14: \'sure\'"", ""Comment 15: \'Hi aleksandra,Do you already fix that? Our operational waiting for order.\'"", ""Comment 16: \'Klient robi restart usługi"", ""Comment 17: nie mamy uprawnień na restart usługi.była luka!image-2023-02-17-14-23-01-390.png!\'"", ""Comment 18: \'!image-2023-02-17-14-24-35-843.png!\'"", ""Comment 19: \'After restarted serviceDHCServiceClient orders have been processed.\'"", ""Comment 20: \'Actually we have done restart the service 3 times today to solve this problem"", ""Comment 21: and this is the 4th. How about after restart and then next order still not sync to dhp? Please give us solution.\'"", ""Comment 22: \'In reference to the conversation please extend the permissions to restart the serviceDHCServiceClient for my account.\'"", ""Comment 23: \'!image-2023-02-17-14-54-40-451.png!za niski poziom logowania usługi.\'"", ""Comment 24: \'Required entity was not found. -jest wyników 10260 do synchry.\'"", ""Comment 25: \'Samples"", \'Comment 26: analyzes and analysis results had to be sent from DHP. Configuration changes were required after running the synchronization for this data.Additionally\', ""Comment 27: the change affected the factory -Wirifa,Pasuruan.And for the factory Pasuruan and only here you still need to do a service restart.\'"", ""Comment 28: \'wyjaśnione przez teams - powiązane zDGS-6921.rozwiązaniem była zmiana dla externalID na numer planta (oprócz tego w tasku wcześniejszym)!image-2023-02-17-17-48-47-661.png!\'"", ""Comment 29: \'Hi piotr,Integration between DHP and DHC already smooth"", ""Comment 30: with monitoring from 17 midnight until 19 feb. Thank you for your support\'"", ""Comment 31: \'Hi"", ""Comment 32: thanks for confirming.As for the reason as I mentioned the problem was related to the export of samples and analysis results. A change was required to set correct the definition for the production areas.I am closing this task.\']""]\nRelated Issues:\n[]\n\n### End'}"
455,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8577\n\n### Instruction:\nCL000020433 is in DHC but not in DHP Andel\r\n\r\nPlease investigate.\r\n\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Please verify I can see it in DHP :!image-2023-02-17-11-29-27-170.png!\'"", ""Comment 3: \'Ah"", ""Comment 4: it was at ASN and not on the Trip tab (where we were looking at). Thanks!\']""]\nRelated Issues:\n[]\n\n### End'}"
456,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8576\n\n### Instruction:\nlinked production areas are failing to auto generate recipes, again.\r\n\r\nhttps://helpdesk.kotrak.com/servicedesk/customer/portal/56/DGS-7271\n\n### Response:\n[""Comment 1: [\'Reklamacja do poprzedniego rca i zgłoszenia - opis w zlinkowanym pliku.\'"", \'Comment 2: ""Hi,We put this ticket on hold per last comment inDGS-8545. Waiting for Thabile when she\\\'s back to office.Regards""\', ""Comment 3: \'Dear Thabile,Please"", ""Comment 4: let us know when you return.Regards\'"", ""Comment 5: \'Hello"", ""Comment 6: please take this off of hold i have commented in DGS-8545\'"", \'Comment 7: ""Hello,Thank you. I\\\'ve passed this issue to our Dev Team.Regards""\', \'Comment 8: ""Hello [~tdladla@deheus.com]\', ""Comment 9: for production area this won\'t work since non of warehouses are assigned to this production area. Because of performance issue we limited technology generation to only those production area that have orders created. Because non of warehouse is assigned to this production area"", \'Comment 10: non of order will be assigned to it and non packed technology will be generated for this particular production area. If you would like to change this process\', \'Comment 11: please contact Product Owner of DH Country (Wijnand) to decide if it\\\'s global or local change and create GDC for you.""\', ""Comment 12: \'Hi,Any feedback? Can we close this task?Regards\'"", \'Comment 13: ""Still discussing with the business. I\\\'ll be on leave till Wed next week. Will respond after.""\', ""Comment 14: \'Sure"", ""Comment 15: waiting for you then :)Best regards\'"", ""Comment 16: \'Hi,Can we close this task?Regards\'"", \'Comment 17: ""Hi AleksandraI\\\'ve escalated it to NL (Theo). I\\\'m waiting for a response. You can place it on hold.Regards""\', ""Comment 18: \'Hi Rey,Sure. Thank you for your information then.Regards\'"", ""Comment 19: \'We can close the ticket. We will be opening a GDC.\'"", ""Comment 20: \'Thank you"", ""Comment 21: Rey.Regards\']""]\nRelated Issues:\n[\'DGS-8545\']\n\n### End'}"
457,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8575\n\n### Instruction:\nPLR DHP Not Sync to DHC from 13:27 but service to DHC is running.\n\n### Response:\n[""Comment 1: [\'Hello,\\\\r\\\\rWe are investigating your issue. We will inform you about the solution as soon as possible.\\\\r\\\\rRegards\\\\r\\\\r\'"", ""Comment 2: \'Could you please provide some examples number for plr’s and the ip addresses and credentials for Citeureup (Welgro) ( application and database?)\'"", ""Comment 3: \'We already restart dhc on citeurup dhp server 3times"", \'Comment 4: after restart plr come to dhc. But I think there is something wrong\', ""Comment 5: wo don’t need to restart service as often as that.\'"", ""Comment 6: \'As I asked you we do no have any information how to log toCiteureup (Welgro) enviroment.So pleaseCould you please provide some examples number for plr’s and the ip addresses and credentials for Citeureup (Welgro) ( application and database?)\'"", ""Comment 7: \'IP DHP Welgro  terminal server : 10.62.15.13IP DHP Database Welgro : 10.62.15.6!image-2!\'"", ""Comment 8: \'User and password"", ""Comment 9: please\'"", ""Comment 10: \'please type your email"", ""Comment 11: I will ask to infrastructure team to add your credential\'"", ""Comment 12: \'If the PLr are in dhc may we change the priority to p2 ?In this task we have focused on clearingandunblocking the process. We can look up for the reason but if analisys will be more time consumingwe may raise RootCause Analysis (RCA)task for you.Please"", ""Comment 13: let us knowhow you wish us to proceed.\'"", ""Comment 14: \'Tha email for credentials has been already sent to you and Eric\'"", ""Comment 15: \'PLR not in DHC yet\'"", ""Comment 16: \'HiPLR already in DHC please closed the ticket.\']""]\nRelated Issues:\n[]\n\n### End'}"
458,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8574\n\n### Instruction:\nHi\r\n\r\nWe need to register this 85-W03A4A UL for PLR 0851150223005 on WO(IP)-147/2/23 document.\r\nWhen we try to register, system shows an message error: *Requested quantity for unit load exceeds available produced quantity. Unit load cannot be registered.*\r\n\r\nHowever, Produced Quantity = 2030kg; we already registered 2010kg and this 85-W03A4A UL is for 20kg\r\nI don\'t understand why system doesn\'t allow to register it.\r\n\r\nThe truck will arraive the factory tomorrow morning to load it. Could you please fix, identify why this i happening or teach us how to solve it?\r\n\r\nThank you very much\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'!image-2023-02-17-07-36-34-592.png!\'"", \'Comment 4: \\\'{code:java}2023-02-17 03:39:41 (9c2448e3-ddcc-42f1-87a3-2861b91583e7/Plant.WMS.BusinessLogic/BR-1-SV-VM0604/7432/199) [Error] Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware - Error during request{  ""scheme"": ""http""\', \'Comment 5:  ""host"": {    ""Value"": ""br-1-sv-vm0604.mubbrasil.local:85""\', \'Comment 6:    ""HasValue"": true\', \'Comment 7:    ""Host"": ""br-1-sv-vm0604.mubbrasil.local""\', \'Comment 8:    ""Port"": 85  }\', \'Comment 9:  ""path"": ""/api/WarehouseIntake/registerMultipleIntakeFromProduction""\', \'Comment 10:  ""queryString"": []\', \'Comment 11:  ""requestBody"": ""{\\\\\\\\""warehouseOrderId\\\\\\\\"":\\\\\\\\""bccb4cef-3798-41ce-9951-21664aec752b\\\\\\\\"",\\\\\\\\""warehouseOrderElementNo\\\\\\\\"":1,\\\\\\\\""bagSize\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":30},\\\\\\\\""unitLoads\\\\\\\\"":[{\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":20},\\\\\\\\""unitLoadType\\\\\\\\"":40,\\\\\\\\""barcode\\\\\\\\"":{\\\\\\\\""code\\\\\\\\"":\\\\\\\\""85-W03A4A\\\\\\\\""}}]}""}.Kotrak.Common.Application.Exceptions.BusinessLogicException: Requested quantity for unit load exceeds available produced quantity. Unit load cannot be registered. ---> Kotrak.Common.Application.Exceptions.BusinessLogicException: Requested quantity for unit load exceeds available produced quantity. Unit load cannot be registered.   at Kotrak.Common.Infrastructure.Interceptors.ApiReferenceExceptionInterceptor.Intercept(IInvocation invocation)   at Castle.DynamicProxy.AbstractInvocation.Proceed()   at Plant.WMS.BusinessLogic.Domain.WarehouseIntakes.Services.IntakeFromProductionDomainService.RegisterMultipleIntakeFromProduction(RegisterMultipleIntakeFromProductionDomainDataStructure dataStructure) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Domain\\\\\\\\WarehouseIntakes\\\\\\\\Services\\\\\\\\IntakeFromProductionDomainService.cs:line 69   at Plant.WMS.BusinessLogic.Application.WarehouseIntake.WarehouseIntakeFromProductionService.RegisterMultipleIntakeFromProduction(RegisterMultipleIntakeFromProductionDataStructure dataStructure\', \'Comment 12: WarehouseOrder warehouseOrder\', \'Comment 13: WarehouseOrderElement warehouseOrderElement\', \'Comment 14: Owner owner) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Application\\\\\\\\WarehouseIntake\\\\\\\\WarehouseIntakeFromProductionService.cs:line 410   at Plant.WMS.BusinessLogic.Application.WarehouseIntake.WarehouseIntakeFromProductionService.RegisterMultipleIntakeFromProduction(RegisterMultipleIntakeFromProductionDataStructure dataStructure) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Application\\\\\\\\WarehouseIntake\\\\\\\\WarehouseIntakeFromProductionService.cs:line 111   at Plant.WMS.BusinessLogic.Application.WarehouseIntake.Handlers.RegisterMultipleIntakeFromProductionCommandHandler.Handle(RegisterMultipleIntakeFromProductionCommand command) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Application\\\\\\\\WarehouseIntake\\\\\\\\Handlers\\\\\\\\RegisterMultipleIntakeFromProductionCommandHandler.cs:line 36   at Kotrak.Common.Infrastructure.Commands.CommandEnvironment.Run[TCommand](TCommand command)   at Kotrak.Common.Infrastructure.Commands.Decorators.IntercontextEventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command)   at Kotrak.Common.Infrastructure.Commands.Decorators.EventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command)   at Kotrak.Common.Infrastructure.Commands.Decorators.ValidationCommandEnvironmentDecorator.Run[TCommand](TCommand command)   at Castle.DynamicProxy.AbstractInvocation.Proceed()   at Kotrak.Common.Infrastructure.Interceptors.LoggingInterceptor`1.Intercept(IInvocation invocation)   at Castle.DynamicProxy.AbstractInvocation.Proceed()   at Kotrak.Common.Infrastructure.Commands.Decorators.HistoryGateDecorator.Dispatch[TCommand](TCommand command)   at Plant.WMS.BusinessLogic.Infrastructure.Api.Controllers.WarehouseIntakeController.RegisterMultipleIntakeFromProduction(RegisterMultipleIntakeFromProductionViewModel viewModel) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Infrastructure.Api\\\\\\\\Controllers\\\\\\\\WarehouseIntakeController.cs:line 329   at lambda_method46691(Closure \', \'Comment 15: Object \', \'Comment 16: Object[] )   at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor.SyncActionResultExecutor.Execute(IActionResultTypeMapper mapper\', \'Comment 17: ObjectMethodExecutor executor\', \'Comment 18: Object controller\', \'Comment 19: Object[] arguments)   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeActionMethodAsync()   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next\', \'Comment 20: Scope& scope\', \'Comment 21: Object& state\', \'Comment 22: Boolean& isCompleted)   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeNextActionFilterAsync()--- End of stack trace from previous location ---   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Rethrow(ActionExecutedContextSealed context)   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next\', \'Comment 23: Scope& scope\', \'Comment 24: Object& state\', \'Comment 25: Boolean& isCompleted)   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeInnerFilterAsync()--- End of stack trace from previous location ---   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeFilterPipelineAsync>g__Awaited|20_0(ResourceInvoker invoker\', \'Comment 26: Task lastTask\', \'Comment 27: State next\', \'Comment 28: Scope scope\', \'Comment 29: Object state\', \'Comment 30: Boolean isCompleted)   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker\', \'Comment 31: Task task\', \'Comment 32: IDisposable scope)   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker\', \'Comment 33: Task task\', \'Comment 34: IDisposable scope)   at Microsoft.AspNetCore.Routing.EndpointMiddleware.<Invoke>g__AwaitRequestTask|6_0(Endpoint endpoint\', \'Comment 35: Task requestTask\', \'Comment 36: ILogger logger)   at Swashbuckle.AspNetCore.SwaggerUI.SwaggerUIMiddleware.Invoke(HttpContext httpContext)   at Swashbuckle.AspNetCore.Swagger.SwaggerMiddleware.Invoke(HttpContext httpContext\', ""Comment 37: ISwaggerProvider swaggerProvider)   at Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware.Invoke(HttpContext httpContext)   --- End of inner exception stack trace ---{code}\'"", ""Comment 38: \'Na unitloadzie kody z reworku?!image-2023-02-17-08-49-43-882.png!!image-2023-02-17-08-57-42-838.png!\'"", ""Comment 39: \'Bulk miał rezerewację do PLR 0851150223021 i jego quantity on hand była 0"", ""Comment 40: dlatego nie można było zarejestrować palety. Po usunięciu rezerwacji z PLRa paleta została zarejestrowana. !screenshot-1!  !screenshot-2! \'"", \'Comment 41: ""Bulk had its reservation forPLR 0851150223021 and its quantity = 0 that is why you couldn\\\'t register a pallet. After removing the reservation\', \'Comment 42: pallet has been registered.Please verify,Regards!image-2023-02-17-09-08-01-591.png!""\', ""Comment 43: \'Hi AleksandraIs it possible to know the source of the request for reservation?I mean"", \'Comment 44: who made this reservation? PCS\', \'Comment 45: user (which user?)And also why we have a document on reservation column\', ""Comment 46: but no reserved quantity?Thank you very much\'"", ""Comment 47: \'!image-2023-02-17-13-55-59-558.png!Po finish jest jeszcze 181 eventów:!image-2023-02-17-14-11-18-404.png!\'"", ""Comment 48: \'Dear Maicon,PCS did not indicate the delivery and per plant configuration"", \'Comment 49: delivery had to be indicated by the user.What I can check are the events on PLR. The last event made by PCS was ProductionLotFinishedEvent. Then\', \'Comment 50: there are 180 updating events\', \'Comment 51: done by uservsantanna and today by admin (which is Kotrak user) and uservsantanna again including Confirm event.To reply your question:_And also why we have a document on reservation column\', \'Comment 52: but no reserved quantity_?>> We havecolumn ""Quantity"" with all stock and ""Quantity on hand"",that shows available stock - quantity of reservations.!image-2023-02-17-14-37-01-649.png!\\\'\', ""Comment 53: \'Hi AleksandraThanks for the information.You can close this task.Thank you very much\'"", ""Comment 54: \'Thank you\']""]\nRelated Issues:\n[]\n\n### End'}"
459,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8573\n\n### Instruction:\nWe need to make consumption in production of item SUR6908-MD-S25 lot number 0891020223037, but this lot number is associated in the sales order/customer with entrusted configuration.  (The lot number returned to factory to be reprocessed).\r\nWe need urgent use this production in an PLR as ingredient, but system not allow to use. Could you remove this configuration entrusted and link with SO to be possible use it?\r\n\r\nThank you\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'We have removed check entrusted,!image-2023-02-16-19-39-57-035.png!please check if any further changes are required.\'"", ""Comment 3: \'{code:java}  update d  set del_cstid=null  FROM [DHPlant_RC].[dbo].[Delivery] d  where Del_Id = 244001{code}\'"", ""Comment 4: \'We added as ingredient in production 0891140223027"", \'Comment 5: but when we try to close production\', \'Comment 6: is showing error message yet\', ""Comment 7: missing stock. Could you check it? \'"", ""Comment 8: \'!MicrosoftTeams-image (49)-1!!MicrosoftTeams-image (47)-1!\'"", ""Comment 9: \'{{update [DHPlant_RC].[dbo].[WarehouseStocks] set [Wst_CstId]=null where Wst_ArtId = 21817 and Wst_DelId = 244001}}\'"", ""Comment 10: \'You should be able to close this PLR. Please check.\'"", ""Comment 11: \'Hi Bartłomiej Now it worked.You can close this task.Thank you very much!\'"", ""Comment 12: \'[[DHP 2.X] Entrusted customer - stock for item.|onenote:https://kotrak.sharepoint.com/sites/erpasysta/Shared%20Documents/Baza%20wiedzy/Baza%20Wiedzy%20-%20ERPSD/Klienci/DEHEUS/DEHEUS%20APPLICATIONS/RPA/Baza%20wiedzy.one#%5bDHP%202.X%5d%20Entrusted%20customer%20-%20stock%20for%20item&section-id=\\\\\\\\{A2F09CD6-A23A-42F3-92F5-ED66B521455B}&page-id=\\\\\\\\{6C364C55-E55B-487F-87F7-BED48EA81D86}&end] ([Widok sieci Web|https://kotrak.sharepoint.com/sites/erpasysta/_layouts/OneNote.aspx?id=%2Fsites%2Ferpasysta%2FShared%20Documents%2FBaza%20wiedzy%2FBaza%20Wiedzy%20-%20ERPSD&wd=target%28Klienci%2FDEHEUS%2FDEHEUS%20APPLICATIONS%2FRPA%2FBaza%20wiedzy.one%7CA2F09CD6-A23A-42F3-92F5-ED66B521455B%2F%5BDHP%202.X%5D%20Entrusted%20customer%20-%20stock%20for%20item%7C6C364C55-E55B-487F-87F7-BED48EA81D86%2F%29])\']""]\nRelated Issues:\n[]\n\n### End'}"
460,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8572\n\n### Instruction:\nRealized weights do not arrive in DHP, which means no packing slips are being printed.\r\n\r\nSO example is SO000067871.\r\n\r\nPlease check, thanks!\n\n### Response:\n[""Comment 1: [\'!afbeelding!\'"", ""Comment 2: \'Hello"", ""Comment 3: We kindly inform you that wecurrentlyare processing another Priority1 task underDGS-8571We will revert to processing your task as soon as possible.Regards\'"", ""Comment 4: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 5: \'spora kolejka dla Proda:!image-2023-02-16-14-44-05-512.png!aktualnie schodzi\'"", ""Comment 6: \'Can I get information on what VT the realization should be? because for trip there is also no connection as below:!image-2023-02-16-15-23-36-849.png!\'"", ""Comment 7: \'kolejka z prod zeszła"", ""Comment 8: co odpiszą na nasz ostatni komentarz - realizacja SO.\'"", ""Comment 9: \'Could you please confirm if we can close this task?Regards\'"", ""Comment 10: \'Could you please confirm if we can close this task?Regards\'"", ""Comment 11: \'Could you please confirm if we can close this task?Regards\'"", ""Comment 12: \'Oops"", ""Comment 13: sorry. Yes you can.\']""]\nRelated Issues:\n[]\n\n### End'}"
461,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8571\n\n### Instruction:\nPlease remove the additional technologies for Andel-West: AW967352: This technology is wrong and now blocking the sending of recipe 966715\n\n### Response:\n[""Comment 1: [\'!afbeelding!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Hello"", ""Comment 4: you may check DGS-8572 first: This one has less priority\'"", ""Comment 5: \'Just to confirm"", ""Comment 6: all three subversions?\'"", ""Comment 7: \'Sure"", ""Comment 8: will do\'"", ""Comment 9: \'All three subversions indeed\'"", ""Comment 10: \'And what about the last one for item code 967352?!image-2023-02-16-14-06-58-989.png!\'"", ""Comment 11: \'For below items"", \'Comment 12: additional technology has been removed. Please\', ""Comment 13: let me know what about the fourth item with code 967352!image-2023-02-16-14-28-09-326.png!\'"", \'Comment 14: ""I think that last one is correct and shouldn\\\'t be removed""\', ""Comment 15: \'Sure. So the three have been removed. Please"", ""Comment 16: let me know if we can close this task.Regards\'"", ""Comment 17: \'Thanks"", ""Comment 18: ticket can be closed\']""]\nRelated Issues:\n[]\n\n### End'}"
462,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8570\n\n### Instruction:\nProśba o skorygowanie od strony bazy naliczonej amortyzacji podatkowej środków trwałych (lista w załączniku) w module ŚT oraz weryfikacja poniższego środka, aby nie naliczała się amortyzacja podatkowa tylko bilansowa w przyszłości.\n\n### Response:\n[""Comment 1: [\'!1_d23311cb039e4c8fb9847b7bf257dbe9![^do skorygowania wartość podatkowa.xlsx] _(12 kB)_\'"", ""Comment 2: \'Hi"", ""Comment 3: Fixed assets from xls file has been corrected. Please verify. When you add new fixed asset and you want to make only balance depreciation (without tax depreciation)  you should add fixed asset like below  !screenshot-1! and on OT document as below !screenshot-2! Please let me know if we can close this issue?\'"", ""Comment 4: \'Everything looks good"", \'Comment 5: thanks for help\', ""Comment 6: task to close.\']""]\nRelated Issues:\n[]\n\n### End'}"
463,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8569\n\n### Instruction:\nWhen creating a VT for Shipping Notice (Trip) 7_L000131024, DHP generates an error (see attachment for screenshot). \n\n### Response:\n[""Comment 1: [\'!Error on creating VT!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 3: \\\'{code:java}2023-02-16 11:17:43 (8e91a85d-e516-4d86-8fdb-f2bcf9b5b0b4/Plant.VC.BusinessLogic/DHVD01AP183/1384/190) [Error] Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware - Error during request{  ""scheme"": ""http""\', \'Comment 4:  ""host"": {    ""Value"": ""dhvd01ap183:82""\', \'Comment 5:    ""HasValue"": true\', \'Comment 6:    ""Host"": ""dhvd01ap183""\', \'Comment 7:    ""Port"": 82  }\', \'Comment 8:  ""path"": ""/api/VehicleTicket/createVehicleTicketFromShippingNotice""\', \'Comment 9:  ""queryString"": []\', \'Comment 10:  ""requestBody"": ""\\\\\\\\""09d81845-4001-4beb-92bb-cc641131eeb6\\\\\\\\""""}.System.InvalidOperationException: Sequence contains no matching element   at System.Linq.ThrowHelper.ThrowNoMatchException()   at Plant.VC.BusinessLogic.Application.VehicleTickets.Extensions.VehicleTicketExplicitMapping.GetShippingNoticeElementsRelations(ShippingNotice shippingNotice\', \'Comment 11: IBusinessPartnerRepository businessPartnerRepository\', \'Comment 12: IOrderRepository orderRepository\', \'Comment 13: IItemRepository itemRepository) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\67ba263564c33499\\\\\\\\Plant.VC.BusinessLogic\\\\\\\\Plant.VC.BusinessLogic.Application\\\\\\\\VehicleTickets\\\\\\\\Extensions\\\\\\\\VehicleTicketExplicitMapping.cs:line 332   at Plant.VC.BusinessLogic.Application.VehicleTickets.Services.VehicleTicketService.CreateVehicleTicketFromShippingNotice(AggregateId vehicleTicketId\', \'Comment 14: AggregateId shippingNoticeId\', \'Comment 15: Boolean isPlanned) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\67ba263564c33499\\\\\\\\Plant.VC.BusinessLogic\\\\\\\\Plant.VC.BusinessLogic.Application\\\\\\\\VehicleTickets\\\\\\\\Services\\\\\\\\VehicleTicketService.cs:line 485   at Plant.VC.BusinessLogic.Application.VehicleTickets.CommandHandlers.CreateVehicleTicketFromShippingNoticeCommandHandler.Handle(CreateVehicleTicketFromShippingNoticeCommand command) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\67ba263564c33499\\\\\\\\Plant.VC.BusinessLogic\\\\\\\\Plant.VC.BusinessLogic.Application\\\\\\\\VehicleTickets\\\\\\\\CommandHandlers\\\\\\\\CreateVehicleTicketFromShippingNoticeCommandHandler.cs:line 21   at Kotrak.Common.Infrastructure.Commands.CommandEnvironment.Run[TCommand](TCommand command)   at Kotrak.Common.Infrastructure.Commands.Decorators.IntercontextEventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command)   at Kotrak.Common.Infrastructure.Commands.Decorators.EventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command)   at Kotrak.Common.Infrastructure.Commands.Decorators.ValidationCommandEnvironmentDecorator.Run[TCommand](TCommand command)   at Castle.DynamicProxy.AbstractInvocation.Proceed()   at Kotrak.Common.Infrastructure.Interceptors.LoggingInterceptor`1.Intercept(IInvocation invocation)   at Castle.DynamicProxy.AbstractInvocation.Proceed()   at Kotrak.Common.Infrastructure.Commands.Decorators.HistoryGateDecorator.Dispatch[TCommand](TCommand command)   at Plant.VC.BusinessLogic.Infrastructure.Api.Controllers.VehicleTicketController.CreateVehicleTicketFromShippingNotice(Guid shippingNoticeId) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\67ba263564c33499\\\\\\\\Plant.VC.BusinessLogic\\\\\\\\Plant.VC.BusinessLogic.Infrastructure.Api\\\\\\\\Controllers\\\\\\\\VehicleTicketController.cs:line 762   at lambda_method6625(Closure \', \'Comment 16: Object \', \'Comment 17: Object[] )   at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor.SyncActionResultExecutor.Execute(IActionResultTypeMapper mapper\', \'Comment 18: ObjectMethodExecutor executor\', \'Comment 19: Object controller\', \'Comment 20: Object[] arguments)   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeActionMethodAsync()   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next\', \'Comment 21: Scope& scope\', \'Comment 22: Object& state\', \'Comment 23: Boolean& isCompleted)   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeNextActionFilterAsync()--- End of stack trace from previous location ---   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Rethrow(ActionExecutedContextSealed context)   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next\', \'Comment 24: Scope& scope\', \'Comment 25: Object& state\', \'Comment 26: Boolean& isCompleted)   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeInnerFilterAsync()--- End of stack trace from previous location ---   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeFilterPipelineAsync>g__Awaited|20_0(ResourceInvoker invoker\', \'Comment 27: Task lastTask\', \'Comment 28: State next\', \'Comment 29: Scope scope\', \'Comment 30: Object state\', \'Comment 31: Boolean isCompleted)   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker\', \'Comment 32: Task task\', \'Comment 33: IDisposable scope)   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker\', \'Comment 34: Task task\', \'Comment 35: IDisposable scope)   at Microsoft.AspNetCore.Routing.EndpointMiddleware.<Invoke>g__AwaitRequestTask|6_0(Endpoint endpoint\', \'Comment 36: Task requestTask\', \'Comment 37: ILogger logger)   at Swashbuckle.AspNetCore.SwaggerUI.SwaggerUIMiddleware.Invoke(HttpContext httpContext)   at Swashbuckle.AspNetCore.Swagger.SwaggerMiddleware.Invoke(HttpContext httpContext\', ""Comment 38: ISwaggerProvider swaggerProvider)   at Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware.Invoke(HttpContext httpContext){code}\'"", ""Comment 39: \'!image-2023-02-16-11-43-01-246.png!\'"", ""Comment 40: \'Could you please check if this packing form is correct?!image-2023-02-16-12-48-04-610.png!\'"", ""Comment 41: \'Hi Aleksandra"", ""Comment 42: this looks correct\'"", ""Comment 43: \'Dear Theo,-Z20 is packed"", \'Comment 44: not bulk. Please\', ""Comment 45: see attached settlement type:!image-2023-02-16-14-35-39-054.png!\'"", ""Comment 46: \'Hi Aleksandra"", ""Comment 47: please close this task\'"", ""Comment 48: \'Thank you\']""]\nRelated Issues:\n[]\n\n### End'}"
464,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8568\n\n### Instruction:\nThere is need to back 2 rounds to Active status, because there should be created invoices and now it\'s not possible to choose this rounds on Purchase Invoices because they are closed.\n\n### Response:\n[""Comment 1: [\'Rounds102051/0240/0001 and 102051/0240/0002 have been moved to Active again.\'"", \'Comment 2: ""These 2 documentsSP-M/0328\', \'Comment 3: SP-M/0330 have been sent to Entry to allow delete invoices from these S2P and update rounds on invoices (it\\\'s not possible to update round number on invoices when invoice is on S2P).""\', ""Comment 4: \'More general: could we give Koen"", \'Comment 5: Steffen\', ""Comment 6: Nancy and Peter Moeiliker the rights to re-open rounds? Also they need to be able to set S2P back to entry status whenever they are archived.\'"", ""Comment 7: \'[~grzegorz.materla@kotrak.com]do dodania dla tych userów uprawnienia do rozpoczyniania nowego procesu. Można stworzyć osobną rolę do tego"", \'Comment 8: niewykluczone\', ""Comment 9: że dojdą w przyszłości kolejni.\'"", \'Comment 10: \\\'[~mbovene@deheus.com],the role ""Start new process for document"" has been added into test and prod Intense for Besse\', \'Comment 11: Koen\', \'Comment 12: Nancy\', \'Comment 13: Peter and Steffen.These users can test it on test environment\', ""Comment 14: but they need to re-login to check it.Best regards,Grzegorz\'"", ""Comment 15: \'For Slaughtery Report documents in MAS NL and MAS BE has been turned on possibility to start new process for users who has rights to start new process for documents.\']""]\nRelated Issues:\n[]\n\n### End'}"
465,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8567\n\n### Instruction:\n21052 on pick location, active batch is correct but does not work.\r\nmanually it works immediately.\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!!image-1!!image-2!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'t seems that after the last update something is not going well.   21180 does not appear in the replenishment. Active batch is goodAllocation is empty"", ""Comment 4: but it is no longer allowed to look at it after the last update of the software.\'"", ""Comment 5: \'The analysis is in progress under the ticket numberDGS-8560\'"", ""Comment 6: \'Hello"", ""Comment 7: information has been provided in issue DGS-8560.Can this be closed?\'"", ""Comment 8: \'Close ticket\']""]\nRelated Issues:\n[\'DGS-8560\']\n\n### End'}"
466,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8566\n\n### Instruction:\nHelllo,\r\n\r\nthere are two warehouse orders for Sneek hanging, with status execution pending, see screenshot . When I try to open corresponding VT\'s I get an error: Can you please solve this and complete the intake?\n\n### Response:\n[""Comment 1: [\'!2023-2-5-8-58-40-644!!2023-2-5-8-59-16-305!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'!image-2023-02-16-10-08-37-853.png!!image-2023-02-16-10-12-09-946.png!!image-2023-02-16-10-13-10-364.png!\'"", \'Comment 4: \\\'{code:java}2023-02-16 10:12:48 (24d7e195-dc88-49c8-9396-176f9a9cb707/Plant.VC.BusinessLogic/DHVD01AP180/27856/203) [Error] Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware - Error during request{  ""scheme"": ""http""\', \'Comment 5:  ""host"": {    ""Value"": ""dhvd01ap180:82""\', \'Comment 6:    ""HasValue"": true\', \'Comment 7:    ""Host"": ""dhvd01ap180""\', \'Comment 8:    ""Port"": 82  }\', \'Comment 9:  ""path"": ""/api/VehicleTicket/getIntakeValidationInfo""\', \'Comment 10:  ""queryString"": []\', \'Comment 11:  ""requestBody"": ""\\\\\\\\""efc5b6c1-7470-4349-aedc-908fb6ff0064\\\\\\\\""""}.System.ArgumentException: Unit mismatch   at Kotrak.Common.SharedKernel.Quantity.ToCommonUnit(Quantity x1\', \'Comment 12: Quantity x2)   at Plant.VC.BusinessLogic.Domain.VehicleTickets.VehicleTicketBulkIntakeElement.get_Weight() in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\67ba263564c33499\\\\\\\\Plant.VC.BusinessLogic\\\\\\\\Plant.VC.BusinessLogic.Domain\\\\\\\\VehicleTickets\\\\\\\\VehicleTicketBulkIntakeElement.cs:line 32   at System.Linq.Enumerable.WhereSelectListIterator`2.MoveNext()   at System.Linq.Enumerable.Aggregate[TSource,TAccumulate](IEnumerable`1 source\', \'Comment 13: TAccumulate seed\', \'Comment 14: Func`3 func)   at Kotrak.Common.SharedKernel.Extensions.QuantityExtensions.Sum[T](IEnumerable`1 source\', \'Comment 15: Func`2 selector)   at Plant.VC.BusinessLogic.Domain.VehicleTickets.Policies.VehicleTicketIntakeDeviationPolicy.CalculateDeviation(VehicleTicket vehicleTicket) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\67ba263564c33499\\\\\\\\Plant.VC.BusinessLogic\\\\\\\\Plant.VC.BusinessLogic.Domain\\\\\\\\VehicleTickets\\\\\\\\Policies\\\\\\\\VehicleTicketIntakeDeviationPolicy.cs:line 34   at Plant.VC.BusinessLogic.Application.VehicleTickets.QueryHandlers.VehicleTicketIntakeDeviationQueryHandler.Handle(VehicleTicketIntakeDeviationQuery query) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\67ba263564c33499\\\\\\\\Plant.VC.BusinessLogic\\\\\\\\Plant.VC.BusinessLogic.Application\\\\\\\\VehicleTickets\\\\\\\\QueryHandlers\\\\\\\\VehicleTicketIntakeDeviationQueryHandler.cs:line 25   at Plant.VC.BusinessLogic.Infrastructure.Api.Controllers.VehicleTicketController.GetIntakeValidationInfo(String vehicleTicketId) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\67ba263564c33499\\\\\\\\Plant.VC.BusinessLogic\\\\\\\\Plant.VC.BusinessLogic.Infrastructure.Api\\\\\\\\Controllers\\\\\\\\VehicleTicketController.cs:line 139   at lambda_method41897(Closure \', \'Comment 16: Object \', \'Comment 17: Object[] )   at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor.SyncActionResultExecutor.Execute(IActionResultTypeMapper mapper\', \'Comment 18: ObjectMethodExecutor executor\', \'Comment 19: Object controller\', \'Comment 20: Object[] arguments)   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeActionMethodAsync()   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next\', \'Comment 21: Scope& scope\', \'Comment 22: Object& state\', \'Comment 23: Boolean& isCompleted)   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeNextActionFilterAsync()--- End of stack trace from previous location ---   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Rethrow(ActionExecutedContextSealed context)   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next\', \'Comment 24: Scope& scope\', \'Comment 25: Object& state\', \'Comment 26: Boolean& isCompleted)   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeInnerFilterAsync()--- End of stack trace from previous location ---   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeFilterPipelineAsync>g__Awaited|20_0(ResourceInvoker invoker\', \'Comment 27: Task lastTask\', \'Comment 28: State next\', \'Comment 29: Scope scope\', \'Comment 30: Object state\', \'Comment 31: Boolean isCompleted)   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker\', \'Comment 32: Task task\', \'Comment 33: IDisposable scope)   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker\', \'Comment 34: Task task\', \'Comment 35: IDisposable scope)   at Microsoft.AspNetCore.Routing.EndpointMiddleware.<Invoke>g__AwaitRequestTask|6_0(Endpoint endpoint\', \'Comment 36: Task requestTask\', \'Comment 37: ILogger logger)   at Swashbuckle.AspNetCore.SwaggerUI.SwaggerUIMiddleware.Invoke(HttpContext httpContext)   at Swashbuckle.AspNetCore.Swagger.SwaggerMiddleware.Invoke(HttpContext httpContext\', ""Comment 38: ISwaggerProvider swaggerProvider)   at Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware.Invoke(HttpContext httpContext){code}\'"", ""Comment 39: \'Dear Thomas,I can see both related VT have status in progress. But I can also see a unit mismatch. Is taht correct?Regards!image-2023-02-16-10-16-42-660.png!!image-2023-02-16-10-17-03-250.png!\'"", ""Comment 40: \'It seems correct"", \'Comment 41: because those products should be packed and not bulk. It seems I cannot correct this\', ""Comment 42: can you do this? You may also remove these products from the VT so that the rest of the VT can be processed\'"", ""Comment 43: \'Also can you see what causes this? because the settlement seems to be correct in DHP?\'"", ""Comment 44: \'I cancelled problematic VTs"", \'Comment 45: changed packing form for those items. Please\', \'Comment 46: create new VTs\', ""Comment 47: it should work fine then.Regards\'"", ""Comment 48: \'thanks"", ""Comment 49: ticket can be closed\'"", ""Comment 50: \'Thank you.\']""]\nRelated Issues:\n[]\n\n### End'}"
467,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8565\n\n### Instruction:\nCan you change in Fiancial Statement: Eendagskuikens to Aankoop\r\n\r\nCan you move documentnr. 1200089181/85 from Aankoop to Slachterij?\r\nYou can see what i have arched.\r\nSucces\n\n### Response:\n[""Comment 1: [\'!image!\'"", \'Comment 2: ""Hello,{quote}Can you change in Fiancial Statement: Eendagskuikens to Aankoop{quote}We can change it on printout of Financial Statement in VAS sector - it should be changed only on FS printout in VAS?{quote}Can you move documentnr. 1200089181/85 from Aankoop to Slachterij?{quote}System displays documents on Financial statement based on \\\'Round Category\\\' on invoices.These 2 invoices have \\\'Round Category\\\' = \\\'Pigs\\\'\', ""Comment 3: due to this are in section \'Pigs\' on Financial Statement. If it should be on \'Slaughtery\' section on Financial statement it should has \'Round Category\' = \'Slaughtery\'.I see that this Item = \'KORE\' has different \'Possible Round Category\'"", \'Comment 4: maybe it\\\'s not well parametrized. Please verify these invoices and this item.!image-2023-02-16-09-28-26-980.png!!image-2023-02-16-09-29-41-998.png!""\', ""Comment 5: \'To change label on printout.Item has been adjusted to different Round Category.\'"", ""Comment 6: \'Do zmiany linkowanie dokumentu SI z PI"", \'Comment 7: PI powinien być widoczny na rundzie i być wygenerowany z SI\', ""Comment 8: błąd przy migracji. PI31944 powinien być widoczny na rundzie.!image-2023-02-21-15-53-33-206.png!\'"", \'Comment 9: ""Do zmiany etykieta na wydruku w VAS - \\\'Eendagskuikens\\\' na \\\'Aankoop\\\'!image-2023-02-22-08-49-21-925.png!""\', \'Comment 10: ""[~bgeytenbeek@deheus.com],we\\\'ve made changes in links\', \'Comment 11: round category in PI (ID: 31944). The document is visible on round now. Also we\\\'ve adjusted the printout for financial statement in VAS sector. You can feel free to test it.Best regards,Grzegorz""\', ""Comment 12: \'Can be closed.\']""]\nRelated Issues:\n[]\n\n### End'}"
468,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8564\n\n### Instruction:\nWe are missing Lot reports in Milas (most for Andel, but also for other sites). The draft Lot reports and/or Lot reports are available in DHC but perhaps were not exported?\r\n\r\nCan you resend the draft Lot reports and Lot reports in the attached list to Milas?\r\n\n\n### Response:\n[""Comment 1: [\'[^20230215_Missing Lot reports in Milas from 20230101-1.xlsx] _(18 kB)_\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 3: ""{code:java}2023-02-13 13:14:28,046 [160] INFO  Evolution.DHCERPService.MilasWebServiceClient.Services.MilasService [C:\\\\\\\\Projects\\\\\\\\evolution.dhcerpservice\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.MilasWebServiceClient\\\\\\\\Services\\\\\\\\MilasService.cs:178] - SendProductionLotReport 863060c6-7c19-4081-b78d-b129fd4a8b1b2023-02-13 13:14:28,093 [160] INFO  Evolution.DHCERPService.MessageSender.Actors.ClientServiceCallActor [C:\\\\\\\\Projects\\\\\\\\evolution.dhcerpservice\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.MessageSender\\\\\\\\Actors\\\\\\\\ClientServiceCallActor.cs:66] - Message with command ProductionLotReportSave and object id 863060c6-7c19-4081-b78d-b129fd4a8b1b was sucessfully processed.{code}Np z Andel wysłali 64 plr\', \'Comment 4: od początku roku{code:java}/****** Script for SelectTopNRows command from SSMS  ******/SELECT *  FROM [Evolution_DHCERP_NL_AS400_Identities].[dbo].[ProductionLotReportMappings]  where dhcid in (select id   FROM [DHCountry_NL_AS400_PROD].[dbo].[ProductionLotReports]  where LotNumber in(\\\'0052160123003\\\',\\\'0984070223002\\\',\\\'0984060223002\\\',\\\'0984060223001\\\',\\\'0984100223004\\\',\\\'0984090223003\\\',\\\'0984030223002\\\',\\\'0984030223001\\\',\\\'0984060223003\\\',\\\'0984130223001\\\',\\\'0984100223003\\\',\\\'0984080223001\\\',\\\'0984070223001\\\',\\\'0984090223001\\\',\\\'0984070223003\\\',\\\'0984100223002\\\',\\\'0984230123004\\\',\\\'0984300123004\\\',\\\'0984160123002\\\',\\\'0984230123001\\\',\\\'0984190123002\\\',\\\'0984170123001\\\',\\\'0984260123002\\\',\\\'0984200123002\\\',\\\'0051090123009\\\',\\\'0984170123002\\\',\\\'0984170123006\\\',\\\'0051090123001\\\',\\\'0984130123001\\\',\\\'0984190123001\\\',\\\'0984160123003\\\',\\\'0984230123002\\\',\\\'0984270123002\\\',\\\'0984160123004\\\',\\\'0984170123003\\\',\\\'0984010223001\\\',\\\'0984220123001\\\',\\\'0984300123001\\\',\\\'0984270123003\\\',\\\'0984300123002\\\',\\\'0984240123002\\\',\\\'0984250123001\\\',\\\'0984270123001\\\',\\\'0984020223001\\\',\\\'0984160123001\\\',\\\'0984170123005\\\',\\\'0984260123001\\\',\\\'0984240123001\\\',\\\'0984110123002\\\',\\\'0984200123001\\\',\\\'0051110123010\\\',\\\'0984110123001\\\',\\\'0984180123001\\\',\\\'0984230123003\\\',\\\'0984170123004\\\',\\\'0984130123002\\\',\\\'0984180123002\\\',\\\'0984300123003\\\',\\\'0984220123002\\\',\\\'0984240123003\\\',\\\'0984130123003\\\',\\\'0984080223002\\\',\\\'0984090223002\\\',\\\'0051291222033\\\'    )){code}Przy ponownej synchrze  info że już jest wysłany:{code:java}2023-02-15 18:08:47,719 [13] WARN  Evolution.DHCERPService.MilasWebServiceClient.Commands.ProductionLotReportSaveCommand [C:\\\\\\\\Projects\\\\\\\\evolution.dhcerpservice\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.MilasWebServiceClient\\\\\\\\Commands\\\\\\\\ProductionLotReportSaveCommand.cs:51] - PLR 863060c6-7c19-4081-b78d-b129fd4a8b1b was already synchronized - skiped2023-02-15 18:08:47,720 [13] INFO  Evolution.DHCERPService.MessageSender.Actors.ClientServiceCallActor [C:\\\\\\\\Projects\\\\\\\\evolution.dhcerpservice\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.MessageSender\\\\\\\\Actors\\\\\\\\ClientServiceCallActor.cs:66] - Message with command ProductionLotReportSave and object id 863060c6-7c19-4081-b78d-b129fd4a8b1b was sucessfully processed.2023-02-15 18:08:47,999 [24] INFO  Evolution.DHCERPService.MessageSender.Handlers.BaseMessageHandler`1 [C:\\\\\\\\Projects\\\\\\\\evolution.dhcerpservice\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.MessageSender\\\\\\\\Handlers\\\\\\\\BaseMessageHandler.cs:64] - Message received successfuly!{code}""\', ""Comment 5: \'Please check if any of the plr list is still missing.\'"", ""Comment 6: \'Hello"", ""Comment 7: please reply to our last comment.Thank you and regards.\'"", ""Comment 8: \'Hello,We are closing this task as we haven’treceivedany replyfromyouforalong time. Regards\']""]\nRelated Issues:\n[]\n\n### End'}"
469,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8563\n\n### Instruction:\nI\'ll write a mail after a meeting..\r\n\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 2: ""Hello,I think it\\\'s the same topic as in https://helpdesk.kotrak.com/browse/DHNLC-1233I think that is due to Item card parametrization. Where it should appear on Financial Statement? In \\\'Expenses\\\' section?If in \\\'Expenses\\\' item should have possible round category also \\\'Expenses\\\' (now is only feed).!image-2023-02-17-12-14-26-341.png!Please verify and let us know that it solves an issue.Regards""\', ""Comment 3: \'{color:black}Hi Damian,{color} {color:black}{color} {color:black}It should be feed.{color} {color:black}{color} {color:black}I made the posting in feed sale"", \'Comment 4: so it should be in feed.{color} {color:black}{color} {color:black}But because it can also be posted as an expense system can’t choose?{color}  {color:black}Am I correct in my understanding?{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Christinede{color} |{color:#000001} {color} |{color:#000001} Jong{color} |  {color:#000001}MedewerkerContractadministratie{color} | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.de-heus.nl/]>{color} | |  *{color:#006FB7} *DEHEUSVOEDERSB.V.*{color}* | | | |{color:#000001} Postbus396 6710BJEde \\\\u200b{color} | |{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} | | |{color:#000001} T:0318675567{color} |  {color:#000001}KvK14626985{color}   _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | | !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | | !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} | | !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} |        *Van:* Damian Świstek (Jira) <jira@kotrak.com>   *Verzonden:* vrijdag 17 februari 2023 12:27  *Aan:* Jong\', ""Comment 5: Christine de <CJong@deheus.com>  *Onderwerp:* DGS-8563 KOOG item not visible in feedsale   \'"", \'Comment 6: ""In case when it should be feed that item should be also parametrized little differently.System displays lines from Feed sales on Financial statement section \\\'Total Feed\\\' when Item has: * has Item Group = \\\'Raw Materials\\\' or \\\'Finish product\\\' * has Possible Round Category = \\\'Feed\\\' * field \\\'Relevant\\\' on Feed sale line should be markedItem card!image-2023-02-17-13-17-06-217.png!Feed sale line!image-2023-02-17-13-18-51-437.png!!image-2023-02-17-13-09-18-889.png!""\', ""Comment 7: \'{color:black}Hi Damian,{color} {color:black}{color} {color:black}This is feed it is a raw material.{color} {color:black}Can you change it on the Itemcard?{color}  {color:black}I don’t have these rights{color} {color:black}😊{color}{color:black}{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Christinede{color} |{color:#000001} {color} |{color:#000001} Jong{color} |  {color:#000001}MedewerkerContractadministratie{color} | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.de-heus.nl/]>{color} | |  *{color:#006FB7} *DEHEUSVOEDERSB.V.*{color}* | | | |{color:#000001} Postbus396 6710BJEde \\\\u200b{color} | |{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} | | |{color:#000001} T:0318675567{color} |  {color:#000001}KvK14626985{color}   _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | | !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | | !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} | | !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} |        *Van:* Damian Świstek (Jira) <jira@kotrak.com>   *Verzonden:* vrijdag 17 februari 2023 13:21  *Aan:* Jong"", ""Comment 8: Christine de <CJong@deheus.com>  *Onderwerp:* DGS-8563 KOOG item not visible in feedsale   !image006!!image007!!image008!\'"", \'Comment 9: ""I could change parametrization of this item\', \'Comment 10: but if this item has been used on other documents\', ""Comment 11: then after changing this item on \'raw material\' it could affect settlements on other documents like Round"", \'Comment 12: Financial Statement\', \'Comment 13: Saldo 2 Pay.Despite this\', \'Comment 14: should I change this item ?Regards""\', ""Comment 15: \'{color:black}It should be change to feed.{color} {color:black}Then it is on the correct category.{color} {color:black}{color} {color:black}{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Christinede{color} |{color:#000001} {color} |{color:#000001} Jong{color} |  {color:#000001}MedewerkerContractadministratie{color} | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.de-heus.nl/]>{color} | |  *{color:#006FB7} *DEHEUSVOEDERSB.V.*{color}* | | | |{color:#000001} Postbus396 6710BJEde \\\\u200b{color} | |{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} | | |{color:#000001} T:0318675567{color} |  {color:#000001}KvK14626985{color}   _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | | !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | | !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} | | !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} |        *Van:* Damian Świstek (Jira) <jira@kotrak.com>   *Verzonden:* vrijdag 17 februari 2023 13:56  *Aan:* Jong"", ""Comment 16: Christine de <CJong@deheus.com>  *Onderwerp:* DGS-8563 KOOG item not visible in feedsale   \'"", \'Comment 17: ""Item Group has been changed from Expenses to \\\'Raw materials\\\' on KOOG item card.If you tick field \\\'Relevant\\\' on Feed sale lines it should appear on Financial statement.Please verify that is ok.""\', ""Comment 18: \'{color:black}Hi Damian,{color} {color:black}{color} {color:black}Okay I will check this.{color} {color:black}Thanks and have a great weekend{color} {color:black}😊{color}{color:black}{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Christinede{color} |{color:#000001} {color} |{color:#000001} Jong{color} |  {color:#000001}MedewerkerContractadministratie{color} | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.de-heus.nl/]>{color} | |  *{color:#006FB7} *DEHEUSVOEDERSB.V.*{color}* | | | |{color:#000001} Postbus396 6710BJEde \\\\u200b{color} | |{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} | | |{color:#000001} T:0318675567{color} |  {color:#000001}KvK14626985{color}   _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | | !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | | !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} | | !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} |        *Van:* Damian Świstek (Jira) <jira@kotrak.com>   *Verzonden:* vrijdag 17 februari 2023 14:14  *Aan:* Jong"", ""Comment 19: Christine de <CJong@deheus.com>  *Onderwerp:* DGS-8563 KOOG item not visible in feedsale   \'"", ""Comment 20: \'Could you confirm that is correct?\'"", ""Comment 21: \'{color:black}Please close ticket. When it is not okay. I will report again.{color} {color:black}Thanks for your action{color} {color:black}😊{color}{color:black}{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Christinede{color} |{color:#000001} {color} |{color:#000001} Jong{color} |  {color:#000001}MedewerkerContractadministratie{color} | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.de-heus.nl/]>{color} | |  *{color:#006FB7} *DEHEUSVOEDERSB.V.*{color}* | | | |{color:#000001} Postbus396 6710BJEde \\\\u200b{color} | |{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} | | |{color:#000001} T:0318675567{color} |  {color:#000001}KvK14626985{color}   _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | | !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | | !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} | | !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} |        *Van:* Damian Świstek (Jira) <jira@kotrak.com>   *Verzonden:* dinsdag 21 februari 2023 15:23  *Aan:* Jong"", ""Comment 22: Christine de <CJong@deheus.com>  *Onderwerp:* DGS-8563 KOOG item not visible in feedsale   \'"", \'Comment 23: ""Has been added role \\\'Item Relevant sectors edit\\\' which allows edit field \\\'Relevant sectors\\\' on Item Card. Users added to role:Bert\', \'Comment 24: Chrsitine\', \'Comment 25: Nancy\', \'Comment 26: Peter,Mitch\', \'Comment 27: Richard""\', ""Comment 28: \'{color:black}Damian,{color} {color:black}{color} {color:black}Thanks so much!{color} {color:black}{color} {color:black}It works like a charm{color} {color:black}😊{color}{color:black}{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Christinede{color} |{color:#000001} {color} |{color:#000001} Jong{color} |  {color:#000001}MedewerkerContractadministratie{color} | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.de-heus.nl/]>{color} | |  *{color:#006FB7} *DEHEUSVOEDERSB.V.*{color}* | | | |{color:#000001} Postbus396 6710BJEde \\\\u200b{color} | |{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} | | |{color:#000001} T:0318675567{color} |  {color:#000001}KvK14626985{color}   _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | | !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | | !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} | | !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} |        *Van:* Damian Świstek (Jira) <jira@kotrak.com>   *Verzonden:* dinsdag 28 februari 2023 12:13  *Aan:* Jong"", ""Comment 29: Christine de <CJong@deheus.com>  *Onderwerp:* DGS-8563 KOOG item not visible in feedsale   \']""]\nRelated Issues:\n[]\n\n### End'}"
470,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8562\n\n### Instruction:\nHi, can you permit access for Hurk, Elvera van den <EHurk@deheus.com>; Dam, Nancy van <NDam@deheus.com>; Schellekens, Janine <JSchellekens@deheus.com> in each others inbox?\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Access for inboxes have been added to these 3 users.\']""]\nRelated Issues:\n[]\n\n### End'}"
471,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8561\n\n### Instruction:\nThis JO-330/23/TEMA has,  zero cost on item 6320003, please help resolve this.\r\nI have tried using the method you showed earlier but it did not work on this one.\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'PLR = 0722110223003!image-2023-02-16-08-13-42-834.png!!image-2023-02-16-08-12-07-649.png!Nie ma tego itema na wydaniu!image-2023-02-16-08-12-51-160.png!\'"", ""Comment 4: \'!image-2023-02-16-08-22-02-383.png!!image-2023-02-16-08-28-33-799.png!\'"", ""Comment 5: \'!image-2023-02-16-08-34-45-472.png!\'"", ""Comment 6: \'!image-2023-02-16-08-40-42-026.png!\'"", ""Comment 7: \'Hi,Regarding this Job Order"", ""Comment 8: you do not have any resource in ERP XL for this item:!image-2023-02-16-09-05-49-463.png!!image-2023-02-16-09-04-51-327.png!?This is error from XL that says you do not have resource for give item:!image-2023-02-16-09-06-44-926.png!You do not have resource registered in XL because the intake was done only based on VT!image-2023-02-16-09-07-38-437.png!that does not have connection to any order!image-2023-02-16-09-08-32-193.png!!image-2023-02-16-09-10-43-782.png!Regards\'"", ""Comment 9: \'Hi,Is there anything else we can do for you or we can close this task?Regards\'"", ""Comment 10: \'Ok Please close the ticket"", ""Comment 11: we will handle it pls.\'"", ""Comment 12: \'Thank you\']""]\nRelated Issues:\n[]\n\n### End'}"
472,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8560\n\n### Instruction:\nGoodmorning,\r\n\r\nthere are a lot of complaints about automatic replenishment not working for premixNL: See attached list, all those are created by hand because automatic replenishment did not work: Please investigate and propose a solution as quick as possible, frustrations are really high at the moment\n\n### Response:\n[""Comment 1: [\'!afbeelding!\'"", ""Comment 2: \'Hello,\\\\r\\\\rWe are investigating your issue. We will inform you about the solution as soon as possible.\\\\r\\\\rRegards\\\\r\\\\r\'"", ""Comment 3: \'Hello,Kindly approve lowering priority of this task to P2 as P1 issues are only those with a critical or a blocking impact on business processes . This seems not to be the case in this issue so we suggest decreasing the issue priority.Regards\'"", ""Comment 4: \'And this is the list from yesterday"", ""Comment 5: you can see in colum created by that a lot are created by the user and not PCS_Automatic!afbeelding-1!\'"", ""Comment 6: \'xml message from pcs this morning[^Replenishments_20230215090412_d1c2b00d-cc79-4203-b99a-6c57a101a152_40577533.xml] _(3 kB)_\'"", ""Comment 7: \'It seems proces runs into an error !afbeelding-2!\'"", ""Comment 8: \'You can set it to P2 indeed\'"", ""Comment 9: \'Thank You\'"", ""Comment 10: \' !ABM for item 21079! \'"", \'Comment 11: ""{code:java}Select TOP (50) * FROM [DHapps_log].[dbo].[PcsWebServiceLog] where OperationId in (SELECT OperationId FROM [DHapps_log].[dbo].[PcsWebServiceLog]  where OperationType = \\\'[PcsReplenishment]\\\' and LogLevel = \\\'DEBUG\\\')Order by Id Desc{code} !PcsReplenishment Errors TOP 50 ! Problem dotyczy tylko towaru 21079 i zaczął się !image-2023-02-15-14-44-09-079!----h2. Rezerwacje pod SO na kodach !image-2023-02-15-14-58-25-799!!image-2023-02-15-15-00-30-960!""\', \'Comment 12: ""{code:java}SELECT TOP (1000) * FROM [DHP_NL_PROD].[dbo].[WarehouseStocks] where wst_artid = 1008   and Wst_SerialNumber = \\\'87014030112022266006\\\'  order by 1 desc  SELECT TOP (1000) * FROM [DHP_NL_PROD].[dbo].Delivery where Del_ArtId = 1008   and Del_SerialNumber = \\\'87014030112022266006\\\'  order by 1 desc  SELECT TOP (1000) * FROM [DHP_NL_PROD].[dbo].RegisterMappings where RgM_ArtId = 1008  and RgM_DelId = 266006  Select * from dbo.WMSStorageElements   where StE_Code like \\\'%4000%\\\'  order by StE_CreateDate desc  Select * from dbo.Reservation where Res_ArtId = 1008{code}""\', ""Comment 13: \'any update?\'"", ""Comment 14: \' !Double allocation with archival! \'"", ""Comment 15: \'Dear Thomas,We are still analyzing.Regards\'"", ""Comment 16: \'{code:java}  DELETE FROM [DHP_NL_PROD].[dbo].[Allocation] where AlN_Id in --(3509) -- nie da się (2289)-- nie da się (2329)-- nie da się (2273)-- (27434)-- (27435)-- (3903)-- nie da się (3602)-- nie da się (3786)-- (3418)-- (3169){code}{code:java}Select * FROM [DHP_NL_PROD].[dbo].[Allocation] where AlN_Id in (2289,2329,2273,3602,3786)Select * FROM [DHP_NL_PROD].[dbo].ArticleCard where Art_Id in (258,993){code}!image-2023-02-27-13-15-31-522!\'"", ""Comment 17: \'any update?\'"", ""Comment 18: \'Dear Thomas,Thi issue and all others task related to replenishment have been still investigated by dev team. We are working on it.Regards\'"", ""Comment 19: \' !Deleted 5 allocations from DHP! \'"", ""Comment 20: \'Dear Thomas,I have information that Marcin has informed you about the case via Teams.Please"", ""Comment 21: let me know what would be the next step. Should we close this task?Regards\'"", ""Comment 22: \'I think the solution for the problem is not yet there on the application so please keep it open\'"", \'Comment 23: ""So let\\\'s put this task On Hold until solution will be deployed to application. Please\', \'Comment 24: let me know if this is fine for you.Regards""\', ""Comment 25: \'Hi,Does the fix implemented underDGS-8630 resolved issue for you?Regards\']""]\nRelated Issues:\n[\'DGS-8593\', \'DGS-8598\', \'DGS-8630\', \'DGS-8595\', \'DGS-8634\', \'DGS-8567\']\n\n### End'}"
473,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8559\n\n### Instruction:\nShipping Notice L000131024 is visible in DHC but not arriving in DHP Utrecht, even after resending. \r\nCan you please check? \n\n### Response:\n[""Comment 1: [\'Hello,\\\\r\\\\rWe are investigating your issue. We will inform you about the solution as soon as possible.\\\\r\\\\rRegards\\\\r\\\\r\'"", ""Comment 2: \'brak commitdate!image-2023-02-15-10-18-11-589.png!\'"", ""Comment 3: \'ogolnie jest takich 159\'"", ""Comment 4: \'Hi @Agnieszka"", ""Comment 5: already some news?\'"", ""Comment 6: \'@Agnieszka?\'"", ""Comment 7: \'The truck needs to leave"", ""Comment 8: please help!\'"", ""Comment 9: \'[~tberendsen@deheus.com]it looks like sth wrong with ASN please look at screen below:!image-2023-02-15-11-56-17-718.png!It looks like this shipping notice is linked to two orders. One is for andel and one is for Utrecht.I think that is the case.\'"", \'Comment 10: ""[~agnieszka.januszewska@kotrak.com] wydłubałem takie zapytanie:{code:java}  select distinct pa.Name as shippingnoticeplant\', \'Comment 11: sn.ForeignNumber as ShippingNoticeNumber,bs.Name as OrderPlant\', \'Comment 12: o.ForeignDocumentNumber as OrderNumber  --\', \'Comment 13:  pa.*\', \'Comment 14: o.*\', \'Comment 15: oei.*\', \'Comment 16: bs.*   from dbo.ShippingNoticeElements e  inner join dbo.ShippingNoticeElementOrders seo on seo.ShippingNoticeElementId = e.Id  inner join dbo.ShippingNotices sn on sn.id = e.ShippingNoticeId  inner join dbo.OrderElements oe on oe.id = seo.OrderElementId  inner join dbo.orders o on o.id = oe.OrderId  inner join dbo.OrderExportInfoes oei on oei.EntityId = o.id  inner join dbo.BusinessStructures bs on bs.id = oei.ClientId  inner join dbo.ProductionAreas pa on pa.id =sn.ProductionAreaId   where ForeignNumber like \\\'%7_L000131024%\\\'{code}""\', ""Comment 17: \'[~tberendsen@deheus.com],It looks like we have two asnsbut one with two elements with wrong order linked:!image-2023-02-15-12-01-31-230.png!\'"", ""Comment 18: \'Please check"", ""Comment 19: should be ok now\'"", \'Comment 20: ""Yes\', \'Comment 21: I see it now.Thanks!This morning I see lots of different things with SN\\\'s. I will monitor it. For now you can close this task.""]\']\nRelated Issues:\n[]\n\n### End'}"
474,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8558\n\n### Instruction:\nOn request of the Formulation department, please remove these 2 links in DHC:\r\n\r\nVE303612 \r\nVE307617 \r\n\r\nPlease do so before 12:00 today. Thanks!\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Hi,Could you please provide me some more details? What do those codes refer to? Could you please provide us with a screenshot from application?Regards\'"", ""Comment 3: \'I passed your question to Vivian"", ""Comment 4: is this attached screenshot sufficient information?!2023-2-4-10-53-11-859!\'"", ""Comment 5: \'Please"", ""Comment 6: confirm. You want us to remove additional technology for those items?\'"", ""Comment 7: \'Yes please"", ""Comment 8: only those two.\'"", ""Comment 9: \'Both additional technologies have been removed. No PLR related.Regards\'"", ""Comment 10: \'Yes thanks! Formulation is happy now :)Thanks a lot.\'"", ""Comment 11: \'Thank you.\']""]\nRelated Issues:\n[]\n\n### End'}"
475,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8557\n\n### Instruction:\nHi\r\n\r\nTask from Wiola.\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'[^DGS-8557.docx]\'"", ""Comment 4: \'Description of the cause of the problem in the attachment[^DGS-8557.docx]\'"", ""Comment 5: \'!image-1!\']""]\nRelated Issues:\n[]\n\n### End'}"
476,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8556\n\n### Instruction:\nThe report Weighbridge dispatch available in VT is duplicating the element.  We have problem in Unit Itaberaí and Apucarana. Could you check and fix it?\r\n\r\n\r\nThank you\n\n### Response:\n[""Comment 1: [\'DGS-8433\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'In the last task (DGS-8433) was asked more examples"", ""Comment 4: but all VTs are with error\'"", ""Comment 5: \'ItaberaíVT-186/23VT-188/23VT-191/23!image!!image-1!!image-2!\'"", ""Comment 6: \'ApucaranaVT-681/23VT-679/23VT-669/23!image-3!!image-4!!image-5!\'"", \'Comment 7: ""Hello guysWe need this fixed asap.DGS-8433 was raise and we provided real cases of that. If the error is not present in other DHPlants it doesn\\\'t mean the problem doesn\\\'t exists. That\\\'s why we informed which plants have the issue.Thank you very much""\', \'Comment 8: ""exec [dbo].[GetWeighBridgeNewPrintout] \\\'86117720-332a-44fa-87cb-b614b40bfb74\\\' !screenshot-1! {code:java}SELECT D.*\\\\t\\\\tFROM dbo.VehicleTicketPackedDispatchElements E\\\\t\\\\tINNER JOIN dbo.VehicleTicketPackedDispatchElementResources R ON R.Id = E.Id AND R.No = E.No\\\\t\\\\tLEFT JOIN dbo.Deliveries D ON D.SerialNumber = R.SerialNumber\\\\t\\\\tWHERE E.Status = 10 AND R.IsCancelled = 0 and e.Id=\\\'86117720-332a-44fa-87cb-b614b40bfb74\\\'{code}tutaj są dwa wpisy !screenshot-3!  !screenshot-2! ""\', \'Comment 9: ""Problem jak w połacznym zgłoszeniu wydruk wiaze te z po deliveryid a tu mamy duble[~marcin.kleszcz@kotrak.com] Problemem jest wiazanie do tabeli delivery poniewaz dla jednej serialnumber jest kilka deliveryid więc dlatego w tym przypadku wyniki się duplikują.Czy jest to standardowe i normlane działanie ? czy Brazylia cos zmieniła w procesie\', \'Comment 10: czy ta procedura jest zła?bo sama procedura jak patrzyłam i w Apu i w innej fabryce jest taka sama\', \'Comment 11: wtedy taka sytuacja z duplikacją pozycji występowała by częsciej\', \'Comment 12: procedura też nie ejst najnowsza.Pytanie czy tak zawsze robili że jeden serial number był przypisany do kilku deliveryid?Przykład dla tgo zgłoszenia vt 669/23 z apuSELECT E.Id\', \'Comment 13: E.No\', \'Comment 14: NULL AS IssueDate\', \'Comment 15: R.SerialNumber\', \'Comment 16: R.WeightValue AS ResourceQuantity\', \'Comment 17: R.WeightUnit AS ResourceQuantityUnit\', \'Comment 18: R.ExpiryDate\', \'Comment 19: D.InternalSerialNumber\', \'Comment 20: D.CreatedDate\', \'Comment 21:  NULL AS ForeignEAN\', \'Comment 22: NULL AS SourceDocumentNumber FROM dbo.VehicleTicketPackedDispatchElements E INNER JOIN dbo.VehicleTicketPackedDispatchElementResources R ON R.Id = E.Id  AND R.No = E.No LEFT JOIN dbo.Deliveries D ON D.SerialNumber = R.SerialNumber WHERE E.Status = 10 AND R.IsCancelled = 0 and e.id= \\\'1E6686E6-0C73-4CCF-940A-6DF5DF515A36\\\'daje 32 wynikinp ten serialnumberd.SerialNumber=\\\'0882030223002\\\' pojawia sie 2 razy :!image-2023-02-15-07-36-03-220.png!natomiast wynik zapytania dla samej tabeliselect * from VehicleTicketPackedDispatchElementResources where id=\\\'1E6686E6-0C73-4CCF-940A-6DF5DF515A36\\\' ten serial number jest tylko raz a wszystkich wyników jest 14!image-2023-02-15-07-35-12-620.png!!image-2023-02-15-07-35-12-620! !image-2023-02-15-07-36-03-220!""\', ""Comment 23: \'Taskhas been forwarded to the developers.\'"", ""Comment 24: \'[~agnieszka.januszewska@kotrak.com] czy możesz podać z przykłady z jakich dokumentów pochodzą te serial number? \'"", \'Comment 25: ""Przykład dla tego zgłoszenia sprawdziłam{color:#0747a6}*vt 669/23 z apucarany*{color}SELECT E.Id\', \'Comment 26: E.No\', \'Comment 27: NULL AS IssueDate\', \'Comment 28: R.SerialNumber\', \'Comment 29: R.WeightValue AS ResourceQuantity\', \'Comment 30: R.WeightUnit AS ResourceQuantityUnit\', \'Comment 31: R.ExpiryDate\', \'Comment 32: D.InternalSerialNumber\', \'Comment 33: D.CreatedDate\', \'Comment 34: NULL AS ForeignEAN\', \'Comment 35: NULL AS SourceDocumentNumber FROM dbo.VehicleTicketPackedDispatchElements E INNER JOIN dbo.VehicleTicketPackedDispatchElementResources R ON R.Id = E.Id AND R.No = E.No LEFT JOIN dbo.Deliveries D ON D.SerialNumber = R.SerialNumber WHERE E.Status = 10 AND R.IsCancelled = 0 and e.id= \\\'1E6686E6-0C73-4CCF-940A-6DF5DF515A36\\\' !image-2023-02-15-09-59-01-956.png!!image-2023-02-15-09-59-01-956!""\', ""Comment 36: \'[^GetWeighBridgeNewPrintout.sql]\'"", ""Comment 37: \'The procedure for printing has been updated.Uploaded to the plant Itaberaí.Please check.If it is correct"", ""Comment 38: we will upload to the other factories.\'"", ""Comment 39: \'Hello"", ""Comment 40: please reply to our last comment.Thank you and regards.\'"", ""Comment 41: \'Hello Piotr,I checked and is correct. Could you add for all units?Thank you\'"", ""Comment 42: \'[~maciej.dobrzanski@kotrak.com] takie zmiany na sql/rdl do wydruków potrzebujemy też wciągnąć na Bitbucket.http://10.10.10.52:82/projects/PLA3/repos/dhp30implementations/browse/BASE/PRINTOUTS/BR\'"", ""Comment 43: \'Tutaj okazuje się"", \'Comment 44: że na Staszku już mamy najnowsze zmiany.Natomiast jak będzie w przyszłości taki temat [~piotr.gaczorek@kotrak.com] to trzeba napisać do Maćka i do mnie\', \'Comment 45: żeby założyć DAPa i wciągnąć zmiany do projektu. Plus zapytać klienta\', \'Comment 46: jeśli tego nie powie\', \'Comment 47: czy wgrywać na innych plantach. [~maciej.dobrzanski@kotrak.com] tylko wydaje się\', \'Comment 48: że nie zawsze zmieniony plik będziemy mogli wgrać na inne fabryki\', \'Comment 49: bo mogą mieć niższą wersję\', ""Comment 50: w których np nie będzie odpowiednich kolumn.\'"", ""Comment 51: \'Rio Claro - aktualny.Apucarana - zmiana.Toledo - zmiana.Caruaru - procedura wywala się w tej wersji planta. !screenshot-4! Itaberai - zmiana już wykonana.Guararapes - zmiana.\'"", ""Comment 52: \'(y)\'"", ""Comment 53: \'Hello. The printouts have been updated on the factories except the factory in Caruaru - plant update is required"", ""Comment 54: due to the plant version.\'"", ""Comment 55: \'Hello Piotr,ok"", ""Comment 56: you can close this task. Thank you.\']""]\nRelated Issues:\n[\'DGS-8433\']\n\n### End'}"
477,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8555\n\n### Instruction:\nAll Purchase invoices should have always filled in fields\xa0\'Scanned Total invoice amount\' and \'Scanned Total VAT amount\'.\r\n\r\n\r\n!image-2023-02-14-15-21-02-039.png!\r\n\r\nWhen PI documents are sent to Milas and these fields are empty there is needed to filled in these fields in Milas.\r\n\r\nIn Intense these 2 fields should be always filled after saving document.\r\n\r\nWhen \'Kofax ID\' on Purchase Invoice is empty these 2 fields should be updated by Gross value and VAT value from Intense document.\r\n\r\nIt should be done on Purchase Invoices for all sectors.\r\n\r\n!image-2023-02-14-15-22-53-702.png!\r\n\r\n\xa0\r\n\r\n\xa0\n\n### Response:\n[\'Comment 1: [""Ready fro tests on UAT environment (IBIP_DH_TEST).If \\\'Kofax ID\\\' on Purchase Invoice is empty fields \\\'Scanned Total invoice amount\\\' and \\\'Scanned Total VAT amount\\\' will be updated after document save. * \\\'Scanned Total invoice amount\\\' = Gross Value for document * \\\'Scanned Total VAT amount\\\' = VAT Value for documentIf \\\'Kofax ID\\\' is not empty document won\\\'t be updated and will be like sent from Kofax.Please verify that everything is correct and after confirmation we can move it on production environment.""\', ""Comment 2: \'Hi,The new functionality has been tested successful by MvB. Please deploy asap to PROD.Thanks for the quick response!     \'"", ""Comment 3: \'Hi,It has been deployed laso on production environment in all sectors.Regards\']""]\nRelated Issues:\n[]\n\n### End'}"
478,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8554\n\n### Instruction:\nItem 307309 was linked an recipe for Helmond was received and accepted in DHC. Technology seems to be generated correctly. \r\nHowever, item and recipe did not arrive in DHP / PCS Helmond.\r\n\r\nCan you please check why the item and recipe are missing in DHP. Plant needs the recipe for production.\n\n### Response:\n[""Comment 1: [\'!image!!image-1!!image-2!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Recipes are now in DHP  !screenshot-1! \'"", ""Comment 4: \'Ok"", ""Comment 5: thank you. What was the issue?\'"", ""Comment 6: \'Missing dhhitem in DHCService"", ""Comment 7: it has fixed in DHC 3.0.60.\'"", ""Comment 8: \'Thank you. This ticket can be closed.\'"", ""Comment 9: \'Thank you for confirmation.\']""]\nRelated Issues:\n[]\n\n### End'}"
479,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8553\n\n### Instruction:\nWhat are the conditons off printing different banking account on invoice.\r\nWill the banking account off ""accounting"" be used or from ""adresses"".\r\n\r\nIf ""adresses"" what are the selecting conditions off the bankingaccount?\r\nIs no bankaccount in ""adresses"" accepted?\r\n\r\nSee also  DGS-8350\n\n### Response:\n[""Comment 1: [\'!image!!image-1!\'"", ""Comment 2: \'What are the criteria off selecting the bank account.In witch order.\'"", ""Comment 3: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 4: \'PleaseThank you"", ""Comment 5: could you provide more details according to my previous question ?could please bring the path to printout template. and document number.It could be set in diffrent way for diffrent document type.To see how to check the path see alsoDGS-8350\'"", ""Comment 6: \'!image-2!!image-3!\'"", ""Comment 7: \'the incorrect HSBC bank account number is now also printed on the invoice.This is done using the Customers table under Addresses.How can be prevented the printing off this banking account\'"", ""Comment 8: \'Thank you for the example but what printout typoe you are using,?!image-2023-02-22-11-45-14-622.png!When I tried to generate an printout I get the empty number.\'"", ""Comment 9: \'In CDN (DH Premix) customer 7727 (De Heus a.s.) has the old DH Premix HSBC bank account number in the card (under Accounting settings). This ‘HSBC’ bank account number is printed on each invoice Premix sends to De Heus a.s. but needs to be removed in order to have the standard ABN bank account number of DH Premix on the invoice (it’s in the letter head).See customer card of customer 0674 where there is no Bank account number in the customer card"", ""Comment 10: then the standard will be printed when generating the invoice.Thanks and regards,Reinier!image-4!!image-5!\'"", ""Comment 11: \'I think this is a bug in CDN as (per below) once I open the Banks I don’t see the number ‘99’  in the list.To my opinion"", \'Comment 12: the field should be blank but I cannot delete this.I tried to change it into NL14ABNA (which is the bank account number of Premix) but this doesn’t help.Now I cannot exit the customer card\', ""Comment 13: see below.Best regards,Reinier!image-6!\'"", ""Comment 14: \'Hellothere is a few different cases you are mentioning herefirstthis is not an error it is not error:!image-2023-03-23-15-30-43-129.png!If you see that message and in fact you did not make changes in the document"", \'Comment 15: just press save and then close the object.I am not sure what printout you are using but according to your message the problem is that the information in ERP XL for customer7727 are not updated and incorrect\', ""Comment 16: do you wish us to set it the same as for 0694? The bank account is taken from address are you not able to add new address for that customer?\'"", \'Comment 17: \\\'CASE WHEN ""Rejestry"".""KAR_IdentKontr""=1  THEN CDN.WirtualnyNumerRachunku(""Rejestry"".""KAR_RachIdentNrKier"",""Rejestry"".""KAR_RachIdent"",""TraNag"".""TrN_KntNumer"",\\\\\\\'PL\\\\\\\') Else ""Rejestry"".""KAR_NrRachunku"" ENDgidnumer dokuemntuTrN_GIDTyp=2037 AND TrN_GIDFirma=1015303 AND TrN_GIDNumer=3375490TrN_GIDNumer=3374351\\\'\', ""Comment 18: \'Our employee B. Czarnocka made an comment.You cannot remove a bank account which has been used in the past but you can archive it"", ""Comment 19: add a new one and choose the new one as default (in the screenshot below I marked the fields to be used for that). When I look at this customer in CDN I see 2 addresses and 2 bank accounts for him. I do notice that  there is an error when trying to edit the current one and it is not possible to archive him or to make the other one default (the field is greyed out).Why this appears and how can we change the default address & thus also bank account number?!image-7!!image-8!\'"", ""Comment 20: \'NL23HSBC0786449802HSBCNL2A\'"", ""Comment 21: \'!addin.PNG|thumbnail!\'"", ""Comment 22: \'Good morningthe bank field on the accounting bookmark has been updated"", \'Comment 23: which by default of the previous add-on is not editable\', ""Comment 24: the add-on is already enabled please verify!image-2023-03-30-13-52-47-402.png!!addin.PNG!!image-2023-03-30-13-53-47-279.png!\'"", ""Comment 25: \'May we close the task?\'"", ""Comment 26: \'Not yet.User did not respnde.\'"", ""Comment 27: \'I don’t see this HSBC bank account number anymore on the customer card so wait for the next invoice"", ""Comment 28: but should be fixed now.Thanks,Reinier\'"", ""Comment 29: \'If solved"", ""Comment 30: ok for me to go ahead & we will see on the next invoice to De Heus a.s. if this HSBC bank account number again appears or not.ThxReinier\'"", ""Comment 31: \'Ticket kan be closed\']""]\nRelated Issues:\n[]\n\n### End'}"
480,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8552\n\n### Instruction:\nPlease remove additional technology UT704911 (Utrecht) from DHC.\r\n\r\nKind regards,\r\nRob.\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Dear Rob,Which subversion? 0 or 1?Regards\'"", ""Comment 3: \'!image-2023-02-15-07-22-16-388.png!\'"", ""Comment 4: \'Dear Rob,Which subversion? 0 or 1?Regards\'"", ""Comment 5: \'Both\'"", ""Comment 6: \'Both additional technologies have been deleted.Regards\'"", ""Comment 7: \'Thank you for the support"", ""Comment 8: the ticket can be closed.\'"", ""Comment 9: \'Thank you.\']""]\nRelated Issues:\n[]\n\n### End'}"
481,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8551\n\n### Instruction:\nRecipe 545201 does not go from DHC Compound to DHP Sneek.\r\nProduct needs to be produced.\r\n\r\nPlease investigate/fix.\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Hello Rob van Veen"", \'Comment 3: It should be fine now. Please verify\', \'Comment 4: Recipe 545201 re-synchronize DHH >AS400 >DHP Sneek Please\', ""Comment 5: let me know if you expect any additional actions from us regarding this issue? Can we close this ticket?Regards.\'"", ""Comment 6: \'AS400?The recipe arrived in SNeek. The ticket can be closed.Thanks for the support.\'"", ""Comment 7: \'fix in new versionRegards\']""]\nRelated Issues:\n[]\n\n### End'}"
482,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8550\n\n### Instruction:\nSP-B/0512 back to entry, S2P isn\'t correct, is it possible to do this myself?\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 2: ""Hello Koen,Now it\\\'s in Entry again.Mitch and Richard now are also able to starting new process for Saldo to pay and put it back to Entry status.Regards""]\']\nRelated Issues:\n[]\n\n### End'}"
483,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8549\n\n### Instruction:\nCustomer 051199\r\nMany feed documents are double booked from 10-06-2022 till 24-09-2022\r\nCan you check and delete this?\n\n### Response:\n[""Comment 1: [\'Hi,please mark in Excel file"", ""Comment 2: which lines should be delete from Feed Sale document - FE-V/0002:[^FS_ElementsToDelete_14022023_GM.xlsx]Best regards,Grzegorz\'"", ""Comment 3: \'To delete the latest duplicates compared by Document number"", \'Comment 4: Item\', ""Comment 5: Gross value.\'"", ""Comment 6: \'Elements to delete on red[^FS_ElementsToDelete_22022023_DS.xlsx]\'"", ""Comment 7: \'[~bgeytenbeek@deheus.com],the duplicate elements have been deleted from FE-V/0002 document.You can feel free to look into the Feed sale and give us the feedback.Best regards,Grzegorz\'"", ""Comment 8: \'THis can be closed.\']""]\nRelated Issues:\n[\'DGS-8537\']\n\n### End'}"
484,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8548\n\n### Instruction:\nHi, \r\n\r\nCould we update all the affected document of DGS-8498 on database level?\r\n\r\nBest Regards, \r\nClara\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Do you wish to set checked fixed costs? Could you provide list of documents numbers?\'"", ""Comment 3: \'Yes"", ""Comment 4: we wish to set checked fixed costs. I will provide you the list this week since we do update document and then will list the affected cases. \'"", \'Comment 5: ""Hi\', ""Comment 6: Sorry for keep you wait. I\'m waiting end user for month end closed. This month they do manage to close themselves. Please close the ticket. If I need any"", \'Comment 7: I will raise new request. Thank you.""]\']\nRelated Issues:\n[]\n\n### End'}"
485,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8547\n\n### Instruction:\nWe need to change bank account numbers on these two types of documents.\r\n\r\nIn the red rectangles are the old numbers and in the black are the new bank accounts.\n\n### Response:\n[""Comment 1: [\'!ESI_Izmena (2)!!SI_Izmena (2)!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Default printouts have been modified: !screenshot-1!  !screenshot-2! Please verify,regards.\'"", ""Comment 4: \'Everything is fine. You can close the ticket.\'"", ""Comment 5: \'Thank you for confirmation.\']""]\nRelated Issues:\n[]\n\n### End'}"
486,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8546\n\n### Instruction:\nHi, from Iwona:\r\n \r\n\r\nProśba o rozliczenie rozrachunków na koncie 238-04 od strony bazy:\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!!image-1!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Documents have been settled. Please verify.\'"", ""Comment 4: \'!image-2!\'"", ""Comment 5: \'Task to close"", ""Comment 6: thanks.\']""]\nRelated Issues:\n[]\n\n### End'}"
487,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8545\n\n### Instruction:\nlinked production areas are failing to auto generate recipes, again.\r\n\r\nhttps://helpdesk.kotrak.com/servicedesk/customer/portal/56/DGS-7271\n\n### Response:\n[""Comment 1: [\'!image!!image-1!!image-2!!image-3!!image-4!!image-5!!image-6!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'We create new RCa"", ""Comment 4: may we close this task and procceed all inDGS-8576?\'"", ""Comment 5: \'Hello,does the situation constantly repeat itself"", ""Comment 6: has technlogy not generated or is not generating in specific cases?\'"", ""Comment 7: \'Thabile is out of office this week. We will respond next week.\'"", ""Comment 8: \'Hello"", ""Comment 9: the function appears to not be working at all. users are manually generating production recipes if the PCS gives a warning stating that the recipe in the system is older than 3 months. the highlighted examples are for the lickline 70 these have orders not older than 90 days in DHP but the production recipes have not generated for them. the start date for all was 01/02/2023 import/acceptance 10/02/2023. all of them have only the base recipe in DHP aside from one or two where the recipes were manually generated !image-7!\']""]\nRelated Issues:\n[\'DGS-8576\']\n\n### End'}"
488,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8544\n\n### Instruction:\nAfter mistake of weighbridge operator in processing VT and canceling some items on it, DHC cannot syncrhonize documents, three item on VT-126/02/2023/CU. In red rectagnle is correct IO number, for black ractangle we need to change IO number to IO-14. \r\n\r\nCan you please check this?\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 3: ""select * from VehicleTicketElementERPDocuments vdjoin VehicleTicketElements ve on ve.id=vd.VehicleTicketElementIdwhere vehicleticketid=\\\'AAA30761-BF08-4687-B1A8-308FE608D710\\\'-- ( pozycja 4 )""\', ""Comment 4: \'Order IO 14 is executed by wmr+ that was modified from!image-2023-02-14-12-48-50-339.png!ON WMR +10 there is full quantity thats why it is impossible to choose this order from dhp ( it is on the list)Please verify and let me know to linked that VC with IO 14 and WMR+ 10 and set it as generated in DHC for that item?\'"", \'Comment 5: ""select * from TradeDocumentSyncs where xlid=\\\'1659655\\\'select * from TradeDocumentElementSyncs where xlid=\\\'1659655\\\'""\', ""Comment 6: \'You need to add these two items on the stock also.!vukota dodavanje 21.02.2023!\'"", ""Comment 7: \'I asked you beforePlease verify and let me know to linked that VC with IO 14 and WMR+ 10 and set it as generated in DHC for that item? it was about a other vtVT-126/02/2023/CU.Do you need any help with this VT and this IO (14)?I do not get anserw.Now you are asking about other VT"", ""Comment 8: could you please create new task about vt 145/2 and please send more details what need to be done with this other VT.\'"", ""Comment 9: \'Hello,We are closing this task as we haven’treceivedany replyfromyouforalong time. If the issueappearsagain"", ""Comment 10: please raise another task.Regards\'"", \'Comment 11: ""Our management did not gave us any instructions regarding this incident so I couldn\\\'t answer you. Thanks for help!""]\']\nRelated Issues:\n[]\n\n### End'}"
489,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8543\n\n### Instruction:\nKB small WB is not showing weights in DHP. \r\n\r\nservices and sites were restarted but DHP still shows 0T \n\n### Response:\n[""Comment 1: [\'!3789c1e7-8efc-4cd6-8634-ebe1421ffbf2.jpg|thumbnail!!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Please"", ""Comment 4: verify now and let me know.Regards\'"", ""Comment 5: \'Hello still not working. DHP initially showed nothing so we added more weigh0t"", ""Comment 6: then it showed weights for a second. [^2023-02-14_11-01-01.mp4] _(230 kB)_\'"", ""Comment 7: \'!image-2023-02-14-10-24-26-417.png!!image-2023-02-14-10-25-22-368.png!\'"", ""Comment 8: \'Please"", ""Comment 9: verify once again\'"", ""Comment 10: \'Hi"", \'Comment 11: its still doing the same thing. ""HP initially showed nothing so we added more weigh0t\', \'Comment 12: then it showed weights for a second.""\\\'\', ""Comment 13: \'Please"", ""Comment 14: verify now\'"", ""Comment 15: \'Not working !image-1!!image-2!\'"", ""Comment 16: \'Please be informed that we have forwarded the issue to the development team in order to internal analysis.We are waiting for more details and will be back with further information as soon as possible.\'"", ""Comment 17: \'We haveadjusted the parsing of data coming from the scale. Now it should work"", ""Comment 18: please verify.Regards\'"", ""Comment 19: \'!image-2023-02-14-14-58-11-956.png!\'"", ""Comment 20: \'Hi,How is the scale working today? Is it fine? If yes"", ""Comment 21: can we close this task?Regards\'"", ""Comment 22: \'Hello"", ""Comment 23: yes it is thank you task can be closed\']""]\nRelated Issues:\n[]\n\n### End'}"
490,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8542\n\n### Instruction:\nI\'m trying to generate Jan VTs but they are not going through.The Period is open\r\n !image-2023-02-13-16-00-41-177.png|thumbnail! \r\n\r\n !image-2023-02-13-16-01-03-177.png|thumbnail! \n\n### Response:\n[\'Comment 1: [""Probably the period of trade operations was closed by accident and later opened. The ERP integrator has updated information about the period closing and that\\\'s why the VT was not generated.We were restarting the ERPIntegrator\', \'Comment 2: the DHC settings were updated again and VT was generated in ERP.""\', ""Comment 3: \'Confirmed on Teams by Nosipho !screenshot-1! \']""]\nRelated Issues:\n[]\n\n### End'}"
491,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8541\n\n### Instruction:\nDears,\r\n\r\nthe following PO numbers are in DHC and not in DHP:\r\n\r\n23009497\r\n23009498\r\n23009499\r\n23009500\r\n23009501\r\n23009502\r\n23009503\r\n\r\nplease check as intake stopped.\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Orders are now in DHP"", \'Comment 3:  !screenshot-2!  !screenshot-3! after restarting the server\', ""Comment 4: IIS services had to be restarted. !screenshot-1! \'"", \'Comment 5: \\\'{code:java}2023-02-13 12:37:59 (/Plant.DHC.Integration/DHP-3/8476/16) [Warning] RawRabbit.Channel.ChannelFactory - Connection was shutdown by Peer. ReplyText ""CONNECTION_FORCED - broker forced connection closure with reason \\\\\\\'shutdown\\\\\\\'""{code}\\\'\', ""Comment 6: \'Thanks Piotr.\'"", \'Comment 7: ""You\\\'re welcome.""]\']\nRelated Issues:\n[]\n\n### End'}"
492,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8540\n\n### Instruction:\nWiola zgłasza błędne działanie funkcjonalności do cofania anulowania wynagrodzeń(komunikat na zrzucie ekranu).\r\n\r\nProśba o cofnięcie anulowania wynagrodzenia dla pracownika Pinkas Mariusz:\r\n\r\nE-UM/2022/01/209\r\n\r\nE-UM/2022/02/74\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Proszę o weryfikację połączenia przez VPN"", ""Comment 3: jest zrywane bez żadnego komunikatu\'"", ""Comment 4: \'Anulowanie dla wskazanych wypłat zostało wycofane"", ""Comment 5: przyczyna komunikatu był indywidualny triggerKR_UpdateWPLZamknieta pilnujący poprawności opisów analitycznych. Pracownik na obecnym zatrudnieniu ma inny opis analityczny niż na anulowanej wypłacie stąd komunikat. Sama funkcja działa prawidłowo. Jeśli istnieje taka potrzeba można rozbudować trigger o dodatkowe warunki ale w ramach osobnego zamówienia i wyceny.\'"", ""Comment 6: \'Dzięki za pomoc"", ""Comment 7: do zamknięcia :)\']""]\nRelated Issues:\n[]\n\n### End'}"
493,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8539\n\n### Instruction:\nThe following recipes are not sent to the PCS.\r\nThey do exists in DHP.\r\n\r\n966715 \r\n960840\r\n\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Dear Wijnand,Under DB I can see recipes are in PCS now. Please"", ""Comment 3: werify.Regards\'"", ""Comment 4: \'!image-2023-02-13-14-34-36-107.png!!image-2023-02-13-14-34-55-161.png!!image-2023-02-13-14-35-26-037.png!\'"", ""Comment 5: \'Hi"", ""Comment 6: the recipes are in the PCS. Thanks!\']""]\nRelated Issues:\n[]\n\n### End'}"
494,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8538\n\n### Instruction:\nLot reports are not send from DHP to DHC. The status in DHP is \'Finished\'. This holds for the following lot reports: 0092040223001, 0092040223002, 0093100223056, 0092040223003, 0093100223053, 0093100223064, 0092110223011\n\n### Response:\n[""Comment 1: [\'Hello,\\\\r\\\\rWe are investigating your issue. We will inform you about the solution as soon as possible.\\\\r\\\\rRegards\\\\r\\\\r\'"", ""Comment 2: \'!image-2023-02-13-14-14-43-811.png!\'"", ""Comment 3: \'Could you please press confirm onh5. 0093100223056 and verifyalso0092040223001"", \'Comment 4: 0092040223002\', ""Comment 5: are cancell now!image-2023-02-13-14-17-52-611.png!\'"", \'Comment 6: ""I can confirm 0093100223056 needs to be send. The ones with status cancelled\', \'Comment 7: doesn\\\'t need to be send.""\', ""Comment 8: \'Let me know when you confirm 0093100223056.\'"", \'Comment 9: ""w logach z produkcji wisza na inboud wiaodmosci\', \'Comment 10: w pliku logów jak sie przywiesi trzeba sprawdzic czy jest log w logach tesktowych modulu prodkolejke zblokowal error typu :2023-02-13 00:00:00 (/Plant.Prod.BusinessLogic/DHVD01AP203/4900/35) [Error] Kotrak.Common.Infrastructure.Integration.Jobs.InboundProcessJob - Error during inbound processingMicrosoft.EntityFrameworkCore.DbUpdateException: An error occurred while saving the entity changes. See the inner exception for details. ---> Microsoft.Data.SqlClient.SqlException (0x80131904): Violation of PRIMARY KEY constraint \\\'PK_Errors\\\'. Cannot insert duplicate key in object \\\'dbo.Errors\\\'. The duplicate key value is (0e883ddf-0f20-46d5-97f9-7fb254896233).The statement has been terminated. * trzeba wywyalic z tabeli intercontst wpis * FROM [DHPlantProdBusinessLogicIntercontext].[dbo].[Errors] where id jak np (0e883ddf-0f20-46d5-97f9-7fb254896233)iloc wiadomosci an inboud :SELECT count (id) FROM [DHPlantProdBusinessLogicIntercontext].[dbo].[InboundMessages]""\', ""Comment 11: \'We have verified that there were problems with the queue of messages"", \'Comment 12: incoming to the production module\', \'Comment 13: which may interfere with the work\', \'Comment 14: the queue has been started and gradually descend the messages\', ""Comment 15: we are monitoring. Please try to confirm the remaining PLR and let us know if it helped.\'"", \'Comment 16: ""The PLR\\\'s I mentionned are from a couple days ago\', ""Comment 17: so I don\'t expect them in the queue. The status of those PLR\'s are already on \'Finished\'"", \'Comment 18: so I shouldn\\\'t confirm them again. It should be resended again from DHP.""\', ""Comment 19: \'pierwsze są z 08.02 które czekają mimo że lista spada zostają . !screenshot-1! \'"", ""Comment 20: \'The problem with the processing of messages has been since February 8"", ""Comment 21: so currently after clearing the process( the message must go down).You can try to manually confirm documents to go out of the queue.\'"", ""Comment 22: \'To confirm these  PLRs quantities are needed to be added( by inventory).We can do it and confirm  these PLRs - but we need confirmation from you. !screenshot-2! \'"", ""Comment 23: \'- dodanie ownera do dbo.owners w bazie  prod(z bazy stock)- przesunięcie stockunitcreated dla ProcessDate - 6dni- dodanie stockunitcreated z error do kolejki inbound production z datą -10dni\'"", ""Comment 24: \'tyle zostało: !screenshot-3! {code:java}SELECT count(id)FROM [DHPlantProdBusinessLogicIntercontext].[dbo].[InboundMessages]{code}\'"", ""Comment 25: \'Message queue is empty. Please check.\'"", ""Comment 26: \'[[DHP 3.0] kolejki dla modułu planta np. inbound prod|onenote:https://kotrak.sharepoint.com/sites/erpasysta/Shared%20Documents/Baza%20wiedzy/Baza%20Wiedzy%20-%20ERPSD/Klienci/DEHEUS/DEHEUS%20APPLICATIONS/Holandia%20Premix%20i%20AS400/Baz%20wiedzy%20z%20AS400.one#%5bDHP%203.0%5d%20kolejki%20dla%20modu%C5%82u%20planta%20np.%20inbound&section-id=\\\\\\\\{9BB564BA-0B58-4580-B9E0-F3CF9D6D80A7}&page-id=\\\\\\\\{B86DBAE3-055E-48BC-A0F3-028121592873}&end] ([Widok sieci Web|https://kotrak.sharepoint.com/sites/erpasysta/_layouts/OneNote.aspx?id=%2Fsites%2Ferpasysta%2FShared%20Documents%2FBaza%20wiedzy%2FBaza%20Wiedzy%20-%20ERPSD&wd=target%28Klienci%2FDEHEUS%2FDEHEUS%20APPLICATIONS%2FHolandia%20Premix%20i%20AS400%2FBaz%20wiedzy%20z%20AS400.one%7C9BB564BA-0B58-4580-B9E0-F3CF9D6D80A7%2F%5BDHP%203.0%5D%20kolejki%20dla%20modu%C5%82u%20planta%20np.%20inbound%7CB86DBAE3-055E-48BC-A0F3-028121592873%2F%29])\'"", ""Comment 27: \'Hello"", ""Comment 28: can we close this task?\'"", ""Comment 29: \'Hello,We are closing this task as we haven’treceivedany replyfromyouforalong time. If the issueappearsagain"", ""Comment 30: please raise another task.Regards\']""]\nRelated Issues:\n[]\n\n### End'}"
495,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8537\n\n### Instruction:\nCan you move the feed delivery date before 01-10-2022 from 100451 > 51199\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Hello Bert,There are 33 lines on this Feed sale (FE-V/0001) with delivery date before 01-10-2022!image-2023-02-13-14-07-37-508.png!Should we moved all these lines to FE-V/0002 (customer 051199)?\'"", ""Comment 3: \'Yes indeed\'"", ""Comment 4: \'All feed sale lines with delivery date before 01-10-2022 have been moved fromFE-V/0001 toFE-V/0002.\']""]\nRelated Issues:\n[\'DGS-8549\']\n\n### End'}"
496,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8536\n\n### Instruction:\nIt should be possible to create credit invoices for SI and PI invoices in all sectors when this invoice is on Saldo to Pay.\r\n\r\nSystem shouldn\'t verify that invoice are on S2P or not.\n\n### Response:\n[\'Comment 1: [""Now it\\\'s possible to use action of crediting invoices for all invoices (SI and PI) in all sectors.It\\\'s not verified right now that invoice is already on Saldo to pay document\', ""Comment 2: then it\'s possible to credit all invoices"", \'Comment 3: it doesn\\\'t matter that this invoice is on S2P or not.It has been modified on test and production environmnents.Please verify that it\\\'s possible to use this action right now.""\', ""Comment 4: \'Zmieniona funkcjaKR_ReversebookingButton_Visible"", ""Comment 5: która odpowiada za podłączenie akcji.\'"", ""Comment 6: \'Is working properly.\'"", ""Comment 7: \'Can be closed.\']""]\nRelated Issues:\n[]\n\n### End'}"
497,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8535\n\n### Instruction:\nHello,\r\n\r\nWe see 2 lot reports with status finished not being send to ERP: Can you check why and resend these? Expect the problem is in DHC, but could be also DHP?\r\n\r\nlot report numbers:\r\n0093100223053\r\n0093100223056\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'0093100223053 = 55ddba83-a09e-4e84-af6c-6db1ca8f597b0093100223056 =e1a5ab46-bd75-452d-86f2-55515e45fa7c\'"", ""Comment 3: \'!image-2023-02-13-12-44-04-085.png!!image-2023-02-13-12-44-23-578.png!\'"", ""Comment 4: \'!image-2023-02-13-12-50-29-851.png!!image-2023-02-13-12-51-07-402.png!\'"", ""Comment 5: \'Hi Thomas,I can see confirm button is active for both PLRs. PLRs are sent to DHC only when they are in confirmed status. Could you please check if you can confirm both PLRs?Regards\'"", \'Comment 6: ""Hi Aleksandra\', \'Comment 7: for the DHP\\\'s used by the Netherlands it is configured that lot reports are also send in status finished (Finished product quantity is send) I assume this is also configured for Helmond?""\', ""Comment 8: \'Hi Thomas,Please check today per solution in taskDGS-8538.Regards\'"", ""Comment 9: \'Ticket  can be closed\'"", ""Comment 10: \'ok"", ""Comment 11: thank you\']""]\nRelated Issues:\n[]\n\n### End'}"
498,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8534\n\n### Instruction:\nconfig for order status from which a PRO can be created is set to ""confirmed and in progress"" but if you click on \'select all\' (create based on order >> order filter) all statuses reappear.\n\n### Response:\n[""Comment 1: [\'[^filter PRO.mp4] _(823 kB)_!image!\'"", ""Comment 2: \'Hello,\\\\r\\\\rWe are investigating your issue. We will inform you about the solution as soon as possible.\\\\r\\\\rRegards\\\\r\\\\r\'"", ""Comment 3: \'Dear Thabile,Select all means select all statuses"", \'Comment 4: from created to cancelled. Please\', \'Comment 5: provide me detailed information\', ""Comment 6: what should appear after choosing all statuses?Regards\'"", \'Comment 7: \\\'Hi AleksandraA change request was submited to restrict what could be seen/used from this screen. We\\\\\\\'ve set the config to only show ""in progress"" and ""confirmed orders"". Therefore the ""Select All"" option should obey the same rules. It makes no sense to be able to configure the system to not show these orders and be easily bypassed by checking ""Select All"".Regards\\\'\', ""Comment 8: \'Hi Rey,Are you able to provide me with the change request number?Regards\'"", ""Comment 9: \'https://helpdesk.kotrak.com/browse/GDC-550\'"", ""Comment 10: \'Thank you\'"", ""Comment 11: \'Hi [~RvanRooyen@deheus.com]"", ""Comment 12: [~tdladla@deheus.com],I created the GDC task for the fix to be implemented under the GDC-834.Regards\'"", ""Comment 13: \'Thank you. The ticket may be closed.\'"", ""Comment 14: \'Thank you.\']""]\nRelated Issues:\n[]\n\n### End'}"
499,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8533\n\n### Instruction:\nPlease check the screenshot. It appears that i do not have access rights to see all the tickets in this case dgs8522. So please expand my rights so I can see all the tickets created by anyone in RS. Thank you.\n\n### Response:\n[""Comment 1: [\'!CannotSee8522ticket.PNG|thumbnail!\'"", ""Comment 2: \'I have added you as a request participants to task DGS-8522.Please"", ""Comment 3: verify.Regards\'"", ""Comment 4: \'Now I can I access. Thank you for your quick help. Best regards.\'"", ""Comment 5: \'Thank you.\'"", ""Comment 6: \'Hello again. It appears that still I do not have access rights to se all the incidents in RS created by anyone. Namely Nemanja just created one incident and I could not see it until he added me manualy via SHARE. Can you please give me same rights as Nemanja Antonic for RS incidents? Thank you.\']""]\nRelated Issues:\n[]\n\n### End'}"
500,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8532\n\n### Instruction:\nHi, \r\n\r\nWe cannot close JO 315/23/AY and show error message as ""Missing Quantity"" to 9105. However, there is enough stock on 9105. No missing resources.\r\n\n\n### Response:\n[""Comment 1: [\'!JO_20230213-1.JPG|thumbnail!!JO_20230213-2.JPG|thumbnail!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'prawdopdoobnie problemem sa rezerwacje na joselect sum(rez_ilosc) from cdn.Rezerwacje join cdn.twrkarty on twr_gidnumer=rez_twrnumer where rez_twrnumer=1084 and Rez_MagNumer=34\'"", ""Comment 4: \'May I know any update?\'"", ""Comment 5: \'Hi ClaraSorry for the delay.As I see now "", ""Comment 6: the JO -315/23/AY was closed by Melody.Item 9105 was released.\'"", \'Comment 7: ""I checked that there was released item TC9105 instead of 9105.I think that probable reason of problems with releasing item 9105 was reservation of delivery  IR+315/23/AY - 2/9/2023and system configuration that doesn\\\'t allow to you to release item before delivery date.There are resources on 9105 but delivery date is later then   2/9/2023. !screenshot-1! ""\', ""Comment 8: \'We do fix that JO and now is ok. Please proceed to close the ticket. Thank\']""]\nRelated Issues:\n[]\n\n### End'}"
501,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8531\n\n### Instruction:\nHi\r\n\r\nOrder SO-8534/22/UMR missing from DHP Umlaas.\r\n\r\nI can\'t find it in DHC either, but this may be a filter.\r\n\r\nI\'m busy with something, but will check back soon.\r\n\r\nRegards\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'2023-02-12 17:23:25,124 [SoapERPService_50] DEBUG Evolution.ErpIntegrator.Services.ERP.CdnXL.SoapERPService [(null)] - Recived Order message from trigger - ID - 7904202023-02-12 17:23:25,155 [SoapERPService_50] DEBUG Evolution.ErpIntegrator.Services.ERP.CdnXL.SoapERPService [(null)] - Order data downloaded - SO-8534/22/UMR2023-02-12 17:23:25,155 [SoapERPService_50] DEBUG Evolution.ErpIntegrator.Services.ERP.CdnXL.SoapERPService [(null)] - Sending Order message - SO-8534/22/UMR2023-02-12 17:23:25,155 [SoapERPService_50] DEBUG Evolution.ErpIntegrator.Services.ServiceManager [(null)] - Order message mapping.... (Firma:556290 - TYP:960/NUMER:790420/LP:0"", \'Comment 3: SO-8534/22/UMR)2023-02-12 17:23:25,202 [SoapERPService_50] DEBUG Evolution.ErpIntegrator.Services.ServiceManager [(null)] - Order message mapped (Firma:556290 - TYP:960/NUMER:790420/LP:0\', \'Comment 4: SO-8534/22/UMR)2023-02-12 17:23:25,202 [SoapERPService_50] DEBUG Evolution.ErpIntegrator.Services.ServiceManager [(null)] - Order message send (Firma:556290 - TYP:960/NUMER:790420/LP:0\', \'Comment 5: SO-8534/22/UMR)2023-02-12 17:23:26,870 [66] DEBUG Evolution.ErpIntegrator.Services.DHC.DHCBusService.Handlers.Documents.Orders.OrderBusinessPartnerAddressIsNotSynchronizedMessageHandler [(null)] - Order OrderId: 0ad206ce-8050-41c7-ba28-36c3140c8e2c BusinessPartnerAddress: c571ba02-6055-4b41-bbfd-01afbee3a32e is not synchronized2023-02-12 17:23:26,870 [66] INFO Evolution.ErpIntegrator.Services.DHC.DHCBusService.Handlers.Documents.Orders.OrderBusinessPartnerAddressIsNotSynchronizedMessageHandler [(null)] - ResynchronizeDataExtension is off - resynchronization skipped2023-02-12 17:23:39,183 [26] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor [(null)] - VehicleTicketProcessor execution started2023-02-12 17:23:39,459 [26] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor [(null)] - VehicleTicketProcessor execution finished2023-02-12 17:23:39,459 [26] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.ProductionLotReports.ProductionLotReportProcessor [(null)] - ProductionLotReportProcessor execution started2023-02-12 17:23:39,475 [26] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.ProductionLotReports.ProductionLotReportProcessor [(null)] - ProductionLotReportProcessor execution finished2023-02-12 17:23:43,012 [SoapERPService_16] DEBUG Evolution.ErpIntegrator.Services.ERP.CdnXL.SoapERPService [(null)] - Recived Order message from trigger - ID - 7904202023-02-12 17:23:43,028 [SoapERPService_16] DEBUG Evolution.ErpIntegrator.Services.ERP.CdnXL.SoapERPService [(null)] - Order data downloaded - SO-8534/22/UMR2023-02-12 17:23:43,028 [SoapERPService_16] DEBUG Evolution.ErpIntegrator.Services.ERP.CdnXL.SoapERPService [(null)] - Sending Order message - SO-8534/22/UMR2023-02-12 17:23:43,028 [SoapERPService_16] DEBUG Evolution.ErpIntegrator.Services.ServiceManager [(null)] - Order message mapping.... (Firma:556290 - TYP:960/NUMER:790420/LP:0\', \'Comment 6: SO-8534/22/UMR)2023-02-12 17:23:43,044 [SoapERPService_16] DEBUG Evolution.ErpIntegrator.Services.ServiceManager [(null)] - Order message mapped (Firma:556290 - TYP:960/NUMER:790420/LP:0\', \'Comment 7: SO-8534/22/UMR)2023-02-12 17:23:43,059 [SoapERPService_16] DEBUG Evolution.ErpIntegrator.Services.ServiceManager [(null)] - Order message send (Firma:556290 - TYP:960/NUMER:790420/LP:0\', ""Comment 8: SO-8534/22/UMR)2023-02-12 17:23:44,135 [51] DEBUG Evolution.ErpIntegrator.Services.DHC.DHCBusService.Handlers.Documents.Orders.OrderBusinessPartnerAddressIsNotSynchronizedMessageHandler [(null)] - Order OrderId: 0ad206ce-8050-41c7-ba28-36c3140c8e2c BusinessPartnerAddress: c571ba02-6055-4b41-bbfd-01afbee3a32e is not synchronized2023-02-12 17:23:44,135 [51] INFO Evolution.ErpIntegrator.Services.DHC.DHCBusService.Handlers.Documents.Orders.OrderBusinessPartnerAddressIsNotSynchronizedMessageHandler [(null)] - ResynchronizeDataExtension is off - resynchronization skipped2023-02-12 17:23:54,191 [16] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor [(null)] - VehicleTicketProcessor execution started\'"", ""Comment 9: \'Przesynchronizowano ponownie - log w komentarzy wyżej.\'"", \'Comment 10: ""We tried to re-sync the document but it won\\\'t create. This document is from the time of the inventory.Could you SO be canceled and reissued?If this doesn\\\'t solve the problem\', \'Comment 11: can we change this priority to P2 and verify the problem with the development department first thing tomorrow morning?""\', \'Comment 12: ""I\\\'ve asked. If you are unable to solve the issue\', \'Comment 13: then drop to a P2.""\', \'Comment 14: ""Needs ti be bumped back to a P1. Order SO-691/23/UMR done to replace order is not sync\\\'ing either.""\', ""Comment 15: \'Can you confirm you are working on this?\'"", ""Comment 16: \'Yes. We are working on it\'"", ""Comment 17: \'Please check now it should be ok\'"", ""Comment 18: \'Asking production to check.\'"", ""Comment 19: \'There was a problem with address synchronization. I forced sync again and order showed up in the system. Please check if other orders from this contractor are correct.\'"", ""Comment 20: \'Thank you. You may close the ticket.Have a good evening.\']""]\nRelated Issues:\n[]\n\n### End'}"
502,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8530\n\n### Instruction:\nPlease help to check this case and solving in Hai Phong 2Plant -0436.\r\n\r\nPLR 4361100223101 could not be found in the Production Report module (Maybe, user deleted this PLR) . But release to stock with stock unit status In progress . Please check and clear this stock unit . Thank u\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Yes"", \'Comment 4: indeed\', \'Comment 5: PLR was in Stock module\', \'Comment 6: so probably it has been deleted by user from Production module.Stock Unit is cleared. Please\', ""Comment 7: verify.Regards\'"", ""Comment 8: \'Dear AleksandraU can close this ticket. Thank u.\'"", ""Comment 9: \'Thank you\']""]\nRelated Issues:\n[]\n\n### End'}"
503,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8529\n\n### Instruction:\nHi\r\n\r\nWe just received the information that Microsoft is validating the security protocol:\r\nbq. Any non-TLS 1.2 compliant and older cipher suites will no longer be supported.\r\n\r\nIn August/2022 we had a DGS-7365 because the security protocol was changed and our Microsoft partner forgot to communicate us about the change. Then Przemysław Przybyszewski made the fix for us.\r\n\r\nI\'d like to know if *the fix done in August is already with TLS 1.2?*\r\n\r\nYou can check it here: [Link here|https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/get-started/removed-deprecated-features-platform-updates#transport-layer-security-tls-rsa-cipher-suites]\r\n\r\nThank you very much\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Please be informed that we have forwarded the issue to the development team in order to internal analysis.We are waiting for more details and will be back with further information as soon as possible.\'"", ""Comment 3: \'[~mberbert@deheus.com]we made changed according to this article [https://learn.microsoft.com/en-us/mem/configmgr/core/plan-design/security/enable-tls-1-2-client]so it should be on TLS 1.2\'"", ""Comment 4: \'Hi PrzemysławThank you very much for this information.You can close this task\']""]\nRelated Issues:\n[]\n\n### End'}"
504,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8528\n\n### Instruction:\nRecipe 110469 did not arrive in Maasbracht.\r\n\r\nI see an error in DHC, see attached screenshot.\n\n### Response:\n[""Comment 1: [\'!2023-02-10 19_57_51-Window!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Hi Bartlomiej"", \'Comment 4: any update to mention? I got a call from the people\', ""Comment 5: they are really urgently waiting on it.\'"", \'Comment 6: ""Please give us a moment. We\\\'re working on it""\', ""Comment 7: \'Sure"", ""Comment 8: thanks!\'"", ""Comment 9: \'Please check. Now it should be ok.\'"", \'Comment 10: ""I see\', \'Comment 11: thanks!I\\\'ve asked if the planning dept. can proceed. Will update you soon.""\', ""Comment 12: \'It is indeed in DHP now"", ""Comment 13: but not in PCS. Any suggestions?\'"", \'Comment 14: ""Probably a PCS issue. On a truckplanning list in the PCS they see it\', \'Comment 15: but not in production.They\\\'ll call PCS supplier.""\', ""Comment 16: \'OK thanks for the information. It should appear in PCS if it is correct in DHP.Please let me know how to contact PCS.\'"", ""Comment 17: \'The people in the factory will do that. We can close this ticket. Please provide an RCA (can be done next week).Thanks for the support!\'"", ""Comment 18: \'The issue is fixed in version 3.0.60 of DHC.RCA is DGS-8487\']""]\nRelated Issues:\n[\'DGS-8487\']\n\n### End'}"
505,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8527\n\n### Instruction:\nPomyłka operatora. Proszę o zmianę indeksu na W00.\r\nProszę o dokonanie potrzebnych zmian w DHP, DHC i CDN\r\n\r\nPasza pilna do workowania.\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'If I understand correctly issue is related to LOT 0211100223032. This lot is confirmed. That mean it has been send to DHC and documents in ERP system has been generated (ZP-443/02/23/G and PW-442/02/23/G)We are sugesting to create new lot and proceed it for new production. Existing dokuments forLOT 0211100223032 in ERP systems should be cancelled and quantity for resources in DHP have to be corrected trough stocktaking.The work related to correcting this situation from the database will take several hours and we cannot guarantee that as a result of them there will be no problems with this product in the future.\'"", ""Comment 4: \'Task to close \'"", ""Comment 5: \'Jakby się powtórzył taki błąd - do poprawy od bazy.Informacja po retro.\']""]\nRelated Issues:\n[]\n\n### End'}"
506,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8526\n\n### Instruction:\nI am not able to calculate technical results.\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 3: ""We\\\'ve fixed this issue with procedure parameter. Now it should be good.Regards""\', ""Comment 4: \'It is working again.\'"", ""Comment 5: \'I close the task - it was related toDGS-8325\']""]\nRelated Issues:\n[\'DGS-8325\']\n\n### End'}"
507,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8525\n\n### Instruction:\nThe PO 1260/12/22 has been intaked with VT 154/2/23 but the resulting POR is not showing up in ERP, i have also checked in DHC yet nothing to indicate it has been processed\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'!image-2023-02-10-12-17-09-600.png!\'"", ""Comment 3: \'!image-2023-02-10-12-20-22-825.png!\'"", ""Comment 4: \'!image-2023-02-10-12-23-22-275.png!\'"", ""Comment 5: \'w DHC VT jest spięty juz z zrealizowanym IO - 181 "", \'Comment 6: po 1260 jest w ogole na inny item,który został zrealizowanym innym dokumentem ale wg erp xl w opsiei dla io - vt 157 a nie 154select cdn.NazwaObiektu(TrN_GIDTyp,TrN_GIDNumer,1,2),trn_openumerw,tno_opis,cdn.NazwaObiektu(zan_gidtyp,zan_gidnumer,1,2)\', ""Comment 7: trn_zannumer,* from cdn.ZamNag  left join cdn.tranag on zan_gidnumer=TrN_ZaNNumer join cdn.TrNOpisy on TnO_TrnNumer=TrN_GIDNumer where trn_zannumer in (27466,27461,25355)!image-2023-02-10-13-11-42-852.png! !image-2023-02-10-13-15-48-519.png! !image-2023-02-10-13-11-42-852!!image-2023-02-10-13-15-48-519!\'"", ""Comment 8: \'wg bazy danych sa dwa vt o numerze 154 na luty :!image-2023-02-10-13-25-11-962.png!\'"", ""Comment 9: \'Hello could you please provide full VT numberbecuase in data base I can see 2 vt:154/2/2023/AC 154/2/2023/JNI DHC country I can see only this154/2/2023/JN it is on hold status and linked to diffrent order= IO 181 and it is in onhold status.It is for diffrent item then the order po 1260 in ERPXLAlso this item is set as not generated"", \'Comment 10: because the IO-481 was executed by VTVT-157/2/2023/AC and it was executed buy next one. Let me know\', \'Comment 11: if the realization for IO 181 is correct\', ""Comment 12: if yes andIf forvt -154/2/2023/JN informationare sufficient for you let me now. If you do not want to proceed the vt-154/2/2023/JN - you may hold/cancel it.!image-2023-02-10-13-37-22-784.png!THE second154/2/2023/AC with AC extension was invisible in application cause it has no elements synchronized to DHC.!image-2023-02-10-13-48-33-390.png!But it is in dhp :with connection to order po-1260!image-2023-02-10-13-53-00-021.png! !image-2023-02-10-13-53-00-021!I resend this VT again to DHC!image-2023-02-10-14-23-50-373.png!And POR was generated :!image-2023-02-10-14-25-13-900.png!!image-2023-02-10-14-23-50-373! !image-2023-02-10-14-25-13-900!\'"", \'Comment 13: ""id vt w dhp\\\'id=2c3cbce0-0cfc-4011-915d-4305f52df6a0\\\'""\', ""Comment 14: \'PLEASE CLOSE\']""]\nRelated Issues:\n[]\n\n### End'}"
508,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8524\n\n### Instruction:\nWe would like to have the same ""add/change conditions"" functionality available on SC\'s as we have on contracts farmer.\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 2: ""[~mbovene@deheus.com]did you mean there is needed flow fro \\\'Contract Slaughtery\\\' document (not Slaughtery Report) as it is in \\\'Contract farmer\\\' document?When document is \\\'Active\\\' and we want to send it to \\\'Add change conditions\\\' to which users it should be processed? (In Contract farmer process it is sent to users from role \\\'Senior contract administrator\\\')""\', ""Comment 3: \'Yes indeed\'"", \'Comment 4: \\\'[~mbovene@deheus.com],I added new flows ""Add/change conditions"" from ""Active"" status for Contract Slaughtery MAS NL and MAS BE on test environment.You can feel free to test it.Best regards,Grzegorz\\\'\', ""Comment 5: \'Tested"", ""Comment 6: can be moved to PROD.\'"", ""Comment 7: \'[~mbovene@deheus.com],the new flows added to PROD process.You can feel free to test it.Best regards,Grzegorz\'"", ""Comment 8: \'Confirmed that can be closed.\']""]\nRelated Issues:\n[]\n\n### End'}"
509,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8523\n\n### Instruction:\nOn Feed sale line in \'Move to round number\' should be possible to choose rounds from other customer who has the same invoice customer like this one on Feed sale.\n\n### Response:\n[\'Comment 1: [\\\'Hi,adjustements on ""Move to another feed sale"" lookup have been done for Feed Sale elements. You can feel free to test it on test environment.Best regards\', ""Comment 2: Grzegorz\'"", ""Comment 3: \'In Production?\'"", ""Comment 4: \'[~mbovene@deheus.com]"", ""Comment 5: I forgot to write this in comment. On the test environment.\'"", ""Comment 6: \'No problem. I have tested this and it works fine. Can be moved to PROD.\'"", \'Comment 7: ""[~mbovene@deheus.com]\', \'Comment 8: the modification has been adjusted on production environment. I\\\'m waiting for respone to close the task.Best regards,Grzegorz""\', ""Comment 9: \'It should be possilbe to choose rounds like on the example below:Customer A "", \'Comment 10: Invoice Customer BCustomer C\', \'Comment 11: Invoice Customer BCustomer D\', ""Comment 12: Invoice Customer EFeed sale on Customer A - should be possible to choose round from Customer A and C (because there is connection between invoice customer)\'"", ""Comment 13: \'HI"", \'Comment 14: it can also be like this:Customer A \', \'Comment 15: Invoice Customer BCustomer B\', \'Comment 16: Invoice Customer BCustomer D\', ""Comment 17: Invoice Customer DThan as well A and B are able to send feed sales to each other.\'"", \'Comment 18: \\\'Hi,we did rollback the settings on the field ""Move to round number"" on production database.The modifications for field have been added on test environment. You can feel free to test it.I\\\\\\\'m waiting for your reply to add it on prod environment.Best regards,Grzegorz\\\'\', ""Comment 19: \'In the test environment I should be able to move feed from and to these three rounds:* 00024J/0276/0001* 808104/0041/0001* 008104/0285/0001All these three customers have the invoice customer 008104. However I am not able to move feed from 00024J/0276/0001 to 008104/0285/0001"", ""Comment 20: not from 00024J/0276/0001 to 808104/0041/0001.\'"", ""Comment 21: \'[~mbovene@deheus.com],I made changes in this area and now it looks good.!image-2023-02-13-11-51-50-132.png!\'"", ""Comment 22: \'OK"", ""Comment 23: can be moved to PROD.\'"", \'Comment 24: \\\'It would be nice if the same procedure (being able to move to different delivery customer but the same invoice customer) is available for the functionality ""Update round number on invoice"".Is that possible?\\\'\', ""Comment 25: \'[~mbovene@deheus.com],done. You can feel free to test it on production environment.\'"", \'Comment 26: \\\'I\\\\\\\'m looking into action and I see that right now the customer on ""Round"" lookup is selected with conditions: * SI: when Customer of Sales invoice has BP_Category -""Slaughter"" then we are use Referance but in other cases we are use Customer field. * PI: when Customer of Purchase invoice has BP_Category - ""Farmer""\', \'Comment 27: ""Pas Farmer""\', \'Comment 28: ""Oppas farmer"" then we are use Referancebut in other cases we are use Customer field.So\', ""Comment 29: for sure are you want to add the funtionality for more Rounds on list for these two cases: Customer and Reference?\'"", ""Comment 30: \'I am not sure if I get you. I am not sure how the reference is involved in this.It should be like this: if a specific invoice is now on round for customer A and customer A has invoice customer B than it should be possible to move this invoice to other rounds that are related to invoice customer B:Customer A "", \'Comment 31: Invoice Customer BCustomer B\', \'Comment 32: Invoice Customer BCustomer D\', ""Comment 33: Invoice Customer DThan as well A and B are able to send invoices to each other.\'"", ""Comment 34: \'[~mbovene@deheus.com],I made changes on action"", ""Comment 35: you can feel free to test it on test environment.Best regards,Grzegorz\'"", ""Comment 36: \'Confirmed that can be closed.\'"", ""Comment 37: \'In NAS sectore change is needed - it should works like it was before. Should be possible to move feed to different round only for rounds from customer which is selected on header of the document.In other sectors it should be possible to choose rounds also from other customers which has the same invoice customer.\'"", ""Comment 38: \'[~grzegorz.materla@kotrak.com]do zmiany w sektorze NAS - powinno być tak jak wcześniej i dać się wybrać rundy powiązane tylko z kontrahentem"", ""Comment 39: który jest w nagłówku Feed sale.\'"", \'Comment 40: ""[~mbovene@deheus.com],we\\\'ve made changes in prod on Feed Sale elements in NAS.You can feel free to test it.Best regards,Grzegorz""\', ""Comment 41: \'Can be closed.\']""]\nRelated Issues:\n[\'DGS-8580\']\n\n### End'}"
510,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8522\n\n### Instruction:\nA colleague receives this message after entering comarch, when he clicks ok, everything works normally. This is not the case for other users, only for RRUISCH users. Do you know what the problem could be?\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Please check now"", ""Comment 4: how it works for this user.\'"", ""Comment 5: \'Everything works. Can you tell me what was the problem?\'"", ""Comment 6: \'The operator did not have the acc. period selected. !screenshot-1! Alternatively select a change for all operators.\'"", ""Comment 7: \'Ok"", ""Comment 8: tnx. You can close the ticket.\']""]\nRelated Issues:\n[]\n\n### End'}"
511,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8521\n\n### Instruction:\nGood morning,\r\n\r\nPlease could you take action on the next problem.\r\nIn DHC the item: 318547 is not sending tot DHP.\r\nOur production plant in Veghel is waiting for this and can\'t process while the item / recipe are not available on DHP.\r\n\r\nKind regards,\r\n\r\nGerard\n\n### Response:\n[""Comment 1: [\'Hello"", ""Comment 2: We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'!image-2023-02-10-07-06-09-974.png!\'"", ""Comment 4: \'@Lukasz"", \'Comment 5: it might not been only this item. For today\', ""Comment 6: there are also no orders in DHC. I think communication between DHC and DHP is failing completely\'"", ""Comment 7: \'318254318547\'"", ""Comment 8: \'@Theo"", \'Comment 9: we will check the communication. For now I can see this item is missing in DHC Service\', \'Comment 10: when I solve this issue\', ""Comment 11: we will check the communication\'"", ""Comment 12: \'I think both issues are related\'"", ""Comment 13: \'Recipe in DHP now!image-2023-02-10-07-19-35-140.png!\'"", \'Comment 14: ""That\\\'s great. Order SO000067034 still isn\\\'t. Should we export it again from ERP?""\', ""Comment 15: \'Let me check the order\'"", ""Comment 16: \'I see the order now"", ""Comment 17: thank you very much. What happened?\'"", ""Comment 18: \'Regarding orderSO000067034"", \'Comment 19: Main Business Partner and Payer have incorrect address\', \'Comment 20: they have address of Target Business Partner. Please\', ""Comment 21: ask order department to correct and resend prder.Regards\'"", ""Comment 22: \'And for the recipe?\'"", ""Comment 23: \'I know what happened. Apart from addresses"", \'Comment 24: the order was for requested item:318547. It did not drop to DHC service. I have resynces this item\', ""Comment 25: so the recipe appeared and order appeared as well. There was one more item to resync -318254. I have resynced it\'"", ""Comment 26: \'Ok"", ""Comment 27: clear. How can we prevent such issues? \'"", ""Comment 28: \'The issue is fixed in versio 3.0.60 of DHC\'"", \'Comment 29: ""I\\\'m trying to monitor items\', \'Comment 30: for example in RCADGS-8487 I have pushed 10 items yesterday.""\', ""Comment 31: \'Theo,Please"", ""Comment 32: let me know if we can close this task.Regards\'"", ""Comment 33: \'Thanks! Glad to hear that it is fixed in future version of DHC. I hope"", \'Comment 34: untill we have installed that version\', ""Comment 35: it doesnt occur too much.Many thanks for your help Aleksandra and Lukasz\'"", \'Comment 36: ""You\\\'re welcome\', \'Comment 37: Theo. Have a nice day!""]\']\nRelated Issues:\n[]\n\n### End'}"
512,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8520\n\n### Instruction:\n\xa0From Round\xa0808104/0041/0002 to round should be moved feed sale lines (sent in email).\r\n\r\n\xa0\r\n\r\nOn this Purchase invoices and also on linked SI and SR should be updated round number from\xa0808104/0041/0002 to\xa000024J/0276/0001\r\n\r\nPI-RLM/2023/0042\r\n\r\nPI-RLM/2023/0067\r\n\r\nPI-RLM/2023/0066\r\n\r\nPI-RLM/2023/0059\r\n\r\nPI-RLM/2023/0058\r\n\r\nPI-RLM/2023/0081\r\n\r\nPI-RLM/2023/0079\xa0\r\n\r\n\xa0\n\n### Response:\n[""Comment 1: [\'These three lines have been moved to this feed saleFE-M/0041 (round808104/0041/0001) - from FE-M/0380 and from FE-M/0447.!image-2023-02-09-15-26-49-816.png|id=x_imageSelected0!\'"", \'Comment 2: ""We\\\'ve updated data on: * Purchase Invoice -\\\'Supplier\\\'\', ""Comment 3: \'Full number\' * Sales Invoice -\'Reference\'"", ""Comment 4: \'Full number\' * Slaughtery report - \'Farmer\',\'Full number\'for these PI\'s"", \'Comment 5: linked SI\\\'s and SR\\\'s:|PI-RLM/2023/0042|SI-RLM/2023/0042|SR/2968||PI-RLM/2023/0059|SI-RLM/2023/0057|SR/2950||PI-RLM/2023/0067|SI-RLM/2023/0065|SR/2967||PI-RLM/2023/0081|SI-RLM/2023/0078|SR/2988||PI-RLM/2023/0058|SI-RLM/2023/0056|SR/2949||PI-RLM/2023/0066|SI-RLM/2023/0064|SR/2966||PI-RLM/2023/0079|SI-RLM/2023/0076|SR/2987|""]\']\nRelated Issues:\n[]\n\n### End'}"
513,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8519\n\n### Instruction:\nno orders are not syncing to DHC \r\n\r\nthe list we have thus far \r\nKB:\r\nSO-388/23/KBW\r\nSO-355/23/KBW\r\nSO-347/23/KBW\r\nSO-410/23/KBW\r\nSO-411/23/KBW\r\nSO-151/23/KBG\r\nSO-148/23/KBG\r\nSO-378/23/KBW\r\nSO-421/23/KBW\r\n\n\n### Response:\n[""Comment 1: [\'Hello,\\\\r\\\\rWe are investigating your issue. We will inform you about the solution as soon as possible.\\\\r\\\\rRegards\\\\r\\\\r\'"", ""Comment 2: \'KD:so-98/23/kdwso--314/23/klrso-315/23/klrso-317/23/klr so-197/23/kdwso-245/23/klrso-316/23/dkdUR: \\\\t76/23/UMR270/23/UMR285/23/UMR363/23/UMR392/23/UMR474/23/UMR475/23/UMR\'"", \'Comment 3: ""aktualnie ejst tylko 355select top 100 DocumentNumber,*from orders where DocumentNumber in (\\\'SO-388/23/KBW\\\',\\\'SO-355/23/KBW\\\',\\\'SO-347/23/KBW\\\',\\\'SO-410/23/KBW\\\',\\\'SO-411/23/KBW\\\',\\\'SO-151/23/KBG\\\',\\\'SO-148/23/KBG\\\',\\\'SO-378/23/KBW\\\',\\\'SO-421/23/KBW\\\')""\', ""Comment 4: \'Order NumberSO-204/23/MOMSO-204/23/MOMSO-205/23/MOMSO-205/23/MOMSO-242/23/MOMSO-242/23/MOMSO-242/23/MOMSO-89/23/MMWSO-89/23/MMWSO-89/23/MMWSO-89/23/MMWSO-89/23/MMWSO-92/23/MMWSO-92/23/MMWSO-92/23/MMWSO-92/23/MMWSO-92/23/MMWSO-92/23/MMWSO-254/23/MOMSO-255/23/MOM\'"", ""Comment 5: \'Próbowalam przeslac 388 ale bez skutku"", ""Comment 6: restrty nie pomagaja w logach nic nie widze ...\'"", ""Comment 7: \'tu wyglada jakby ordery prestaly isc o 10.25 !image-2023-02-09-14-09-50-856.png!\'"", ""Comment 8: \'Hello"", ""Comment 9:  please note that some of the branches are at a standstill\'"", \'Comment 10: ""Check I can see that all of this documents are in dhc :\\\'SO-388/23/KBW\\\',\\\'SO-355/23/KBW\\\',\\\'SO-347/23/KBW\\\',\\\'SO-410/23/KBW\\\',\\\'SO-411/23/KBW\\\',\\\'SO-151/23/KBG\\\',\\\'SO-148/23/KBG\\\',\\\'SO-378/23/KBW\\\',\\\'SO-421/23/KBW\\\'""\', \'Comment 11: ""po kosnulatacje z Przemkiem puscilam taki update jeszcze ,update cdn.ZamNag set zan_stan=zan_stan where (zan_zamrok=2023 and zan_zamseria in ( \\\'mmw\\\'\', ""Comment 12: \'mom\') and  zan_zamnumer in  (204"", \'Comment 13: 242\', \'Comment 14: 89 \', \'Comment 15: 92 \', \'Comment 16: 254\', \'Comment 17: 255)) or ( zan_zamrok=2023 and zan_zamseria in (\\\'kdw\\\',\\\'klr\\\') and (zan_zamnumer =197 or zan_zamnumer in (245,315,317,314,316,245))) or (zan_zamrok=2023 and zan_zamseria in ( \\\'umr\\\') and  zan_zamnumer in  (76,270,285,363,392,474,475 ))jak napisza ze czegos im barlk trzeba wymusic synchre w erp xl""\', ""Comment 18: \'From what I have verified also other mentioned order numbers are in DHC.\'"", ""Comment 19: \'DH_Sys który blokował tabele"", ""Comment 20: Przemek poprawił triggery i jakos poszlo\'"", ""Comment 21: \'May we close the task?\'"", ""Comment 22: \'Hello"", ""Comment 23: yes you may thank you\']""]\nRelated Issues:\n[]\n\n### End'}"
514,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8518\n\n### Instruction:\nI have changed the PO link on the VT listed in the attachment. Before that the VTs were NOT sent to ERP, because wrongly linked POs did not have sufficient quantity. I have changed the VT-PO link to correct PO, but I cannot sent the VT\'s to ERP, because there is validation in DHC that once VT was sent, it cannot be resent again, even if ERP rejected it. \r\nThat is why I ask for removing the message, and resending those VT again. If resending is a problem, pls remove the message, then I can resend them from DHC interface. (I hope it will work). PLs call me if you have any questions. \n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Hello,Kindly approve lowering priority of this task to P2 as P1 issues are only those with a critical or a blocking impact on business processes . This seems not to be the case in this issue so we suggest decreasing the issue priority.Regards\'"", ""Comment 4: \'And could you please let us know where do you exactly chnaged this linking? What table / db or under application?!image-2023-02-09-12-40-31-949.png!\'"", ""Comment 5: \'I changed it using the standard DHC functionality"", ""Comment 6: in the interface !image-1!\'"", ""Comment 7: \'nothing from tables \'"", ""Comment 8: \'Hello,Kindly approve lowering priority of this task to P2 as P1 issues are only those with a critical or a blocking impact on business processes . This seems not to be the case in this issue so we suggest decreasing the issue priority.Regards\'"", ""Comment 9: \'it is blocking the process since december"", \'Comment 10: when I lower the priority\', ""Comment 11: when it is resolved then? \'"", ""Comment 12: \'Mappings has been removed.\'"", ""Comment 13: \'According to service agreement"", \'Comment 14: P1 - are incident having a critical or blocking impact on business process which means De Heus cannot produce or deliver. If the issue exists from December\', \'Comment 15: 2022\', ""Comment 16: it is not blocking.\'"", ""Comment 17: \'Ok"", \'Comment 18: removed\', ""Comment 19: that means I can resend the tickets again? \'"", ""Comment 20: \'Yes"", \'Comment 21: You can try to resend them.Kindly approve lowering priority of this task to P2 as P1 issues are only those with a critical or a blocking impact on business processes .This seems not to be the case in this issue so we suggest decreasing the issue priority.According to service agreement\', \'Comment 22: P1 - are incident having a critical or blocking impact on business process which means De Heus cannot produce or deliver. If the issue exists from December\', \'Comment 23: 2022\', ""Comment 24: it is not blocking.\'"", ""Comment 25: \'Hi"", \'Comment 26: I have sent the VTs\', \'Comment 27: and some were recived by ERP properly\', \'Comment 28: but some not\', ""Comment 29: I am getting the following message in DHC: Evolution.DHCERPService.IdentityMapping.IdentityNotMappedException: Key of entity OrderElementMappingEntity was not mapped. Key value Id: 669944d2-2e07-4551-8c4d-2f178bc037c8   at Evolution.DHCERPService.IdentityMapping.IdentityMappingRepository`1.GetERPKey(GuidKey key) in E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\18317313\\\\\\\\DHAPPSV3-DHCER400-JOB1\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.IdentityMapping\\\\\\\\IdentityMappingRepository.cs:line 42   at Evolution.DHCERPService.WoWWebServiceClient.Services.IntakeServiceClient.SendIntake(VehicleTicket vehicleTicket) in E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\18317313\\\\\\\\DHAPPSV3-DHCER400-JOB1\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.WoWWebServiceClient\\\\\\\\Services\\\\\\\\IntakeServiceClient.cs:line 69\'"", ""Comment 30: \'also VT 419/12/2022 cannot be sent"", \'Comment 31: from one reason or another the button ""generate ERP document"" is inactive \\\'\', ""Comment 32: \'List of VTs which have mentioned error message in DHC !image-2!\'"", ""Comment 33: \'For VT-419/12/2022 was generated POR-419/12/2022/ document in ERP system. Please check if. Error message You have send is related to this document.Please check.\'"", ""Comment 34: \'Please check document 426/12/2022/. It look like it is use in ERP system.Rest of documents has been synchronised. Please verify.\'"", ""Comment 35: \'Please"", ""Comment 36: let me know do you expect any additional actions from us regarding this issue? Can we close this ticket?\'"", ""Comment 37: \'not yet"", ""Comment 38: we must verify well what had been done \'"", ""Comment 39: \'Waiting for your feedback then.Additionally"", \'Comment 40: according to service agreement\', \'Comment 41: P1 - are incident having a critical or blocking impact on business process which means De Heus cannot produce or deliver. If the issue exists from December\', \'Comment 42: 2022\', \'Comment 43: it is not blocking and verification is time consuming\', \'Comment 44: I insist on P2 priority.In P1 we are focusing on clearingandunblocking the process.If there is a need from your sideto investigate the reasonof the issue\', \'Comment 45: we may raise RootCause Analysis (RCA)task for you.Please\', ""Comment 46: let us knowhow you wish us to proceed.Regards\'"", ""Comment 47: \'no permission for RCA\'"", ""Comment 48: \'We will not create RCa then"", ""Comment 49: did you verify426/12/2022 and rest of the documents?\'"", ""Comment 50: \'Hello,We are closing this task as we haven’treceivedany replyfromyouforalong time. If the issueappearsagain"", ""Comment 51: please raise another task.Regards\']""]\nRelated Issues:\n[]\n\n### End'}"
515,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8517\n\n### Instruction:\nOn contract farmer and contracy slaughtery (linked to contract farmer) method in table \'Market indices prices\' (\'Pricing meat\' tab) should be updated on value = \'week\' for customers from list below.\r\n\r\n!image-2023-02-09-12-26-31-160.png!\r\n |200264|\r\n|200257|\r\n|200237|\r\n|200243|\r\n|200239|\r\n|200248|\r\n|200236|\r\n|200268|\r\n|200262|\r\n|200222|\r\n|200223|\r\n|200245|\r\n|200212|\r\n|200254|\r\n|200226|\r\n|200220|\r\n|200302|\r\n|200303|\r\n|200259|\r\n|200244|\r\n|200209|\r\n|200266|\r\n|200211|\r\n|200260|\r\n|200210|\r\n|102086|\r\n|200253|\r\n|2220|\r\n|200364|\r\n|200246|\r\n|200247|\r\n|200238|\r\n|122041|\r\n|200214|\r\n|200215|\r\n|200249|\r\n|200206|\r\n|200233|\r\n|200205|\r\n|101942|\r\n|187|\r\n|200305|\r\n|200256|\r\n|200258|\r\n|200228|\r\n|201|\r\n|200232|\r\n|200229|\r\n|200263|\r\n|200251|\r\n|200207|\r\n|200219|\r\n|101898|\r\n|200203|\r\n|200217|\r\n|200304|\r\n|200235|\r\n|101519|\r\n|101936|\r\n|200240|\r\n|200265|\r\n|200261|\r\n|200267|\r\n|200301|\r\n|200218|\r\n|200213|\r\n|200250|\r\n|200221|\r\n|5844|\r\n|200208|\r\n|125798|\r\n|B100061|\r\n|B100078|\r\n|B100056|\r\n|B100057|\r\n|B100049|\r\n|B100054|\r\n|B100059|\r\n|B100052|\r\n|B100079|\r\n|B100053|\r\n|B100058|\r\n|B005580|\r\n|B100075|\r\n|B100055|\r\n|B100051|\r\n|B100077|\r\n|B100080|\r\n\r\n\xa0\r\n\r\n\xa0\n\n### Response:\n[\'Comment 1: [""Lista Contract Slaughtery\', \'Comment 2: które też powinny być zaktualizowane o week w kolumnie \\\'Method\\\'[^Map2.xlsx]""\', ""Comment 3: \'[~damian.swistek@kotrak.com] wszystkie rekordy wraz z tymi w excel zostały zaktualizowane na bazie produkcyjnej :).\'"", \'Comment 4: ""Hi [~khuibers@deheus.com],all lines have been updated on production environment. You can feel free to test it.I\\\'m waiting for your response to close the task.Best regards,Grzegorz Materla""\', ""Comment 5: \'[~khuibers@deheus.com]could you confim?\'"", \'Comment 6: ""{color:black}Hello{color} {color:black}{color} {color:black}All contracts are ok{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | | | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.de-heus.nl/]>{color} | |  *{color:#006FB7} *DEHEUSVOEDERSB.V.‑LOCATIEHELMOND*{color}* | | | |{color:#000001} Gerstdijk12 \\\\u200b5704RGHelmond{color} | | |{color:#000001} M:{color}{color:#000001}{color}{color:#000001}+32-11-546672{color}{color:#000001} <tel:+32%20-%2011%20-%2054%2066%2072>{color} |  {color:#000001}KvK14626985{color}   _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | | !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | | !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} | | !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} |        *Van:* Damian Świstek (Jira) <jira@kotrak.com>   *Verzonden:* dinsdag 21 februari 2023 15:32  *Aan:* Huibers\', \'Comment 7: Koen <khuibers@deheus.com>  *Onderwerp:* DGS-8517 Update indices prices method = \\\'week\\\' for Contract Farmer and Contract Slaughtery for many customers   ""]\']\nRelated Issues:\n[]\n\n### End'}"
516,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8516\n\n### Instruction:\nCześć,\r\n\r\nProszę o jak najszybsze zweryfikowanie problemu przeniesienia LP z Optimy do CDN-a; migracja pierwszy raz po zmianie struktury.\r\n\r\n \r\n\r\nProszę o przekierowanie  zadania do Pani Monik Biśty\r\n\n\n### Response:\n[""Comment 1: [\'!image![^Przechwytywanie komunikatów.log] _(603 kB)_\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'[^DGS-8516.docx]\'"", ""Comment 4: \'Odpowiedź w załączniku[^DGS-8516.docx]\'"", ""Comment 5: \'Została dodana na próbe lista E-UM3/2023/06/*/E Niestety Iwona Sadowska nie może jej pobrać z Optimy \'"", ""Comment 6: \'Lista główna za styczeń została przeniesiona.Ze względu na zmiany wydziałów z dniem 01.02.2023 system wymagał ustawienia daty importu na 31.01.2023"", \'Comment 7: dodatkowo prze-edytowano poprzednie wydziały pracowników (obowiązujące w ramach listy za styczeń) Na przyszłość proszę zwrócić uwagę na nazwy działów\', \'Comment 8: nie jestem w stanie sprawdzić jak to będzie wpływać na dalsze działanie systemu ale na zapisach historycznych osób dla których wydział był zmieniany brakuje informacji co zmieniano i wynika to właśnie z faktu iż nazwa wydziału jest taka sama ale w innej gałęzi. Może to powodować nieprawidłowości.Jeśli chodzi o testową listę płac na późniejszy okres proszę o weryfikację czy lista została zamknięta na czas przeniesienia\', \'Comment 9: ponieważ XL jej nie widzi (lista w buforze nie może być przeniesiona dl XL)\', ""Comment 10: po zamknięciu listy proszę o przekazanie informacji do księgowości w celu weryfikacji importu.\'"", ""Comment 11: \'Odp od Iwony Sadowskiej : Jeśli chodzi o listę testową za okres luty została poprawnie zaksięgowana.Problem jest tylko z listą styczniową – nie została zaksięgowana jak również wszystkie koszty weszły wg „starej” struktury"", ""Comment 12: przed zmianą.\'"", ""Comment 13: \'Proszę o wskazanie lokalizacji gdzie zapisywane są logi i errory z działania automatu do księgowania lub o ich przesłanie z piątku"", ""Comment 14: godziny wieczorne\'"", ""Comment 15: \'[^AutoAccounting v.2.0.7z] _(25 kB)_\'"", ""Comment 16: \'Będę wdzięczna za weryfikację czy w log i error z soboty i niedzieli jest jakiś zapis dot. listy płac:E-UM/2023/01/* GIDTyp => 2976 GIDFirma => 246785 GIDNumer =>3226lub o przesłanie tych log/error!image-2023-02-13-14-12-48-134.png!\'"", ""Comment 17: \'2023-02-12 00:34:21.9799|ERROR|AutoAccounting.Posting| [6536] Nie udało sie zaksięgować dokumentu E-UM/2023/01/* BŁAD XLKsiegujDokument() => 120 | Wystąpił wewnętrzny błąd modyfikacji danych.|Zaistniała sytuacja nieprzewidziana przez program.||Przyczyna:|Szczegóły operacji:Operacja zmiany obiektu o identyfikatorze .Identyfikator operacji: .Błąd: "", \'Comment 18: .||Remedium:|Spróbuj wykonać operację ponownie\', \'Comment 19: jeżeli problem nie będzie ustępował\', \'Comment 20: skontaktuj się z Administratorem systemu.2023-02-12 22:37:19.6975|TRACE|AutoAccounting.Posting| [4104] START AutoAcounting - Posting2023-02-12 22:37:19.6975|TRACE|AutoAccounting.Log| [4104] Pobieranie dodatkowych procedur do wykonania2023-02-12 22:37:19.7131|TRACE|AutoAccounting.Log| [4104] Ilość dodatkowych procedur do wykonania => 02023-02-12 22:37:19.7131|TRACE|AutoAccounting.Posting| [4104] Rozpoczęcie pobierania dokumentów do zaksięgowania2023-02-12 22:37:19.7131|TRACE|AutoAccounting.Posting| [4104] Pobrano dokumenty do zaksięgowania w ilości => 12023-02-12 22:37:19.7131|TRACE|AutoAccounting.Posting| [4104] Księgowanie dokumentu Identyfikator => E-UM/2023/01/* GIDTyp => 2976 GIDFirma => 246785 GIDNumer =>3226 GIDLp =>02023-02-12 22:37:19.7131|TRACE|AutoAccounting.Log| [4104] Pobieranie dodatkowych procedur do wykonania2023-02-12 22:37:19.7288|TRACE|AutoAccounting.Log| [4104] Ilość dodatkowych procedur do wykonania => 22023-02-12 22:37:19.7288|TRACE|AutoAccounting.Log| [4104] InputString przed zamianą => exec [CDN].[KR_PoprawOpisListyPlacKosztyNEW] ^DNGIDTyp^\', \'Comment 21: ^DNGIDNumer^2023-02-12 22:37:19.7288|TRACE|AutoAccounting.Log| [4104] InputString po zmianie => exec [CDN].[KR_PoprawOpisListyPlacKosztyNEW] 2976\', \'Comment 22: 32262023-02-12 22:37:19.7443|TRACE|AutoAccounting.Log| [4104] Pomyślnie wykonano procedurę SQL => exec [CDN].[KR_PoprawOpisListyPlacKosztyNEW] ^DNGIDTyp^\', \'Comment 23: ^DNGIDNumer^2023-02-12 22:37:19.7443|TRACE|AutoAccounting.Log| [4104] InputString przed zamianą => exec [CDN].[KR_PoprawOpisListyPlacNEW] ^DNGIDTyp^\', \'Comment 24: ^DNGIDNumer^2023-02-12 22:37:19.7443|TRACE|AutoAccounting.Log| [4104] InputString po zmianie => exec [CDN].[KR_PoprawOpisListyPlacNEW] 2976\', \'Comment 25: 32262023-02-12 22:37:19.7443|TRACE|AutoAccounting.Log| [4104] Pomyślnie wykonano procedurę SQL => exec [CDN].[KR_PoprawOpisListyPlacNEW] ^DNGIDTyp^\', ""Comment 26: ^DNGIDNumer^\'"", ""Comment 27: \'Lista została zaksięgowana"", ""Comment 28: proszę o weryfikację.\'"", \'Comment 29: ""It\\\'s Ok. Task to close""]\']\nRelated Issues:\n[]\n\n### End'}"
517,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8515\n\n### Instruction:\n I am trying to look for December 2022 closing balance for 2022, but I cant find the Balances in 2023 for January as a beginning, I should add those balances as a beginning in 2023 or the system should take it as a balance what is the option to do this? looking your responses. the year is not closed still some thing to correct and waiting until it will be Audited or any changes.\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Hi,To add opening balance in new period (2023)"", \'Comment 3: please open Accounting module\', \'Comment 4: then choose period:!image-2023-02-10-13-08-13-424.png!!image-2023-02-10-13-08-41-565.png!Then you need to go to Accounting >> Tools tab >> Transfer Opening Balance!image-2023-02-10-13-05-40-981.png!Then decide whether you want to transfer all accounts the All\', \'Comment 5: if Selected\', \'Comment 6: please choose Selected and then + button to select desired account!image-2023-02-10-13-07-27-235.png!Please\', ""Comment 7: let us know if this is fine for you.Regards\'"", ""Comment 8: \'Hi,Is there anything else we can do for you?Regards\'"", ""Comment 9: \'Hello,We are closing this task as we haven’treceivedany replyfromyouforalong time. If the issueappearsagain"", ""Comment 10: please raise another task.Regards\'"", ""Comment 11: \'I tried to Move for 2022 Ending Balance for 2023 Beginning Balance but not working properly it will take 2022 Beginning Balance for 2023 Beginning Balance. can you help me on this\'"", ""Comment 12: \'Dear Sir"", \'Comment 13:  not yet resolved for this Issue\', \'Comment 14: I tried to Move opening Balance for 2023 from 2022 Ending and closing balance\', \'Comment 15: but not working properly it will take 2022 Opening Balance as 2023 Opening balance. Can you look it again for you assist. Thanks.   {color:#1F3864}With best Regards,{color} {color:#1F3864}{color} {color:#1F3864}Getish Lemma\', \'Comment 16: Finance Manager{color} {color:#1F3864}{color} {color:#1F3864}Alema Koudijs Feed PLC{color} {color:#1F3864}(+251) 912 144 728{color}{color:#2E74B5}{color} !image001!{color:#2E74B5}{color}        *From:* Aleksandra Przybyłek (Jira) <jira@kotrak.com>   *Sent:* Friday\', \'Comment 17: February 10\', ""Comment 18: 2023 3:11 PM  *To:* Getish Lemma <Getish@alemakoudijs.com>  *Subject:* DGS-8515 2022 closing balance   !image002!!image003!!image004!!image005!\'"", ""Comment 19: \'Hi,The issue is not resolved for you"", ""Comment 20: however you did not inform us since the 10th of February.Please raise a new task for this issue as this task has been already closed and settled.Best Regards\']""]\nRelated Issues:\n[]\n\n### End'}"
518,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8514\n\n### Instruction:\nHello,\r\n\r\nPlease assist cancel SORC-6/23/UMR.\r\n\r\nStock was collected from a customer and user had to credit them for it, user mistakenly included another product on the credit note, user created a new SORC-7/23/UMR (which is correct).\r\nStock from SORC-6/23/UMR was used.\r\n\r\nCan you please assist in cancelling SORC-6/23/UMR.\r\n\r\n\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'document 6 /sorcTrN_GIDTyp=2009 AND TrN_GIDFirma=556290 AND TrN_GIDNumer=40775877TrN_GIDNumer=4077709select * from cdn.traelem where tre_gidnumer in (4077587,4077709)\'"", ""Comment 3: \'!image-2023-02-10-15-34-25-678.png!\'"", ""Comment 4: \'!image-2023-02-10-15-35-28-389.png!\'"", ""Comment 5: \'zasobyselect * from cdn.dostawy where Dst_GIDTyp=160 AND Dst_GIDNumer=825391select * from cdn.twrzasoby where twz_twrnumer=13371 and twz_magnumer=4\'"", ""Comment 6: \'--select * from cdn.traselem where Trs_GIDNumer=4077709select * from cdn.traelem where Tre_GIDNumer=4077709select TrS_Ilosc,* from cdn.traselem where Trs_DstNumer=825391--select * from cdn.traselem where Trs_GIDNumer=4077587--select TrS_Ilosc,* from cdn.traselem where Trs_DstNumer=798475--select TrS_Ilosc,* from cdn.traselem where Trs_DstNumer=799863select TwZ_IlSpr,* from cdn.twrzasoby where twz_dstnumer in (825391)--),798475)--,799863)select * from cdn.twrzasoby where twz_twrnumer=13371 and TwZ_IlSpr >= 0.3750 and TwZ_MagNumer=4select Dst_KsiegowaNetto/Dst_Ilosc,* from cdn.dostawy where Dst_GIDNumer in (825391,835319,839194)select Trs_DstNumer,839194,* from cdn.traselem t where Trs_DstNumer=825391 and TrS_GIDNumer in (4077651,4091295)update t set Trs_DstNumer=839194 from cdn.traselem t where Trs_DstNumer=825391 and TrS_GIDNumer in (4077651,4091295)select * from cdn.traelem where Tre_GIDNumer=4077587select TrS_Ilosc,* from cdn.traselem where Trs_DstNumer=798475 and TrS_GIDNumer>= 4077587--select TrS_Ilosc,* from cdn.traselem where Trs_DstNumer=799863 and TrS_GIDNumer>= 4077587select Dst_KsiegowaNetto/Dst_Ilosc,* from cdn.dostawy where Dst_GIDNumer in (798475,834103)select * from cdn.twrzasoby where twz_twrnumer=13371 and TwZ_IlSpr >= 0.1500 and TwZ_MagNumer=4select Trs_DstNumer,834103,* from cdn.traselem t where Trs_DstNumer=798475 and TrS_GIDNumer in (4077651)--update t set Trs_DstNumer=834103 from cdn.traselem t where Trs_DstNumer=798475 and TrS_GIDNumer in (4077651)\'"", ""Comment 7: \'[^sorc6.docx]\'"", ""Comment 8: \'Heelo"", ""Comment 9: we made operations on db nightly please verify.Deatils in attachment.If what we did is ok please notce that realistion this on production db will be cost more then 3 man-hours.[^sorc6.docx]\'"", ""Comment 10: \'Hello,Purchasing Department Approved.Please make the same changes on LIVE.\'"", \'Comment 11: \\\'Good morning One of the supplies that was available for ""swap"" was consumed\', \'Comment 12: we need additional time for analysis - the main logic itself to cancel documents will not change.So the task may take more than 3 rbh\', ""Comment 13: = additional analysis and changes on the production environment is about 2 rbh.\'"", ""Comment 14: \'!hand.PNG|thumbnail! !period_prod.PNG|thumbnail!\'"", ""Comment 15: \'In the course of retesting on a nightly DB we encountered another problem"", \'Comment 16: a trading period has been closed and it is not possible to cancel documents.Is it possible to open this period\', \'Comment 17: the same situatuon would be on the prod version.Please also bear in mind that the later we have feedback\', \'Comment 18: the more analysis is necessary\', \'Comment 19: it may turn out that\', \'Comment 20: for example\', \'Comment 21: in a given warehouse completely run out of resources and in order to replace supplies and cancel SORc it will be necessary to generate transfers\', ""Comment 22: etc.!hand.PNG!!image-2023-02-21-14-24-14-331.png!\'"", ""Comment 23: \'Hello,Period is now open.\'"", ""Comment 24: \'Thank you so I testes it on nightly again and then did the same on productionall 3 documentssic 191sorc 7sorc 6are cancelled now operator can make new sorc for sor-105/23/umr and then create clip docuemnt,if there will be problem the number of new sic clipped invoice"", \'Comment 25: let us know\', ""Comment 26: before it will be confirmed.!image-2023-02-22-15-01-07-346.png!\'"", ""Comment 27: \'Thank you so much.You may close this ticket\']""]\nRelated Issues:\n[]\n\n### End'}"
519,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8513\n\n### Instruction:\nDear, \r\nI don´t see label in DHP for 5445. Recipe is okay.\r\npls check it,\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 2: ""brak labelek w dhc service!image-2023-02-09-10-01-26-375.png!select * from labels where DhhItemId=\\\'9608C72D-1656-4F66-A392-C39BE6558FC8\\\' and ProductionAreaId=\\\'53D059F7-7B99-4CEF-A24C-6706B2F6F6C7\\\'recipe jest""\', \'Comment 3: ""023-02-09 10:00:49,439 [70] ERROR Evolution.DHCountry.Infrastructure.Commands.CommandHandlerWithLog4Net`1 [(null)] - Exception occurred when handling command Evolution.DHCountry.Dictionaries.Labels.Commands.SendLabelChangedMessageCommand of ID=\\\'da3ca5c0-f7f0-4c1b-b7c8-04a3df270154\\\'. Command data: \\\'Evolution.DHCountry.Dictionaries.Labels.Commands.SendLabelChangedMessageCommand[CommandId=\\\'da3ca5c0-f7f0-4c1b-b7c8-04a3df270154\\\'\', ""Comment 4: LabelId=\'f10e986d-0394-4867-b87e-4c53ee769566\']\'.AutoMapper.AutoMapperMappingException:Mapping types:Label_58409578ECBEFFA14BC24C43BE145B28A08E64E550FF16DA798E9978C252CC51 -> List`1System.Data.Entity.DynamicProxies.Label_58409578ECBEFFA14BC24C43BE145B28A08E64E550FF16DA798E9978C252CC51 -> System.Collections.Generic.List`1[[Evolution.DHCountry.Interfaces.Labels.LabelElement"", \'Comment 5: Evolution.DHCountry.Interfaces\', \'Comment 6: Version=3.0.61.0\', \'Comment 7: Culture=neutral\', \'Comment 8: PublicKeyToken=null]]Destination path:LabelChangedMessage.Elements.ElementsSource value:System.Data.Entity.DynamicProxies.Label_58409578ECBEFFA14BC24C43BE145B28A08E64E550FF16DA798E9978C252CC51 ---> System.Data.Entity.Core.EntityCommandExecutionException: An error occurred while executing the command definition. See the inner exception for details. ---> System.Data.SqlClient.SqlException: Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding. ---> System.ComponentModel.Win32Exception: The wait operation timed out --- End of inner exception stack trace --- at System.Data.SqlClient.SqlConnection.OnError(SqlException exception\', \'Comment 9: Boolean breakConnection\', \'Comment 10: Action`1 wrapCloseInAction) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj\', \'Comment 11: Boolean callerHasConnectionLock\', \'Comment 12: Boolean asyncClose) at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior\', \'Comment 13: SqlCommand cmdHandler\', \'Comment 14: SqlDataReader dataStream\', \'Comment 15: BulkCopySimpleResultSet bulkCopyHandler\', \'Comment 16: TdsParserStateObject stateObj\', \'Comment 17: Boolean& dataReady) at System.Data.SqlClient.SqlDataReader.TryConsumeMetaData() at System.Data.SqlClient.SqlDataReader.get_MetaData()""\', \'Comment 18: ""nie wpada do tabeli export inforesselect top 10 * from LabelExportInfoes --order by senddate descwhere entityid in (\\\'F10E986D-0394-4867-B87E-4C53EE769566\\\',\\\'010A84D5-6B88-4CCE-8C78-2AB8B153D0FD\\\')""\', ""Comment 19: \'labelka nie wpada do labale export infoes"", \'Comment 20: nie ma erororw już recipe jest\', \'Comment 21: item jest w dhp\', ""Comment 22: elementy lableki są takie same w obu bazach - country service\'"", ""Comment 23: \'brakowało baseitemid w dhc service na dhh itemie\'"", ""Comment 24: \'teraz brak commitdatelogi z dhcint=egration2023-02-09 12:11:27 (/Plant.DHC.Integration/CZDHPIISBE01/9444/13) [Error] Plant.Integration.DhcService.Infrastructure.FetchDataFromDhcTask - LabelPipelineExecutor execution errorSystem.Exception: Cannot connect to server ---> System.ServiceModel.FaultException: Internal server error\'"", ""Comment 25: \'Please verify it shoul be ok now :!image-2023-02-09-12-24-17-903.png!\'"", ""Comment 26: \'It´s okay. thx\']""]\nRelated Issues:\n[]\n\n### End'}"
520,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8512\n\n### Instruction:\nPlease set round + feed sale B001070/0161/0001 active \n\n### Response:\n[""Comment 1: [\'Hello,\\\\r\\\\rRound and Feed sale are Active now.\\\\r\\\\rRegards\']""]\nRelated Issues:\n[]\n\n### End'}"
521,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8511\n\n### Instruction:\nProszę o pomoc przy zamknięciu vt\r\nWaga konicowa do vt 1909 -17,340\r\n\r\nKomunikat czynności sąwykonywane prawidłowo. \n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'The weight of unloading is 21,440 t now and there is no actual weight registered now. Please"", ""Comment 4: advise!image-2023-02-09-07-28-14-364.png|width=1469,height=286!\'"", ""Comment 5: \'plz close the task \'"", ""Comment 6: \'dla wyjaśnienia bo temat nie został rozwiązany: problemem nie jest brak wagi"", \'Comment 7: wagi nie ma bo nie mogli zważyć samochodu\', \'Comment 8: podczas zapisywania VT waga była\', ""Comment 9: widać to na screenie zgłoszeniowym. Problemem jest ilość zrealizowana na WMO i tu pytanie co system zrobił!image-2!!image-3!!image-4!!image-5!\'"", ""Comment 10: \'została kwestia anulowania ZPM !screenshot-1! \'"", ""Comment 11: \'Marcin Block wyjaśni na sesji z DH.\']""]\nRelated Issues:\n[]\n\n### End'}"
522,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8510\n\n### Instruction:\nProduction recipes are not appearing in DHP Helmond.\r\n\r\nEg. order SO000066143 item 303315.\r\n\r\nRecipes in DHC are created but don\'t appear in DHP.\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 2: ""Can you specify what is lacking. Both order SO000066143 and recipe for303315 are available in Helmond\\\'s DHP!image-2023-02-08-17-05-27-839.png!!image-2023-02-08-17-05-41-960.png!""\', ""Comment 3: \'In DHC subversions of the recipe are created (without checking 11 and 12).Those are not found in DHP.... so the plant is missing the added special or medicine.\'"", ""Comment 4: \'Any news?\'"", ""Comment 5: \'Should be fixed"", ""Comment 6: please check.\'"", ""Comment 7: \'Hi Gedeon,it seems to be working fine now. Thanks.What was the problem/solution?Regards,Rob.\'"", ""Comment 8: \'Hi Rob,Integration between DHC and DHP suspended. Can we close this task?Regards\'"", ""Comment 9: \'Hi Aleksandra,what caused this? Can this be avoided to happen? Can we fix it ourselves next time maybe?Regards\'"", ""Comment 10: \'I think we should treat it as incidental case. We will observe if the issue re-occurs.Regards\'"", ""Comment 11: \'This ticket can be closed.\']""]\nRelated Issues:\n[]\n\n### End'}"
523,"{'prompt': ""Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8509\n\n### Instruction:\nMove of DHP and DHC databases and applications to the prod server\n\n### Response:\n['Comment 1: []']\nRelated Issues:\n[]\n\n### End""}"
524,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8508\n\n### Instruction:\nHi,\r\nIn our plant in Andel, we have received 952 bags of product 087059 (bags a 25 kg), but we cannot finalize this intake due to a missing barcode prefix.\r\nCan you please check? \r\n\n\n### Response:\n[""Comment 1: [\'!20230208_145716.jpg|thumbnail!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'!image-2023-02-09-11-36-39-917.png!\'"", ""Comment 4: \'!image-2023-02-09-11-37-14-682.png!\'"", ""Comment 5: \'Hi,Configuration has been set up:!image-2023-02-09-11-44-08-098.png!Regards\'"", ""Comment 6: \'Na barcode prefix kliknąć edit i dodać prefix!image-2023-02-09-11-45-01-613.png!\'"", ""Comment 7: \'Hi Aleksandra,Dziekuje bardzo. A question? Does dit count for only this product? \'"", ""Comment 8: \'It works for all products of Andel Mest now :)\'"", ""Comment 9: \'Thanks Aleksandra! You can close the task\'"", ""Comment 10: \'Thank you :)\']""]\nRelated Issues:\n[]\n\n### End'}"
525,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8507\n\n### Instruction:\nWe need to have notification service configurated so that we will be able to use the email address feature in DHC\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Dzięki Przemku :)\'"", ""Comment 3: \'Dear [~SFeyi@koudijs.com.gh]"", \'Comment 4: to configure notification service we will need some email account to send notification\', \'Comment 5: please provide us information about email address that we can use\', \'Comment 6: password\', \'Comment 7: smtp server address\', ""Comment 8: port to communicate with smtp and other necessary information like type of security protocol.\'"", ""Comment 9: \'Okay I will get back to you with those details soon Kind regards  | !image001!!image004! |  *{color:#2E74B5} *Feyi Seyram Solomon*{color}*{color:#2E74B5} ServiceDesk Engineer{color}  *{color:#2E74B5} *Koudijs Ghana Limited*{color}*{color:#2E74B5} Phone: +233 30 7000 580 : Mobile: +233 59 6914 778{color}{color:#2E74B5}{color}  *{color:#2E74B5} *GK-0173-1282"", \'Comment 10: Tema Free Zone Enclave*{color}*  *{color:#2E74B5} *Tema\', \'Comment 11: Greater Accra\', \'Comment 12: COD TD 200 Ghana*{color}*  *{color:#2E74B5} **{color}*{color:#2E74B5} This e-mail message and its attachments are subject to the disclaimer published at the website of{color} [{color:#0563C1}Koudijs Animal Nutrition{color}|https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.koudijs.com%2Fdisclaimer&data=05%7C01%7CSFeyi%40koudijs.com.gh%7C1cdd4c26b4484d6270e708daf877ef8b%7C1004261bdfb74f37830f7438cb8a1b69%7C1%7C0%7C638095491246060747%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Sda%2Fs8RH6LVyAD6b9dCkcyZFILd6rVJqdsWh%2B65H9QE%3D&reserved=0]{color:#2E74B5}{color}  |        *From:* Przemysław Przybyszewski (Jira) <jira@kotrak.com>   *Sent:* Friday\', \'Comment 13: March 17\', \'Comment 14: 2023 10:35 AM  *To:* Feyi\', ""Comment 15: Solomon <SFeyi@koudijs.com.gh>  *Subject:* DGS-8507 notification service configuration   !image002!\'"", ""Comment 16: \'Email : [StarLims@deheus.com|mailto:StarLims@deheus.com] Password: St@RL1m5 Smtp : smtp.office365.com Port : 587 Security protocol : starts  Will this help?  | !image001!!image004! |  *{color:#2E74B5} *Feyi Seyram Solomon*{color}*{color:#2E74B5} ServiceDesk Engineer{color}  *{color:#2E74B5} *Koudijs Ghana Limited*{color}*{color:#2E74B5} Phone: +233 30 7000 580 : Mobile: +233 59 6914 778{color}{color:#2E74B5}{color}  *{color:#2E74B5} *GK-0173-1282"", \'Comment 17: Tema Free Zone Enclave*{color}*  *{color:#2E74B5} *Tema\', \'Comment 18: Greater Accra\', \'Comment 19: COD TD 200 Ghana*{color}*  *{color:#2E74B5} **{color}*{color:#2E74B5} This e-mail message and its attachments are subject to the disclaimer published at the website of{color} [{color:#0563C1}Koudijs Animal Nutrition{color}|https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.koudijs.com%2Fdisclaimer&data=05%7C01%7CSFeyi%40koudijs.com.gh%7C1cdd4c26b4484d6270e708daf877ef8b%7C1004261bdfb74f37830f7438cb8a1b69%7C1%7C0%7C638095491246060747%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Sda%2Fs8RH6LVyAD6b9dCkcyZFILd6rVJqdsWh%2B65H9QE%3D&reserved=0]{color:#2E74B5}{color}  |        *From:* Przemysław Przybyszewski (Jira) <jira@kotrak.com>   *Sent:* Friday\', \'Comment 20: March 17\', \'Comment 21: 2023 10:35 AM  *To:* Feyi\', ""Comment 22: Solomon <SFeyi@koudijs.com.gh>  *Subject:* DGS-8507 notification service configuration   !image002!\'"", ""Comment 23: \'Hi [~SFeyi@koudijs.com.gh]"", \'Comment 24: yes\', ""Comment 25: it should enough.\']""]\nRelated Issues:\n[\'DGS-8504\']\n\n### End'}"
526,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8506\n\n### Instruction:\nHello, \r\n\r\nVT-1188/1 is closed, but the stock unit status has status in progress. What is going on? please solve this and let us know the cause so we can prevent this from happening\n\n### Response:\n[""Comment 1: [\'!afbeelding-4!!afbeelding-6!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 3: "" !screenshot-1! {code:java}SELECT *  FROM [DHPlantStockBusinessLogicEvents].[dbo].[StockUnits]  where AggregateId=\\\'FA380786-43F2-4804-91A1-322DB3E12B0E\\\' and EventType like \\\'%status%\\\'  order by Created  SELECT *  FROM [DHPlantStockBusinessLogicEvents].[dbo].[StockUnits]  where AggregateId=\\\'78387d81-af37-4c6f-8329-b73c1b23e557\\\' and EventType like \\\'%status%\\\'  order by Created{code} !screenshot-2! {code:java}SELECT *  FROM [DHPlantVCBusinessLogicEvents].[dbo].[VehicleTickets]  where AggregateId=\\\'28C232A5-FD90-4D8A-87ED-E7008D8B6B20\\\'   order by Created  SELECT *  FROM [DHPlantVCBusinessLogicEvents].[dbo].[VehicleTickets]  where AggregateId=\\\'c3fb8632-3d2a-4ad1-b699-2f3b90e8fcfb\\\'    order by Created{code} !screenshot-3! {code:java}SELECT status,*  FROM [DHPlantStockBusinessLogicMain].[dbo].[VehicleTickets]  where id=\\\'28c232a5-fd90-4d8a-87ed-e7008d8b6b20\\\'--or id=\\\'c3fb8632-3d2a-4ad1-b699-2f3b90e8fcfb\\\'   SELECT status,*from DHPlantVCBusinessLogicMain.[dbo].[VehicleTickets]  where id=\\\'28c232a5-fd90-4d8a-87ed-e7008d8b6b20\\\'--or id=\\\'c3fb8632-3d2a-4ad1-b699-2f3b90e8fcfb\\\' select top 10 * from DHPlantStockBusinessLogicMain.[dbo].[Deliveries]where [SourceDocumentId] in(\\\'28c232a5-fd90-4d8a-87ed-e7008d8b6b20\\\')--,\\\'c3fb8632-3d2a-4ad1-b699-2f3b90e8fcfb\\\') select top 10 * from DHPlantStockBusinessLogicMain.[dbo].[StockUnits]where DeliveryId in(--\\\'DF8495E1-F842-42A3-B343-4684B99CAC4C\\\',\\\'D68C07B7-029C-45B6-8F7E-F69EA6A477C7\\\'){code} !screenshot-4! ""\', \'Comment 4: ""{code:java}SELECT v.status,s.LogisticStatus,d.Status,v.Document,s.ItemId,i.Code,s.Id,s.QuantityOnHand,s.InitialQuantity  FROM [DHPlantStockBusinessLogicMain].[dbo].[VehicleTickets] v   inner join DHPlantStockBusinessLogicMain.[dbo].[Deliveries] d on v.id=d.SourceDocumentId  inner join DHPlantStockBusinessLogicMain.[dbo].[StockUnits] s on s.DeliveryId=d.Id  inner join DHPlantStockBusinessLogicMain.[dbo].Items i on i.id=s.ItemId  --where v.Id=\\\'28c232a5-fd90-4d8a-87ed-e7008d8b6b20\\\' where v.Status=120 and LogisticStatus=2{code} !screenshot-5! ""\', ""Comment 5: \'Attempted to divide by zero.{code:java}   at System.Decimal.DecCalc.VarDecDiv(DecCalc& d1"", \'Comment 6: DecCalc& d2)   at Plant.Stock.BusinessLogic.Domain.Services.CloseStockUnitsIntakeDomainService.<>c__DisplayClass3_0.<CalculateStockUnitsQuantityDifference>b__2(StockUnitQuantityDifferenceCalculationData stockUnit) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Domain\\\\\\\\Services\\\\\\\\CloseStockUnitsIntakeDomainService.cs:line 103   at System.Linq.Enumerable.ToDictionary[TSource,TKey,TElement](IEnumerable`1 source\', \'Comment 7: Func`2 keySelector\', \'Comment 8: Func`2 elementSelector\', \'Comment 9: IEqualityComparer`1 comparer)   at System.Linq.Enumerable.ToDictionary[TSource,TKey,TElement](IEnumerable`1 source\', \'Comment 10: Func`2 keySelector\', \'Comment 11: Func`2 elementSelector)   at Plant.Stock.BusinessLogic.Domain.Services.CloseStockUnitsIntakeDomainService.CalculateStockUnitsQuantityDifference(IEnumerable`1 stockUnitsData\', \'Comment 12: Quantity absoluteDifference) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Domain\\\\\\\\Services\\\\\\\\CloseStockUnitsIntakeDomainService.cs:line 99   at Plant.Stock.BusinessLogic.Domain.Services.CloseStockUnitsIntakeDomainService.CalculateQuantityDifference(IEnumerable`1 stockUnitsData\', \'Comment 13: Quantity finalQuantity) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Domain\\\\\\\\Services\\\\\\\\CloseStockUnitsIntakeDomainService.cs:line 0   at Plant.Stock.BusinessLogic.Domain.Services.CloseStockUnitsIntakeDomainService.CalculateQuantityDifference(IEnumerable`1 stockUnits\', \'Comment 14: Quantity finalQuantity\', \'Comment 15: SourceDocument intakeSourceDocument) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Domain\\\\\\\\Services\\\\\\\\CloseStockUnitsIntakeDomainService.cs:line 37   at Plant.Stock.BusinessLogic.Domain.Services.RegisterIntakeDomainService.CloseBulkIntake(Delivery delivery\', \'Comment 16: IEnumerable`1 stockUnits\', ""Comment 17: Quantity finalQuantity) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Domain\\\\\\\\Services\\\\\\\\RegisterIntakeDomainService.cs:line 235   at Plant.Stock.BusinessLogic.Application.Services.RegisterIntakeService.CloseBulkIntake(CloseBulkIntakeElementData data) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Application\\\\\\\\Services\\\\\\\\RegisterIntakeService.cs:line 277   at Plant.Stock.BusinessLogic.Application.CommandHandlers.BulkIntake.CloseBulkIntakeCommandHandler.Handle(CloseBulkIntakeCommand command) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Application\\\\\\\\CommandHandlers\\\\\\\\BulkIntake\\\\\\\\CloseBulkIntakeCommandHandler.cs:line 30   at Kotrak.Common.Infrastructure.Commands.CommandEnvironment.Run[TCommand](TCommand command)   at Kotrak.Common.Infrastructure.Commands.Decorators.IntercontextEventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command)   at Kotrak.Common.Infrastructure.Commands.Decorators.EventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command)   at Kotrak.Common.Infrastructure.Commands.Decorators.ValidationCommandEnvironmentDecorator.Run[TCommand](TCommand command)   at Castle.DynamicProxy.AbstractInvocation.Proceed()   at Kotrak.Common.Infrastructure.Interceptors.LoggingInterceptor`1.Intercept(IInvocation invocation)   at Castle.DynamicProxy.AbstractInvocation.Proceed()   at Kotrak.Common.Infrastructure.Commands.Decorators.HistoryGateDecorator.Dispatch[TCommand](TCommand command)   at Plant.Stock.BusinessLogic.Infrastructure.ContextIntegration.IntercontextCommunication.VC.VehicleTicketIntakeClosedEventHandler.Handle(VehicleTicketIntakeClosedEvent message) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Infrastructure.ContextIntegration\\\\\\\\IntercontextCommunication\\\\\\\\VC\\\\\\\\VehicleTicketIntakeClosedEventHandler.cs:line 34   at Kotrak.Integration.IntegrationPluginCommon.IntercontextCommunication.Inbound.IntercontextInboundHandler`2.Handle(InternalStorageDto message){code}\'"", \'Comment 18: ""Hello\', \'Comment 19: statuses were updated by checking error messages in the stock module for VT\\\'s.And resent for events  VehicleTicketIntakeClosed. !screenshot-7! ""\', \'Comment 20: ""Oke\', \'Comment 21: and this should\\\'t occur anymore?""\', ""Comment 22: \'Hello Thomas,as for recurrence there were no new cases.\'"", ""Comment 23: \'Ticket can be closed\']""]\nRelated Issues:\n[]\n\n### End'}"
527,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8505\n\n### Instruction:\nVT-1627/2/2023/P nie przechodzi do CDNa\r\n\r\nByła zmiana na ZS-32/02/23/P  kod GT267X00X-W00 na ZS-332/02/23/P \r\nPozostałe elementy przeszły jeden został z błędem \r\n\n\n### Response:\n[""Comment 1: [\'!image!!image-1!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'!image-2023-02-08-14-23-26-693.png!!image-2023-02-08-14-25-13-074.png!\'"", ""Comment 4: \'!image-2023-02-08-14-37-19-632.png!!image-2023-02-08-14-40-13-638.png!\'"", ""Comment 5: \'Czy jest możliwość usunięcia elementu z VT i dodania go ponownie w plancie?\'"", ""Comment 6: \'Niestety nie bo pozostale elementy z tego vt przeszly z dhc \'"", ""Comment 7: \'I have verified this issue. When you modified order element released on VT you should delete this element from VT and add new one from correct order. Right now we sugest to add this element manualy to WZ document and correct quantity in DHP through stocktaking.Please"", \'Comment 8: let me know if the answer is sufficient for you. Do you expect any additional actions from us regarding this issue? Can we close this ticket?Zweryfikowałem ten problem. Kiedy zmodyfikowałeś element zamówienia wydany na VT\', ""Comment 9: powinieneś usunąć ten element z VT i dodać nowy z właściwego zamówienia. W tej chwili sugerujemy ręcznie dodać brakujący element do dokumentu WZ i skorygować ilość w DHP poprzez inwentaryzację.Proszę o informację czy przekazana odpowiedź jest dla Państwa wystarczająca? Czy oczekują Państwo od nas jakiś dodatkowych działań w zakresie tego zgłoszenia? Czy możemy zamknąć zgłoszenie?\'"", ""Comment 10: \'Na VT był usunięty ZS-32/02/23/P kod GT267X00X-W00 i dodany za niego ZS-332/02/23/.Na pierwszym screenie widać błąd przed zmianą na drugim jest juz po tej zmianie. Elementy przeszły"", ""Comment 11: była całą lista jak widać. ale jeden pozostał. \'"", ""Comment 12: \'According to previous sugestion please add this element manualy to WZ document and correct quantity in DHP through stocktaking.Zgodnie z wcześniejszą sugestią zalecamyręcznie dodać brakujący element do dokumentu WZ i skorygować ilość w DHP poprzez inwentaryzację.\'"", ""Comment 13: \'Close\'"", ""Comment 14: \'przy ponownym tego typu błędzie  - poprawiamy od bazy - prośba klienta po retro. \']""]\nRelated Issues:\n[]\n\n### End'}"
528,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8504\n\n### Instruction:\nThe email address function in DHC is not working, kindly help solve.\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'I think it has never worked for you as you do not have notification service configured. If there is a need"", ""Comment 4: please raise a GDC task.Regards\'"", ""Comment 5: \'!image-2023-02-08-14-09-17-901.png!\'"", ""Comment 6: \'please close\'"", ""Comment 7: \'Thank you\']""]\nRelated Issues:\n[\'DGS-8507\']\n\n### End'}"
529,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8503\n\n### Instruction:\nShipping Notice L000126539 is in DHC but is not arriving in DHP Andel (factory 98). Can you please check, we have to load this truck.  \r\n\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'I see it is in DHP now. Mihgt have been some delay \'"", ""Comment 3: \'!image-2023-02-08-11-51-57-742.png!\'"", ""Comment 4: \'Dear Theo,It is in plant now.Regards!image-2023-02-08-12-04-49-977.png!\'"", ""Comment 5: \'Sorry"", \'Comment 6: I missed your previous comment. Yes\', \'Comment 7: possible there was a delay\', \'Comment 8: I have restarted application pools. Please\', ""Comment 9: confirm if we can close this task.Regards\'"", ""Comment 10: \'Yes"", ""Comment 11: please close the task. \']""]\nRelated Issues:\n[]\n\n### End'}"
530,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8502\n\n### Instruction:\nVT 2666/2/2023/G nie chce wygenerować się z DHC do CDN.\r\nBrak komunikatu błędu, prośba o rozwiązanie problemu.\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Ale ten VT ma już wygenerowane dokumenty!image-2023-02-08-13-48-13-669.png!!image-2023-02-08-13-48-13-669!\'"", ""Comment 3: \'Ok"", \'Comment 4: dzięki do zamknięcia\', ""Comment 5: wyjątkowo długo się generowały.\'"", ""Comment 6: \'luzik :)\']""]\nRelated Issues:\n[]\n\n### End'}"
531,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8501\n\n### Instruction:\nI would like to schedule a meeting with you to help me with an issue on NAV reporting.\r\nWhat I would like is to be able to relate a Job Order to sales made per product,\r\nCan you help with this?\r\n\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Would you mind sending us more details? It would be very helpful to receive some examples of documents and information which exactly data are important for reporting (with screenshots).How do you calculate NAV? Do you have any formula or example of a report?\'"", ""Comment 3: \'please close\']""]\nRelated Issues:\n[]\n\n### End'}"
532,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8500\n\n### Instruction:\nSee below, VT-465 is multiplied multiple times in WO module, these elements contain no data: Please check, and fix this \n\n### Response:\n[""Comment 1: [\'!afbeelding-4!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'id=91710f26-6c92-4dbc-8f4e-26ac842c39b0\'"", \'Comment 4: \\\'{code:java}2023-02-08 10:01:41 (c3d5f865-3134-4017-b09b-8648dce97529/Plant.VC.BusinessLogic/DHVD01AP183/11148/237) [Error] Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware - Error during request{  ""scheme"": ""http""\', \'Comment 5:  ""host"": {    ""Value"": ""dhvd01ap183:82""\', \'Comment 6:    ""HasValue"": true\', \'Comment 7:    ""Host"": ""dhvd01ap183""\', \'Comment 8:    ""Port"": 82  }\', \'Comment 9:  ""path"": ""/api/VehicleTicket/completeDispatch""\', \'Comment 10:  ""queryString"": []\', \'Comment 11:  ""requestBody"": ""{\\\\\\\\""id\\\\\\\\"":\\\\\\\\""ae59ae71-510c-4f57-952e-3d33ef5b2d83\\\\\\\\"",\\\\\\\\""date\\\\\\\\"":\\\\\\\\""2023-02-08T09:01:43.915Z\\\\\\\\""}""}.Kotrak.Extensions.Validation.Abstractions.ValidationException: Validation failed: -- Missing weight on packed elements. Warehouse order has to be finished ---> Plant.VC.BusinessLogic.DomainAbstractions.VehicleTickets.VehicleTicketInvalidDispatchOperationException: Validation failed: -- MissingWeightOnPackedElementsMessage   at Plant.VC.BusinessLogic.Domain.VehicleTickets.VehicleTicket.SetDispatchCompleted() in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\67ba263564c33499\\\\\\\\Plant.VC.BusinessLogic\\\\\\\\Plant.VC.BusinessLogic.Domain\\\\\\\\VehicleTickets\\\\\\\\VehicleTicket.cs:line 744   at Plant.VC.BusinessLogic.Application.VehicleTickets.Services.VehicleTicketService.CompleteVehicleTicketDispatch(AggregateId vehicleTicketId\', \'Comment 12: DateTime date) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\67ba263564c33499\\\\\\\\Plant.VC.BusinessLogic\\\\\\\\Plant.VC.BusinessLogic.Application\\\\\\\\VehicleTickets\\\\\\\\Services\\\\\\\\VehicleTicketService.cs:line 418   at Kotrak.Common.Infrastructure.Commands.CommandEnvironment.Run[TCommand](TCommand command)   at Kotrak.Common.Infrastructure.Commands.Decorators.IntercontextEventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command)   at Kotrak.Common.Infrastructure.Commands.Decorators.EventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command)   at Kotrak.Common.Infrastructure.Commands.Decorators.ValidationCommandEnvironmentDecorator.Run[TCommand](TCommand command)   at Castle.DynamicProxy.AbstractInvocation.Proceed()   at Kotrak.Common.Infrastructure.Interceptors.LoggingInterceptor`1.Intercept(IInvocation invocation)   at Castle.DynamicProxy.AbstractInvocation.Proceed()   at Kotrak.Common.Infrastructure.Commands.Decorators.HistoryGateDecorator.Dispatch[TCommand](TCommand command)   at Plant.VC.BusinessLogic.Infrastructure.Api.Controllers.VehicleTicketController.CompleteDispatch(CompleteVehicleTicketDispatchViewModel viewModel) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\67ba263564c33499\\\\\\\\Plant.VC.BusinessLogic\\\\\\\\Plant.VC.BusinessLogic.Infrastructure.Api\\\\\\\\Controllers\\\\\\\\VehicleTicketController.cs:line 618   at lambda_method240975(Closure \', \'Comment 13: Object \', \'Comment 14: Object[] )   at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor.SyncActionResultExecutor.Execute(IActionResultTypeMapper mapper\', \'Comment 15: ObjectMethodExecutor executor\', \'Comment 16: Object controller\', \'Comment 17: Object[] arguments)   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeActionMethodAsync()   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next\', \'Comment 18: Scope& scope\', \'Comment 19: Object& state\', \'Comment 20: Boolean& isCompleted)   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeNextActionFilterAsync()--- End of stack trace from previous location ---   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Rethrow(ActionExecutedContextSealed context)   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next\', \'Comment 21: Scope& scope\', \'Comment 22: Object& state\', \'Comment 23: Boolean& isCompleted)   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeInnerFilterAsync()--- End of stack trace from previous location ---   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeFilterPipelineAsync>g__Awaited|20_0(ResourceInvoker invoker\', \'Comment 24: Task lastTask\', \'Comment 25: State next\', \'Comment 26: Scope scope\', \'Comment 27: Object state\', \'Comment 28: Boolean isCompleted)   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker\', \'Comment 29: Task task\', \'Comment 30: IDisposable scope)   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker\', \'Comment 31: Task task\', \'Comment 32: IDisposable scope)   at Microsoft.AspNetCore.Routing.EndpointMiddleware.<Invoke>g__AwaitRequestTask|6_0(Endpoint endpoint\', \'Comment 33: Task requestTask\', \'Comment 34: ILogger logger)   at Swashbuckle.AspNetCore.SwaggerUI.SwaggerUIMiddleware.Invoke(HttpContext httpContext)   at Swashbuckle.AspNetCore.Swagger.SwaggerMiddleware.Invoke(HttpContext httpContext\', ""Comment 35: ISwaggerProvider swaggerProvider)   at Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware.Invoke(HttpContext httpContext)   --- End of inner exception stack trace ---{code}\'"", ""Comment 36: \'!image-2023-02-08-10-57-52-799.png!\'"", ""Comment 37: \'!image-2023-02-08-11-13-20-751.png!\'"", ""Comment 38: \'!image-2023-02-08-11-14-37-091.png!\'"", ""Comment 39: \'!image-2023-02-08-11-31-59-758.png!\'"", ""Comment 40: \'What order number should be linked to this VT?\'"", ""Comment 41: \'here you see all order number that should be related to the VT. But somehow system only generates a few"", ""Comment 42: when one is fullfilled others are created with empty data!afbeelding-6!\'"", ""Comment 43: \'Dear Thomas,We have resend missing order that caused the issue and closed all empty WO (PD)Please"", ""Comment 44: let us know if this is fine for you.Regards\'"", ""Comment 45: \'Thanks! ticket can be closed\'"", ""Comment 46: \'Thank you\'"", ""Comment 47: \'[[DHP] VT is duplicated multiple time after fulfilling first order|onenote:https://kotrak.sharepoint.com/sites/erpasysta/Shared%20Documents/Baza%20wiedzy/Baza%20Wiedzy%20-%20ERPSD/Klienci/DEHEUS/DEHEUS%20APPLICATIONS/Holandia%20Premix%20i%20AS400/Baz%20wiedzy%20z%20AS400.one#%5bDHP%5d%20VT%20is%20duplicated%20multiple%20time%20after%20fulfilling%20first&section-id=\\\\\\\\{9BB564BA-0B58-4580-B9E0-F3CF9D6D80A7}&page-id=\\\\\\\\{42941D5F-5106-42D9-A367-A9B57DA0EFB6}&end] ([Widok sieci Web|https://kotrak.sharepoint.com/sites/erpasysta/_layouts/OneNote.aspx?id=%2Fsites%2Ferpasysta%2FShared%20Documents%2FBaza%20wiedzy%2FBaza%20Wiedzy%20-%20ERPSD&wd=target%28Klienci%2FDEHEUS%2FDEHEUS%20APPLICATIONS%2FHolandia%20Premix%20i%20AS400%2FBaz%20wiedzy%20z%20AS400.one%7C9BB564BA-0B58-4580-B9E0-F3CF9D6D80A7%2F%5BDHP%5D%20VT%20is%20duplicated%20multiple%20time%20after%20fulfilling%20first%7C42941D5F-5106-42D9-A367-A9B57DA0EFB6%2F%29])\']""]\nRelated Issues:\n[]\n\n### End'}"
533,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8499\n\n### Instruction:\nWhen there is a SILO SHOT on a round, this is under expenses and you can see it on the feed sale (this is good). However, when you generate the FS printout, for this line (SILO SHOT, under \'diverse kosten\') the document nr. is empty, and the real document nr. (SIB...) is shown under description. We would like to see \'DE HEUS VOEDERS B.V\' as \'referentie\' (= reference) just like the feed lines, the invoice nr. under \'document nr.\', and the description \'SILO SHOT\' under \'omschrijving\' (description) if possible (it\'s in line with the rest then). This example is on FS-B/0486 (ID 95412).\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Hello [~SDriesen@deheus.com]"", ""Comment 4: we changed the data shown on the printout at MasBE now everything should match the information you provided.!image-2023-02-08-13-08-06-104.png!\'"", \'Comment 5: ""Hello Tomasz,Everything seems fine now\', \'Comment 6: just that the customer\\\'s name is shown under reference. Can that be DE HEUS VOEDERS B.V just as on the feed segment?""\', \'Comment 7: ""My apologies\', ""Comment 8: I misread. It\'s fine now"", \'Comment 9: thank you!""]\']\nRelated Issues:\n[]\n\n### End'}"
534,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8498\n\n### Instruction:\nHi, \r\n\r\nEven in same customer some of Sale Invoice able to post. Some are not. And we didn\'t get any error message for unposted Sale Invoice. Kindly reference attached for more details.\n\n### Response:\n[""Comment 1: [\'!image!!image-1!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 3: \\\'You can not post this becouse there is no ""Fixed delivery value"" parameter set on document that create delivery/resource used on that SI dokument.!image-2023-02-07-18-05-11-375.png!If this not set then delivery do not have set ""Cost has been fixed"" parameter.!image-2023-02-07-18-06-11-343.png!And accounting tab is disable on WZ / (C)FS document\', \'Comment 4: as well as ""Cost of goods sold has been fixed"" parameter is turned off.!image-2023-02-07-18-08-57-958.png!!image-2023-02-07-18-09-13-145.png!To turn this parameter On on all documents You will have to finddocument that create this delivery and check ""Fixed delivery value"" parameter!image-2023-02-07-18-11-44-591.png!!image-2023-02-07-18-11-56-821.png!That will check this parameter on all documents that use this delivery/resource unless there will be other deliveries that do not have this parameter checked.Please\', ""Comment 5: let me know if the answer is sufficient for you. Do you expect any additional actions from us regarding this issue? Can we close this ticket?\'"", ""Comment 6: \'Please"", ""Comment 7: let me know if the answer is sufficient for you. Do you expect any additional actions from us regarding this issue? Can we close this ticket?\'"", ""Comment 8: \'Hi"", ""Comment 9: we are clear. Thank you. You can proceed to close ticket. Sorry for late response.\']""]\nRelated Issues:\n[]\n\n### End'}"
535,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8497\n\n### Instruction:\nVT-402/1/2023/vp with error message (SDNL-38749)\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'!image-2023-02-08-09-11-54-654.png!\'"", ""Comment 4: \'!image-2023-02-08-09-25-57-896.png!!image-2023-02-08-09-24-51-092.png!A w bazie:!image-2023-02-08-09-27-37-641.png!\'"", ""Comment 5: \'Itemy w DHC"", ""Comment 6: żaden z nich nie jest archive!image-2023-02-08-09-38-41-888.png!\'"", ""Comment 7: \'Hi,Indeed"", \'Comment 8: under the database I can see on order element item with code 00921 and name that is now assigned to code 00922. Probably the code was mistakenly assigned in ERP\', \'Comment 9: SO has been made and sent do DHC\', \'Comment 10: and then Item was corrected in ERP. But it does not correct in DHC. To sollve this issue\', ""Comment 11: you should create new Sales Order and clip it with VT.Regards!image-2023-02-08-10-11-00-145.png!\'"", \'Comment 12: ""{code:java}SELECT *  FROM [Evolution_DHCountry].[dbo].[Orders] where DocumentNumber = \\\'SO-188/01/2023/V\\\'  SELECT *  FROM [Evolution_DHCountry].[dbo].[OrderElements] where orderid = \\\'7B1AB58E-A2AC-4114-ABED-BAB516D175C9\\\'  --SELECT *  --FROM [Evolution_DHCountry].[dbo].[VehicleTickets] where DocumentNumber = \\\'402/1/2023/VP\\\'  -- SELECT ItemId\', ""Comment 13: *  --FROM [Evolution_DHCountry].[dbo].[VehicleTicketElements] where VehicleTicketId = \'67233B7F-975A-4C15-9D8F-42E6FD6C1C33\'   SELECT *  FROM [Evolution_DHCountry].[dbo].[Items] where id in ( \'0986B80F-9F36-4ACD-ADA9-4745BC717D18\',\'0986B80F-9F36-4ACD-ADA9-4745BC717D18\') or code in (\'00921\'"", \'Comment 14: \\\'00922\\\'){code}""\', ""Comment 15: \'Hello,Is there anything else we can do for you due to requested VT?Regards\'"", ""Comment 16: \'Hello,Is there anything else we can do for you due to requested VT?Regards\'"", ""Comment 17: \'Hi,It has been resolved under*DGS-8645.*Please"", ""Comment 18: let us know if we can close both tasks.Regards\'"", ""Comment 19: \'Ticket can be closed.!image-1!\'"", ""Comment 20: \'Thank you\']""]\nRelated Issues:\n[]\n\n### End'}"
536,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8496\n\n### Instruction:\nHello,\r\n\r\nA scanner incident is reported by the premix factory, I attached a video of the incident. \r\n\r\nWhen a warehouse employee scans a pallet\r\nlabel, for which no WMO is available, it can happen the employee scans the\r\nlabel a second time because he gets no response. When doing so, the DHP mobile application runs in an error and only solution is to restart. \r\n\r\nCan you please try to reproduce this and supply a fix?\r\n\r\n\r\n\n\n### Response:\n[""Comment 1: [\'[^ED81CB6B.mp4] _(28,05 MB)_\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Hi,I need few more inforamtion. Does the inciden occur only for one device or multiple devices. Are the scanners restarted often? Did user / users tried to logout and login? Clear cache?Regards\'"", ""Comment 4: \'[~marcin.block@kotrak.com]prośba o przygotowanie środowiska do testów dla Oli Masternak"", \'Comment 5: Maciej na Stand Up powiedział\', ""Comment 6: żeby tak zrobić :)\'"", ""Comment 7: \'Please be informed that we have forwarded the issue to the development team in order to internal analysis.We are waiting for more details and will be back with further information as soon as possible.\'"", ""Comment 8: \'Thanks"", ""Comment 9: incident occurs for all devices. \'"", ""Comment 10: \'any update?\'"", ""Comment 11: \'Dear Thomas,The issue has been still investigated by dev team. We are working on it.Regards\'"", ""Comment 12: \'Mobilny: ^2.7.1911.16.mp4Baza: DHP_NL_PROD1. Otwieram task listę2. Skanuję kod niepowiązany z WMO(/) Pojawia się komunikat o braku WMO"", \'Comment 13: który jest powiązany z tym barcodem3. Skanuję kod jeszcze raz (nie zamykam poprzedniego komunikatu)(x) Pojawia się błąd [^2.7.1911.16.mp4] {code:java}DHPlantMobile.exe ArgumentException Value does not fall within the expected range. at Microsoft.AGL.Common.MISC.HandleAr(PAL_ERROR ar) at System.Windows.Forms.Form.ShowDialog() at BeeMobile.MessageBox.MessageBoxModal.ShowDialog() at BeeMobile.MessageBox.MessageBoxModal.#=qeLqESOQJcNxgfwzrjtbA8Q==(Control #=qrm2DquzWZy2V02erddaodw==\', \'Comment 14: String #=q4ortAnrWpqoWcdr829dRTQ==\', \'Comment 15: String #=q5RS4Y1QmV1KgTSpv6$W9RQ==\', \'Comment 16: String[] #=qwa7E2DVbQ5LCzB$bnML2cQ==) at BeeMobile.MessageBox.MessageBox.ShowDialog(Control Parent) at DHPlantMobile.Controls.KotrakMessageBox.ShowDialog(String title\', \'Comment 17: String message\', \'Comment 18: KotrakMessageBoxButtons buttonsType) at DHPlantMobile.Controls.KotrakMessageBox.ShowDialog(String message\', \'Comment 19: KotrakMessageBoxButtons buttonsType\', \'Comment 20: KotrakMessageBoxType type) at DHPlantMobile.Task.TaskListForm.backgroundWorkerSelectTask_RunWorkerCompleted(Object sender\', \'Comment 21: RunWorkerCompletedEventArgs e) at System.ComponentModel.BackgroundWorker.TellThemOnGuiCompleted(Object sender\', \'Comment 22: EventArgs e) at System.Windows.Forms.Control.TASK.Invoke() at System.Windows.Forms.Control._InvokeAll() at System.Windows.Forms.Control.WnProc(WM wm\', \'Comment 23: Int32 wParam\', \'Comment 24: Int32 lParam) at System.Windows.Forms.Control._InternalWnProc(WM wm\', \'Comment 25: Int32 wParam\', \'Comment 26: Int32 lParam) at Microsoft.AGL.Forms.EVL.EnterModalDialog(IntPtr hwnModal) at System.Windows.Forms.Form.ShowDialog() at BeeMobile.MessageBox.MessageBoxModal.ShowDialog() at BeeMobile.MessageBox.MessageBoxModal.#=qeLqESOQJcNxgfwzrjtbA8Q==(Control #=qrm2DquzWZy2V02erddaodw==\', \'Comment 27: String #=q4ortAnrWpqoWcdr829dRTQ==\', \'Comment 28: String #=q5RS4Y1QmV1KgTSpv6$W9RQ==\', \'Comment 29: String[] #=qwa7E2DVbQ5LCzB$bnML2cQ==) at BeeMobile.MessageBox.MessageBox.ShowDialog(Control Parent) at DHPlantMobile.Controls.KotrakMessageBox.ShowDialog(String title\', \'Comment 30: String message\', \'Comment 31: KotrakMessageBoxButtons buttonsType) at DHPlantMobile.Controls.KotrakMessageBox.ShowDialog(String message\', \'Comment 32: KotrakMessageBoxButtons buttonsType\', \'Comment 33: KotrakMessageBoxType type) at DHPlantMobile.Task.TaskListForm.backgroundWorkerSelectTask_RunWorkerCompleted(Object sender\', \'Comment 34: RunWorkerCompletedEventArgs e) at System.ComponentModel.BackgroundWorker.TellThemOnGuiCompleted(Object sender\', \'Comment 35: EventArgs e) at System.Windows.Forms.Control.TASK.Invoke() at System.Windows.Forms.Control._InvokeAll() at System.Windows.Forms.Control.WnProc(WM wm\', \'Comment 36: Int32 wParam\', \'Comment 37: Int32 lParam) at System.Windows.Forms.Control._InternalWnProc(WM wm\', \'Comment 38: Int32 wParam\', \'Comment 39: Int32 lParam) at Microsoft.AGL.Forms.EVL.EnterModalDialog(IntPtr hwnModal) at System.Windows.Forms.Form.ShowDialog() at DHPlantMobile.Main.MenuForm.InvokeTaskList() at DHPlantMobile.Main.MenuForm.myButtonTaskList_Click(Object sender\', \'Comment 40: EventArgs e) at System.Windows.Forms.Control.TASK.Invoke() at System.Windows.Forms.Control._InvokeAll() at System.Windows.Forms.Control.InvokeHelper(Delegate method\', \'Comment 41: Boolean fSynchronous\', \'Comment 42: Object[] rgobjArgs) at DHPlantMobile.Main.MenuForm.MenuUserSelect_Click(MyIcon icon) at MyControls.MyIcon.OnClick() at MyControls.MyMenuIcon.HandleMouseUp(Object sender\', \'Comment 43: MouseEventArgs e) at System.Windows.Forms.Control.OnMouseUp(MouseEventArgs e) at System.Windows.Forms.Control.WnProc(WM wm\', \'Comment 44: Int32 wParam\', \'Comment 45: Int32 lParam) at System.Windows.Forms.ContainerControl.WnProc(WM wm\', \'Comment 46: Int32 wParam\', \'Comment 47: Int32 lParam) at System.Windows.Forms.Control._InternalWnProc(WM wm\', \'Comment 48: Int32 wParam\', \'Comment 49: Int32 lParam) at Microsoft.AGL.Forms.EVL.EnterModalDialog(IntPtr hwnModal) at System.Windows.Forms.Form.ShowDialog() at DHPlantMobile.Main.LoginUserForm.LogIn() at DHPlantMobile.Main.LoginUserForm.LoginProcess() at DHPlantMobile.Main.LoginUserForm.menuItemConfig_Click(Object sender\', \'Comment 50: EventArgs e) at System.Windows.Forms.MenuItem.OnClick(EventArgs e) at System.Windows.Forms.Menu.ProcessMnuProc(Control ctlThis\', \'Comment 51: WM wm\', \'Comment 52: Int32 wParam\', \'Comment 53: Int32 lParam) at System.Windows.Forms.Form.WnProc(WM wm\', \'Comment 54: Int32 wParam\', \'Comment 55: Int32 lParam) at System.Windows.Forms.Control._InternalWnProc(WM wm\', \'Comment 56: Int32 wParam\', ""Comment 57: Int32 lParam) at Microsoft.AGL.Forms.EVL.EnterMainLoop(IntPtr hwnMain) at System.Windows.Forms.Application.Run(Form fm) at DHPlantMobile.Program.Main(){code}\'"", ""Comment 58: \'Hi Thomas,The information from dev is that this will be fixed in new version.Please"", ""Comment 59: let me know if we can close this task.Regards\'"", ""Comment 60: \'Hi,Did the fix inderDGS-8630 solve issue for you?Regards\']""]\nRelated Issues:\n[]\n\n### End'}"
537,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8495\n\n### Instruction:\nDear, \r\npls update SU code list for medicated labels according to the languages.\r\nthx\r\n\n\n### Response:\n[""Comment 1: [\'[^SU codes SK_HU_07022023.csv] _(8 kB)_[^SU codes_CZ_SK_07022023.csv] _(12 kB)_\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Hi,SU codes have been updated. Please"", ""Comment 4: verify.Regards\'"", ""Comment 5: \'Hi"", ""Comment 6: it is ok.thx\']""]\nRelated Issues:\n[]\n\n### End'}"
538,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8494\n\n### Instruction:\nDears,\r\n\r\nI have made an account for my colleague GGeerts for DHP for the new plant in Helmond. Unfortunately I have made a mistake in typing the password. Can you please adjust GGeert\'s current password for DHP 3.0 in Helmond to:\r\n\r\nHeus22!\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'I sent a new password in private message.\'"", ""Comment 3: \'Hi Theo,Did you receive new password for Gerard? Does it work properly? Can we close this task?Regarsd\'"", ""Comment 4: \'Hi,Can we close this task?Regards\'"", ""Comment 5: \'Hello,We are closing this task as we haven’treceivedany replyfromyouforalong time. If the issueappearsagain"", ""Comment 6: please raise another task.Regards\']""]\nRelated Issues:\n[]\n\n### End'}"
539,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8493\n\n### Instruction:\nFor some reason, the heavy pallet location group no longer works.\r\n\r\nThis currently results in the warehouse filling up all locations and when heavy pallets arrive, they have to empty racks again to put the pallets in the right place.\r\n\r\nThis does not seem to go well with the locations that are linked to this location group. The fact that all locations are 3 double in it also indicates that something is going wrong here.\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Please be informed that we have forwarded the issue to the development team in order to internal analysis.We are waiting for more details and will be back with further information as soon as possible.\'"", ""Comment 4: \'[~bkremers@deheus.com] I removed this group and recreated it again. Please check if it will work. !ZP Location group! \'"", ""Comment 5: \'Hi,Can we close this task?Regards\'"", ""Comment 6: \'I still did not recieve any responce from the userI again asked for responce\'"", ""Comment 7: \'Waiting for ypur feedback then.Regards\'"", ""Comment 8: \'Any feedback?\']""]\nRelated Issues:\n[]\n\n### End'}"
540,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8492\n\n### Instruction:\nPlease create a new user for Agra-Matic. \r\n\r\nName: Willeke van Dijk.\r\n\r\nSame permissions as Nicole van Stigt Thans\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Account created.\']""]\nRelated Issues:\n[]\n\n### End'}"
541,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8491\n\n### Instruction:\nOld production orders are still in DHP.\r\nIn CDN are the orders canceled.\r\nHow can this list be corrected?\r\n\r\nIt seems to go wrong:\r\nWhen cancelled confirmed  \r\n\r\nWhen Closed confirmed it seem to be alwright.\r\n\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!!image-1!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 3: ""{code:java}select distinct cdn.nazwaobiektu (zan_gidtyp\', \'Comment 4: ZaN_GIDNumer,1,2) from cdn.ZamNag zleft join cdn.ZamElem e on z.ZaN_GIDNumer=e.ZaE_GIDNumerwhere --ZaN_GIDTyp=960 AND ZaN_GIDFirma=1015303 AND ZaN_GIDNumer=18035 and ZaE_GIDNumer is null and ZaN_Stan=35{code}{code:java}select status,DocumentNumber,*  FROM [Evolution_DHCountry].[dbo].[Orders]  where DocumentNumber in({code}{code:java}select *from  [dbo].[OrderExportInfoes] oewhere entityid in(select id  FROM [dbo].[Orders] o  where  DocumentNumber in(\\\'SO-201/05/2022/V\\\',\\\'SO-202/05/2022/V\\\',\\\'SO-203/05/2022/V\\\',\\\'SO-204/05/2022/V\\\',\\\'SO-205/05/2022/V\\\',\\\'SO-206/05/2022/V\\\',\\\'SO-207/05/2022/V\\\')){code}""\', \'Comment 5: ""Hello.When canceling an order from XL\', \'Comment 6: do not select options \\\'All items of order will be deleted\\\' and \\\'Customer\\\'s data will be deleted\\\'.When you choose option all reservation will be deleted already canceling orders is available. !screenshot-1! I have resent these orders to DHP - now the status will be correct.I will check the others and send a list.""\', ""Comment 7: \'Hello. I am sending a full list of corrected statuses for orders"", ""Comment 8: [^orders.txt] Please check and send a feedback.Regards.\'"", ""Comment 9: \'[[DHC] błędny status zamówień dhc/dhp|onenote:https://kotrak.sharepoint.com/sites/erpasysta/Shared%20Documents/Baza%20wiedzy/Baza%20Wiedzy%20-%20ERPSD/Klienci/DEHEUS/DEHEUS%20APPLICATIONS/Holandia%20Premix%20i%20AS400/Baza%20wiedzy.one#%5bDHC%5d%20b%C5%82%C4%99dny%20status%20zam%C3%B3wie%C5%84%20dhc/dhp&section-id=\\\\\\\\{B6BA0A4E-07B0-413E-A582-89B093FD9A36}&page-id=\\\\\\\\{8DE7307B-E53A-430D-B6AF-596D8DCB3070}&end] ([Widok sieci Web|https://kotrak.sharepoint.com/sites/erpasysta/_layouts/OneNote.aspx?id=%2Fsites%2Ferpasysta%2FShared%20Documents%2FBaza%20wiedzy%2FBaza%20Wiedzy%20-%20ERPSD&wd=target%28Klienci%2FDEHEUS%2FDEHEUS%20APPLICATIONS%2FHolandia%20Premix%20i%20AS400%2FBaza%20wiedzy.one%7CB6BA0A4E-07B0-413E-A582-89B093FD9A36%2F%5BDHC%5D%20b%C5%82%C4%99dny%20status%20zam%C3%B3wie%C5%84%20dhc%5C%2Fdhp%7C8DE7307B-E53A-430D-B6AF-596D8DCB3070%2F%29])\'"", ""Comment 10: \'Waiting for feedback off requester\'"", ""Comment 11: \'Hello,can I count on an update of this ticket?Thank you and regards.\'"", ""Comment 12: \'Ticket can be closed\']""]\nRelated Issues:\n[]\n\n### End'}"
542,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8490\n\n### Instruction:\nPlease check the screenshot for error message. JO\'s can not be processed due to an error. Thank you.\n\n### Response:\n[""Comment 1: [\'!JO!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 3: ""Hi Aleksandra. The issuer confirmed me that this problem also dissapeared and that JO\\\'s are being processed normaly. As of 10-15 mins ago. As I said and for previous ticket if you find anything suspicious or misuse please fell fre to share with me. Thank you.""\', \'Comment 4: \\\'Let me know if you still have this problem.The indicated message is displayed when the document creating the used resource does not have the ""Fixed delivery value"" parameter selected.!image-2023-02-07-16-50-53-588.png!For a given JO document there are 2 RM documents. One of them\', \'Comment 5: IR--100/02/23/S\', \'Comment 6: has taken resources from 3 deliveries:IR+-73/02/23/S\', \'Comment 7: IR+-76/02/23/S\', \'Comment 8: IR+-87/02/23/SAccording to the message all of those documents did not have set ""Fixed delivery value"" parameter.For example JO-73/02/23/S that created document IR+-73/02/23/S was closed today.!image-2023-02-07-16-53-32-093.png!That means ""Fixed delivery value"" parameter on IR+ document related to this JO were set today\', ""Comment 9: after closing this JO.At the moment this parameter is set on all related IR+ documents and JO document has got to close status.Please try to close JO-20/02/23/S or let me know if I may try to close it.\'"", \'Comment 10: ""Well this is one highly detailed report! Now it is quite clear for all of us what causes this kind of JO\\\'s processing conflict. Thank you very much. Best regards.""\', ""Comment 11: \'You may now close this ticket. Thank you"", ""Comment 12: best regards.\']""]\nRelated Issues:\n[]\n\n### End'}"
543,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8489\n\n### Instruction:\nHello again, we have the same problem with receipes in Cuprija. Receipes in Sabac are OK so it is again like DGS-8470. Please check what is the problem. Thank you.\n\n### Response:\n[""Comment 1: [\'!recipes!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Hi,In Cuprija you have exactly the same configuration as in Sabac"", \'Comment 4: recipes are available. Please\', \'Comment 5: provide me a screenshot from DHP\', ""Comment 6: where is the issue.Regards!image-2023-02-07-12-23-04-287.png!\'"", ""Comment 7: \'I just called the issuer on which behalf I created the ticket and he told me that the problem was solved  10-15 mins ago so the screenshot does not exist anymore. Did you find any irregularities in using the app? Maybe some users are not doing something properly? Maybe...\'"", ""Comment 8: \'It is difficult to judge as we do not know what user did"", \'Comment 9: maybe user opened wrong tab or sth or some connection issue.If the issue reoccurs\', \'Comment 10: please raise a new task. Forn now\', ""Comment 11: I am closing this task.Regards\'"", ""Comment 12: \'I understand. Thank you for quick answer. Ragards\']""]\nRelated Issues:\n[]\n\n### End'}"
544,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8488\n\n### Instruction:\nPlease help to check VT-3471/23 and quickly solve for Bien Hoa plant .\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Please check. Now it should be OK.\'"", ""Comment 4: \'Hi Łukasz LasokTks for ur support. \'"", ""Comment 5: \'brak błędów.\']""]\nRelated Issues:\n[]\n\n### End'}"
545,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8487\n\n### Instruction:\n2 recipes 147296 and 116000 don\'t show up in DHP.\r\n\r\nThey exist in DHC however. Resending them from DHH did not help.\r\n\r\nPlease assist. Needs to be produced before tomorrow morning. You can call me on +31621679216\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Dear Martijn,This issue was investigated in other RCA task under:[https://helpdesk.kotrak.com/servicedesk/customer/portal/56/DGS-7809]I have granted you access"", ""Comment 4: please check.The DHC 3.0.60 version should solve the problem.Regards\'"", ""Comment 5: \'!image-2023-02-09-09-16-16-098.png!\'"", ""Comment 6: \'DearMartijn,Below is the list of items which I pushed / resynced to DHC Service as they were missing in DHC Service.306250116002116003132160148296148294306814132330132310140373306808Regards\'"", ""Comment 7: \'Please"", ""Comment 8: let us know if we can close this task.Regards\'"", ""Comment 9: \'{color:black}Yes"", \'Comment 10: thanks{color} {color:black}{color} | |{color:#000001} Kindregards,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Martijn{color} |{color:#000001} {color} |{color:#000001} Meier{color} |  {color:#000001}ApplicationEngineer{color} | | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.deheus.com/]>{color} | |  *{color:#006FB7} *DEHEUSANIMALNUTRITIONB.V.*{color}* | | | |{color:#000001} P.O.Box396 6710BJEde TheNetherlands{color} | |{color:#000001} Rubensstraat175 6717VEEde TheNetherlands{color} | | |{color:#000001} M:{color}{color:#000001}{color}{color:#000001}+31621679216{color}{color:#000001} <tel:+31%206%2021%20679%20216>{color} |  {color:#000001}CoC16011201{color}   _{color:#000001} _Thise‑mailmessageanditsattachmentsaresubjecttothedisclaimer_ _publishedonthewebsiteof_{color}_{color:#000001} _+{color}[{color:#000001}{color}{color:#000001} _+ DeHeusAnimalNutrition+_{color}{color:#000001} {color}|https://www.deheus.com/disclaimer]{color:#000001} {color}+__{color:#000001} _._{color}_ | | !image002! <[https://www.facebook.com/deheusanimalnutrition]>{color:black}{color} | | !image003! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image004! <[https://www.linkedin.com/company/royal-de-heus/mycompany/]>{color:black}{color} | | !image005! <[https://www.instagram.com/de_heus_animal_nutrition/]>{color:black}{color} |      *From:* Aleksandra Przybyłek (Jira) <jira@kotrak.com>   *Sent:* vrijdag 10 februari 2023 13:16  *To:* Meier\', ""Comment 11: Martijn <mmeier@deheus.com>  *Subject:* DGS-8487 [RCA] - 2 receipes not coming to DHP Maasbracht   |  *{color:white} *CAUTION: This message originated from outside the organisation. Please do not click on links or open attachments unless you trust the sender and know the content is safe.*{color}* |   \']""]\nRelated Issues:\n[\'DGS-8486\', \'DGS-8528\']\n\n### End'}"
546,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8486\n\n### Instruction:\n2 recipes 147296 and 116000 don\'t show up in DHP.\r\n\r\nThey exist in DHC however. Resending them from DHH did not help.\r\n\r\nPlease assist. Needs to be produced before tomorrow morning. You can call me on +31621679216\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Recipes for 147296 and 116000 are avaible in DHP. Please check.!image-2023-02-06-19-46-37-025.png!!image-2023-02-06-19-47-04-386.png!\'"", ""Comment 3: \'[[DHP 3.0] Brak itemu w DHCService|onenote:https://kotrak.sharepoint.com/sites/erpasysta/Shared%20Documents/Baza%20wiedzy/Baza%20Wiedzy%20-%20ERPSD/Klienci/DEHEUS/DEHEUS%20APPLICATIONS/S%C5%82owacja/Baza%20wiedzy.one#%5bDHP%203.0%5d%20Brak%20itemu%20w%20DHCService&section-id=\\\\\\\\{DF42641F-8CC9-4202-8956-D8DA3EB978DE}&page-id=\\\\\\\\{1F3C6D0F-FACF-46BE-9BE3-93975830A455}&end] ([Widok sieci Web|https://kotrak.sharepoint.com/sites/erpasysta/_layouts/OneNote.aspx?id=%2Fsites%2Ferpasysta%2FShared%20Documents%2FBaza%20wiedzy%2FBaza%20Wiedzy%20-%20ERPSD&wd=target%28Klienci%2FDEHEUS%2FDEHEUS%20APPLICATIONS%2FS%C5%82owacja%2FBaza%20wiedzy.one%7CDF42641F-8CC9-4202-8956-D8DA3EB978DE%2F%5BDHP%203.0%5D%20Brak%20itemu%20w%20DHCService%7C1F3C6D0F-FACF-46BE-9BE3-93975830A455%2F%29])\'"", ""Comment 4: \'I see"", \'Comment 5: thanks! What was the cause\', ""Comment 6: and how did you solve it?\'"", ""Comment 7: \'In this task we have focused on clearingandunblocking the process. Provided items did not synchronized correctly. I had to correct data in database and resynchronize items in DHH"", \'Comment 8: I also had to resynchnize recipes\', \'Comment 9: production recipes and technology on DHC.If there is a need from your sideto investigate the reasonof the issue\', \'Comment 10: we may raise RootCause Analysis (RCA)task for you.Please\', ""Comment 11: let us knowhow you wish us to proceed.\'"", ""Comment 12: \'Thanks Bartłomiej. I thought there was an agreement dat an RCA is created for every P1 incident.So please proceed on that. Thanks!\'"", ""Comment 13: \'Hi"", ""Comment 14: RCA DGS-8487 has been created.\'"", ""Comment 15: \'May we close this P1 task ?\'"", ""Comment 16: \'Yes"", ""Comment 17: this one can be closed. Can you please grant me access to DGS-8487? :)\'"", ""Comment 18: \'You should already have access\'"", ""Comment 19: \'Dear Martijn,Could you please check task with number DGS-8487 via portal?Regards\']""]\nRelated Issues:\n[\'DGS-8487\']\n\n### End'}"
547,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8485\n\n### Instruction:\nWhen I check the missing RM report for Utrecht, I see some items displayed that have plenty of stock: Can you check what\'s going on? Are the lot reports still closed automatic when there is stock?\r\n\r\nSee RM report attached.\r\nItem 0002, 0041, 0048 have plenty of stock on hand, but are still dispayed \n\n### Response:\n[""Comment 1: [\'!afbeelding!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'We wsparciu Macieja zaczęłam od 0002"", ""Comment 4: ale nie wyświetla takich PLRów!image-2023-02-08-08-54-15-777.png!!image-2023-02-08-08-54-37-584.png!\'"", ""Comment 5: \'Dlatowaru 0041!image-2023-02-08-08-55-29-232.png!Potwierdziłam PLRa!image-2023-02-08-08-55-56-715.png!Zniknął z raportu!image-2023-02-08-08-56-24-501.png!\'"", ""Comment 6: \'[~aleksandra.przybylek@kotrak.com],Raport pokazuje missing stock na moment potwierdzania konkretnego raportu.Owszem mają stan magazynowy ale jest on w całości zarezerwowany pod inne loty produkcyjne.Sprawdziłem sporą ilość raportów i w każdym przypadku okazywało sie że brakuje tego stanu do potwierdzenia raportu (min. z powodu tego że jest on zarezerwowany pod inny raport)Te przypadki które udalo Ci się potwierdzić to są takie które i tak byłyby w koncu potwierdzone przez automat. Automat podczas potwierdzania bierze raporty z najmniejsza ilością prób potwierdzeń. Więc to to determinuje kiedy taki raport zostałby potwierdzony.Aby rozwiązać ich problemy należałoby niestety ręcznie pousuwać te rezerwacje i albo wtedy te raporty potwierdzić albo zostawić tą pracę dla automatu.\'"", ""Comment 7: \'Dear Thomas,The report shows missing stock at the moment of confirming a specific report.You do have stock"", \'Comment 8: but it is fully reserved for other production lots.We checked a large number of reports and in each case it turned out that this state is missing to confirm the report (at least because it is reserved for another report)Automatic confirmation closes reports with the least number of confirmation attempts. This is what determines when such a report would be confirmed.To solve the issue\', \'Comment 9: unfortunately\', ""Comment 10: these reservations would have to be removed manually and either confirmed also manually or we would leave this work for the automatic closing.Regards\'"", \'Comment 11: ""Hi Aleksandra: I\\\'m missing your pont. Check article 0002: The report displays a Missing quantity of 273451kg. But the quantity on hand (so not reserved!) is said to be 165 860 kg. So that quantity can be consumed/reserved\', \'Comment 12: but quantity is not lowered""\', ""Comment 13: \'And check article 0041: Missing quantity is reported as 58267kg: But DHP displays 0041 with quantity on hand 376 430kg: So more than enough. Sorry to say"", \'Comment 14: but as far I can see this is not reserved for anything\', ""Comment 15: otherwise it wasn;t on hand: So please check again!afbeelding-4!!afbeelding-6!\'"", ""Comment 16: \'Hi [~TDankers@deheus.com],Please"", \'Comment 17: let me explain to you how the mechanism of auto-confirmation lot reports works. The picture below presents the configuration of the auto-confirmation mechanism:!image-2023-02-08-16-46-18-029.png! * *CronSchedules* means how often the mechanism will check for production lots to be confirmed - in this case every single 1 hour. * *MaxCount* means how many ProductionLots will be taken by autoconfirm mechanism to be confirmed - Currently\', \'Comment 18: it is set to 200. * *MaxAgeInDays* means how ""old"" production lots will be taken into consideration in autoconfirming Production Lot mechanism - Currently\', \'Comment 19: it is set to 60 days.What is more\', \'Comment 20: in the production lots table there is a column that stores information about how many confirmation trials were performed in order to auto-confirm production lot (Please look at the picture below)!image-2023-02-08-16-50-39-647.png!The mechanism for auto-confirmation of production lots selects only those lot reports that are not older than 60 days and are sorted by the least amount of confirmation attempts.I analyzed 3 production lots with missing item 0002. Those lots are 0071190123076\', \'Comment 21: 0071190123082\', \'Comment 22: 0071190123089.In order to determine if/when those lots will be taken by the auto-confirmation mechanism we can use the query presented below:{code:java};WITH ProductionLotsConfirmationTraials AS(  SELECT ROW_NUMBER() OVER(ORDER BY ConfirmationAttempts ASC) AS NumberInQueue\', \'Comment 23: LotNumber\', \'Comment 24: ConfirmationAttempts  FROM [DHPlantProdBusinessLogicMain].[dbo].[ProductionLots] PL  WHERE PL.ProductionLotStatus = 3 and CAST(PL.StartDate AS DATE) >= DATEADD(DAY\', \'Comment 25: -60\', ""Comment 26: CAST(GETDATE() AS DATE)))SELECT * FROM ProductionLotsConfirmationTraialsWHERE LotNumber IN (\\\\\'0071190123076\\\\\'"", ""Comment 27: \\\\\'0071190123082\\\\\'"", ""Comment 28: \\\\\'0071190123089\\\\\'){code}And here are the results of the query execution:!image-2023-02-08-17-07-10-874.png!It looks like that even though there is a stock available in order to confirm those lots the number in the queue is saying that there are 654 lot reports that have a lower number of confirmation trials. So that is probably the issue of why those lots are not confirmed automatically.I hope that I helped. If you have more questions please feel free to ask me. I will do my best to respond to your questions on Friday since tomorrow I will be not present at work.Regards\'"", ""Comment 29: \'Hi Maciej"", \'Comment 30: Appreciated the explanation\', ""Comment 31: that helps a lot! Clear how the mechanism works and why it stays in the report even so stock is available\'"", ""Comment 32: \'Hi Thomas,Do you need any further help or should we close this task?Regards\'"", ""Comment 33: \'You can close this task\'"", ""Comment 34: \'Thank you\']""]\nRelated Issues:\n[]\n\n### End'}"
548,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8484\n\n### Instruction:\nRecipe 515205 exists in DHC, but not in DHP Sneek\r\n\r\nIn DHCService_Error queue, I see this error message regarding this recipe:\r\n\r\nThe conversion of a datetime2 data type to a datetime data type resulted in an out-of-range value. \r\n\r\nWhat causes this error, and how do we solve it?\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Hi,Recipe in Sneek now.Please"", ""Comment 3: verify.Regards!image-2023-02-07-15-10-32-661.png!\'"", ""Comment 4: \'{color:black}Yes"", \'Comment 5: I see it\', \'Comment 6: thanks!{color} {color:black}{color} {color:black}As always\', \'Comment 7: I’d like to know what was wrong here and whether I could have solved this myself. Can you briefly explain please?{color} {color:black}{color} | |{color:#000001} Kindregards,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Martijn{color} |{color:#000001} {color} |{color:#000001} Meier{color} |  {color:#000001}ApplicationEngineer{color} | | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.deheus.com/]>{color} | |  *{color:#006FB7} *DEHEUSANIMALNUTRITIONB.V.*{color}* | | | |{color:#000001} P.O.Box396 6710BJEde TheNetherlands{color} | |{color:#000001} Rubensstraat175 6717VEEde TheNetherlands{color} | | |{color:#000001} M:{color}{color:#000001}{color}{color:#000001}+31621679216{color}{color:#000001} <tel:+31%206%2021%20679%20216>{color} |  {color:#000001}CoC16011201{color}   _{color:#000001} _Thise‑mailmessageanditsattachmentsaresubjecttothedisclaimer_ _publishedonthewebsiteof_{color}_{color:#000001} _+{color}[{color:#000001}{color}{color:#000001} _+ DeHeusAnimalNutrition+_{color}{color:#000001} {color}|https://www.deheus.com/disclaimer]{color:#000001} {color}+__{color:#000001} _._{color}_ | | !image002! <[https://www.facebook.com/deheusanimalnutrition]>{color:black}{color} | | !image003! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image004! <[https://www.linkedin.com/company/royal-de-heus/mycompany/]>{color:black}{color} | | !image005! <[https://www.instagram.com/de_heus_animal_nutrition/]>{color:black}{color} |      *From:* Aleksandra Przybyłek (Jira) <jira@kotrak.com>   *Sent:* dinsdag 7 februari 2023 15:12  *To:* Meier\', ""Comment 8: Martijn <mmeier@deheus.com>  *Subject:* DGS-8484 SDNL-38558 | Recipe 515205 in DHC but not in DHP Sneek   |  *{color:white} *CAUTION: This message originated from outside the organisation. Please do not click on links or open attachments unless you trust the sender and know the content is safe.*{color}* |   !image006!\'"", ""Comment 9: \'Hi,The item was missing in DHC Service. I have resynced item"", ""Comment 10: resynced recipe and technology. Can I close this task?Regards\'"", ""Comment 11: \'Yes"", ""Comment 12: you can. Thanks for the explanation!\'"", ""Comment 13: \'Thank you.\']""]\nRelated Issues:\n[]\n\n### End'}"
549,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8483\n\n### Instruction:\nIn order to accurately track stock can we have the lot numbers appear on their respective JOs? \n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Hello,This functionality is already working. Please see example for PLR:0722090223002 and respectiveJO-313/23/TEMA!image-2023-02-10-10-49-05-852.png!!image-2023-02-10-10-52-35-193.png!Regards\'"", ""Comment 3: \'please close\'"", ""Comment 4: \'Thank you\'"", ""Comment 5: \'Alright kindly close  | !image001!!image006! |  *{color:#2E74B5} *Feyi Seyram Solomon*{color}*{color:#2E74B5} ServiceDesk Engineer{color}  *{color:#2E74B5} *Koudijs Ghana Limited*{color}*{color:#2E74B5} Phone: +233 30 7000 580 : Mobile: +233 59 6914 778{color}{color:#2E74B5}{color}  *{color:#2E74B5} *GK-0173-1282"", \'Comment 6: Tema Free Zone Enclave*{color}*  *{color:#2E74B5} *Tema\', \'Comment 7: Greater Accra\', \'Comment 8: COD TD 200 Ghana*{color}*  *{color:#2E74B5} **{color}*{color:#2E74B5} This e-mail message and its attachments are subject to the disclaimer published at the website of{color} [{color:#0563C1}Koudijs Animal Nutrition{color}|https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.koudijs.com%2Fdisclaimer&data=05%7C01%7CSFeyi%40koudijs.com.gh%7C1cdd4c26b4484d6270e708daf877ef8b%7C1004261bdfb74f37830f7438cb8a1b69%7C1%7C0%7C638095491246060747%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Sda%2Fs8RH6LVyAD6b9dCkcyZFILd6rVJqdsWh%2B65H9QE%3D&reserved=0]{color:#2E74B5}{color}  |      *From:* Aleksandra Przybyłek (Jira) <jira@kotrak.com>   *Sent:* Friday\', \'Comment 9: February 10\', \'Comment 10: 2023 9:55 AM  *To:* Feyi\', ""Comment 11: Solomon <SFeyi@koudijs.com.gh>  *Subject:* DGS-8483 Lot numbers on JOs   |  *{color:white} *CAUTION: This message originated from outside the organisation. Please do not click on links or open attachments unless you trust the sender and know the content is safe.*{color}* |   !image002!!image004!!image005!\']""]\nRelated Issues:\n[]\n\n### End'}"
550,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8482\n\n### Instruction:\nHello,\r\n\r\nWe have again an issue with inventorisation.\r\n\r\nComparing the figures downloaded at the end of 31 December 2022 for (stock on hand dated  31st December 2022) and\r\nthe report pulled today for (stock on hand dated 31st December 2022)\r\n\r\nThere seem to be variances in the figures.\r\n\r\nKindly help us get to the cause\n\n### Response:\n[""Comment 1: [\'[^recheck dec 31 2022.xls] _(67 kB)_\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 3: \\\'Hi SamuelAs I see now the quantities on stocks are different then in your report. The differences between quantity on stock and ""for sales"" are very small.The small differences result from documents such as warehouse documents without an internal document (generated from inventory) or purchase document (PORC-120/21) without a warehouse document (WR-)WR--126/22WR--118/22WR--127/22WR+1553/22This is because you generated inventory in different way - inventory configuration: stocktaken quantity: warehouseThere should be IR-\', \'Comment 4: IR+ documents generated from these documents. !screenshot-1! There is also IR--247/21/TEMA without WR-so you should generate WR- - by right mouse button on IR--247/21/TEMA and choose option WR- ""Release from warehouse""There are also some differences which probably results from some system errors and which has to be analysed .\\\'\', ""Comment 5: \'Is it possible to generate all document released or closed on 31st December 2022; but has initiating date prior to 31st December 2022 ( we believe lots of documents from prior month and year were released to disrupt the inventory process)\'"", \'Comment 6: ""Hi SamuelYes \', ""Comment 7: it\'s possible to create documents with date on 31st December and before.Regarding to Inventory process:If at the time of creating the inventory in the system there was a difference between the quantity for sale and the quantity in stock"", \'Comment 8: it certainly caused the inventory to be incorrect to some extent.Stocks  should always be leveled before starting an inventory and  there must be no documents in the buffer.At the moment\', \'Comment 9: even in the system there are still documents in the buffer in old years\', \'Comment 10: e.g. IR-3416/22/TEMA""\', ""Comment 11: \'How do we bring this document to excel with quantity and value to explain differences in inventory to our Bosses?\'"", \'Comment 12: \\\'Every document in the system can be transfer to excel file.You need to open document and use   !screenshot-2! [Export to speadsheet] icon - this option will transfer item with quantityor by [Printing icon] - but you need to print document as ""View on the screen"" and then use export icon (first icon on the left)The system will open Export window and you can choose options like:Export to excel\', \'Comment 13: PDF\', ""Comment 14: others !screenshot-3! \'"", ""Comment 15: \'What documents should I be looking for and how do I navigate to get all these documents causing these differences at a go?\'"", ""Comment 16: \'I think we need help resolving all warehouse discrepancies as soon as possible"", ""Comment 17: how do we do that  IR-3416/22.\'"", ""Comment 18: \'[^Warehouse_discrepancies.xlsx]\'"", \'Comment 19: ""HiI generated Internal Receipt and Internal Release documents from WR-\', \'Comment 20: WR+also I generated WR-\', \'Comment 21: WR+ from SORs documents from this list: !screenshot-4! I fixed document PORC-206/21\', \'Comment 22: the stock of 1101011 i s ok now (technically ok).I\\\'m attaching the list of documents  that are left to fix [^Warehouse_discrepancies.xlsx] ""\', \'Comment 23: \\\'HiI generated all warehouse documents.Now all differences between sales and warehouse quantity results from documents with status ""BUFFER""This is actually ok.But you need to remember that before inventory all documents should be confirmed.If you will try to add new inventory now the system will show warning:For warehouse ...... there are documents in buffer. It contains items which trade quantity is different than quantity in stock. It may not be possible to fully correct shortage quantity. Documents in buffer will not be confirmed until inventory is completed. !screenshot-5! \\\'\', ""Comment 24: \'Could you please confirm if we can close this task?Regards\'"", ""Comment 25: \'This ticket was created by Samuel so I cannot authorize that please.  | !image001!!image004! |  *{color:#2E74B5} *Feyi Seyram Solomon*{color}*{color:#2E74B5} ServiceDesk Engineer{color}  *{color:#2E74B5} *Koudijs Ghana Limited*{color}*{color:#2E74B5} Phone: +233 30 7000 580 : Mobile: +233 59 6914 778{color}{color:#2E74B5}{color}  *{color:#2E74B5} *GK-0173-1282"", \'Comment 26: Tema Free Zone Enclave*{color}*  *{color:#2E74B5} *Tema\', \'Comment 27: Greater Accra\', \'Comment 28: COD TD 200 Ghana*{color}*  *{color:#2E74B5} **{color}*{color:#2E74B5} This e-mail message and its attachments are subject to the disclaimer published at the website of{color} [{color:#0563C1}Koudijs Animal Nutrition{color}|https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.koudijs.com%2Fdisclaimer&data=05%7C01%7CSFeyi%40koudijs.com.gh%7C1cdd4c26b4484d6270e708daf877ef8b%7C1004261bdfb74f37830f7438cb8a1b69%7C1%7C0%7C638095491246060747%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Sda%2Fs8RH6LVyAD6b9dCkcyZFILd6rVJqdsWh%2B65H9QE%3D&reserved=0]{color:#2E74B5}{color}  |        *From:* Beata Kapturska (Jira) <jira@kotrak.com>   *Sent:* Friday\', \'Comment 29: March 17\', \'Comment 30: 2023 11:15 AM  *To:* Feyi\', ""Comment 31: Solomon <SFeyi@koudijs.com.gh>  *Subject:* DGS-8482 INVENTORY ON HAND   !image002!\'"", ""Comment 32: \'[~SAgbeke@koudijs.com.gh]Could you please confirm if we can close this task?Best Regards\'"", ""Comment 33: \'yes please\']""]\nRelated Issues:\n[]\n\n### End'}"
551,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8481\n\n### Instruction:\nCan you re-open round ID 30372? I thought this was already done, but I can not book a correction report on it. \n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 2: ""Hello,Round is in Active status now.We sent it back to \\\'Active\\\' status to Anja\\\'s inbox (as it was before).!image-2023-02-06-11-52-45-590.png!Regards""\', \'Comment 3: ""Who is able to re-open rounds at the moment? It should be Koen\', \'Comment 4: Steffen\', \'Comment 5: Nancy\', \'Comment 6: Peter and Bessel.I see lot\\\'s of tasks about this and I would like some users to be able to re-open rounds themselves.""\', ""Comment 7: \'It has been added in taskhttps://helpdesk.kotrak.com/servicedesk/customer/portal/56/DGS-8568\']""]\nRelated Issues:\n[]\n\n### End'}"
552,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8480\n\n### Instruction:\nPrzy podziale pozycji na różne magazyny w kontrakcie system (GUI)  przypisuję cenę z magazynu źródłowego pomimo wprowadzenia przez kupca innej ceny na pozycji, której ilość dokładamy już w momencie przepisywania ilości. Zapisanie formatu nie wnosi nic do poprawności danych.\r\n\r\n\r\nPrzykład kontrakt ZZ-298/01/23 testowany przeze mnie.\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \' !screenshot-1! \'"", \'Comment 3: ""Hi\', \'Comment 4: the application has an active configuration for copying the price and VAT from the source element to the target in split position.I understand it\\\'s a different case and is it always?Does it look like this on the test too?""\', ""Comment 5: \'Hello"", ""Comment 6: please reply to our last comment.Thank you and regards.\'"", \'Comment 7: \\\'Function ""split position"" should work as described in task https://helpdesk.kotrak.com/browse/GDC-589\\\'\', ""Comment 8: \'DEV-TS01-20 can I get access to this server for tests ? pgaczorek account because this GDC is from the middle of last year.\'"", ""Comment 9: \'done\'"", ""Comment 10: \'Access granted\'"", ""Comment 11: \'I made a scenario with GDC on the test for the order and the price is rewritten from the split position.Is it reproducible"", ""Comment 12: e.g. can it be repeated on the test - this case from the current dgs?Maybe a step-by-step video.\'"", ""Comment 13: \'you can close this task\']""]\nRelated Issues:\n[]\n\n### End'}"
553,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8479\n\n### Instruction:\nWe can update rounds for archived SI+PI, but not for SR. Can you make this possible too? \r\n\r\nThis is okay by Mitch. \n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 2: ""Hello Dirco,There is functionality for SR to updating round and invoices connected to SR.Could you verify that you are able to do it by this action from lightning - action \\\'Update SR and linked invoices Round Number\\\'?!image-2023-02-06-10-47-34-260.png!Regards""\', \'Comment 3: ""Yes I see now\', \'Comment 4: please close it. Thanks! Could not do this in another SR\', \'Comment 5: but don\\\'t know which this was""\', ""Comment 6: \'I close the task"", ""Comment 7: if there will appear some other issues with action please report it to us.Regards\']""]\nRelated Issues:\n[]\n\n### End'}"
554,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8478\n\n### Instruction:\nWhen deleted records appears again.\r\n\r\nAdvice was : VT on hold and then delete.\r\n\r\nQuestion : Witch VT?\n\n### Response:\n[""Comment 1: [\'See also ticket DGS-8293\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'This VT should be set on hold before delting SOR?The VT is closed. How can it then reopen the sor?!image!!image-1!!image-2!!image-3!\'"", \'Comment 4: \\\'Hi,SOR-111/09/2022/V will return because in DHP there is an information about dispatch so ERP Int ""copies"" the situation in documents in ERP.Why do you want to delete documents with items dispatched?Regards\\\'\', ""Comment 5: \'Hi,Any feedback?Regards\'"", ""Comment 6: \'This SOR111/09 has been incorrectly (double) createdSo this one has to be cancelled\'"", ""Comment 7: \'Can you please provide me:>> SOR number that was incorrectly (double) created by SOR-111?>> SO that is the source for duplicated SOR (the other one"", \'Comment 8: not 111)From ERP all seems to be good:we have one VT\', \'Comment 9: one SO and one SOR\', ""Comment 10: quantities are correct:!image-2023-03-01-12-49-20-309.png!!image-2023-03-01-12-50-33-501.png!!image-2023-03-01-12-51-28-996.png!\'"", ""Comment 11: \'!image-4!\'"", ""Comment 12: \'!image-5!\'"", ""Comment 13: \'Hi,I do not see where it is a duplicate. SOR-138 is clipped with different VT document and different SO document!image-2023-03-23-14-56-00-207.png!!image-2023-03-23-14-56-30-434.png!Please"", \'Comment 14: compare my screenshots from today and the previous one.If we want to cancel SOR-111 for ever\', \'Comment 15: we also need to cancel clipped VT-3865. Please\', ""Comment 16: accept or deny. What about SO-92 then?Regards\'"", ""Comment 17: \'Any feedback?Regards\'"", ""Comment 18: \'!image-6!\'"", ""Comment 19: \'I am waiting off responce from the user\'"", ""Comment 20: \'Waiting for your feedback then\'"", ""Comment 21: \'The user can not cancel this SOR.hen he tries to cancel the acceptbutton is still grey.The user is asking if Kotrak will cancel this SOR!image-7!\'"", ""Comment 22: \'I still do not have an answer for marked question that I have asked on the 23rd of March:If we want to cancel SOR-111 for ever"", \'Comment 23: we also need to cancel clipped VT-3865. Please\', ""Comment 24: accept or deny. What about SO-92 then?It is impossible to cancel SOR just like that.!image-2023-04-18-14-16-08-716.png!\'"", ""Comment 25: \'!image-8!\'"", ""Comment 26: \'VT-3865 has been cancelled in DHC"", \'Comment 27: SOR-111 has been deleted as it was in buffer\', \'Comment 28: SO-92 has been cancelled in ERP XL. Please\', \'Comment 29: verify.In DHP\', \'Comment 30: please perform inventory. Please\', ""Comment 31: let us know if we can close this task.Regards\']""]\nRelated Issues:\n[]\n\n### End'}"
555,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8477\n\n### Instruction:\nPlease help to check  VT-289/2/23 in Hai Phong 2 Plant (0436).\r\nThis VT can\'t be closed .\n\n### Response:\n[""Comment 1: [\'!image!!image-1!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 3: ""NA VT są 2x close VT w zależności co się wybierze -Final weighing is required in workflow-Unsupported VT close direction{code:java}SELECT *  FROM [DHPlantVCBusinessLogicMain].[dbo].[RF_VehicleTicketWorkflowTransitions] where id=\\\'3a68bd66-6d06-4fb9-af98-4c5a8ccf3ed0\\\'   insert into  [DHPlantVCBusinessLogicMain].[dbo].[RF_VehicleTicketWorkflowTransitions]  values  (\\\'3A68BD66-6D06-4FB9-AF98-4C5A8CCF3ED0\\\',2,\\\'2023-02-04 10:40\\\',3,\\\'XB3\\\',null)  select top 10 * from dbo.RF_WorkflowNodes where id=\\\'0C2FEEE4-64B4-4D16-87FF-99BCEEBF0693\\\'    select top 10 * from RF_VehicleTicketWorkflows where id=\\\'3a68bd66-6d06-4fb9-af98-4c5a8ccf3ed0\\\' {code}""\', ""Comment 4: \'Please check"", ""Comment 5:  VT-289 is now closed.\'"", ""Comment 6: \'[[DHP 3.0] Close VT"", ""Comment 7: problem z zamknięciem VT|onenote:https://kotrak.sharepoint.com/sites/erpasysta/Shared%20Documents/Baza%20wiedzy/Baza%20Wiedzy%20-%20ERPSD/Klienci/DEHEUS/DEHEUS%20APPLICATIONS/Wietnam/Baza%20wiedzy.one#%5bDHP%203.0%5d%20Close%20VT,%20problem%20z%20zamkni%C4%99ciem%20VT&section-id=\\\\\\\\{2B12CDB9-0ACA-4E3F-B40E-E88F97AD3C58}&page-id=\\\\\\\\{B5A9B8B1-38A8-4E61-AFB4-6DCA80B4A046}&end] ([Widok sieci Web|https://kotrak.sharepoint.com/sites/erpasysta/_layouts/OneNote.aspx?id=%2Fsites%2Ferpasysta%2FShared%20Documents%2FBaza%20wiedzy%2FBaza%20Wiedzy%20-%20ERPSD&wd=target%28Klienci%2FDEHEUS%2FDEHEUS%20APPLICATIONS%2FWietnam%2FBaza%20wiedzy.one%7C2B12CDB9-0ACA-4E3F-B40E-E88F97AD3C58%2F%5BDHP%203.0%5D%20Close%20VT%2C%20problem%20z%20zamkni%C4%99ciem%20VT%7CB5A9B8B1-38A8-4E61-AFB4-6DCA80B4A046%2F%29])\'"", ""Comment 8: \'Hi Piotr Gaczorek .You can close the ticket .\']""]\nRelated Issues:\n[]\n\n### End'}"
556,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8476\n\n### Instruction:\nAction \'Export S2P to Milas\' for S2P document should be executed only when document is sent \'To Archive\' to avoid situations when someone export S2P to Milas and then will change data on S2P. After sending S2P it shouldn\'t be possible to modify document again.\r\n\r\nAction \'Export S2P to Milas\' shouldn\'t be available from lightning button from ribbon - should be removed for all users.\r\n\r\nOnly few users should be able to send Archived S2P document to Entry state (Starting new process for document) - for now Mitch and Richard if there will be need to send again S2P to Milas.\r\n\r\nIt should be applied to all sectors.\r\n\r\n\xa0\n\n### Response:\n[""Comment 1: [\'Do zmiany ta akcja:!image-2023-02-03-12-53-46-122.png!!image-2023-02-03-12-53-53-556.png!\'"", ""Comment 2: \'Wszystkie akcje powinny wyglądać tak:!image-2023-02-03-13-53-57-914.png!\'"", ""Comment 3: \'We blocked the possibility of sending saldo2pay to milas from the button under the lightning"", ""Comment 4: saldo is send to milas automatically when the flow to the archive is performed!image-2023-02-03-14-47-28-069.png!\'"", \'Comment 5: ""Zmienione zostało ustawienie \\\'New process can be started\\\' na wszystkich dokumentach \\\'Saldo to Pay\\\' we wszyskich sektorach:!image-2023-02-06-10-24-26-533.png!Rola \\\'ALL\\\' ma uprawnienia do rozpoczynania nowego procesu. Na tą chwilę możliwość tą powinni mieć Mitch i Richard i są oni w tej roli.Usunięte zostało to uprawnienie dla roli \\\'All users\\\'\', \'Comment 6: tylko rola \\\'ALL\\\' ma możliwość rozpoczynania nowego procesu.!image-2023-02-06-10-31-12-337.png!""\', \'Comment 7: ""Exporting Saldo to pay to Milas now is moved to flow\', \'Comment 8: when document is sending \\\'To archive\\\' system sends S2P to Milas.!image-2023-02-06-11-12-21-523.png!Rights for starting new process has been added for Mitch and Richard. It will be possible to start new process in case when it\\\'s needed resend document Saldo to pay to Milas.!image-2023-02-06-11-11-12-104.png!""]\']\nRelated Issues:\n[]\n\n### End'}"
557,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8475\n\n### Instruction:\nwe have problem in production SUR7579-P-MD, 0871010223005, system not allow to add or change reservation.\r\nThe last time that we had similar problem (DGS-8210) was changed to settlement basing on ""Mixed"" , but this is not correct, we need to make consumption of correct delivery.\r\nWe need to load urgent, could you check why we have this error?\r\nThank you\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Hi,Is error message the same as in DGS-8210?\'"", ""Comment 4: \'To unblock this process we can change configuration as in DGS-8210 for a while"", \'Comment 5: you could add reservation and confirm and then we will return to previous configuration. The error is because for example this item is taken from two different deliveries\', \'Comment 6: please see attach:!image-2023-02-03-13-19-23-898.png!As Łukasz mentioned in previous task\', \'Comment 7: it comes from system assumption. If you want change assumption\', ""Comment 8: please raise a GDC task. In P1 task we are focusing on unblocking process.Regards\'"", \'Comment 9: ""Hello Aleksandra,we don\\\'t know if have the same error message\', \'Comment 10: because system not allow to add reservation and when we try to close\', \'Comment 11: shows that is missing reservation.But the tab reservation is with the same error\', \'Comment 12: gray lines without option to edit\', \'Comment 13: and white lines with option to add but when we select lot number\', \'Comment 14: changes to red but is not exceeded quantitty. So it\\\'s not possible to confirm.""\', ""Comment 15: \'Aleksandra,we can use 2 different deliveries"", ""Comment 16: and if PCS send a delivery with not available stock we can change the delivery on tab reservation. This happened other times and was possible to edit. Why is not possible edit this one?\'"", ""Comment 17: \'Is it possible tochange configuration to mixed and check if reservation is possible?\'"", ""Comment 18: \'We can see that there was some timeout that is why PLR did not change status to confirmed in Prod module. In Stock module it is confirmed and there are dispatches already that is why reservations are not editable. Please"", ""Comment 19: let us know if you can process PLR in ERP manually. Regards\'"", \'Comment 20: \\\'I changed the configuration for ""mixed""\', ""Comment 21: but it\\\\\'s not possible add the lot number"", ""Comment 22: system shows the line red even if I didn\\\\\'t add all quantity !image-2!\'"", ""Comment 23: \'Please"", \'Comment 24: return configuration.We can see that there was some timeout that is why PLR did not change status to confirmed in Prod module. In Stock module it is confirmed and there are dispatches already that is why reservations are not editable. Please\', ""Comment 25: let us know if you can process PLR in ERP manually. Regards\'"", ""Comment 26: \'We pushed the event. Please"", ""Comment 27: verify\'"", ""Comment 28: \'Aleksandra I returned configuration. And in ERP we created inventory to have stock to invoice. But I need to close this production because this process is temporary and they need to reverse the inventory.You can change to P2. But I still need your help to close this production and open RCA to investigate what happened.Thank You\'"", ""Comment 29: \'We pushed event"", ""Comment 30: please verify now\'"", ""Comment 31: \'Dear [~psilva@deheus.com],as Aleksandra wrote earlier"", \'Comment 32: the lack of possibility to indicate the deliveries from which PLR should to be settled was due to the fact that all raw materials have already been settled.Settlement of raw materials occurred as a result of executing the report confirmation procedure. The procedure settled the raw materials but did not confirm the report due to a timeout in communication between the Stock and Production modules. The timeout\', \'Comment 33: in turn\', \'Comment 34: occurred due to an incorrect way of registerin the production. The procedure used to register the batch report was executed separately for each dosing of raw materials\', \'Comment 35: while it should have been executed once per batch.As of today\', \'Comment 36: we have confirmed the report in the production module and triggered its synchronization to DHC.In order to avoid similar problems in the future\', ""Comment 37: we propose to return to discussions about adding a separate procedure to allow each dosing to be registered with a separate message.\'"", ""Comment 38: \'Dear Priscyla,Can we close this task?Regards\'"", ""Comment 39: \'Dear Priscyla,Can we close this task?Regards\'"", ""Comment 40: \'Hi Aleksandra,yes"", ""Comment 41: you can close this task.Thank you.\']""]\nRelated Issues:\n[\'DGS-8210\', \'DAP-12601\', \'DAP-13280\']\n\n### End'}"
558,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8474\n\n### Instruction:\nDears,\r\n\r\nOne of our customers in Denmark gets audited next Monday and they need the labels. \r\nCan you generate Danish labels for the following three products:\r\n508609, 505312 and 508689? \r\nWe need these a.s.a.p. I hope you can help us. \n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Ostatnie wersje z DHH505312 - ver 154 508609 - ver 69508689 - ver 25\'"", ""Comment 3: \'Dear Theo,Could you please clarify? The newest version from DHH are the newest versions in Plant for requested items. Is that correct? Or freshest labels are required?!image-2023-02-03-12-15-37-286.png!!image-2023-02-03-12-16-27-421.png!!image-2023-02-03-12-16-58-944.png!\'"", ""Comment 4: \'Hi Aleksandra,Actually I need the labels for these orders (see image). Is that possible?!image-2!\'"", ""Comment 5: \'These orders have order only the three products i mentioned earlier. But it is important that we get the labels with the correct versions. If I can do something to assit you"", ""Comment 6: please let me know\'"", ""Comment 7: \'Theo,The first Order is in Plant. But please"", \'Comment 8: mind this order is from October. Could you please provide me the screenshot where the information is missing? And\', ""Comment 9: please send us Order numbers in excelRegards!image-2023-02-03-13-31-16-056.png!\'"", ""Comment 10: \'Otherwise the most recent versions of the labels might be sufficient for now as well. \'"", ""Comment 11: \'Theo,The first Order is in Plant. But please"", \'Comment 12: mind this order is from October. Could you please provide me the screenshot where the information is missing? And\', ""Comment 13: please send us Order numbers in excelRegards\'"", ""Comment 14: \'See attached Excel file (first column) for the Sales Orders. I miss all the label information because in the beginning there were not any labels printed. So all I need are the labels. At leaset for the three products I have mentioned earlier[^Copy of Pakbonnen van klant_638109503540026658.xlsx] _(14 kB)_\'"", ""Comment 15: \'Thank you\'"", ""Comment 16: \'[^TRADER_BagLabel_03022023_155931486_fa3dc2ee-cb59-4a6d-9855-93c1ebac33a7.xml]\'"", ""Comment 17: \'Please"", ""Comment 18: try to print and let us know if it works\'"", \'Comment 19: ""{code:java}select ii.Code as itemcode\', \'Comment 20:  o.DocumentNumber as salesordernumber\', \'Comment 21:  bp.Code as customercode\', \'Comment 22: e.No as linenumber\', ""Comment 23:  (select top 1 r.EntityId rc_EntityIdfrom [DHPlantPcsBusinessLogicMain].[dbo].Recipes rjoin [DHPlantPcsBusinessLogicMain].[dbo].Items i on i.id = r.ItemIdjoin [DHPlantProdBusinessLogicMain].[dbo].Labels l on l.ItemId = r.ItemId and l.VersionNo=r.Version and r.PlantId = l.PlantId join [DHPlantProdBusinessLogicMain].[dbo].Languages g on g.Id = l.LanguageIdwhere 1=1and i.id = ii.idand g.Code = \'DA\'order by r.Version desc"", ""Comment 24: Subversion desc) as recipeidfrom [DHPlantPcsBusinessLogicMain].dbo.Orders oinner join dbo.OrderElements e on e.id = o.idinner join dbo.items ii on ii.id = e.itemidinner join [DHPlantPcsBusinessLogicMain].dbo.BusinessPartners bp on bp.Id = o.TargetBusinessPartnerIdwhere o.ForeignDocument = \'SO000011036\'and ii.code in(\'508609\'"", \'Comment 25: \\\'505312\\\',\\\'508689\\\'){code}""\', ""Comment 26: \'In reference to the internal conversations via teams can we change the status of the request to p2?You respond to Maciej Dobrzański that this one label that we created was ok"", \'Comment 27: but unfortunately\', ""Comment 28: there is problem with missing this orders in other ( not supported by Kotrak) so do you want us to create other xmls files for the rest ?\'"", ""Comment 29: \'Sytuacja wygląda tak że jakby się zdecydowali robić te xml jednak to :na swagerze post big label request :uzupełniamy wg danych z select"", \'Comment 30: nazwy column pokrywają się z polami w polach do uzupełnienia\', \'Comment 31: język bez zmian\', ""Comment 32: i jak sprawdziłąm selectem cały czas ten sam costumer code,!image-2023-02-03-17-16-23-044.png!i klikamy na dole executei weryfikujemy czy plik xml się utworzył tutaj :!image-2023-02-03-17-18-35-225.png!wygenrowane pliki wycinamy i wysyłamy w tasku ( nie zostawiamy w tym folderze)\'"", \'Comment 33: ""tu wersja select juz na te wszystkie ordery z excela z foreignnumerami zeby moze było szybciej z tym poleciecselect ii.Code as itemcode\', \'Comment 34: o.DocumentNumber as salesordernumber\', \'Comment 35: o.ForeignDocument\', \'Comment 36: bp.Code as customercode\', \'Comment 37: e.No as linenumber\', ""Comment 38: (select top 1 r.EntityId rc_EntityIdfrom [DHPlantPcsBusinessLogicMain].[dbo].Recipes rjoin [DHPlantPcsBusinessLogicMain].[dbo].Items i on i.id = r.ItemIdjoin [DHPlantProdBusinessLogicMain].[dbo].Labels l on l.ItemId = r.ItemId and l.VersionNo=r.Version and r.PlantId = l.PlantId join [DHPlantProdBusinessLogicMain].[dbo].Languages g on g.Id = l.LanguageIdwhere 1=1and i.id = ii.idand g.Code = \'DA\'order by r.Version desc"", ""Comment 39: Subversion desc) as recipeidfrom [DHPlantPcsBusinessLogicMain].dbo.Orders oinner join dbo.OrderElements e on e.id = o.idinner join dbo.items ii on ii.id = e.itemidinner join [DHPlantPcsBusinessLogicMain].dbo.BusinessPartners bp on bp.Id = o.TargetBusinessPartnerIdwhere o.ForeignDocument in (\'SO000011036\',\'SO000007243\',\'SO000014250\',\'SO000017312\',\'SO000011036\',\'SO000011036\',\'SO000007243\',\'SO000014250\',\'SO000007243\',\'SO000014250\',\'SO000017312\',\'SO000017312\',\'SO000019255\',\'SO000020555\',\'SO000020544\',\'SO000022840\',\'SO000023891\',\'SO000025114\',\'SO000019255\',\'SO000025116\',\'SO000030186\',\'SO000033625\',\'SO000035730\',\'SO000023891\',\'SO000023891\',\'SO000036852\',\'SO000038307\',\'SO000038307\',\'SO000040369\',\'SO000044219\',\'SO000044882\',\'SO000046836\',\'SO000049821\',\'SO000054521\',\'SO000053590\',\'SO000056862\',\'SO000060692\')and ii.code in(\'508609\'"", \'Comment 40: \\\'505312\\\',\\\'508689\\\')""\', \'Comment 41: ""Hi Agnieszka\', \'Comment 42: you can close this task. Many thanks for your and Maciej\\\'s help in this. ""\', ""Comment 43: \'No issue :)Regards\']""]\nRelated Issues:\n[]\n\n### End'}"
559,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8473\n\n### Instruction:\nHi, form Wiola\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!!image-1!!image-2!\'"", ""Comment 2: \'Przy dodawaniu jakiego atrybutu (nazwa) jest taki błąd?\'"", ""Comment 3: \'!image-3!\'"", \'Comment 4: ""|Współpraca z XL - komunikat z błędem przy zapisie grupy atrybutów\', ""Comment 5: do której został dodany atrybut bez zaznaczonego parametru Synchronizowany z Comarch ERP XL.Z poziomu konfiguracji firmy / Płace / Atrybuty-grupy dodając grupę atrybutów w której zostanie przypisany atrybut bez zaznaczonego parametru Synchronizowany z Comarch ERP XL - podczas zapisu pojawia się komunikat:Cannot insert the value NULL into column \'AKl_AtKId\'"", \'Comment 6: table \\\'ERPXL_FIRMA_XL.CDN.AtrKompletyLinki\\\'; column does not allow nulls. INSERT fails.|2022.5.1|Oczekujące||||||Zgłaszający||||Data zgłoszenia||||Wersja realizacji|||||2022-06-24 08:51:43|2023.5.1|||""\', \'Comment 7: ""Dzień dobry,Na ten moment nie powinno być błędu przy otwieraniu atrybutów na pracownikach. Po naprawie nie powtórzyłam też błędu przy dodawaniu grupy atrybutów. Nie mniej jednak na stronie producenta znalazłam informację że jest to znany błąd o poniższej treści i planowana wersja naprawy to2023.5.1. Proszę o weryfikację czy przy dodawaniu tego pakietu dla innych pracowników problem się powtórzy.Współpraca z XL - komunikat z błędem przy zapisie grupy atrybutów\', ""Comment 8: do której został dodany atrybut bez zaznaczonego parametru Synchronizowany z Comarch ERP XL.Z poziomu konfiguracji firmy / Płace / Atrybuty-grupy dodając grupę atrybutów w której zostanie przypisany atrybut bez zaznaczonego parametru Synchronizowany z Comarch ERP XL - podczas zapisu pojawia się komunikat:Cannot insert the value NULL into column \'AKl_AtKId\'"", \'Comment 9: table \\\'ERPXL_FIRMA_XL.CDN.AtrKompletyLinki\\\'; column does not allow nulls. INSERT fails.""\', ""Comment 10: \'Jest ok"", \'Comment 11: temat do zamknięcia\', ""Comment 12: dzięki.\']""]\nRelated Issues:\n[]\n\n### End'}"
560,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8472\n\n### Instruction:\nHi, \r\n\r\nAt CDN XL 2020 ( x.x.x.41), \r\n We got error as attached when we try these steps -\r\nOption-1 \r\n    1) SO 289 => Item  - 883486200068   -  22 kg\r\n    2) SOR   => Change Quantity to 22 kg to 22.1 kg and save\r\n     ... Got resource issue as attached. \r\n\r\nOption-2\r\n    1) SO 289 => Item  - 883486200068   -  22 kg\r\n    2) SOR   =>  Generate as  Item  - 883486200068   -  22 kg\r\n    3) SORC => Quantity change to 22.1 kg and save.\r\n     ... Got resource issue as attached. \r\n\r\nOption-3 \r\nWe can release it if we try as below\r\n    1) SO 289 => Item  - 883486200068   -  22.1 kg\r\n    2) SOR   => can generate successfully.\r\n\r\nQuestion : \r\n1) since option 3 is works, stock must be available in system. Why we cannot do as Option 1 and Option 2. Any limitation?\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!DHF-1.JPG|thumbnail!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Hi "", ""Comment 4: Any update on below case. \'"", \'Comment 5: ""I\\\'ve changed configuration for SORC documents. From now on ERP system will allow you to use another delivery for release corrections. Second option should be avaible for You from now on.For purpose of analysis of first option we will need more information such as message with expanded Details section and document with such issue for analysis.""\', ""Comment 6: \'select * --update k set Kon_Wartosc=1from cdn.konfig k where kon_numer=-123\'"", ""Comment 7: \'Please"", ""Comment 8: let me know do you expect any additional actions from us regarding this issue? Can we close this ticket?\'"", ""Comment 9: \'Hi"", ""Comment 10: Sorry for late response. I am a bit confuse about 1st option. May I know what is it? I assume 2nd option be resource release from SOR correction able to use it? If we have extra resources. For Example: SOR with 20 kg and SORC with 20.56 kg. Is it worked?\'"", ""Comment 11: \'System ERP XL works based on quantities from deliveries. When You try to increase quantity on release document in Yours configuration it tries to release quantity from the exact same delivery.Ive changed that configuration option Please try to relog (log off and log on) into ERP sstem and check if system let You to increase quantity without any error message.\'"", ""Comment 12: \'So"", ""Comment 13: we will ask user to try and will update here. Please take on hold till end of next week? Is it ok?\'"", ""Comment 14: \'Please"", ""Comment 15: let me know do you expect any additional actions from us regarding this issue? Can we close this ticket?\'"", \'Comment 16: ""Hi\', ""Comment 17: users are testing this week. Could you please hold till end of this week (25-Feb). If we don\'t have any further issue"", \'Comment 18: please close the ticket. Thank you in advance.""\', ""Comment 19: \'Please"", ""Comment 20: let me know do you expect any additional actions from us regarding this issue? Can we close this ticket?\'"", ""Comment 21: \'Hi,Please close the ticket. \']""]\nRelated Issues:\n[]\n\n### End'}"
561,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8471\n\n### Instruction:\nHello, This is needed for planned Go-Live of Helmond: I set Priority to P2, but prio is high: We have an recipe 114206 which is blocked by contamination: Strange thing is that it is blocked for location Helmond, but same item/recipe exist also for location Maasbracht and is not blocked there: Can you check this and see what is wrong?\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'!image-2023-02-03-09-53-54-818.png!\'"", ""Comment 3: \'Hi Thomas,For this issue"", ""Comment 4: please create a story in task under DHITS-695 and let us know if we can close DGS task.Best regards\'"", ""Comment 5: \'Ticket created\'"", ""Comment 6: \'Thank you. Can I close DGS?\'"", ""Comment 7: \'Will it be picked there? I see it is not handled currently\'"", ""Comment 8: \'No"", ""Comment 9: this issue will be processed in DHITS as the factory is not on Service Desk.Regards\'"", ""Comment 10: \'Oke"", ""Comment 11: please close this ticket\'"", ""Comment 12: \'Thank you.\']""]\nRelated Issues:\n[]\n\n### End'}"
562,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8470\n\n### Instruction:\nThere are only 5 recipes available in dropdown menu for rework in Cuprija plant. It is necessary that all of the recipes are available in that menu, not just last 5. Thank you.\n\n### Response:\n[""Comment 1: [\'!HowItShouldBe!!NowOnly5available!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Please check should be working now.\'"", ""Comment 4: \'It is OK now. Thank you for your help. Best regards!\']""]\nRelated Issues:\n[]\n\n### End'}"
563,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8469\n\n### Instruction:\nHi\r\n\r\nWe created and wrongly registered a UL in WO(IP) process. However, when we try to remove the registered UL, system shows an error message.\r\nWO(IP)-24/2/23\r\n85-W02OS5\r\n\r\nCould you please remove this UL from registered?\r\n\r\nThank you\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \' !screenshot-1!  !screenshot-3!  !screenshot-2!  !screenshot-4!  !screenshot-5! \'"", ""Comment 4: \'Hello"", ""Comment 5: this STK is correct one?Because this code has one  !screenshot-6! !image-2023-02-03-13-58-25-071!\'"", \'Comment 6: ""Hi PiotrWe tried to clear the UL from WO(IP) screen\', \'Comment 7: without success.So we tried to release the UL in WMS module by stk also. So after we restored this UL. But we\\\'ll not use it. Physically this palletlabel doesn\\\'t exists anymore.What is your instructions? Confirm this WO(IP) with this UL and release it later with UL STK?Thank you""\', ""Comment 8: \'Yes please process it further and then release it by stocktaking.If there are errors please let me know.\'"", \'Comment 9: ""Hi PiotrI\\\'m trying to COMPLETE it\', \'Comment 10: however the button is disabled.Could you please complete it?Thank you!image-1!""\', ""Comment 11: \'Hi Maicon"", \'Comment 12: I chose the completed option\', ""Comment 13: please check.\'"", \'Comment 14: ""Hi PiotrNow it\\\'s OKYou can close this taskThank you very much""\', ""Comment 15: \'You are welcome\']""]\nRelated Issues:\n[]\n\n### End'}"
564,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8468\n\n### Instruction:\nthe following IOs are not showing up in DHP for VT to be created\r\nIO 404/23, 405/2 and 406/23 please help\n\n### Response:\n[""Comment 1: [\'Hello,\\\\r\\\\rWe are investigating your issue. We will inform you about the solution as soon as possible.\\\\r\\\\rRegards\\\\r\\\\r\'"", ""Comment 2: \'!4062.PNG|thumbnail! !406.PNG|thumbnail! !405.PNG|thumbnail!\'"", ""Comment 3: \'Please verify again it seems like all of them are all in dhp please verify. !4062.PNG!\'"", ""Comment 4: \'please close\']""]\nRelated Issues:\n[]\n\n### End'}"
565,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8467\n\n### Instruction:\nHi\r\n\r\nWe had a case of PLR whitout PCS report on screen last week.\r\nYesterday it happened again.\r\nThe PLR lot number *0882300123013* had the Start, Batches and Finish production on PCS however DHP didn\'t received information abou dosed quantity and it\'s reservations.\r\n\r\nHowever I checked in database and the information is there.\r\n\r\nCould you please check why this is happeneing?\r\nI\'m afraid of having more and more cases like this.\r\n\r\nThank you\n\n### Response:\n[""Comment 1: [\'!image!!image-1!!image-2!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'HiAny news?Thank you\'"", ""Comment 4: \'id=d80b877a-e353-4871-9fd2-4c8495888097\'"", ""Comment 5: \'!image-2023-02-06-14-00-31-759.png!\'"", \'Comment 6: \\\'!image-2023-02-06-14-37-30-990.png!{code:java}An error occurred while saving the entity changes. See the inner exception for details. -> The INSERT statement conflicted with the FOREIGN KEY constraint ""FK_Dosings_StockUnits_StockUnitId"". The conflict occurred in database ""DHPlantProdBusinessLogicMain""\', \'Comment 7: table ""dbo.StockUnits""\', ""Comment 8: column \\\\\'Id\\\\\'.The statement has been terminated.{code}\'"", ""Comment 9: \'!image-2023-02-06-14-48-11-133.png!Ale w stocku jest już inne id!image-2023-02-06-14-48-28-792.png!\'"", ""Comment 10: \'!image-2023-02-06-14-49-45-803.png!\'"", \'Comment 11: ""{code:java}FROM [DHPlantStockBusinessLogicMain].[dbo].[StockUnits] where id = \\\'09f525d4-e4aa-4811-a20e-4aa65483e2a7\\\' or id = \\\'FB9FD93F-73B2-41A6-931B-BF5EB50CC60A\\\'  FROM [DHPlantProdBusinessLogicIntercontext].[dbo].[Errors] where message like \\\'%D80B877A-E353-4871-9FD2-4C8495888097%\\\'  SELECT * FROM [DHPlantPCSBusinessLogicIntercontext].[dbo].[Errors] where message like \\\'%D80B877A-E353-4871-9FD2-4C8495888097%\\\'{code}{code:java}FROM [DHPlantProdBusinessLogicMain].[dbo].[ProductionLots] where LotNumber = \\\'0882300123013\\\'select * FROM [DHPlantProdBusinessLogicMain].[dbo].[ProductionLotElements] where id = \\\'D80B877A-E353-4871-9FD2-4C8495888097\\\'SELECT TOP (1000) [Id]      ,[Barcode]      ,[CreatedDate]      ,[ItemId]      ,[DeliveryId]      ,[Type]  FROM [DHPlantProdBusinessLogicMain].[dbo].[StockUnits] where Barcode = \\\'88-W02781\\\' and ItemId = \\\'EB087234-9A43-47BD-8E59-2EE33AB790DA\\\'{code}""\', ""Comment 12: \'Hi,The issue is with stock unit with barcode88-W02781. How was the intake done? Or how was it registered? By two users? Or were there some corrections made?Regards\'"", ""Comment 13: \'W błędach woła"", \'Comment 14: że StockUnit z ""żółtym"" id jest not found. I stock unit z tym id jest nie we wszystkich modułach. Wygląda troche tak\', ""Comment 15: jakby było usunięte i na nowo dodane!image-2023-02-07-11-29-15-178.png!!image-2023-02-07-11-29-15-178!\'"", \'Comment 16: ""{code:java}{code}{code:java}SELECT * FROM [DHPlantProdBusinessLogicIntercontext].[dbo].[Errors] where message like \\\'%09F525D4-E4AA-4811-A20E-4AA65483E2A7%\\\' order by CreateDate desc--SELECT * FROM [DHPlantStockBusinessLogicIntercontext].[dbo].[Errors] where message like \\\'%09F525D4-E4AA-4811-A20E-4AA65483E2A7%\\\' order by CreateDate desc--SELECT * FROM [DHPlantWmsBusinessLogicIntercontext].[dbo].[Errors] where message like \\\'%09F525D4-E4AA-4811-A20E-4AA65483E2A7%\\\' order by CreateDate descSELECT * FROM [DHPlantVCBusinessLogicIntercontext].[dbo].[Errors] where message like \\\'%09F525D4-E4AA-4811-A20E-4AA65483E2A7%\\\' order by CreateDate desc--SELECT * FROM [DHPlantQAMBusinessLogicIntercontext].[dbo].[Errors] where message like \\\'%09F525D4-E4AA-4811-A20E-4AA65483E2A7%\\\' order by CreateDate descSELECT * FROM [DHPlantPCSBusinessLogicIntercontext].[dbo].[Errors] where message like \\\'%09F525D4-E4AA-4811-A20E-4AA65483E2A7%\\\' order by CreateDate desc{code}""\', \'Comment 17: ""{code:java}SELECT * FROM [DHPlantProdBusinessLogicMain].[dbo].[StockUnits] where id = \\\'09f525d4-e4aa-4811-a20e-4aa65483e2a7\\\' or id = \\\'FB9FD93F-73B2-41A6-931B-BF5EB50CC60A\\\'SELECT * FROM [DHPlantVCBusinessLogicMain].[dbo].[StockUnits] where id = \\\'09f525d4-e4aa-4811-a20e-4aa65483e2a7\\\' or id = \\\'FB9FD93F-73B2-41A6-931B-BF5EB50CC60A\\\'SELECT * FROM [DHPlantPCSBusinessLogicMain].[dbo].[StockUnits] where id = \\\'09f525d4-e4aa-4811-a20e-4aa65483e2a7\\\' or id = \\\'FB9FD93F-73B2-41A6-931B-BF5EB50CC60A\\\'SELECT * FROM [DHPlantStockBusinessLogicMain].[dbo].[StockUnits] where id = \\\'09f525d4-e4aa-4811-a20e-4aa65483e2a7\\\' or id = \\\'FB9FD93F-73B2-41A6-931B-BF5EB50CC60A\\\'SELECT * FROM [DHPlantWmsBusinessLogicMain].[dbo].[StockUnits] where id = \\\'09f525d4-e4aa-4811-a20e-4aa65483e2a7\\\' or id = \\\'FB9FD93F-73B2-41A6-931B-BF5EB50CC60A\\\'SELECT * FROM [DHPlantQAMBusinessLogicMain].[dbo].[StockUnits] where id = \\\'09f525d4-e4aa-4811-a20e-4aa65483e2a7\\\' or id = \\\'FB9FD93F-73B2-41A6-931B-BF5EB50CC60A\\\'{code}""\', \'Comment 18: ""Hi AleksandraTracking the documents for this UL\', \'Comment 19: it wasn\\\'t done by two users (attached screen)I didn\\\'t find any DGS raised to fix this UL.What is the problem? Can you fix it? Will it happen again? What should we do to prevent it?Thank you!image-3!""\', ""Comment 20: \'HiAny news?How long will it take to fix that? Do we need to wait for it happened again?Thank you\'"", ""Comment 21: \'Hi,The issue relates to recreated barcodes. Problematic barcodes are quite old"", \'Comment 22: befor the version 8.3 has been upgraded.!image-2023-02-15-12-59-26-544.png|width=1540,height=110!Please\', ""Comment 23: let me know if we should fix the information on the printout.Regards\'"", ""Comment 24: \'Hi,Do you need any further action from our side or shall we close this task?Regards\'"", ""Comment 25: \'Hi AleksandraThank you for this information.Is there anything you can do to not allow this happen again? Probably fix this this information?Thank you very much\'"", ""Comment 26: \'Hi![~maciej.dobrzanski@kotrak.com]jesteśmy w stanie to jakoś globalnie fixnąć? :)\'"", ""Comment 27: \'[~aleksandra.przybylek@kotrak.com] badamy możliwości\'"", ""Comment 28: \'Please be informed that we have forwarded the issue to the development team in order to internal analysis how to prevent such situation.We are waiting for more details and will be back with further information as soon as possible.\'"", ""Comment 29: \'Podobna sytuacja dla 2 lotów z tego taska oba dotyczą tych dóch barcode :https://helpdesk.kotrak.com/browse/DGS-8728?filter=-1!image-2023-03-10-12-12-20-395.png!\'"", ""Comment 30: \'[~aleksandra.przybylek@kotrak.com] czy te rozjechane stany pochodzą sprzed wersji 8.3?\'"", ""Comment 31: \'[~maciej.dobrzanski@kotrak.com] Tak. Stock unit jest stworzony w styczniu 2022"", ""Comment 32: a oni mieli upgrade do wersji 7.9 w marcu 2022!image-2023-03-27-14-25-17-529.png!\'"", ""Comment 33: \'After the changes in version 8.3 the problem should no longer occurs. The barcode provided is from mid-September 2022!image-2023-04-19-12-53-10-450.png!and updates were done in November 2022.\']""]\nRelated Issues:\n[\'DGS-7646\', \'DGS-8728\']\n\n### End'}"
566,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8466\n\n### Instruction:\nChainge main, target and payer customer off SO-76/10/2022/V and ESI-3/11/2022/vexp from 7727 to 0674\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!!image-1!\'"", ""Comment 2: \'SDNL-35552\'"", ""Comment 3: \'See also DGS-8431\'"", ""Comment 4: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 5: \'Hello,Customer data changed as requested. Please"", ""Comment 6: verify and let us know if we can close this task.Regards!image-2023-02-07-10-21-27-262.png!!image-2023-02-07-10-21-44-034.png!\'"", ""Comment 7: \'Ticket can be closed\'"", ""Comment 8: \'Thank you\']""]\nRelated Issues:\n[]\n\n### End'}"
567,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8465\n\n### Instruction:\nMentioned recipe does not arrive in DHC. \r\n\r\nImport in DHC fails:\r\nObject reference not set to an instance of an object\r\n\r\nPlease verify why this happens. Thanks!\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'In DHC this bestmix has no base item and no linked items also"", ""Comment 3: could you fixed the linking and resend recipe? !image-2023-02-02-15-19-05-263.png!\'"", \'Comment 4: ""I\\\'m not familiar with this\', \'Comment 5: I have asked the user if she is. I\\\'ll come back to you later.""\', ""Comment 6: \'The item is linked to another BestMix item.!afbeelding!\'"", ""Comment 7: \'!967242.PNG|thumbnail!\'"", ""Comment 8: \'Are you sure that this is correct ? !967242.PNG!\'"", \'Comment 9: ""select distinct (i.Code) from RecipeIngredients rijoin Items i on ri.ItemId=i.id where ri.RecipeId in  (\\\'EBEA41EC-A0ED-40D4-B305-2025806C4EB9\\\',\\\'953BD597-2953-4D36-A5C6-25B4FD73989D\\\'\', \'Comment 10: \\\'1CF05321-0ACC-4AA1-9688-8D567D5D7D9E\\\')""\', ""Comment 11: \'nutrietinty tez wszystkie sa\'"", ""Comment 12: \'This ticket can be closed"", ""Comment 13: it is solved.\']""]\nRelated Issues:\n[]\n\n### End'}"
568,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8464\n\n### Instruction:\nHello, \r\n\r\nthis seems to be simular issue as DGS-8443: A lot report in DHP has status in progress but should be closed: If I check the request log I see 7 messages send, including islastbatch message. If I check DHP then the Lot only has 4 batches registered: When I try to resend batchreports the system indicates the batch is finished: Please Check this, we miss finished product stock in our systems due to this bug\n\n### Response:\n[""Comment 1: [\'!afbeelding!!afbeelding-1!!afbeelding-2!\'"", ""Comment 2: \'Same problem applies to PCS Lotnr: 305447"", ""Comment 3: 305384\'"", ""Comment 4: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 5: \'Impacted lots:!image-2023-02-06-07-45-08-260.png!\'"", ""Comment 6: \'!image-2023-02-06-08-14-57-618.png!\'"", ""Comment 7: \'{code:java}Exception has been thrown by the target of an invocation. -> A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider"", \'Comment 8: error: 40 - Could not open a connection to SQL Server) -> The network path was not found.An exception was thrown while activating Plant.Prod.BusinessLogic.Application.ProductionLots.CommandHandlers.RegisterBatchReportCommandHandler -> Plant.Prod.BusinessLogic.Application.ProductionLots.TransactionalProductionLotService -> Plant.Prod.BusinessLogic.Application.OrderProduction.TransactionalOrderProductionSynchronizationService -> Plant.Prod.BusinessLogic.Infrastructure.Persistance.ProductionOrders.ProductionOrderRepository -> Plant.Prod.BusinessLogic.Domain.ProductionOrders.ProductionOrderFactory -> Kotrak.Common.Infrastructure.BarcodeGenerator.BarcodeGenerator -> λ:Kotrak.Common.Infrastructure.BarcodeGenerator.NumberToAlphaBarcodeGeneratorPolicy. -> A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider\', ""Comment 9: error: 40 - Could not open a connection to SQL Server) -> The network path was not found.{code}\'"", ""Comment 10: \'!image-2023-02-06-08-26-15-292.png!!image-2023-02-06-08-33-57-988.png!\'"", ""Comment 11: \'!image-2023-02-06-08-54-48-536.png!*Production**!image-2023-02-06-08-56-41-333.png!**PCS**!image-2023-02-06-08-57-09-202.png!*\'"", ""Comment 12: \'!image-2023-02-06-09-00-20-054.png!!image-2023-02-06-09-01-02-612.png!!image-2023-02-06-09-01-20-182.png!\'"", ""Comment 13: \'Any update?\'"", ""Comment 14: \'Yes. For now we know the reason for all three PLR. As you can see below"", \'Comment 15: there was network related issue with connection to SQL. We are working on a solutionAn exception was thrown while activating Plant.Prod.BusinessLogic.Application.ProductionLots.CommandHandlers.RegisterBatchReportCommandHandler -> Plant.Prod.BusinessLogic.Application.ProductionLots.TransactionalProductionLotService -> Plant.Prod.BusinessLogic.Application.OrderProduction.TransactionalOrderProductionSynchronizationService -> Plant.Prod.BusinessLogic.Infrastructure.Persistance.ProductionOrders.ProductionOrderRepository -> Plant.Prod.BusinessLogic.Domain.ProductionOrders.ProductionOrderFactory -> Kotrak.Common.Infrastructure.BarcodeGenerator.BarcodeGenerator -> λ:Kotrak.Common.Infrastructure.BarcodeGenerator.NumberToAlphaBarcodeGeneratorPolicy. -> A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider\', ""Comment 16: error: 40 - Could not open a connection to SQL Server) -> The network path was not found.\'"", ""Comment 17: \'I have resent messages. It looks good now.Please"", ""Comment 18: verify\'"", ""Comment 19: \'Oke"", ""Comment 20: thanks: Can you also check https://helpdesk.kotrak.com/servicedesk/customer/portal/56/DGS-8443? same issue but then for location Nijkerk\'"", ""Comment 21: \'Yes"", \'Comment 22: we are are working on it. But\', \'Comment 23: unfortunatelly\', ""Comment 24: for Nijkerk the cause is different and now it is under dev verification.Can we close this task?Regards\'"", ""Comment 25: \'Yes you can close this task"", ""Comment 26: please make sure that ticket/fix will be visible in release notes of next version: otherwise we miss indication that it is fixed\'"", ""Comment 27: \'Dear Thomas,As I mentioned before"", \'Comment 28: here it was caused by network / connection issue. Regarding task DGS-8443 we are working on it to diagnose what happened and let you know inDGS-8443.In that case\', ""Comment 29: regarding Maasbracht I am closing this task.Regards\']""]\nRelated Issues:\n[]\n\n### End'}"
569,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8463\n\n### Instruction:\nGood afternoon,\r\nplease, would you create an openings balance for item 0694 on plant Veghel with a quantity of 200 kg.\r\n\r\nThanks for support.\r\n\r\nRegards,\r\n\r\nGerard\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Hello Gerard,The opening balance has been created. Please"", ""Comment 3: verify.Regards!image-2023-02-03-08-07-17-172.png!\'"", ""Comment 4: \'Hello Gerard,Can we close this task?Regards\'"", ""Comment 5: \'Hello Aleksandra,My apology"", ""Comment 6: that i forgot to send you an answer about this. But is correct.Please close this ticket.Have a nice weekend,Kind regards,Gerard\'"", ""Comment 7: \'Hello Gerard,Thank you for your information.Regards\']""]\nRelated Issues:\n[]\n\n### End'}"
570,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8462\n\n### Instruction:\nHello,\r\n\r\nVehicle ticket for dispatch are not created: Application is receiving bulkdispatch messages from PCS: Please check what is going on. For location Utrecht is happens more often, service restart or something is usually the solution\n\n### Response:\n[""Comment 1: [\'Hello,\\\\r\\\\rWe are investigating your issue. We will inform you about the solution as soon as possible.\\\\r\\\\rRegards\\\\r\\\\r\'"", ""Comment 2: \'Please try now\'"", ""Comment 3: \'wg logów tutaj był jakis problem o 5.17 wskazuje na jakies problemy z siecią ?!image-2023-02-02-13-35-22-850.png!\'"", ""Comment 4: \'Thanks\'"", ""Comment 5: \'May we close the task?\'"", ""Comment 6: \'Task can be closed\']""]\nRelated Issues:\n[]\n\n### End'}"
571,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8461\n\n### Instruction:\nIn the attachment we see an overview of S2P\'s that are archived. The rounds that are linked to it should be closed as well.\r\n\r\nCreating and archiving the S2P is te last step in the round process. Could you close all these rounds?\r\n\r\nNext to that we need to think about a structural approach for this. Can we automate it like this:\r\n* S2P for a specific round is archived manually by a user\r\n* The related round is automatically closed in the system\n\n### Response:\n[""Comment 1: [\'[^Rounds to be closed.xlsx] _(60 kB)_\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Do sprawdzenia excel i które z tych rund są do zamknięcia i można je zamknąć (przepływ do archiwum).Druga część to do obsłużenia to globalnie w systemie"", ""Comment 4: ale to też powiązane z podlinkowanymi taskami - do analizy.\'"", ""Comment 5: \'All of the indicated rounds are already closed\'"", \'Comment 6: ""It\\\'s related to other 2 tasks\', \'Comment 7: which should be considered with this one and we need to find best solution how to handle it globally.[https://helpdesk.kotrak.com/servicedesk/customer/portal/56/DGS-7956]https://helpdesk.kotrak.com/browse/DHNLC-1147""\', ""Comment 8: \'[^Closed runds.xlsx]\'"", ""Comment 9: \'Should we plan a discussion with some users to have this solved?\'"", ""Comment 10: \'Can be closed\']""]\nRelated Issues:\n[\'DGS-7956\']\n\n### End'}"
572,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8460\n\n### Instruction:\nGood morning,\r\n\r\nOur specials we book with the item code DIVO in the feed sale document.\r\nBecause we want to know what kind of feed the posting is, we give it a description.\r\nProblem is that this is not visible on the feedsale nor the financial statement.\r\n\r\nI will write an e-mail with printscreens.\r\n\n\n### Response:\n[""Comment 1: [\'{color:black}Good morning,{color} {color:black}{color} {color:black}Our specials we book with the item code DIVO in the feed sale document.{color} {color:black}Because we want to know what kind of feed the posting is"", ""Comment 2: we give it a description.{color}{color:black}{color} !image001!{color:black}{color}{color:black}{color} {color:black}Problem is that this is not visible on the feedsale nor the financial statement.{color}{color:black}{color} !image002!{color:black}{color}{color:black}{color} {color:black}Can this be modified?{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Christinede{color} |{color:#000001} {color} |{color:#000001} Jong{color} |  {color:#000001}MedewerkerContractadministratie{color} | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}{color:blue}{color}!image003!{color:blue}{color}{color:black} <[https://www.de-heus.nl/]>{color} | |  *{color:#006FB7} *DEHEUSVOEDERSB.V.*{color}* | | | |{color:#000001} Postbus396 6710BJEde \\\\u200b{color} | |{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} | | |{color:#000001} T:0318675567{color} |  {color:#000001}KvK14626985{color}   _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | |{color:blue}{color} !image004!{color:blue}{color} <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | |{color:blue}{color} !image005!{color:blue}{color} <[https://twitter.com/de_heus_voeders]>{color:black}{color} | |{color:blue}{color} !image006!{color:blue}{color} <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | |{color:blue}{color} !image007!{color:blue}{color} <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} |   \'"", ""Comment 3: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 4: \'Do sprawdzenia i ewentualnego poprawienia także procedury dotyczące wyciągania tych danych na wydruki FSKR_Printout_FS_TotalFeed_NAS\'"", ""Comment 5: \'Poprawiona procedura i select na dokumencie financial statement\'"", \'Comment 6: ""The feed table now shows the description and name of the item in the \\\'NAS\\\' sector as it works in other sectors""\', ""Comment 7: \'{color:black}Dear Tomasz,{color} {color:black}{color} {color:black}This is not yet functional?{color} {color:black}See enclosed feed sale extract from Intense NAS just a moment ago.{color} {color:black}{color} {color:black}For the migration post it can be that this field wasn’t filled.{color} {color:black}I checked it for SI000037572"", \'Comment 8: cause this is a posting made in Intense. Description is filled.{color}{color:black}{color} !image006!{color:black}{color}{color:black}{color} {color:black}{color} {color:black}{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Christinede{color} |{color:#000001} {color} |{color:#000001} Jong{color} |  {color:#000001}MedewerkerContractadministratie{color} | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.de-heus.nl/]>{color} | |  *{color:#006FB7} *DEHEUSVOEDERSB.V.*{color}* | | | |{color:#000001} Postbus396 6710BJEde \\\\u200b{color} | |{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} | | |{color:#000001} T:0318675567{color} |  {color:#000001}KvK14626985{color}   _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | | !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | | !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} | | !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} |      *Van:* Tomasz Zygoń (Jira) <jira@kotrak.com>   *Verzonden:* dinsdag 7 februari 2023 10:42  *Aan:* Jong\', ""Comment 9: Christine de <CJong@deheus.com>  *Onderwerp:* DGS-8460 Description DIVO not visible in Feed Sale document   |  *{color:white} *CAUTION: This message originated from outside the organisation. Please do not click on links or open attachments unless you trust the sender and know the content is safe.*{color}* |   !image006-1![^Feed VD Berg koppel slacht.xlsx] _(13 kB)_!image007!\'"", \'Comment 10: ""What is a problem because i can\\\'t redo situation where description is not copied from feed to financial statementView from feed sale!image-2023-02-07-15-08-54-541.png!View from financial statement!image-2023-02-07-15-13-22-107.png!""\', ""Comment 11: \'{color:black}Good morning Tomasz,{color} {color:black}{color} {color:black}We prefer a setting where our description is copied onto our FS.{color} {color:black}Is this not possible?{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Christinede{color} |{color:#000001} {color} |{color:#000001} Jong{color} |  {color:#000001}MedewerkerContractadministratie{color} | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.de-heus.nl/]>{color} | |  *{color:#006FB7} *DEHEUSVOEDERSB.V.*{color}* | | | |{color:#000001} Postbus396 6710BJEde \\\\u200b{color} | |{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} | | |{color:#000001} T:0318675567{color} |  {color:#000001}KvK14626985{color}   _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | | !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | | !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} | | !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} |      *Van:* Tomasz Zygoń (Jira) <jira@kotrak.com>   *Verzonden:* dinsdag 7 februari 2023 15:17  *Aan:* Jong"", ""Comment 12: Christine de <CJong@deheus.com>  *Onderwerp:* DGS-8460 Description DIVO not visible in Feed Sale document   |  *{color:white} *CAUTION: This message originated from outside the organisation. Please do not click on links or open attachments unless you trust the sender and know the content is safe.*{color}* |   !image006-2!!image007-1!!image006!!image007!\'"", \'Comment 13: ""Hello Christine,On Financial statement are presented values from Feed sale lines from field \\\'Description\\\'\', ""Comment 14: it means that if you change field \'Description\' on Feed sale document"", \'Comment 15: you will see it on Financial statement document also like on the screen below. Values are copied to FS\', \'Comment 16: so it looks good\', \'Comment 17: right?!image-2023-02-08-08-45-32-669.png!Regards""\', ""Comment 18: \'{color:black}Hi Damian,{color} {color:black}{color} {color:black}When we modify description and it is visible on feed sale extract and financial statement all is good{color} {color:black}😊{color}{color:black}{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Christinede{color} |{color:#000001} {color} |{color:#000001} Jong{color} |  {color:#000001}MedewerkerContractadministratie{color} | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.de-heus.nl/]>{color} | |  *{color:#006FB7} *DEHEUSVOEDERSB.V.*{color}* | | | |{color:#000001} Postbus396 6710BJEde \\\\u200b{color} | |{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} | | |{color:#000001} T:0318675567{color} |  {color:#000001}KvK14626985{color}   _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | | !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | | !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} | | !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} |      *Van:* Damian Świstek (Jira) <jira@kotrak.com>   *Verzonden:* woensdag 8 februari 2023 08:49  *Aan:* Jong"", ""Comment 19: Christine de <CJong@deheus.com>  *Onderwerp:* DGS-8460 Description DIVO not visible in Feed Sale document   |  *{color:white} *CAUTION: This message originated from outside the organisation. Please do not click on links or open attachments unless you trust the sender and know the content is safe.*{color}* |   !image006-3!!image006!!image007!\']""]\nRelated Issues:\n[]\n\n### End'}"
573,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8459\n\n### Instruction:\n!image-2023-02-02-11-10-51-390.png!\n\n### Response:\n[\'Comment 1: [""This value \\\'Totaal door u te betalen EUR\\\' should be always positive like a \\\'Totaal\\\' above?""\', ""Comment 2: \'Indeed\'"", ""Comment 3: \'Is it relevant to all sectors for S2P printouts?\'"", \'Comment 4: ""Do zmiany na wydrukach Saldo to Pay (także nowych\', \'Comment 5: które są stworzone i w trakcie akceptacji)\', \'Comment 6: aby wartość \\\'Totaal door u te betalen EUR\\\' była zawsze wyświetlana jako dodatnia.!https://attachments.office.net/owa/damian.swistek%40kotrak.com/service.svc/s/GetAttachmentThumbnail?id=AAMkADY2ZTAxMzM3LTE0YjctNGI0Ni1hYjIxLWE3MDFjOTVkNmExNwBGAAAAAAA%2FcPjpt4lNRZFonusrO6C9BwA5bA29TyJrQIX6A6F8SkSqAAAAAAEJAAA5bA29TyJrQIX6A6F8SkSqAAS37XAJAAABEgAQADpxOtUHE69HhCtCVdopo1c%3D&thumbnailType=2&token=eyJhbGciOiJSUzI1NiIsImtpZCI6IkQ4OThGN0RDMjk2ODQ1MDk1RUUwREZGQ0MzODBBOTM5NjUwNDNFNjQiLCJ0eXAiOiJKV1QiLCJ4NXQiOiIySmozM0Nsb1JRbGU0Tl84dzRDcE9XVUVQbVEifQ.eyJvcmlnaW4iOiJodHRwczovL291dGxvb2sub2ZmaWNlLmNvbSIsInVjIjoiNzQ1YWJkOWJmNWUxNGJhMWJkNjE5OTZmNzhmMzQzNGYiLCJzaWduaW5fc3RhdGUiOiJbXCJrbXNpXCJdIiwidmVyIjoiRXhjaGFuZ2UuQ2FsbGJhY2suVjEiLCJhcHBjdHhzZW5kZXIiOiJPd2FEb3dubG9hZEA5OGIwMzVmZi1iMTIxLTQ1OGItYTNmMC0zMjM1NGRiMWI3ODEiLCJpc3NyaW5nIjoiU0lQIiwiYXBwY3R4Ijoie1wibXNleGNocHJvdFwiOlwib3dhXCIsXCJwdWlkXCI6XCIxMTUzNzY1OTMyMzQ4MzE1MTQ3XCIsXCJzY29wZVwiOlwiT3dhRG93bmxvYWRcIixcIm9pZFwiOlwiYjU1MGNmY2EtYjZhYS00NmFkLWFlYjAtZTllNjIyYTMyOTE2XCIsXCJwcmltYXJ5c2lkXCI6XCJTLTEtNS0yMS0zNjk5NTUyNDA4LTIxNDA2MTAxMy0yMzI0NTA4MTctMTMxMDk3OTRcIn0iLCJuYmYiOjE2NzUzMzY0ODQsImV4cCI6MTY3NTMzNzA4NCwiaXNzIjoiMDAwMDAwMDItMDAwMC0wZmYxLWNlMDAtMDAwMDAwMDAwMDAwQDk4YjAzNWZmLWIxMjEtNDU4Yi1hM2YwLTMyMzU0ZGIxYjc4MSIsImF1ZCI6IjAwMDAwMDAyLTAwMDAtMGZmMS1jZTAwLTAwMDAwMDAwMDAwMC9hdHRhY2htZW50cy5vZmZpY2UubmV0QDk4YjAzNWZmLWIxMjEtNDU4Yi1hM2YwLTMyMzU0ZGIxYjc4MSIsImhhcHAiOiJvd2EifQ.vi3s1cwR0sp_nHT4VSl7JBkFmYFEkdHjs7qh4RR6jtmY3jACh_PZcqdjzjOaw08wBcBzvZyPk62y8OZTDCn5GWtaOWEpbQgRsS49LzVEATJ-XqUpDABaS6vQb-3jfpo9L2AKzdZ_P8aTvhgihtoijrBwqE-FaZTaXnOGft2-qcrS7ISDUqTnTMfJRBuIoFqv5eLwMXC-OAFBqZbsCAYcYEZ6VFdu-GD8f4oaK90Pwr4bMT_yGjdtTp0bVM7I9Sl-zLm8-7rYDE_sXRklLZPkMvtQtChZ1LC4hrVQIyXeFF9fyiyeu2E4PAzaQzNc9jMkvS2AlhY7TbpRGpE5Az1iYg&X-OWA-CANARY=bF9w9Ol8Nkmp9r29KcE7SrCyhVAPBdsYVieOrdUWt0bGur9Y-jGXtOaeLqKdFyZZeIjFVZ4E8_I.&owa=outlook.office.com&scriptVer=20230120008.13&animation=true!""\', ""Comment 7: \'Yes\'"", ""Comment 8: \'At this point. We have such a case that if the total value is greater than 0"", \'Comment 9: we display inscription Total door u te betalen EUR + total value multipliedby (-1),in the second case\', \'Comment 10: if the value is lower\', ""Comment 11: we display the inscription Total aan u overgemaakt EUR + total valueDo we need to remove this functionality and just showTotal door u te betalen EUR +total value\'"", ""Comment 12: \'Yes indeed"", ""Comment 13: we would like to see a positive number in both cases.\'"", ""Comment 14: \'We have made changes on test database after confirm that its ok"", ""Comment 15: we gonna upload it on production.\'"", ""Comment 16: \'It looks OK"", ""Comment 17: please move it to Production.\'"", ""Comment 18: \'Moved to production database.\'"", ""Comment 19: \'Tekst na podsumowaniu wydruku saldo to pay powinien być tekst taki jak był wcześniej w zależności od tego czy była to wartość większa czy mniejsza niż 0"", ""Comment 20: a sama wartość liczbowa powinna być zawsze ze znakiem plus.\']""]\nRelated Issues:\n[\'DGS-8326\']\n\n### End'}"
574,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8458\n\n### Instruction:\nCan you re-open round from customer 00129 Bartels Wintelre (round 1)? It is already archived, but I have a correction SR to be booked. \r\n\r\nS2P state is Entry. \r\n\r\nRound ID is 30372. \n\n### Response:\n[""Comment 1: [\'Round is open again in Anja Verdam inbox.\']""]\nRelated Issues:\n[]\n\n### End'}"
575,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8457\n\n### Instruction:\nNew user account: Daan Aalbers\r\n\r\nBusiness Office / Administrator. Access to Nicole Inbox.\n\n### Response:\n[""Comment 1: [\'Account created.\']""]\nRelated Issues:\n[]\n\n### End'}"
576,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8456\n\n### Instruction:\nWhen the full number on a PI created from a SR is changed somehow it changes the full number but not the round number. \r\n\n\n### Response:\n[""Comment 1: [\'!image!!image-1!\'"", ""Comment 2: \'We fixed this issue in a test environment. In the DGS-8318 Round number of removed round - JIRA Kotrak S.A.you will find a description of the situation"", ""Comment 3: we are still waiting for confirmation. We have added an action that calculates round numbers on a round and updates all rounds related to a given customer.\'"", ""Comment 4: \'I am not sure what you need from us...\'"", \'Comment 5: ""In task [https://helpdesk.kotrak.com/servicedesk/customer/portal/56/DGS-8318]it\\\'s fixed and it\\\'s on test database. After tests and confirmation that it works properly in DGS-8318 we can close this task also.""\', ""Comment 6: \'DGS-8318 is approved.\']""]\nRelated Issues:\n[]\n\n### End'}"
577,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8455\n\n### Instruction:\nHello,\r\n\r\nI got a question from the business about wrong business partner data in DH CDN: I checked and didn\'t see a problem, but as you can see in both screenshots: There is a difference in the data presented between two users: How can this be solved? I suspect it being some caching issue or something but don\'t know how to solve\n\n### Response:\n[""Comment 1: [\'!afbeelding!!afbeelding-1!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'There is an difference in customer data between English and Dutch languages!image-2023-02-02-10-35-11-039.png!!image-2023-02-02-10-36-51-514.png!Data shown by DH CDN depends on Language you choose when log into application!image-2023-02-02-10-38-17-496.png!Please"", ""Comment 4: let me know if the answer is sufficient for you. Do you expect any additional actions from us regarding this issue? Can we close this ticket?\'"", \'Comment 5: ""How it that possible? The display of data shouldn\\\'t depend on language setting?? Sorry but this isn;t a solution to the problem""\', ""Comment 6: \'Adress data for customers (business parners) can be translated in DH CDN depending on choosen language. If data for selected language is gray then it came from ERPXL. If this data for choosen language is black then translation was created in DH CDN and can be modified by user.This is standard functionality provided by DH CDN.There is no tranlation data for customer (business parner) information in ERP XL.Please"", ""Comment 7: let me know if the answer is sufficient for you.\'"", ""Comment 8: \'Oke"", \'Comment 9: so to solve this\', ""Comment 10: I need to add translation? How to do this?\'"", ""Comment 11: \'Hello: How to fix this?\'"", ""Comment 12: \'After You log into DH CDN application and open selected business card information card!image-2023-02-03-08-05-09-856.png!You will have an opton to change language for translation!image-2023-02-03-08-06-06-719.png!As You can see in this case all data in usiness partner card are black... when there was english chosen tgose data were gray!image-2023-02-03-08-07-30-259.png!You can remove this translation using remove option!image-2023-02-03-08-08-06-043.png!or change it and save the changes using save option!image-2023-02-03-08-08-42-471.png!Please"", ""Comment 13: let me know if the answer is sufficient for you.\'"", \'Comment 14: ""I try to remove it\', \'Comment 15: but after save and re-opening the business partner\', \'Comment 16: it\\\'s still there""\', ""Comment 17: \'can you trry?\'"", ""Comment 18: \'Data for Dutch translation should be ok right now please verify.!image-2023-02-03-10-42-18-829.png!\'"", ""Comment 19: \'Yes it is oke now"", ""Comment 20: I figured out how to adjust. Thanks\']""]\nRelated Issues:\n[]\n\n### End'}"
578,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8454\n\n### Instruction:\nHello,\r\n\r\nShipping Notice L000122318 isn\'t arriving at DHP Utrecht. It is in DHC, but somehow it is not coming through to the plant. This trip needs to departure today, so it is urgent. \r\nHope you can find the reason. \n\n### Response:\n[""Comment 1: [\'Hello,We kindly inform you that wecurrentlyare processing another Priority1 task.We will revert to processing your task as soon as possible.Regards\'"", ""Comment 2: \'Hi Piotr"", ""Comment 3: the truck needs to leave within one hour. Please assist\'"", ""Comment 4: \'i am checking i will let you know.\'"", ""Comment 5: \' !screenshot-1! \'"", ""Comment 6: \'Related order is blocked in DHC SO000062704"", ""Comment 7: please  resent this order.\'"", ""Comment 8: \'I have exported this order again. Please check? \'"", ""Comment 9: \'Yes"", ""Comment 10:  !screenshot-2! I can see SN now in DHP.\'"", ""Comment 11: \'Great! Thanks a lot!\'"", ""Comment 12: \'You are welcome.\']""]\nRelated Issues:\n[]\n\n### End'}"
579,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8453\n\n### Instruction:\nWhen i put in description in the description this doesn\'t come on the invoice. Only the code name comes on the invoice. See appendix.\n\n### Response:\n[""Comment 1: [\'!3v bv 1.PNG|thumbnail!!3v bv.PNG|thumbnail!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 3: ""Hello,Invoice printout doesn\\\'t come from Intense\', \'Comment 4: then we can\\\'t do this antyhing with invoice printout.Is this invoice printed from Milas or other system? I think there should be some changes in system where the invoice is printing.Regards""\', \'Comment 5: ""It\\\'s a topic related to Milas\', \'Comment 6: so I close the task.!image-2023-02-15-13-26-47-563.png!""]\']\nRelated Issues:\n[]\n\n### End'}"
580,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8452\n\n### Instruction:\nHi, \r\n\r\nWhen I close JO 67/23/AY, costing for bulk code is wrong. While I check the raw material usage, raw material cost distribution is not equally. The things is not one or two raw materials. There is a lot. I do raise as P1 due to this JO in Jan 2023 and now we are closing month end. \n\n### Response:\n[""Comment 1: [\'!image!!image-1!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'I have a problem with logging in"", ""Comment 4: can you release license for XL?Module Workstation license is not accessible. Program session will be blocked.\'"", ""Comment 5: \'We are doing now. Please try again\'"", ""Comment 6: \'it works thanks\'"", ""Comment 7: \'please exit the documents related to this job order !screenshot-1! "", ""Comment 8: thank you.\'"", ""Comment 9: \'Already exit\'"", ""Comment 10: \'The solution is to unpost the related documents for the problematic codes in relation to the delivery. !screenshot-2! And the execution of the cost repair procedure for the delivery.The problem is due to the incorrect value of the cost which e.g. for 1113050 should be 709697,43 with price 1340 and the cost itself comes out that much.\'"", ""Comment 11: \'klient wybrał opcję KK i poprawy dokumentu IR-{code:java}select TrE_KsiegowaNetto,TrE_Pozycja,* from cdn.TraElem where Tre_GIDTyp=1616 AND Tre_GIDNumer=2574917 and TrE_Pozycja in(2,6,7,8,9,10,11,18,19,20,21,22,23,24)select TrS_KosztKsiegowy,TrS_GIDLp,* from cdn.traselem where Trs_GIDTyp=1616 AND Trs_GIDNumer=2574917  and TrS_GIDLp in(2,6,7,8,9,10,11,18,19,20,21,22,23,24){code}Poprawa wartości dla dokumentu jak wyżej i wygenerowanie dokumentów KK dla pozycji.\'"", \'Comment 12: ""Please verify\', \'Comment 13: CC\\\'s documents  have been generated: !screenshot-3! Correction for RW+ also after closed JO. !screenshot-4! ""\', ""Comment 14: \'We have been fixed all the related documents. You can close this ticket. \'"", ""Comment 15: \'Thank you for confirmation.\']""]\nRelated Issues:\n[]\n\n### End'}"
581,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8451\n\n### Instruction:\nIn he financial statement van Odink stand none document nr. under feed.\r\nCan you add this?\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,\\\\r\\\\rWe are investigating your issue. We will inform you about the solution as soon as possible.\\\\r\\\\rRegards\\\\r\\\\r\'"", \'Comment 3: ""In addition. There are Document numbers for all these postings in the system\', \'Comment 4: however they don\\\'t appear on the printout.""\', ""Comment 5: \'We fixed it.!image-2023-02-02-10-24-14-529.png!\']""]\nRelated Issues:\n[]\n\n### End'}"
582,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8450\n\n### Instruction:\nWe have problem in stock for item SUR7462-P-MD-S25, 0871141222007, produced 8695kg and was used 8695kg, but we still have 1000kg in stock. We checked on stock fisically and we don\'t have item anymore and any stocktaking was done for the item. \r\n\r\nCould you check why we still have stock for this item if was loaded?\r\n\r\nThank you.\n\n### Response:\n[\'Comment 1: ["" !screenshot-1! {code:java}SELECT created,event,EventType,Username  FROM [DHPlantProdBusinessLogicEvents].[dbo].[ProductionLots]  where AggregateId=\\\'8F626584-F9D7-4354-9239-FEC19B8D0FE7\\\'   order by created    SELECT TOP (1000) [Id]      ,[Created]      ,[AggregateType]      ,[AggregateId]      ,[Event]      ,[EventType]      ,[UserId]      ,[UserName]      ,[CorrelationId]  FROM [DHPlantStockBusinessLogicEvents].[dbo].[StockUnits]  where AggregateId=\\\'8B7C9DA6-A0D6-4856-8109-7D94C9CDC3D5\\\'  order by Created desc       select *  FROM [DHPlantStockBusinessLogicMain].[dbo].[StockUnits]  where DeliveryId=\\\'E78D4B86-E871-4EF0-AED7-B4838D90A531\\\' select *  FROM [DHPlantStockBusinessLogicMain].[dbo].[Deliveries]  where SourceDocumentId=\\\'8F626584-F9D7-4354-9239-FEC19B8D0FE7\\\'   select *  FROM [DHPlantStockBusinessLogicMain].[dbo].[ProductionLots]  where LotNumber=\\\'0871141222007\\\'{code}!image-2023-02-03-09-29-57-998! !image-2023-02-03-09-30-14-753!""\', ""Comment 2: \'Stand up - ustalenia.\\\\r\'"", ""Comment 3: \'!ByCorrelationId! [^DGS-8450_queries.sql] !ProductionLotQuantityChangedEvent! !StockUnitQuantityChangedEvent! !StockUnitReleases!\'"", \'Comment 4: ""Przyczyną problemu jest równoległa obsługa w serwisie StockEngine dwóch zdarzeń dotyczących tego samego StockUnit\\\'a:1. rejestracja przyjęcia pakowanego z produkcji przez użytkownika (obsługa żądania API z aplikacji Web) - CorrelationId =7BAED985-27A5-4A0A-89FF-3D64BE0046F12. rejestracja kolejnego dozowania do produkcji przez PCS (obsługa zdarzenia z serwisu PCS) - CorrelationId = B0029C71-D2F0-492C-860D-F3307801CFB7Oba procesy pobrały StockUnita z ilością3037.598 kg.Przyjęcie palety powinno zmniejszyć stan o 1000 kg.Dozowanie powinno zwiększyć stan produkcji o 36,5 kg.Po wykonaniu obu operacji stan powinien wynosić 2074.098 kg.Ponieważ procesy wykonywały się równolegle\', \'Comment 5: drugi proces nadpisał zmiany wykonane przez pierwszy proces i stan wynosił3074.098 kg.W taki sposób powstało nadmiarowe 1000 kg stanu.Rozwiązaniem problemu mogłoby być zaimplementowanie obsługi konkurencyjności przy zapisie agregatu StockUnit\\\'a.!image-2023-02-21-15-15-08-692.png!""\', ""Comment 6: \'[~tomasz.nojek@kotrak.com] dzięki!\'"", ""Comment 7: \'[~psilva@deheus.com]The reason for this error in quantity was parallel processing both of WO(IP) and registration of dosing by the PCS system. Those two activities were performed in the same second.The best way to solve this problem is to introduce concurrency in DHP both during the registration of information from PCS and performing intake from production on WO(IP).I raised the GDC-849 to implement this change in order to avoid such issues in the future"", ""Comment 8: I will discuss it with Theo. Please follow the GDC ticket in order to by updated on the current status of the solution.\'"", ""Comment 9: \'Hello"", ""Comment 10: as it was written in the last comment GDC has been created GDC-849.This issue has been closed.\']""]\nRelated Issues:\n[\'DGS-8380\', \'DGS-8715\']\n\n### End'}"
583,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8449\n\n### Instruction:\nPlease re-open round B002601/0010/0001\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 2: ""Hello,It\\\'s Active right now.Regards""]\']\nRelated Issues:\n[]\n\n### End'}"
584,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8448\n\n### Instruction:\nI notice that I can\'t see Matteo Minnen\'s inbox and he can\'t see mine. For Koen Huibers\' inbox this is already (and he can already see Matteo\'s). Can you add this for me?\r\n\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 2: ""I added Matteo\\\'s inbox to Koen and steffen""]\']\nRelated Issues:\n[]\n\n### End'}"
585,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8447\n\n### Instruction:\nPlease help to check this case and solving in Hau Giang Plant -0434.\r\n\r\nPLR 4341180123042 could not be found in the Production Report module . But release to stock with stock unit status In progress . Please check and clear this stock unit . Thank u.\r\n\n\n### Response:\n[""Comment 1: [\'!image-1!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'!image-2023-02-01-10-00-41-438.png!!image-2023-02-01-10-00-55-483.png!\'"", \'Comment 4: ""Hello,How is it possible that stock unit has been created from source document that do not exist? Wasn\\\'t this PLR deleted?Please\', \'Comment 5: try to do inventory on this stock unit and let us know.Regards""\', \'Comment 6: ""Hi Aleksandra Przybyłek .That\\\'s right. Maybe the user deleted this PLR . Please help clear this stock unit . Thank u.""\', \'Comment 7: ""{code:java}UPDATE DSET Status = 2\', \'Comment 8: Quantity = 0\', \'Comment 9: ExpiryDate = GETDATE()FROM DHPlantStockBusinessLogicMain.dbo.Deliveries DLEFT JOIN DHPlantStockBusinessLogicMain.dbo.StockUnits S ON S.DeliveryId = D.IdWHERE D.SourceDocumentId IN (\\\'8F261A64-6EE4-4823-AEA3-0426C01090A8\\\')UPDATE SSET Quantity=0,Quantityonhand = 0,logisticstatus=8FROM DHPlantStockBusinessLogicMain.dbo.Deliveries DLEFT JOIN DHPlantStockBusinessLogicMain.dbo.StockUnits S ON S.DeliveryId = D.IdWHERE D.SourceDocumentId IN (\\\'8F261A64-6EE4-4823-AEA3-0426C01090A8\\\'){code}""\', ""Comment 10: \'Hi,Stock and deliveries have been updated.Please"", ""Comment 11: verify.Regards\'"", ""Comment 12: \'Thanks you . You can do close this ticket.\']""]\nRelated Issues:\n[]\n\n### End'}"
586,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8446\n\n### Instruction:\nplease set ID 92117 back to entry\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'This is the wrong number; please set Srbe/1757 back to entry\'"", ""Comment 3: \'Hello,SRBe/1757 is now in Entry again.Regards\']""]\nRelated Issues:\n[]\n\n### End'}"
587,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8445\n\n### Instruction:\nGoodmorning,\r\n\r\nplease, would you create an openings balance for item: 303921-Z20 with a quantity of 10 kg and an openings balance for item: 087240-Z20 with also a quantity of 10 kg. Both items on plant Andel.\r\n\r\nThanks for support,\r\n\r\nKind regards,\r\n\r\nGerard Geerts\r\n \n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Dear Gerard,Opening balance for item087240-Z20 has been created. However"", ""Comment 3: there is no item like303921-Z20 in database. Please create item and let me know to process further.Regards!image-2023-02-01-12-19-53-594.png!\'"", ""Comment 4: \'Dear Aleksandra,sorry about my late reaction on this serviceticket.About the missing item"", ""Comment 5: I asked the person whose responsible for this.After that I asked you to create an openings balance.Regards,Gerard\'"", ""Comment 6: \'Dear Aleksandra,it should be an openings balance for item: 303921-Z20 Geurts on plant Andel.Regards,Gerard \'"", ""Comment 7: \'Dear Gerard,But there is still not such item in DB. You need to create it in ERP and send do DHP"", ""Comment 8: then I could create opening balance for this itemRegards!image-2023-02-03-07-32-39-369.png!\'"", ""Comment 9: \'The same in DHC:!image-2023-02-03-07-41-30-462.png!\'"", ""Comment 10: \'Hello Gerard,Any feedback? I can see this item has been sent to DHC. Should we create an opening balance for item303921-Z20?Regards\'"", ""Comment 11: \'Good morning Aleksandra,the item is also available in DHP.One moment"", ""Comment 12: i will aksed my collegue.Kind regards,Gerard\'"", ""Comment 13: \'Hello Alexandra,Please"", ""Comment 14: create an opningsbalance with 10 kg for itemcode: 303921-Z20-Geurts on plant Andel? Regards,Gerard!image!\'"", ""Comment 15: \'Dear Gerard,Should it be pallet or bulk? As in Stock Units there are both with ending:-Z20-Geurts!image-2023-02-22-17-20-49-445.png!Regards\'"", ""Comment 16: \'Goodmorning Aleksandra,The printscreen shows not the right item?It should be the item: 303921-Z20-Geurts.Regards,Gerard\'"", ""Comment 17: \'Good afternoon Gerard,My question was what settlement type shoud be defined to303921-Z20-Geurts.: bulk or pallet?Regards,Aleksandra\'"", \'Comment 18: \\\'Hello Aleksandra,""pallet"" please.Regards,Gerard\\\'\', ""Comment 19: \'Dear Gerard,The second Opening Balance is ready.!image-2023-02-23-14-58-08-263.png!Please"", ""Comment 20: verify.Regards,Aleksandra\'"", \'Comment 21: ""Dear Aleksandra,Thanks for support.Verify is done. It\\\'s oké!Please close this service ticket?Have a nice evening.Kind regards,Gerard""\', ""Comment 22: \'Thank you. The same to you"", \'Comment 23: Gerard\', ""Comment 24: have a nice eveningKind Regards\']""]\nRelated Issues:\n[]\n\n### End'}"
588,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8444\n\n### Instruction:\nPlease check VT-619/1/23: Quantities are consumed on item history, but still I cannot close VT due to missing stock. \n\n### Response:\n[""Comment 1: [\'!afbeelding!!afbeelding-1!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'{code:java}Cannot complete bulk when requested quantity greater than reserved quantity event automatic stocktaking is generated. -> CannotCompleteBulkWhenRequestedQuantityGraterThanReservedQuantityEvenAutomaticStocktakingIsGeneratedMessage{code}!image-2023-02-01-14-40-57-943!\'"", ""Comment 4: \'I forced a status change for VT please check.Are there other cases like this or is it an incident?\'"", ""Comment 5: \'It seems like an incident. thanks for solving. You can close the issue\']""]\nRelated Issues:\n[]\n\n### End'}"
589,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8443\n\n### Instruction:\nHello, \r\n\r\nlot report 0061270123041 is in status \'in progress\'. But there are two batches missing. I found those in the APIrequest log, but when I try to reprocess those, I got the message that the lot is already finished. The 2 missing batchreport xmls are added to the ticket. Can you investigate and make sure these are registered correctly? because produced quantity is not send to ERP and is leading to problems.\n\n### Response:\n[""Comment 1: [\'[^batch 923265.xml] _(10 kB)_[^last batch 923265.xml] _(0,7 kB)_\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'*STOCK - 24 ELEMENTY*!image-2023-02-01-13-59-43-276.png!!image-2023-02-01-14-00-01-688.png!\'"", ""Comment 4: \'*PROD - 24 ELELENTY**!image-2023-02-01-14-01-07-721.png!*!image-2023-02-01-14-03-11-960.png!\'"", ""Comment 5: \'*PCS - 24 ELEMENTY**!image-2023-02-01-14-04-45-160.png!**!image-2023-02-01-14-05-40-804.png!*\'"", ""Comment 6: \'PCS QUANTITIES!image-2023-02-01-14-12-06-295.png!\'"", ""Comment 7: \'W PCS ma status finished a w Prod in progress\'"", \'Comment 8: \\\'Log z modułu Stock:{code:java}2023-01-27 16:04:48 (6a6f60a6-8463-4cfc-8fe3-fc95f785728d/Plant.Stock.BusinessLogic/DHVD01AP181/13608/12) [Error] Kotrak.Integration.IntegrationPluginCommon.IntercontextCommunication.Inbound.InboundIntercontextErrorHandler - Error during handling message of type ""Plant.PCS.BusinessLogic.DomainAbstractions.ProductionLots.ProductionBatchReportRegisteredEvent""\', ""Comment 9: retry no 1Kotrak.Common.Application.Exceptions.BusinessLogicException: Production lot with id 2c1d1b84-8cc8-4c2d-9f44-c436d8c9c73a was not found ---> Kotrak.Common.Application.Exceptions.BusinessLogicException: ProductionLotNotFoundMessage   at Plant.Stock.BusinessLogic.Application.ProductionLots.ProductionLotService.RegisterRawMaterialsUsage(RegisterRawMaterialsUsageActionData data) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Application\\\\\\\\ProductionLots\\\\\\\\ProductionLotService.cs:line 0   at Plant.Stock.BusinessLogic.Application.ProductionLots.CommandHandlers.RegisterBatchReportCommandHandler.Handle(RegisterBatchReportCommand command) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Application\\\\\\\\ProductionLots\\\\\\\\CommandHandlers\\\\\\\\RegisterBatchReportCommandHandler.cs:line 26   at Kotrak.Common.Infrastructure.Commands.CommandEnvironment.Run[TCommand](TCommand command)   at Kotrak.Common.Infrastructure.Commands.Decorators.IntercontextEventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command)   at Kotrak.Common.Infrastructure.Commands.Decorators.EventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command)   at Kotrak.Common.Infrastructure.Commands.Decorators.ValidationCommandEnvironmentDecorator.Run[TCommand](TCommand command)   at Castle.DynamicProxy.AbstractInvocation.Proceed()   at Kotrak.Common.Infrastructure.Interceptors.LoggingInterceptor`1.Intercept(IInvocation invocation)   at Castle.DynamicProxy.AbstractInvocation.Proceed()   at Kotrak.Common.Infrastructure.Commands.Decorators.HistoryGateDecorator.Dispatch[TCommand](TCommand command)   at Kotrak.Integration.IntegrationPluginCommon.IntercontextCommunication.Inbound.IntercontextInboundHandler`2.Handle(InternalStorageDto message)   --- End of inner exception stack trace ---{code}\'"", ""Comment 10: \'Logi z Proda z mniej więcej tej godziny{code:java}2023-01-27 16:00:24 (/Plant.Prod.BusinessLogic/DHVD01AP181/6224/8) [Error] Plant.Prod.BusinessLogic.Infrastructure.Tasks.TryConfirmProductionLotTask - An error occurred while trying to confirm automatically production lot with id [38bcbd76-a671-4926-b7cb-facbaa6f55ec].Plant.Prod.BusinessLogic.DomainAbstractions.ProductionLots.DomainExceptions.ProductionLotConfirmException: Validation failed: -- ProductionLotQuantityIsNegativeOrZeroMessage   at Plant.Prod.BusinessLogic.Domain.ProductionLots.ConfirmProductionLotDomainService.ValidateConfirmation(ProductionLot productionLot"", \'Comment 11: ConfirmProductionLotActionData data) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Domain\\\\\\\\ProductionLots\\\\\\\\ConfirmProductionLotDomainService.cs:line 111   at Plant.Prod.BusinessLogic.Domain.ProductionLots.ConfirmProductionLotDomainService.ConfirmProductionLotWithStockEngineApiCall(ProductionLot productionLot\', \'Comment 12: ConfirmProductionLotActionData data\', \'Comment 13: Func`3 stockEngineApiCall) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Domain\\\\\\\\ProductionLots\\\\\\\\ConfirmProductionLotDomainService.cs:line 123   at Plant.Prod.BusinessLogic.Application.ProductionLots.ProductionLotService.ConfirmProductionLotAutomatically(ConfirmProductionLotDto dto) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Application\\\\\\\\ProductionLots\\\\\\\\ProductionLotService.cs:line 371   at Kotrak.Common.Infrastructure.Commands.CommandEnvironment.Run[TCommand](TCommand command)   at Kotrak.Common.Infrastructure.Commands.Decorators.IntercontextEventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command)   at Kotrak.Common.Infrastructure.Commands.Decorators.EventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command)   at Kotrak.Common.Infrastructure.Commands.Decorators.ValidationCommandEnvironmentDecorator.Run[TCommand](TCommand command)   at Castle.DynamicProxy.AbstractInvocation.Proceed()   at Kotrak.Common.Infrastructure.Interceptors.LoggingInterceptor`1.Intercept(IInvocation invocation)   at Castle.DynamicProxy.AbstractInvocation.Proceed()   at Kotrak.Common.Infrastructure.Commands.Decorators.HistoryGateDecorator.Dispatch[TCommand](TCommand command)   at Plant.Prod.BusinessLogic.Infrastructure.Tasks.TryConfirmProductionLotTask.TryConfirmProductionLot(Guid productionLotId) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Infrastructure\\\\\\\\Tasks\\\\\\\\TryConfirmProductionLotTask.cs:line 1122023-01-27 16:14:48 (null/Plant.Prod.BusinessLogic/DHVD01AP181/6224/7) [Error] Kotrak.Common.Infrastructure.ICommandRunEnvironment - Error during Void Run[SynchronizeShippingNoticeCommand](Plant.Prod.BusinessLogic.Application.Interfaces.ShippingNotices.Commands.SynchronizeShippingNoticeCommand) methodKotrak.Common.Application.Exceptions.BusinessLogicException: Some order elements with keys (69a9e395-84b3-4d69-a814-a6e757445584\', \'Comment 14: 3)\', \'Comment 15: (69a9e395-84b3-4d69-a814-a6e757445584\', ""Comment 16: 1) were not found. ---> Kotrak.Common.Application.Exceptions.BusinessLogicException: ProductionOrderSomeOrderElementsWereNotFoundMessage   at Plant.Prod.BusinessLogic.Application.ShippingNotices.ShippingNoticeService.ThrowIfAnyOrderElementWasNotFound(IEnumerable`1 keys) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Application\\\\\\\\ShippingNotices\\\\\\\\ShippingNoticeService.cs:line 117   at Plant.Prod.BusinessLogic.Application.ShippingNotices.ShippingNoticeService.AssertReferences(ShippingNoticeData data) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Application\\\\\\\\ShippingNotices\\\\\\\\ShippingNoticeService.cs:line 88   at Plant.Prod.BusinessLogic.Application.ShippingNotices.ShippingNoticeService.Create(ShippingNoticeData data) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Application\\\\\\\\ShippingNotices\\\\\\\\ShippingNoticeService.cs:line 44   at Kotrak.Common.Infrastructure.Commands.CommandEnvironment.Run[TCommand](TCommand command)   at Kotrak.Common.Infrastructure.Commands.Decorators.IntercontextEventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command)   at Kotrak.Common.Infrastructure.Commands.Decorators.EventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command)   at Kotrak.Common.Infrastructure.Commands.Decorators.ValidationCommandEnvironmentDecorator.Run[TCommand](TCommand command)   at Castle.DynamicProxy.AbstractInvocation.Proceed()   at Kotrak.Common.Infrastructure.Interceptors.LoggingInterceptor`1.Intercept(IInvocation invocation)   --- End of inner exception stack trace ---{code}\'"", ""Comment 17: \'W intercontext nie ma śladu:!image-2023-02-06-11-45-38-264.png!!image-2023-02-06-11-45-54-305.png!\'"", \'Comment 18: \\\'h2. Przeanalizowałem dogłębnie temat i mam parę wniosków:{code:java}SELECT *  FROM [DHPlantPCSBusinessLogicIntercontext].[dbo].[Errors]   where CreateDate between \\\\\\\'2023-01-27 16:00:48.8833333\\\\\\\' and \\\\\\\'2023-01-27 17:30:48.8833333\\\\\\\' and Message like \\\\\\\'%prod%\\\\\\\'SELECT *  FROM [DHPlantStockBusinessLogicIntercontext].[dbo].[Errors]   where CreateDate between \\\\\\\'2023-01-27 16:00:48.8833333\\\\\\\' and \\\\\\\'2023-01-27 17:30:48.8833333\\\\\\\' and Message like \\\\\\\'%prod%\\\\\\\'SELECT *  FROM [DHPlantProdBusinessLogicIntercontext].[dbo].[Errors]   where CreateDate between \\\\\\\'2023-01-27 16:00:48.8833333\\\\\\\' and \\\\\\\'2023-01-27 17:30:48.8833333\\\\\\\' and Message like \\\\\\\'%prod%\\\\\\\'SELECT Created,EventType  FROM [DHPlantPCSBusinessLogicEvents].[dbo].[ProductionLots] p   where AggregateId = \\\\\\\'2C1D1B84-8CC8-4C2D-9F44-C436D8C9C73A\\\\\\\'  ORDER BY Created DESC  SELECT Created,EventType  FROM [DHPlantStockBusinessLogicEvents].[dbo].[ProductionLots] p   where AggregateId = \\\\\\\'2C1D1B84-8CC8-4C2D-9F44-C436D8C9C73A\\\\\\\'  ORDER BY Created DESCSELECT Created,EventType  FROM [DHPlantProdBusinessLogicEvents].[dbo].[ProductionLots] p   where AggregateId = \\\\\\\'2C1D1B84-8CC8-4C2D-9F44-C436D8C9C73A\\\\\\\'  ORDER BY Created DESC{code}Po eventach widać że Event:Plant.PCS.BusinessLogic.DomainAbstractions.ProductionLots.ProductionBatchReportRegisteredEventDla tego missing batcha (3 i 4) pojawił się *{color:#de350b}dopiero po około 1h19m opóźnienia.{color}**Batch numer dwa czas:2023-01-27 16:11:47.7615228**Batch numer trzy czas:2023-01-27 17:30:08.4554092**Batch numer cztery czas:2023-01-27 17:30:09.3331415**Finish production odrazu po bo 4 batch ma w message: ""Last batch =1"": 2023-01-27 17:30:10.0259866*W prodzie ostatni event to event z godziny:2023-01-27 16:11:48.0798563 Plant.Prod.BusinessLogic.DomainAbstractions.ProductionLots.DomainEvents.ProductionLotElementsChangedEventCzyli poleciał update na elementach zgodnie z tym co zostało wysłane w batchu numer dwa.!image-2023-02-24-11-15-14-278.png!To screen potwierdzający ową sytuację. *Te 3 wyniki to wyniki z 3 ostatnich selectów*.Co ciekawe w żadnej tabeli intercontextu (stock\', \'Comment 19: prod\', \'Comment 20: pcs) *nie mam żadnych errorów z tegowego czasu (tak samo jak szukam po pcslot albo po productionlotid)*.---------------------------------------------------------Przejdźmy zatem do dbo.WebApiRequestLog:!image-2023-02-24-11-17-21-409.png!Wszystkie batche które dostaliśmy z PCS-a zostały zaakceptowane - oprócz tych które próbował wysłać Thomas - te nie przeszły\', \'Comment 21: *gdyż ten Lot już jest finished z odpowiednią ilością w PCS*.Problem jest taki że ta ilość nie zgadza się z tym co mamy w Stocku i w Prod.Różnica jest jedynie o właśnie tego Batcha numer trzy:{code:java}<ProductionReportToERP xmlns:xsi=""http://www.w3.org/2001/XMLSchema-instance"">  <BatchReports>    <BatchReport>      <ProductionLineId>1</ProductionLineId>      <PcsLotId>923265</PcsLotId>      <PcsBatchId>2631381</PcsBatchId>      <RecipeId>30313</RecipeId>      <QuantityKg>6002.337</QuantityKg>      <StartBatchMixing>2023-01-27T15:40:24</StartBatchMixing>      <FinishBatchMixing>2023-01-27T16:12:22</FinishBatchMixing>      <IsBrokenBatch>false</IsBrokenBatch>      <IsLastBatch>false</IsLastBatch>      <LOTReportType>1</LOTReportType>      <ItemCode>163420</ItemCode>      <Ingredients>        <Ingredient>          <ItemCode>0112</ItemCode>          <Intakes>            <Intake>              <DeliveryId xsi:nil=""true"" />              <QuantityKg>17.926</QuantityKg>            </Intake>            <Intake>              <DeliveryId xsi:nil=""true"" />              <QuantityKg>29.694</QuantityKg>            </Intake>          </Intakes>        </Ingredient>        <Ingredient>          <ItemCode>0233</ItemCode>          <Intakes>            <Intake>              <DeliveryId xsi:nil=""true"" />              <QuantityKg>90.09</QuantityKg>            </Intake>          </Intakes>        </Ingredient>        <Ingredient>          <ItemCode>0153</ItemCode>          <Intakes>            <Intake>              <DeliveryId xsi:nil=""true"" />              <QuantityKg>119.2</QuantityKg>            </Intake>          </Intakes>        </Ingredient>        <Ingredient>          <ItemCode>0307</ItemCode>          <Intakes>            <Intake>              <DeliveryId xsi:nil=""true"" />              <QuantityKg>546</QuantityKg>            </Intake>          </Intakes>        </Ingredient>        <Ingredient>          <ItemCode>0010</ItemCode>          <Intakes>            <Intake>              <DeliveryId xsi:nil=""true"" />              <QuantityKg>179.1</QuantityKg>            </Intake>          </Intakes>        </Ingredient>        <Ingredient>          <ItemCode>0362</ItemCode>          <Intakes>            <Intake>              <DeliveryId xsi:nil=""true"" />              <QuantityKg>18.752</QuantityKg>            </Intake>            <Intake>              <DeliveryId xsi:nil=""true"" />              <QuantityKg>132.057</QuantityKg>            </Intake>            <Intake>              <DeliveryId xsi:nil=""true"" />              <QuantityKg>52.091</QuantityKg>            </Intake>          </Intakes>        </Ingredient>        <Ingredient>          <ItemCode>0356</ItemCode>          <Intakes>            <Intake>              <DeliveryId xsi:nil=""true"" />              <QuantityKg>6.594</QuantityKg>            </Intake>            <Intake>              <DeliveryId xsi:nil=""true"" />              <QuantityKg>203.906</QuantityKg>            </Intake>          </Intakes>        </Ingredient>        <Ingredient>          <ItemCode>0378</ItemCode>          <Intakes>            <Intake>              <DeliveryId xsi:nil=""true"" />              <QuantityKg>16.312</QuantityKg>            </Intake>            <Intake>              <DeliveryId xsi:nil=""true"" />              <QuantityKg>529.188</QuantityKg>            </Intake>          </Intakes>        </Ingredient>        <Ingredient>          <ItemCode>0041</ItemCode>          <Intakes>            <Intake>              <DeliveryId xsi:nil=""true"" />              <QuantityKg>360.104</QuantityKg>            </Intake>            <Intake>              <DeliveryId xsi:nil=""true"" />              <QuantityKg>981.996</QuantityKg>            </Intake>          </Intakes>        </Ingredient>        <Ingredient>          <ItemCode>0001</ItemCode>          <Intakes>            <Intake>              <DeliveryId xsi:nil=""true"" />              <QuantityKg>1451.2</QuantityKg>            </Intake>          </Intakes>        </Ingredient>        <Ingredient>          <ItemCode>0001</ItemCode>          <Intakes>            <Intake>              <DeliveryId xsi:nil=""true"" />              <QuantityKg>588.2</QuantityKg>            </Intake>          </Intakes>        </Ingredient>        <Ingredient>          <ItemCode>0642</ItemCode>          <Intakes>            <Intake>              <DeliveryId xsi:nil=""true"" />              <QuantityKg>6.176</QuantityKg>            </Intake>            <Intake>              <DeliveryId xsi:nil=""true"" />              <QuantityKg>13.621</QuantityKg>            </Intake>            <Intake>              <DeliveryId xsi:nil=""true"" />              <QuantityKg>26.672</QuantityKg>            </Intake>            <Intake>              <DeliveryId xsi:nil=""true"" />              <QuantityKg>55.289</QuantityKg>            </Intake>            <Intake>              <DeliveryId xsi:nil=""true"" />              <QuantityKg>109.843</QuantityKg>            </Intake>            <Intake>              <DeliveryId xsi:nil=""true"" />              <QuantityKg>211.28</QuantityKg>            </Intake>          </Intakes>        </Ingredient>        <Ingredient>          <ItemCode>0831</ItemCode>          <Intakes>            <Intake>              <DeliveryId xsi:nil=""true"" />              <QuantityKg>0.076</QuantityKg>            </Intake>            <Intake>              <DeliveryId xsi:nil=""true"" />              <QuantityKg>0.95</QuantityKg>            </Intake>            <Intake>              <DeliveryId xsi:nil=""true"" />              <QuantityKg>7.982</QuantityKg>            </Intake>          </Intakes>        </Ingredient>        <Ingredient>          <ItemCode>0631</ItemCode>          <Intakes>            <Intake>              <DeliveryId xsi:nil=""true"" />              <QuantityKg>6.002</QuantityKg>            </Intake>          </Intakes>        </Ingredient>        <Ingredient>          <ItemCode>0851</ItemCode>          <Intakes>            <Intake>              <DeliveryId xsi:nil=""true"" />              <QuantityKg>1.227</QuantityKg>            </Intake>          </Intakes>        </Ingredient>        <Ingredient>          <ItemCode>0684</ItemCode>          <Intakes>            <Intake>              <DeliveryId xsi:nil=""true"" />              <QuantityKg>0.088</QuantityKg>            </Intake>            <Intake>              <DeliveryId xsi:nil=""true"" />              <QuantityKg>0.376</QuantityKg>            </Intake>            <Intake>              <DeliveryId xsi:nil=""true"" />              <QuantityKg>2.895</QuantityKg>            </Intake>            <Intake>              <DeliveryId xsi:nil=""true"" />              <QuantityKg>9.259</QuantityKg>            </Intake>          </Intakes>        </Ingredient>        <Ingredient>          <ItemCode>0839</ItemCode>          <Intakes>            <Intake>              <DeliveryId xsi:nil=""true"" />              <QuantityKg>14.462</QuantityKg>            </Intake>          </Intakes>        </Ingredient>        <Ingredient>          <ItemCode>0672</ItemCode>          <Intakes>            <Intake>              <DeliveryId xsi:nil=""true"" />              <QuantityKg>6.009</QuantityKg>            </Intake>          </Intakes>        </Ingredient>        <Ingredient>          <ItemCode>0640</ItemCode>          <Intakes>            <Intake>              <DeliveryId xsi:nil=""true"" />              <QuantityKg>38.99</QuantityKg>            </Intake>          </Intakes>        </Ingredient>        <Ingredient>          <ItemCode>0718</ItemCode>          <Intakes>            <Intake>              <DeliveryId xsi:nil=""true"" />              <QuantityKg>0.025</QuantityKg>            </Intake>            <Intake>              <DeliveryId xsi:nil=""true"" />              <QuantityKg>0.124</QuantityKg>            </Intake>            <Intake>              <DeliveryId xsi:nil=""true"" />              <QuantityKg>0.534</QuantityKg>            </Intake>            <Intake>              <DeliveryId xsi:nil=""true"" />              <QuantityKg>4.869</QuantityKg>            </Intake>          </Intakes>        </Ingredient>        <Ingredient>          <ItemCode>0773</ItemCode>          <Intakes>            <Intake>              <DeliveryId xsi:nil=""true"" />              <QuantityKg>14.981</QuantityKg>            </Intake>          </Intakes>        </Ingredient>        <Ingredient>          <ItemCode>0845</ItemCode>          <Intakes>            <Intake>              <DeliveryId xsi:nil=""true"" />              <QuantityKg>0.19</QuantityKg>            </Intake>            <Intake>              <DeliveryId xsi:nil=""true"" />              <QuantityKg>3.81</QuantityKg>            </Intake>          </Intakes>        </Ingredient>        <Ingredient>          <ItemCode>0989</ItemCode>          <Intakes>            <Intake>              <DeliveryId xsi:nil=""true"" />              <QuantityKg>24</QuantityKg>            </Intake>          </Intakes>        </Ingredient>        <Ingredient>          <ItemCode>0195</ItemCode>          <Intakes>            <Intake>              <DeliveryId xsi:nil=""true"" />              <QuantityKg>3.54</QuantityKg>            </Intake>            <Intake>              <DeliveryId xsi:nil=""true"" />              <QuantityKg>12.916</QuantityKg>            </Intake>            <Intake>              <DeliveryId xsi:nil=""true"" />              <QuantityKg>30.643</QuantityKg>            </Intake>          </Intakes>        </Ingredient>        <Ingredient>          <ItemCode>0204</ItemCode>          <Intakes>            <Intake>              <DeliveryId xsi:nil=""true"" />              <QuantityKg>3.689</QuantityKg>            </Intake>            <Intake>              <DeliveryId xsi:nil=""true"" />              <QuantityKg>69.411</QuantityKg>            </Intake>          </Intakes>        </Ingredient>      </Ingredients>    </BatchReport>  </BatchReports></ProductionReportToERP>{code}*Który to w żaden sposób nie różni sie od pozostałych.*No i oczywiście o batcha numer cztery:{code:java}<ProductionReportToERP xmlns:xsi=""http://www.w3.org/2001/XMLSchema-instance"">  <BatchReports>    <BatchReport>      <ProductionLineId>1</ProductionLineId>      <PcsLotId>923265</PcsLotId>      <PcsBatchId>1</PcsBatchId>      <RecipeId>30313</RecipeId>      <QuantityKg>0.01</QuantityKg>      <StartBatchMixing>2023-01-27T16:13:33</StartBatchMixing>      <FinishBatchMixing>2023-01-27T16:13:33</FinishBatchMixing>      <IsBrokenBatch>false</IsBrokenBatch>      <IsLastBatch>true</IsLastBatch>      <LOTReportType>1</LOTReportType>      <ItemCode>163420</ItemCode>      <Ingredients />    </BatchReport>  </BatchReports></ProductionReportToERP>{code}Mam z tym tematem problem\', \'Comment 22: gdyż na początku myślałem że po prostu zmienie status w PCS i ponownie dośle te batche\', \'Comment 23: ale wtedy ta ilość quantity także podniesie się w PCS i będzie rozjazd pomiędzy tym co jest w PCS\', \'Comment 24: a tym co Prod/Stock (prawdopodobnie wgl messege nie doleci\', \'Comment 25: gdyż to quantity będzie mu się nie zgadzać i walidacja tego nie puści).*Obstawiam że po prostu że moduł PCS musiał być w tym momencie mega obciążony\', \'Comment 26: gdyż nie jest to normalne że event batcha wskakuje dopiero po 1h19m.*Tylko nie mam zielonego pojęcia dlaczego te dwa missing batche w żaden sposób nie poleciały do Prod/Stocka i to quantity sie nie zmieniło(?).Analizowałem też Event Viewera i nie widzę żadnych blockerów w tamtym okresie\', \'Comment 27: tylko informacje ale w zupełnie innym temacie.Request o pomoc(flag): [~maciej.dobrzanski@kotrak.com]\', \'Comment 28: [~tomasz.nojek@kotrak.com]*UPDATE:*{color:#4c9aff}*Wpadłem na pomysł żeby po prostu wysłać ten event z trzecim batchem na kolejki Prod i SE.*{color}{color:#4c9aff}*Powinno zupdejtować ilość w tych dwóch modułach\', ""Comment 29: no i jeszcze wysłać ten event Finishproduction i powinnien być w prodzie jako finished.*{color}\'"", ""Comment 30: \'ta dam!image-2023-02-24-13-28-58-935.png|width=1035,height=361!!image-2023-02-24-13-30-34-988.png!\'"", ""Comment 31: \'No i mówiłam już Gedeonowi"", ""Comment 32: że w Nijkerk to zaczyna być repetitive issuehttps://helpdesk.kotrak.com/browse/DGS-8604\'"", ""Comment 33: \'Hello any update? I have a new example: batch report is accepted according to pcsbusinesslogic table"", \'Comment 34: but not visible in DHP. if I try to resend xml\', \'Comment 35: there is a message that the lot report is finished\', \'Comment 36: MEssage:<ProductionReportToERP xmlns:xsi=""http://www.w3.org/2001/XMLSchema-instance""> <BatchReports> <BatchReport> <ProductionLineId>1</ProductionLineId> <PcsLotId>928417</PcsLotId> <PcsBatchId>2650039</PcsBatchId> <RecipeId>17894</RecipeId> <QuantityKg>9980</QuantityKg> <StartBatchMixing>2023-02-23T07:35:37</StartBatchMixing> <FinishBatchMixing>2023-02-23T10:48:49</FinishBatchMixing> <IsBrokenBatch>false</IsBrokenBatch> <IsLastBatch>false</IsLastBatch> <LOTReportType>1</LOTReportType> <ItemCode>169123-Z20</ItemCode> <Ingredients> <Ingredient> <ItemCode>169123</ItemCode> <Intakes> <Intake> <DeliveryId xsi:nil=""true"" /> <QuantityKg>5000.659</QuantityKg> </Intake> <Intake> <DeliveryId xsi:nil=""true"" /> <QuantityKg>4979.341</QuantityKg> </Intake> </Intakes> </Ingredient> </Ingredients> </BatchReport> </BatchReports></ProductionReportToERP>\\\'\', ""Comment 37: \'Hi Thomas,0061270123041 is confirmed now"", ""Comment 38: however we are investigating why this happened.Regards\'"", ""Comment 39: \'Dear Thomas,To confirm0061270123041 we needed to resend event to Prod and Stock module. We tried also to diagnose what caused the issue.For now"", \'Comment 40: we have spent 6,5 h in this task. In the mean time\', \'Comment 41: the same issue in the same plant - Nijkerk reoccured under:DGS-8604. As it seemed to be repetitive\', \'Comment 42: I suggest raising RCA task for this issue.Please\', ""Comment 43: let me know if you agree for RCA task or shall we investigate in current DGS-8443 task.Regards\'"", ""Comment 44: \'Agreed with RCA task\'"", ""Comment 45: \'Thank you. RCA task is underDGS-8686. Please"", ""Comment 46: confirm if you have access.\'"", ""Comment 47: \'I have\'"", ""Comment 48: \'Great. In that case I am closing this task.Regards\']""]\nRelated Issues:\n[\'DGS-8686\']\n\n### End'}"
590,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8442\n\n### Instruction:\nI cannot sort by delivery date on a financial statement\r\n\r\nI would like to be able to sort all the feed from old to nwe\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 3: ""Hello,We can do it globally for Financial statement printout. It means that always lines will be sorted from old to new by \\\'Delivery date\\\'.Should it be applied only in NAS sector and for section Feed or for all sections (Calves\', \'Comment 4: Feed\', \'Comment 5: Slaughtery\', \'Comment 6: Expenses)?!image-2023-02-02-10-38-04-884.png!""\', ""Comment 7: \'Yes please"", ""Comment 8: do it for all sectors in all categories.\'"", ""Comment 9: \'Done for all sectors for both database and all categories.\'"", ""Comment 10: \'Can be closed.\'"", ""Comment 11: \'We just created an FS and the delivery dates are all intertwined.It should be sorted on date"", ""Comment 12: now it is sorted only on the first number of the date.!image-1!\'"", \'Comment 13: ""FS printouts in all sectors have been changed\', \'Comment 14: now all lines in all categories are sorted by \\\'Delivery date\\\' asceding like on screen below.!image-2023-02-06-15-05-05-767.png!Done on test and production database.Regards""]\']\nRelated Issues:\n[]\n\n### End'}"
591,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8441\n\n### Instruction:\nWe need to migrate some missing AS/400 date for two LAS customers\n\n### Response:\n[""Comment 1: [\'[^AA - LAS_Migration_PURCHASEINVOICE_workfile_003651+006514.xlsx] _(140 kB)_[^AA - LAS_Migration_SALESINVOICE_workfile_003651+006514.xlsx] _(621 kB)_\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 3: ""[~mbovene@deheus.com],all lines have been migrated to Intense. You can feel free to check the data. I\\\'m waiting for your feedback.Best regards,Grzegorz""\', ""Comment 4: \'Done.\'"", \'Comment 5: ""Ok thank you for respone. I\\\'m closing the task.""]\']\nRelated Issues:\n[]\n\n### End'}"
592,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8440\n\n### Instruction:\nHi\r\nUrgent task from Wiola\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Proszę o wskazanie osoby dla której występuje problem"", ""Comment 4: oraz przykładowej listy płac\'"", ""Comment 5: \'!image-1!\'"", ""Comment 6: \'[^KUP.docx]\'"", ""Comment 7: \'W załączniku wyjaśnienia[^KUP.docx]\'"", ""Comment 8: \'Czy temat można uznać za zakończony?\'"", ""Comment 9: \'Myślę"", ""Comment 10: że możemy zamknąć.\']""]\nRelated Issues:\n[]\n\n### End'}"
593,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8439\n\n### Instruction:\nplease remove the documents attached becasue they have zero quantity and stopping us from progressing in certain processes\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'!image-2023-01-31-16-34-42-373.png!\'"", ""Comment 4: \'TrN_GIDNumer=437604,TrN_GIDNumer=412473-- spinacz elementów por\'"", ""Comment 5: \'select cdn.NazwaObiektu(trn_gidtyp,trn_gidnumer,1,2),* from cdn.tranag where trn_gidtyp=1497 and trn_trnrok=2022 and trn_stan in (0,1,2)\'"", ""Comment 6: \'select cdn.NazwaObiektu(trn_gidtyp,trn_gidnumer,1,2),trn_gidnumer,TrN_SpiNumer,TrN_ZwrNumer,trs_gidnumer,trs_spinumer,trs_spityp,trs_zwrnumer,trs_zwrtyp,* from cdn.tranag join cdn.traselem on trs_gidnumer=trn_gidnumerwhere (trn_gidtyp in (1497) and trn_trnrok=2022 and trn_stan in (0,1,2)) or trs_spinumer in (412217,412232,412241,367362,367361,367360,462425)\'"", ""Comment 7: \'Document was removed"", \'Comment 8: it looked like some strange ERP XL error\', ""Comment 9: I verified before if the dociment are not related to any other clip.Please verify and let me know if we may close the task.\'"", ""Comment 10: \'please close\']""]\nRelated Issues:\n[]\n\n### End'}"
594,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8438\n\n### Instruction:\nOrderChangedMessage: Id=1c42acd1-d8ea-428f-8f5a-606b79537f88 DocumentNo=\'SO000060938\' DocNumeratorYear=2023 DocNumeratorMonth=1 DocNumeratorNumber=12026 DocNumeratorSeries= OrderType=2\r\nValidation failed for one or more entities. See \'EntityValidationErrors\' property for more details.The validation error are: [Code - Value is required]\r\n\r\nThese are the details from the communication log. Can you please investigate and explain what is wrong?\r\n\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \' !screenshot-1!  !screenshot-2! Inny bez tego błedu nie pustą sekcję Silos !screenshot-3! \'"", ""Comment 3: \'Those orders with errors have the silos section filled in: !screenshot-4!  Can you check if these orders have the correct data sent from the erp?\'"", ""Comment 4: \'Hi Piotr"", \'Comment 5: thanks! I deleted the silo info in ERP for the order and the order is now in DHC. Not yet in DHP by the way. Can you check this as well\', ""Comment 6: or do I need to be more patient for this?\'"", \'Comment 7: ""In my opinion import of order shouldn\\\'t fail in DHC when there is no silo information.  But this I will discuss with Thomas Dankers and ask him to raise a GDC for it. For now my concern is that this order goes correctly to the plant""\', \'Comment 8: ""Ah\', \'Comment 9: the order is in DHP as well. I was not being impatient but didn\\\'t change my filter.You can close this request.""\', ""Comment 10: \'Thank you for confirmation.\']""]\nRelated Issues:\n[]\n\n### End'}"
595,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8437\n\n### Instruction:\nThis revenue does not come in financial statement\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 3: ""Hello,I see that is an issue because we\\\'re showing documents PI when Reference is filled. On this document field is empty.!image-2023-01-31-15-43-10-676.png!Why this field is empty? Is there any reason why this field is empty?For this case filling field \\\'Reference\\\' will resolve issue\', \'Comment 4: however there are some inaccuracies here between Round and Financial statement which we can also adjust.Please inform us about \\\'Reference\\\' on PI invoices.""\', ""Comment 5: \'Is there needed any work in this task or could we close the task?\'"", ""Comment 6: \'[~bgeytenbeek@deheus.com]could you confirm?\'"", ""Comment 7: \'L999999 has been filled in as a Reference.Confirmed that can be closed.\']""]\nRelated Issues:\n[\'DGS-8425\']\n\n### End'}"
596,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8436\n\n### Instruction:\nI get an error when archiving\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 3: ""Hello,Did you get any error message from Intense when you try to send document to \\\'Archive\\\'? If yes\', \'Comment 4: please attach a screen of message.Regards""\', ""Comment 5: \'Document is in archive state so you handled it"", ""Comment 6: can i close this task or you have any question?\'"", ""Comment 7: \'Could we close the task?\'"", ""Comment 8: \'Yes\']""]\nRelated Issues:\n[]\n\n### End'}"
597,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8435\n\n### Instruction:\nHi\r\nW tym tygodniu mamy już 2 przypadki, w których mamy rozbieżność na pozycjach vt w dhp i w dhc. Proszę o zbadanie sytuacji, bo my nic nie wyłapaliśmy.\r\n\r\nRafał Boniecki\n\n### Response:\n[""Comment 1: [\'analiza z dgsa:VT-282: RGM_parrentid 28283747 wydany dla dwóch VTE_id (915414,915377)VT-166: RGM_parrentid 28314514,28314511 wydany dla VT elementu 914924 ale powinien dla vte_id =914915 - różne między parrentid a paletą.Brakuje wtedy elementów w dhc .\'"", ""Comment 2: \'mamy akceptację na 4h analizy.\'"", ""Comment 3: \'zgodnie z rozmową.\'"", ""Comment 4: \'Zapytanie po retro o status zgłoszenia - o komentarz do taska.\'"", ""Comment 5: \'Hi"", ""Comment 6: any news?\'"", ""Comment 7: \'W Łomży jest tego kilka elementów najnowszy jest z 12.2022 vt-25452/12/2022Brakuje elementu 12!image-2023-03-24-15-11-14-991.png!Tutaj widać nieścisłość!image-2023-03-24-15-11-38-839.png!{code:java}SELECT rgm_id,RgM_VtEIdRelease,RgM_ParrentId,RgM_Quantity  FROM [DHP_Lomza].[dbo].[RegisterMappings]  where RgM_Id in(28175975,28175971) or RgM_VtEIdRelease=911506or RgM_ParrentId in(28175975,28175971)-----SELECT sum(RgM_Quantity)  FROM [DHP_Lomza].[dbo].[RegisterMappings]  where RgM_VtEIdRelease=911506and RgM_ParrentId in(28175975)-----SELECT sum(RgM_Quantity)  FROM [DHP_Lomza].[dbo].[RegisterMappings]  where RgM_ParrentId in(28175971){code}\'"", ""Comment 8: \'Łęczyca - SQL01-20vt:6179/3/20236631/4/2023elementy id: ilość542573 1,2543924 0,45\'"", ""Comment 9: \'Hello"", ""Comment 10: can we get a copy of the database Łęczyca - SQL01-20 from the ssms level for verification the problem described in the task?\'"", ""Comment 11: \'Hi"", ""Comment 12: we decided to close that task. We consider it again when problem will return...\'"", ""Comment 13: \'According to information ticket has been closed.\']""]\nRelated Issues:\n[\'DGS-8323\']\n\n### End'}"
598,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8434\n\n### Instruction:\nWe have some productions not produced but we don\'t have option to cancel. \r\n\r\nSUR7546-P-MD 0871230123004\r\nSUR7546-P-MD 0871200123031\r\nSUR7546-P-MD 0871200123032\r\nSUR7546-P-MD 0871200123033\r\nSUR7546-P-MD 0871200123034\r\n\r\nCould you please cancel the productions?\r\n\r\nThank you\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 2: ""{code:java}  FROM [DHPlantProdBusinessLogicMain].[dbo].[ProductionLots] where LotNumber in(\\\'0871291222002\\\',\\\'0871230123004\\\',\\\'0871200123031\\\',\\\'0871200123032\\\',\\\'0871200123033\\\',\\\'0871200123034\\\'){code}status 3.""\', ""Comment 3: \'Documents have been cancelled.\'"", ""Comment 4: \'Could you please confirm if we can close this task?Regards\'"", ""Comment 5: \'Hello,We are closing this task as we haven’treceivedany replyfromyouforalong time. Regards\']""]\nRelated Issues:\n[]\n\n### End'}"
599,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8433\n\n### Instruction:\nThe report Weighbridge dispatch available in VT is duplicating the element. Could you check and fix it?\r\n\r\nThank you\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'The problem is for the all elements"", ""Comment 4: items and vt or it happend always?\'"", \'Comment 5: ""Hi Agnieszka,it\\\'s happening for all elements and all vts dispatch.""\', ""Comment 6: \'!image-2023-02-01-13-28-46-495.png!\'"", ""Comment 7: \'GetWeighBridgeNewPrintout-- tu sa elementy vt.GetWeighBridgePrintout\'"", ""Comment 8: \'!image-2023-02-01-14-17-49-857.png!\'"", \'Comment 9: ""SELECT E.Id\', \'Comment 10: E.No\', \'Comment 11: NULL AS IssueDate\', \'Comment 12: R.SerialNumber\', \'Comment 13: R.WeightValue AS ResourceQuantity\', \'Comment 14: R.WeightUnit AS ResourceQuantityUnit\', \'Comment 15: R.ExpiryDate\', \'Comment 16: D.InternalSerialNumber\', \'Comment 17: D.CreatedDate\', \'Comment 18: NULL AS ForeignEAN\', \'Comment 19: NULL AS SourceDocumentNumber FROM dbo.VehicleTicketPackedDispatchElements E INNER JOIN dbo.VehicleTicketPackedDispatchElementResources R ON R.Id = E.Id AND R.No = E.No LEFT JOIN dbo.Deliveries D ON D.SerialNumber = R.SerialNumber WHERE E.Status = 10 AND R.IsCancelled = 0 and e.id=\\\'cb88b35b-f52c-4781-a9f1-2c1f3424e92b\\\'""\', \'Comment 20: ""[~marcin.kleszcz@kotrak.com] Problemem jest wiazanie do tabeli delivery poniewaz dla jednej serialnumber jest kilka deliveryid więc dlatego w tym przypadku wyniki się duplikują.Czy jest to standardowe i normlane działanie ? czy Brazylia cos zmieniła w procesie\', \'Comment 21: czy ta procedura jest zła?bo sama procedura jak patrzyłam i w Apu i w innej fabryce jest taka sama\', \'Comment 22: wtedy taka sytuacja z duplikacją pozycji występowała by częsciej\', \'Comment 23: procedura też nie ejst najnowsza.Pytanie czy tak zawsze robili że jeden serial number był przypisany do kilku deliveryid?Przykład dla tgo zgłoszenia vt 669/23 z apuSELECT E.Id\', \'Comment 24: E.No\', \'Comment 25: NULL AS IssueDate\', \'Comment 26: R.SerialNumber\', \'Comment 27: R.WeightValue AS ResourceQuantity\', \'Comment 28: R.WeightUnit AS ResourceQuantityUnit,R.ExpiryDate\', \'Comment 29: D.InternalSerialNumber\', \'Comment 30: D.CreatedDate\', \'Comment 31: NULL AS ForeignEAN\', ""Comment 32: NULL AS SourceDocumentNumber FROM dbo.VehicleTicketPackedDispatchElements E INNER JOIN dbo.VehicleTicketPackedDispatchElementResources R ON R.Id = E.Id AND R.No = E.No LEFT JOIN dbo.Deliveries D ON D.SerialNumber = R.SerialNumberWHERE E.Status = 10 AND R.IsCancelled = 0 and e.id=\'1E6686E6-0C73-4CCF-940A-6DF5DF515A36\'daje 32 wynikinp ten serialnumberd.SerialNumber=\'0882030223002\' pojawia sie 2 razy :!image-2023-02-15-07-30-17-836.png!naromiast wynik zapytania dla samej tabeliselect * from VehicleTicketPackedDispatchElementResources where id=\'1E6686E6-0C73-4CCF-940A-6DF5DF515A36\'!image-2023-02-15-07-31-38-280.png!select SerialNumber,* from dbo.Deliveries D where SerialNumber in (\'0881230123002\'"", ""Comment 33: \'0881250123013\'"", ""Comment 34: \'0881250123012\'"", ""Comment 35: \'0881191222020\'"", ""Comment 36: \'0881270123010\') order by 1select top 100 * from dbo.StockUnits where DeliveryId in (\'5204C239-1C6F-4760-8F92-8D44E95AF8CA\'"", ""Comment 37: \'B32C320E-E095-484D-9FB9-821C655C9D56\'"", \'Comment 38: \\\'B68AC030-7F37-48F3-9947-5EEB81B6A35D\\\')Pytanie czy takie rzeczy powinny się dziać!image-2023-02-02-13-16-27-474.png!!image-2023-02-15-07-30-17-836! !image-2023-02-15-07-31-38-280!""\', ""Comment 39: \'Hello,Could you please provide other vt with similar situation?\'"", ""Comment 40: \'[~marcin.kleszcz@kotrak.com]czy udało sie zweryfikowac czy działanie jest prawidlowe\'"", ""Comment 41: \'Good morning"", \'Comment 42: after our analysis\', \'Comment 43: it appears that the situation was due to the fact that to one serial number in this case was assigned several different deliveries. Neither the printout nor the procedure has been modified recently\', \'Comment 44: and the same procedure is used in other plants\', \'Comment 45: as you have not indicated more cases\', \'Comment 46: I close the notification\', \'Comment 47: if there is a new case\', \'Comment 48: or the need to continue work\', ""Comment 49: please create a new ticket and refer to this number.\']""]\nRelated Issues:\n[\'DGS-8556\']\n\n### End'}"
600,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8432\n\n### Instruction:\nPlease close both contracts below :\r\n\r\nItem : HCL\r\n\r\nPO-10/05/2019/RMP\r\nPO-4/06/2021/RMP\r\n\r\nComment user :\r\n\r\n I receive notifications when I want to close it, which I follow up, but then I receive new notifications. ( canceling Call offs etx )\r\n\r\n \n\n### Response:\n[""Comment 1: [\'!image!!image-1!\'"", ""Comment 2: \'10/05 ma element na 0 kg jeden :ZaN_GIDTyp=960 AND ZaN_GIDFirma=1015303 AND ZaN_GIDNumer=612!image-2023-01-30-17-53-33-485.png!\'"", ""Comment 3: \'na ipor jest wyprodukowane nawet wiecej :  !image-2023-01-30-17-54-48-144.png!TrN_GIDTyp=1490 AND TrN_GIDFirma=1015303 AND TrN_GIDNumer=32615\'"", ""Comment 4: \'2 różne magnumery na zaelem:select * from cdn.ZamElem where zae_gidnumer=612\'"", ""Comment 5: \'select * from cdn.ZamElem where zae_gidnumer=612select * from cdn.TraElem where tre_gidnumer=32615select * from cdn.tranag where trn_gidnumer=32615select * from cdn.ZamNag where ZaN_GIDNumer=612select * from cdn.traselem where trs_gidnumer=32615select * from cdn.Magazyny where mag_gidnumer in (2,8)\'"", ""Comment 6: \'zamowienie z czerwca 2021 pdobnieZaN_GIDTyp=960 AND ZaN_GIDFirma=1015303 AND ZaN_GIDNumer=12395select cdn.NazwaObiektu(trn_gidtyp,trn_gidnumer,1,2)"", \'Comment 7: * from cdn.tranag where TrN_ZaNNumer=12395select cdn.NazwaObiektu(trn_gidtyp,trn_gidnumer,1,2)\', ""Comment 8: * from cdn.tranag where TrN_ZaNNumer=612\'"", ""Comment 9: \'Hello for the orderPO-10/05/2019/RMP there is and POri document for more then 20250 kg"", \'Comment 10: it seems like the second position on order made some problems\', \'Comment 11: also it is very old order- maybe something were done unsually.The pori isPORI-27/05/2019/VIMP - so from what I can see this should be set to executed as the correct status.Did you wish to change it status\', ""Comment 12: did you need more changes for that PO and related elements send us informations.!image-2023-01-30-17-53-33-485.png!\'"", ""Comment 13: \'AboutPO-4/06/2021/RMP it is only confirmed ( with no realated POR"", ""Comment 14: nor PORI)did you wish to close it or to cancel it?After closing the order will get the status closed confirmed.What notification the operator got? Did it blocked him from operation?!image-2023-01-30-18-47-02-106.png!\'"", ""Comment 15: \'The contracts are indeed old and need to be closed / deleted.I can’t change it.I don’t exactly know the reasons why but they need to be closed in anyway. Met vriendelijke groeten"", ""Comment 16: with kind regardsFrank BoersmaSupport Inkoop en Logistiek !image-2!\'"", ""Comment 17: \'Hello,Requested POs are closed now. Please"", ""Comment 18: verify if this status is fine for you and if we can close this task.Regards\'"", ""Comment 19: \'I have asked the user for a conformation \'"", ""Comment 20: \'Waiting for your feedback then.Regards\'"", ""Comment 21: \'Hi,Any feedback?Regards\'"", ""Comment 22: \'Hi,Any feedback?Regards\'"", ""Comment 23: \'Ticket can be closed\']""]\nRelated Issues:\n[]\n\n### End'}"
601,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8431\n\n### Instruction:\nChainge main, target and payer customer off SO-76/10/2022/V and ESI-3/11/2022/vexp from 7727 to 0674\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!!image-1!\'"", ""Comment 2: \'Dear,According to the service agreement this task should be categorized as a service request.Kindly approve change of the type of this task.RegardsAgnieszka Januszewska\'"", ""Comment 3: \'see also DGS-8466\'"", ""Comment 4: \'Hi,We are closing this task as a duplicate toDGS-8466,Regards\']""]\nRelated Issues:\n[]\n\n### End'}"
602,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8430\n\n### Instruction:\nArtikel 704956 has been exported to Intens, unfortunately I don\'t see this in Intens (New Items)\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 2: ""Hello,There is a New Item Card in \\\'MAS NL\\\' sector with code = \\\'704956\\\' has been sent from Milas on 20.01.2023.Someone should parametrized this item and decide for which sectors item should be created from New Item Card document. Then item will be able to choose in Intense in this sector/sectors.!image-2023-01-30-16-15-54-887.png!!image-2023-01-30-16-17-24-349.png!Regards""\', ""Comment 3: \'Could we close the task?\'"", ""Comment 4: \'Confirmed that can be closed.\']""]\nRelated Issues:\n[]\n\n### End'}"
603,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8429\n\n### Instruction:\nThese  messages ara show in quarantaine screen in DHP. \r\nQuestion : Where can we see the interval off time for wich items will be show in this screen because there is a great variation in the interval\r\nSome item will be correct for more then half a year\r\nThere will be differences between items with the same therm.\r\n\n\n### Response:\n[""Comment 1: [\'!image-1!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'zgodnie z rozmową. \'"", ""Comment 4: \'Is there anything known about the status of this issue?\']""]\nRelated Issues:\n[]\n\n### End'}"
604,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8428\n\n### Instruction:\nFields on Tech Results tab on Financial Statement document:\r\n * Total value of first loader\xa0\r\n * Total value of all loader\r\n\r\nshould be changed and calculated with all item codes instead of \'SLAC\' item like it is right now.\r\n\r\n\xa0\r\n\r\n*How it is:*\r\n\r\n(Sum of net values from invoices (PI and SI) related to Slaughtery reports (without invoices from Reversed Slaughtery Reports) with item code = \'SLAC\')\r\n\r\nminus\r\n\r\n(Sum of net values from invoices (PI and SI) related to Slaughtery reports (without invoices from Reversed Slaughtery Reports) with item code = \'AFKK\')\r\n\r\n\xa0\r\n\r\n*How it should be:*\r\n\r\n(Sum of net values from invoices (PI and SI) related to Slaughtery reports (without invoices from Reversed Slaughtery Reports) with item code != \'AFKK\')\r\n\r\nminus\r\n\r\n(Sum of net values from invoices (PI and SI) related to Slaughtery reports (without invoices from Reversed Slaughtery Reports) with item code = \'AFKK\')\r\n\r\n\xa0\r\n\r\nDue to this change also values for other calculations will change:\r\n * Feed profit\r\n * Average price delivered broilers per kg\r\n\r\n!image-2023-01-30-16-09-14-749.png!\r\n\r\nexample - FS-M/0219, ID= 79562 on IBIP_DH_TEST\n\n### Response:\n[\'Comment 1: [""[~mbovene@deheus.com]we have been changed calculations on Technial Results for Total value of first loaders. These changes have impact on fields Total value of all loaders and Feed profit. We also changed Average price delivered calulation because it\\\'s related with Total value of first/all loaders calculation.You can feel free to test it on test environment for MAS NL and MAS BE. I\\\'m waiting for your feedback.Best regards\', \'Comment 2: Grzegorz""\', \'Comment 3: \\\'There is still something not good in the ""Voerwinst""(Feed profit).It should be 217.146,90 - 140.972,02 - 25.257,54 = 50.917,34 !image!\\\'\', \'Comment 4: \\\'Two other changes from the business:* Change “Doorgroei na 1e keer uitladen (g/d)” to ""Doorgroei (g/d)""* Make this 0 decimals instead of 2\\\'\', \'Comment 5: ""Please verify now and recalcualte technical results\', \'Comment 6: there should be value for Feed profit =50917.35 on document FS and also on printout.Before my change this value 1185,02 was as positive\', \'Comment 7: but it should be with negative sign. I\\\'ve changed this value for -1185,02 and also add vat and gross value for this line.!image-2023-02-02-13-45-04-522.png!""\', \'Comment 8: \\\'Two other changes from the business: * Change “Doorgroei na 1e keer uitladen (g/d)” to ""Doorgroei (g/d)"" * Make this 0 decimals instead of 2DONE :)\\\'\', ""Comment 9: \'[~mbovene@deheus.com]could you verify it?After confirmation we can move also these changes on production environment.\'"", ""Comment 10: \'Verified.\'"", ""Comment 11: \'[~grzegorz.materla@kotrak.com]do przeniesienia na prod\'"", ""Comment 12: \'[~damian.swistek@kotrak.com]przeniesione na prod.\'"", ""Comment 13: \'[~mbovene@deheus.com],modification for technical resultscalculations have been adjusted in prod environment.You can feel free to test it.Best regards,Grzegorz\'"", ""Comment 14: \'Can be closed.\']""]\nRelated Issues:\n[\'DGS-8053\', \'DGS-8215\']\n\n### End'}"
605,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8427\n\n### Instruction:\nFor Abma 000105 - this is a free contract - we can not open a new round, see error below. \n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Its fixed now on test and production database"", ""Comment 3: you can test it on test database.\'"", ""Comment 4: \'Dodano dodatkowy warunek na wykonanie akcji przy free farmer kontrakcie\'"", ""Comment 5: \'Still same error"", ""Comment 6: I can not create the new round\'"", \'Comment 7: ""Can you check it now i don\\\'t get this error now.""\', ""Comment 8: \'Still can not open round. Now only this error. !image-1!\'"", ""Comment 9: \'Ogólnie z free farmer contractu nie możemy wykonać tej akcjiakcja jest stworzona dla dokumentu CF"", \'Comment 10: już przy pierwszym kroku szuka dokumentuów z ddf_id CF\', ""Comment 11: akcja jest całkowicie nie przystosowana do dokumentu ffc\'"", ""Comment 12: \'Can you please check this again"", ""Comment 13: it is urgent\'"", \'Comment 14: ""Hello Dirco,We\\\'re verifying this topic\', ""Comment 15: because it looks like in the system it\'s not well prepared creating Round and Feed sale from \'Free Farmer Contract\'.We need to investigate it little more.Is it possible to create \'Contract farmer\' from this \'Free farmer contract\' which you need right now?We don\'t want to stop you with work"", \'Comment 16: then we want to find some temporary solution.This functionality works well from Contract Farmer\', \'Comment 17: but from Free Farmer Contract it looks different in our configuration\', \'Comment 18: due to this it will take more time to review it.Regards""\', ""Comment 19: \'Comment at mail Tomasz: I still can not create the next round \'"", ""Comment 20: \'Hello Dirco,Please verify right now that is it correct and you can generate properly Round from Free Contract Farmer.Regards\'"", ""Comment 21: \'Yes it is fixed now. This can be closed"", ""Comment 22: thanks. \']""]\nRelated Issues:\n[]\n\n### End'}"
606,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8426\n\n### Instruction:\nPlease help to check VT-1669/1/23  in Nghe An Plant ( 0432) .\r\nItem BPEY000731 can\'t released to stock with reson ""Serial number already exists"" ( it has the same serial number as item BPEY00419).\r\nWhy is there no warning when user recording a duplicate serial number ? User still can complete WO and close VT?\n\n### Response:\n[""Comment 1: [\'!image!!image-1!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 3: ""{code:java}SELECT       [SerialNumber]      ,[InternalSerialNumber]\\\\t  ,*      FROM [DHPlantWmsBusinessLogicMain].[dbo].[UnitLoads]  where SerialNumber=\\\'30012023PO1249TH2\\\'  select * from dbo.Items where id in(\\\'D03E04FB-01A1-4AB3-ADD1-A58575C860AC\\\',\\\'68BE024E-3115-4964-A5B8-295114645D6D\\\'){code} !screenshot-1! brakuje w stock:VT ma 22 elementy !screenshot-2! !image-2023-01-30-14-12-48-772!""\', ""Comment 4: \'Hello as for correction the  VT you can edit the delivery that is already in stock and then send the message with the error again. !screenshot-3! And yes"", ""Comment 5: there should be a warning.Were there other cases like this?\'"", ""Comment 6: \'1 question before you can close the ticket: Serial can edit or not if that already for using?\'"", \'Comment 7: ""Where it is already used because I don\\\'t see that initial<> current quanitity? There is only a restriction on the uniqueness of the entry.Regards""\', ""Comment 8: \'HI Piotr GaczorekYou can close this ticket. Thanks u.\']""]\nRelated Issues:\n[]\n\n### End'}"
607,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8425\n\n### Instruction:\nI will write an e-mail for this topic.\r\n\r\n\r\n\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'{color:black}Hi,{color} {color:black}{color} {color:black}Can you help us with the following?{color} {color:black}Customer 100725 shows in FS-N/0023 ID88499 These post:{color}{color:black}{color} !image001!{color:black}{color}{color:black}{color} {color:black}When we go to Excel our Slaughtery is out of the overview (see Excel){color}{color:black}{color} !image002!{color:black}{color}{color:black}{color} {color:black}{color} {color:black}How can this be?{color} {color:black}{color} {color:black}{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Christinede{color} |{color:#000001} {color} |{color:#000001} Jong{color} |  {color:#000001}MedewerkerContractadministratie{color} | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}{color:blue}{color}!image003!{color:blue}{color}{color:black} <[https://www.de-heus.nl/]>{color} | |  *{color:#006FB7} *DEHEUSVOEDERSB.V.*{color}* | | | |{color:#000001} Postbus396 6710BJEde \\\\u200b{color} | |{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} | | |{color:#000001} T:0318675567{color} |  {color:#000001}KvK14626985{color}   _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | |{color:blue}{color} !image004!{color:blue}{color} <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | |{color:blue}{color} !image005!{color:blue}{color} <[https://twitter.com/de_heus_voeders]>{color:black}{color} | |{color:blue}{color} !image006!{color:blue}{color} <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | |{color:blue}{color} !image007!{color:blue}{color} <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} |     [^FS Trenning (geen slacht).xlsx] _(24 kB)_\'"", \'Comment 3: ""Hello,I see that is an issue because we\\\'re showing documents PI when Reference is filled. On these 2 documentsPI-FNN/2022/0379,PI-FNN/2022/0380 this field is empty.Why this field is empty? Is there any reason why this field is empty?!image-2023-01-30-12-04-35-753.png!That\\\'s why it\\\'s not visible on this list (at summary \\\'Total Slaughtery\\\' we\\\'re showing invoices when \\\'Supplier\\\' (not referecne) is filled\', ""Comment 4: so in this case it\'s ok and values from invoices are summed).For this case filling field \'Reference\' will resolve issue"", \'Comment 5: however there are some inaccuracies here between Round and Financial statement which we can also adjust.Please inform us about \\\'Reference\\\' on PI invoices.!image-2023-01-30-12-04-21-628.png!""\', ""Comment 6: \'{color:black}Hi Damian,{color} {color:black}{color} {color:black}Something went wrong with this migration.{color} {color:black}Invoices should be:{color} {color:black}Leading doc a regular sale{color} {color:black}Purchase a registered purchase.{color} {color:black}{color} {color:black}I asked Mitch if he could change these postings"", \'Comment 7: but he can not.{color} {color:black}Could you please make the change?{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Christinede{color} |{color:#000001} {color} |{color:#000001} Jong{color} |  {color:#000001}MedewerkerContractadministratie{color} | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.de-heus.nl/]>{color} | |  *{color:#006FB7} *DEHEUSVOEDERSB.V.*{color}* | | | |{color:#000001} Postbus396 6710BJEde \\\\u200b{color} | |{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} | | |{color:#000001} T:0318675567{color} |  {color:#000001}KvK14626985{color}   _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | | !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | | !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} | | !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} |      *Van:* Damian Świstek (Jira) <jira@kotrak.com>   *Verzonden:* maandag 30 januari 2023 12:14  *Aan:* Jong\', ""Comment 8: Christine de <CJong@deheus.com>  *Onderwerp:* DGS-8425 FS 100725 Trenning incomplete   |  *{color:white} *CAUTION: This message originated from outside the organisation. Please do not click on links or open attachments unless you trust the sender and know the content is safe.*{color}* |   !image006-1!!image007-1!!image006!!image007!\'"", \'Comment 9: ""Hi Christine,We can change some data if it\\\'s not correct\', \'Comment 10: but what data should we change? Like on screens?!image-2023-01-31-13-28-02-948.png!!image-2023-01-31-13-25-32-220.png!""\', ""Comment 11: \'{color:black}Yes perfect Damian{color} {color:black}😊{color}{color:black}{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Christinede{color} |{color:#000001} {color} |{color:#000001} Jong{color} |  {color:#000001}MedewerkerContractadministratie{color} | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.de-heus.nl/]>{color} | |  *{color:#006FB7} *DEHEUSVOEDERSB.V.*{color}* | | | |{color:#000001} Postbus396 6710BJEde \\\\u200b{color} | |{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} | | |{color:#000001} T:0318675567{color} |  {color:#000001}KvK14626985{color}   _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | | !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | | !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} | | !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} |      *Van:* Damian Świstek (Jira) <jira@kotrak.com>   *Verzonden:* dinsdag 31 januari 2023 13:30  *Aan:* Jong"", ""Comment 12: Christine de <CJong@deheus.com>  *Onderwerp:* DGS-8425 FS 100725 Trenning incomplete   |  *{color:white} *CAUTION: This message originated from outside the organisation. Please do not click on links or open attachments unless you trust the sender and know the content is safe.*{color}* |   !image006-2!!image007-2!!image006!!image007!\'"", ""Comment 13: \'Now it is like on screens below.PI-RTN/2022/0148 - PI Registration (on my earlier screen I made mistake and mark as Regular)- reference is filledSI-RLN/2022/0310 - SI RegularNow only PI Registration is on the Round and Financial StatementPlease verify that everything is correct.Regards!image-2023-01-31-14-52-35-950.png!!image-2023-01-31-14-48-26-232.png!\'"", ""Comment 14: \'{color:black}Hi Damian,{color} {color:black}{color} {color:black}We miss these ones. Could you also change these to registration?{color} {color:black}ID 35452{color}{color:black}{color} !image001!{color:black}{color}{color:black}{color} {color:black}SI ID 36376{color} {color:black}{color} {color:black}{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Christinede{color} |{color:#000001} {color} |{color:#000001} Jong{color} |  {color:#000001}MedewerkerContractadministratie{color} | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image002!{color:black} <[https://www.de-heus.nl/]>{color} | |  *{color:#006FB7} *DEHEUSVOEDERSB.V.*{color}* | | | |{color:#000001} Postbus396 6710BJEde \\\\u200b{color} | |{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} | | |{color:#000001} T:0318675567{color} |  {color:#000001}KvK14626985{color}   _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | | !image003! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | | !image004! <[https://twitter.com/de_heus_voeders]>{color:black}{color} | | !image005! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image006! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} |      *Van:* Damian Świstek (Jira) <jira@kotrak.com>   *Verzonden:* dinsdag 31 januari 2023 15:01  *Aan:* Jong"", ""Comment 15: Christine de <CJong@deheus.com>  *Onderwerp:* DGS-8425 FS 100725 Trenning incomplete   |  *{color:white} *CAUTION: This message originated from outside the organisation. Please do not click on links or open attachments unless you trust the sender and know the content is safe.*{color}* |   !image001-1!!image007-3!!image008!!image007!\'"", ""Comment 16: \'Hi Christine,SI ID 36376 - changed to Regular!image-2023-02-01-09-18-20-068.png!PI35452 - Registration and filled Reference!image-2023-02-01-09-22-18-336.png!Please verify that is correct.Regards\'"", ""Comment 17: \'{color:black}Goodmorning,{color} {color:black}{color} {color:black}Thanks Damian! Now FS is complete{color} {color:black}😊{color}{color:black}{color} {color:black}Have a good day.{color} {color:black}{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Christinede{color} |{color:#000001} {color} |{color:#000001} Jong{color} |  {color:#000001}MedewerkerContractadministratie{color} | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.de-heus.nl/]>{color} | |  *{color:#006FB7} *DEHEUSVOEDERSB.V.*{color}* | | | |{color:#000001} Postbus396 6710BJEde \\\\u200b{color} | |{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} | | |{color:#000001} T:0318675567{color} |  {color:#000001}KvK14626985{color}   _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | | !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | | !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} | | !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} |      *Van:* Damian Świstek (Jira) <jira@kotrak.com>   *Verzonden:* woensdag 1 februari 2023 09:25  *Aan:* Jong"", ""Comment 18: Christine de <CJong@deheus.com>  *Onderwerp:* DGS-8425 FS 100725 Trenning incomplete   |  *{color:white} *CAUTION: This message originated from outside the organisation. Please do not click on links or open attachments unless you trust the sender and know the content is safe.*{color}* |   !image006-3!!image007-4!!image006!!image007!\']""]\nRelated Issues:\n[\'DGS-8437\']\n\n### End'}"
608,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8424\n\n### Instruction:\nOn customer 816755 we are not able to open a new round. It seems that the contract is closed.\r\n816755/0069/0001\r\nOn 016755 contract 0057 can be closed.\r\n\r\nThanks for your action.\r\n\r\n\r\n\r\n\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 2: ""Hello,Contract Farmer CF-N/0069 now is in \\\'Draft\\\' status in your Inbox\', \'Comment 3: you should be able to process it and then Create new Round.Contract FarmerCF-N/0057 has been closed.Please verify that is correct.""\', ""Comment 4: \'Sorry I forgot to reply. You can resolve this as done.\']""]\nRelated Issues:\n[]\n\n### End'}"
609,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8423\n\n### Instruction:\nWe want to delete conversion documents from the round of An de Stegge but we can\'t find the documents in documents. Please could you tell us how we can delete this documents?\n\n### Response:\n[""Comment 1: [\'!An de Stegge documentnr.PNG|thumbnail!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 3: ""Hello,Please try to clear this field \\\'From\\\' on ribbon and you should be able to find these documents.!image-2023-01-30-09-47-23-364.png!Regards""\', ""Comment 4: \'Could we close the task?\'"", ""Comment 5: \'Yes\']""]\nRelated Issues:\n[]\n\n### End'}"
610,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8422\n\n### Instruction:\nPlease help to check this case and solving in Can Tho Plant -0437\r\nOn canceled of Production lot report with stock unit status In progress . \r\n** PLR 44372140123005 and 4372200123005\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: \'Dla lota4372200123005!image-2023-02-01-08-45-42-916.png!errory:!image-2023-02-01-08-44-25-864.png!!image-2023-02-01-08-45-00-565.png!!image-2023-02-01-08-45-00-565! !image-2023-02-01-08-45-42-916!\'"", ""Comment 4: \'LOT4372200123005!image-2023-02-01-08-47-35-682.png!!image-2023-02-01-08-47-55-209.png!\'"", ""Comment 5: \'!image-2023-02-01-09-10-10-118.png!\'"", ""Comment 6: \'Dear Hardy,You can do inventory for those two stock units. Or we can correct them under database. Please"", \'Comment 7: let us know what is better for you.For duplicated PLRs (I guess this was the reason for cancelling them\', ""Comment 8: I have asked in DGS-8329 if you agree to raise RCA task).Regards\'"", \'Comment 9: ""{code:java}--UPDATE D--SET Status = 2\', \'Comment 10: Quantity = 0\', \'Comment 11: ExpiryDate = GETDATE()select *FROM DHPlantStockBusinessLogicMain.dbo.Deliveries DLEFT JOIN DHPlantStockBusinessLogicMain.dbo.StockUnits S ON S.DeliveryId = D.IdWHERE D.SourceDocumentId IN (\\\'B85005E1-F436-427F-95CF-DA74DD5F25F5\\\',\\\'A867C990-3B57-4896-803A-68D29937439F\\\')--UPDATE S--SET Quantity=0,Quantityonhand = 0,logisticstatus=8select *FROM DHPlantStockBusinessLogicMain.dbo.Deliveries DLEFT JOIN DHPlantStockBusinessLogicMain.dbo.StockUnits S ON S.DeliveryId = D.IdWHERE D.SourceDocumentId IN (\\\'B85005E1-F436-427F-95CF-DA74DD5F25F5\\\',\\\'A867C990-3B57-4896-803A-68D29937439F\\\'){code}""\', ""Comment 12: \'please correct under DB and i have answer in DGS-8329\'"", ""Comment 13: \'Stock Units are corrected. Please"", ""Comment 14: verify.Regards\'"", ""Comment 15: \'W Prod i w Stock PLRy mają różne ID!image-2023-02-03-10-53-26-923.png!\'"", ""Comment 16: \'Hi Piotr Gaczorek .You can close the ticket .\'"", ""Comment 17: \'Hi leksandra Przybyłek.You can close the ticket .\']""]\nRelated Issues:\n[\'DGS-8330\', \'DGS-8329\']\n\n### End'}"
611,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8421\n\n### Instruction:\nSql Nightrun  job on DHVD01AP53 stopped for the second time. Linked server 10.111.4.5 can\'t be reached, see screenshot. Perhaps this has something to do with the Microsoft interruption last Thursday? Perhaps someone can take a look. Thanks in advance. Nightrun didn\'t run Thursday to Friday and Friday to Saturday night. As the interruption @Microsoft happened on Thursday it seems logical but i could be wrong. \n\n### Response:\n[""Comment 1: [\'!DHVD01AP53.JPG|thumbnail!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Thanks"", \'Comment 4: but last night the sync did run again. It is kind of strange and also sometimes but worrying that it isn\\\\\\\'t running. Also the error message is something i can\\\\\\\'t explain. 01/29/2023 02:11:12,BMadmin_Interfacing (night run) Azure,Error,12,DHVD01AP53,BMadmin_Interfacing (night run) Azure,e2 - NutrientDescriptions,,Executed as user: HEUS\\\\\\\\sa_sqld01ap53. TCP Provider: The semaphore timeout period has expired. [SQLSTATE 07008] (Error 121) OLE DB provider ""SQLNCLI11"" for linked server ""10.111.4.5"" returned message ""Communication link failure"". [SQLSTATE 01000] (Error 7412). The step failed.,00:53:44,16,7412,,,,001/27/2023 02:12:18,BMadmin_Interfacing (night run) Azure,Error,12,DHVD01AP53,BMadmin_Interfacing (night run) Azure,e2 - NutrientDescriptions,,Executed as user: HEUS\\\\\\\\sa_sqld01ap53. Cannot get the current row value of column ""[10.111.4.5].[BestmixSyncDB].[dbo].[NutrientDescriptions].Language"" from OLE DB provider ""SQLNCLI11"" for linked server ""10.111.4.5"". [COLUMN_NAME= Language STATUS=Unknown DBBINDSTATUS] [SQLSTATE 42000] (Error 7341) OLE DB provider ""SQLNCLI11"" for linked server ""10.111.4.5"" returned message ""Multiple-step OLE DB operation generated errors. Check each OLE DB status value<c/> if available. No work was done."". [SQLSTATE 01000] (Error 7412). The step failed.,01:54:03,16,7412,,,,0Do we need to send these messages to you in the first place? \\\'\', ""Comment 5: \'Dear Rob,We have discussed your case. We think you should contactMebrate or your IT to solve this case.Regards\'"", ""Comment 6: \'Ok"", ""Comment 7: i will discuss this internally. Thanks. \'"", ""Comment 8: \'Shall we leave this task open or can we close it?Regards\'"", ""Comment 9: \'Goodmorning"", ""Comment 10: you can close this task. Thanks!\'"", ""Comment 11: \'Thank you.\']""]\nRelated Issues:\n[]\n\n### End'}"
612,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8420\n\n### Instruction:\nWe have several documents confirmed on DHP but they are not integrating to DHC. \r\n0851250123005\r\n0851250123014\r\n0851250123015\r\n0853250123001\r\n0851250123011\r\nCould you please fix it? It\'s urgent, we are waiting to 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: ""Please werify if SQL server works. I\\\'m not able to expand databases!image-2023-01-27-20-24-11-876.png!Also i\\\'m not able to log on to server:!image-2023-01-27-20-27-59-454.png!""\', ""Comment 3: \'!image-2023-01-27-20-33-02-599.png!\'"", ""Comment 4: \'Please"", ""Comment 5: try this password Kotr@2023\'"", ""Comment 6: \'!image!\'"", \'Comment 7: \\\'2023-01-27 16:59:47 (15de5d19-7ce1-4538-964d-eb22444b4e3e/Plant.DHC.Integration/BR-1-SV-VM0604/15144/5) [Error] Kotrak.Integration.IntegrationPluginCommon.IntercontextCommunication.Inbound.InboundIntercontextErrorHandler - Error during handling message of type ""Plant.Stock.BusinessLogic.DomainAbstractions.Deliveries.DeliveryCreatedEvent""\', \'Comment 8: retry no -1Kotrak.Integration.IntegrationPluginCommon.Interfaces.ConnectionBrokenException: An error occurred while sending the request. ---> System.ServiceModel.CommunicationException: An error occurred while sending the request. ---> System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.. ---> System.Net.Sockets.SocketException (10054): An existing connection was forcibly closed by the remote host. --- End of inner exception stack trace --- at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error\', \'Comment 9: CancellationToken cancellationToken) at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource<System.Int32>.GetResult(Int16 token) at System.Net.Http.HttpConnection.<CheckUsabilityOnScavenge>g__ReadAheadWithZeroByteReadAsync|45_0() at System.Net.Http.HttpConnection.SendAsyncCore(HttpRequestMessage request\', \'Comment 10: Boolean async\', \'Comment 11: CancellationToken cancellationToken) --- End of inner exception stack trace --- at System.Net.Http.HttpConnection.SendAsyncCore(HttpRequestMessage request\', \'Comment 12: Boolean async\', \'Comment 13: CancellationToken cancellationToken) at System.Net.Http.HttpConnectionPool.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage request\', \'Comment 14: Boolean async\', \'Comment 15: Boolean doRequestAuth\', \'Comment 16: CancellationToken cancellationToken) at System.Net.Http.RedirectHandler.SendAsync(HttpRequestMessage request\', \'Comment 17: Boolean async\', \'Comment 18: CancellationToken cancellationToken) at System.Net.Http.DecompressionHandler.SendAsync(HttpRequestMessage request\', \'Comment 19: Boolean async\', \'Comment 20: CancellationToken cancellationToken) at System.Net.Http.HttpClient.<SendAsync>g__Core|83_0(HttpRequestMessage request\', \'Comment 21: HttpCompletionOption completionOption\', \'Comment 22: CancellationTokenSource cts\', \'Comment 23: Boolean disposeCts\', \'Comment 24: CancellationTokenSource pendingRequestsCts\', \'Comment 25: CancellationToken originalCancellationToken) at System.ServiceModel.Channels.HttpChannelFactory`1.HttpClientRequestChannel.HttpClientChannelAsyncRequest.SendRequestAsync(Message message\', \'Comment 26: TimeoutHelper timeoutHelper) --- End of inner exception stack trace --- at System.ServiceModel.Channels.HttpChannelUtilities.ProcessGetResponseWebException(HttpRequestException requestException\', \'Comment 27: HttpRequestMessage request\', \'Comment 28: HttpAbortReason abortReason) at System.ServiceModel.Channels.HttpChannelFactory`1.HttpClientRequestChannel.HttpClientChannelAsyncRequest.SendRequestAsync(Message message\', \'Comment 29: TimeoutHelper timeoutHelper) at System.ServiceModel.Channels.RequestChannel.RequestAsync(Message message\', \'Comment 30: TimeSpan timeout) at System.ServiceModel.Channels.RequestChannel.RequestAsyncInternal(Message message\', \'Comment 31: TimeSpan timeout) at System.ServiceModel.Channels.RequestChannel.Request(Message message\', \'Comment 32: TimeSpan timeout) at System.ServiceModel.Dispatcher.RequestChannelBinder.Request(Message message\', \'Comment 33: TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannel.Call(String action\', \'Comment 34: Boolean oneway\', \'Comment 35: ProxyOperationRuntime operation\', \'Comment 36: Object[] ins\', \'Comment 37: Object[] outs\', \'Comment 38: TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(MethodCall methodCall\', \'Comment 39: ProxyOperationRuntime operation) at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(MethodInfo targetMethod\', \'Comment 40: Object[] args) at generatedProxy_1.PushDeliveries(Package`1 ) at Plant.Integration.DhcService.Communication.BasePushService`1.PushPackage(IDhcService dhcService\', \'Comment 41: Package`1 package) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\e810c04f78ab209c\\\\\\\\Plant.Integration.DhcService\\\\\\\\Plant.Integration.DhcService.Communication\\\\\\\\BasePushService.cs:line 40 --- End of inner exception stack trace --- at Plant.Integration.DhcService.Communication.BasePushService`1.PushPackage(IDhcService dhcService\', \'Comment 42: Package`1 package) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\e810c04f78ab209c\\\\\\\\Plant.Integration.DhcService\\\\\\\\Plant.Integration.DhcService.Communication\\\\\\\\BasePushService.cs:line 40 at Plant.Integration.DhcService.Communication.BasePushService`1.CallService(IDhcService dhcService\', ""Comment 43: Package`1 package) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\e810c04f78ab209c\\\\\\\\Plant.Integration.DhcService\\\\\\\\Plant.Integration.DhcService.Communication\\\\\\\\BasePushService.cs:line 62 at Plant.Integration.DhcService.Application.PushDataFilter`1.Process(PackageIntegrationState input) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\e810c04f78ab209c\\\\\\\\Plant.Integration.DhcService\\\\\\\\Plant.Integration.DhcService.Application\\\\\\\\PushDataFilter.cs:line 26 at Kotrak.Integration.Pipeline.PredefinedFilters.FilterBase`1.Execute(T input) at Kotrak.Integration.Pipeline.PredefinedFilters.FilterBase`1.Execute(T input) at Kotrak.Integration.Pipeline.Pipeline`1.Excecute(T input) at Plant.Integration.DhcService.Infrastructure.Handlers.BaseInboundMessageHandler`1.Handle(TEvent message) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\e810c04f78ab209c\\\\\\\\Plant.Integration.DhcService\\\\\\\\Plant.Integration.DhcService.Infrastructure\\\\\\\\Handlers\\\\\\\\BaseInboundMessageHandler.cs:line 49 at Kotrak.Integration.IntegrationPluginCommon.IntercontextCommunication.Inbound.IntercontextInboundHandler`2.Handle(InternalStorageDto message)\'"", ""Comment 44: \'Monikanow can you access?\'"", ""Comment 45: \'Yes I have. during analysis\'"", ""Comment 46: \'Have you made any changes inSQL server firewall settings or another network settings?\'"", \'Comment 47: ""I checked with Ludemila and no\', \'Comment 48: we didn\\\'t changed nothing.""\', ""Comment 49: \'Can I restart the DHP servers?\'"", ""Comment 50: \'Yes please make restart.\'"", ""Comment 51: \'done\'"", ""Comment 52: \'could you check integration now?\'"", ""Comment 53: \'yes . I will let you know\'"", ""Comment 54: \'Now the production are in DHC. Do you know why we had this problem?\'"", ""Comment 55: \'There was problem with connect into DHP SQL server from server 10.55.64.12. Now it works. This was incydentally problem restart helps.!image-2023-01-27-22-18-00-964.png!\']""]\nRelated Issues:\n[]\n\n### End'}"
613,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8419\n\n### Instruction:\nProszę o sprawdzenie, czemu dokument nie chce się prawidłowo zaksięgować, przypisane zostały właściwe konta 505-02-01-03 i 505-02-01-08 do nowych MPK-ów;\r\nPoniżej dekretacja:\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: \'Przy próbie księgowania nie otrzymaliśmy żadnego komunikatu błędu. Wycofaliśmy dekretację.Proszę o sprawdzenie i informację"", ""Comment 4: jaki błąd pojawia się u Pani przy dekretacji.Pozdrawiam!image-2023-01-27-17-55-51-009.png!\'"", ""Comment 5: \'Została właśnie przeprowadzona ponowna próba i przeszło bez problemuDziękujeTask do zamkniecia\']""]\nRelated Issues:\n[]\n\n### End'}"
614,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8418\n\n### Instruction:\nHi,\r\n\r\nIs it possible to add transport cost to Internal Orders (IOs)\r\n\r\nIf possible how ?\r\nif not what options do we have.\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 SamuelThere is no functionality for adding costs on internal order in the system.We can add an attribute in which we enter the value of the transport cost just for information purposes"", \'Comment 3: but this cost will not increase the value of the goods in stock.Regards\', ""Comment 4: Beata\'"", ""Comment 5: \'Many Thanks Kindly Close the Ticket\']""]\nRelated Issues:\n[]\n\n### End'}"
615,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8417\n\n### Instruction:\nDear Jira service Desk\r\nWe have a stalk unit of Fry Meal (9004 ) = 501kg but we couldn`t process it on dispatch for a customer to sell it.  keeps saying missing stalk . \r\nWe only needed 75 kg to dispatch when there is already 501kg available on system .  \r\nHope someone will help us figure out a solution.\r\nThanks always   \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: \'Thanks very much !\'"", ""Comment 4: \'Dear Gemechis,This item is expired. You can edit delivery and change the date.Regards!image-2023-01-27-16-38-22-420.png!\'"", ""Comment 5: \'Hello Dear  Yes that was a solution ; I edited the expiry date as suggested and Sales dispatch was successful.  Thanks very much  Problem solved !!image001!\'"", ""Comment 6: \'Thank you\']""]\nRelated Issues:\n[]\n\n### End'}"
616,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8416\n\n### Instruction:\nKD has order 217/23/KLR showing in production but are unable to produce off of it as the order element is not appearing \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: \'BulkProductID was missing"", ""Comment 4: Item was resent from DHC,Please check. !screenshot-1! \'"", ""Comment 5: \'thank you"", ""Comment 6: task can be closed\']""]\nRelated Issues:\n[]\n\n### End'}"
617,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8415\n\n### Instruction:\nHello, can you please remove AD \xa0AW967242 from DHC, this one is no longer Active\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Hi Thomas,Additional Technology has been removed.Regards\'"", ""Comment 3: \'Thanks"", ""Comment 4: ticket can be closed\']""]\nRelated Issues:\n[]\n\n### End'}"
618,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8414\n\n### Instruction:\nserver is: 10.84.1.22\r\nC:\\CA contains the latest one\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'proszę o przekazanie do działu dev"", ""Comment 4: będzie to rozliczane w ramach wsparcia integracji z MS D365\'"", ""Comment 5: \'certyfikat podmieniony\'"", ""Comment 6: \'Please check should be working now"", ""Comment 7: resolved by developers.\'"", ""Comment 8: \'Hello,We are closing this task as we haven’treceivedany replyfromyouforalong time. Regards\']""]\nRelated Issues:\n[]\n\n### End'}"
619,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8413\n\n### Instruction:\nGood evening,\r\n\r\nI have got a problem with item code 116270 for plant Maasbracht.\r\nThe recipe is not available on DHC.\r\n\r\nPlease could you help me, out production needs this one.\r\n\r\nKind regards\r\n\r\nGerard Geerts\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Hello Monika,did you find a course of this problem?Regards,Gerard\'"", ""Comment 3: \'no still analysis\'"", ""Comment 4: \'Oké! Thanks for a reaction sofar.\'"", ""Comment 5: \'Reason is full queuesThere is missing DHH item in dhC Service database. Then should be sent information about recipe. We will monitoring list of queue and when it will decrease recipe should appear in DHP!image-2023-01-26-22-35-23-984.png!\'"", ""Comment 6: \'Hello Monika,This problem could we found it by ourselves by analysis and after that resolve it?Thanks for your support.Kind regards,Gerard\'"", ""Comment 7: \'For item116270 recipes version 22 and 23 should be in plant now. please verify\'"", ""Comment 8: \'Hello Gerard"", ""Comment 9: regarding message queues you can verify with BP here for DHCService whether messages are being processed. !screenshot-1! \']""]\nRelated Issues:\n[]\n\n### End'}"
620,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8412\n\n### Instruction:\nKindly remove these documents form buffer as they are inconsequential and preventing the closing of the month\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: \\\'Why don\\\\\\\'t you untick ""To buffer"" and save this document?!image-2023-01-26-17-33-56-290.png!What should happen next with those PORC documents? Should they be executed or cancelled?Regards!image-2023-01-26-17-33-56-290!\\\'\', ""Comment 4: \'!image-1!\'"", ""Comment 5: \'This is what happens when i try that\'"", ""Comment 6: \'Hi,Just to confirm:Corrected document is POR-73/21/MAG issued on the 22nd of February"", \'Comment 7: 2021 and it has correction under PORC-129/21!image-2023-01-30-08-14-37-231.png!!image-2023-01-30-08-18-47-738.png!PORC-129/21 is issued on the 30th of April 2021 (quantity)!image-2023-01-30-08-17-54-700.png!!image-2023-01-30-08-18-15-937.png!PORC-350/21 was issued on 14th of June 2021 (value\', ""Comment 8: but issued first due to gid number)!image-2023-01-30-08-21-50-513.png!!image-2023-01-30-08-22-16-744.png!\'"", \'Comment 9: ""Hi,We have analised all clipped documents. PORC-129 has been issue incorrect. In our opinion\', \'Comment 10: the best option would be to remove PORC-129 (as it is in buffer\', \'Comment 11: you can delete it here:!image-2023-01-30-09-23-22-114.png|width=831,height=342! )and issue this correction document again. But please\', \'Comment 12: mind this correction will correct current stock.I would like you to clarify one more thing: how document from 2021 interrupts closing months in 2023? Didn\\\'t it interrupted closing month in 2022? Do you receive any error?Regards""\', \'Comment 13: ""{color:#212121}First of all i have tried deleting and it doesn\\\'t delete\', \'Comment 14: and we are now closing all our months\', \'Comment 15: we haven\\\'t closed months before this is the first time that is why this issue is now coming up. You can try deleting it and see if it will delete. It wont.{color} ----""\', ""Comment 16: \'PORC-129 has been deleted. Now you need to generate correction document again.The issue was caused that first correction PORC-350 was done to element and the next correction PORC-129 was done to PORC-350 (header)"", \'Comment 17: not to element.Please4\', ""Comment 18: check and let us know if you can proceed further.Regards\'"", ""Comment 19: \'Trza było ustawić TrN_SpiTyp = 0{code:java}update n set TrN_SpiTyp=0 from cdn.tranag n where trn_gidnumer = 269472{code}\'"", ""Comment 20: \'you removed just one. i want all removed please\'"", ""Comment 21: \'Hello,Regarding documents:!image-2023-02-01-07-54-36-429.png!shall we delete them or remove from buffer? I have chnaged clipper type on those documents so you can also remove them by yourself.Regards\'"", ""Comment 22: \'okay let me remove them and see if they move\'"", ""Comment 23: \'Sure"", ""Comment 24: waiting for your feedback then.\'"", ""Comment 25: \'it works kindly close\'"", ""Comment 26: \'Thank you.\']""]\nRelated Issues:\n[]\n\n### End'}"
621,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8411\n\n### Instruction:\nRecipe 3620.025 v. 15 and 16 are not synchronized to DHP\n\n### Response:\n[\'Comment 1: [""In DHH one ingredient is rounded up to quantity 0this 3014014 - quantity 0 in kg and quantity % 0,0000377 but DHH rounds up to 4 digitsThe recipe\\\'s ingredient cannot have 0 quantity\', \'Comment 2: That is why it is not synchronized to DHPVersion 15 and 16 have the same problemSerge needs to send the recipe again with a slightly bigger quantity - on 14 it was 0,0001The quantity needs to be discussed with Serge. In case You need more then 4 digits then we would have to make the change globally in DHHBest regards\', \'Comment 3: Marta""\', ""Comment 4: \'!image!\']""]\nRelated Issues:\n[]\n\n### End'}"
622,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8410\n\n### Instruction:\nIntakes are not being sent from DHP to DHC.\r\nAn example we have more intakes that are not synchronized to DHC at all.\r\n\r\nFor example, we have ASN-104/01/2023 and ASN-105/01/2023. Which are identical but one isn’t in DHC and the other one is. \r\n\r\nASN-104/01-23 is done in Vt-381/01/23 and ASN-105/01/2023 is done in VT-380/1/23. Both are closed around the same time.  \r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!!image-1!!image-2!!image-3!!image-4!!image-5!!image-6!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 3: "" !screenshot-1! {code:java}2023-01-26 14:20:02,688 [5] ERROR Evolution.DHCService.Client.PushServiceOrchestrator [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\156434433\\\\\\\\DHAPPSV3-DHCSC25-JOB1\\\\\\\\Evolution.DHCService.Client\\\\\\\\Evolution.DHCService.Client\\\\\\\\PushServiceOrchestrator.cs:41] - Synchronization error. Service PushVehicleTickets is unable to synchronize2023-01-26 14:20:02,689 [5] ERROR Evolution.DHCService.Client.PushServiceOrchestrator [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\156434433\\\\\\\\DHAPPSV3-DHCSC25-JOB1\\\\\\\\Evolution.DHCService.Client\\\\\\\\Evolution.DHCService.Client\\\\\\\\PushServiceOrchestrator.cs:42] - Evolution.DHCService.Client.Exceptions.TransmissionException: Cannot connect to server ---> System.ServiceModel.CommunicationException: There was an error while trying to serialize parameter http://tempuri.org/:package. The InnerException message was \\\'Enum value \\\'16388\\\' is invalid for type \\\'Evolution.DHCService.Contracts.DeliveryStatus\\\' and cannot be serialized. Ensure that the necessary enum values are present and are marked with EnumMemberAttribute attribute if the type has DataContractAttribute attribute.\\\'.  Please see InnerException for more details. ---> System.Runtime.Serialization.SerializationException: Enum value \\\'16388\\\' is invalid for type \\\'Evolution.DHCService.Contracts.DeliveryStatus\\\' and cannot be serialized. Ensure that the necessary enum values are present and are marked with EnumMemberAttribute attribute if the type has DataContractAttribute attribute.   at System.Runtime.Serialization.EnumDataContract.WriteEnumValue(XmlWriterDelegator writer\', \'Comment 4: Object value)   at System.Runtime.Serialization.EnumDataContract.WriteXmlValue(XmlWriterDelegator xmlWriter\', \'Comment 5: Object obj\', \'Comment 6: XmlObjectSerializerWriteContext context)   at System.Runtime.Serialization.XmlObjectSerializerWriteContext.WriteDataContractValue(DataContract dataContract\', \'Comment 7: XmlWriterDelegator xmlWriter\', \'Comment 8: Object obj\', \'Comment 9: RuntimeTypeHandle declaredTypeHandle){code} !screenshot-2! ""\', ""Comment 10: \'Jest jedna taka dostawa z oczekującym VT{code:java}SELECT *  FROM [DHP_NL_PROD].[dbo].[Delivery] where  Del_Status=16388 and del_vteid in(SELECT [Vex_VtEId]        FROM [DHP_NL_PROD].[dbo].[VehicleTicketExport]  where Vex_Ticket is not null){code}del_id=268651\'"", ""Comment 11: \'{code:java}SELECT *--update d--set del_status=4  FROM [DHP_NL_PROD].[dbo].[Delivery] d where  Del_Status=16388 and del_vteid in(SELECT [Vex_VtEId]        FROM [DHP_NL_PROD].[dbo].[VehicleTicketExport]  where Vex_Ticket is not null){code}{code:java}\\\\t  UPDATE R\\\\t SET  RGM_STATUS=4  FROM [DHP_NL_PROD].[dbo].[RegisterMappings] R  WHERE RgM_DelId IN(268651){code}DEL_ID=268445{code:java}UPDATE RSET RgM_Status=4  FROM [DHP_NL_PROD].[dbo].[RegisterMappings] R  WHERE RgM_DelId IN( SELECT Del_ID--update d--set del_status=4  FROM [DHP_NL_PROD].[dbo].[Delivery] d   where  del_vteid in(SELECT [Vex_VtEId]        FROM [DHP_NL_PROD].[dbo].[VehicleTicketExport]  where Vex_Ticket is not null))  AND RgM_Status<>4{code}{code:java}select d.del_id"", ""Comment 12: d.Del_Status --update d--set d.Del_Status=4from dbo.VehicleTicketElementRelease r--inner join dbo.RegisterMappings m on m.rgm_id = r.VeW_RgMIdinner join dbo.Delivery d on d.del_id = r.VeW_DelIdwhere r.VeW_VtEId in (SELECT [Vex_VtEId]        FROM [DHP_NL_PROD].[dbo].[VehicleTicketExport]  where Vex_Ticket is not null)  --and m.RgM_Status <> 4  and d.Del_Status <> 4{code}{code:java}268587update r set RgM_Status=4  FROM [DHP_NL_PROD].[dbo].[RegisterMappings] r  where RgM_DelId in(select distinct d.del_id--update d--set d.Del_Status=4from dbo.VehicleTicketElementRelease r--inner join dbo.RegisterMappings m on m.rgm_id = r.VeW_RgMIdinner join dbo.Delivery d on d.del_id = r.VeW_DelIdwhere r.VeW_VtEId in (SELECT [Vex_VtEId]        FROM [DHP_NL_PROD].[dbo].[VehicleTicketExport]  where Vex_Ticket is not null))  and RgM_Status=16388{code}\'"", ""Comment 13: \'Currently VTs should be synchronized,the reason was wrong status for deliveries.Please check.\'"", ""Comment 14: \'What was the status?To what status is it changed?\'"", ""Comment 15: \'The status of Delivery was changed to Delivery Finished.Please"", ""Comment 16: let us know if it is working fine no for you and we can close this task.Regards\'"", ""Comment 17: \'What is the reason  this went to “wrong status” There is no diference with other VT in DHP\'"", ""Comment 18: \' Wrong status in DHC in Shipping notices?\'"", ""Comment 19: \'Hello"", ""Comment 20: more precisely delivery status from the dhp level - as an ID that is not synchronized to DHC.\'"", ""Comment 21: \'[~piotr.gaczorek@kotrak.com]potrzebujemy na RCA i 8h na analize.\'"", ""Comment 22: \'RCA will be created but developers need 8 working hours for analysis. Please accept.\'"", ""Comment 23: \'There will be costs for this investigation?\'"", ""Comment 24: \'Yes. The costs will be on your side unless it happens it is an application bug"", ""Comment 25: but it seems to be not for now.\'"", ""Comment 26: \'Hello"", \'Comment 27: RCA has been created DGS-8619\', ""Comment 28: but developers need 8 working hours for analysis.We are closing this task.Regards\']""]\nRelated Issues:\n[\'DGS-8619\']\n\n### End'}"
623,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8409\n\n### Instruction:\nI can not delete PI 0645 ID 88376. \r\n\r\nThis is after deleting SI 940. Can you fix this? See error below. Please inform Richard and Nancy also. \n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 3: ""Hello,This Purchase Invoice is on Saldo to Pay\', \'Comment 4: that\\\'s why it\\\'s not possible to delete it from Intense.Firstly Purchase Invoice should be deleted from Saldo to Pay document and then it will be possible to deletePI 0645 ID 88376Please verify and check that is possible.Regards""\', ""Comment 5: \'Thanks"", ""Comment 6: please close this one\']""]\nRelated Issues:\n[]\n\n### End'}"
624,"{'prompt': ""Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8408\n\n### Instruction:\nMeeting on Client request \n\n### Response:\n['Comment 1: []']\nRelated Issues:\n[]\n\n### End""}"
625,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8407\n\n### Instruction:\nHi,\r\nWe have some Job Orders with missing cost of some raw materials (example JO 154/23/tema)\r\n\r\nHow do we fixed them and how do we ensure they don happen again.\r\n\r\nAlso all the cost are the same is there a reason ?\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'!screenshot-1!PLR: 0722200123007!image-2023-01-26-18-16-53-078.png!!image-2023-01-26-18-17-21-294.png!\'"", \'Comment 4: ""Po godzinie stworzenia PLR czyli 11:36{code:java}2023-01-20 11:35:59,853 [14] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateWarehouseMovementReceipt [(null)] - GenerateWarehouseMovementReceipt execution finished2023-01-20 11:35:59,884 [9] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor [(null)] - VehicleTicketProcessor execution finished2023-01-20 11:35:59,884 [9] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.ProductionLotReports.ProductionLotReportProcessor [(null)] - ProductionLotReportProcessor execution started2023-01-20 11:35:59,916 [9] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.ProductionLotReports.ProductionLotReportProcessor [(null)] - ProductionLotReportProcessor execution finished2023-01-20 11:35:59,916 [9] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.WarehouseMovements.WarehouseMovementProcessor [(null)] - WarehouseMovementProcessor execution started2023-01-20 11:35:59,947 [9] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.WarehouseMovements.WarehouseMovementProcessor [(null)] - WarehouseMovementProcessor execution finished2023-01-20 11:36:14,932 [14] DEBUG Evolution.ErpIntegrator.Services.ERP.CdnXL.SoapERPService [(null)] - Recived Trade Document Create or Update message from trigger - 5836922023-01-20 11:36:15,026 [SoapERPService_9] DEBUG Evolution.ErpIntegrator.Services.ERP.CdnXL.SoapERPService [(null)] - Recived Bussines Partner Vendor Item Code message from trigger - 992023-01-20 11:36:15,026 [SoapERPService_9] DEBUG Evolution.ErpIntegrator.Services.ERP.CdnXL.SoapERPService [(null)] - Recived Bussines Partner Vendor Item Code data downloaded - 992023-01-20 11:36:15,026 [SoapERPService_9] DEBUG Evolution.ErpIntegrator.Services.ERP.CdnXL.SoapERPService [(null)] - Sending Bussines Partner Vendor Item Code message - Evolution.ErpIntegrator.CdnXL.Interfaces.Dictionaries.BusinessPartners.XLBusinessPartnerItemCode2023-01-20 11:36:15,042 [SoapERPService_9] DEBUG Evolution.ErpIntegrator.Services.ServiceManager [(null)] - ItemBusinessPartnerCodeChange Message mapping... (ID=ID - -99)2023-01-20 11:36:15,042 [SoapERPService_9] DEBUG Evolution.ErpIntegrator.Services.ServiceManager [(null)] - ItemBusinessPartnerCodeChange Message mapped... (ID=ID - -99)2023-01-20 11:36:15,042 [SoapERPService_9] DEBUG Evolution.ErpIntegrator.Services.ServiceManager [(null)] - ItemBusinessPartnerCodeChange Message sent... (ID=ID - -99)2023-01-20 11:36:15,932 [14] DEBUG Evolution.ErpIntegrator.Services.ERP.CdnXL.SoapERPService [(null)] - Recived Trade Document Create or Update message from trigger - 5836922023-01-20 11:36:23,307 [SoapERPService_13] DEBUG Evolution.ErpIntegrator.Services.ERP.CdnXL.SoapERPService [(null)] - Recived Order message from trigger - ID - 265332023-01-20 11:36:23,369 [SoapERPService_13] DEBUG Evolution.ErpIntegrator.Services.ERP.CdnXL.SoapERPService [(null)] - Order data downloaded - SO-256/23/ATMK2023-01-20 11:36:23,369 [SoapERPService_13] DEBUG Evolution.ErpIntegrator.Services.ERP.CdnXL.SoapERPService [(null)] - Sending Order message - SO-256/23/ATMK2023-01-20 11:36:23,369 [SoapERPService_13] DEBUG Evolution.ErpIntegrator.Services.ServiceManager [(null)] - Order message mapping.... (Firma:1339393 - TYP:960/NUMER:26533/LP:0\', \'Comment 5: SO-256/23/ATMK)2023-01-20 11:36:23,400 [SoapERPService_13] DEBUG Evolution.ErpIntegrator.Services.ServiceManager [(null)] - Order message mapped (Firma:1339393 - TYP:960/NUMER:26533/LP:0\', \'Comment 6: SO-256/23/ATMK)2023-01-20 11:36:23,400 [SoapERPService_13] DEBUG Evolution.ErpIntegrator.Services.ServiceManager [(null)] - Order message send (Firma:1339393 - TYP:960/NUMER:26533/LP:0\', \'Comment 7: SO-256/23/ATMK)2023-01-20 11:36:28,400 [10] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor [(null)] - VehicleTicketProcessor execution started2023-01-20 11:36:28,822 [10] INFO  Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor [(null)] - VehicleTicket - VT-598/12/2022/AC [Id: eb447291-b547-440d-8692-03c7b93d34e7]2023-01-20 11:36:28,822 [10] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor [(null)] - VehicleTicket Validator started - Evolution.ErpIntegrator.Extensions.VTOrderValidator.VehicleTicketOrderValidator2023-01-20 11:36:28,853 [10] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor [(null)] - VehicleTicket Validator finished - Evolution.ErpIntegrator.Extensions.VTOrderValidator.VehicleTicketOrderValidator2023-01-20 11:36:28,932 [14] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateWarehouseMovementReceipt [(null)] - GenerateWarehouseMovementReceipt execution started2023-01-20 11:36:28,978 [14] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2020.Transactions.XLTransaction [(null)] - XL transaction created\', \'Comment 8: token ID - 75-4l-kPc1ORJNhISD]L^M5---.>CM--2023-01-20 11:36:29,010 [14] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateWarehouseMovementReceipt [(null)] - Creating WMR+ element for vte Id: f7fa08ba-027e-456b-9c21-edf094e7d3d2 (1101011 - 29960.000000)2023-01-20 11:36:29,088 [14] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateWarehouseMovementReceipt [(null)] - Found 0 WMR- () for order IO-3879/222023-01-20 11:36:29,103 [14] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2020.Transactions.XLTransaction [(null)] - XL transaction rollbacked\', ""Comment 9: token ID - 75-4l-kPc1ORJNhISD]L^M5---.>CM--2023-01-20 11:36:29,103 [14] DEBUG Evolution.ErpIntegrator.DHC.DHC30.Database.DhcTransaction [(null)] - DHC transaction rollback staeted2023-01-20 11:36:29,103 [14] DEBUG Evolution.ErpIntegrator.DHC.DHC30.Database.DhcTransaction [(null)] - DHC transaction rollback finished2023-01-20 11:36:29,119 [14] ERROR Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateWarehouseMovementReceipt [(null)] - Can\'t find WMR- document to map to WMR+Evolution.ErpIntegrator.ERP.Interfaces.Exceptions.WarehouseMovementReleaseNotMappedException: Can\'t find WMR- document to map to WMR+   at Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateWarehouseMovementReceipt.MapWarehouseMovementRelease(VehicleTicket vehicleTicket"", \'Comment 10: InternalOrder internalOrder\', \'Comment 11: WarehouseMovementReceipt warehouseMovementReceipt)   at Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateWarehouseMovementReceipt.OnExecute(VehicleTicket vehicleTicket)2023-01-20 11:36:29,150 [14] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateWarehouseMovementReceipt [(null)] - GenerateWarehouseMovementReceipt execution finished2023-01-20 11:36:29,150 [10] INFO  Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor [(null)] - VehicleTicket - VT-261/1/2023/AC [Id: c8d31e77-918c-40ee-b1a6-0870c1913538]2023-01-20 11:36:29,150 [10] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor [(null)] - VehicleTicket Validator started - Evolution.ErpIntegrator.Extensions.VTOrderValidator.VehicleTicketOrderValidator2023-01-20 11:36:29,182 [10] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor [(null)] - VehicleTicket Validator finished - Evolution.ErpIntegrator.Extensions.VTOrderValidator.VehicleTicketOrderValidator2023-01-20 11:36:29,307 [15] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateWarehouseMovementReceipt [(null)] - GenerateWarehouseMovementReceipt execution started2023-01-20 11:36:29,338 [15] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2020.Transactions.XLTransaction [(null)] - XL transaction created\', \'Comment 12: token ID - YZ8I-b`ET1ShDdNkEeUDf-5---/VH=--2023-01-20 11:36:29,385 [15] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateWarehouseMovementReceipt [(null)] - Creating WMR+ element for vte Id: f805aed1-6403-4e89-9b0d-b3d1129ebaf3 (1002200 - 9000.000000)2023-01-20 11:36:29,447 [15] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateWarehouseMovementReceipt [(null)] - Found 0 WMR- () for order IO-82/232023-01-20 11:36:29,447 [15] DEBUG Evolution.ErpIntegrator.DHC.DHC30.Database.DhcTransaction [(null)] - DHC transaction rollback staeted2023-01-20 11:36:29,463 [15] DEBUG Evolution.ErpIntegrator.DHC.DHC30.Database.DhcTransaction [(null)] - DHC transaction rollback finished2023-01-20 11:36:29,463 [15] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2020.Transactions.XLTransaction [(null)] - XL transaction rollbacked\', ""Comment 13: token ID - YZ8I-b`ET1ShDdNkEeUDf-5---/VH=--2023-01-20 11:36:29,478 [15] ERROR Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateWarehouseMovementReceipt [(null)] - Can\'t find WMR- document to map to WMR+Evolution.ErpIntegrator.ERP.Interfaces.Exceptions.WarehouseMovementReleaseNotMappedException: Can\'t find WMR- document to map to WMR+   at Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateWarehouseMovementReceipt.MapWarehouseMovementRelease(VehicleTicket vehicleTicket"", \'Comment 14: InternalOrder internalOrder\', \'Comment 15: WarehouseMovementReceipt warehouseMovementReceipt)   at Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateWarehouseMovementReceipt.OnExecute(VehicleTicket vehicleTicket){code}""\', \'Comment 16: ""Hi,Probably JO was reopened\', ""Comment 17: questioned itam was added (but lack of price hasn\'t been noticed) and documents of internal release were generated. To solve this case"", \'Comment 18: you can use function Settlinig Job Order - the price has been corrected. Closin JO also should correct the price of additionally added item.Regards!image-2023-01-30-10-00-24-610.png!""\', ""Comment 19: \'Thank you.It worked Kindly close the ticket\'"", ""Comment 20: \'Thank you\'"", ""Comment 21: \'Hi"", ""Comment 22: have a JO with the same issue but the procedure would not work for this.\'"", ""Comment 23: \'Kindly open and let us resolve it  JO 238/23/TEMA\'"", ""Comment 24: \'Hi,Please"", ""Comment 25: create new task for this issue. Thank you in advance.Regards\']""]\nRelated Issues:\n[]\n\n### End'}"
626,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8406\n\n### Instruction:\nPlease help to check PLR 4361170123050 in Hai Phong Plant ( 0436) .\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: ""Według historii  !screenshot-1! zostało przyjęte 975kg\', \'Comment 4: potem wydane x2 i przyjęta różnica - JORDYN:{code:java}SELECT      [Created]      ,[Event]      ,[EventType]      ,[UserName]  FROM [DHPlantStockBusinessLogicEvents].[dbo].[StockUnits] where AggregateId=\\\'0EC7F20D-41CA-49C6-A835-9C06D4ED072A\\\'  order by created{code} !screenshot-2!  !screenshot-3!  !screenshot-4! !image-2023-01-26-07-49-38-211!""\', ""Comment 5: \'A delivery for PLR was created"", ""Comment 6: then issued for the following releases:-518,089kg-95,238kgThen operator JORDYN made another intake in relation to this delivery(created from this PLR) for 613,327.You can see it here !screenshot-5! \'"", ""Comment 7: \'May you help more specific steps how to do that?if as your motioned below"", ""Comment 8: we will Pre-produce that and make user avoid mistake\'"", ""Comment 9: \'Hello"", ""Comment 10: in reference to the answer additional changes have been made in the application version 8.3 that should prevent this type of situations.\'"", ""Comment 11: \'Hi Piotr GaczorekYou can closed this ticket. Thank u .\']""]\nRelated Issues:\n[]\n\n### End'}"
627,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8405\n\n### Instruction:\nWe have 2 sales order duplicated on DHC. We notice the status was not updated to DHP, so we sent again the sale order, but now we have 2 lines for the same SO. \r\nOVE-052063\r\nOVE-028066\r\nCould you check why sytem duplicated the SO and didn\'t updated the version?\r\n\r\nThank you\r\n\r\n\r\n\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!!image-1!\'"", ""Comment 2: \'sorry"", \'Comment 3: I added wrong\', \'Comment 4: not update the version\', ""Comment 5: but update the sales order status.\'"", ""Comment 6: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 7: \'Różnica w mapowaniu dla ErpIDCompany !screenshot-1!  !screenshot-2! \'"", ""Comment 8: \'Hello"", \'Comment 9: orders have now CompanyID\', ""Comment 10: looks like currently a field is sent from ERP - have there been any changes? !screenshot-4! these two orders previously had ERPidcompany=10!image-2023-01-26-13-54-33-498!\'"", \'Comment 11: ""Hello Piotr,these orders were created more than a year ago\', \'Comment 12: so maybe yes\', \'Comment 13: we had some integration update. Could you fix the status because if integration changed we can\\\'t update?OVE-052063 CancelledOVE-028066 Executed""\', ""Comment 14: \'I changed the status for orders in DHC & sent them to plant"", ""Comment 15: please check.\'"", ""Comment 16: \'Could you please confirm if we can close this task?Regards\'"", \'Comment 17: ""Hi Piotr,I checked and it\\\'s correct. Thank you.""\', ""Comment 18: \'Hi Priscyla"", ""Comment 19: thank you for confirmation.\']""]\nRelated Issues:\n[]\n\n### End'}"
628,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8404\n\n### Instruction:\n W dhc zalega vt-1763/1/2023/G oraz  vt-1679\r\nvt-1769 posiada taki komunikat Komunikat” Error of type XLApiException has been thrown (XLNowyDokument:2017).\r\n\r\nAPI Name - XLNowyDokument\r\n\r\nAPI Result - 2017\r\n\r\nFlags - 240\r\n\r\nBŁĘDY:|Błąd konwersji/generowania subelementu: [00001 DT219X02S-W00] Zabrakło ilości (nie udało się pobrać towaru lub wymuszono realizacje całości). (NowyDokument-17)”\r\n\r\nNatomiast vt-1679 posiada : Error of type XLApiException has been thrown (XLNowyDokument:2017).\r\nAPI Name - XLNowyDokument\r\nAPI Result - 2017\r\nFlags - 240\r\nBŁĘDY:|Błąd konwersji/generowania subelementu: [00001 0551] Zabrakło ilości (nie udało się pobrać towaru lub wymuszono realizacje całości). (NowyDokument-17)\r\n\r\nIlosci z ZW w CDN z tym co jest w DHC zgadzaja sie . Nie widac tez zadnych rezerwacji które blokowaly by towar.\r\n\r\nProsba o weryfikacje i rozwiazanie problemu\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Hello,Kindly approve lowering priority of this task to P2 as P1 issues are only those with a critical or a blocking impact on business processes . This seems not to be the case in this issue so we suggest decreasing the issue priority.Regards\'"", ""Comment 3: \'Ok but please correct this vt today\'"", ""Comment 4: \'Sure"", ""Comment 5: working on it. Thank you\'"", ""Comment 6: \'{code:java}2023-01-25 18:34:51,385 [34] INFO  Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor [(null)] - VehicleTicket - VT-1763/1/2023/G [Id: c68225ae-adbf-4cf6-9d94-61690e57546f]2023-01-25 18:34:51,385 [34] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor [(null)] - VehicleTicket Validator started - Evolution.ErpIntegrator.Extensions.VTOrderValidator.VehicleTicketOrderValidator2023-01-25 18:34:51,401 [34] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor [(null)] - VehicleTicket Validator finished - Evolution.ErpIntegrator.Extensions.VTOrderValidator.VehicleTicketOrderValidator2023-01-25 18:34:51,668 [13] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateWarehouseMovementReceipt [(null)] - GenerateWarehouseMovementReceipt execution started2023-01-25 18:34:51,889 [13] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2021.Transactions.XLTransaction [(null)] - XL transaction created"", \'Comment 7: token ID - PVY8cX5VHQ;YjVi`^VEN9=5---.hE]--2023-01-25 18:34:51,920 [13] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateWarehouseMovementReceipt [(null)] - Creating WMR+ element for vte Id: 6195b8b8-b779-4b95-8bbe-3dfd92a75d33 (DT219X02S-W00 - 0,125000)2023-01-25 18:34:51,920 [13] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateWarehouseMovementReceipt [(null)] - Creating WMR+ element for vte Id: 6250c1b2-5fd5-4fb4-8120-1387fd7a7a7b (DT219X02S-W00 - 0,925000)2023-01-25 18:34:51,920 [13] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateWarehouseMovementReceipt [(null)] - Creating WMR+ element for vte Id: 7dc34b1f-96ae-467f-b2af-8c8434503610 (DB0B1X00S-V00 - 3,000000)2023-01-25 18:34:51,935 [13] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateWarehouseMovementReceipt [(null)] - Creating WMR+ element for vte Id: a30d4c74-e8a3-41ad-8f77-deba52ed75bb (DB0A1X00S-V00 - 7,000000)2023-01-25 18:34:51,935 [13] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateWarehouseMovementReceipt [(null)] - Creating WMR+ element for vte Id: dfbc4a2e-3e92-4b4b-94ba-02beb1563fb9 (DB0A1X00S-V00 - 3,000000)2023-01-25 18:34:51,935 [13] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateWarehouseMovementReceipt [(null)] - Creating WMR+ element for vte Id: e49b9a60-54d3-4b15-a520-dd0ffa18db3f (DT1D4X00G-W00 - 6,000000)2023-01-25 18:34:51,967 [13] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateWarehouseMovementReceipt [(null)] - Found only one WMR- (MMW-127/01/23/M) for order ZW-176/01/23/G2023-01-25 18:34:51,967 [13] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateWarehouseMovementReceipt [(null)] - Maping to WMR- MMW-127/01/23/M [ID = Firma:246785 - TYP:1603/NUMER:12707009/LP:0]2023-01-25 18:34:51,967 [13] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2021.LoginHelper [(null)] - Changing context to 14322023-01-25 18:34:57,795 [13] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2021.LoginHelper [(null)] - Contex changed to 14322023-01-25 18:34:57,795 [13] DEBUG Evolution.ErpIntegrator.CdnXL.Interfaces.Documents.ExternalOrderTransactions.XLAPIExternalOrderTransaction [(null)] - NB Flag - Class = Net\', ""Comment 8: API = N2023-01-25 18:34:59,323 [13] ERROR Evolution.ErpIntegrator.CdnXL.CdnXL2021.Documents.ExternalOrderTransactions.CdnXL2021ExternalOrderTransactionRepository [(null)] - Error of type Evolution.ErpIntegrator.CdnXL.CdnXL2021.XLApiException has been thrown (XLNowyDokument:2017).API Name - XLNowyDokumentAPI Result - 2017{code}\'"", ""Comment 9: \'{code:java}2023-01-25 18:25:35,644 [62] INFO  Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor [(null)] - VehicleTicket - VT-1679/1/2023/G [Id: d00f4aff-b4bc-414f-91b1-113abd617e07]2023-01-25 18:25:35,644 [62] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor [(null)] - VehicleTicket Validator started - Evolution.ErpIntegrator.Extensions.VTOrderValidator.VehicleTicketOrderValidator2023-01-25 18:25:35,660 [62] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor [(null)] - VehicleTicket Validator finished - Evolution.ErpIntegrator.Extensions.VTOrderValidator.VehicleTicketOrderValidator2023-01-25 18:25:35,738 [34] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateWarehouseMovementReceipt [(null)] - GenerateWarehouseMovementReceipt execution started2023-01-25 18:25:35,785 [34] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2021.Transactions.XLTransaction [(null)] - XL transaction created"", \'Comment 10: token ID - cQYDUi5OVAO_USkcM=_76M5----kE---2023-01-25 18:25:35,832 [34] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateWarehouseMovementReceipt [(null)] - Creating WMR+ element for vte Id: c0ff0ed2-3151-4762-952a-e6fde6281d64 (0551 - 22,020000)2023-01-25 18:25:35,863 [34] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateWarehouseMovementReceipt [(null)] - Found only one WMR- (MMW-88/01/23/S) for order ZW-168/01/23/G2023-01-25 18:25:35,863 [34] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateWarehouseMovementReceipt [(null)] - Maping to WMR- MMW-88/01/23/S [ID = Firma:246785 - TYP:1603/NUMER:12702815/LP:0]2023-01-25 18:25:35,863 [34] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2021.LoginHelper [(null)] - Changing context to 14322023-01-25 18:25:41,328 [34] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2021.LoginHelper [(null)] - Contex changed to 14322023-01-25 18:25:41,328 [34] DEBUG Evolution.ErpIntegrator.CdnXL.Interfaces.Documents.ExternalOrderTransactions.XLAPIExternalOrderTransaction [(null)] - NB Flag - Class = Net\', \'Comment 11: API = N2023-01-25 18:25:42,219 [34] ERROR Evolution.ErpIntegrator.CdnXL.CdnXL2021.Documents.ExternalOrderTransactions.CdnXL2021ExternalOrderTransactionRepository [(null)] - Error of type Evolution.ErpIntegrator.CdnXL.CdnXL2021.XLApiException has been thrown (XLNowyDokument:2017).API Name - XLNowyDokumentAPI Result - 2017Flags - 240BĊDY:|Bӹd konwersji/generowania subelementu: [00001 0551] Zabrakԯ iloݣi (nie udaԯ siꡰobra桴owaru lub wymuszono realizacje caԯݣi). (NowyDokument-17)   at Evolution.ErpIntegrator.CdnXL.CdnXL2021.Documents.ExternalOrderTransactions.CdnXL2021ExternalOrderTransactionRepository.CreateHeader(XLExternalOrderTransaction documentHeader) in C:\\\\\\\\TeamCity\\\\\\\\buildAgent\\\\\\\\work\\\\\\\\57a7e278b67a115c\\\\\\\\Evolution.ErpIntegrator\\\\\\\\CdnXL\\\\\\\\Evolution.ErpIntegrator.CdnXL.CdnXL2021\\\\\\\\Documents\\\\\\\\ExternalOrderTransactions\\\\\\\\CdnXL2021ExternalOrderTransactionRepository.cs:line 792023-01-25 18:25:42,219 [34] DEBUG Evolution.ErpIntegrator.DHC.DHC30.Database.DhcTransaction [(null)] - DHC transaction rollback staeted2023-01-25 18:25:42,219 [34] DEBUG Evolution.ErpIntegrator.DHC.DHC30.Database.DhcTransaction [(null)] - DHC transaction rollback finished2023-01-25 18:25:42,219 [34] ERROR Evolution.ErpIntegrator.CdnXL.CdnXL2021.Transactions.XLTransaction [(null)] - XL rollback error - possibly no transactionError of type Evolution.ErpIntegrator.CdnXL.CdnXL2021.XLApiException has been thrown (XLTransakcja - Rollback:-1).API Name - XLTransakcja - RollbackAPI Result - -12023-01-25 18:25:42,219 [34] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2021.Transactions.XLTransaction [(null)] - XL transaction rollbacked\', \'Comment 12: token ID - cQYDUi5OVAO_USkcM=_76M5----kE---2023-01-25 18:25:42,250 [34] ERROR Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateWarehouseMovementReceipt [(null)] - Error of type XLApiException has been thrown (XLNowyDokument:2017).API Name - XLNowyDokumentAPI Result - 2017Flags - 240BĊDY:|Bӹd konwersji/generowania subelementu: [00001 0551] Zabrakԯ iloݣi (nie udaԯ siꡰobra桴owaru lub wymuszono realizacje caԯݣi). (NowyDokument-17)Error of type Evolution.ErpIntegrator.CdnXL.CdnXL2021.XLApiException has been thrown (XLNowyDokument:2017).API Name - XLNowyDokumentAPI Result - 2017Flags - 240BĊDY:|Bӹd konwersji/generowania subelementu: [00001 0551] Zabrakԯ iloݣi (nie udaԯ siꡰobra桴owaru lub wymuszono realizacje caԯݣi). (NowyDokument-17)   at Evolution.ErpIntegrator.CdnXL.CdnXL2021.Documents.ExternalOrderTransactions.CdnXL2021ExternalOrderTransactionRepository.CreateHeader(XLExternalOrderTransaction documentHeader) in C:\\\\\\\\TeamCity\\\\\\\\buildAgent\\\\\\\\work\\\\\\\\57a7e278b67a115c\\\\\\\\Evolution.ErpIntegrator\\\\\\\\CdnXL\\\\\\\\Evolution.ErpIntegrator.CdnXL.CdnXL2021\\\\\\\\Documents\\\\\\\\ExternalOrderTransactions\\\\\\\\CdnXL2021ExternalOrderTransactionRepository.cs:line 167   at Evolution.ErpIntegrator.CdnXL.CdnXL2021.Documents.WarehouseMovements.CdnXL2021WarehouseMovementReceiptRepository.CreateHeader(XLWarehouseMovementReceipt warehouseMovementReceipt) in C:\\\\\\\\TeamCity\\\\\\\\buildAgent\\\\\\\\work\\\\\\\\57a7e278b67a115c\\\\\\\\Evolution.ErpIntegrator\\\\\\\\CdnXL\\\\\\\\Evolution.ErpIntegrator.CdnXL.CdnXL2021\\\\\\\\Documents\\\\\\\\WarehouseMovements\\\\\\\\CdnXL2021WarehouseMovementReceiptRepository.cs:line 256   at Evolution.ErpIntegrator.CdnXL.CdnXL2021.Documents.WarehouseMovements.CdnXL2021WarehouseMovementReceiptRepository.CreateDocumentWithElements(XLWarehouseMovementReceipt warehouseMovementReceipt\', \'Comment 13: Boolean confirmDoc\', \'Comment 14: Boolean forceQuantity) in C:\\\\\\\\TeamCity\\\\\\\\buildAgent\\\\\\\\work\\\\\\\\57a7e278b67a115c\\\\\\\\Evolution.ErpIntegrator\\\\\\\\CdnXL\\\\\\\\Evolution.ErpIntegrator.CdnXL.CdnXL2021\\\\\\\\Documents\\\\\\\\WarehouseMovements\\\\\\\\CdnXL2021WarehouseMovementReceiptRepository.cs:line 0   at Evolution.ErpIntegrator.CdnXL.CdnXL2021.Documents.WarehouseMovements.CdnXL2021WarehouseMovementReceiptRepository.CreateDocumentWithElements(WarehouseMovementReceipt warehouseMovementReceipt\', \'Comment 15: Boolean confirmDoc\', ""Comment 16: Boolean forceQuantity) in C:\\\\\\\\TeamCity\\\\\\\\buildAgent\\\\\\\\work\\\\\\\\57a7e278b67a115c\\\\\\\\Evolution.ErpIntegrator\\\\\\\\CdnXL\\\\\\\\Evolution.ErpIntegrator.CdnXL.CdnXL2021\\\\\\\\Documents\\\\\\\\WarehouseMovements\\\\\\\\CdnXL2021WarehouseMovementReceiptRepository.cs:line 233   at Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateWarehouseMovementReceipt.OnExecute(VehicleTicket vehicleTicket)2023-01-25 18:25:42,281 [34] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateWarehouseMovementReceipt [(null)] - GenerateWarehouseMovementReceipt execution finished2023-01-25 18:25:42,281 [62] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor [(null)] - VehicleTicket Extension started - VT-1679/1/2023/G [Id: d00f4aff-b4bc-414f-91b1-113abd617e07] Evolution.ErpIntegrator.Extensions.PackagesAndShipments.PackagesAndShipmentGenerator2023-01-25 18:25:42,281 [62] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Interfaces.ExtensionsHelper [(null)] - Package generation skipped - no POR/PORI documents found VT-1679/1/2023/G2023-01-25 18:25:42,281 [62] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor [(null)] - VehicleTicket Extension completed - VT-1679/1/2023/G [Id: d00f{code}\'"", ""Comment 17: \'VT-1763/1/2023/GNa pozycji zamówienia jest mniejsza ilość niż na mmp!image-2023-01-25-19-07-39-646.png!!image-2023-01-25-19-08-12-949.png!!image-2023-01-25-19-09-00-832.png!\'"", ""Comment 18: \'vt-1679Na dostawach jest:!image-2023-01-25-19-22-22-916.png!Co daje 22,02. Czyli więcej niż na zamówieniu. Do weryfikacji.!image-2023-01-25-19-12-47-259.png!!image-2023-01-25-19-13-41-237.png!!image-2023-01-25-19-14-29-241.png!\'"", ""Comment 19: \'W ZW - 168  jest zadeklarowane 25 t czyli wiecej niz na dostawach \'"", ""Comment 20: \'Skoro jest więcej niż na dostawach / zasobach (w XLu są tylko te dwie dostawy dla tego towaru)"", ""Comment 21: to skąd ma pobrać?\'"", ""Comment 22: \'Ok ilosc na ZW została skorygowana - błąd pojawia sie nadal\'"", ""Comment 23: \'Na ZW ilosc moze byc wieksza niz na vt. Nie moze byc mniejsza.\'"", ""Comment 24: \'1763 jest już generated!image-2023-01-26-12-25-27-769.png!\'"", ""Comment 25: \'Jeśli chodzi o vt-1679"", ""Comment 26: potrzebujemy zrobić ręcznie dokument MMP z poziomu XLa i spiąć go od strony bazy.Proszę o akceptację\'"", ""Comment 27: \'ok"", ""Comment 28: działajcie,\'"", ""Comment 29: \'Jeśli chodzi o vt-1679"", \'Comment 30: element jest anulowany\', ""Comment 31: przywrócić go i podpiąć MMP? MMP zostało wygenerowane do MMW!image-2023-01-27-12-47-29-448.png!\'"", \'Comment 32: ""{code:java}SELECT * FROM [Evolution_DHCountry].[dbo].[VehicleTicketElementERPDocuments] where VehicleTicketElementId = \\\'C0FF0ED2-3151-4762-952A-E6FDE6281D64\\\'  or VehicleTicketElementId = \\\'0938DB7A-90F8-40C5-A761-533F284ACF74\\\'select Status\', ""Comment 33: * from VehicleTickets where DocumentNumber = \'1679/1/2023/g\' or DocumentNumber = \'1153/1/2023/s\'select * from VehicleTicketElements where VehicleTicketId in (\'D00F4AFF-B4BC-414F-91B1-113ABD617E07\'"", \'Comment 34: \\\'963560FA-3D77-4814-9FC3-24363F22B980\\\'){code}""\', ""Comment 35: \'Jeśli chodzi o vt-1679"", \'Comment 36: element jest anulowany\', ""Comment 37: przywrócić go i podpiąć MMP? MMP zostało wygenerowane do MMW\'"", ""Comment 38: \'Jeśli chodzi o vt-1679"", \'Comment 39: element jest anulowany\', ""Comment 40: przywrócić go i podpiąć MMP? MMP zostało wygenerowane do MMW\'"", ""Comment 41: \'Any feedback?\'"", ""Comment 42: \'Tak podepnij prosze\'"", ""Comment 43: \'Gotowe. Proszę o weryfikację.\'"", ""Comment 44: \'Task to close\']""]\nRelated Issues:\n[]\n\n### End'}"
629,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8403\n\n### Instruction:\nSince recently, we automatically see the SR\'s behind the Onbase link automatically, great! However, I have 2 questions remaining because in the first place, the SR that is showed is quite small: \r\n1. Can the note section, right to the SR, be hidden automatically, because there never is a note?\r\n2. Could the square where the SR is shown be a bit bigger? Together with the hide of the note section, the SR can be bigger from the first moment, without having to zoom in? \r\n\r\nThis modification (if possible) would be for both MAS BE and MAS NL (Mitch\'s demand)\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 [~SDriesen@deheus.com],regarding your question\', ""Comment 4: the answers below:1. The note section is part of OneBase functionality. We can\'t set default view for that"", ""Comment 5: because it is works just as web browser.2. We can\'t change size"", \'Comment 6: because in the views on documents we can only use predefinied layouts. Used layout on SR is splited by three identical size area without possible to change width.!image-2023-01-30-13-27-53-660.png!Best regards,Grzegorz""\', ""Comment 7: \'Hello Grzegorz"", \'Comment 8: pity that this is not possible\', ""Comment 9: but understandable reading your explanation. thank you for the update.\'"", \'Comment 10: ""[~SDriesen@deheus.com],thank you. Have a nice day.I\\\'m closing the task.Best regards,Grzegorz""]\']\nRelated Issues:\n[\'DGS-8317\']\n\n### End'}"
630,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8402\n\n### Instruction:\nThe VT of this call-off is closed, but it is not received in the ERP: Can you check if it\'s synced to DHC and ERP and check what goes wrong? Thanks\n\n### Response:\n[""Comment 1: [\'!afbeelding-1!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'!image-2023-01-25-15-13-43-401.png!\'"", ""Comment 4: \'Header:!image-2023-01-25-15-24-42-359.png!!image-2023-01-25-15-22-16-329.png!!image-2023-01-25-15-24-42-359!\'"", ""Comment 5: \'!image-2023-01-25-15-25-05-946.png!\'"", ""Comment 6: \'Dear Thomas,I have resent this Shipping Notice"", \'Comment 7: but I can see status both in DHP and DHC is accepted. Is that correct?!image-2023-01-25-15-42-29-455.png!!image-2023-01-25-15-42-47-754.png!Please\', ""Comment 8: verify if ASN arrived to Milas.Regards\'"", ""Comment 9: \'VT-436 for this ASN"", \'Comment 10: in DHC has staus hold. Probably this stops from arriving. Please\', ""Comment 11: check VT!image-2023-01-25-15-48-09-953.png!\'"", \'Comment 12: ""VT\\\'s are all getting status hold\', \'Comment 13: I guess it\\\'s not related? Resending unfortunately didn\\\'t solve the problem""\', ""Comment 14: \'!image-2023-01-25-17-01-24-421.png!\'"", ""Comment 15: \'Please"", ""Comment 16: check now and let me know if documents arrived to MilasRegards\'"", ""Comment 17: \'[[DHC] PONOWNE WYSŁANIE VT DO MILAS|onenote:https://kotrak.sharepoint.com/sites/erpasysta/Shared%20Documents/Baza%20wiedzy/Baza%20Wiedzy%20-%20ERPSD/Klienci/DEHEUS/DEHEUS%20APPLICATIONS/Holandia%20Premix%20i%20AS400/Baz%20wiedzy%20z%20AS400.one#%5bDHC%5d%20PONOWNE%20WYS%C5%81ANIE%20VT%20DO%20MILAS&section-id=\\\\\\\\{9BB564BA-0B58-4580-B9E0-F3CF9D6D80A7}&page-id=\\\\\\\\{4EBEDAA7-0DC4-410F-A617-93B6B59B31B6}&end] ([Widok sieci Web|https://kotrak.sharepoint.com/sites/erpasysta/_layouts/OneNote.aspx?id=%2Fsites%2Ferpasysta%2FShared%20Documents%2FBaza%20wiedzy%2FBaza%20Wiedzy%20-%20ERPSD&wd=target%28Klienci%2FDEHEUS%2FDEHEUS%20APPLICATIONS%2FHolandia%20Premix%20i%20AS400%2FBaz%20wiedzy%20z%20AS400.one%7C9BB564BA-0B58-4580-B9E0-F3CF9D6D80A7%2F%5BDHC%5D%20PONOWNE%20WYS%C5%81ANIE%20VT%20DO%20MILAS%7C4EBEDAA7-0DC4-410F-A617-93B6B59B31B6%2F%29])\'"", ""Comment 18: \'Hi,Please"", ""Comment 19: check now and let me know if documents arrived to MilasRegards\'"", \'Comment 20: ""I think we found the reason now why it\\\'s not arriving. Ticket can be closed""\', ""Comment 21: \'Thank you.Regards\']""]\nRelated Issues:\n[]\n\n### End'}"
631,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8401\n\n### Instruction:\nHi\r\nUrgent from Aneta\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Dzień dobry,Proszę o wskazanie w ramach jakiego szablonu zestawienia są wyliczane i za jaki okres obrachunkowy (cały 2022 czy częściowy)?Dodatkowo"", \'Comment 3: czy zanim pojawił się problem z przeliczaniem zestawień\', ""Comment 4: czy były dokonywane jakieś modyfikacje w ramach szablonu lub definicji pozycji w ramach wskazanego zestawienia?Pozdrawiam\'"", ""Comment 5: \'Please verify if now working faster\'"", ""Comment 6: \'Otrzymałam właśnie informację"", ""Comment 7: że zgłoszenie zostało rozwiązane w ramach DGS-8400.Proszę po potwierdzeniePozdrawiam\'"", ""Comment 8: \'tak"", ""Comment 9: Aneta dzwoniła że ruszyło\'"", ""Comment 10: \'To zamykamy?\'"", ""Comment 11: \'czekam na potwierdzenie od Anety\'"", ""Comment 12: \'!image-1!\'"", ""Comment 13: \'Jakie indeksy zostały dodane? \'"", ""Comment 14: \'tabela[CDNXL_DEHEUS].[CDN].[Stany]missing_index_3609402_3609401 missing_index_3609404_3609403\']""]\nRelated Issues:\n[]\n\n### End'}"
632,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8400\n\n### Instruction:\nHi\r\n\r\nTask from Iwona\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'According to call with Emlia Markiewicz she has been informed how to coorrect definitions of reports. Can I close this issue?\'"", ""Comment 3: \'yep"", ""Comment 4: to close. Many thanks.\']""]\nRelated Issues:\n[]\n\n### End'}"
633,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8399\n\n### Instruction:\nWe would like to send the Financial Statement and Saldo-2-Pay with one click in Outlook. Preferebly directly to the right representative.\r\n\r\nCould we think of a functionality about this?\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 2: ""Hello\', \'Comment 3: # We could think about some solution maybe like this:From Saldo to pay document it could be possible to execute action (button or from lightning) and printout for S2P and Financial statement will be generated in .pdf files and attached to S2P document in Intense. Then Intense will open preview window like e-mail message and user can preview message and edit all data: Subject\', \'Comment 4: e-mail\', ""Comment 5: attachments (e-mail will be filled from customer card where is e-mail address). After editing and confirming in this winow and clicks \'Send\' button"", ""Comment 6: e-mail with attachments will be sent.This solution requires configuration of e-mail or e-mails (depending from which e-mail adresses should it be sent) in Intense. There could be also some issues when there is politics of changing password in De Heus (when password is changed we need also change password in Intense configuration). # There is also some option to make printout and printout will be attached to e-mail and message will open in Outlook application.In these case when users working on terminal and there is no Outlook application it will be useless becasue it couldn\'t be possible to open Outlook.In each case we should verify details of the solution and how to handle it"", \'Comment 7: but we can think about some solution.""\', ""Comment 8: \'Because of e-mail password changes I prefer the second option.Can we meet for this next Friday?\'"", \'Comment 9: ""Yes\', ""Comment 10: we can meet on next friday. It could be hard to do 2nd option if users don\'t have Outlook on terminal"", \'Comment 11: but we can see what could be possible. I\\\'ll try to show possibilites in Intense with e-mail sending.""\', \'Comment 12: ""After meeting confirmed that should be realized 1st option on test environment.{quote} # We could think about some solution maybe like this:From Saldo to pay document it could be possible to execute action (button or from lightning) and printout for S2P and Financial statement will be generated in .pdf files and attached to S2P document in Intense. Then Intense will open preview window like e-mail message and user can preview message and edit all data: Subject\', \'Comment 13: e-mail\', ""Comment 14: attachments (e-mail will be filled from customer card where is e-mail address). After editing and confirming in this winow and clicks \'Send\' button"", \'Comment 15: e-mail with attachments will be sent.This solution requires configuration of e-mail or e-mails (depending from which e-mail adresses should it be sent) in Intense. There could be also some issues when there is politics of changing password in De Heus (when password is changed we need also change password in Intense configuration).{quote}We need information about: * e-mail template which should be generated and sent to customer * e-mail accounts for users - should it be sent always from one global mail account like [intense@deheus.com|mailto:intense@deheus.com]or each user should have configured in Intense individual mail account (in case if there will be individual mail accounts for each user and password for this e-mail changes\', \'Comment 16: it will be needed to change password for e-mail account in Intense also)""\', ""Comment 17: \'[nldierenadministratie@deheus.com|mailto:nldierenadministratie@deheus.com] (ask for password to Martijn)Email template:Beste klant,Bij deze ontvangt u de afrekening. In de bijlage een technisch overzicht van het koppel en de betalingsspecificatie.Bij vragen of opmerkingen kunt u contact opnemen met de specialist.Met vriendelijke groeten,De dierenadministratiePlease analyse the possibilities for translation.\']""]\nRelated Issues:\n[\'DGS-7649\']\n\n### End'}"
634,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8398\n\n### Instruction:\nIs it possible to see the job orders from which an SOR picks its stock quantity from? if yes how?\n\n### Response:\n[""Comment 1: [\'Can you be more specific about this request?JO takes resources from delivery documents created from receipts by PLR and VT.SOR documents are generated for VT releases.\'"", ""Comment 2: \'Yes so basically what i am trying to say is for example"", ""Comment 3: the job order with number JO 1/23 is for 7700-B50 with quantity 1000kg and an SO has been created to sell 7700-b50 is there a way to find out if the SOR document from the SO can show whether the quantity for 7700-b50 was consumed from JO 1/23\'"", ""Comment 4: \'please stop working on this and close\']""]\nRelated Issues:\n[]\n\n### End'}"
635,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8397\n\n### Instruction:\nShipping Notice 98_L000112306 is in DHC but isn\'t arriving in DHP. Can you please check? \n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'!image-2023-01-25-10-04-26-677.png!\'"", ""Comment 3: \'!image-2023-01-25-10-07-02-201.png!\'"", ""Comment 4: \'This SN is in DHP but Executiondateis set to the year 1900 - can it be corrected?!image-2023-01-25-10-12-56-494.png!\'"", \'Comment 5: ""Hi Piotr\', ""Comment 6: thanks for your reply. It\'s strange"", \'Comment 7: because nowhere is date 1/1/1900 communicated. I have exported the SN again\', \'Comment 8: let\\\'s see what  happens""\', ""Comment 9: \'I see the date is now correct in DHC\'"", ""Comment 10: \'And now it is in DHP as well. Thanks"", ""Comment 11: you can close this request.\'"", ""Comment 12: \'Thank you for confirmation.\']""]\nRelated Issues:\n[]\n\n### End'}"
636,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8396\n\n### Instruction:\nHello,\r\n\r\nHow can i delete multiple accounts from the charts of accounts?\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Hello,Unfortunatelly"", \'Comment 3: it is not possible to delete multiple accounts with one click. You need to delete accounts one by one starting from the lowest level for example:!image-2023-01-24-19-03-03-965.png!What is more\', \'Comment 4: if there are some settlements in current period for this account\', ""Comment 5: the system will not allow you to delete the account.Regards\'"", ""Comment 6: \'Thank you please\']""]\nRelated Issues:\n[]\n\n### End'}"
637,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8395\n\n### Instruction:\ncannot confirm PLR 0672230123016 and 0672240123001. the error message does not give an indication as to what the issue might be. \r\n\r\nwe have checked the logs around this date no error message related. \r\nno raw materials are archived. \r\nmaintenance shows that the order, recipe, item etc. are in every module they need to be in. \r\nwe restarted services IntegrationPCS and Production nothing. \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: \'>> confiremd PLR0672230123016id=41616471-4073-4d43-9413-13290367340d>> LOG Prod{code:java}2023-01-24 18:37:54 (32901eea-9335-4778-84b9-72ca6c750256/Plant.Prod.BusinessLogic/SAKDSRV04/18592/210) [Error] Kotrak.Common.Infrastructure.ICommandRunEnvironment - Error during Void Run[UpdateProductionLotCommand](Plant.Prod.BusinessLogic.Application.Interfaces.ProductionLots.Commands.UpdateProductionLotCommand) methodSystem.AggregateException: One or more errors occurred. (Response status code does not indicate success: 500 (Internal Server Error).) ---> Refit.ApiException: Response status code does not indicate success: 500 (Internal Server Error).   at Refit.RequestBuilderImplementation.<>c__DisplayClass14_0`2.<<BuildCancellableTaskFuncForMethod>b__0>d.MoveNext() in /_/Refit/RequestBuilderImplementation.cs:line 313   --- End of inner exception stack trace ---   at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions)   at System.Threading.Tasks.Task`1.GetResultCore(Boolean waitCompletionNotification)   at Plant.Prod.BusinessLogic.Infrastructure.ContextIntegration.ApiServices.StockEngine.StockEngineApi.UpdateReservationsAndConfirmProductionLot(AggregateId productionLotId"", \'Comment 4: AggregateId businessUnitId\', \'Comment 5: Quantity productionQuantity\', \'Comment 6: IEnumerable`1 settlementData\', \'Comment 7: IEnumerable`1 dosingSiloItemData) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Infrastructure.ContextIntegration\\\\\\\\ApiServices\\\\\\\\StockEngine\\\\\\\\StockEngineApi.cs:line 165   at Castle.Proxies.Invocations.IStockEngineApi_UpdateReservationsAndConfirmProductionLot.InvokeMethodOnTarget()   at Castle.DynamicProxy.AbstractInvocation.Proceed()   at Kotrak.Common.Infrastructure.Interceptors.ApiReferenceExceptionInterceptor.Intercept(IInvocation invocation)   at Castle.DynamicProxy.AbstractInvocation.Proceed()   at Castle.Proxies.IStockEngineApiProxy.UpdateReservationsAndConfirmProductionLot(AggregateId productionLotId\', \'Comment 8: AggregateId businessUnitId\', \'Comment 9: Quantity productionQuantity\', \'Comment 10: IEnumerable`1 settlementData\', \'Comment 11: IEnumerable`1 dosingSiloItemData)   at Plant.Prod.BusinessLogic.Domain.ProductionLots.ConfirmProductionLotDomainService.UpdateReservationsAndConfirmProductionLot(ProductionLot productionLot\', \'Comment 12: ConfirmProductionLotActionData data\', \'Comment 13: IEnumerable`1 reservations\', \'Comment 14: IEnumerable`1 dosingSiloItemData) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Domain\\\\\\\\ProductionLots\\\\\\\\ConfirmProductionLotDomainService.cs:line 88   at Plant.Prod.BusinessLogic.Application.ProductionLots.ProductionLotService.UpdateProductionLot(UpdateProductionLotActionData data) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Application\\\\\\\\ProductionLots\\\\\\\\ProductionLotService.cs:line 334   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 38   at Kotrak.Common.Infrastructure.Commands.CommandEnvironment.Run[TCommand](TCommand command)   at Kotrak.Common.Infrastructure.Commands.Decorators.IntercontextEventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command)   at Kotrak.Common.Infrastructure.Commands.Decorators.EventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command)   at Kotrak.Common.Infrastructure.Commands.Decorators.ValidationCommandEnvironmentDecorator.Run[TCommand](TCommand command)   at Castle.DynamicProxy.AbstractInvocation.Proceed()   at Kotrak.Common.Infrastructure.Interceptors.LoggingInterceptor`1.Intercept(IInvocation invocation)2023-01-24 18:37:54 (/Plant.Prod.BusinessLogic/SAKDSRV04/18592/195) [Error] Serilog.AspNetCore.RequestLoggingMiddleware - HTTP ""POST"" ""/api/productionLot/update"" responded 500 in 859.0456 ms{code}>> Request Log{code:java}2023-01-24 18:37:54 (32901eea-9335-4778-84b9-72ca6c750256/Plant.Prod.BusinessLogic/SAKDSRV04/18592/210) [Error] Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware - Error during request{  ""scheme"": ""http""\', \'Comment 15:  ""host"": {    ""Value"": ""sakdsrv04:83""\', \'Comment 16:    ""HasValue"": true\', \'Comment 17:    ""Host"": ""sakdsrv04""\', \'Comment 18:    ""Port"": 83  }\', \'Comment 19:  ""path"": ""/api/productionLot/update""\', \'Comment 20:  ""queryString"": []\', \'Comment 21:  ""requestBody"": ""{\\\\\\\\""elements\\\\\\\\"":[{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":1,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""a3e8359c-1434-47af-807b-194b09e15329\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":251}},{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":2,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""2d5d699e-9140-435c-b557-a904b15d0846\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":1.68}},{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":3,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""9915211b-5428-419f-ace3-500107b293c8\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":0.4}},{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":4,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""c790227e-d0d1-4391-84ec-b997d014b365\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":348}},{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":5,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""b6693bc8-055e-4394-99ed-cd2ac383ab5c\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":3}},{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":6,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""cb9254cd-11f3-45d1-8e9a-2379ea68b108\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":1388}},{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":7,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""523a75e3-f5e9-4ea7-88ef-9ba4fd1b9b1c\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":235}},{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":8,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""ccb356e8-b899-46d6-97aa-7f4af566f8d3\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":73}},{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":9,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""97ae7ce1-ac4a-4852-8f5e-6a62446c1b3c\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":450}},{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":10,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""eacc5086-a76d-45b8-b34b-aadcdf8063de\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":6.26}},{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":11,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""ed1e952c-87b4-46cd-84a3-5f2c50fffb4a\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":15.4}},{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":13,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""99faf3a0-9376-4ac9-953e-c5d13887c0c6\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":218}},{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":14,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""31f81b61-b661-4d65-84d4-707133fa2816\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":2}},{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":15,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""9c5d67c9-a8d5-4bee-b4d0-d0b18233ad9a\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":0.6}},{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":16,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""c7f1f3c2-3267-46dd-a88e-cad65fd117b8\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":3.24}}],\\\\\\\\""executions\\\\\\\\"":[{\\\\\\\\""elements\\\\\\\\"":[{\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""1ffec991-c0ee-4d19-be6e-4d1ab446d7c9\\\\\\\\"",\\\\\\\\""recipeElementId\\\\\\\\"":12,\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""pcs\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":60}}],\\\\\\\\""readyProductId\\\\\\\\"":\\\\\\\\""8ae3d247-05f9-4268-a5d6-e0ff11cfded8\\\\\\\\"",\\\\\\\\""packingRecipeId\\\\\\\\"":\\\\\\\\""c535edc8-9d73-41b7-9d30-e7eae9b7c08a\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":2995.58},\\\\\\\\""requestedQuantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":3000},\\\\\\\\""expiryDate\\\\\\\\"":\\\\\\\\""2023-07-22T19:13:06.966Z\\\\\\\\""}],\\\\\\\\""reservations\\\\\\\\"":[{\\\\\\\\""deliveryId\\\\\\\\"":\\\\\\\\""d3fe0c16-69c1-42e6-a085-57b9d7419036\\\\\\\\"",\\\\\\\\""stockUnitId\\\\\\\\"":\\\\\\\\""b4bdeeae-2472-4738-bd4a-5f0b5f331708\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""t\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":0.251}},{\\\\\\\\""deliveryId\\\\\\\\"":\\\\\\\\""bcf1cff7-f7de-4e12-8666-b55c603a5de5\\\\\\\\"",\\\\\\\\""stockUnitId\\\\\\\\"":\\\\\\\\""e88d2913-317a-477b-8d8e-147e7d7cbad3\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""t\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":1.388}},{\\\\\\\\""deliveryId\\\\\\\\"":\\\\\\\\""ef8f9c94-733a-47e1-aff0-5d68c71560f1\\\\\\\\"",\\\\\\\\""stockUnitId\\\\\\\\"":\\\\\\\\""d262b243-0635-4658-9d75-5882d9362942\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""t\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":0.0004}},{\\\\\\\\""deliveryId\\\\\\\\"":\\\\\\\\""43743169-cb9d-4b48-a313-fd1d38ce7b72\\\\\\\\"",\\\\\\\\""stockUnitId\\\\\\\\"":\\\\\\\\""89e420a1-c8d9-4721-964a-02f307513427\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""t\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":0.0154}},{\\\\\\\\""deliveryId\\\\\\\\"":\\\\\\\\""932f7272-1f25-411e-a64a-1c8d42bfd98f\\\\\\\\"",\\\\\\\\""stockUnitId\\\\\\\\"":\\\\\\\\""2d67090b-fada-43fb-b7b4-387680bf3ded\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""t\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":0.45}},{\\\\\\\\""deliveryId\\\\\\\\"":\\\\\\\\""f3af5dbd-4fb0-458c-8200-45f81258592c\\\\\\\\"",\\\\\\\\""stockUnitId\\\\\\\\"":\\\\\\\\""ddbd03ce-2068-4432-ae7e-a6477f1704f2\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""t\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":0.002}},{\\\\\\\\""deliveryId\\\\\\\\"":\\\\\\\\""67fe0c1f-ae58-4574-a5b5-fae0944b2b73\\\\\\\\"",\\\\\\\\""stockUnitId\\\\\\\\"":\\\\\\\\""67c7f7f8-651f-49c4-a41e-127c09088fa8\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""t\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":0.073}},{\\\\\\\\""deliveryId\\\\\\\\"":\\\\\\\\""e2151be8-cfdc-44d4-b1b9-520aa36820c8\\\\\\\\"",\\\\\\\\""stockUnitId\\\\\\\\"":\\\\\\\\""21df176b-34bf-46b3-803d-dd8e5cb02ba7\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""t\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":0.235}},{\\\\\\\\""deliveryId\\\\\\\\"":\\\\\\\\""34cf4324-c829-4286-b7ea-2aa653d6b25c\\\\\\\\"",\\\\\\\\""stockUnitId\\\\\\\\"":\\\\\\\\""6ee5a5ca-c350-40b6-9368-3bbe79b9c479\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""t\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":0.00168}},{\\\\\\\\""deliveryId\\\\\\\\"":\\\\\\\\""090f8a80-f370-43b4-b268-0304d8b2e108\\\\\\\\"",\\\\\\\\""stockUnitId\\\\\\\\"":\\\\\\\\""12363980-6291-444c-a76a-2342b1c1c3d7\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""t\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":0.00626}},{\\\\\\\\""deliveryId\\\\\\\\"":\\\\\\\\""882ff3a6-1c35-45ba-ad49-1cbce7aaadac\\\\\\\\"",\\\\\\\\""stockUnitId\\\\\\\\"":\\\\\\\\""b637f0b5-c5b5-45d6-811a-a8e622b65d1e\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""t\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":0.348}},{\\\\\\\\""deliveryId\\\\\\\\"":\\\\\\\\""a1e07f9f-f4fb-4405-b833-583746841a68\\\\\\\\"",\\\\\\\\""stockUnitId\\\\\\\\"":\\\\\\\\""e250823d-0c9e-4aa0-9539-5df2ffdd658a\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""t\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":0.218}},{\\\\\\\\""deliveryId\\\\\\\\"":\\\\\\\\""90227a2e-0100-4223-83f0-7aea35fd2250\\\\\\\\"",\\\\\\\\""stockUnitId\\\\\\\\"":\\\\\\\\""dde7ba82-8eb6-4c85-8d5f-160932a2fcd3\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""t\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":0.00324}},{\\\\\\\\""deliveryId\\\\\\\\"":\\\\\\\\""845f2076-870a-4c68-8a52-b081666cfe25\\\\\\\\"",\\\\\\\\""stockUnitId\\\\\\\\"":\\\\\\\\""6aee2c6f-fa5c-451d-9edd-d5e5e1e12150\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""t\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":0.003}},{\\\\\\\\""deliveryId\\\\\\\\"":\\\\\\\\""e118e00e-7ed0-4522-bc80-060fa157ced6\\\\\\\\"",\\\\\\\\""stockUnitId\\\\\\\\"":\\\\\\\\""849bb14d-53f7-4ef3-ad5c-7ff0af6e734a\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""t\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":0.0006}}],\\\\\\\\""productionLotId\\\\\\\\"":\\\\\\\\""41616471-4073-4d43-9413-13290367340d\\\\\\\\"",\\\\\\\\""recipeId\\\\\\\\"":\\\\\\\\""c535edc8-9d73-41b7-9d30-e7eae9b7c08a\\\\\\\\"",\\\\\\\\""labelId\\\\\\\\"":null,\\\\\\\\""productionOrderId\\\\\\\\"":\\\\\\\\""3a12e985-3eb8-4720-84be-33f075efbc09\\\\\\\\"",\\\\\\\\""businessPartnerId\\\\\\\\"":\\\\\\\\""d8db5ff8-b203-44b0-ab5a-6526b352a2a5\\\\\\\\"",\\\\\\\\""shiftNumberId\\\\\\\\"":null,\\\\\\\\""statusChange\\\\\\\\"":2}""}.System.AggregateException: One or more errors occurred. (Response status code does not indicate success: 500 (Internal Server Error).) ---> Refit.ApiException: Response status code does not indicate success: 500 (Internal Server Error).   at Refit.RequestBuilderImplementation.<>c__DisplayClass14_0`2.<<BuildCancellableTaskFuncForMethod>b__0>d.MoveNext() in /_/Refit/RequestBuilderImplementation.cs:line 313   --- End of inner exception stack trace ---   at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions)   at System.Threading.Tasks.Task`1.GetResultCore(Boolean waitCompletionNotification)   at Plant.Prod.BusinessLogic.Infrastructure.ContextIntegration.ApiServices.StockEngine.StockEngineApi.UpdateReservationsAndConfirmProductionLot(AggregateId productionLotId\', \'Comment 22: AggregateId businessUnitId\', \'Comment 23: Quantity productionQuantity\', \'Comment 24: IEnumerable`1 settlementData\', \'Comment 25: IEnumerable`1 dosingSiloItemData) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Infrastructure.ContextIntegration\\\\\\\\ApiServices\\\\\\\\StockEngine\\\\\\\\StockEngineApi.cs:line 165   at Castle.Proxies.Invocations.IStockEngineApi_UpdateReservationsAndConfirmProductionLot.InvokeMethodOnTarget()   at Castle.DynamicProxy.AbstractInvocation.Proceed()   at Kotrak.Common.Infrastructure.Interceptors.ApiReferenceExceptionInterceptor.Intercept(IInvocation invocation)   at Castle.DynamicProxy.AbstractInvocation.Proceed()   at Castle.Proxies.IStockEngineApiProxy.UpdateReservationsAndConfirmProductionLot(AggregateId productionLotId\', \'Comment 26: AggregateId businessUnitId\', \'Comment 27: Quantity productionQuantity\', \'Comment 28: IEnumerable`1 settlementData\', \'Comment 29: IEnumerable`1 dosingSiloItemData)   at Plant.Prod.BusinessLogic.Domain.ProductionLots.ConfirmProductionLotDomainService.UpdateReservationsAndConfirmProductionLot(ProductionLot productionLot\', \'Comment 30: ConfirmProductionLotActionData data\', \'Comment 31: IEnumerable`1 reservations\', \'Comment 32: IEnumerable`1 dosingSiloItemData) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Domain\\\\\\\\ProductionLots\\\\\\\\ConfirmProductionLotDomainService.cs:line 88   at Plant.Prod.BusinessLogic.Application.ProductionLots.ProductionLotService.UpdateProductionLot(UpdateProductionLotActionData data) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Application\\\\\\\\ProductionLots\\\\\\\\ProductionLotService.cs:line 334   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 38   at Kotrak.Common.Infrastructure.Commands.CommandEnvironment.Run[TCommand](TCommand command)   at Kotrak.Common.Infrastructure.Commands.Decorators.IntercontextEventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command)   at Kotrak.Common.Infrastructure.Commands.Decorators.EventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command)   at Kotrak.Common.Infrastructure.Commands.Decorators.ValidationCommandEnvironmentDecorator.Run[TCommand](TCommand command)   at Castle.DynamicProxy.AbstractInvocation.Proceed()   at Kotrak.Common.Infrastructure.Interceptors.LoggingInterceptor`1.Intercept(IInvocation invocation)   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_method9698(Closure \', \'Comment 33: Object \', \'Comment 34: Object[] )   at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor.SyncObjectResultExecutor.Execute(IActionResultTypeMapper mapper\', \'Comment 35: ObjectMethodExecutor executor\', \'Comment 36: Object controller\', \'Comment 37: Object[] arguments)   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeActionMethodAsync()   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next\', \'Comment 38: Scope& scope\', \'Comment 39: Object& state\', \'Comment 40: 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 41: Scope& scope\', \'Comment 42: Object& state\', \'Comment 43: 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 44: Task lastTask\', \'Comment 45: State next\', \'Comment 46: Scope scope\', \'Comment 47: Object state\', \'Comment 48: Boolean isCompleted)   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker\', \'Comment 49: Task task\', \'Comment 50: IDisposable scope)   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker\', \'Comment 51: Task task\', \'Comment 52: IDisposable scope)   at Microsoft.AspNetCore.Routing.EndpointMiddleware.<Invoke>g__AwaitRequestTask|6_0(Endpoint endpoint\', \'Comment 53: Task requestTask\', \'Comment 54: ILogger logger)   at Swashbuckle.AspNetCore.SwaggerUI.SwaggerUIMiddleware.Invoke(HttpContext httpContext)   at Swashbuckle.AspNetCore.Swagger.SwaggerMiddleware.Invoke(HttpContext httpContext\', ""Comment 55: ISwaggerProvider swaggerProvider)   at Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware.Invoke(HttpContext httpContext){code}\'"", \'Comment 56: \\\'Po restarcie pooli ponowiłam confirm na tym samym PLRze{code:java}2023-01-24 18:56:55 (2e53ede8-9517-4e92-ba70-4a54a27c1a7c/Plant.Prod.BusinessLogic/SAKDSRV04/4496/9) [Error] Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware - Error during request{  ""scheme"": ""http""\', \'Comment 57:  ""host"": {    ""Value"": ""sakdsrv04:83""\', \'Comment 58:    ""HasValue"": true\', \'Comment 59:    ""Host"": ""sakdsrv04""\', \'Comment 60:    ""Port"": 83  }\', \'Comment 61:  ""path"": ""/api/productionLot/update""\', \'Comment 62:  ""queryString"": []\', \'Comment 63:  ""requestBody"": ""{\\\\\\\\""elements\\\\\\\\"":[{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":1,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""a3e8359c-1434-47af-807b-194b09e15329\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":251}},{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":2,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""2d5d699e-9140-435c-b557-a904b15d0846\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":1.68}},{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":3,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""9915211b-5428-419f-ace3-500107b293c8\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":0.4}},{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":4,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""c790227e-d0d1-4391-84ec-b997d014b365\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":348}},{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":5,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""b6693bc8-055e-4394-99ed-cd2ac383ab5c\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":3}},{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":6,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""cb9254cd-11f3-45d1-8e9a-2379ea68b108\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":1388}},{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":7,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""523a75e3-f5e9-4ea7-88ef-9ba4fd1b9b1c\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":235}},{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":8,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""ccb356e8-b899-46d6-97aa-7f4af566f8d3\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":73}},{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":9,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""97ae7ce1-ac4a-4852-8f5e-6a62446c1b3c\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":450}},{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":10,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""eacc5086-a76d-45b8-b34b-aadcdf8063de\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":6.26}},{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":11,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""ed1e952c-87b4-46cd-84a3-5f2c50fffb4a\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":15.4}},{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":13,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""99faf3a0-9376-4ac9-953e-c5d13887c0c6\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":218}},{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":14,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""31f81b61-b661-4d65-84d4-707133fa2816\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":2}},{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":15,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""9c5d67c9-a8d5-4bee-b4d0-d0b18233ad9a\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":0.6}},{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":16,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""c7f1f3c2-3267-46dd-a88e-cad65fd117b8\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":3.24}}],\\\\\\\\""executions\\\\\\\\"":[{\\\\\\\\""elements\\\\\\\\"":[{\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""1ffec991-c0ee-4d19-be6e-4d1ab446d7c9\\\\\\\\"",\\\\\\\\""recipeElementId\\\\\\\\"":12,\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""pcs\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":60}}],\\\\\\\\""readyProductId\\\\\\\\"":\\\\\\\\""8ae3d247-05f9-4268-a5d6-e0ff11cfded8\\\\\\\\"",\\\\\\\\""packingRecipeId\\\\\\\\"":\\\\\\\\""c535edc8-9d73-41b7-9d30-e7eae9b7c08a\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":2995.58},\\\\\\\\""requestedQuantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":3000},\\\\\\\\""expiryDate\\\\\\\\"":\\\\\\\\""2023-07-22T19:13:06.966Z\\\\\\\\""}],\\\\\\\\""reservations\\\\\\\\"":[{\\\\\\\\""deliveryId\\\\\\\\"":\\\\\\\\""d3fe0c16-69c1-42e6-a085-57b9d7419036\\\\\\\\"",\\\\\\\\""stockUnitId\\\\\\\\"":\\\\\\\\""b4bdeeae-2472-4738-bd4a-5f0b5f331708\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""t\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":0.251}},{\\\\\\\\""deliveryId\\\\\\\\"":\\\\\\\\""bcf1cff7-f7de-4e12-8666-b55c603a5de5\\\\\\\\"",\\\\\\\\""stockUnitId\\\\\\\\"":\\\\\\\\""e88d2913-317a-477b-8d8e-147e7d7cbad3\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""t\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":1.388}},{\\\\\\\\""deliveryId\\\\\\\\"":\\\\\\\\""ef8f9c94-733a-47e1-aff0-5d68c71560f1\\\\\\\\"",\\\\\\\\""stockUnitId\\\\\\\\"":\\\\\\\\""d262b243-0635-4658-9d75-5882d9362942\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""t\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":0.0004}},{\\\\\\\\""deliveryId\\\\\\\\"":\\\\\\\\""43743169-cb9d-4b48-a313-fd1d38ce7b72\\\\\\\\"",\\\\\\\\""stockUnitId\\\\\\\\"":\\\\\\\\""89e420a1-c8d9-4721-964a-02f307513427\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""t\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":0.0154}},{\\\\\\\\""deliveryId\\\\\\\\"":\\\\\\\\""932f7272-1f25-411e-a64a-1c8d42bfd98f\\\\\\\\"",\\\\\\\\""stockUnitId\\\\\\\\"":\\\\\\\\""2d67090b-fada-43fb-b7b4-387680bf3ded\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""t\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":0.45}},{\\\\\\\\""deliveryId\\\\\\\\"":\\\\\\\\""f3af5dbd-4fb0-458c-8200-45f81258592c\\\\\\\\"",\\\\\\\\""stockUnitId\\\\\\\\"":\\\\\\\\""ddbd03ce-2068-4432-ae7e-a6477f1704f2\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""t\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":0.002}},{\\\\\\\\""deliveryId\\\\\\\\"":\\\\\\\\""67fe0c1f-ae58-4574-a5b5-fae0944b2b73\\\\\\\\"",\\\\\\\\""stockUnitId\\\\\\\\"":\\\\\\\\""67c7f7f8-651f-49c4-a41e-127c09088fa8\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""t\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":0.073}},{\\\\\\\\""deliveryId\\\\\\\\"":\\\\\\\\""e2151be8-cfdc-44d4-b1b9-520aa36820c8\\\\\\\\"",\\\\\\\\""stockUnitId\\\\\\\\"":\\\\\\\\""21df176b-34bf-46b3-803d-dd8e5cb02ba7\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""t\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":0.235}},{\\\\\\\\""deliveryId\\\\\\\\"":\\\\\\\\""34cf4324-c829-4286-b7ea-2aa653d6b25c\\\\\\\\"",\\\\\\\\""stockUnitId\\\\\\\\"":\\\\\\\\""6ee5a5ca-c350-40b6-9368-3bbe79b9c479\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""t\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":0.00168}},{\\\\\\\\""deliveryId\\\\\\\\"":\\\\\\\\""090f8a80-f370-43b4-b268-0304d8b2e108\\\\\\\\"",\\\\\\\\""stockUnitId\\\\\\\\"":\\\\\\\\""12363980-6291-444c-a76a-2342b1c1c3d7\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""t\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":0.00626}},{\\\\\\\\""deliveryId\\\\\\\\"":\\\\\\\\""882ff3a6-1c35-45ba-ad49-1cbce7aaadac\\\\\\\\"",\\\\\\\\""stockUnitId\\\\\\\\"":\\\\\\\\""b637f0b5-c5b5-45d6-811a-a8e622b65d1e\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""t\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":0.348}},{\\\\\\\\""deliveryId\\\\\\\\"":\\\\\\\\""a1e07f9f-f4fb-4405-b833-583746841a68\\\\\\\\"",\\\\\\\\""stockUnitId\\\\\\\\"":\\\\\\\\""e250823d-0c9e-4aa0-9539-5df2ffdd658a\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""t\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":0.218}},{\\\\\\\\""deliveryId\\\\\\\\"":\\\\\\\\""90227a2e-0100-4223-83f0-7aea35fd2250\\\\\\\\"",\\\\\\\\""stockUnitId\\\\\\\\"":\\\\\\\\""dde7ba82-8eb6-4c85-8d5f-160932a2fcd3\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""t\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":0.00324}},{\\\\\\\\""deliveryId\\\\\\\\"":\\\\\\\\""845f2076-870a-4c68-8a52-b081666cfe25\\\\\\\\"",\\\\\\\\""stockUnitId\\\\\\\\"":\\\\\\\\""6aee2c6f-fa5c-451d-9edd-d5e5e1e12150\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""t\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":0.003}},{\\\\\\\\""deliveryId\\\\\\\\"":\\\\\\\\""e118e00e-7ed0-4522-bc80-060fa157ced6\\\\\\\\"",\\\\\\\\""stockUnitId\\\\\\\\"":\\\\\\\\""849bb14d-53f7-4ef3-ad5c-7ff0af6e734a\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""t\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":0.0006}}],\\\\\\\\""productionLotId\\\\\\\\"":\\\\\\\\""41616471-4073-4d43-9413-13290367340d\\\\\\\\"",\\\\\\\\""recipeId\\\\\\\\"":\\\\\\\\""c535edc8-9d73-41b7-9d30-e7eae9b7c08a\\\\\\\\"",\\\\\\\\""labelId\\\\\\\\"":null,\\\\\\\\""productionOrderId\\\\\\\\"":\\\\\\\\""3a12e985-3eb8-4720-84be-33f075efbc09\\\\\\\\"",\\\\\\\\""businessPartnerId\\\\\\\\"":\\\\\\\\""d8db5ff8-b203-44b0-ab5a-6526b352a2a5\\\\\\\\"",\\\\\\\\""shiftNumberId\\\\\\\\"":null,\\\\\\\\""statusChange\\\\\\\\"":2}""}.System.AggregateException: One or more errors occurred. (Response status code does not indicate success: 500 (Internal Server Error).) ---> Refit.ApiException: Response status code does not indicate success: 500 (Internal Server Error).   at Refit.RequestBuilderImplementation.<>c__DisplayClass14_0`2.<<BuildCancellableTaskFuncForMethod>b__0>d.MoveNext() in /_/Refit/RequestBuilderImplementation.cs:line 288   --- End of inner exception stack trace ---   at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions)   at System.Threading.Tasks.Task`1.GetResultCore(Boolean waitCompletionNotification)   at System.Threading.Tasks.Task`1.get_Result()   at Plant.Prod.BusinessLogic.Infrastructure.ContextIntegration.ApiServices.StockEngine.StockEngineApi.UpdateReservationsAndConfirmProductionLot(AggregateId productionLotId\', \'Comment 64: AggregateId businessUnitId\', \'Comment 65: Quantity productionQuantity\', \'Comment 66: IEnumerable`1 settlementData\', \'Comment 67: IEnumerable`1 dosingSiloItemData) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Infrastructure.ContextIntegration\\\\\\\\ApiServices\\\\\\\\StockEngine\\\\\\\\StockEngineApi.cs:line 165   at Castle.Proxies.Invocations.IStockEngineApi_UpdateReservationsAndConfirmProductionLot.InvokeMethodOnTarget()   at Castle.DynamicProxy.AbstractInvocation.Proceed()   at Kotrak.Common.Infrastructure.Interceptors.ApiReferenceExceptionInterceptor.Intercept(IInvocation invocation)   at Castle.DynamicProxy.AbstractInvocation.Proceed()   at Castle.Proxies.IStockEngineApiProxy.UpdateReservationsAndConfirmProductionLot(AggregateId productionLotId\', \'Comment 68: AggregateId businessUnitId\', \'Comment 69: Quantity productionQuantity\', \'Comment 70: IEnumerable`1 settlementData\', \'Comment 71: IEnumerable`1 dosingSiloItemData)   at Plant.Prod.BusinessLogic.Domain.ProductionLots.ConfirmProductionLotDomainService.UpdateReservationsAndConfirmProductionLot(ProductionLot productionLot\', \'Comment 72: ConfirmProductionLotActionData data\', \'Comment 73: IEnumerable`1 reservations\', \'Comment 74: IEnumerable`1 dosingSiloItemData) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Domain\\\\\\\\ProductionLots\\\\\\\\ConfirmProductionLotDomainService.cs:line 88   at Plant.Prod.BusinessLogic.Application.ProductionLots.ProductionLotService.UpdateProductionLot(UpdateProductionLotActionData data) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Application\\\\\\\\ProductionLots\\\\\\\\ProductionLotService.cs:line 334   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 38   at Kotrak.Common.Infrastructure.Commands.CommandEnvironment.Run[TCommand](TCommand command)   at Kotrak.Common.Infrastructure.Commands.Decorators.IntercontextEventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command)   at Kotrak.Common.Infrastructure.Commands.Decorators.EventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command)   at Kotrak.Common.Infrastructure.Commands.Decorators.ValidationCommandEnvironmentDecorator.Run[TCommand](TCommand command)   at Castle.Proxies.Invocations.IRunEnvironment_Run.InvokeMethodOnTarget()   at Castle.DynamicProxy.AbstractInvocation.Proceed()   at Kotrak.Common.Infrastructure.Interceptors.LoggingInterceptor`1.Intercept(IInvocation invocation)   at Castle.DynamicProxy.AbstractInvocation.Proceed()   at Castle.Proxies.ICommandRunEnvironmentProxy.Run[TCommand](TCommand command)   at Kotrak.Common.Infrastructure.Commands.StandardGate.Dispatch[TCommand](TCommand command)   at Kotrak.Common.Infrastructure.Commands.Decorators.AsyncGateDecorator.Dispatch[TCommand](TCommand command)   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_method6341(Closure \', \'Comment 75: Object \', \'Comment 76: Object[] )   at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor.SyncObjectResultExecutor.Execute(IActionResultTypeMapper mapper\', \'Comment 77: ObjectMethodExecutor executor\', \'Comment 78: Object controller\', \'Comment 79: Object[] arguments)   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeActionMethodAsync()   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next\', \'Comment 80: Scope& scope\', \'Comment 81: Object& state\', \'Comment 82: 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 83: Scope& scope\', \'Comment 84: Object& state\', \'Comment 85: 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 86: Task lastTask\', \'Comment 87: State next\', \'Comment 88: Scope scope\', \'Comment 89: Object state\', \'Comment 90: Boolean isCompleted)   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker\', \'Comment 91: Task task\', \'Comment 92: IDisposable scope)   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker\', \'Comment 93: Task task\', \'Comment 94: IDisposable scope)   at Microsoft.AspNetCore.Routing.EndpointMiddleware.<Invoke>g__AwaitRequestTask|6_0(Endpoint endpoint\', \'Comment 95: Task requestTask\', \'Comment 96: ILogger logger)   at Swashbuckle.AspNetCore.SwaggerUI.SwaggerUIMiddleware.Invoke(HttpContext httpContext)   at Swashbuckle.AspNetCore.Swagger.SwaggerMiddleware.Invoke(HttpContext httpContext\', ""Comment 97: ISwaggerProvider swaggerProvider)   at Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware.Invoke(HttpContext httpContext){code}\'"", ""Comment 98: \'{code:java}2023-01-24 18:56:55 (2e53ede8-9517-4e92-ba70-4a54a27c1a7c/Plant.Prod.BusinessLogic/SAKDSRV04/4496/9) [Error] Kotrak.Common.Infrastructure.ICommandRunEnvironment - Error during Void Run[UpdateProductionLotCommand](Plant.Prod.BusinessLogic.Application.Interfaces.ProductionLots.Commands.UpdateProductionLotCommand) methodSystem.AggregateException: One or more errors occurred. (Response status code does not indicate success: 500 (Internal Server Error).) ---> Refit.ApiException: Response status code does not indicate success: 500 (Internal Server Error).   at Refit.RequestBuilderImplementation.<>c__DisplayClass14_0`2.<<BuildCancellableTaskFuncForMethod>b__0>d.MoveNext() in /_/Refit/RequestBuilderImplementation.cs:line 288   --- End of inner exception stack trace ---   at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions)   at System.Threading.Tasks.Task`1.GetResultCore(Boolean waitCompletionNotification)   at System.Threading.Tasks.Task`1.get_Result()   at Plant.Prod.BusinessLogic.Infrastructure.ContextIntegration.ApiServices.StockEngine.StockEngineApi.UpdateReservationsAndConfirmProductionLot(AggregateId productionLotId"", \'Comment 99: AggregateId businessUnitId\', \'Comment 100: Quantity productionQuantity\', \'Comment 101: IEnumerable`1 settlementData\', \'Comment 102: IEnumerable`1 dosingSiloItemData) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Infrastructure.ContextIntegration\\\\\\\\ApiServices\\\\\\\\StockEngine\\\\\\\\StockEngineApi.cs:line 165   at Castle.Proxies.Invocations.IStockEngineApi_UpdateReservationsAndConfirmProductionLot.InvokeMethodOnTarget()   at Castle.DynamicProxy.AbstractInvocation.Proceed()   at Kotrak.Common.Infrastructure.Interceptors.ApiReferenceExceptionInterceptor.Intercept(IInvocation invocation)   at Castle.DynamicProxy.AbstractInvocation.Proceed()   at Castle.Proxies.IStockEngineApiProxy.UpdateReservationsAndConfirmProductionLot(AggregateId productionLotId\', \'Comment 103: AggregateId businessUnitId\', \'Comment 104: Quantity productionQuantity\', \'Comment 105: IEnumerable`1 settlementData\', \'Comment 106: IEnumerable`1 dosingSiloItemData)   at Plant.Prod.BusinessLogic.Domain.ProductionLots.ConfirmProductionLotDomainService.UpdateReservationsAndConfirmProductionLot(ProductionLot productionLot\', \'Comment 107: ConfirmProductionLotActionData data\', \'Comment 108: IEnumerable`1 reservations\', \'Comment 109: IEnumerable`1 dosingSiloItemData) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Domain\\\\\\\\ProductionLots\\\\\\\\ConfirmProductionLotDomainService.cs:line 88   at Plant.Prod.BusinessLogic.Application.ProductionLots.ProductionLotService.UpdateProductionLot(UpdateProductionLotActionData data) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Application\\\\\\\\ProductionLots\\\\\\\\ProductionLotService.cs:line 334   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 38   at Kotrak.Common.Infrastructure.Commands.CommandEnvironment.Run[TCommand](TCommand command)   at Kotrak.Common.Infrastructure.Commands.Decorators.IntercontextEventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command)   at Kotrak.Common.Infrastructure.Commands.Decorators.EventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command)   at Kotrak.Common.Infrastructure.Commands.Decorators.ValidationCommandEnvironmentDecorator.Run[TCommand](TCommand command)   at Castle.Proxies.Invocations.IRunEnvironment_Run.InvokeMethodOnTarget()   at Castle.DynamicProxy.AbstractInvocation.Proceed()   at Kotrak.Common.Infrastructure.Interceptors.LoggingInterceptor`1.Intercept(IInvocation invocation)2023-01-24 18:56:55 (/Plant.Prod.BusinessLogic/SAKDSRV04/4496/8) [Error] Serilog.AspNetCore.RequestLoggingMiddleware - HTTP ""POST"" ""/api/productionLot/update"" responded 500 in 3008.1672 ms{code}\\\'\', ""Comment 110: \'>> ze Stocka{code:java}2023-01-24 18:56:55 (2e53ede8-9517-4e92-ba70-4a54a27c1a7c/Plant.Stock.BusinessLogic/SAKDSRV04/10032/9) [Error] Kotrak.Common.Infrastructure.ICommandRunEnvironment - Error during Void Run[UpdateReservationsAndConfirmProductionLotCommand](Plant.Stock.BusinessLogic.Application.Interfaces.ProductionLots.Commands.UpdateReservationsAndConfirmProductionLotCommand) methodSystem.ArgumentException: Unit mismatch   at Kotrak.Common.SharedKernel.Quantity.ToCommonUnit(Quantity x1"", \'Comment 111: Quantity x2)   at Kotrak.Common.SharedKernel.Quantity.op_Subtraction(Quantity q\', \'Comment 112: Quantity q2)   at Plant.Stock.BusinessLogic.Domain.StockManagement.StockData.DecreaseQuantity(Quantity quantity) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Domain\\\\\\\\StockManagement\\\\\\\\StockData.cs:line 58   at Plant.Stock.BusinessLogic.Domain.StockReplenishment.Policies.StockUnitBaseReplenishmentPolicy.FetchReplenishment(ReplenishmentData replenishmentData) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Domain\\\\\\\\StockReplenishment\\\\\\\\Policies\\\\\\\\StockUnitBaseReplenishmentPolicy.cs:line 28   at Plant.Stock.BusinessLogic.Domain.ProductionSettlement.Policies.ProductionSettlementBasePolicy.FetchReplenishment(IEnumerable`1 filteredStockData\', \'Comment 113: Quantity quantity) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Domain\\\\\\\\ProductionSettlement\\\\\\\\Policies\\\\\\\\ProductionSettlementBasePolicy.cs:line 104   at Plant.Stock.BusinessLogic.Domain.ProductionSettlement.Policies.ProductionSettlementBasePolicy.FetchProductionElementReplenishment(IEnumerable`1 stockData\', \'Comment 114: ProductionElementSettlementData settlementData\', \'Comment 115: List`1 response\', \'Comment 116: List`1 missingStock) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Domain\\\\\\\\ProductionSettlement\\\\\\\\Policies\\\\\\\\ProductionSettlementBasePolicy.cs:line 90   at Plant.Stock.BusinessLogic.Domain.ProductionSettlement.Policies.ProductionSettlementBasePolicy.FetchProductionSettlement(IEnumerable`1 stockData\', \'Comment 117: IEnumerable`1 productionElementsData) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Domain\\\\\\\\ProductionSettlement\\\\\\\\Policies\\\\\\\\ProductionSettlementBasePolicy.cs:line 48   at Plant.Stock.BusinessLogic.Domain.ProductionSettlement.ProductionSettlementDomainService.FetchProductionSettlement(IEnumerable`1 stockForSettlement\', \'Comment 118: IEnumerable`1 stockUnits\', \'Comment 119: IEnumerable`1 deliveries\', \'Comment 120: IEnumerable`1 locations\', \'Comment 121: IProductionSettlementPolicy productionSettlementPolicy) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Domain\\\\\\\\ProductionSettlement\\\\\\\\ProductionSettlementDomainService.cs:line 220   at Plant.Stock.BusinessLogic.Domain.ProductionSettlement.ProductionSettlementDomainService.ExecuteProductionSettlement(ProductionSettlementData data) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Domain\\\\\\\\ProductionSettlement\\\\\\\\ProductionSettlementDomainService.cs:line 61   at Plant.Stock.BusinessLogic.Domain.ProductionLots.Services.ConfirmProductionDomainService.ExecuteProductionSettlement(ConfirmProductionLotDomainData data) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Domain\\\\\\\\ProductionLots\\\\\\\\Services\\\\\\\\ConfirmProductionDomainService.cs:line 102   at Plant.Stock.BusinessLogic.Domain.ProductionLots.Services.ConfirmProductionDomainService.ConfirmProductionLot(ConfirmProductionLotDomainData data) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Domain\\\\\\\\ProductionLots\\\\\\\\Services\\\\\\\\ConfirmProductionDomainService.cs:line 52   at Plant.Stock.BusinessLogic.Application.ProductionLots.ProductionLotService.ConfirmProduction(ProductionLot productionLot\', \'Comment 122: IEnumerable`1 productionElements\', \'Comment 123: IEnumerable`1 ingredientDeliveries\', \'Comment 124: IEnumerable`1 ingredientStockUnits\', \'Comment 125: IEnumerable`1 locations\', \'Comment 126: IEnumerable`1 transcodingDefinitions) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Application\\\\\\\\ProductionLots\\\\\\\\ProductionLotService.cs:line 797   at Plant.Stock.BusinessLogic.Application.ProductionLots.ProductionLotService.UpdateReservationsAndConfirmProductionLot(UpdateReservationsAndConfirmProductionLotActionData data) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Application\\\\\\\\ProductionLots\\\\\\\\ProductionLotService.cs:line 459   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 32   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.Proxies.Invocations.IRunEnvironment_Run.InvokeMethodOnTarget()   at Castle.DynamicProxy.AbstractInvocation.Proceed()   at Kotrak.Common.Infrastructure.Interceptors.LoggingInterceptor`1.Intercept(IInvocation invocation)2023-01-24 18:56:55 (/Plant.Stock.BusinessLogic/SAKDSRV04/10032/7) [Error] Serilog.AspNetCore.RequestLoggingMiddleware - HTTP ""POST"" ""/api/productionLot/updateReservationsAndConfirm"" responded 500 in 1510.1593 ms2023-01-24 18:59:13 (/Plant.Stock.BusinessLogic/SAKDSRV04/10032/10) [Error] Kotrak.Common.Infrastructure.CleanEventsTask - Problem with data cleaning task executionMicrosoft.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 (258): The wait operation timed out.   at Microsoft.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception\', \'Comment 127: Boolean breakConnection\', \'Comment 128: Action`1 wrapCloseInAction)   at Microsoft.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj\', \'Comment 129: Boolean callerHasConnectionLock\', \'Comment 130: Boolean asyncClose)   at Microsoft.Data.SqlClient.TdsParserStateObject.ThrowExceptionAndWarning(Boolean callerHasConnectionLock\', \'Comment 131: Boolean asyncClose)   at Microsoft.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject stateObj\', \'Comment 132: UInt32 error)   at Microsoft.Data.SqlClient.TdsParserStateObject.ReadSniSyncOverAsync()   at Microsoft.Data.SqlClient.TdsParserStateObject.TryReadNetworkPacket()   at Microsoft.Data.SqlClient.TdsParserStateObject.TryPrepareBuffer()   at Microsoft.Data.SqlClient.TdsParserStateObject.TryReadByte(Byte& value)   at Microsoft.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior\', \'Comment 133: SqlCommand cmdHandler\', \'Comment 134: SqlDataReader dataStream\', \'Comment 135: BulkCopySimpleResultSet bulkCopyHandler\', \'Comment 136: TdsParserStateObject stateObj\', \'Comment 137: Boolean& dataReady)   at Microsoft.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds\', \'Comment 138: RunBehavior runBehavior\', \'Comment 139: String resetOptionsString\', \'Comment 140: Boolean isInternal\', \'Comment 141: Boolean forDescribeParameterEncryption\', \'Comment 142: Boolean shouldCacheForAlwaysEncrypted)   at Microsoft.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior\', \'Comment 143: RunBehavior runBehavior\', \'Comment 144: Boolean returnStream\', \'Comment 145: Boolean isAsync\', \'Comment 146: Int32 timeout\', \'Comment 147: Task& task\', \'Comment 148: Boolean asyncWrite\', \'Comment 149: Boolean inRetry\', \'Comment 150: SqlDataReader ds\', \'Comment 151: Boolean describeParameterEncryptionRequest)   at Microsoft.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior\', \'Comment 152: RunBehavior runBehavior\', \'Comment 153: Boolean returnStream\', \'Comment 154: TaskCompletionSource`1 completion\', \'Comment 155: Int32 timeout\', \'Comment 156: Task& task\', \'Comment 157: Boolean& usedCache\', \'Comment 158: Boolean asyncWrite\', \'Comment 159: Boolean inRetry\', \'Comment 160: String method)   at Microsoft.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion\', \'Comment 161: Boolean sendToPipe\', \'Comment 162: Int32 timeout\', \'Comment 163: Boolean& usedCache\', \'Comment 164: Boolean asyncWrite\', \'Comment 165: Boolean inRetry\', \'Comment 166: String methodName)   at Microsoft.Data.SqlClient.SqlCommand.ExecuteNonQuery()   at Microsoft.EntityFrameworkCore.Storage.RelationalCommand.ExecuteNonQuery(RelationalCommandParameterObject parameterObject)   at Microsoft.EntityFrameworkCore.RelationalDatabaseFacadeExtensions.ExecuteSqlRaw(DatabaseFacade databaseFacade\', \'Comment 167: String sql\', \'Comment 168: IEnumerable`1 parameters)   at Microsoft.EntityFrameworkCore.RelationalDatabaseFacadeExtensions.ExecuteSqlRaw(DatabaseFacade databaseFacade\', \'Comment 169: String sql\', \'Comment 170: Object[] parameters)   at Kotrak.Common.Infrastructure.EF.EventRepository.BaseEventRepositoryEf`1.CleanData(TimeSpan removeOlderThen)   at Kotrak.Common.Infrastructure.CleanEventsTask.<ExecuteAsync>b__9_0()ClientConnectionId:c39e892c-3080-4114-991c-0209bbba9894Error Number:-2,State:0,Class:112023-01-24 19:01:00 (db3de036-734d-453f-a742-e6c899409eb1/Plant.Stock.BusinessLogic/SAKDSRV04/10032/18) [Error] Kotrak.Common.Infrastructure.ICommandRunEnvironment - Error during Void Run[ChangeProductionLotQuantityCommand](Plant.Stock.BusinessLogic.Application.Interfaces.ProductionLots.Commands.ChangeProductionLotQuantityCommand) methodMicrosoft.Data.SqlClient.SqlException (0x80131904): Execution Timeout Expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.Operation cancelled by user. ---> System.ComponentModel.Win32Exception (258): The wait operation timed out.   at Microsoft.Data.SqlClient.SqlConnection.OnError(SqlException exception\', \'Comment 171: Boolean breakConnection\', \'Comment 172: Action`1 wrapCloseInAction)   at Microsoft.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception\', \'Comment 173: Boolean breakConnection\', \'Comment 174: Action`1 wrapCloseInAction)   at Microsoft.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj\', \'Comment 175: Boolean callerHasConnectionLock\', \'Comment 176: Boolean asyncClose)   at Microsoft.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior\', \'Comment 177: SqlCommand cmdHandler\', \'Comment 178: SqlDataReader dataStream\', \'Comment 179: BulkCopySimpleResultSet bulkCopyHandler\', \'Comment 180: TdsParserStateObject stateObj\', \'Comment 181: Boolean& dataReady)   at Microsoft.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior\', \'Comment 182: SqlCommand cmdHandler\', \'Comment 183: SqlDataReader dataStream\', \'Comment 184: BulkCopySimpleResultSet bulkCopyHandler\', \'Comment 185: TdsParserStateObject stateObj)   at Microsoft.Data.SqlClient.SqlBulkCopy.RunParser(BulkCopySimpleResultSet bulkCopyHandler)   at Microsoft.Data.SqlClient.SqlBulkCopy.CopyBatchesAsyncContinuedOnSuccess(BulkCopySimpleResultSet internalResults\', \'Comment 186: String updateBulkCommandText\', \'Comment 187: CancellationToken cts\', \'Comment 188: TaskCompletionSource`1 source)   at Microsoft.Data.SqlClient.SqlBulkCopy.CopyBatchesAsyncContinued(BulkCopySimpleResultSet internalResults\', \'Comment 189: String updateBulkCommandText\', \'Comment 190: CancellationToken cts\', \'Comment 191: TaskCompletionSource`1 source)   at Microsoft.Data.SqlClient.SqlBulkCopy.CopyBatchesAsync(BulkCopySimpleResultSet internalResults\', \'Comment 192: String updateBulkCommandText\', \'Comment 193: CancellationToken cts\', \'Comment 194: TaskCompletionSource`1 source)   at Microsoft.Data.SqlClient.SqlBulkCopy.WriteToServerInternalRestContinuedAsync(BulkCopySimpleResultSet internalResults\', \'Comment 195: CancellationToken cts\', \'Comment 196: TaskCompletionSource`1 source)   at Microsoft.Data.SqlClient.SqlBulkCopy.WriteToServerInternalRestAsync(CancellationToken cts\', \'Comment 197: TaskCompletionSource`1 source)   at Microsoft.Data.SqlClient.SqlBulkCopy.WriteToServerInternalAsync(CancellationToken ctoken)   at Microsoft.Data.SqlClient.SqlBulkCopy.WriteRowSourceToServerAsync(Int32 columnCount\', \'Comment 198: CancellationToken ctoken)   at Microsoft.Data.SqlClient.SqlBulkCopy.WriteToServer(DataTable table\', \'Comment 199: DataRowState rowState)   at Microsoft.Data.SqlClient.SqlBulkCopy.WriteToServer(DataTable table)   at EFCore.BulkExtensions.SQLAdapters.SQLServer.SqlOperationsServerAdapter.InsertAsync[T](DbContext context\', \'Comment 200: Type type\', \'Comment 201: IList`1 entities\', \'Comment 202: TableInfo tableInfo\', \'Comment 203: Action`1 progress\', \'Comment 204: Boolean isAsync\', \'Comment 205: CancellationToken cancellationToken)   at EFCore.BulkExtensions.SQLAdapters.SQLServer.SqlOperationsServerAdapter.InsertAsync[T](DbContext context\', \'Comment 206: Type type\', \'Comment 207: IList`1 entities\', \'Comment 208: TableInfo tableInfo\', \'Comment 209: Action`1 progress\', \'Comment 210: Boolean isAsync\', \'Comment 211: CancellationToken cancellationToken)   at EFCore.BulkExtensions.SQLAdapters.SQLServer.SqlOperationsServerAdapter.Insert[T](DbContext context\', \'Comment 212: Type type\', \'Comment 213: IList`1 entities\', \'Comment 214: TableInfo tableInfo\', \'Comment 215: Action`1 progress)   at EFCore.BulkExtensions.SqlBulkOperation.Insert[T](DbContext context\', \'Comment 216: Type type\', \'Comment 217: IList`1 entities\', \'Comment 218: TableInfo tableInfo\', \'Comment 219: Action`1 progress)   at EFCore.BulkExtensions.DbContextBulkTransaction.Execute[T](DbContext context\', \'Comment 220: Type type\', \'Comment 221: IList`1 entities\', \'Comment 222: OperationType operationType\', \'Comment 223: BulkConfig bulkConfig\', \'Comment 224: Action`1 progress)   at EFCore.BulkExtensions.DbContextBulkExtensions.BulkInsert[T](DbContext context\', \'Comment 225: IList`1 entities\', \'Comment 226: BulkConfig bulkConfig\', \'Comment 227: Action`1 progress\', \'Comment 228: Type type)   at Kotrak.Common.Infrastructure.EF.EventRepository.GenericEventRepositoryEf`2.Persist(TAggregateRoot aggregateRoot)   at Kotrak.Common.Infrastructure.Repositories.AggregateRootRepository`2.PersistEvents(TAggregateRoot root)   at Kotrak.Common.Infrastructure.Repositories.AggregateRootRepository`2.Persist(TAggregateRoot root)   at Plant.Stock.BusinessLogic.Application.ProductionLots.ProductionLotService.ChangeQuantity(AggregateId productionLotId\', ""Comment 229: Quantity quantity) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Application\\\\\\\\ProductionLots\\\\\\\\ProductionLotService.cs:line 274   at Plant.Stock.BusinessLogic.Application.ProductionLots.CommandHandlers.ChangeProductionLotQuantityCommandHandler.Handle(ChangeProductionLotQuantityCommand command) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Application\\\\\\\\ProductionLots\\\\\\\\CommandHandlers\\\\\\\\ChangeProductionLotQuantityCommandHandler.cs:line 30   at Kotrak.Common.Infrastructure.Commands.CommandEnvironment.Run[TCommand](TCommand command)   at Kotrak.Common.Infrastructure.Commands.Decorators.IntercontextEventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command)   at Kotrak.Common.Infrastructure.Commands.Decorators.EventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command)   at Kotrak.Common.Infrastructure.Commands.Decorators.ValidationCommandEnvironmentDecorator.Run[TCommand](TCommand command)   at Castle.Proxies.Invocations.IRunEnvironment_Run.InvokeMethodOnTarget()   at Castle.DynamicProxy.AbstractInvocation.Proceed()   at Kotrak.Common.Infrastructure.Interceptors.LoggingInterceptor`1.Intercept(IInvocation invocation)ClientConnectionId:8f72d6b0-9bb0-4bd5-9ecf-79d29ffe9cd4Error Number:-2,State:0,Class:11{code}\'"", \'Comment 230: \\\'Request ze Stocka:{code:java}2023-01-24 18:56:55 (2e53ede8-9517-4e92-ba70-4a54a27c1a7c/Plant.Stock.BusinessLogic/SAKDSRV04/10032/9) [Error] Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware - Error during request{  ""scheme"": ""http""\', \'Comment 231:  ""host"": {    ""Value"": ""sakdsrv04:92""\', \'Comment 232:    ""HasValue"": true\', \'Comment 233:    ""Host"": ""sakdsrv04""\', \'Comment 234:    ""Port"": 92  }\', \'Comment 235:  ""path"": ""/api/productionLot/updateReservationsAndConfirm""\', \'Comment 236:  ""queryString"": []\', \'Comment 237:  ""requestBody"": ""{\\\\\\\\""productionLotId\\\\\\\\"":\\\\\\\\""41616471-4073-4d43-9413-13290367340d\\\\\\\\"",\\\\\\\\""businessUnitId\\\\\\\\"":\\\\\\\\""93f3b3c7-eefc-47ed-a18e-8629f8dc1c5e\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":2995.580000},\\\\\\\\""elements\\\\\\\\"":[{\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""a3e8359c-1434-47af-807b-194b09e15329\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":251.0},\\\\\\\\""reservations\\\\\\\\"":[{\\\\\\\\""deliveryId\\\\\\\\"":\\\\\\\\""d3fe0c16-69c1-42e6-a085-57b9d7419036\\\\\\\\"",\\\\\\\\""stockUnitId\\\\\\\\"":\\\\\\\\""b4bdeeae-2472-4738-bd4a-5f0b5f331708\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""t\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":0.251}}]},{\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""2d5d699e-9140-435c-b557-a904b15d0846\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":1.68},\\\\\\\\""reservations\\\\\\\\"":[{\\\\\\\\""deliveryId\\\\\\\\"":\\\\\\\\""34cf4324-c829-4286-b7ea-2aa653d6b25c\\\\\\\\"",\\\\\\\\""stockUnitId\\\\\\\\"":\\\\\\\\""6ee5a5ca-c350-40b6-9368-3bbe79b9c479\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""t\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":0.00168}}]},{\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""9915211b-5428-419f-ace3-500107b293c8\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":0.4},\\\\\\\\""reservations\\\\\\\\"":[{\\\\\\\\""deliveryId\\\\\\\\"":\\\\\\\\""ef8f9c94-733a-47e1-aff0-5d68c71560f1\\\\\\\\"",\\\\\\\\""stockUnitId\\\\\\\\"":\\\\\\\\""d262b243-0635-4658-9d75-5882d9362942\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""t\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":0.0004}}]},{\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""c790227e-d0d1-4391-84ec-b997d014b365\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":348.0},\\\\\\\\""reservations\\\\\\\\"":[{\\\\\\\\""deliveryId\\\\\\\\"":\\\\\\\\""882ff3a6-1c35-45ba-ad49-1cbce7aaadac\\\\\\\\"",\\\\\\\\""stockUnitId\\\\\\\\"":\\\\\\\\""b637f0b5-c5b5-45d6-811a-a8e622b65d1e\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""t\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":0.348}}]},{\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""b6693bc8-055e-4394-99ed-cd2ac383ab5c\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":3.0},\\\\\\\\""reservations\\\\\\\\"":[{\\\\\\\\""deliveryId\\\\\\\\"":\\\\\\\\""845f2076-870a-4c68-8a52-b081666cfe25\\\\\\\\"",\\\\\\\\""stockUnitId\\\\\\\\"":\\\\\\\\""6aee2c6f-fa5c-451d-9edd-d5e5e1e12150\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""t\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":0.003}}]},{\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""cb9254cd-11f3-45d1-8e9a-2379ea68b108\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":1388.0},\\\\\\\\""reservations\\\\\\\\"":[{\\\\\\\\""deliveryId\\\\\\\\"":\\\\\\\\""bcf1cff7-f7de-4e12-8666-b55c603a5de5\\\\\\\\"",\\\\\\\\""stockUnitId\\\\\\\\"":\\\\\\\\""e88d2913-317a-477b-8d8e-147e7d7cbad3\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""t\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":1.388}}]},{\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""523a75e3-f5e9-4ea7-88ef-9ba4fd1b9b1c\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":235.0},\\\\\\\\""reservations\\\\\\\\"":[{\\\\\\\\""deliveryId\\\\\\\\"":\\\\\\\\""e2151be8-cfdc-44d4-b1b9-520aa36820c8\\\\\\\\"",\\\\\\\\""stockUnitId\\\\\\\\"":\\\\\\\\""21df176b-34bf-46b3-803d-dd8e5cb02ba7\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""t\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":0.235}}]},{\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""ccb356e8-b899-46d6-97aa-7f4af566f8d3\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":73.0},\\\\\\\\""reservations\\\\\\\\"":[{\\\\\\\\""deliveryId\\\\\\\\"":\\\\\\\\""67fe0c1f-ae58-4574-a5b5-fae0944b2b73\\\\\\\\"",\\\\\\\\""stockUnitId\\\\\\\\"":\\\\\\\\""67c7f7f8-651f-49c4-a41e-127c09088fa8\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""t\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":0.073}}]},{\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""97ae7ce1-ac4a-4852-8f5e-6a62446c1b3c\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":450.0},\\\\\\\\""reservations\\\\\\\\"":[{\\\\\\\\""deliveryId\\\\\\\\"":\\\\\\\\""932f7272-1f25-411e-a64a-1c8d42bfd98f\\\\\\\\"",\\\\\\\\""stockUnitId\\\\\\\\"":\\\\\\\\""2d67090b-fada-43fb-b7b4-387680bf3ded\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""t\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":0.45}}]},{\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""eacc5086-a76d-45b8-b34b-aadcdf8063de\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":6.26},\\\\\\\\""reservations\\\\\\\\"":[{\\\\\\\\""deliveryId\\\\\\\\"":\\\\\\\\""090f8a80-f370-43b4-b268-0304d8b2e108\\\\\\\\"",\\\\\\\\""stockUnitId\\\\\\\\"":\\\\\\\\""12363980-6291-444c-a76a-2342b1c1c3d7\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""t\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":0.00626}}]},{\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""ed1e952c-87b4-46cd-84a3-5f2c50fffb4a\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":15.4},\\\\\\\\""reservations\\\\\\\\"":[{\\\\\\\\""deliveryId\\\\\\\\"":\\\\\\\\""43743169-cb9d-4b48-a313-fd1d38ce7b72\\\\\\\\"",\\\\\\\\""stockUnitId\\\\\\\\"":\\\\\\\\""89e420a1-c8d9-4721-964a-02f307513427\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""t\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":0.0154}}]},{\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""99faf3a0-9376-4ac9-953e-c5d13887c0c6\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":218.0},\\\\\\\\""reservations\\\\\\\\"":[{\\\\\\\\""deliveryId\\\\\\\\"":\\\\\\\\""a1e07f9f-f4fb-4405-b833-583746841a68\\\\\\\\"",\\\\\\\\""stockUnitId\\\\\\\\"":\\\\\\\\""e250823d-0c9e-4aa0-9539-5df2ffdd658a\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""t\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":0.218}}]},{\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""31f81b61-b661-4d65-84d4-707133fa2816\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":2.0},\\\\\\\\""reservations\\\\\\\\"":[{\\\\\\\\""deliveryId\\\\\\\\"":\\\\\\\\""f3af5dbd-4fb0-458c-8200-45f81258592c\\\\\\\\"",\\\\\\\\""stockUnitId\\\\\\\\"":\\\\\\\\""ddbd03ce-2068-4432-ae7e-a6477f1704f2\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""t\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":0.002}}]},{\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""9c5d67c9-a8d5-4bee-b4d0-d0b18233ad9a\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":0.6},\\\\\\\\""reservations\\\\\\\\"":[{\\\\\\\\""deliveryId\\\\\\\\"":\\\\\\\\""e118e00e-7ed0-4522-bc80-060fa157ced6\\\\\\\\"",\\\\\\\\""stockUnitId\\\\\\\\"":\\\\\\\\""849bb14d-53f7-4ef3-ad5c-7ff0af6e734a\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""t\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":0.0006}}]},{\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""c7f1f3c2-3267-46dd-a88e-cad65fd117b8\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":3.24},\\\\\\\\""reservations\\\\\\\\"":[{\\\\\\\\""deliveryId\\\\\\\\"":\\\\\\\\""90227a2e-0100-4223-83f0-7aea35fd2250\\\\\\\\"",\\\\\\\\""stockUnitId\\\\\\\\"":\\\\\\\\""dde7ba82-8eb6-4c85-8d5f-160932a2fcd3\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""t\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":0.00324}}]},{\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""1ffec991-c0ee-4d19-be6e-4d1ab446d7c9\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""pcs\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":60.0},\\\\\\\\""reservations\\\\\\\\"":[]}],\\\\\\\\""siloItems\\\\\\\\"":[]}""}.System.ArgumentException: Unit mismatch   at Kotrak.Common.SharedKernel.Quantity.ToCommonUnit(Quantity x1\', \'Comment 238: Quantity x2)   at Kotrak.Common.SharedKernel.Quantity.op_Subtraction(Quantity q\', \'Comment 239: Quantity q2)   at Plant.Stock.BusinessLogic.Domain.StockManagement.StockData.DecreaseQuantity(Quantity quantity) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Domain\\\\\\\\StockManagement\\\\\\\\StockData.cs:line 58   at Plant.Stock.BusinessLogic.Domain.StockReplenishment.Policies.StockUnitBaseReplenishmentPolicy.FetchReplenishment(ReplenishmentData replenishmentData) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Domain\\\\\\\\StockReplenishment\\\\\\\\Policies\\\\\\\\StockUnitBaseReplenishmentPolicy.cs:line 28   at Plant.Stock.BusinessLogic.Domain.ProductionSettlement.Policies.ProductionSettlementBasePolicy.FetchReplenishment(IEnumerable`1 filteredStockData\', \'Comment 240: Quantity quantity) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Domain\\\\\\\\ProductionSettlement\\\\\\\\Policies\\\\\\\\ProductionSettlementBasePolicy.cs:line 104   at Plant.Stock.BusinessLogic.Domain.ProductionSettlement.Policies.ProductionSettlementBasePolicy.FetchProductionElementReplenishment(IEnumerable`1 stockData\', \'Comment 241: ProductionElementSettlementData settlementData\', \'Comment 242: List`1 response\', \'Comment 243: List`1 missingStock) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Domain\\\\\\\\ProductionSettlement\\\\\\\\Policies\\\\\\\\ProductionSettlementBasePolicy.cs:line 90   at Plant.Stock.BusinessLogic.Domain.ProductionSettlement.Policies.ProductionSettlementBasePolicy.FetchProductionSettlement(IEnumerable`1 stockData\', \'Comment 244: IEnumerable`1 productionElementsData) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Domain\\\\\\\\ProductionSettlement\\\\\\\\Policies\\\\\\\\ProductionSettlementBasePolicy.cs:line 48   at Plant.Stock.BusinessLogic.Domain.ProductionSettlement.ProductionSettlementDomainService.FetchProductionSettlement(IEnumerable`1 stockForSettlement\', \'Comment 245: IEnumerable`1 stockUnits\', \'Comment 246: IEnumerable`1 deliveries\', \'Comment 247: IEnumerable`1 locations\', \'Comment 248: IProductionSettlementPolicy productionSettlementPolicy) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Domain\\\\\\\\ProductionSettlement\\\\\\\\ProductionSettlementDomainService.cs:line 220   at Plant.Stock.BusinessLogic.Domain.ProductionSettlement.ProductionSettlementDomainService.ExecuteProductionSettlement(ProductionSettlementData data) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Domain\\\\\\\\ProductionSettlement\\\\\\\\ProductionSettlementDomainService.cs:line 61   at Plant.Stock.BusinessLogic.Domain.ProductionLots.Services.ConfirmProductionDomainService.ExecuteProductionSettlement(ConfirmProductionLotDomainData data) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Domain\\\\\\\\ProductionLots\\\\\\\\Services\\\\\\\\ConfirmProductionDomainService.cs:line 102   at Plant.Stock.BusinessLogic.Domain.ProductionLots.Services.ConfirmProductionDomainService.ConfirmProductionLot(ConfirmProductionLotDomainData data) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Domain\\\\\\\\ProductionLots\\\\\\\\Services\\\\\\\\ConfirmProductionDomainService.cs:line 52   at Plant.Stock.BusinessLogic.Application.ProductionLots.ProductionLotService.ConfirmProduction(ProductionLot productionLot\', \'Comment 249: IEnumerable`1 productionElements\', \'Comment 250: IEnumerable`1 ingredientDeliveries\', \'Comment 251: IEnumerable`1 ingredientStockUnits\', \'Comment 252: IEnumerable`1 locations\', \'Comment 253: IEnumerable`1 transcodingDefinitions) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Application\\\\\\\\ProductionLots\\\\\\\\ProductionLotService.cs:line 797   at Plant.Stock.BusinessLogic.Application.ProductionLots.ProductionLotService.UpdateReservationsAndConfirmProductionLot(UpdateReservationsAndConfirmProductionLotActionData data) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Application\\\\\\\\ProductionLots\\\\\\\\ProductionLotService.cs:line 459   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 32   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.Proxies.Invocations.IRunEnvironment_Run.InvokeMethodOnTarget()   at Castle.DynamicProxy.AbstractInvocation.Proceed()   at Kotrak.Common.Infrastructure.Interceptors.LoggingInterceptor`1.Intercept(IInvocation invocation)   at Castle.DynamicProxy.AbstractInvocation.Proceed()   at Castle.Proxies.ICommandRunEnvironmentProxy.Run[TCommand](TCommand command)   at Kotrak.Common.Infrastructure.Commands.StandardGate.Dispatch[TCommand](TCommand command)   at Kotrak.Common.Infrastructure.Commands.Decorators.AsyncGateDecorator.Dispatch[TCommand](TCommand command)   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_method9745(Closure \', \'Comment 254: Object \', \'Comment 255: Object[] )   at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor.SyncObjectResultExecutor.Execute(IActionResultTypeMapper mapper\', \'Comment 256: ObjectMethodExecutor executor\', \'Comment 257: Object controller\', \'Comment 258: Object[] arguments)   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeActionMethodAsync()   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next\', \'Comment 259: Scope& scope\', \'Comment 260: Object& state\', \'Comment 261: 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 262: Scope& scope\', \'Comment 263: Object& state\', \'Comment 264: 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 265: Task lastTask\', \'Comment 266: State next\', \'Comment 267: Scope scope\', \'Comment 268: Object state\', \'Comment 269: Boolean isCompleted)   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker\', \'Comment 270: Task task\', \'Comment 271: IDisposable scope)   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker\', \'Comment 272: Task task\', \'Comment 273: IDisposable scope)   at Microsoft.AspNetCore.Routing.EndpointMiddleware.<Invoke>g__AwaitRequestTask|6_0(Endpoint endpoint\', \'Comment 274: Task requestTask\', \'Comment 275: ILogger logger)   at Swashbuckle.AspNetCore.SwaggerUI.SwaggerUIMiddleware.Invoke(HttpContext httpContext)   at Swashbuckle.AspNetCore.Swagger.SwaggerMiddleware.Invoke(HttpContext httpContext\', ""Comment 276: ISwaggerProvider swaggerProvider)   at Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware.Invoke(HttpContext httpContext){code}\'"", ""Comment 277: \'Hi,Tere is a unit mismatch on item:!image-2023-01-24-18-20-34-818.png!!image-2023-01-24-18-21-07-649.png!!image-2023-01-24-18-22-41-696.png!Please"", ""Comment 278: verify item.Regards\'"", ""Comment 279: \'thank you task can be closed \']""]\nRelated Issues:\n[]\n\n### End'}"
638,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8394\n\n### Instruction:\nPlease close the contracts. Customer is not able to the following notification\r\nClose old contract. Closing give errors.\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: \'Contracts were closed after selecting the context from the PO documents.\'"", ""Comment 4: \'!image-2023-01-25-07-38-53-802.png!\'"", ""Comment 5: \'!image-2!\'"", ""Comment 6: \'!image-3!\'"", ""Comment 7: \'HI"", ""Comment 8: are these 5/07/2022/INT and 8/07/2022/INT also supposed to be closed?\'"", ""Comment 9: \'Only the mentioned contracts.!image-4!\'"", ""Comment 10: \'PO-4/7/2022/INT and PO-6/7/2022/INT are partially completed"", \'Comment 11: so they have the status Closed in progress.PO-9/7/2022/INT was only confirmed\', ""Comment 12: so it has the Closed status.\'"", ""Comment 13: \'Ticket can be closed\']""]\nRelated Issues:\n[]\n\n### End'}"
639,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8393\n\n### Instruction:\nWO(PD)120/1/23 cannot be closed due to WD-212 being in status processable. Please cancel this WD so we can close the WO\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: \'Please check should be correct now.Please use erase option  !screenshot-2! \'"", ""Comment 4: \'Hi Piotr"", ""Comment 5: thanks Ticket can be closed\']""]\nRelated Issues:\n[]\n\n### End'}"
640,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8392\n\n### Instruction:\nSales order SO000057337 has to be produced early this afternoon.\r\nIt is in DHC but not in DHP Meppel.\r\n\r\nPlease investigate.\n\n### Response:\n[""Comment 1: [\'Hello"", ""Comment 2: We kindly inform you that wecurrentlyare processing another Priority1 task.We will revert to processing your task as soon as possible.Regards\'"", ""Comment 3: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 4: \'The item for the order was missing in DHCService (DHHitem).It was corrected.Please resend order.Fixed in dhc 3.0.60 - about missing items DHH in DHCservice.\'"", ""Comment 5: \'After resending the order popped up in DHP.Thank you for the support"", ""Comment 6: the ticket can be closed.\']""]\nRelated Issues:\n[]\n\n### End'}"
641,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8391\n\n### Instruction:\nProśba o wsparcie, wyrzuca błąd przy rozrachunku\r\nW razie problemów prosze kontaktowac sie z Business Reporterem\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: \'Any news ??\'"", ""Comment 4: \'Any news ??\'"", ""Comment 5: \'documents have been settled"", ""Comment 6: please verify\'"", ""Comment 7: \'Task to close \']""]\nRelated Issues:\n[]\n\n### End'}"
642,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8390\n\n### Instruction:\nFor PI-RTN/2022/0067 ID72972 and SI-RLN/2022/0269 ID72971 I used a wrong description. It should be 196 Rosékalveren 24-11 stal De Kievit. Can this be modified?\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: \'Changed descriptions in both documents.\']""]\nRelated Issues:\n[]\n\n### End'}"
643,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8389\n\n### Instruction:\nSystem didin\'t create assemly pallets for WMO\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: \'Please "", ""Comment 4: can you exit the document?\'"", ""Comment 5: \'!image-2023-01-24-10-20-19-083.png!{code:java}select RgM_AssemblyLogisticId"", \'Comment 6: RgM_ArtId\', \'Comment 7: RgM_Id,RgM_Quantity,RgM_IsReleased,RgM_IsActivated,RgM_Type,RgM_AssemblyLogisticId--into dbo.rgm_dgs3033from [dbo].[WMSInternalDocumentOrderSubElements] wjoin RegisterMappings r on WiS_RgmId = RgM_idwhere WiS_ElementId  in (select WiE_Id from WMSInternalDocumentOrderElements where WiE_HeaderId = 2740)select RgM_AssemblyLogisticId\', \'Comment 8: RgM_ArtId\', ""Comment 9: RgM_Id,RgM_Quantity,RgM_IsReleased,RgM_IsActivated,RgM_Type,RgM_AssemblyLogisticId,*from RegisterMappings where rgm_id=1269129  select * from WMSInternalDocumentOrderAssemblies where WiA_HeaderId = 2740{code}\'"", \'Comment 10: ""{code:java}SELECT Cst_Code,RTRIM(CtA_Name1 + \\\' \\\' + isnull(CtA_Name2,\\\'\\\') + \\\' \\\' + isnull(CtA_Name3,\\\'\\\')) CustomerName,CtA_Street +\\\'\', ""Comment 11: \' + CtA_PostCode + \' \'+CtA_City as Address,dbo.GetDocumentNumber(dbo.OrderMapper(odh_ordtype)"", \'Comment 12: odh_ordnumber\', \'Comment 13: odh_ordmonth\', \'Comment 14: odh_ordyear\', \'Comment 15: odh_ordseries) DocNumber,RP.RgM_Id,RP.RgM_Code,RP.RgM_Quantity,count(RC.RgM_Id) bagsCount,isnull(A.WiA_CloseUserId,0) CloseUserId,RP.RgM_IsReleased,OE.Ode_id,E.WiE_OdeId FROM dbo.WMSInternalDocumentOrderAssemblies Ajoin dbo.RegisterMappings RP on A.WiA_RgMId = RP.RgM_IdLEFT JOIN dbo.RegisterMappings RC on RP.RgM_Id = RC.RgM_AssemblyLogisticIdLEFT JOIN dbo.WMSInternalDocumentOrderSubElements SE on RC.RgM_Id = SE.WiS_RgmIdLEFT JOIN dbo.WMSInternalDocumentOrderElements E on SE.WiS_ElementId = E.WiE_IdLEFT JOIN dbo.OrderElement OE on E.WiE_OdeId = OE.Ode_Id LEFT JOIN dbo.OrderHeader OH on OE.OdE_OdHId = OH.OdH_IdLEFT JOIN dbo.CustomerCard CC on OH.OdH_Cst2Id = CC.Cst_IdLEFT JOIN dbo.CustomerAdressCard AC on OH.OdH_CtA2Id = AC.CtA_IdWHERE WiA_HeaderId = 2740group by Cst_Code,CtA_Name1,CtA_Name2,CtA_Name3,CtA_Street\', \'Comment 16: CtA_PostCode,CtA_City,RP.RgM_Id,OdH_OrdNumber,OdH_OrdMonth,OdH_OrdYear,OdH_OrdSeries,RP.RgM_Code,RP.RgM_Quantity,WiA_CloseUserId,RP.RgM_IsReleased\', \'Comment 17: dbo.GetDocumentNumber(dbo.OrderMapper(odh_ordtype)\', \'Comment 18: odh_ordnumber\', \'Comment 19: odh_ordmonth\', \'Comment 20: odh_ordyear\', \'Comment 21: odh_ordseries),OE.Ode_id,E.WiE_OdeId{code}!image-2023-01-24-10-39-38-621!----Prawidłowy przykład dla HeaderId = 2732!image-2023-01-24-10-40-36-891!----h2. Aktualny stan na 10:41 24.01.2023!image-2023-01-24-10-42-05-187!----h2. Po poprawie !image-2023-01-24-10-51-38-846!""\', ""Comment 22: \'There was no link to the order. It was linked from the database  !screenshot-2! \'"", ""Comment 23: \'where was there no link to the order?\'"", ""Comment 24: \'Missing WiE_OdeId in dbo.WMSInternalDocumentOrderElements\'"", ""Comment 25: \'task to be closed\'"", ""Comment 26: \'[[DHP] [WMS] ZPM(K) utworzony"", ""Comment 27: brakuje składanki|onenote:https://kotrak.sharepoint.com/sites/erpasysta/Shared%20Documents/Baza%20wiedzy/Baza%20Wiedzy%20-%20ERPSD/Klienci/DEHEUS/DEHEUS%20APPLICATIONS/Polska/Baza%20wiedzy/DHP%20Produkcja.one#%5bDHP%5d%20%5bWMS%5d%20ZPM(K)%20utworzony,%20brakuje%20sk%C5%82adanki&section-id=\\\\\\\\{CC5FB5C6-8E0D-42E5-8319-3DC0E80D8642}&page-id=\\\\\\\\{3E43D2FD-CF4C-4FC7-96D1-308C582AEBD5}&end] ([Widok sieci Web|https://kotrak.sharepoint.com/sites/erpasysta/_layouts/OneNote.aspx?id=%2Fsites%2Ferpasysta%2FShared%20Documents%2FBaza%20wiedzy%2FBaza%20Wiedzy%20-%20ERPSD&wd=target%28Klienci%2FDEHEUS%2FDEHEUS%20APPLICATIONS%2FPolska%2FBaza%20wiedzy%2FDHP%20Produkcja.one%7CCC5FB5C6-8E0D-42E5-8319-3DC0E80D8642%2F%5BDHP%5D%20%5BWMS%5D%20ZPM%28K%5C%29%20utworzony%2C%20brakuje%20sk%C5%82adanki%7C3E43D2FD-CF4C-4FC7-96D1-308C582AEBD5%2F%29])\']""]\nRelated Issues:\n[]\n\n### End'}"
644,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8387\n\n### Instruction:\nWe produced production SUR1222-P-MD - 0871200123026 and confirmed, but production is not available in DHC. Could you check why production didn\'t integrated and fix it?\r\n\r\nThank you\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 2: \\\'!image-2023-01-23-23-22-51-714.png!2023-01-23 19:21:35 (14755c15-2f75-42e9-9303-b601ac9d9be8/Plant.Prod.BusinessLogic/BR-4-SV-VM0204/16144/8) [Error] Kotrak.Integration.IntegrationPluginCommon.IntercontextCommunication.Inbound.InboundIntercontextErrorHandler - Error during handling message of type ""Plant.PCS.BusinessLogic.DomainAbstractions.ProductionLots.ProductionBatchReportUpdatedEvent""\', \'Comment 3: retry no 1Microsoft.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 (258): The wait operation timed out. at Microsoft.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception\', \'Comment 4: Boolean breakConnection\', \'Comment 5: Action`1 wrapCloseInAction) at Microsoft.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj\', \'Comment 6: Boolean callerHasConnectionLock\', \'Comment 7: Boolean asyncClose) at Microsoft.Data.SqlClient.TdsParserStateObject.ThrowExceptionAndWarning(Boolean callerHasConnectionLock\', \'Comment 8: Boolean asyncClose) at Microsoft.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject stateObj\', \'Comment 9: UInt32 error) at Microsoft.Data.SqlClient.TdsParserStateObject.ReadSniSyncOverAsync() at Microsoft.Data.SqlClient.TdsParserStateObject.TryReadNetworkPacket() at Microsoft.Data.SqlClient.TdsParserStateObject.TryPrepareBuffer() at Microsoft.Data.SqlClient.TdsParserStateObject.TryReadByte(Byte& value) at Microsoft.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior\', \'Comment 10: SqlCommand cmdHandler\', \'Comment 11: SqlDataReader dataStream\', \'Comment 12: BulkCopySimpleResultSet bulkCopyHandler\', \'Comment 13: TdsParserStateObject stateObj\', \'Comment 14: Boolean& dataReady) at Microsoft.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior\', \'Comment 15: SqlCommand cmdHandler\', \'Comment 16: SqlDataReader dataStream\', \'Comment 17: BulkCopySimpleResultSet bulkCopyHandler\', \'Comment 18: TdsParserStateObject stateObj) at Microsoft.Data.SqlClient.SqlBulkCopy.RunParser(BulkCopySimpleResultSet bulkCopyHandler) at Microsoft.Data.SqlClient.SqlBulkCopy.CopyBatchesAsyncContinuedOnSuccess(BulkCopySimpleResultSet internalResults\', \'Comment 19: String updateBulkCommandText\', \'Comment 20: CancellationToken cts\', \'Comment 21: TaskCompletionSource`1 source) at Microsoft.Data.SqlClient.SqlBulkCopy.CopyBatchesAsyncContinued(BulkCopySimpleResultSet internalResults\', \'Comment 22: String updateBulkCommandText\', \'Comment 23: CancellationToken cts\', \'Comment 24: TaskCompletionSource`1 source) at Microsoft.Data.SqlClient.SqlBulkCopy.CopyBatchesAsync(BulkCopySimpleResultSet internalResults\', \'Comment 25: String updateBulkCommandText\', \'Comment 26: CancellationToken cts\', \'Comment 27: TaskCompletionSource`1 source) at Microsoft.Data.SqlClient.SqlBulkCopy.WriteToServerInternalRestContinuedAsync(BulkCopySimpleResultSet internalResults\', \'Comment 28: CancellationToken cts\', \'Comment 29: TaskCompletionSource`1 source) at Microsoft.Data.SqlClient.SqlBulkCopy.WriteToServerInternalRestAsync(CancellationToken cts\', \'Comment 30: TaskCompletionSource`1 source) at Microsoft.Data.SqlClient.SqlBulkCopy.WriteToServerInternalAsync(CancellationToken ctoken) at Microsoft.Data.SqlClient.SqlBulkCopy.WriteRowSourceToServerAsync(Int32 columnCount\', \'Comment 31: CancellationToken ctoken) at Microsoft.Data.SqlClient.SqlBulkCopy.WriteToServer(DataTable table\', \'Comment 32: DataRowState rowState) at EFCore.BulkExtensions.SQLAdapters.SQLServer.SqlOperationsServerAdapter.InsertAsync[T](DbContext context\', \'Comment 33: Type type\', \'Comment 34: IList`1 entities\', \'Comment 35: TableInfo tableInfo\', \'Comment 36: Action`1 progress\', \'Comment 37: Boolean isAsync\', \'Comment 38: CancellationToken cancellationToken) at EFCore.BulkExtensions.SQLAdapters.SQLServer.SqlOperationsServerAdapter.InsertAsync[T](DbContext context\', \'Comment 39: Type type\', \'Comment 40: IList`1 entities\', \'Comment 41: TableInfo tableInfo\', \'Comment 42: Action`1 progress\', \'Comment 43: Boolean isAsync\', \'Comment 44: CancellationToken cancellationToken) at EFCore.BulkExtensions.SQLAdapters.SQLServer.SqlOperationsServerAdapter.Insert[T](DbContext context\', \'Comment 45: Type type\', \'Comment 46: IList`1 entities\', \'Comment 47: TableInfo tableInfo\', \'Comment 48: Action`1 progress) at EFCore.BulkExtensions.DbContextBulkTransaction.Execute[T](DbContext context\', \'Comment 49: Type type\', \'Comment 50: IList`1 entities\', \'Comment 51: OperationType operationType\', \'Comment 52: BulkConfig bulkConfig\', \'Comment 53: Action`1 progress) at EFCore.BulkExtensions.DbContextBulkExtensions.BulkInsert[T](DbContext context\', \'Comment 54: IList`1 entities\', \'Comment 55: BulkConfig bulkConfig\', \'Comment 56: Action`1 progress\', \'Comment 57: Type type) at Kotrak.Common.Infrastructure.EF.EventRepository.GenericEventRepositoryEf`2.Persist(TAggregateRoot aggregateRoot) at Kotrak.Common.Infrastructure.Repositories.AggregateRootRepository`2.PersistEvents(TAggregateRoot root) at Kotrak.Common.Infrastructure.Repositories.AggregateRootRepository`2.Persist(TAggregateRoot root) at Plant.Prod.BusinessLogic.Application.ProductionLots.ProductionLotService.UpdateBatchReport(UpdateBatchReportActionData data) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Application\\\\\\\\ProductionLots\\\\\\\\ProductionLotService.cs:line 527 at Plant.Prod.BusinessLogic.Application.ProductionLots.CommandHandlers.UpdateBatchReportCommandHandler.Handle(UpdateBatchReportCommand command) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Application\\\\\\\\ProductionLots\\\\\\\\CommandHandlers\\\\\\\\UpdateBatchReportCommandHandler.cs:line 22 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 Castle.Proxies.ICommandRunEnvironmentProxy.Run[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.StandardGate.Dispatch[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.AsyncGateDecorator.Dispatch[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.HistoryGateDecorator.Dispatch[TCommand](TCommand command) at Plant.Prod.BusinessLogic.Infrastructure.ContextIntegration.MessageHandlers.BaseMessageHandler`2.Handle(TMessage message) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Infrastructure.ContextIntegration\\\\\\\\MessageHandlers\\\\\\\\BaseMessageHandler.cs:line 27 at Kotrak.Integration.IntegrationPluginCommon.IntercontextCommunication.Inbound.IntercontextInboundHandler`2.Handle(InternalStorageDto message)ClientConnectionId:8600914b-326c-41d8-b0cf-cc2acc8535c9Error Number:-2,State:0,Class:11Wykonana reindeksacja bazy DHC country i DHC service nie pomogław logach w DHP nie ma żadnego komunikatu!image-2023-01-24-00-30-11-956.png!przy próbie kolejnej wysyłki LOT z DHP nie pojawia sie nowy wis w logachD:\\\\\\\\Kotrak\\\\\\\\dhp30_IIS\\\\\\\\PlantIntegrationDhcService\\\\\\\\LogsD:\\\\\\\\Kotrak\\\\\\\\dhp30_IIS\\\\\\\\PlantProductionBusinessLogic\\\\\\\\Logsmoduły w IISPlantProductionBusinessLogic iPlantIntegrationDhcService były restartowaneDHC service było restartowaneselect lotnumber\', ""Comment 58: *--update p set ProductionLotStatus=ProductionLotStatusfrom ProductionLots p where lotnumber like \\\\\'0871200123026%\\\\\'select lotnumber"", \'Comment 59: *--update p set ProductionLotStatus=ProductionLotStatusfrom ProductionLots pselect lotnumber\', ""Comment 60: * from ProductionLots where ReadyProductId = \\\\\'C1A626A7-E181-4CD8-8E7A-EAC19DDB2B61\\\\\'select lotnumber"", ""Comment 61: * from ProductionLots where recipeid in (\\\\\'64FCA566-0933-48B1-B569-560CB1737B42\\\\\'"", ""Comment 62: \\\\\'17D9E9E0-31E7-401E-8DF7-ED5E447C5C04\\\\\')select * from Items where id in ( \\\\\'BAC9E85F-0B80-4371-8459-461D2C0F9184\\\\\'"", ""Comment 63: \\\\\'A4018A7F-5DDC-468E-90A5-DA5AD769A4D2\\\\\')select * from Recipes where id in (\\\\\'64FCA566-0933-48B1-B569-560CB1737B42\\\\\'"", ""Comment 64: \\\\\'17D9E9E0-31E7-401E-8DF7-ED5E447C5C04\\\\\')select * from RecipeElements where id in (\\\\\'64FCA566-0933-48B1-B569-560CB1737B42\\\\\'"", ""Comment 65: \\\\\'17D9E9E0-31E7-401E-8DF7-ED5E447C5C04\\\\\')select * from RecipeElements r1join items i on i.id = r1.ItemIdfull outer join RecipeElements r2 on r1.ItemId =r2.ItemId and r2.id=\\\\\'17D9E9E0-31E7-401E-8DF7-ED5E447C5C04\\\\\'where r1.id  in (\\\\\'64FCA566-0933-48B1-B569-560CB1737B42\\\\\') order by r2.Noselectselect * from Items where--itemtype = 1id = \\\\\'BAC9E85F-0B80-4371-8459-461D2C0F9184\\\\\' 118 1select * from cdn.b9a646dd-dc8b-4e3d-933d-d1251013f306\'"", ""Comment 66: \'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 67: \'[^ProductionLotConfirmedEvent.txt]\'"", ""Comment 68: \'PLR is now in DHC!image-2023-01-24-09-17-38-012.png!\'"", \'Comment 69: ""Hello Piotr,I checked and now it\\\'s correct. Do you know why we had this problem?""\', ""Comment 70: \'This problem with PLR should be treated as an incident,the next time an error occurs an RCA will be created.We had to resend the message to DHC.Regards.\'"", ""Comment 71: \'+[[DHP 3.0] Ponowne przesłanie PLR do DHC - generowanie message jak nie ma(ostatni pkt).|onenote:https://kotrak.sharepoint.com/sites/erpasysta/Shared%20Documents/Baza%20wiedzy/Baza%20Wiedzy%20-%20ERPSD/Klienci/DEHEUS/DEHEUS%20APPLICATIONS/RPA/Baza%20wiedzy.one#%5bDHP%203.0%5d%20Ponowne%20przes%C5%82anie%20PLR%20do%20DHC%20&section-id=\\\\\\\\{A2F09CD6-A23A-42F3-92F5-ED66B521455B}&page-id=\\\\\\\\{7502CC07-E06E-48A2-82DD-39E0D4819C77}&end] ([Widok sieci Web|https://kotrak.sharepoint.com/sites/erpasysta/_layouts/OneNote.aspx?id=%2Fsites%2Ferpasysta%2FShared%20Documents%2FBaza%20wiedzy%2FBaza%20Wiedzy%20-%20ERPSD&wd=target%28Klienci%2FDEHEUS%2FDEHEUS%20APPLICATIONS%2FRPA%2FBaza%20wiedzy.one%7CA2F09CD6-A23A-42F3-92F5-ED66B521455B%2F%5BDHP%203.0%5D%20Ponowne%20przes%C5%82anie%20PLR%20do%20DHC%20%7C7502CC07-E06E-48A2-82DD-39E0D4819C77%2F%29])+\'"", ""Comment 72: \'All information was provided in the last comment.This ticket is closed.Regards.\']""]\nRelated Issues:\n[]\n\n### End'}"
645,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8386\n\n### Instruction:\nIn DHP tema there a re a few plr from 2020 that we would want to get rid of as it is not making the plrs presentable. can you help\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 2: ""Could you please provide us with those PLRs\\\' numbers?Regards""\', ""Comment 3: \'!image!\'"", \'Comment 4: ""Could you please clarify? Do you want us to delete them from application? Why don\\\'y you cancel them?Regards""\', ""Comment 5: \'cancelling them does not remove them. please delete them form application \'"", ""Comment 6: \'Tych PLR nie ma w DHC"", \'Comment 7: wzięłam zakres dat taki\', ""Comment 8: jakie są daty na ich screenie!image-2023-01-24-15-47-13-760.png!!image-2023-01-24-15-47-13-760!\'"", ""Comment 9: \'!image-2023-01-24-16-26-55-534.png!\'"", ""Comment 10: \'Requested PLRs have been deleted from all modules in Plant. Please"", ""Comment 11: verify.Regards\'"", ""Comment 12: \'thanks it has been cleared. please close\'"", ""Comment 13: \'Thank you.Regards\']""]\nRelated Issues:\n[]\n\n### End'}"
646,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8385\n\n### Instruction:\nProblem z ponowną fiskalizacją fs91/01/22/Łpoz\r\nBłąd w załączniku \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: \'Could you please clarify why are you trying to fiscalize FV second time?Regards\'"", ""Comment 4: \'Jednak będzie bez fiskalizacji. Błąd uzytkownika Temat do zamknięcia \'"", ""Comment 5: \'!image-2023-01-23-16-16-18-289.png!\']""]\nRelated Issues:\n[]\n\n### End'}"
647,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8384\n\n### Instruction:\nSame problem again. After creating a VT ticket, no warehouse order is created.\r\n\r\nVT-388 Can you please check this?\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 2: ""Dear Nemanja,I have restarted application again. Please\', \'Comment 3: lest me know if it helped,Can you check if the problem still occurs now and cancel the problematic VT\\\'s and re-issue?Regards""\', \'Comment 4: ""Again the same problem\', \'Comment 5: now we can\\\'t see wo for vt VT-422/1/23""\', ""Comment 6: \'VT-422/1/23id=fab8158a-2be8-4ae8-8975-81dace95aa07\'"", ""Comment 7: \'Log jest po modify date"", \'Comment 8: po id czy numerze VT\', ""Comment 9: nic!image-2023-01-24-14-14-52-290.png!{code:java}2023-01-24 11:52:29 (0d514f08-657b-46e3-a3fe-8f9b788144a1/Plant.WMS.BusinessLogic/RSIIS01/17904/9) [Error] Kotrak.Common.Infrastructure.ICommandRunEnvironment - Error during Void Run[CreatePerformDispatchWarehouseOrderCommand](Plant.WMS.BusinessLogic.Application.Interfaces.WarehouseOrders.Commands.CreatePerformDispatchWarehouseOrderCommand) methodKotrak.Common.Application.Exceptions.BusinessLogicException: Item 20365-B10 is archived ---> Kotrak.Common.Application.Exceptions.BusinessLogicException: ItemIsArchivedMessage   at Plant.WMS.BusinessLogic.Application.WarehouseOrders.WarehouseOrderService.GetItemOrThrow(AggregateId itemId) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Application\\\\\\\\WarehouseOrders\\\\\\\\WarehouseOrderService.cs:line 1078   at Plant.WMS.BusinessLogic.Application.WarehouseOrders.WarehouseOrderService.AssertCreateWarehouseOrderElement(CreateWarehouseOrderElementDataStructure elementDataStructure) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Application\\\\\\\\WarehouseOrders\\\\\\\\WarehouseOrderService.cs:line 909   at Plant.WMS.BusinessLogic.Application.WarehouseOrders.WarehouseOrderService.CreatePerformDispatchWarehouseOrder(CreateWarehouseOrderDataStructure dataStructure) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Application\\\\\\\\WarehouseOrders\\\\\\\\WarehouseOrderService.cs:line 188   at Plant.WMS.BusinessLogic.Application.WarehouseOrders.WarehouseOrderService.CreatePerformDispatchWarehouseOrders(CreateWarehouseOrderDataStructure dataStructure) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Application\\\\\\\\WarehouseOrders\\\\\\\\WarehouseOrderService.cs:line 207   at Plant.WMS.BusinessLogic.Application.Workflows.WorkflowRunner.Run(Workflow workflow) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Application\\\\\\\\Workflows\\\\\\\\WorkflowRunner.cs:line 17   at 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 10: ""{code:java}SELECT *  FROM [DHPlantVCBusinessLogicMain].[dbo].[VehicleTicketPackedDispatchElements] where SourceDocumentNumber = \\\'SO-226/1/23/S\\\' order by No desc  SELECT *  FROM [DHPlantVCBusinessLogicMain].[dbo].[Items] where id in (\\\'C8F78926-607A-451B-BE62-16BCB2C84395\\\',\\\'EBAE1313-DC15-47AE-B641-AF19C501D61C\\\',\\\'83E9AD90-9DD0-48F8-B156-46AF9506201F\\\',\\\'6006F666-ABE4-488F-9159-D95C6B3D0831\\\',\\\'FEE125C4-63DD-49DD-95ED-49D65F0EF9B1\\\',\\\'87BD8B45-7ACA-4482-9100-15A53B851FBB\\\',\\\'9C020A11-3003-4173-9C47-3939161D4781\\\',\\\'6B183163-82B0-4C40-987B-4BFF53A9B729\\\',\\\'59F2C964-483E-4A51-908C-76AF65996B02\\\',\\\'7A82B2B7-0B5C-497A-9F2E-DBD5F6BC5CAC\\\'){code}""\', ""Comment 11: \'!image-2023-01-24-14-16-50-642.png!\'"", ""Comment 12: \'!image-2023-01-24-14-21-06-569.png!\'"", ""Comment 13: \'VT-388/1/23id = e4748ffa-6475-42ed-8235-2616e87d6f90!image-2023-01-24-14-24-07-988.png!\'"", ""Comment 14: \'I am asking for a quick solution"", ""Comment 15: our loadings are at a standstill due to the non-generation of WO in the warehouse.\'"", ""Comment 16: \'Dar Nemanja,For VT-422/1/23 item20365-B10 is archaived. The same issue with VT-388"", ""Comment 17: item 20583-B10 is archaived. Maybe someone has archived them after processing VT? Is there such possibility?Regards\'"", ""Comment 18: \'Nevertheless"", ""Comment 19: those two items cause the issue.\'"", ""Comment 20: \'Ok"", ""Comment 21: i will check now with our product manager.\'"", ""Comment 22: \'Thank you. Waiting for your feedback then.Regards\'"", ""Comment 23: \'Hi,Any feedback?Regards\'"", ""Comment 24: \'Everything is ok for now. The product manager unarchived the codes that he archived by mistake. There is no problem with creating a WO for now.\'"", ""Comment 25: \'Great. So I am closing this task. If the issue reoccurs"", ""Comment 26: please raise another one.Regards\'"", ""Comment 27: \'Ok"", \'Comment 28: tnx\', ""Comment 29: you can close the ticket.\']""]\nRelated Issues:\n[\'DGS-8378\']\n\n### End'}"
648,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8383\n\n### Instruction:\nDuring the puchase monitor tests, we detected a difference between the contract volumes in DHC and DH CDN.\r\n\r\nThe problem was noticed in two contracts ZZ-572/12/22 and 574/12/22. Where does this difference come from?\r\n\r\nWhen i want synchronize contracts in DHC, it\'s occurs error.\r\n\n\n### Response:\n[""Comment 1: [\'!1!!2023-01-23_095833.jpg|thumbnail!!2023-01-23_100109.jpg|thumbnail!!2023-01-23_100139.jpg|thumbnail!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Sorry for the delay in response ZZ-572 - in progress - Quantity executed 24,82T"", \'Comment 4: unexecuted 0,18T.ZZ-574 - executed. This first order is still as in the request\', ""Comment 5: the second order is already updated(executed).What is the difference for the order ZZ-572?\'"", ""Comment 6: \'chodzi o ilości niezrealizowane/zrealizowane:Zrobiłem sync w DHC i się zmieniło na poprawne ilości np ZZ-54/02/23!image-2023-02-20-11-57-00-692.png!!image-2023-02-20-11-57-56-800.png!\'"", \'Comment 7: ""{code:java}  select * FROM [Evolution_DHCountry].[dbo].[OrderElements]  where OrderId in( select id  FROM [Evolution_DHCountry].[dbo].[Orders] where    documentnumber like \\\'zz-54/02/23\\\'   and status=3)  select *     FROM [Evolution_DHCountry].[dbo].[ContractElements]  where ContractId=\\\'D5EBAC15-3E21-470A-BB27-A9221AABFD00\\\'  select *    FROM [Evolution_DHCountry].[dbo].[Contracts]  where OrderId=\\\'7A144BD5-055F-4E50-AC66-5C2AF367C6E4\\\'    select *    FROM [Evolution_DHCountry].[dbo].[Orders] where   documentnumber like \\\'zz-54/02/23%\\\'   and status=3{code}""\', ""Comment 8: \'{code:java} select UnexecutedQuantity as ilosc1,QuantityInTransit as ilosc2,rez.rez_ilosc as rezerwacja"", \'Comment 9: [CDN].nazwaobiektu ( rez.rez_zrdtyp\', ""Comment 10: rez.rez_zrdnumer,1,2) as numer,*  FROM [sql03-20\\\\\\\\dhapp].[Evolution_DHCountry].[dbo].[ContractElements] dhccinner join [sql03-20].[DhcErpPlugin].[dbo].[ContractSyncs] erpc on dhcc.contractid=erpc.dhcid  inner join [sql03-20].[CDNXL_DEHEUS].[CDN].[Rezerwacje] rez on rez.Rez_ZrdNumer=erpc.xlid  and dhcc.ElementNo=rez.Rez_zrdlp where (dhcc.UnexecutedQuantity<>rez.rez_ilosc and dhcc.QuantityInTransit<>rez.rez_ilosc and (dhcc.UnexecutedQuantity+dhcc.QuantityInTransit<>rez.rez_ilosc)){code}\'"", ""Comment 11: \'po resent zeszło do 122 z prawie 700.\'"", ""Comment 12: \'{code:java}2023-02-20 20:00:00,003 [DefaultQuartzScheduler_Worker-3] DEBUG Quartz.Core.JobRunShell [(null)] - Calling Execute on job Contracts.ContractsSynchronization2023-02-20 20:00:00,003 [DefaultQuartzScheduler_Worker-3] DEBUG Evolution.DHCountry.Logging.DomainCommandHandlerWithLog4NetTracing [(null)] - Handled command [Evolution.DHCountry.Documents.Contracts.Commands.SynchronizeERPContractsCommand] by command handler [Evolution.DHCountry.Domain.DomainCommandHandlerWithPublishingEvents] under domain context [1749f5579d6144c28c2ed916e979d630]2023-02-20 20:00:00,191 [DefaultQuartzScheduler_Worker-3] DEBUG Quartz.Core.JobRunShell [(null)] - Trigger instruction : NoInstruction2023-02-20 20:00:01,214 [217] DEBUG Evolution.DHCountry.Logging.EventPublisherWithLog4NetTracing [(null)] - Published event [Evolution.DHCountry.Documents.Contracts.Events.ContractChangedEvent] to publisher [Evolution.Events.EventPublisher] under domain context [c39bb8b8f3f84c44b71a0df42cd11d7e]2023-02-20 20:00:01,292 [217] DEBUG Evolution.DHCountry.Logging.EventPublisherWithLog4NetTracing [(null)] - Published event [Evolution.DHCountry.Documents.Contracts.Events.ContractChangedEvent] to publisher [Evolution.Events.EventPublisher] under domain context [a84ee29a598f4a46bb549563c6df46d7]2023-02-20 20:00:01,402 [217] DEBUG Evolution.DHCountry.Logging.EventPublisherWithLog4NetTracing [(null)] - Published event [Evolution.DHCountry.Documents.Contracts.Events.ContractChangedEvent] to publisher [Evolution.Events.EventPublisher] under domain context [bd1cd41215f3423886f88b83c2d2a9e1]2023-02-20 20:00:01,481 [217] DEBUG Evolution.DHCountry.Logging.EventPublisherWithLog4NetTracing [(null)] - Published event [Evolution.DHCountry.Documents.Contracts.Events.ContractChangedEvent] to publisher [Evolution.Events.EventPublisher] under domain context [430c707837ac41639695d8c2bc699ffb]{code}!image-2023-02-21-13-43-30-571!\'"", ""Comment 13: \'{code:java}WHERE ZaN_GIDTyp = 960                    AND ZaN_ZamTyp = 1152                AND ZaN_DataWystawienia  BETWEEN @DateFrom AND @DateTo  AND EXISTS(                        SELECT ZaE_GIDNumer"", ""Comment 14: ZaE_GIDLp FROM CDN.ZamElem                             INNER JOIN CDN.Magazyny M WITH (NOLOCk) ON M.Mag_GidNumer = ZaE_MagNumer                            WHERE ZaE_GIDNumer = ZaN_GIDNumer AND ZaE_GidTyp=ZaN_GidTyp                            AND M.Mag_Kod IN @Warehouses){code}\'"", ""Comment 15: \'The mechanism works so that documents from the last seven days are synchronized at 20:00"", \'Comment 16: the date of issue is what counts(ZaN_DataWystawienia).As for the update\', \'Comment 17: should be perform manual synchronization\', \'Comment 18: but by selecting the appropriate factory and the appropriate date range.If there are still inaccuracies after manual synchronization\', \'Comment 19: please provide a specific examples(after successful manual synchronization).If a change in automatic synchronization is required\', ""Comment 20: it should be reported to GDC.\'"", ""Comment 21: \'I think you can close this task.\']""]\nRelated Issues:\n[]\n\n### End'}"
649,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8382\n\n### Instruction:\nFeed Sale document posted as Expenses.\r\nCustomer Mensing 006174\r\n\n\n### Response:\n[""Comment 1: [\'{color:black}Goodmorning,{color} {color:black}{color} {color:black}In customer Mensing 006174 we missed some feed sale documents. I made a manual posting in Feed Sale for these.{color}{color:black}{color} !image001!{color:black}{color}{color:black}{color} {color:black}Strange thing is that these lines are shown in expenses.{color}  {color:black}When opening these lines it switch back to Feed Sale.{color} {color:black}These should be on Feed sale"", ""Comment 2: cause all lines are related to feed.{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}!image002!{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} !image003!{color:blue}{color} <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | |{color:blue}{color} !image004!{color:blue}{color} <[https://twitter.com/de_heus_voeders]>{color:black}{color} | |{color:blue}{color} !image005!{color:blue}{color} <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | |{color:blue}{color} !image006!{color:blue}{color} <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} |   \'"", ""Comment 3: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 4: ""**Everything works as intended. On the subject card\', \'Comment 5: we see an indication of the expenses group. That\\\'s why this feed sale lane is in the expense group.!image-2023-01-23-11-54-24-165.png!""\', ""Comment 6: \'Can be closed\']""]\nRelated Issues:\n[]\n\n### End'}"
650,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8381\n\n### Instruction:\nHello, good day,\r\n\r\nWe will love to transfer opening balances from 2022 to 2023.\r\n1, Chart of accounts have been moved alread and team members are working in 2023.  will it affect the transfer?\r\n\r\n2. Can we select some accounts and leave some for later? \r\n\r\n3. How do we transfer the opening balances. \r\n\r\nMany thanks\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Hello # Thereis no problem that you wrking and posting in 2023 before opening balance has been transferred. You must always remember that all acounts from charts of account should be tranferred before you make transfer of charts of accounts. # You can transfer like that in three ways: * transfer all accounts to obening balance as accepted"", \'Comment 3: after changes in 2022 change opening balance status to Buffer and then discard opening balance and transfer it once again!image-2023-01-23-07-25-48-430.png! * second way is totransfer all accounts into opening balance as accepted\', ""Comment 4: after changes in 2022 transfer once again all accounts (without discarding old opening balance). That will make you will have opening balance (with all accounts) and opening balance (with ony accounts that was changed in 2022) * third option is to transfer opening balance for delected accounts and after changes transfer again for all accounts (that will make abalne account correction as in second case)!image-2023-01-23-07-31-23-952.png!    3. You need to go to period that opening balance should be transffered ( in our case 2023) and next: * Tools-> * transfer of opening balance-> * choose if you want transfer all accounts or selected ones * selected the document status (even if you choose accepted you can change to buffer after balance account will be imported) * If you choose selected account you need to add them using add button (if you choose all accounts you should skip this step) * import opening balance using button with yellow lightning!image-2023-01-23-07-36-56-879.png!\'"", ""Comment 5: \'Can we close this issue?\'"", ""Comment 6: \'OK please "", ""Comment 7: will raise another ticket if we encounter an issue.\'"", ""Comment 8: \'I am not able to select the General Ledger+ Bffers!image!\'"", ""Comment 9: \'You should be able to do it right now. Please verify.\'"", \'Comment 10: ""I still can\\\'t select it\', \'Comment 11: please.""\', ""Comment 12: \'Can we connect via team viewer ? could you give me access ?\'"", ""Comment 13: \'id should look like that now:!image-2023-01-27-11-19-24-241.png!\'"", ""Comment 14: \'it is not working please"", ""Comment 15: i am even using the admin user !image-1!\'"", ""Comment 16: \'Can we connect via team viewer ? could you give me access ?\'"", ""Comment 17: \'ID : 1 308 392 631PASS: yqiz1um5\'"", ""Comment 18: \'should be ok right now. Can I close this issue?\'"", ""Comment 19: \'Yes it is very ok\']""]\nRelated Issues:\n[]\n\n### End'}"
651,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8380\n\n### Instruction:\nWe have problem in stock for item SUR7462-P-MD-S25, 0871141222007, produced 8695kg and was used 8695kg, but we still have 1000kg in stock. We checked on stock fisically and we don\'t have item anymore and any stocktaking was done for the item. \r\n\r\nCould you check why we still have stock for this item if was loaded?\r\n\r\nThank you.\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \' !screenshot-1!  !screenshot-2! \'"", ""Comment 3: \' !screenshot-3!  !screenshot-4!  !screenshot-5! 0871141222007 - 9695 kgvt-2494/22 - 8675 kgvt-214/23 - 8650 kg0872311222001 - 20 kg0871200123015 - 8650 kg\'"", ""Comment 4: \' !screenshot-6! !image-2023-01-23-08-39-17-569!!image-2023-01-23-08-45-11-123!\'"", ""Comment 5: \'For this PLR should be 0871141222007 -1000kg  !screenshot-7! It can be corrected by stocktaking but for further analysis should be created RCA.Please confirm whether we treat it as an incident and after correction we close this ticket or the analysis under RCA should be created.\'"", ""Comment 6: \'Hello Piotr,the analysis under RCA should be created. Thank you.\'"", ""Comment 7: \'Hi Priscyla,RCA has been created DGS-8450.\'"", ""Comment 8: \'RCA has been created DGS-8450.This ticket has been closed.\']""]\nRelated Issues:\n[\'DGS-8450\']\n\n### End'}"
652,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8379\n\n### Instruction:\nunder samples the field ""tolerance source""  has selection ""latest product"" which no longer functions  as it should.\r\nif ""latest product"" is selected when  you open the A/O the values appear for a second then disappear this does not happen when the actual latest version number is selected.\n\n### Response:\n[""Comment 1: [\'[^both options exptd values issue.mp4] _(1,24 MB)_[^Exptd Values.mp4] _(381 kB)_\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'zmieniając tolerancję z wersji receptury na ostatni produkt"", ""Comment 4: przy otwarciu AO kasowane są expected values dla sładników AO.\'"", ""Comment 5: \'po stand up. Do testów.\'"", ""Comment 6: \'Hello,any feedback?\'"", ""Comment 7: \'hej [~aleksandra.przybylek@kotrak.com]"", \'Comment 8: [~piotr.gaczorek@kotrak.com]\', ""Comment 9: dopytajcie proszę klienta czy problem dalej występuje i czy mają świeże przykłady z wersji 8.5\'"", ""Comment 10: \'Dear Thabile,Could you please let us know if the issue still exists in version 8.5? If yes"", ""Comment 11: could you please provide us with fresh examples?Regards\'"", ""Comment 12: \'Hello"", \'Comment 13: it appears that all new samples now default to the latest technology \', \'Comment 14: which solves the problem however if you select ""latest product"" expected values are still blank (recorded an example on live attached)[^8.5.mp4] _(2,97 MB)_\\\'\', ""Comment 15: \'[~marek.mamcarz@kotrak.com]jednak coś mają"", ""Comment 16: to było poprawione w wersji 8.5?\']""]\nRelated Issues:\n[]\n\n### End'}"
653,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8378\n\n### Instruction:\nIt has been happening since this morning, but after restarting ISS, WOs appeared, but now I tried restarting IIS again, but WOs do not appear. \n\n### Response:\n[""Comment 1: [\'!image!!image-1!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 3: ""I restarted the application pool. Can you check if the problem will still occur now and cancel the problematic VT\\\'s  and re-issue?""\', ""Comment 4: \'For now"", \'Comment 5: everything works\', ""Comment 6: we will monitor the situation.\'"", ""Comment 7: \'Thank you for information"", ""Comment 8: if the problem returns please  send a specific VT number.\'"", ""Comment 9: \'Hello"", ""Comment 10: have there been any new cases?Or could you please confirm if we can close this task?Regards\'"", ""Comment 11: \'You can close the ticket.\'"", ""Comment 12: \'This task/ticket should be treated as an incident,the next time an error occurs an RCA will be created.Regards.\'"", ""Comment 13: \'Hi Piotr"", ""Comment 14: same problem again. VT 388 can you check please?\']""]\nRelated Issues:\n[\'DGS-8384\']\n\n### End'}"
654,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8377\n\n### Instruction:\nPlease migrate this missing file.\r\nMissing migration 101662 Spijker NAS\n\n### Response:\n[""Comment 1: [\'{color:black}Hello,{color} {color:black}{color} {color:black}Please migrate these missing files.{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} |   [^Sales migration_Spijker 101662.xlsx] _(18 kB)_[^Purchase_migration_Spijker 101662.xlsx] _(19 kB)_\'"", ""Comment 2: \'[~CJong@deheus.com],all lines have been migrated"", ""Comment 3: You can feel free to test it.Best regards,Grzegorz\'"", ""Comment 4: \'Sorry I forgot to reply. You can resolve this as done.\'"", \'Comment 5: ""No problem. Thank you for a reply. I\\\'m closing the task.Best regards,Grzegorz""]\']\nRelated Issues:\n[]\n\n### End'}"
655,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8376\n\n### Instruction:\nWe have again issues with address id\'s in orders. Both cases are for same customer (018896).\r\n\r\nSales order SO000055396 order and trip are sent to DHP and picked up by PCS but data is missing in VC. \r\nError can be found in DHP logging today 12:05 (see screenprints 1 and 2)\r\n\r\nWe resend customer / address and the sales order from Milas. This did not solve the issue. We need the orer and trip in DHP so that dispatch can be registered.\r\n\r\nSales order SO000055359 is in visible in DHP but trip is not visible. Order and trip information is sent to PCS. We need the trip in DHP for registration of dispatch and to load packed items. Only if we have a trip, the printout is made for packed and the warehouse order can be created.\r\nError message: see screenprint 3 and 4.\r\n\r\nWe resend the order and the trip, but this results in same error message.\r\n\r\nPlease support us in solving the issue for this customer.\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: ""select ForeignDocumentNumber\', \'Comment 4: MainBusinessPartnerId,MainBusinessPartnerAddressId,b.code --b.CurrentAddressId,a.BusinessPartnerId,* fromorders o join BusinessPartners b on b.id=o.MainBusinessPartnerId--join Addresses a on a.BusinessPartnerId=b.Idwhere o.ForeignDocumentNumber in ( \\\'SO000055396 \\\',\\\'SO000055359\\\')""\', ""Comment 5: \'!image-2023-01-20-12-59-48-553.png!\'"", ""Comment 6: \'ForSO000055396 the cause is the same as in DGS-8369.The order is for Main BP with code 818897but the address is linked to other BP with code018897.Please try to verify and fixed this data on order and resend it again to dhc.\'"", \'Comment 7: ""select UpdateDate,* from Addresses where id=\\\'39ACFF28-FC22-46F6-AC8B-C85C18DC7F8A\\\' or BusinessPartnerId=\\\'C9F0FDA3-A541-43F7-9A63-21831B7403B2\\\'select UpdateDate,* from BusinessPartners where id=\\\'EF48DAAB-5760-4F19-9E51-18894C7ED2C5\\\'or id =\\\'C9F0FDA3-A541-43F7-9A63-21831B7403B2\\\'""\', ""Comment 8: \'drugie zamowienie jest w dhp gdzie trzeba : !image-2023-01-20-13-53-21-129.png!\'"", \'Comment 9: \\\'przy wslce shipiing notice nadal errorAn 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 10: table ""dbo.OrderElements"".The statement has been terminated.\\\'\', ""Comment 11: \'Customer 818897 and 018897 have same customer name and same address details.How does DHP find the address Id for a customer? Can it be that DHP selects it based on e.g. the name and that it finds multiple results and selects the address linked to 018897 instead of the address linked to 818897? Or is this address id sent with the order from Milas?\'"", ""Comment 12: \'There is table bussinesspartners"", \'Comment 13: everyone has his id. We do not compare names\', ""Comment 14: cause will be to time consuming.And there is a table address where very address has his id and realtion to id of bussiness Partners.One address can not be linked to few diffrent BP!image-2023-01-20-14-18-35-213.png!\'"", \'Comment 15: ""select *from ShippingNotices where id=\\\'D3ACE234-7A5D-4256-B46A-4F4EAF98BED1\\\'select * from ShippingNoticeElements where id=\\\'D3ACE234-7A5D-4256-B46A-4F4EAF98BED1\\\'select* from ShippingNoticeElementOrderElements where id=\\\'D3ACE234-7A5D-4256-B46A-4F4EAF98BED1\\\'jest w pcs te dwa elementy na inen zamowienie psuja chyba cos!image-2023-01-20-14-23-09-740.png!""\', \'Comment 16: ""tego ordera brakuje w vt =select * from orders where id=\\\'CFD5F416-0ECD-4990-80C7-A65401259960\\\'""\', ""Comment 17: \'too drugie zamówienie z asn to własnie to : !image-2023-01-20-14-31-51-540.png!\'"", ""Comment 18: \'The second order is correctly synchro to dhp"", ""Comment 19: but Shipping Notice has elements from both of the orders -SO000055396 andSO000055359 so after fixing address and resending order it all shoud be in DHP.\'"", \'Comment 20: ""Id\\\'s / names: we checked Milas/Webmethods and indeed the combination of MainBP and address Id is not correct. The Invoice customer is sent as Main BP combined with the addressId of de the delivery customer... that is indeed not correct.We will check why the mapping was done this way. For the order: we updated Main BP id. It is now 018897. Order was updated in DHC. I am waiting to get the update in DHP. We also resent the trip (that indeed is for the two orders). As soon as the order arrives in DHP\', \'Comment 21: I think the trip will also be registered correctly in DHP.About the lookup on name: I was not sure if DHC received the address Id\', \'Comment 22: but now I see that this is the case. Indeed\', \'Comment 23: check on name is not a good idea and in this case no lookup is needed at all - because the Id is received.I will check if the update now arrives correctly.""\', ""Comment 24: \'Order and trip arrived in DHP and were sent to PCS. This ticket can be closed.\']""]\nRelated Issues:\n[]\n\n### End'}"
656,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8375\n\n### Instruction:\nUsers were unable to confirm PLR 0662150123005 due to  reservations not being assigned\r\n\r\nwe have tried to resend messages but it has not resolved 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: \'Resend messages have been needed - document creation and messages related with PLR processing. !screenshot-1! Looking at the logs in order:-ProductionOrder was missing"", \'Comment 3: -SalesOrder and the cause was target Business Partner address for the day of creation was missing.Currently\', ""Comment 4: it was enough to transfer the PLR \\\\u200b\\\\u200bitself.\'"", ""Comment 5: \'Hello"", ""Comment 6: thank you task can be closed\']""]\nRelated Issues:\n[]\n\n### End'}"
657,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8374\n\n### Instruction:\nI cannot make a reverse for  a sales invoices. Martijn Beek also not.\r\nIt is working earlier perfect\n\n### Response:\n[\'Comment 1: [""Could you provide number of Sales Invoice which isn\\\'t possible to reverse?There are some conditions when this action is possible to use\', \'Comment 2: so we\\\'ll verify it on example.""\', ""Comment 3: \'Related to this issue: to this issue: [DHNLC-1157] [GL]All sectors-Credit Invoice actions to be adjusted (availability) - JIRA Kotrak S.A. It is about SR/0083 in MAS NL.\'"", \'Comment 4: ""Action visibilty has been changed in all sectors.Now it\\\'s possible to use action \\\'Create correction invoice\\\' fo invoices which are not involved in Saldo to pay.Only invoices which are involved in Saldo to pay which is \\\'Archived\\\' are not possible to credit.Invoices involved in Saldo to pay in \\\'Entry\\\' status are possible to credit.It\\\'s done on IBIP_DH and IBIP_DH_TESTPlease verify and confirm that it works properly.""\', ""Comment 5: \'Can be closed.\']""]\nRelated Issues:\n[]\n\n### End'}"
658,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8373\n\n### Instruction:\nCould you reverse these SR\'s and all invoices (PI\'s and SI\'s) created from them.\r\nSR/2188\r\nSR/2189\r\nSR/2190\r\nSR/2191\r\nSR/2192\r\n\r\nThese are trade SR\'s and we cannot use this button.\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 2: ""Please verify now\', \'Comment 3: it should be possible.Action \\\'Create reverse SR\\\' now is also visible for Slaughtery reports: * when \\\'Full number\\\' is empty and \\\'Farmer code\\\' = 888888 * when it is Trade (full number is Trade) it is possible to reverse the SR""\', ""Comment 4: \'This can be closed.\']""]\nRelated Issues:\n[\'DGS-8349\']\n\n### End'}"
659,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8372\n\n### Instruction:\nProśba o podpięcie płatności WBR 2048/23 do FAI-65/01/23/WNT, komunikat:\r\n\r\n \r\n\r\nWykonywany skrypt SQL:\r\n\r\nDECLARE @KwotaRozliczenia DECIMAL(15,2);\r\n\r\nSET @KwotaRozliczenia=0;\r\n\r\nEXEC CDN.DodajRozliczenieUwzglWycene  @GIDFirma=246785,@GIDTyp1=3344,@GIDNumer1=44600,@GIDLp1=1,@GIDTyp2=784,@GIDNumer2=1822755,@GIDLp2=0,@Kwota=@KwotaRozliczenia OUTPUT,@UserID=543,@DataDzisiejsza=81105,@R2ParID=NULL;\r\n\r\nSELECT @KwotaRozliczenia;\r\n\r\n \n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 3: ""The reason are manual changes on this posting (account 204-01-092563). You should unpost this document and post it again without manual changes on 2* account generated by posting scheme. Then error shouldn\\\'t appear anymore!image-2023-01-20-08-12-50-303.png!""\', ""Comment 4: \'!image-1!\'"", \'Comment 5: \\\'according to conversation I added new posting scheme named ""FAI koszty przeł rok"" please verify if problem still occurs\\\']\']\nRelated Issues:\n[]\n\n### End'}"
660,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8371\n\n### Instruction:\nWe have a problem with duplication of raw materials in DHC.  Can you check what the problem is?\n\n### Response:\n[""Comment 1: [\'!dupliranje sirovina!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'This item has SSP code added on definition. It should be corrected. !screenshot-1!  !screenshot-2! \'"", ""Comment 4: \'This SSP item doesn`t work. i`m asking you for help. it is urgent.\'"", ""Comment 5: \'Hello"", ""Comment 6: please check with new version of the recipe.Item has been corrected but new v. is needed.\'"", ""Comment 7: \'now we can not see new version\'"", ""Comment 8: \'New version of the recipe should be sent from DHH and Bestmix.Has another version been created?\'"", ""Comment 9: \'new version is created"", ""Comment 10: but not visible in dhp.\'"", ""Comment 11: \'Hi"", \'Comment 12: now are in DHP  !screenshot-3! please check and confirm\', ""Comment 13: thanks.Regards.\'"", ""Comment 14: \'hi. now is ok.\'"", ""Comment 15: \'can you tell me how to slove this problem? if it reapears\'"", ""Comment 16: \'Hi,when it comes to unlinking the items from the SSP"", ""Comment 17: such an operation is only possible from the database.In DHC you can only do linking.\'"", ""Comment 18: \'All information was provided in the last comment.This ticket  has been closed.\']""]\nRelated Issues:\n[]\n\n### End'}"
661,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8370\n\n### Instruction:\nReports an error on IR+ AND IR-. For some reason there is nothing on those IR documents. They remain in green with the description `does not apply\'.\n\n### Response:\n[""Comment 1: [\'!Screenshot_10!!Screenshot_8!!Screenshot_9!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 3: ""\\\'does not apply\\\'  refers to a document without an element & looks like a problem with the erpintegrator session for XL.IR--  has been generated for this JO  correctly. !screenshot-1! These can be removed and we will restart the ERPintregrator services for verification in the following days.""\', \'Comment 4: ""Still can\\\'t confirm JO? Did you do anything on this?""\', ""Comment 5: \'Can I get a example?\'"", \'Comment 6: ""{color:black}{color} {color:black}{color}   *From:* Nemanja Antonic (Jira) <jira@kotrak.com>   *Sent:* Monday\', \'Comment 7: January 23\', ""Comment 8: 2023 1:00 PM  *To:* Vukota Barjaktarovic <vbarjaktarovic@deheus.com>  *Subject:* DGS-8370 Cannot close JO   |  *{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}* |      {color:#999999}—-—-—-—{color}    {color:#999999}Reply above this line.{color}     Nemanja Antonic added you as a participant.   [{color:#0052CC}View request{color}|https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhelpdesk.kotrak.com%2Fservicedesk%2Fcustomer%2Fportal%2F56%2FDGS-8370%3Fsda_source%3Dnotification-email&data=05%7C01%7Cvbarjaktarovic%40deheus.com%7C15b94491c28048f0efde08dafd39649d%7C1004261bdfb74f37830f7438cb8a1b69%7C1%7C0%7C638100720191884788%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=mfnuWMTjhBJBvvWS1qAngW6g8urOuie8X90cEksZ3A0%3D&reserved=0] · [{color:#0052CC}Turn off this request\'s notifications{color}|https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhelpdesk.kotrak.com%2Fservicedesk%2Fcustomer%2Fportal%2F56%2FDGS-8370%2Funsubscribe%3Fjwt%3DeyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJxc2giOiI3NzZjNmQ5ZWY4YzA0YzQ4MDQ3OWNlZDQ4YjMwNDQ5YWVjOGFlODZkNWU5ZDYyZDQyMGJiOGFlN2Y4YWNhZDMyIiwiaXNzIjoic2VydmljZWRlc2stand0LXRva2VuLWlzc3VlciIsImNvbnRleHQiOnsidXNlciI6IkpJUkFVU0VSMzI5MDUiLCJpc3N1ZSI6IkRHUy04MzcwIn0sImV4cCI6MTY3Njg5NDQwNSwiaWF0IjoxNjc0NDc1MjA1fQ.a2ezT0Jy5uJa3PIVLAjyfULm4FN1IVWBmBk1gxNGlU0&data=05%7C01%7Cvbarjaktarovic%40deheus.com%7C15b94491c28048f0efde08dafd39649d%7C1004261bdfb74f37830f7438cb8a1b69%7C1%7C0%7C638100720192041025%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=8Pfg3OxBgokc%2FgWenDOf0e0fDoqpyuxC3um0rTf2E7s%3D&reserved=0]  {color:#7A869A}This is shared with Nemanja Antonic"", \'Comment 9: Barbara Czarnocka\', \'Comment 10: Hardy Huy\', \'Comment 11: and 12 other people.{color}  {color:#7A869A}KOTRAK\', \'Comment 12: powered by{color} [{color:#7A869A}{color}{color:#0052CC} Jira Service Desk{color}{color:#7A869A}{color}|https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.atlassian.com%2Fsoftware%2Fjira%2Fservice-desk%2Fpowered-by%3Futm_medium%3Demail%26utm_source%3Dservice-desk_email-notification_server%26utm_campaign%3Dservice-desk_email-notification_server&data=05%7C01%7Cvbarjaktarovic%40deheus.com%7C15b94491c28048f0efde08dafd39649d%7C1004261bdfb74f37830f7438cb8a1b69%7C1%7C0%7C638100720192041025%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=MP%2Fg6yEuGmEHPJ4SzJjE5K8VzYSleMy59TmSrl9mrJU%3D&reserved=0]{color:#7A869A}\', \'Comment 13: sent you this message.{color}    !Screenshot_8-1!!Screenshot_9-1!""\', ""Comment 14: \'!Screenshot_8-2!!Screenshot_9-2!\'"", ""Comment 15: \'These are examples from the first half of january and they have already generated documents"", ""Comment 16: are there other current examples?\'"", ""Comment 17: \'In Cuprija still have problem to close JO. \'"", ""Comment 18: \'Hello"", ""Comment 19: I have one0382240123009 - I will check and let you now.\'"", ""Comment 20: \'We have missing resources:!image-2023-01-25-09-07-08-398.png!Reservation from DHP:!image-2023-01-25-09-07-25-479.png!Deliveries created in XL:!image-2023-01-25-09-08-05-221.png!IR- document created by operator VUKBAR not by ERPintegrator.Current stock for item:!image-2023-01-25-09-09-09-934.png!Stocks are missing.\'"", ""Comment 21: \'that is done. but what with others JO?\'"", ""Comment 22: \'Please give me current example - number. I will check.\'"", ""Comment 23: \'!Screenshot_11!\'"", ""Comment 24: \'{code:java}2023-01-19 22:51:03,578 [16] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.ProductionLotReports.ProductionLotReportProcessor [(null)] - ProductionLotReportProcessor execution started2023-01-19 22:51:03,609 [18] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.ProductionLotReports.GenerateJobOrder [(null)] - GenerateJobOrder execution started2023-01-19 22:51:03,609 [18] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.ProductionLotReports.GenerateJobOrder [(null)] - Started PLR Id: bdcd42ad-e64e-45a0-9c2c-6f1a30a990b6 processing2023-01-19 22:51:03,625 [18] INFO  Evolution.ErpIntegrator.IntegrationLibrary.Documents.ProductionLotReports.GenerateJobOrder [(null)] - Generating documents for PLR Id: bdcd42ad-e64e-45a0-9c2c-6f1a30a990b62023-01-19 22:51:03,672 [18] INFO  Evolution.ErpIntegrator.IntegrationLibrary.Documents.ProductionLotReports.GenerateJobOrder [(null)] - Generating Job Order for PLR Id: bdcd42ad-e64e-45a0-9c2c-6f1a30a990b62023-01-19 22:51:03,672 [18] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.ProductionLotReports.GenerateJobOrder [(null)] - Generate JO by PLR data.2023-01-19 22:51:03,734 [Thread 18] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2014.Documents.JobOrders.CdnXL2014JORepository [(null)] - JO Created: ID - 118778 [JO-139/01/23/CU]2023-01-19 22:51:03,922 [18] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2014.Documents.JobOrders.CdnXL2014JORepository [(null)] - JO Element Created: ID - 118628 for new process 1186632023-01-19 22:51:04,000 [18] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2014.Documents.JobOrders.CdnXL2014JORepository [(null)] - Job order elemnt ID - 118628 process for item 04304 added2023-01-19 22:51:04,078 [18] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2014.Documents.JobOrders.CdnXL2014JORepository [(null)] - Job order elemnt ID - 118628 ingredient 04301 added2023-01-19 22:51:04,312 [18] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2014.Documents.JobOrders.CdnXL2014JORepository [(null)] - Job order elemnt ID - 118628 product 04304 added2023-01-19 22:51:04,937 [Thread 18] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2014.Documents.JobOrders.CdnXL2014JORepository [(null)] - JO Closed: ID - 118778 (2816)2023-01-19 22:51:05,015 [18] INFO  Evolution.ErpIntegrator.IntegrationLibrary.Documents.ProductionLotReports.GenerateJobOrder [(null)] - Generated JO ID - 118778 For PLR Id: bdcd42ad-e64e-45a0-9c2c-6f1a30a990b6 - BY PLR2023-01-19 22:51:05,219 [18] INFO  Evolution.ErpIntegrator.IntegrationLibrary.Documents.ProductionLotReports.GenerateJobOrder [(null)] - Generating Release for PLR Id: bdcd42ad-e64e-45a0-9c2c-6f1a30a990b62023-01-19 22:51:05,219 [18] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.ProductionLotReports.GenerateJobOrder [(null)] - Adding Element 04301 with quantity 20000.0000 on CU2023-01-19 22:51:05,312 [18] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2014.Documents.InternalDocuments.CdnXL2014InternalDocumentRepository [(null)] - InternalRelease created: Firma:1015297 - TYP:1616/NUMER:1635788/LP:0 IR--166/01/23/CU2023-01-19 22:51:05,437 [18] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2014.Documents.InternalDocuments.CdnXL2014InternalDocumentRepository [(null)] - InternalRelease Element Created: Firma:1015297 - TYP:1616/NUMER:1635788/LP:12023-01-19 22:51:05,531 [12] DEBUG Evolution.ErpIntegrator.Services.ERP.CdnXL.SoapERPService [(null)] - Recived Trade Document Create or Update message from trigger - 16357882023-01-19 22:51:05,562 [12] DEBUG Evolution.ErpIntegrator.Services.ERP.CdnXL.SoapERPService [(null)] - Recived Trade Document Create or Update message from trigger - 16357882023-01-19 22:51:05,578 [18] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2014.Documents.InternalDocuments.CdnXL2014InternalDocumentRepository [(null)] - InternalRelease Document Confirmed: Firma:1015297 - TYP:1616/NUMER:1635788/LP:02023-01-19 22:51:05,640 [18] INFO  Evolution.ErpIntegrator.IntegrationLibrary.Documents.ProductionLotReports.GenerateJobOrder [(null)] - Generated IR- Firma:1015297 - TYP:1616/NUMER:1635788/LP:0 For PLR Id: bdcd42ad-e64e-45a0-9c2c-6f1a30a990b62023-01-19 22:51:05,719 [18] INFO  Evolution.ErpIntegrator.IntegrationLibrary.Documents.ProductionLotReports.GenerateJobOrder [(null)] - Generating Receipt for PLR Id: bdcd42ad-e64e-45a0-9c2c-6f1a30a990b62023-01-19 22:51:05,782 [18] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2014.Documents.InternalDocuments.CdnXL2014InternalDocumentRepository [(null)] - InternalReceipt created: Firma:1015297 - TYP:1617/NUMER:1635789/LP:0 IR+-149/01/23/CU2023-01-19 22:51:05,891 [18] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2014.Documents.InternalDocuments.CdnXL2014InternalDocumentRepository [(null)] - InternalReceipt Element Created: Firma:1015297 - TYP:1617/NUMER:1635789/LP:12023-01-19 22:51:05,985 [12] DEBUG Evolution.ErpIntegrator.Services.ERP.CdnXL.SoapERPService [(null)] - Recived Trade Document Create or Update message from trigger - 16357892023-01-19 22:51:06,016 [12] DEBUG Evolution.ErpIntegrator.Services.ERP.CdnXL.SoapERPService [(null)] - Recived Trade Document Create or Update message from trigger - 16357892023-01-19 22:51:06,031 [18] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2014.Documents.InternalDocuments.CdnXL2014InternalDocumentRepository [(null)] - InternalReceipt Document Confirmed: Firma:1015297 - TYP:1617/NUMER:1635789/LP:02023-01-19 22:51:06,063 [18] INFO  Evolution.ErpIntegrator.IntegrationLibrary.Documents.ProductionLotReports.GenerateJobOrder [(null)] - Generated IR+ Firma:1015297 - TYP:1617/NUMER:1635789/LP:0 For PLR Id: bdcd42ad-e64e-45a0-9c2c-6f1a30a990b62023-01-19 22:51:06,157 [18] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.ProductionLotReports.GenerateJobOrder [(null)] - PLR processing finished2023-01-19 22:51:06,157 [18] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.ProductionLotReports.GenerateJobOrder [(null)] - GenerateJobOrder execution finished2023-01-19 22:51:06,157 [16] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.ProductionLotReports.ProductionLotReportProcessor [(null)] - ProductionLotReportProcessor execution finished{code}\'"", ""Comment 25: \' !screenshot-2! \'"", \'Comment 26: \\\'When closing the job orders problematic one\\\\\\\'s were 106 and 115 - there was a problem with the lack of a fixed cost due to the fact that the documents referred to each other. A manual change had to be made for the delivery - IR+. !screenshot-3! You can check problematic IR+ with graph - ""documents with unfixed costs"" . You should close the related JO before closing the problematic one. !screenshot-4! If there is a problem with this please choose Fixed delivery value on IR+(which is the delivery).Currently\', ""Comment 27: job orders are closed.Can you check if there are any other problems.\'"", ""Comment 28: \'Could you please confirm if we can close this task?Regards\'"", ""Comment 29: \'Hello,We are closing this task as we haven’treceivedany replyfromyouforalong time. If the issueappearsagain"", ""Comment 30: please raise another task.Regards\']""]\nRelated Issues:\n[]\n\n### End'}"
662,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8369\n\n### Instruction:\nHello, \r\n\r\n this is reported many times, but problem still occurs: In maasbracht I have 2 orders not synced to VC module:\r\nSO000050086\r\nSO000050108\r\n\r\nPlease  can you check again the case and mayby perform root cause analysis to get rid of this issue? \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\\\\rAgnieszka Januszewska\'"", ""Comment 2: \'Same applies SO000047783"", ""Comment 3: SO000052890\'"", ""Comment 4: \'ciepie sie o adres ponowna wysylka adresu i zamówienia nie pomogłaselect MainBusinessPartnerId,MainBusinessPartnerAddressId,* from orders where ForeignDocumentNumber in ( \\\\\'SO000050086\\\\\',\\\\\'SO000050108\\\\\'"", ""Comment 5: \\\\\'SO000047783\\\\\'"", \'Comment 6: \\\\\\\'SO000052890\\\\\\\')select * from OrderExportInfoes where EntityId=\\\\\\\'1D94C9A0-0F06-45E0-B143-AE315ADB0D40\\\\\\\'select UpdateDate,* from Addresses where id=\\\\\\\'D8294CF0-D490-4E50-9AC2-1972730AAEA8\\\\\\\'select* from AddressExportInfoes where EntityId=\\\\\\\'D8294CF0-D490-4E50-9AC2-1972730AAEA8\\\\\\\' and ClientId=\\\\\\\'F1300CAE-63B3-4F46-AD2E-1023E3748092\\\\\\\'select UpdateDate,* from BusinessPartners where id=\\\\\\\'BB3FECBE-0583-4256-A7E5-982A1521B8AB\\\\\\\'select * from BusinessPartnerExportInfoes where entityid=\\\\\\\'BB3FECBE-0583-4256-A7E5-982A1521B8AB\\\\\\\' and ClientId=\\\\\\\'F1300CAE-63B3-4F46-AD2E-1023E3748092\\\\\\\'An error occurred while saving the entity changes. See the inner exception for details. -> The INSERT statement conflicted with the FOREIGN KEY constraint ""FK_Orders_ContactDatas_MainBusinessPartnerId_MainBusinessPartnerContactDataId"". The conflict occurred in database ""DHPlantVCBusinessLogicMain""\', \'Comment 7: table ""dbo.ContactDatas"".The statement has been terminated.\\\'\', \'Comment 8: ""adrs domyslny jest inny =select UpdateDate,* from Addresses where id=\\\'D8294CF0-D490-4E50-9AC2-1972730AAEA8\\\' or id=\\\'0C00D6AE-8BA4-4C7A-8416-4DD0DDCCED20\\\'""\', ""Comment 9: \'For ordersSO000052890,SO000050108,SO000047783 is set BusinessPartner with code100064But has set addres that is not linked with the BP100064 but with BP code 000168.!image-2023-01-20-08-16-31-395.png!So please try to send this orders with consistent data this is the current address fo that customer:!image-2023-01-20-08-19-09-035.png! If address is for data from the other BP :!image-2023-01-20-08-21-12-701.png!You may add similar address for BP or use as mainpartner BP000168.\'"", ""Comment 10: \'For orderSO000050086 the bussiness partner is009907 but the address is the current address from diffrent BP with code00097K\'"", ""Comment 11: \'mają na orderach adresy przypsane do innych BP - ciekawe co odpiszą,\'"", ""Comment 12: \'Ticket can be closed\']""]\nRelated Issues:\n[]\n\n### End'}"
663,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8368\n\n### Instruction:\nChanhe Main and Target adress from 7727 to 0674.\r\n\r\n(Payer has already been changed)\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!!image-1!!image-2!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.RegardsAgnieszka Januszewska\'"", ""Comment 3: \'Dear Bert,Main"", ""Comment 4: and Target have been changed!image-2023-01-19-13-23-10-842.png|width=1052,height=195!!image-2023-01-19-13-23-37-125.png|width=1201,height=242!Regards\'"", ""Comment 5: \'[^DGS-8368.xlsx]\'"", \'Comment 6: ""{code:java}select TrN_KnPNumer\', \'Comment 7: TrN_AdPNumer\', \'Comment 8: TrN_KnDNumer\', \'Comment 9: TrN_AdWNumer\', \'Comment 10: TrN_KntNumer\', \'Comment 11: TrN_KnANumer\', \'Comment 12: * from cdn.tranag where TrN_GIDTyp=2037 AND TrN_GIDFirma=1015303 AND TrN_GIDNumer=3375490select knt_gidnumer\', \'Comment 13: KnA_GIDTyp\', ""Comment 14: a.KnA_GIDNumerfrom cdn.KntKartyjoin cdn.KntAdresy a on KnA_KntNumer=Knt_GIDNumerwhere Knt_Akronim like \'%0674%\' and KnA_DataArc=0 and KnA_GIDTyp=864--UPDATE cdn.tranag set TrN_KnDNumer = 1060"", \'Comment 15: TrN_AdWNumer = 3130\', \'Comment 16: TrN_KntNumer = 1060\', \'Comment 17: TrN_KnANumer = 3130 --where TrN_GIDTyp=2037 AND TrN_GIDFirma=1015303 AND TrN_GIDNumer=3375490{code}""\', ""Comment 18: \'I asked user if it is oke.\'"", ""Comment 19: \'Waiting for your feedback then.Regards\'"", ""Comment 20: \'Again I asked user if it is oke.So far no answer\'"", ""Comment 21: \'ok\'"", ""Comment 22: \'Should be correct,.Ticket can be closed!image-3!\']""]\nRelated Issues:\n[]\n\n### End'}"
664,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8367\n\n### Instruction:\nHi\r\n\r\nWe are trying to move the UL barcode 87-W007OI to the EMBALAGEM location. However, system displays an error message.\r\n\r\nAlso, when I try to filter EMBALAGEM  location in WMS Unitloads screen, an Internal error occurres.\r\n\r\nCould you please help us with this issue?\r\n\r\nThank you very much\n\n### Response:\n[""Comment 1: [\'!image!!image-1!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.RegardsAgnieszka Januszewska\'"", ""Comment 3: \'HelloDo we have any news about this?Thnk you\'"", ""Comment 4: \'We are analyzing the problem.\'"", \'Comment 5: \\\'{code:java}2023-01-20 13:56:47 (cbddcadc-d97e-4649-b7eb-31e497a23c64/Plant.WMS.BusinessLogic/BR-4-SV-VM0204/11584/217) [Error] Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware - Error during request{  ""scheme"": ""http""\', \'Comment 6:  ""host"": {    ""Value"": ""br-4-sv-vm0204:85""\', \'Comment 7:    ""HasValue"": true\', \'Comment 8:    ""Host"": ""br-4-sv-vm0204""\', \'Comment 9:    ""Port"": 85  }\', \'Comment 10:  ""path"": ""/api/WarehouseMovement/registerMultipleMovements""\', \'Comment 11:  ""queryString"": []\', \'Comment 12:  ""requestBody"": ""{\\\\\\\\""movementData\\\\\\\\"":[{\\\\\\\\""unitLoadId\\\\\\\\"":\\\\\\\\""fb595f60-c10d-49db-8502-1057a7d0710d\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""pcs\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":5318},\\\\\\\\""destinationLocationId\\\\\\\\"":\\\\\\\\""6636b77f-3e39-43ce-9ebe-e168ca0c0180\\\\\\\\""}]}""}.System.ArgumentException: Unit mismatch   at Kotrak.Common.SharedKernel.Extensions.QuantityExtensions.<>c__9`1.<Sum>b__9_0(Quantity x\', \'Comment 13: Quantity y)   at System.Linq.Enumerable.Aggregate[TSource,TAccumulate](IEnumerable`1 source\', \'Comment 14: TAccumulate seed\', \'Comment 15: Func`3 func)   at Kotrak.Common.SharedKernel.Extensions.QuantityExtensions.Sum[T](IEnumerable`1 source\', \'Comment 16: Func`2 selector)   at Plant.WMS.BusinessLogic.Domain.WarehouseMovements.ExplicitMapping.ToFastMovementValidationData(FastMovementDomainDataStructure dataStructure) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Domain\\\\\\\\WarehouseMovements\\\\\\\\ExplicitMapping.cs:line 25   at Plant.WMS.BusinessLogic.Domain.WarehouseMovements.Services.FastMovementDomainService.GenerateFastMovement(FastMovementDomainDataStructure dataStructure) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Domain\\\\\\\\WarehouseMovements\\\\\\\\Services\\\\\\\\FastMovementDomainService.cs:line 58   at Plant.WMS.BusinessLogic.Application.WarehouseMovements.FastWarehouseMovementService.RegisterMultipleFastMovements(MultipleFastMovementDataStructure dataStructure) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Application\\\\\\\\WarehouseMovements\\\\\\\\FastWarehouseMovementService.cs:line 74   at Plant.WMS.BusinessLogic.Application.Workflows.WorkflowRunner.Run(Workflow workflow) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Application\\\\\\\\Workflows\\\\\\\\WorkflowRunner.cs:line 17   at Plant.WMS.BusinessLogic.Application.WarehouseMovements.Handlers.RegisterMultipleFastMovementsCommandHandler.Handle(RegisterMultipleFastMovementsCommand command) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Application\\\\\\\\WarehouseMovements\\\\\\\\Handlers\\\\\\\\RegisterMultipleFastMovementsCommandHandler.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.WMS.BusinessLogic.Infrastructure.Api.Controllers.WarehouseMovementController.RegisterMultipleMovements(RegisterMultipleMovementsViewModel viewModel) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Infrastructure.Api\\\\\\\\Controllers\\\\\\\\WarehouseMovementController.cs:line 114   at lambda_method47002(Closure \', \'Comment 17: Object \', \'Comment 18: Object[] )   at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor.SyncActionResultExecutor.Execute(IActionResultTypeMapper mapper\', \'Comment 19: ObjectMethodExecutor executor\', \'Comment 20: Object controller\', \'Comment 21: Object[] arguments)   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeActionMethodAsync()   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next\', \'Comment 22: Scope& scope\', \'Comment 23: Object& state\', \'Comment 24: 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 25: Scope& scope\', \'Comment 26: Object& state\', \'Comment 27: 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 28: Task lastTask\', \'Comment 29: State next\', \'Comment 30: Scope scope\', \'Comment 31: Object state\', \'Comment 32: Boolean isCompleted)   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker\', \'Comment 33: Task task\', \'Comment 34: IDisposable scope)   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker\', \'Comment 35: Task task\', \'Comment 36: IDisposable scope)   at Microsoft.AspNetCore.Routing.EndpointMiddleware.<Invoke>g__AwaitRequestTask|6_0(Endpoint endpoint\', \'Comment 37: Task requestTask\', \'Comment 38: ILogger logger)   at Swashbuckle.AspNetCore.SwaggerUI.SwaggerUIMiddleware.Invoke(HttpContext httpContext)   at Swashbuckle.AspNetCore.Swagger.SwaggerMiddleware.Invoke(HttpContext httpContext\', ""Comment 39: ISwaggerProvider swaggerProvider)   at Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware.Invoke(HttpContext httpContext){code}\'"", \'Comment 40: ""Done\', ""Comment 41: one barcode \'87-OB00G4\' has bag size unit= pcs"", \'Comment 42: should be kg for destination location. !screenshot-1! ""\', ""Comment 43: \'Hi PiotrThank you very muchYou can close this task\'"", ""Comment 44: \'Hi MaiconYou are welcome.Regards.\']""]\nRelated Issues:\n[]\n\n### End'}"
665,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8366\n\n### Instruction:\nProduction from the 16th, 17th and 18th are not generation JO documents in ERP. Kindly assist. seems like synchronization is failing. thank you\n\n### Response:\n[""Comment 1: [\'please cancelsolved internally\'"", ""Comment 2: \'Thanks for the information.\']""]\nRelated Issues:\n[]\n\n### End'}"
666,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8365\n\n### Instruction:\nGood afternoon,\r\n\r\nPlease, would you create an openings balance for item code: 088127 on plant: Nijkerk. Quantity 5 pcs.\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: \'Opening balance for item has been created.\'"", ""Comment 3: \'Goodmorning Piotr,Thanks for support on this.Please"", ""Comment 4: close this ticket.Regards,Gerard\']""]\nRelated Issues:\n[]\n\n### End'}"
667,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8364\n\n### Instruction:\nRecipe for 506960 is in DHH and DHC, but does not appear in DHP Sneek.\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'I see the recipe has arrived.Ticket can be closed"", ""Comment 3: thanks.\']""]\nRelated Issues:\n[]\n\n### End'}"
668,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8363\n\n### Instruction:\nTwo sales orders are not arriving in DHP Sneek. Can you please check why? The orders are in DHC. \n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 2: ""!image-2023-01-18-14-07-53-248.png!{code:java}SELECT DocumentNumber\', ""Comment 3: * FROM [DHCountry_NL_AS400_PROD].[dbo].[Orders] where DocumentNumber = \'SO000054520\'SELECT * FROM [DHCountry_NL_AS400_PROD].[dbo].[OrderElements] where OrderId = \'7F273905-B08B-4677-A87E-32D466639425\'SELECT DocumentNumber"", \'Comment 4: * FROM [DHCountry_NL_AS400_PROD].[dbo].[Orders] where DocumentNumber = \\\'SO000054522\\\'SELECT * FROM [DHCountry_NL_AS400_PROD].[dbo].[OrderElements] where OrderId = \\\'D02C7757-324B-43C1-8F0E-257D914541A5\\\'{code}""\', ""Comment 5: \'Brak orderów w DHC Service:!image-2023-01-18-14-09-07-053.png!\'"", ""Comment 6: \'{code:java}2023-01-18 09:59:23,723 [31] INFO  Evolution.DHCService.Dhc30.Handlers.OrderChangedMessageHandler [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\156434433\\\\\\\\DHAPPSV3-DHCSER534-JOB1\\\\\\\\Evolution.DHCService\\\\\\\\Evolution.DHCService.Dhc30\\\\\\\\Handlers\\\\\\\\BaseMessageHandler.cs:37] - Receiving message (Evolution.DHCountry.Interfaces.Orders.Messages.OrderChangedMessage) [Id:7f273905-b08b-4677-a87e-32d466639425]2023-01-18 09:59:23,738 [31] INFO  Evolution.DHCService.Dhc30.Handlers.OrderChangedMessageHandler [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\156434433\\\\\\\\DHAPPSV3-DHCSER534-JOB1\\\\\\\\Evolution.DHCService\\\\\\\\Evolution.DHCService.Dhc30\\\\\\\\Handlers\\\\\\\\BaseMessageHandler.cs:49] - Message received successfuly!{code}\'"", ""Comment 7: \'{code:java}2023-01-18 09:59:57,385 [85] INFO  Evolution.DHCService.Dhc30.Handlers.OrderChangedMessageHandler [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\156434433\\\\\\\\DHAPPSV3-DHCSER534-JOB1\\\\\\\\Evolution.DHCService\\\\\\\\Evolution.DHCService.Dhc30\\\\\\\\Handlers\\\\\\\\BaseMessageHandler.cs:37] - Receiving message (Evolution.DHCountry.Interfaces.Orders.Messages.OrderChangedMessage) [Id:d02c7757-324b-43c1-8f0e-257d914541a5]2023-01-18 09:59:57,401 [85] INFO  Evolution.DHCService.Dhc30.Handlers.OrderChangedMessageHandler [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\156434433\\\\\\\\DHAPPSV3-DHCSER534-JOB1\\\\\\\\Evolution.DHCService\\\\\\\\Evolution.DHCService.Dhc30\\\\\\\\Handlers\\\\\\\\BaseMessageHandler.cs:49] - Message received successfuly!{code}\'"", ""Comment 8: \'W DHC Service item nie wpadł też!image-2023-01-18-14-15-35-451.png!\'"", ""Comment 9: \'!image-2023-01-18-14-17-48-701.png!\'"", ""Comment 10: \'Dear Theo,Please resent Orders from Milas. Then it should be fine.Regards\'"", \'Comment 11: ""Hi Aleksandra\', ""Comment 12: I have exported them again. Don\'t see them in DHP (yet)"", \'Comment 13: but perhaps i\\\'m a bit impatient :) What did you do in order to get them through?""\', ""Comment 14: \'Yes I see them in DHP\'"", \'Comment 15: ""Well\', \'Comment 16: the Item from the Orders was not in DHC Service and this caused the issue. I had to resend DHH item\', \'Comment 17: then resynced recipe\', \'Comment 18: production recipe and technology. It may take a while untl Orders will be reprocessed :). Let\\\'s wait a bit.Regards""\', \'Comment 19: ""Oh\', \'Comment 20: that\\\'s great. In that case can we close this task? :)""\', ""Comment 21: \'Yes please"", ""Comment 22: close the task. Thank you very much for your help\'"", ""Comment 23: \'No problem. Thank you\'"", ""Comment 24: \'zrobiłam resync brakujących towarów:--110122 recipe not accepted--140135"", \'Comment 25: wysłałam wszystko w dhc (recipe\', ""Comment 26: prod recipe i tehno)--306891 recipe not accepted\']""]\nRelated Issues:\n[]\n\n### End'}"
669,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8362\n\n### Instruction:\nDea, \r\nwe don´t see label for 2287 in DHP Bestovice. Pls solve it asap. We need it today afternoon.\r\n\r\nit´s in DHH - info from Holland.\r\nthx, Lucy\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: \'The item was not linked. I have linked item. Please"", ""Comment 3: verify if this is fine for you.Regards\'"", ""Comment 4: \'Hi"", ""Comment 5: it is okay now. thxHow is it possible taht it wasn´t linked? It was linked because if not I wouldn´t see recipe.Did I do sth wrong?Lucy\'"", ""Comment 6: \'This is well known issue for DHC version lower than 55. The best way to avoid this situation is to upgrade DHC to the highest version.Please"", ""Comment 7: let us know if we can close this task.Regards\'"", ""Comment 8: \'Yes"", ""Comment 9: you can close it.\']""]\nRelated Issues:\n[]\n\n### End'}"
670,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8361\n\n### Instruction:\nWhen partial items are loaded, i.e. partial quantities of items, then loading other items and reloading the first item, the system miscalculates quantities, increases 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: \'!image-2023-01-19-11-11-01-049.png!\'"", ""Comment 4: \'Hi,Is the issue repetitive - did it occure for oter VTs? What about other plants"", ""Comment 5: does the issue occur for all or only for Spytkowice?Regards\'"", ""Comment 6: \'!image-2023-01-19-11-50-44-790.png!W logach na godzinę initial i na end!image-2023-01-19-11-52-30-336.png!{code:java}System.NullReferenceException: Object reference not set to an instance of an object.   at BinaryData.Browser.barButtonItemSaveAs_ItemClick(Object sender"", \'Comment 7: ItemClickEventArgs e) in E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\31916033\\\\\\\\DHP-DHPD957-JOB1\\\\\\\\BinaryData\\\\\\\\Browser.cs:line 107   at DevExpress.XtraBars.BarItem.OnClick(BarItemLink link)   at DevExpress.XtraBars.BarButtonItem.OnClick(BarItemLink link)   at DevExpress.XtraBars.BarItemLink.OnLinkClick()   at DevExpress.XtraBars.BarButtonItemLink.OnLinkClick()   at DevExpress.XtraBars.BarItemLink.OnLinkAction(BarLinkAction action\', \'Comment 8: Object actionArgs)   at DevExpress.XtraBars.BarButtonItemLink.OnLinkAction(BarLinkAction action\', \'Comment 9: Object actionArgs)   at DevExpress.XtraBars.ViewInfo.BarSelectionInfo.ClickLink(BarItemLink link)   at DevExpress.XtraBars.ViewInfo.BarSelectionInfo.UnPressLink(BarItemLink link)   at DevExpress.XtraBars.Ribbon.Handler.BaseRibbonHandler.OnUnPressItem(DXMouseEventArgs e\', \'Comment 10: RibbonHitInfo hitInfo)   at DevExpress.XtraBars.Ribbon.Handler.BaseRibbonHandler.OnUnPress(DXMouseEventArgs e\', \'Comment 11: RibbonHitInfo hitInfo)   at DevExpress.XtraBars.Ribbon.Handler.RibbonHandler.OnUnPress(DXMouseEventArgs e\', \'Comment 12: RibbonHitInfo hitInfo)   at DevExpress.XtraBars.Ribbon.Handler.BaseRibbonHandler.OnMouseUp(DXMouseEventArgs e)   at DevExpress.XtraBars.Ribbon.Handler.RibbonHandler.OnMouseUp(DXMouseEventArgs e)   at DevExpress.XtraBars.Ribbon.RibbonControl.OnMouseUp(MouseEventArgs e)   at System.Windows.Forms.Control.WmMouseUp(Message& m\', \'Comment 13: MouseButtons button\', \'Comment 14: Int32 clicks)   at System.Windows.Forms.Control.WndProc(Message& m)   at DevExpress.Utils.Controls.ControlBase.WndProc(Message& m)   at DevExpress.XtraBars.Ribbon.RibbonControl.WndProc(Message& m)   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd\', \'Comment 15: Int32 msg\', \'Comment 16: IntPtr wparam\', ""Comment 17: IntPtr lparam){code}\'"", ""Comment 18: \'yes"", \'Comment 19: this problem is repetitive\', \'Comment 20: in each such cases\', ""Comment 21: please check at this moment Spytkowice\'"", ""Comment 22: \'Co udało mi się ustalić:>> info od Marcina:Logika systemu działa chyba tak"", \'Comment 23: że jak załadują pierwszy element na 3t potem kolejny towar na drugi element 3 Tpo czym wrócą do 1 elementu i doładują 3t żeby niby było 6t na 1 a 3t na 2. To na koniec mają po 6t na każdym lub na 1 jest 3t a na drugim jest 6tLogikę pisał Tomek Nojek\', \'Comment 24: a uzgadniał Paweł Ogieła>> info od Tomka:Tomkowi też się tak wydaje\', \'Comment 25: że system nie jest przygotowany na wielokrotny zasyp do tej samej komory i mogą się pojawić błędy w takim przypadku i\', ""Comment 26: żebyłaby potrzebna analiza kodu do rejestracji tych zasypów\'"", ""Comment 27: \'Hello,We have analised your case. The system does not support partial loading. If there is a need from your side"", ""Comment 28: please raise a GDC task.Regards\'"", ""Comment 29: \'Hello,We have analised your case. The system does not support partial loading. If there is a need from your side"", ""Comment 30: please raise a GDC task.Regards\'"", ""Comment 31: \'please close this task"", ""Comment 32: we will do it in DHP 3.0\'"", ""Comment 33: \'Sure. With pleasure.Regards\']""]\nRelated Issues:\n[]\n\n### End'}"
671,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8360\n\n### Instruction:\nHi,\r\nVT number 000647, date issue 17 Jan 2023 cannot sync to DHC \n\n### Response:\n[\'Comment 1: [""odkryłam log w bazie dhc country :2023-01-17 21:39:48,816 [6] ERROR Evolution.DHCountry.Documents.VehicleTickets.Handlers.VehicleTicketChangedHandler [(null)] - System.Data.Entity.Core.EntityException: The underlying provider failed on Open. ---> System.Data.SqlClient.SqlException: MSDTC on server \\\'IDSQL02-TEST\\\' is unavailable.""\', ""Comment 2: \'!image-2023-01-18-12-00-50-597.png!\'"", \'Comment 3: ""Hello I checked one again dhc country logs and I found log from 9.38 pm logs thatMSDTC on server \\\'IDSQL02-TEST\\\' is unavailable.could you ask your It if there were any problems or maintenance during this time?""\', ""Comment 4: \'Hi,I already ask to our IT Infrastructure team"", \'Comment 5: the DB server was restarted at that time,and my question is\', \'Comment 6: if the server is on\', ""Comment 7: is the data not automated sync again?\'"", ""Comment 8: \'It looks like the VT was synchronized from the PLant DB to DHC Service DB"", ""Comment 9: and the do not go from to DB DHCCountry.If there be no commitedate of synchronization betweenPLant DB to DHC Service DB it wil be resend but in that that case there was need to resend it again.If that restart wasscheduled it is better to do that when there are no working on DHP Plant/DHCountry users.May we close the task?\'"", ""Comment 10: \'ok thank you\']""]\nRelated Issues:\n[\'DGS-8355\']\n\n### End'}"
672,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8359\n\n### Instruction:\nHi\r\n\r\nCan\'t generate docs to cdn.\r\n\r\nRafał Boniecki\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'the seventh VT element is different from the seventh order element !screenshot-1!DD5A1S00K-F00 ZS 7 element.DB0B1X00S-V00 VT 7 element.Were changes made to the order?\'"", \'Comment 4: ""We don\\\'t know but it can be...""\', ""Comment 5: \'Item has been corrected.\'"", ""Comment 6: \'ok"", ""Comment 7: thanks. Task to close.\']""]\nRelated Issues:\n[]\n\n### End'}"
673,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8358\n\n### Instruction:\nHi\r\nLack of vt-1227 in dhc.\r\n\r\nRafał Boniecki\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! the weights are wrong (it looks like they should be the other way) - we can open this VT and you will correct it.\'"", ""Comment 4: \'We issued doc in cdn manually. Thanks for help. Task to close.\'"", ""Comment 5: \'Thank you for confirmation. \']""]\nRelated Issues:\n[]\n\n### End'}"
674,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8357\n\n### Instruction:\nHi,\r\n\r\nPlease help this issue:\r\nVT Still In Progress, although dispatch prosess already done and VT closed come to DHC and ERP.\r\nPlease give solution and please give us route cause\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: \'id vtka =138014jest zamkniety w dhc"", \'Comment 4: ale wyglada jakby znowu się otwarł w DHP? vth_status =1nie mamy logów\', ""Comment 5: czy można zweryfikowac co sie tam podziało oprócz tego!image-2023-01-18-13-26-13-081.png!\'"", ""Comment 6: \'In DHc VT is in closed status we do not find error logs.From what I can see with you the logs on vehicleticketlog and vehicleticketelementlog tables are not supported. It looks like VT was opened in dhp. were there more cases like this? If this is a one-time case"", ""Comment 7: do you set a good status or will you do it yourself?\'"", ""Comment 8: \'Hi"", \'Comment 9: - could you explain how it can be?- what do you mean about vehicleticketlog and vehicleticketelementlog tables are not supported ?- this is the first time case- How we can close VT\', ""Comment 10: beside VT on DHC and SOR on ERP already close. And actually the truck already out from factory on 16th Jan (when issue was happened).?\'"", \'Comment 11: ""and one thing\', \'Comment 12: if we closed VT using manual wb on DHP interface\', \'Comment 13: I think the problem is departure date between VT Close DHP and DHC will be different\', \'Comment 14: and I don\\\'t know about the integration impact.""\', ""Comment 15: \'Hiad 1. we are unable to give verify it cause there is no error log"", \'Comment 16: maybe you may ask operator how this Vt was proceed?Did someone change something from database>?Aboutvehicleticketlog and vehicleticketelementlog - in both tables there are no entries.If there was a one time issue and we do not have more information it looks like one-time incident. In other file logs there is no information from that hour or for that VT.By now the VT seems to be generated correctly to erp\', ""Comment 17: so we may change the status from database. Do you wish us to do that?\'"", ""Comment 18: \'How to make table vehicleticketlog and vehicleticketelementlog can save data?please change status correctly for that vt with departure data based on dispatch close date that already recorded.\'"", ""Comment 19: \'Status has been changed"", ""Comment 20: we need to ask our developers about the solution for log monitoring.\'"", ""Comment 21: \'[~piotr.gaczorek@kotrak.com]ustawiłam status na 3 z 1update VehicleTicketHeader set vth_status=3 where vth_id in (138014)Pytaja jeszcze jak mieć ustawioen logowanie na tych tabelach z vt w dhp"", ""Comment 22: Block powinien być w przyszłym tygodniu to najwyżej zagadaj.\'"", ""Comment 23: \'!image-2023-01-25-07-10-26-506.png!\'"", ""Comment 24: \'Hello,change logging has been enabled for VT header and VT elements. Ifthe problem occurs again"", ""Comment 25: please create a new ticket. This one should be treated as an incident. Can we close this ticket?\'"", ""Comment 26: \'ok thank you for your support\']""]\nRelated Issues:\n[]\n\n### End'}"
675,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8356\n\n### Instruction:\nHi, \r\n\r\n   Like DGS-8304, Asia Formulation Team said they are not able to see ""Replacement Price"" for MTR factory(56) on DHH. On DHC, we do see as upload successfully. We don\'t know why since week 1 2023, that kinds of issue happen. No root cause is found and after some time they are able to see it. Could you please help check. \n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'!image-2023-01-18-10-44-30-958.png!\'"", ""Comment 3: \'{code:java}2023-01-18 08:41:51,708 [123] INFO  Evolution.DHHolding.GatewayPlugin.Handlers.PriceListChangedMessageHandler [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\152764417\\\\\\\\DHAPPSV3-DHH593-JOB1\\\\\\\\Evolution.DHHolding.GatewayPlugin\\\\\\\\GatewayPlugin\\\\\\\\BaseMessageHandler.cs:64] - Receiving message (Evolution.DHHolding.Interfaces.Prices.PriceListChangedMessage) [Id:757c4810-0a17-498a-a99b-214fc1ded538]2023-01-18 08:41:51,723 [123] INFO  Evolution.DHHolding.GatewayPlugin.Handlers.PriceListChangedMessageHandler [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\152764417\\\\\\\\DHAPPSV3-DHH593-JOB1\\\\\\\\Evolution.DHHolding.GatewayPlugin\\\\\\\\GatewayPlugin\\\\\\\\BaseMessageHandler.cs:69] - Message received successfuly!2023-01-18 08:41:52,192 [123] INFO  Evolution.DHHolding.GatewayPlugin.Handlers.PriceListChangedMessageHandler [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\152764417\\\\\\\\DHAPPSV3-DHH593-JOB1\\\\\\\\Evolution.DHHolding.GatewayPlugin\\\\\\\\GatewayPlugin\\\\\\\\BaseMessageHandler.cs:64] - Receiving message (Evolution.DHHolding.Interfaces.Prices.PriceListChangedMessage) [Id:3e2267cb-3f29-4031-9407-5b5cd5be40d3]2023-01-18 08:41:52,208 [123] INFO  Evolution.DHHolding.GatewayPlugin.Handlers.PriceListChangedMessageHandler [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\152764417\\\\\\\\DHAPPSV3-DHH593-JOB1\\\\\\\\Evolution.DHHolding.GatewayPlugin\\\\\\\\GatewayPlugin\\\\\\\\BaseMessageHandler.cs:69] - Message received successfuly!{code}\'"", \'Comment 4: \\\'Dear Clara,Price list and ""Replacement Price"" for plant MTR are visible if we consider week 2.!image-2023-01-18-10-50-08-295.png!!image-2023-01-18-10-50-35-330.png!And week 3:!image-2023-01-18-10-52-55-533.png!!image-2023-01-18-10-54-52-556.png!Are they correct?Regards\\\'\', ""Comment 5: \'At about what time replacement prices have been sent from DHC?Regards\'"", \'Comment 6: ""Hi\', \'Comment 7: Yes\', \'Comment 8: that\\\'s send from DHC. I don\\\'t know why Asia Team take some time to see it. Could you please check DHH received time for Week 3?""\', ""Comment 9: \'Dear Clara,Replacement Price Analyses ia a report which is calculated from Price List. Someone in DHH needs to click refresh after choosing relevant week. So it does not have arrival date.When was the Price List for week 3 sent?Regards\'"", ""Comment 10: \'Hi"", \'Comment 11: We do send it week3 at 17-Jan around 5:45 pm (MM Time) (GMT+6:30).Regards\', ""Comment 12: Clara\'"", ""Comment 13: \'+5h:30 >> bo zmiana czasu to będzie 22:30 CET!image-2023-01-19-10-03-54-005.png!\'"", ""Comment 14: \'17 stycznia nic o wskazanej godzinie"", \'Comment 15: a te\', \'Comment 16: które są:{code:java}2023-01-17 12:23:44,433 [17] INFO Evolution.DHHolding.GatewayPlugin.Handlers.PriceListChangedMessageHandler [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\152764417\\\\\\\\DHAPPSV3-DHH593-JOB1\\\\\\\\Evolution.DHHolding.GatewayPlugin\\\\\\\\GatewayPlugin\\\\\\\\BaseMessageHandler.cs:69] - Message received successfuly!{code}18 stycznia pierwsz zapisy dopiero o 8 coś!image-2023-01-19-10-34-08-854.png!Ale\', ""Comment 17: 17go to był Wtorek i były też P1 z opóźnieniem dla Voedershttps://helpdesk.kotrak.com/browse/DGS-8337\'"", \'Comment 18: ""Dear Clara,I haven\\\'t found anything suspicious in logs. Changed message has been processed successfully for Price List.However\', \'Comment 19: on the 17th there was some delay in processing in DHH\', \'Comment 20: we have received task from Netherlands regarding item delays in processing.Regards""\', ""Comment 21: \'Hi"", ""Comment 22: Thank you for checking. I will let you know if still face same issue on next week. \'"", ""Comment 23: \'Shall we close ths task or put it on hold until next week?\'"", ""Comment 24: \'I prefer to hold till next week (26 Jan).\'"", ""Comment 25: \'Sure\'"", ""Comment 26: \'Hi"", \'Comment 27: We got inform from user that this week is ok. They can see replacement price on DHH without any issue. Please close the ticket. ThanksBest Regards\', ""Comment 28: Clara\'"", ""Comment 29: \'Hi Clara.Thank you for your information.Regards\']""]\nRelated Issues:\n[]\n\n### End'}"
676,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8355\n\n### Instruction:\nHi,\r\nVT number 000647, date issue 17 Jan 2023 cannot sync to DHC \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: \'!image-2023-01-18-08-57-12-505.png!\'"", ""Comment 4: \'Should be ok please verify :!image-2023-01-18-09-28-10-658.png!\'"", ""Comment 5: \'hi"", ""Comment 6: could you tell us the route cause of this problem?\'"", ""Comment 7: \'We need route cause to avoid this issue happen again\'"", ""Comment 8: \'hello?\'"", ""Comment 9: \'Hello,In this task we have focused on clearingandunblocking the process.I raised RootCause Analysis (RCA)task for you :DGS-8360Cause from now there is no errors in log to indentify reason quickly.May we close this task?\'"", ""Comment 10: \'ok thank you"", ""Comment 11: please close this task.\']""]\nRelated Issues:\n[\'DGS-8360\']\n\n### End'}"
677,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8354\n\n### Instruction:\nHi\r\n\r\nDaily we are finding errors in DHP when we try to scan a SU barcode in PCS to load the dosing silos.\r\nMost of time we use other SU barcode fo the same delivery or we go to the WebUI and click in the _UL screen > Stocktaking UL > OK_ . Wth this action the WMS engine updates the Stock and PCS engine with correct status and quantity.\r\nHowever Quantity on Hand sometimes is fixed, sometimes not. This became too hard and it\'s becoming critical. Because is happening more and more.\r\n\r\nI could list here all SU barcodes with Stock/PCS diferences, but there is too much for each plant that has integration with PCS.\r\n\r\nYou can run this query in all of three plants with PCS integration: Apucarana, Toledo and Guararapes and you\'ll find SUs with different information about QuantityOnHand or LogisticStatus. I attached an example of Guararapes result, but you can check in all other Toledo and Apucarana plants.\r\n\r\n{noformat}\r\nSELECT\r\n\tssu.Barcode, ssu.QuantityOnHand, psu.QuantityOnHand, ssu.LogisticStatus, psu.LogisticStatus\r\nFROM DHPlantStockBusinessLogicMain.dbo.StockUnits ssu \r\n\tINNER JOIN DHPlantPCSBusinessLogicMain.dbo.StockUnits psu ON psu.Id = ssu.Id \r\nWHERE ssu.LogisticStatus & 470 = ssu.LogisticStatus\r\nAND ssu.Quantity <> 0\r\nAND (ssu.QuantityOnHand <> psu.QuantityOnHand\r\nOR ssu.LogisticStatus <> psu.LogisticStatus\r\n)\r\n{noformat}\r\n\r\nSo, could you please fix these SUs and fix the root cause of this in DHP engines communication?\r\n\r\nThank you very much\n\n### Response:\n[""Comment 1: [\'!image!\'"", \'Comment 2: ""It\\\'s important to highlight that in December we had 8 DGS about communication errors between engines:* DGS-7974* DGS-8087* DGS-8184* DGS-8185* DGS-8186* DGS-8187* DGS-8203* DGS-8209I don\\\'t have *DGS - Monthly Report* of January yet\', \'Comment 3: but I can assure you that this is not the first.I think a RCA should be raised to thisThank you""\', ""Comment 4: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 5: \'There is already one RCA - DGS-8168I will find out if this is one case and let you know.Regards.\'"", ""Comment 6: \'Nasz select pokazuje to samo aktualnie są tylko te  created w listopadzie.2022 !screenshot-1! . Tutaj Guararapes.\'"", ""Comment 7: \'Hello,the codes that are still on the list for Guararapes differences are from November:!image-2023-01-25-14-14-56-969.png!We will correct them and check if they will be new/next.I just want to confirm if the stock ones are correct.\'"", ""Comment 8: \'Hi PiotrWe still have some barcodes from Apucarana and some from Guararapes.Thank you!image-2!!image-3!\'"", \'Comment 9: ""{code:java}update supcsset supcs.Quantity=su.Quantity,supcs.QuantityOnHand=su.QuantityOnHandFROM DHPlantStockBusinessLogicMain.dbo.StockUnits suINNER JOIN DHPlantPCSBusinessLogicMain.dbo.StockUnits supcs ON supcs.id = su.idwhere --supcs.barcode <> su.barcode and supcs.Quantity<>su.Quantity and su.LogisticStatus not in(32,32800)and supcs.Quantity=0{code}{code:java}SELECT * FROM DHPlantPCSBusinessLogicMain.api.StockUnits su WHERE su.Barcode = \\\'88-W0AREG\\\'{code}{code:java}select supcs.Quantity,supcs.QuantityOnHand,supcs.Id,su.Quantity,su.QuantityOnHand,supcs.barcode,supcs.LogisticStatus,su.LogisticStatus,su.id,su.CreatedDateFROM DHPlantStockBusinessLogicMain.dbo.StockUnits suINNER JOIN DHPlantPCSBusinessLogicMain.dbo.StockUnits supcs ON supcs.id = su.idwhere --supcs.barcode <> su.barcode and supcs.Quantity<>su.Quantity and su.LogisticStatus not in(32,32800)or supcs.QuantityOnHand<>su.QuantityOnHand and su.LogisticStatus not in(32,32800){code}""\', \'Comment 10: ""I corrected the codes for Guararapes.\\\'85-OB001B\\\',\\\'85-OB001G\\\',\\\'85-OB0016\\\',\\\'85-OB001F\\\',\\\'85-OB001H\\\',\\\'85-OB001L\\\',\\\'85-OB001I\\\',\\\'85-OB001D\\\'these were on the list of differences also in the last verifications with the same differences.The others codes change during production. Task is still under analysis.""\', ""Comment 11: \'Hello PiotrThere is this new UL:* Apucarana 88-W0AREG* Guararapes 85-W02DZYThank you\'"", ""Comment 12: \'Hello Maicon. The problem should not occur in version 8.5I would like to know if there will be an upgrade in the near future to fix the problem.Regards.\'"", \'Comment 13: ""Hi Piotr We\\\'ll plan the upgrade for the next days.You can close this task.Thank you very much""\', ""Comment 14: \'Thank you for information.\']""]\nRelated Issues:\n[]\n\n### End'}"
678,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8353\n\n### Instruction:\nPlease remove additional technology UT506468 from DHC Compound.\r\n\r\n\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Additional technology UT506468 has been removed.\'"", ""Comment 3: \'Thanks Piotr,the ticket can be closed"", ""Comment 4: thank you for the support.\'"", ""Comment 5: \'Thank you for confirmation,\\\\rRegards.\']""]\nRelated Issues:\n[]\n\n### End'}"
679,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8352\n\n### Instruction:\nwe have problem to read some barcodes on PCS, system can not identify barcodes in the integration.\r\n\r\n88-W0FHGI\r\n\r\n88-W0FHGM\r\n\r\n88-W0FHGQ\r\n\r\n88-W0FHGJ\r\n\r\nCould you please check if we have some error and why the barcodes are not available for pcs?\r\n\r\nThank you\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'!image-1!\'"", ""Comment 3: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 4: \' !screenshot-1! \'"", ""Comment 5: \'We  can see this barcodes in view [api].[StockUnits] !screenshot-2! Can you ask PCS provider if the problem is not on their side?Regards.\'"", ""Comment 6: \'Hello"", ""Comment 7: do you have information according to our last comment or feedback from PCS provider?Could you please confirm if we can close this task?Regards\'"", ""Comment 8: \'Hello,We are closing this task as we haven’treceivedany replyfromyouforalong time.Regards\']""]\nRelated Issues:\n[]\n\n### End'}"
680,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8351\n\n### Instruction:\nMissing migration 101529 Huisman NAS\r\n\n\n### Response:\n[""Comment 1: [\'{color:black}Goodday,{color} {color:black}{color} {color:black}Please migrate these missing files for customer Huisman 101529.{color} {color:black}Thanks.{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} |   [^Sales migration_Huisman 101529.xlsx] _(17 kB)_[^Feed migration_Huisman 101529.xlsx] _(254 kB)_[^Purchase_migration_Huisman 101529.xlsx] _(21 kB)_\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 3: ""[~CJong@deheus.com],please fix data in column Del_ItmID for Feed Sale. A few items doesn\\\'t exists in Intense.I\\\'m waiting for correct data.Best regards,Grzegorz""\', ""Comment 4: \'[~CJong@deheus.com],All documents have been migrated into Intense Platform.You can feel free to test it.Best regards,Grzegorz\'"", ""Comment 5: \'Sorry I forgot to reply. You can resolve this as done.\'"", \'Comment 6: ""No problem. Thank you for a reply. I\\\'m closing the task.Best regards,Grzegorz""]\']\nRelated Issues:\n[]\n\n### End'}"
681,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8350\n\n### Instruction:\nWhat are the conditons off printing different banking account on invoice.\r\nWill the banking account off ""accounting"" be used or from ""adresses"".\r\n\r\nIf ""adresses"" what are the selecting conditions off the bankingaccount?\r\nIs no bankaccount in ""adresses"" accepted?\r\n\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: \'Hello"", ""Comment 4: could please bring the path to printout template. and document number.It could be set in diffrent way for diffrent document type.this is example of path :!image-2023-01-18-14-48-46-340.png!\'"", ""Comment 5: \'Dear,According to the service agreement this task should be categorized as a service request.Kindly approve change of the type of this task.Regards\'"", ""Comment 6: \'You can categorized this task as a service request.\'"", ""Comment 7: \'Thank you"", ""Comment 8: could you provide more details according to my previous question ?could please bring the path to printout template. and document number.It could be set in diffrent way for diffrent document type.this is example of path :\'"", ""Comment 9: \'See also DGS-8553\'"", ""Comment 10: \'Since a new task has been created in the same topic"", ""Comment 11: this one will be closed.\']""]\nRelated Issues:\n[]\n\n### End'}"
682,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8349\n\n### Instruction:\nWe should be able to reverse these even though we don’t indicate a full number. In these cases the SR’s are linked to Boer BE.\r\n The SR’s and all related invoices should be reversed.\r\nThe SR’s should be reversed as well.\xa0\n\n### Response:\n[\'Comment 1: [""How it is now:Action \\\'Create Reverse SR\\\' should be visible when on Slaughtery Report \\\'Full number\\\' is filled and selected Round in this field is active.How should it be:If \\\'Full number\\\' is empty *and* \\\'Farmer code\\\' = 888888 action should be visible for these SR documents[~mbovene@deheus.com]is it right?What about reversing Slaughtery Reports. As I know for now there is no functionality for creating reverse Slaughtery Report (correction of original one).How we should handle or deleting Slaughtery Reports should be possible in some cases?""\', \'Comment 2: \\\'Indeed when \\\\\\\'Full number\\\\\\\' is empty and \\\\\\\'Farmer code\\\\\\\' = 888888 action should be visible for these SR documents.Also when it is Trade (full number is Trade) it should be possible to reverse the SR. Now this is not possible.I don\\\\\\\'t get your statement ""As I know for now there is no functionality for creating reverse Slaughtery Report (correction of original one)"". I don\\\\\\\'t have the rights but there is a possibility to reverse SR\\\\\\\'s (see attachment).Deleting SR\\\\\\\'s is needed sometimes now after reversion. Now  the reversed SR\\\\\\\'s are still part of the technical results calculation in Intense. But they shouldn\\\\\\\'t. In order to remove them they are deleted right now.I don\\\\\\\'t want users to be able to delete SR\\\\\\\'s.!image!\\\'\', \'Comment 3: \\\'{quote}Indeed when \\\\\\\'Full number\\\\\\\' is empty and \\\\\\\'Farmer code\\\\\\\' = 888888 action should be visible for these SR documents.Also when it is Trade (full number is Trade) it should be possible to reverse the SR. Now this is not possible.{quote}We can implement this change for these conditions and it could be possible.Regarding part of creating Credit Slaughtery Report:{quote}I don\\\\\\\'t get your statement ""As I know for now there is no functionality for creating reverse Slaughtery Report (correction of original one)"". I don\\\\\\\'t have the rights but there is a possibility to reverse SR\\\\\\\'s (see attachment).Deleting SR\\\\\\\'s is needed sometimes now after reversion. Now the reversed SR\\\\\\\'s are still part of the technical results calculation in Intense. But they shouldn\\\\\\\'t. In order to remove them they are deleted right now.I don\\\\\\\'t want users to be able to delete SR\\\\\\\'s.!image!{quote}Action \\\\\\\'Create reverse SR\\\\\\\' has few steps and there are: # Creating correct SI invoices # Creating correct PI invoices # Creating correct SI guarantees invoices # Creating S2P (if exist) # Updating field \\\\\\\'Reverse SR\\\\\\\' on Salughtery Report documentIn intense we don\\\\\\\'t have functionality of creating corrected Slaughtery Reports. Only creating documents related to Slaughtery Report.I think functionality of reversing SR is based on this task https://helpdesk.kotrak.com/browse/DHNLC-477I got a quick look at Technical results and calculations skip those SR which has marked field \\\\\\\'Reverse SR\\\\\\\'\\\'\', ""Comment 4: \'Ok"", ""Comment 5: please extend the reverse SR functionality.\'"", \'Comment 6: ""Functionality has been extended.Action \\\'Create reverse SR\\\' now is also visible for Slaughtery reports: * when \\\'Full number\\\' is empty and \\\'Farmer code\\\' = 888888 * when it is Trade (full number is Trade) it is possible to reverse the SRIt\\\'s done in MAS NL sector on IBIP_DH and IBIP_DH_TEST.Please verify and confirm that is correct.""\', ""Comment 7: \'Zmienione zostały warunki podłączenia akcji oraz warunek wywołania akcji grupującej.\'"", ""Comment 8: \'My confirmation.\']""]\nRelated Issues:\n[\'DGS-8373\']\n\n### End'}"
683,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8348\n\n### Instruction:\nWe have problem to accept recipe in DHC, system shows an error message and the recipe is not accept.\r\n\r\nItem SUR7721-P-MD version 2\r\n\r\nCould you please check why we can\'t accept and fix it?\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: \'pelniutko bledów do recipe !image-2023-01-17-13-29-39-786.png!\'"", ""Comment 4: \'Please check now\'"", \'Comment 5: ""Hello\', \'Comment 6: now it\\\'s correct. You can close this task. Thank you.""]\']\nRelated Issues:\n[]\n\n### End'}"
684,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8347\n\n### Instruction:\nUser M. Erp can not login DH CDN (SDNL-37717)\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: \'New message from user:Suddenly I can log in.   ?????Please close ticket\'"", ""Comment 4: \'I am able to log on could you profide full operator login and from what rdp he try to log on\'"", ""Comment 5: \'Please close ticket\']""]\nRelated Issues:\n[]\n\n### End'}"
685,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8346\n\n### Instruction:\nThe PO with number 1283/22 cannot be seen in DHP, please help solve and kindly show me how to solve this issue going forward please.\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-18-07-48-19-101.png!\'"", \'Comment 3: \\\'An error occurred while updating the entries. See the inner exception for details. -> The INSERT statement conflicted with the FOREIGN KEY constraint ""FK_Orders_ContactDatas_MainBusinessPartnerId_MainBusinessPartnerContactDataId"". The conflict occurred in database ""DHPlantVCBusinessLogicMain""\', \'Comment 4: table ""dbo.ContactDatas"".The statement has been terminated.\\\'\', ""Comment 5: \'Please verify.\'"", ""Comment 6: \'please close\']""]\nRelated Issues:\n[]\n\n### End'}"
686,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8345\n\n### Instruction:\nSee example\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,Why do you want to delete this line?It\\\'s not possible because it is feed sale line which comes from Milas\', \'Comment 4: so it\\\'s functionality related to integration with Milas implemented in Intense.In that cases you can only move feed to different round.""\', \'Comment 5: ""Hi Damian\', \'Comment 6: we would like to delete the yellow lines.This customer quit with his contract\', \'Comment 7: but the checkbox was still activated. So there were send from Milas while they shouldn\\\'t been send.!image-1!""\', ""Comment 8: \'(68677,82796,82797,75547,98017,98016,98015) id usuniętych elementów nie usunięte z mapingów id dokumentu30878\'"", ""Comment 9: \'Feed Sale lane is deleted.\']""]\nRelated Issues:\n[]\n\n### End'}"
687,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8344\n\n### Instruction:\nMissing migration 803319 Engelenhoven NAS\n\n### Response:\n[""Comment 1: [\'{color:black}Goodmorning,{color} {color:black}{color} {color:black}Please migrate these missing files for customer Engelenhoven 803319.{color} {color:black}Thanks.{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} |   [^Purchase_migration_Engelenhoven 803319.xlsx] _(22 kB)_[^Sales migration_Engelenhoven 803319.xlsx] _(19 kB)_[^Feed migration_Engelenhoven 803319.xlsx] _(256 kB)_\'"", \'Comment 2: ""[~CJong@deheus.com],I can\\\'t map item -505305 in Del_ItmID column forFeed migration. Could you fix it?Best regards,Grzegorz""\', ""Comment 3: \'Hi"", ""Comment 4: you can take the item code DIVO for this. Thanks in advance.\'"", ""Comment 5: \'| |{color:#666666} Jong"", \'Comment 6: Christine de heeft een OneDrive voor Bedrijven-bestand met u gedeeld. Klik op de onderstaande koppeling om het bestand te bekijken.{color} | | !image00001! |{color:#0072c6}{color} [{color:#0072c6}{color}{color:#0072c6}Feed migration_Engelenhoven 803319.xlsx{color}|https://deheusanimalnutrition-my.sharepoint.com/personal/cjong_deheus_com/Documents/Desktop/NAS%20Intense/Feed%20migration_Engelenhoven%20803319.xlsx?web=1]{color:#0072c6}{color}{color:#0072c6}{color} |       {color:black}Hi Grzegorz,{color} {color:black}{color} {color:black}For this item I also made a DIVO.{color} {color:black}See enclosed file{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) <jira@kotrak.com>   *Verzonden:* woensdag 18 januari 2023 09:59  *Aan:* Jong\', ""Comment 7: Christine de <CJong@deheus.com>  *Onderwerp:* DGS-8344 Missing migration 803319 Engelenhoven 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 8: \'Hi [~mbovene@deheus.com],A lot of migration files have mistakes. Next case when item code is wrong -505506. Could you check the data and sendme a correct data file?The user is responsible for correct data in migration files.If you can"", ""Comment 9: please look into task too - https://helpdesk.kotrak.com/browse/DGS-8343.Best regards,Grzegorz\'"", \'Comment 10: ""Hi [~CJong@deheus.com],your enclosed file doesn\\\'t work. Please add the attachement into the Jira task.Best regards,Grzegorz""\', ""Comment 11: \'{color:black}Dear Grzegorz,{color} {color:black}{color} {color:black}Some items are not in Intense and should have the code DIVO.{color} {color:black}I didn’t test all the item codes.{color} {color:black}Enclosed the modified file.{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) <jira@kotrak.com>   *Verzonden:* woensdag 18 januari 2023 11:01  *Aan:* Jong"", ""Comment 12: Christine de <CJong@deheus.com>  *Onderwerp:* DGS-8344 Missing migration 803319 Engelenhoven 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}* |   [^Feed migration_Engelenhoven 803319-1.xlsx] _(256 kB)_\'"", ""Comment 13: \'[~mbovene@deheus.com]"", ""Comment 14: [~CJong@deheus.com],Purchase and Sales Invoices have been migrated into Intense Platform.You can feel free to test it.Best regards,Grzegorz\'"", ""Comment 15: \'[~CJong@deheus.com],all documents have been migrated. You can feel free to test it.Best regards,Grzegorz\'"", ""Comment 16: \'Sorry I forgot to reply. You can resolve this as done.\'"", \'Comment 17: ""No problem. Thank you for a reply. I\\\'m closing the task.Best regards,Grzegorz""]\']\nRelated Issues:\n[]\n\n### End'}"
688,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8343\n\n### Instruction:\nMissing migration 102038 Westerink NAS\n\n### Response:\n[""Comment 1: [\'{color:black}Goodmorning,{color} {color:black}{color} {color:black}Please migrate these missing files for customer Westerink 102038.{color} {color:black}Thanks.{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_Westerink 102038.xlsx] _(251 kB)_[^Sales migration_Westerink 102038.xlsx] _(13 kB)_[^Purchase_migration_Westerink 102038.xlsx] _(18 kB)_\'"", \'Comment 2: ""Hi [~CJong@deheus.com],item code -505520 - from FS excel file doesn\\\'t exsist in Intesne for NAS sector. Could you fix it?Best regards,Grzegorz""\', \'Comment 3: ""[~CJong@deheus.com],which Contract Farmer is correct for all import lines?Are you sure\', ""Comment 4: that contract farmer \'CF-N/0068\' is for all Sales invoice lines? Because"", \'Comment 5: for PI and FS I see different contract - \\\'CF-N/0042\\\'.Best regards,Grzegorz""\', ""Comment 6: \'{color:black}Hi Grzegorz,{color} {color:black}{color} {color:black}I made it a DIVO item.{color} {color:black}See enclosed file.{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) <jira@kotrak.com>   *Verzonden:* dinsdag 17 januari 2023 15:03  *Aan:* Jong"", ""Comment 7: Christine de <CJong@deheus.com>  *Onderwerp:* DGS-8343 Missing migration 102038 Westerink 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}* |   [^Feed migration_Westerink 102038-1.xlsx] _(251 kB)_\'"", ""Comment 8: \'{color:black}Sorry Grzegorz"", \'Comment 9: the correct contract is number 0042.{color} {color:black}The round for Westerink is 102038/0042/0001{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) <jira@kotrak.com>   *Verzonden:* dinsdag 17 januari 2023 15:48  *Aan:* Jong\', ""Comment 10: Christine de <CJong@deheus.com>  *Onderwerp:* DGS-8343 Missing migration 102038 Westerink 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 11: \'[~CJong@deheus.com],all documents have been migrated. You can feel free to test it.Best regards,Grzegorz\'"", ""Comment 12: \'Sorry I forgot to reply. You can resolve this as done.\'"", \'Comment 13: ""No problem. Thank you for a reply. I\\\'m closing the task.Best regards,Grzegorz""]\']\nRelated Issues:\n[]\n\n### End'}"
689,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8342\n\n### Instruction:\nWe are missing a lot of migration files for a specific customer. Could you please migrate the information from the files?\r\n\r\nMigration files for customers:\r\n * 817005\r\n * 013563\n\n### Response:\n[""Comment 1: [\'została zrobiona kolejna migracja do NAS!image-2023-01-19-12-19-47-476.png!\'"", ""Comment 2: \'kolejna migracja"", ""Comment 3: dla MAS NL!image-2023-01-19-15-48-58-157.png!\'"", \'Comment 4: ""All documents have been migrated into Intense Platform.I\\\'m closing the task.Best regards,Grzegorz""]\']\nRelated Issues:\n[]\n\n### End'}"
690,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8341\n\n### Instruction:\nDHC keeps throwing this error message for certain VT\'s when we regenerate the VT the error message eventually updates to the correct one. \r\n\r\nwe are also still experiencing issues with PLR\'s appearing as though they have not generated but are just not linked to their applicable Job Orders.\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!!image-1!\'"", ""Comment 2: \'[^VT error message.mp4] _(449 kB)_\'"", ""Comment 3: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 4: \'To tak: jeśli chodzi o VT-581"", ""Comment 5: teraz ma nieco innego errora!image-2023-01-17-14-25-11-639.png!\'"", ""Comment 6: \'VT-583 jest już generated bez messega!image-2023-01-17-14-26-39-807.png!\'"", ""Comment 7: \'Dziś już jest generated!image-2023-01-18-11-10-50-214.png!\'"", ""Comment 8: \'19A93EF2-6069-4084-A4F0-C5EF1F6F43F2\'"", ""Comment 9: \'Ilości się zgadzają...!image-2023-01-18-11-37-00-130.png!!image-2023-01-18-11-33-41-531.png!!image-2023-01-18-11-35-57-745.png!!image-2023-01-18-11-35-23-004.png!\'"", ""Comment 10: \'Hello,Yesterday"", \'Comment 11: when I have a look at this VT\', \'Comment 12: I had other error. This is also error from ERP XL:!image-2023-01-18-13-15-52-710.png!This error is rooted generally in Deliveries:>>the lack of a resource>> or the related delivery has dispatched,>> the intake may not have been done yet\', \'Comment 13: i.e. PLR not produced\', \'Comment 14: e.gToday VT-581 has generated documents and all is fine.However\', \'Comment 15: error below may mean that two processes / documents have been processed at the same time. To verify this error we need fresh example or exact time when the documents were generated from VT and resulted with this error!image-2023-01-18-13-39-52-995.png!Reagrding not linked JO and IR documents\', \'Comment 16: again we need the freshest example. Probably there may be a tmeout\', ""Comment 17: but to be sure we need to verify it with the new exampe.Regards!image-2023-01-18-13-39-52-995!\'"", ""Comment 18: \'Hello"", ""Comment 19: new example for VT issue 295!image-2!\'"", ""Comment 20: \'please can we link the old job order examples... the latest example is for the 19th !image-3!\'"", ""Comment 21: \'SO-31/23/MOM!image-2023-01-20-09-32-02-297.png!\'"", ""Comment 22: \'Log z erp ntegratora[^vt-295.txt]\'"", ""Comment 23: \'[^so-31-23-MOM.txt]^DHCService dla ordera z tego VT^\'"", \'Comment 24: ""Data błędu:!image-2023-01-20-09-54-15-817.png!O tej godzinie leciały timeouty\', ""Comment 25: aż miłoXD{code:java}2023-01-19 20:19:03,272 [27] INFO  Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor [(null)] - VehicleTicket - VT-295/1/2023/MM [Id: 3a693e2e-f6ec-4322-bb4b-0a7b762fab81]2023-01-19 20:19:03,272 [27] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor [(null)] - VehicleTicket Validator started - Evolution.ErpIntegrator.Extensions.VTOrderValidator.VehicleTicketOrderValidator2023-01-19 20:19:03,272 [27] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor [(null)] - VehicleTicket Validator finished - Evolution.ErpIntegrator.Extensions.VTOrderValidator.VehicleTicketOrderValidator2023-01-19 20:19:03,569 [68] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateSalesOrderRelease [(null)] - GenerateSalesOrderRelease execution started2023-01-19 20:19:03,850 [68] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateSalesOrderRelease [(null)] - Forcing document number - 143/0/2023/MPMM for vt element id - Id: 0672ff6b-f5f1-4bc5-ace9-c136d90a565c2023-01-19 20:19:04,038 [68] ERROR Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateSalesOrderRelease [(null)] - System.OutOfMemoryException: Exception of type \'System.OutOfMemoryException\' was thrown.   at System.Data.SqlClient.TdsParser.TdsExecuteRPC(SqlCommand cmd"", \'Comment 26: _SqlRPC[] rpcArray\', \'Comment 27: Int32 timeout\', \'Comment 28: Boolean inSchema\', \'Comment 29: SqlNotificationRequest notificationRequest\', \'Comment 30: TdsParserStateObject stateObj\', \'Comment 31: Boolean isCommandProc\', \'Comment 32: Boolean sync\', \'Comment 33: TaskCompletionSource`1 completion\', \'Comment 34: Int32 startRpc\', \'Comment 35: Int32 startParam)   at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior\', \'Comment 36: RunBehavior runBehavior\', \'Comment 37: Boolean returnStream\', \'Comment 38: Boolean async\', \'Comment 39: Int32 timeout\', \'Comment 40: Task& task\', \'Comment 41: Boolean asyncWrite\', \'Comment 42: Boolean inRetry\', \'Comment 43: SqlDataReader ds\', \'Comment 44: Boolean describeParameterEncryptionRequest)   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior\', \'Comment 45: RunBehavior runBehavior\', \'Comment 46: Boolean returnStream\', \'Comment 47: String method\', \'Comment 48: TaskCompletionSource`1 completion\', \'Comment 49: Int32 timeout\', \'Comment 50: Task& task\', \'Comment 51: Boolean& usedCache\', \'Comment 52: Boolean asyncWrite\', \'Comment 53: Boolean inRetry)   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior\', \'Comment 54: RunBehavior runBehavior\', \'Comment 55: Boolean returnStream\', \'Comment 56: String method)   at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior\', \'Comment 57: 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 58: DbCommandInterceptionContext`1 c)   at System.Data.Entity.Infrastructure.Interception.InternalDispatcher`1.Dispatch[TTarget,TInterceptionContext,TResult](TTarget target\', \'Comment 59: Func`3 operation\', \'Comment 60: TInterceptionContext interceptionContext\', \'Comment 61: Action`3 executing\', \'Comment 62: Action`3 executed)   at System.Data.Entity.Infrastructure.Interception.DbCommandDispatcher.Reader(DbCommand command\', \'Comment 63: DbCommandInterceptionContext interceptionContext)   at System.Data.Entity.Internal.InterceptableDbCommand.ExecuteDbDataReader(CommandBehavior behavior)   at System.Data.Common.DbCommand.ExecuteReader(CommandBehavior behavior)   at System.Data.Entity.Core.EntityClient.Internal.EntityCommandDefinition.ExecuteStoreCommands(EntityCommand entityCommand\', \'Comment 64: CommandBehavior behavior)   at System.Data.Entity.Core.Objects.Internal.ObjectQueryExecutionPlan.Execute[TResultType](ObjectContext context\', \'Comment 65: ObjectParameterCollection parameterValues)   at System.Data.Entity.Core.Objects.ObjectQuery`1.<>c__DisplayClass41_0.<GetResults>b__1()   at System.Data.Entity.Core.Objects.ObjectContext.ExecuteInTransaction[T](Func`1 func\', \'Comment 66: IDbExecutionStrategy executionStrategy\', \'Comment 67: Boolean startLocalTransaction\', \'Comment 68: Boolean releaseConnectionOnSuccess)   at System.Data.Entity.Core.Objects.ObjectQuery`1.<>c__DisplayClass41_0.<GetResults>b__0()   at System.Data.Entity.SqlServer.DefaultSqlExecutionStrategy.Execute[TResult](Func`1 operation)   at System.Data.Entity.Core.Objects.ObjectQuery`1.GetResults(Nullable`1 forMergeOption)   at System.Data.Entity.Core.Objects.ObjectQuery`1.<System.Collections.Generic.IEnumerable<T>.GetEnumerator>b__31_0()   at System.Data.Entity.Internal.LazyEnumerator`1.MoveNext()   at System.Linq.Enumerable.Single[TSource](IEnumerable`1 source)   at System.Data.Entity.Core.Objects.ELinq.ObjectQueryProvider.<>c__14`1.<GetElementFunction>b__14_3(IEnumerable`1 sequence)   at System.Data.Entity.Core.Objects.ELinq.ObjectQueryProvider.ExecuteSingle[TResult](IEnumerable`1 query\', \'Comment 69: Expression queryRoot)   at System.Data.Entity.Core.Objects.ELinq.ObjectQueryProvider.System.Linq.IQueryProvider.Execute[TResult](Expression expression)   at System.Data.Entity.Internal.Linq.DbQueryProvider.Execute[TResult](Expression expression)   at System.Linq.Queryable.Single[TSource](IQueryable`1 source)   at Evolution.ErpIntegrator.CdnXL.CdnXL2019.Dictionaries.Items.CdnXL2019ItemRepository.GetItem(XLObjectKey xlId\', \'Comment 70: String code) in C:\\\\\\\\TeamCity\\\\\\\\buildAgent\\\\\\\\work\\\\\\\\57a7e278b67a115c\\\\\\\\Evolution.ErpIntegrator\\\\\\\\CdnXL\\\\\\\\Evolution.ErpIntegrator.CdnXL.CdnXL2019\\\\\\\\Dictionaries\\\\\\\\Items\\\\\\\\CdnXL2019ItemRepository.cs:line 241   at Evolution.ErpIntegrator.CdnXL.CdnXL2019.Dictionaries.Items.CdnXL2019ItemRepository.GetItem(ObjectKey id) in C:\\\\\\\\TeamCity\\\\\\\\buildAgent\\\\\\\\work\\\\\\\\57a7e278b67a115c\\\\\\\\Evolution.ErpIntegrator\\\\\\\\CdnXL\\\\\\\\Evolution.ErpIntegrator.CdnXL.CdnXL2019\\\\\\\\Dictionaries\\\\\\\\Items\\\\\\\\CdnXL2019ItemRepository.cs:line 30   at Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateSalesOrderRelease.GenerateSalesOrderReleaseData(VehicleTicket vehicleTicket\', ""Comment 71: IMatchRule`1 vehicleTicketElementSelector)   at Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateSalesOrderRelease.OnExecute(VehicleTicket vehicleTicket)   at Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketIntegrationTaskBase.OnExecute(Object data)   at Evolution.ErpIntegrator.IntegrationLibrary.IntegrationTaskBase.Execute(Object data)2023-01-19 20:19:04,038 [68] ERROR Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor [(null)] - Exception of type \'System.OutOfMemoryException\' was thrown.System.OutOfMemoryException: Exception of type \'System.OutOfMemoryException\' was thrown.   at System.Data.SqlClient.TdsParser.TdsExecuteRPC(SqlCommand cmd"", \'Comment 72: _SqlRPC[] rpcArray\', \'Comment 73: Int32 timeout\', \'Comment 74: Boolean inSchema\', \'Comment 75: SqlNotificationRequest notificationRequest\', \'Comment 76: TdsParserStateObject stateObj\', \'Comment 77: Boolean isCommandProc\', \'Comment 78: Boolean sync\', \'Comment 79: TaskCompletionSource`1 completion\', \'Comment 80: Int32 startRpc\', \'Comment 81: Int32 startParam)   at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior\', \'Comment 82: RunBehavior runBehavior\', \'Comment 83: Boolean returnStream\', \'Comment 84: Boolean async\', \'Comment 85: Int32 timeout\', \'Comment 86: Task& task\', \'Comment 87: Boolean asyncWrite\', \'Comment 88: Boolean inRetry\', \'Comment 89: SqlDataReader ds\', \'Comment 90: Boolean describeParameterEncryptionRequest)   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior\', \'Comment 91: RunBehavior runBehavior\', \'Comment 92: Boolean returnStream\', \'Comment 93: String method\', \'Comment 94: TaskCompletionSource`1 completion\', \'Comment 95: Int32 timeout\', \'Comment 96: Task& task\', \'Comment 97: Boolean& usedCache\', \'Comment 98: Boolean asyncWrite\', \'Comment 99: Boolean inRetry)   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior\', \'Comment 100: RunBehavior runBehavior\', \'Comment 101: Boolean returnStream\', \'Comment 102: String method)   at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior\', \'Comment 103: 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 104: DbCommandInterceptionContext`1 c)   at System.Data.Entity.Infrastructure.Interception.InternalDispatcher`1.Dispatch[TTarget,TInterceptionContext,TResult](TTarget target\', \'Comment 105: Func`3 operation\', \'Comment 106: TInterceptionContext interceptionContext\', \'Comment 107: Action`3 executing\', \'Comment 108: Action`3 executed)   at System.Data.Entity.Infrastructure.Interception.DbCommandDispatcher.Reader(DbCommand command\', \'Comment 109: DbCommandInterceptionContext interceptionContext)   at System.Data.Entity.Internal.InterceptableDbCommand.ExecuteDbDataReader(CommandBehavior behavior)   at System.Data.Common.DbCommand.ExecuteReader(CommandBehavior behavior)   at System.Data.Entity.Core.EntityClient.Internal.EntityCommandDefinition.ExecuteStoreCommands(EntityCommand entityCommand\', \'Comment 110: CommandBehavior behavior)   at System.Data.Entity.Core.Objects.Internal.ObjectQueryExecutionPlan.Execute[TResultType](ObjectContext context\', \'Comment 111: ObjectParameterCollection parameterValues)   at System.Data.Entity.Core.Objects.ObjectQuery`1.<>c__DisplayClass41_0.<GetResults>b__1()   at System.Data.Entity.Core.Objects.ObjectContext.ExecuteInTransaction[T](Func`1 func\', \'Comment 112: IDbExecutionStrategy executionStrategy\', \'Comment 113: Boolean startLocalTransaction\', \'Comment 114: Boolean releaseConnectionOnSuccess)   at System.Data.Entity.Core.Objects.ObjectQuery`1.<>c__DisplayClass41_0.<GetResults>b__0()   at System.Data.Entity.SqlServer.DefaultSqlExecutionStrategy.Execute[TResult](Func`1 operation)   at System.Data.Entity.Core.Objects.ObjectQuery`1.GetResults(Nullable`1 forMergeOption)   at System.Data.Entity.Core.Objects.ObjectQuery`1.<System.Collections.Generic.IEnumerable<T>.GetEnumerator>b__31_0()   at System.Data.Entity.Internal.LazyEnumerator`1.MoveNext()   at System.Linq.Enumerable.Single[TSource](IEnumerable`1 source)   at System.Data.Entity.Core.Objects.ELinq.ObjectQueryProvider.<>c__14`1.<GetElementFunction>b__14_3(IEnumerable`1 sequence)   at System.Data.Entity.Core.Objects.ELinq.ObjectQueryProvider.ExecuteSingle[TResult](IEnumerable`1 query\', \'Comment 115: Expression queryRoot)   at System.Data.Entity.Core.Objects.ELinq.ObjectQueryProvider.System.Linq.IQueryProvider.Execute[TResult](Expression expression)   at System.Data.Entity.Internal.Linq.DbQueryProvider.Execute[TResult](Expression expression)   at System.Linq.Queryable.Single[TSource](IQueryable`1 source)   at Evolution.ErpIntegrator.CdnXL.CdnXL2019.Dictionaries.Items.CdnXL2019ItemRepository.GetItem(XLObjectKey xlId\', \'Comment 116: String code) in C:\\\\\\\\TeamCity\\\\\\\\buildAgent\\\\\\\\work\\\\\\\\57a7e278b67a115c\\\\\\\\Evolution.ErpIntegrator\\\\\\\\CdnXL\\\\\\\\Evolution.ErpIntegrator.CdnXL.CdnXL2019\\\\\\\\Dictionaries\\\\\\\\Items\\\\\\\\CdnXL2019ItemRepository.cs:line 241   at Evolution.ErpIntegrator.CdnXL.CdnXL2019.Dictionaries.Items.CdnXL2019ItemRepository.GetItem(ObjectKey id) in C:\\\\\\\\TeamCity\\\\\\\\buildAgent\\\\\\\\work\\\\\\\\57a7e278b67a115c\\\\\\\\Evolution.ErpIntegrator\\\\\\\\CdnXL\\\\\\\\Evolution.ErpIntegrator.CdnXL.CdnXL2019\\\\\\\\Dictionaries\\\\\\\\Items\\\\\\\\CdnXL2019ItemRepository.cs:line 30   at Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateSalesOrderRelease.GenerateSalesOrderReleaseData(VehicleTicket vehicleTicket\', \'Comment 117: IMatchRule`1 vehicleTicketElementSelector)   at Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateSalesOrderRelease.OnExecute(VehicleTicket vehicleTicket)   at Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketIntegrationTaskBase.OnExecute(Object data)   at Evolution.ErpIntegrator.IntegrationLibrary.IntegrationTaskBase.Execute(Object data)   at Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor.<>c__DisplayClass6_2.<ProcessSingleVT>b__1(){code}""\', ""Comment 118: \'XL:!image-2023-01-20-10-55-54-884.png!!image-2023-01-20-11-10-13-378.png!DHC!image-2023-01-20-10-56-11-789.png!!image-2023-01-20-11-02-45-157.png!!image-2023-01-20-11-10-13-378!\'"", ""Comment 119: \'These are linked!image-2023-01-20-11-31-02-434.png!\'"", ""Comment 120: \'Do sprawdzenia:0633160123002 0633160123001 0682190123003!image-2023-01-20-11-34-32-579.png!!image-2023-01-20-11-34-32-579!\'"", ""Comment 121: \'!image-2023-01-20-11-42-17-641.png!MM-PL05111-S7238-B50-C-0260!image-2023-01-20-11-48-53-670.png!\'"", ""Comment 122: \'All are linked now:!image-2023-01-20-12-09-43-767.png!Additionally"", \'Comment 123: this PLR had message (screenshot below). I have resent technology and generated documents from application and ERP documents generated!image-2023-01-20-12-05-13-689.png!!image-2023-01-20-12-05-33-824.png!Those two:06331601230020633160123001I have generated documents for PLR in DHC\', \'Comment 124: JOs were generated\', ""Comment 125: IR+ and IR- have to be linked.\'"", ""Comment 126: \'Regarding VT-295"", ""Comment 127: we are investigating.Regards\'"", ""Comment 128: \'Regarding this error:!image-2023-01-20-12-48-55-844.png!We have found information about timeouts. I have restarted Erp Int. Please"", ""Comment 129: let me know if this error reoccurs.Regards\'"", \'Comment 130: ""Dziś generowałam dokumenty m.in dla tego PLRa 0633160123001\', ""Comment 131: id = \'83C4067F-FB7C-4E11-BA41-DBD8D06F3BC3\'!image-2023-01-20-13-08-35-850.png!W DHC pojawił sie tylko dokument JO-656/23/KBP{code:java}2023-01-20 13:00:10,473 [79] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.ProductionLotReports.ProductionLotReportProcessor [(null)] - ProductionLotReportProcessor execution started2023-01-20 13:00:10,520 [8] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.ProductionLotReports.GenerateJobOrder [(null)] - GenerateJobOrder execution started2023-01-20 13:00:10,520 [8] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.ProductionLotReports.GenerateJobOrder [(null)] - Started PLR Id: 83c4067f-fb7c-4e11-ba41-dbd8d06f3bc3 processing2023-01-20 13:00:10,567 [8] INFO Evolution.ErpIntegrator.IntegrationLibrary.Documents.ProductionLotReports.GenerateJobOrder [(null)] - Generating documents for PLR Id: 83c4067f-fb7c-4e11-ba41-dbd8d06f3bc32023-01-20 13:00:10,723 [8] INFO Evolution.ErpIntegrator.IntegrationLibrary.Documents.ProductionLotReports.GenerateJobOrder [(null)] - Generating Job Order for PLR Id: 83c4067f-fb7c-4e11-ba41-dbd8d06f3bc32023-01-20 13:00:10,723 [8] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.ProductionLotReports.GenerateJobOrder [(null)] - Generate JO by PLR data.2023-01-20 13:00:10,770 [Thread 8] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2019.LoginHelper [(null)] - Changing context to 3892023-01-20 13:00:11,332 [Thread 8] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2019.LoginHelper [(null)] - Contex changed to 3892023-01-20 13:00:13,082 [Thread 8] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.JobOrders.CdnXL2019JORepository [(null)] - JO Created: ID - 495164 [JO-656/23/KBP]2023-01-20 13:00:13,473 [8] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.JobOrders.CdnXL2019JORepository [(null)] - JO Element Created: ID - 521565 for new process 5036032023-01-20 13:00:13,864 [8] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.JobOrders.CdnXL2019JORepository [(null)] - Job order elemnt ID - 521565 process for item RB64080-B50-M added2023-01-20 13:00:14,114 [8] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.JobOrders.CdnXL2019JORepository [(null)] - Job order elemnt ID - 521565 ingredient RB64080-B50-M added2023-01-20 13:00:14,207 [8] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.JobOrders.CdnXL2019JORepository [(null)] - Job order elemnt ID - 521565 product RB64080-B50-M added2023-01-20 13:00:14,426 [8] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.JobOrders.CdnXL2019JORepository [(null)] - JO Closed: ID - 495164 (2816)2023-01-20 13:00:14,567 [8] INFO Evolution.ErpIntegrator.IntegrationLibrary.Documents.ProductionLotReports.GenerateJobOrder [(null)] - Generated JO ID - 495164 For PLR Id: 83c4067f-fb7c-4e11-ba41-dbd8d06f3bc3 - BY PLR2023-01-20 13:00:14,598 [8] INFO Evolution.ErpIntegrator.IntegrationLibrary.Documents.ProductionLotReports.GenerateJobOrder [(null)] - Generating Release for PLR Id: 83c4067f-fb7c-4e11-ba41-dbd8d06f3bc32023-01-20 13:00:14,598 [8] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.ProductionLotReports.GenerateJobOrder [(null)] - IR- Document generation disabled in configuration - skipped.2023-01-20 13:00:14,598 [8] INFO Evolution.ErpIntegrator.IntegrationLibrary.Documents.ProductionLotReports.GenerateJobOrder [(null)] - Generating Receipt for PLR Id: 83c4067f-fb7c-4e11-ba41-dbd8d06f3bc32023-01-20 13:00:14,598 [8] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.ProductionLotReports.GenerateJobOrder [(null)] - IR+ Document generation disabled in configuration - skipped.2023-01-20 13:00:14,692 [8] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.JobOrders.CdnXL2019JORepository [(null)] - JO Closed: ID - 495164 (4)2023-01-20 13:00:15,023 [8] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.JobOrders.CdnXL2019JORepository [(null)] - JO Closed: ID - 495164 (6)2023-01-20 13:00:17,140 [48] DEBUG Evolution.ErpIntegrator.Services.ERP.CdnXL.SoapERPService [(null)] - Recived Trade Document Create or Update message from trigger - 40929122023-01-20 13:00:18,209 [48] DEBUG Evolution.ErpIntegrator.Services.ERP.CdnXL.SoapERPService [(null)] - Recived Trade Document Create or Update message from trigger - 40929132023-01-20 13:00:18,974 [9] DEBUG Evolution.ErpIntegrator.Services.ERP.CdnXL.SoapERPService [(null)] - Recived Trade Document Create or Update message from trigger - 40929132023-01-20 13:00:19,350 [8] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.JobOrders.CdnXL2019JORepository [(null)] - JO Closed: ID - 495164 (7)2023-01-20 13:00:19,437 [8] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.JobOrders.CdnXL2019JORepository [(null)] - JO status invalid - expeced zamkniete"", \'Comment 132: was rozliczono w 50.0% (4)2023-01-20 13:00:19,437 [8] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.JobOrders.CdnXL2019JORepository [(null)] - JO status not changed properly - try to close again2023-01-20 13:00:19,450 [8] ERROR Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.JobOrders.CdnXL2019JORepository [(null)] - Error of type Evolution.ErpIntegrator.CdnXL.CdnXL2019.XLApiException has been thrown (XLZamknijZlecenieProd:6).API Name - XLZamknijZlecenieProdAPI Result - 6ERRORS:|Error while saving data in database (ZamknijZlecenieProd-6) at Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.JobOrders.CdnXL2019JORepository.InternalCloseDocument(JobOrder header\', \'Comment 133: DocumentStatus documentStatus) in C:\\\\\\\\TeamCity\\\\\\\\buildAgent\\\\\\\\work\\\\\\\\57a7e278b67a115c\\\\\\\\Evolution.ErpIntegrator\\\\\\\\CdnXL\\\\\\\\Evolution.ErpIntegrator.CdnXL.CdnXL2019\\\\\\\\Documents\\\\\\\\JobOrders\\\\\\\\CdnXL2019JORepository.cs:line 158 at Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.JobOrders.CdnXL2019JORepository.CloseDocument(JobOrder header\', \'Comment 134: DocumentStatus documentStatus) in C:\\\\\\\\TeamCity\\\\\\\\buildAgent\\\\\\\\work\\\\\\\\57a7e278b67a115c\\\\\\\\Evolution.ErpIntegrator\\\\\\\\CdnXL\\\\\\\\Evolution.ErpIntegrator.CdnXL.CdnXL2019\\\\\\\\Documents\\\\\\\\JobOrders\\\\\\\\CdnXL2019JORepository.cs:line 1132023-01-20 13:00:19,465 [8] ERROR Evolution.ErpIntegrator.IntegrationLibrary.Documents.ProductionLotReports.GenerateJobOrder [(null)] - Error of type Evolution.ErpIntegrator.CdnXL.CdnXL2019.XLApiException has been thrown (XLZamknijZlecenieProd:6).API Name - XLZamknijZlecenieProdAPI Result - 6ERRORS:|Error while saving data in database (ZamknijZlecenieProd-6) at Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.JobOrders.CdnXL2019JORepository.InternalCloseDocument(JobOrder header\', \'Comment 135: DocumentStatus documentStatus) in C:\\\\\\\\TeamCity\\\\\\\\buildAgent\\\\\\\\work\\\\\\\\57a7e278b67a115c\\\\\\\\Evolution.ErpIntegrator\\\\\\\\CdnXL\\\\\\\\Evolution.ErpIntegrator.CdnXL.CdnXL2019\\\\\\\\Documents\\\\\\\\JobOrders\\\\\\\\CdnXL2019JORepository.cs:line 158 at Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.JobOrders.CdnXL2019JORepository.CloseDocument(JobOrder header\', \'Comment 136: DocumentStatus documentStatus) in C:\\\\\\\\TeamCity\\\\\\\\buildAgent\\\\\\\\work\\\\\\\\57a7e278b67a115c\\\\\\\\Evolution.ErpIntegrator\\\\\\\\CdnXL\\\\\\\\Evolution.ErpIntegrator.CdnXL.CdnXL2019\\\\\\\\Documents\\\\\\\\JobOrders\\\\\\\\CdnXL2019JORepository.cs:line 139 at Evolution.ErpIntegrator.IntegrationLibrary.Documents.ProductionLotReports.GenerateJobOrder.OnExecute(Object data)2023-01-20 13:00:19,465 [8] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.ProductionLotReports.GenerateJobOrder [(null)] - PLR processing finished2023-01-20 13:00:19,465 [8] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.ProductionLotReports.GenerateJobOrder [(null)] - GenerateJobOrder execution finished2023-01-20 13:00:19,465 [79] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.ProductionLotReports.ProductionLotReportProcessor [(null)] - ProductionLotReportProcessor execution finished2023-01-20 13:00:25,285 [79] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor [(null)] - VehicleTicketProcessor execution started2023-01-20 13:00:25,410 [79] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor [(null)] - VehicleTicketProcessor execution finished{code}""\', ""Comment 137: \'Hello"", ""Comment 138: issue is still occurring !image-4!\'"", ""Comment 139: \'!image-2023-01-23-13-21-57-209.png!\'"", ""Comment 140: \'Hello,Thank you for your information. Regarding PLRs 0633160123002"", \'Comment 141: 0633160123001\', ""Comment 142: automatic generating documents is not configured for this production area. Documents need to be genrated manually!image-2023-01-23-13-26-21-002.png!\'"", ""Comment 143: \'Cześć:)[~piotr.chmielarski@kotrak.com]po wstępnej rozmowie z Pawłem Piechem"", \'Comment 144: przepinam na dev z prośbą o akceptację. Wygląda na to\', \'Comment 145: że coś tam dzieje się niedobrego\', \'Comment 146: a każdy kejs ma inny błąd. Tyle\', \'Comment 147: co udało nam się przeanalizować\', ""Comment 148: jest w tasku. Z góry Wielkie Dzięki:)\'"", ""Comment 149: \'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 150: \'hello"", ""Comment 151: thank you  we have reenabled the auto generate. new examples for the VT error message !image-5!\'"", ""Comment 152: \'Hello,As I mentioned before"", \'Comment 153: errors about missing quantity roots in Deliveries:>>the lack of a resource>> or the related delivery has dispatched,>> the intake may not have been done yet\', \'Comment 154: i.e. PLR not produced\', \'Comment 155: e.gRegarding error about ""SystemOutOfMemory Exception"">> we have verified and could see that ERP Int was opened 6 times - so they worked at the same time - documents were processed>> we have linked JOs and IR documents to PLRs>> since Monday JOs are processed corectly\', ""Comment 156: so in our opinion multiple opeed ERP Int could cause documents did not link..System out of memory should not appear unless erp int is open multiple times.Regards\'"", ""Comment 157: \'Why was ERP Integrator opened 6 times?\'"", ""Comment 158: \'VT 186 and 188 (KB) generated into the ERP (they have been invoiced) but they are now appearing as not generated in DHC. VT a432 (UR) has the same problem!image-6!!image-7!!image-8!!image-9!!image-10!\'"", ""Comment 159: \'!image-2023-02-14-08-12-19-967.png!\'"", ""Comment 160: \'Dla VT-432 SO!image-2023-02-14-08-26-47-548.png!DlaVT 186!image-2023-02-14-08-28-23-993.png!VT-188!image-2023-02-14-08-29-31-747.png!\'"", ""Comment 161: \'Regarding VT-188"", \'Comment 162: please make sure that there is correct SO clipped. The error comes from XL and means that either Source document - in this case SO-148 is in status buffer or executed. So the SOR% document cannot be generated. In fact\', ""Comment 163: to SO-148 there is SOR generated under SOR-167/23/KBP with the same quantity as in SO but is clipped to VT-241/1/202/KB what is visible on the screenshot of SOR document. This situation is to verify on your side.!image-2023-02-14-08-45-28-629.png!!image-2023-02-14-08-56-38-917.png!!image-2023-02-14-08-49-53-243.png!!image-2023-02-14-08-49-01-150.png!!image-2023-02-14-08-48-07-329.png!\'"", ""Comment 164: \'!image-2023-02-14-09-00-31-515.png!!image-2023-02-14-09-00-58-426.png!!image-2023-02-14-09-01-36-519.png!\'"", ""Comment 165: \'We have found more cases thanVT-432 and VT-186. It seems that initially documents were generated and clipped in DHC. But SOR documents have been unclipped but we do not now why. Maybe some process goes on database. We can also see that someone ore something pushed those VTs yesterday morning. It does not seem to by sync issue as this refers only to 8 documents. For now"", ""Comment 166: please let us know if we should clipped VTs to generated SOR document per list below:!image-2023-02-14-13-47-29-837.png!Regards\'"", ""Comment 167: \'Hello"", ""Comment 168: yes please clip the documents against the applicable VTS. \'"", ""Comment 169: \'Dear Thabile,Please"", ""Comment 170: check and verify now.Regards\'"", ""Comment 171: \'Hello"", \'Comment 172: thank you they are linked\', ""Comment 173: we appear to be having different issues everyday.  we are unable to cancel VT 456 (placed on hold) as it says SOR 729/23/PUR is linked to it. this document has been cancelled in the ERP. !image-11![^2023-02-16_8-26-16.mp4] _(370 kB)_\'"", ""Comment 174: \'!image-2023-02-16-10-47-18-434.png!!image-2023-02-16-10-49-49-515.png!\'"", ""Comment 175: \'Dear Thabile,Where do you see the error message that youare unable to cancel VT 456 {color:#0747a6}_(placed on hold) as it says SOR 729/23/PUR is linked to it._{color}{color:#172b4d}?{color}{color:#172b4d}Regards{color}\'"", ""Comment 176: \'!image-2023-02-16-11-05-54-920.png!!image-2023-02-16-11-07-22-679.png!\'"", ""Comment 177: \'[^dgs-8341.xlsx]\'"", ""Comment 178: \'Dear Thabile,Now you should be able to cancel VT"", ""Comment 179: please verify.\'"", ""Comment 180: \'Hello"", \'Comment 181: we\\\\\\\'re still experiencing the error for ""System out of memory"" can you tell us why the integrator would open itself multiple times? \\\'\', ""Comment 182: \'Hello"", ""Comment 183: we are still experiencing the JOs not linked to their corresponding PLR issue as well!image-12!\'"", ""Comment 184: \'!image-13!\'"", ""Comment 185: \'!image-2023-03-01-15-31-20-789.png|width=543,height=419!!image-2023-03-01-15-32-04-669.png|width=1166,height=345!\'"", ""Comment 186: \'Hi,I have linked IR + and IR - and JOs to PLRs. Still investigating why erp int is opening multiple time. We can see it has been shut down several times.Starting on Monday"", ""Comment 187: has anybody reset the Erp Int? Or was there the power outage?Regards\'"", ""Comment 188: \'Hello"", \'Comment 189: no one has\', ""Comment 190: no power failures either. according to IT server has been up for 17days (restart due to windows updates) \'"", ""Comment 191: \'Standardowe błędy:{code:java}ERRORS:|Missing quantity (failed to retrieve the item or the entire execution was forced). (DodajPozycje-17) - (4501010)   at Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.InternalDocuments.CdnXL2019InternalDocumentRepository.AddElement(Int32 xlDocumentId"", \'Comment 192: XLInternalDocumentElement xlElement) in C:\\\\\\\\TeamCity\\\\\\\\buildAgent\\\\\\\\work\\\\\\\\57a7e278b67a115c\\\\\\\\Evolution.ErpIntegrator\\\\\\\\CdnXL\\\\\\\\Evolution.ErpIntegrator.CdnXL.CdnXL2019\\\\\\\\Documents\\\\\\\\InternalDocuments\\\\\\\\CdnXL2019InternalDocumentRepository.cs:line 260   at Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.InternalReleases.CdnXL2019InternalReleaseRepository.CreateIRWithElements(InternalRelease internalRelease\', \'Comment 193: Boolean confirmDoc) in C:\\\\\\\\TeamCity\\\\\\\\buildAgent\\\\\\\\work\\\\\\\\57a7e278b67a115c\\\\\\\\Evolution.ErpIntegrator\\\\\\\\CdnXL\\\\\\\\Evolution.ErpIntegrator.CdnXL.CdnXL2019\\\\\\\\Documents\\\\\\\\InternalReleases\\\\\\\\CdnXL2019InternalReleaseRepository.cs:line 64   at Evolution.ErpIntegrator.IntegrationLibrary.Documents.ProductionLotReports.GenerateJobOrder.GenerateRelease(ProductionLotReport productionLotReport\', \'Comment 194: JobOrder jobOrder\', \'Comment 195: JobOrderElement element\', \'Comment 196: PLRDocuments documentMapping)2023-02-12 00:07:11,508 [9] ERROR Evolution.ErpIntegrator.IntegrationLibrary.Documents.ProductionLotReports.GenerateJobOrder [(null)] - Error of type Evolution.ErpIntegrator.CdnXL.CdnXL2019.XLApiException has been thrown (XLDodajPozycje:17).API Name - XLDodajPozycjeAPI Result - 17Flags - 13{code}{code:java}ERRORS:|Cannot find document header. (ZamknijDokument-3)   at Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.ExternalOrderTransactions.CdnXL2019ExternalOrderTransactionRepository.CloseDocument(XLExternalOrderTransaction document\', \'Comment 197: 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 198: 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 199: Boolean confirmDoc) in C:\\\\\\\\TeamCity\\\\\\\\buildAgent\\\\\\\\work\\\\\\\\57a7e278b67a115c\\\\\\\\Evolution.ErpIntegrator\\\\\\\\CdnXL\\\\\\\\Evolution.ErpIntegrator.CdnXL.CdnXL2019\\\\\\\\Documents\\\\\\\\SalesOrderReleases\\\\\\\\CdnXL2019SalesOrderReleaseRepository.cs:line 312023-02-12 00:07:56,311 [117] DEBUG Evolution.ErpIntegrator.DHC.DHC30.Database.DhcTransaction [(null)] - DHC transaction rollback staeted2023-02-12 00:07:56,311 [117] DEBUG Evolution.ErpIntegrator.DHC.DHC30.Database.DhcTransaction [(null)] - DHC transaction rollback finished2023-02-12 00:07:56,311 [117] 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}{code:java}ERRORS:|Transactions with this customer have been stopped. (NowyDokument-18)   at Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.ExternalOrderTransactions.CdnXL2019ExternalOrderTransactionRepository.CreateHeader(XLExternalOrderTransaction documentHeader) in C:\\\\\\\\TeamCity\\\\\\\\buildAgent\\\\\\\\work\\\\\\\\57a7e278b67a115c\\\\\\\\Evolution.ErpIntegrator\\\\\\\\CdnXL\\\\\\\\Evolution.ErpIntegrator.CdnXL.CdnXL2019\\\\\\\\Documents\\\\\\\\ExternalOrderTransactions\\\\\\\\CdnXL2019ExternalOrderTransactionRepository.cs:line 792023-02-12 00:13:56,381 [83] DEBUG Evolution.ErpIntegrator.DHC.DHC30.Database.DhcTransaction [(null)] - DHC transaction rollback staeted2023-02-12 00:13:56,381 [83] DEBUG Evolution.ErpIntegrator.DHC.DHC30.Database.DhcTransaction [(null)] - DHC transaction rollback finished2023-02-12 00:13:56,396 [83] 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 200: \'{code:java}2023-02-13 04:06:30,717 [16] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2019.LoginHelper [(null)] - Changing context to 272023-02-13 04:06:38,775 [1] DEBUG Evolution.ErpIntegrator.PlatformApplication.Application [(null)] - Started configuration of IoC container2023-02-13 04:06:38,993 [1] WARN  Evolution.ErpIntegrator.CdnXL.CdnXL2019.ErpVersionConfiguration [(null)] - Implementation for interface Evolution.ErpIntegrator.ERP.Interfaces.Attachments.IAttachmentRepository not found!2023-02-13 04:06:41,212 [1] DEBUG Evolution.ErpIntegrator.PlatformApplication.Application [(null)] - Finished configuration of IoC container2023-02-13 04:06:41,212 [1] DEBUG Evolution.ErpIntegrator.PlatformApplication.Application [(null)] - Started configuration of Platform Client2023-02-13 04:06:41,884 [1] DEBUG Evolution.ErpIntegrator.PlatformApplication.Application [(null)] - Resending exceptions2023-02-13 04:06:41,884 [1] DEBUG Evolution.ErpIntegrator.PlatformApplication.Application [(null)] - Finished configuration of Platform Client2023-02-13 04:06:42,181 [1] INFO  Evolution.ErpIntegrator.PlatformApplication.Application [(null)] - Running startup extension Evolution.ErpIntegrator.Extensions.DBTriggerCheck.DBTriggerCheckExtension2023-02-13 04:06:42,181 [1] INFO  Evolution.ErpIntegrator.PlatformApplication.Application [(null)] - Extension completed2023-02-13 04:06:42,181 [1] INFO  Evolution.ErpIntegrator.PlatformApplication.Application [(null)] - Starting in singe process mode.2023-02-13 04:06:42,197 [1] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2019.LoginHelper [(null)] - XL login attempt on user - ERPINT2023-02-13 04:06:46,280 [1] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2019.LoginHelper [(null)] - Set api version to - 201932023-02-13 04:06:46,280 [1] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2019.LoginHelper [(null)] - Set current context - 12023-02-13 04:06:46,280 [1] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2019.LoginHelper [(null)] - XL login"", ""Comment 201: session ID - 597550{code}!image-2023-03-02-08-13-35-430.png!\'"", ""Comment 202: \'Ten fragment pojawia się 3 razy"", ""Comment 203: jeszcze ok 1:30 i 16:30,14 lutego da razy!image-2023-03-02-08-14-54-332.png!\'"", ""Comment 204: \'!image-2023-03-02-09-14-30-809.png|width=1154,height=350!\'"", ""Comment 205: \'[^DGS-8341 uzasadnienie na retro.docx]\'"", ""Comment 206: \'[^DGS-8341 uzasadnienie na retro.docx]\'"", ""Comment 207: \'Please close this ticket"", ""Comment 208: and open the RCA for out of memory.\'"", ""Comment 209: \'RCA is underDGS-8756Regards\']""]\nRelated Issues:\n[\'DGS-8756\']\n\n### End'}"
691,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8340\n\n### Instruction:\nPlease help to check  VT-775/23. WO was closed without realization. And \r\nnothing on stock.\r\n\r\n**Note: Issue in Binh Dinh plant(ID 438) 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: \'Było reopen: !screenshot-1!  !screenshot-2! Messages: !screenshot-3!  !screenshot-4! !image-2023-01-18-16-15-18-612!!image-2023-01-18-16-16-36-800!\'"", \'Comment 4: ""Hello\', \'Comment 5: warehouse order has been reopened by User QUOCVUONG and next Closed without realization(also by QUOCVUONG) - last operations for WO.Can you ask why the user chose that?I know that the VT should be cancelled\', \'Comment 6: but in this case it\\\'s best to re-issue the document.We can change the status of this to canceled from database.""\', ""Comment 7: \'Hello"", ""Comment 8: any news about this case?Thank you and regards.\'"", ""Comment 9: \'you can close the ticket\']""]\nRelated Issues:\n[]\n\n### End'}"
692,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8339\n\n### Instruction:\nOn the dhvd02ap170 some labels are not being imported.\r\nThe recipe  115283 must be sent to the plant tonight. But in DHC the recipe remains in draft (version 25) because of the missing label.\r\n\r\nPlease check why the label is not being imported in DHH. I tried already by stopping and starting the autoimporter but that didn\'t help.\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Dear Wijnand,On my side I can see item linked correctly in DHC!image-2023-01-16-21-18-38-460.png!Recipe in DHC!image-2023-01-16-21-19-07-626.png!It is accepted and has label:!image-2023-01-16-21-19-36-233.png!Could you please verify? Maybe it had some delay in synchronisation.Regards\'"", ""Comment 3: \'It is also in plant Maasbracht!image-2023-01-16-21-28-04-885.png!\'"", ""Comment 4: \'DearWijnand,As taskDGS-8337 has been resolved"", \'Comment 5: please\', ""Comment 6: confirm if we can close this task.Regards\'"", ""Comment 7: \'Hello,We are closing this task as we haven’treceivedany replyfromyouforalong time. What is more"", \'Comment 8: it has been confirmed in task DGS-8337 that all is working fine now. If the issueappearsagain\', ""Comment 9: please raise another task.Regards\']""]\nRelated Issues:\n[]\n\n### End'}"
693,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8338\n\n### Instruction:\nCould you please add the column ""Document Number"" in the round category Eggs in the LAS?\r\n\r\nWe need to present the ERP number in here.\n\n### Response:\n[""Comment 1: [\'Added Document Number column to view.!image-2023-01-18-12-11-48-308.png!\'"", ""Comment 2: \'We need the documents numbers in the LAS to be filled in the category expenses as well. Now this whole column is empty.\']""]\nRelated Issues:\n[]\n\n### End'}"
694,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8337\n\n### Instruction:\nItem 115283 is in DHC but does not go to DHP.\r\nIt is needed urgently in DHP Maasbracht, but I can\'t find it in any other DHP.\r\n\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 2: ""Hello,Please check the DHH Holding.Don\\\'t show in DHH items.Look screenshot!image-2023-01-16-17-18-02-445.png!Regards.""\', ""Comment 3: \'Hi Adrian,somehow it is in DHH now AND in DHP.This ticket can be closed.Thanks for the support.\']""]\nRelated Issues:\n[]\n\n### End'}"
695,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8336\n\n### Instruction:\nHi\r\n\r\nWe are experiecing unusual slowdown on _Production lot_ screen in Rio Claro\'s DHP 2.5 server.\r\nWe just restarted both servers: At first the database server, then we restarted application server, but without success.\r\n\r\nCould you please check it?\r\n\r\nThank you\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'I checked the indexes,and i made rebuild and update stats"", ""Comment 4: please verify.\'"", \'Comment 5: ""Hi PiotrNow it\\\'s fine! It\\\'s taking the usual time to load the screen.You can close this taskThank you very much""\', ""Comment 6: \'Hello MaiconThank you for confirmation.\']""]\nRelated Issues:\n[]\n\n### End'}"
696,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8335\n\n### Instruction:\nDzień dobry,\r\n\r\nw zeszłym tygodniu był problem z zaksięgowaniem wyciągu - zgłoszenie do zamknięcia - zostało ono zrealizowane zdalnie przez Monikę Biśta. \r\n\r\n\r\n\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Ticket has been closed.\']""]\nRelated Issues:\n[]\n\n### End'}"
697,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8334\n\n### Instruction:\nPlease remove the users:\r\n\r\nPerquin en Veldkamp from the automatic responce\r\n\n\n### Response:\n[""Comment 1: [\'This is for : Premix\'"", ""Comment 2: \'!image-1!\'"", ""Comment 3: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 4: \'Hello,Issue is resolved - Users deactivated.Best Regards,Łukasz Stępień\']""]\nRelated Issues:\n[]\n\n### End'}"
698,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8333\n\n### Instruction:\nUser can’t see whether the SO’s :  SO-396+397/09/2022 are booked out of stock  or if they are cancelled in CDN.\r\nThey should have been booked out of stock in order to create invoices for De Heus Poland, but so far, there were no invoices\r\n( material was physically there and has been loaded, seen transport paper)\r\nHow can it be invoiced?\r\n  \r\n\r\n\r\n \n\n### Response:\n[""Comment 1: [\'!image!!image-1!!image-2!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 3: ""It\\\'s about restoring these orders in XL and manual execution from the XL level or what are the expectations for the task? The status in the GUI is visible. Canceled as mentioned in the task. !screenshot-1! Regards.""\', ""Comment 4: \'Hello"", ""Comment 5: any news about this case?Thank you and regards.\'"", ""Comment 6: \'According to me is only one correct.I Have asked the user what the meaning exactly is. \'"", ""Comment 7: \'Comment in wrong ticket\'"", ""Comment 8: \'Ticket can be closed\']""]\nRelated Issues:\n[]\n\n### End'}"
699,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8332\n\n### Instruction:\nOrders and shipping notices for this customer often don\'t arrive in the factory. But after some investigations it seems that the SN isn\'t in DHP, for example L000105355.\r\nSales Order SO000052655 is in DHP though and the Shipping Notice is in DHC also.\r\nCan you please check what is wrong so we can fix this?\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 2: "" !screenshot-1! 2023-01-16 12:56:39.260{code:java}  FROM [DHCService_NL_AS400_PROD].[dbo].[ShippingNoticeExportInfoes]  where EntityId=\\\'0B43E530-3C45-4BEC-9FBB-E668E14A2889\\\'  FROM [DHCService_NL_AS400_PROD].[dbo].[Orders]    where ForeignDocumentNumber in(\\\'SO000052660\\\')  FROM [DHCService_NL_AS400_PROD].[dbo].[Addresses]  where BusinessPartnerId=\\\'C9F0FDA3-A541-43F7-9A63-21831B7403B2\\\'{code}""\', ""Comment 3: \'For this order the address is wrongly associated with BP (order SO000052660 for the main BP and payer)Correct this data in DHC?\'"", ""Comment 4: \'Could you please confirm if we can close this task?Regards\'"", \'Comment 5: ""Hi Piotr\', \'Comment 6: no please don\\\'t close this task yet. I need as example and I\\\'m not sure if this one is correct in Milas and we need to change it there. But it has low priority for us now.""\', \'Comment 7: ""Hi Theo\', \'Comment 8: thank you for information -  so we\\\'ll wait for an answer.Regards.""\', ""Comment 9: \'Hello,can I count on an update of this ticket?Thank you and regards.\'"", ""Comment 10: \'Hello,We are closing this task as we haven’treceivedany replyfromyouforalong time.Regards\']""]\nRelated Issues:\n[]\n\n### End'}"
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: \'[~aleksandra.masternak@kotrak.com]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 [~Eric.quang@deheus.com],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 [~Eric.quang@deheus.com],Do you have any integration with a PCS system in this plant?\'"", ""Comment 73: \'Dear [~Eric.quang@deheus.com],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: ""[~mbovene@deheus.com]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: \'[~mbovene@deheus.com],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: ""[~mbovene@deheus.com],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}[~grzegorz.materla@kotrak.com]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: \'[~mbovene@deheus.com],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: \'[~mbovene@deheus.com]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 -> *PI*MAS 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: \'[~grzegorz.materla@kotrak.com] - 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: \'[~mbovene@deheus.com]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: \'[~mbovene@deheus.com],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: \'[~mbovene@deheus.com],next sector PAS with FS print is ready to tests.Best regards,Grzegorz\'"", ""Comment 62: \'[~mbovene@deheus.com],next sector OPPAS with FS print is ready to tests.Best regards,Grzegorz\'"", ""Comment 63: \'[~mbovene@deheus.com],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: \'[~mbovene@deheus.com]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) <jira@kotrak.com>   *Verzonden:* vrijdag 13 januari 2023 12:26  *Aan:* Jong"", ""Comment 5: Christine de <CJong@deheus.com>  *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: \'[~tomasz.zygon@kotrak.com]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: \'[~tomasz.zygon@kotrak.com]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) <jira@kotrak.com>   *Verzonden:* dinsdag 7 februari 2023 11:32  *Aan:* Jong\', ""Comment 21: Christine de <CJong@deheus.com>  *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 <AKucharska@deheus.com> *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: [monika.bista@kotrak.com|mailto:monika.bista@kotrak.com]*Kotrak S.A.*Parczewskiego 2540-582 KatowicePoland*tel./phone:* (+48 32)35 12700[www.kotrak.com|https://kotrak.com/]*Certified ISO 9001:2015*++*Sąd Rejonowy / District Court* *Katowice-Wschód w Katowicach* *Wydział VIII Gospodarczy KRS\', \'Comment 7: nr KRS*: 0000704357*NIP*: 954-24-96-628 *Regon:* 277683949*Kapitał zakładowy / Share capital:* 1.052.700,00 zł\', \'Comment 8: opłacony w całości / paid in full*Lokalizacje / 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: ""[~tomasz.zygon@kotrak.com]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 [~mbovene@deheus.com],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) <jira@kotrak.com>   *Verzonden:* donderdag 12 januari 2023 15:05  *Aan:* Dam\', ""Comment 7: Nancy van <NDam@deheus.com>  *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: ""[~mbovene@deheus.com],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-W005CB*Thank you!image!!image-1!\'"", ""Comment 6: \'Hi AgnieszkaHere the evidence for SU* *83-W09QFA** *83-W09R5T** *83-W09GP5*Thank 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,RIJSBERGEN*Payer:*>> code:811338>> name:P. AMMERLAAN ETTEN-LEUR B.V.>> address:BREEDSCHOTSESTRAAT 33,4891PK,RIJSBERGEN*Target:***>> 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: [aleksandra.przybylek@kotrak.com|mailto:aleksandra.przybylek@kotrak.com]also please"", ""Comment 66: if it is possible access for user piotr.gaczorek@kotrak.comRegards\'"", ""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 Piotr.Gaczorek@apac.corp.deheus.com !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 fajri.agusman@deheus.com\'"", ""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: \'[~piotr.gaczorek@kotrak.com] 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: \'[~maciej.dobrzanski@kotrak.com]Maciek"", \'Comment 53: sprawdziłam zgodnie z Twoimi wytycznymi\', ""Comment 54: ale może coś dojrzysz Twoim mądrzejszym okiem :)\'"", ""Comment 55: \'[~aleksandra.przybylek@kotrak.com] 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: \'[~maciej.dobrzanski@kotrak.com]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 (hgorp@deheus.com) - 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: \'*MASBE*IF 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: \'*MASNL*IF 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 [~mbovene@deheus.com]\', \'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: \'[~mbovene@deheus.com]"", \'Comment 7: according to your answer\', ""Comment 8: we will add a column with one value.Best regards,Grzegorz\'"", ""Comment 9: \'[~mbovene@deheus.com] 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: \'[~TDankers@deheus.com],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: ""[~TDankers@deheus.com],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: \'[~aleksandra.przybylek@kotrak.com],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: \'[~aleksandra.przybylek@kotrak.com] po rozmowie z dev podjąłem decyzję że fix bedzie w 8.5\'"", ""Comment 7: \'[~maciej.dobrzanski@kotrak.com]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: ""[~mbovene@deheus.com]\', \'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: \'[~mbovene@deheus.com]"", ""Comment 7: good. Could you send me the original file? Because I can not use picture in SQL query.\'"", ""Comment 8: \'[~mbovene@deheus.com]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: \'[~mbovene@deheus.com]"", ""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: \'[~mbovene@deheus.com],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: \'[~mbovene@deheus.com]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 <NDam@deheus.com>; Geerenstein\', \'Comment 30: Dirco van <DGeerenstein@deheus.com>; Jong\', \'Comment 31: Christine de <CJong@deheus.com>; Meijer\', \'Comment 32: Thelma <TMeijer@deheus.com>; Geijtenbeek\', \'Comment 33: Bert <BGeijtenbeek@deheus.com>; Broek\', \'Comment 34: Bessel van den <bbroek@deheus.com>; Verdam\', \'Comment 35: Anja <AVerdam@deheus.com>; Reimerink\', \'Comment 36: Rick <RReimerink@deheus.com>; Visser\', \'Comment 37: Oscar <OVisser@deheus.com>; Groot\', \'Comment 38: Erik de <EGroot@deheus.com>; Driesens\', \'Comment 39: Steffen <SDriesen@deheus.com>; Huibers\', \'Comment 40: Koen <KHuibers@deheus.com>""\', \'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[~mbovene@deheus.com]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: ""[~tomasz.zygon@kotrak.com]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: \'[~CJong@deheus.com]"", \'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) <jira@kotrak.com>   *Verzonden:* woensdag 4 januari 2023 12:57  *Aan:* Jong\', ""Comment 7: Christine de <CJong@deheus.com>  *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: \'[~CJong@deheus.com]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) <jira@kotrak.com>   *Verzonden:* woensdag 4 januari 2023 13:31  *Aan:* Jong"", ""Comment 11: Christine de <CJong@deheus.com>  *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: \'[~CJong@deheus.com]all data has been migrated into Intense. You can feel free to test it.\'"", ""Comment 13: \'[~CJong@deheus.com]"", ""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) <jira@kotrak.com>   *Verzonden:* donderdag 12 januari 2023 14:24  *Aan:* Jong\', ""Comment 17: Christine de <CJong@deheus.com>  *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 [~CJong@deheus.com],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 [~RvanRooyen@deheus.com],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.[~przemyslaw.przybyszewski@kotrak.com]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: \'[~agnieszka.januszewska@kotrak.com]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: \'[~mberbert@deheus.com]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: \'[~mberbert@deheus.com]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 [~lalmeida1@deheus.com]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) <jira@kotrak.com>   *Verzonden:* dinsdag 3 januari 2023 12:28  *Aan:* Jong\', ""Comment 6: Christine de <CJong@deheus.com>  *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 it*How 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'}"
800,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8231\n\n### Instruction:\nItem 967337 (Premix Veghel, factory 014) is linked in DHC to bag item code (B25).\r\n\r\nPlease relink to bulk item code.\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: \'But this is linked correctrly. Please"", ""Comment 4: verify!image-2023-01-03-07-53-44-091.png!\'"", ""Comment 5: \'Ok. Looks like someone did it in the meantime.Thank you.\']""]\nRelated Issues:\n[]\n\n### End'}"
801,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8230\n\n### Instruction:\nDzień dobry, \r\n\r\nproszę o informację dotyczącą poniższego zagadnienia:\r\n\r\n""Czy\xa0Optima posiada funkcję, dzięki której będziemy mogły sprawdzić przedawnienia urlopów wypoczynkowych?\r\n\r\nPozdrawiam\r\nPaulina Świątczak""\n\n### Response:\n[""Comment 1: [\'In system there is a standard printout where you can check how many leave days left on particular day. PLease tell us if it is sufficient solution for you?!image-2023-01-02-16-31-26-700.png!!image-2023-01-02-16-33-31-538.png!\'"", ""Comment 2: \'Dzień dobry"", \'Comment 3: poniżej informacja od Pauliny: ""Dziękuję za informację o zestawieniu\', \'Comment 4: ale to jeszcze nie jest to.Mamy pracownika\', \'Comment 5: któremu przedawnił się urlop\', \'Comment 6: poniżej screen.Chodziło mi bardziej o to\', \'Comment 7: by system pilnował tego okresu\', \'Comment 8: w momencie przedawnienia urlopu wypoczynkowego stworzył np. wiersz zaznaczony innym kolorem pod danym limitem urlopowym. By to było widoczne w limitach.""!obraz!\\\'\', ""Comment 9: \'Czy miałoby to działać w poniższy sposób:Zgodnie z art. 161 Kodeksu pracy pracodawca jest obowiązany udzielić pracownikowi urlopu w tym roku kalendarzowym"", \'Comment 10: w którym pracownik uzyskał do niego prawo. Urlop niewykorzystany do końca roku staje się urlopem zaległym\', ""Comment 11: którego należy udzielić pracownikowi najpóźniej do 30 września następnego roku kalendarzowego (art. 168 Kodeksu pracy).Czy w jakiś inny? Jaki?\'"", ""Comment 12: \'Czy miałoby to działać w poniższy sposób:Zgodnie z art. 161 Kodeksu pracy pracodawca jest obowiązany udzielić pracownikowi urlopu w tym roku kalendarzowym"", \'Comment 13: w którym pracownik uzyskał do niego prawo. Urlop niewykorzystany do końca roku staje się urlopem zaległym\', ""Comment 14: którego należy udzielić pracownikowi najpóźniej do 30 września następnego roku kalendarzowego (art. 168 Kodeksu pracy).Czy w jakiś inny? Jaki?\'"", ""Comment 15: \'czy zgłoszenie będzie kontynuowane?\'"", ""Comment 16: \'Informacja od zglaszajacegoTaki komunikat może pokazywać się w momencie wejścia w limity u danego pracownika.System powinien wyświetlić informację „Przekroczono limit!” a pod spodem komunikat z poniższej wiadomości.Tak to widzę. \'"", ""Comment 17: \'Tak ale po jakich parametrach system ma traktować urlop jako przekroczony?Czy miałoby to działać w poniższy sposób:Zgodnie z art. 161 Kodeksu pracy pracodawca jest obowiązany udzielić pracownikowi urlopu w tym roku kalendarzowym"", \'Comment 18: w którym pracownik uzyskał do niego prawo. Urlop niewykorzystany do końca roku staje się urlopem zaległym\', ""Comment 19: którego należy udzielić pracownikowi najpóźniej do 30 września następnego roku kalendarzowego (art. 168 Kodeksu pracy).Czy w jakiś inny? Jaki?\'"", ""Comment 20: \'Any news ?? Paulina Swiatczak send to You mail with information\'"", ""Comment 21: \'Yes I already send her additional questions. \'"", ""Comment 22: \'From: Świątczak Paulina <pswiatczak@deheus.com> Sent: Thursday"", \'Comment 23: February 23\', \'Comment 24: 2023 10:19 AMTo: Monika Biśta <monika.bista@kotrak.com>Subject: RE: Przedawnienie urlopuPani Moniko,Możemy to zrobić na oknie informacji bieżących.  Pozdrawiam,Paulina Świątczakspecjalista ds. administracji płac \\\\t+48 532 519 504pswiatczak@deheus.com www.deheus.pl W tytułach wiadomości stosuję regułę ARDI: A – proszę o akcję\', \'Comment 25: działanie;    R – proszę o recenzję\', \'Comment 26: reakcję;    D – proszę o decyzję;    I – informuję                     \\\\tDe Heus Sp. z o. o.   ul. Lotnicza 21B   99–100 Łęczyca   tel.: 24 721 04 00   fax: 24 721 04 04REGON: 011917655   NIP: 526-13-06-893   wysokość kapitału zakładowego: 22 141 000.00 zł nr KRS: 0000060991   Sąd Rejonowy dla Łodzi-Śródmieścia w Łodzi XX Wydział KRSTreść tej informacji może być poufna\', \'Comment 27: w związku z czym powinna trafić bezpośrednio do rąk adresata. Jakiekolwiek jej ujawnianie\', \'Comment 28: rozpowszechnianie\', ""Comment 29: bądź kopiowanie jest zabronione.\'"", ""Comment 30: \'From: Monika Biśta Sent: Tuesday"", \'Comment 31: February 28\', \'Comment 32: 2023 2:56 PMTo: Świątczak Paulina <pswiatczak@deheus.com>Subject: RE: Przedawnienie urlopuDzień dobry\', \'Comment 33: Niestety nie udało się skorzystać z Informacji Bieżących. Dodałam to w formie raportu z poziomu listy pracowników. Dałam sortowanie od tych którym pozostaje najwięcej z zeszłego roku. Proszę o informację czy jest ok czy coś do zmiany. Pozdrawiam / Best regards,Monika Biśta mobile: +48 538 212 162tel.: +48 32 35 12 721e-mail: monika.bista@kotrak.com     Kotrak S.A.Parczewskiego 2540-582 KatowicePoland tel./phone: (+48 32) 35 12 700www.kotrak.comCertified ISO 9001:2015Sąd Rejonowy / District Court Katowice-Wschód w Katowicach Wydział VIII Gospodarczy KRS\', \'Comment 34: nr KRS: 0000704357NIP: 954-24-96-628 Regon: 277683949Kapitał zakładowy / Share capital: 1.052.700,00 zł\', \'Comment 35: opłacony w całości / paid in fullLokalizacje / Locations: Kraków\', \'Comment 36: Łódź\', \'Comment 37: Warszawa\', \'Comment 38: Opole\', \'Comment 39: Bielsko-Biała\', \'Comment 40: Gdańsk\', ""Comment 41: London\'"", ""Comment 42: \'ThanksTask to close\']""]\nRelated Issues:\n[]\n\n### End'}"
802,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8229\n\n### Instruction:\nItem 967337 (Premix Veghel, factory 014) is linked in DHC to bag item code (B25).\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Please relink to bulk item code\'"", ""Comment 3: \'!image-1!\'"", ""Comment 4: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 5: ""poprzedni baseitemid=\\\'6A0F95CF-0CD6-450C-81D5-B2C98AF65A8A\\\'""\', ""Comment 6: \'Please verify linking was fix.But now you need to send agaian recipes the old one will not work properly!image-2023-01-02-16-56-04-218.png!\'"", ""Comment 7: \'Seem to be oke!image-2!\']""]\nRelated Issues:\n[]\n\n### End'}"
803,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8228\n\n### Instruction:\nWM-84/01/23/VP is not processed in DHC and so it is not processed in the ERP. How can I check the reason for it being not processed and how to fix it? This will prevent lot reports from failing, but I can;t see anything in the logging so it\'s unclear how to fix\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: \'2023-01-02 19:44:53,992 [15] ERROR Evolution.ErpIntegrator.CdnXL.CdnXL2016.Documents.WarehouseMovements.CdnXL2016WarehouseMovementReleaseRepository [(null)] - Error occurred - document was not deletedError of type Evolution.ErpIntegrator.CdnXL.CdnXL2016.XLApiException has been thrown (XLZamknijDokument:3).API Name - XLZamknijDokumentAPI Result - 3ERRORS:|Cannot find document header. (ZamknijDokument-3) at Evolution.ErpIntegrator.CdnXL.CdnXL2016.Documents.ExternalOrderTransactions.CdnXL2016ExternalOrderTransactionRepository.CloseDocument(XLExternalOrderTransaction document"", \'Comment 4: DocumentStatus status) in C:\\\\\\\\TeamCity\\\\\\\\buildAgent\\\\\\\\work\\\\\\\\57a7e278b67a115c\\\\\\\\Evolution.ErpIntegrator\\\\\\\\CdnXL\\\\\\\\Evolution.ErpIntegrator.CdnXL.CdnXL2016\\\\\\\\Documents\\\\\\\\ExternalOrderTransactions\\\\\\\\CdnXL2016ExternalOrderTransactionRepository.cs:line 527 at Evolution.ErpIntegrator.CdnXL.CdnXL2016.Documents.WarehouseMovements.CdnXL2016WarehouseMovementReleaseRepository.CloseDocument(XLWarehouseMovementRelease header\', \'Comment 5: DocumentStatus status) in C:\\\\\\\\TeamCity\\\\\\\\buildAgent\\\\\\\\work\\\\\\\\57a7e278b67a115c\\\\\\\\Evolution.ErpIntegrator\\\\\\\\CdnXL\\\\\\\\Evolution.ErpIntegrator.CdnXL.CdnXL2016\\\\\\\\Documents\\\\\\\\WarehouseMovements\\\\\\\\CdnXL2016WarehouseMovementReleaseRepository.cs:line 131 at Evolution.ErpIntegrator.CdnXL.CdnXL2016.Documents.WarehouseMovements.CdnXL2016WarehouseMovementReleaseRepository.CreateDocumentWithElements(XLWarehouseMovementRelease warehouseMovementRelease\', ""Comment 6: Boolean confirmDoc) in C:\\\\\\\\TeamCity\\\\\\\\buildAgent\\\\\\\\work\\\\\\\\57a7e278b67a115c\\\\\\\\Evolution.ErpIntegrator\\\\\\\\CdnXL\\\\\\\\Evolution.ErpIntegrator.CdnXL.CdnXL2016\\\\\\\\Documents\\\\\\\\WarehouseMovements\\\\\\\\CdnXL2016WarehouseMovementReleaseRepository.cs:line 512023-01-02 19:44:53,992 [15] DEBUG Evolution.ErpIntegrator.DHC.DHC30.Database.DhcTransaction [(null)] - DHC transaction rollback staeted2023-01-02 19:44:53,992 [15] DEBUG Evolution.ErpIntegrator.DHC.DHC30.Database.DhcTransaction [(null)] - DHC transaction rollback finished2023-01-02 19:44:53,992 [15] ERROR Evolution.ErpIntegrator.CdnXL.CdnXL2016.Transactions.XLTransaction [(null)] - XL rollback error - possibly no transactionError of type Evolution.ErpIntegrator.CdnXL.CdnXL2016.XLApiException has been thrown (XLTransakcja - Rollback:-1).API Name - XLTransakcja - RollbackAPI Result - -1\'"", ""Comment 7: \'Po odlokowaniu dokumentu komunikat o braku stanu\'"", \'Comment 8: ""select * from cdn.tranag where TrN_gidnumer=2868328select cdn.nazwaobiektu (trn_gidtyp,trn_gidnumer,1,2) from cdn.tranag where trn_gidnumer=2868328select  FROM [Evolution_DHCountry].[dbo].[WarehouseMovementElements] where WarehouseMovementId=\\\'A5AFDAE6-3115-4D39-9BD9-5E4647232157\\\'""\', ""Comment 9: \'deliveryid=312DCA91-5148-45FB-A3AD-78A9FD851D41\'"", ""Comment 10: \'At fisrt there some ir+ document that was blocked/ invalid in ERPXLAfter fixing that there was error about missing quantity for item 21079"", ""Comment 11: it was because this wm was linked to some old delievery that was already released.!image-2023-01-03-17-54-56-136.png!I removed that linkin and then generated the documents.!image-2023-01-03-17-55-27-661.png!\'"", \'Comment 12: ""Thanks\', \'Comment 13: but as you can see there are more WM\\\'s not generated: So what I\\\'m looking for is some kind of work instruction so that we can correct those that fail. Is that available?""\', \'Comment 14: ""update [Evolution_DHCountry].[dbo].[WarehouseMovementElements] set deliveryid=nullwhere WarehouseMovementId in (\\\'5A11C86C-B36E-4D22-9558-B92CEB64331D\\\'\', \'Comment 15: \\\'99100D53-C8A8-4951-8546-0E43A2D0A819\\\')""\', ""Comment 16: \'Hello,In this task we have focused on clearingandunblocking the process.You mentioned only 1 number.I found other 2 WM from this year and both were related for that same delivery. : 80/01 and 81/02I remove information about delivery idAbout where and how to check the error:use generate after choosing the WMthen if no documents were created check the ERPintegrator log file!image-2023-01-09-08-34-26-698.png!If in log for the moment when you choose generate you have informration about missing quantity verify in erp xl if quantity for that Item in the same warehouse.If there is not enough recources so you need to create and fixed that from ERPXL ( erp xl users know how to do that)If there is enough recources like in case of item21079the problem is that delivery was executed by other document like in ERPXL there is this document IR - 148/11/2022( this document was not generated by erp int)About missing information visable from DHC application to add that please create a GDC task.\'"", ""Comment 17: \'Please close this ticket"", ""Comment 18: thanks for your help\']""]\nRelated Issues:\n[]\n\n### End'}"
804,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8227\n\n### Instruction:\nWszystkie silosy poniżej 10 tyś. Oznaczone kolorem zielonym do zmiany (zakładka pozostałe gatunki-k.aktywni + Drób-k.aktywni).\r\n\r\nProśba o przekazanie do Moniki Biśty.\n\n### Response:\n[""Comment 1: [\'[^SILOSY GP 09.09.2022.xlsx] _(606 kB)_\'"", ""Comment 2: \'Hello,Kindly approve lowering priority of this task to P2 as P1 issues are only those with a critical or a blocking impact on business processes . This seems not to be the case in this issue so we suggest decreasing the issue priority.Regards\'"", ""Comment 3: \'My bad"", ""Comment 4: we can set it even as P3.\'"", ""Comment 5: \'Data has been corrected. PLease verify and give us feedback\'"", ""Comment 6: \'Thanks"", ""Comment 7: task to close.\']""]\nRelated Issues:\n[]\n\n### End'}"
805,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8226\n\n### Instruction:\nthe material was at stock in Moerdijk and is / has been loaded for Ukraine the last months, even today.\r\n\r\nPlease create full sor’s so invoicing can take place.\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'!image-1!\'"", ""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-02-15-24-52-682.png!\'"", ""Comment 5: \'Twr_GIDNumer=2208\'"", ""Comment 6: \'!virtu.PNG|thumbnail! !source_warehouse.PNG|thumbnail!\'"", \'Comment 7: ""According to message there is not enough stock for item XS00102.Stock are for warehouse Virtu but the order ( so -110/08/2022) has as source order set warehouse \\\'ex\\\'In this situoation please create warehouse movements from Virtu to EX\', \'Comment 8: for that item then check if the stock is in correct magazine and try again to genarate the SOR.!image-2023-01-02-16-32-34-615.png!!virtu.PNG!""\', ""Comment 9: \'May we close the task?\'"", ""Comment 10: \'Not yet\'"", ""Comment 11: \'How can we help"", ""Comment 12: is any information unclear?\'"", ""Comment 13: \'tu nie zrobili nic na towarze"", \'Comment 14: zadnego przesuniecia\', ""Comment 15: nic,\'"", ""Comment 16: \'It was on stock. Even in the allocation list and is used in SO and should be booked out off stock.Can you do this?The warehouse can not be changed. Should be done by intake?\'"", \'Comment 17: ""[^wmrmanual.pdf]About  It was on stock.But today and when you tried to create a sor it is not on right warehouse,That\\\'s whyyou got a mesage with information about missing stock and I send you the screenshoot and explanation.I also verify it again 20.01.2023\', \'Comment 18: if anyone did something with stock for that item on that WAREHOUSE.Today I checked again this stock lagain ,Go to accounting and look for items list and open details for that item!image-2023-01-30-15-14-06-174.png!As you can see there no stock for WAREHOUSE named EX.So please create the WMR documents\', \'Comment 19: I can see that documents like that where created before by ERPXL users.Like this one:!image-2023-01-30-15-38-29-435.png!I also add manual in english how to add WMR+ and WMR- documents\', \'Comment 20: !image-2023-01-30-15-38-29-435!""\', ""Comment 21: \'I am wauiting off responce off the requester\'"", ""Comment 22: \'May we close the task?\'"", ""Comment 23: \'close the ticket\']""]\nRelated Issues:\n[]\n\n### End'}"
806,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8225\n\n### Instruction:\nGood afternoon,\r\n\r\nPlease, would you so kind to create an openingsbalance for item: 303895-Z20 with a quantity of 3000 kg for plant Andel (pallets)\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: \'Dear Gerard,Please"", ""Comment 3: verify.Regards!image-2023-01-02-13-59-11-288.png!\'"", ""Comment 4: \'Dear Aleksandra,Thanks"", ""Comment 5: please close this ticket.Kind regards,Gerard\']""]\nRelated Issues:\n[]\n\n### End'}"
807,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8224\n\n### Instruction:\nClosed accounting period - needs to be opened again. \r\nThe accounting period was closed by mistake. \n\n### Response:\n[""Comment 1: [\'Zgłoszone telefonicznie\'"", ""Comment 2: \'The issue has been done and closed.\']""]\nRelated Issues:\n[]\n\n### End'}"
808,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8223\n\n### Instruction:\nVT-1903/12/22 is not arriving in DHC: After resending I see it in the logs but it seems not to be processed and so it is not send back to Milas, can you check?\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'I can see that VT and DHCPlease check?!image-2023-01-02-13-43-57-545.png!\'"", ""Comment 3: \'what was wrong then? or did I miss it somehow?\'"", ""Comment 4: \'Hard to say"", ""Comment 5: from what I can see it has Create Date :2022-12-30 11:06:49.477Is the notification closed at this point?\'"", ""Comment 6: \'Please close this ticket\']""]\nRelated Issues:\n[]\n\n### End'}"
809,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8222\n\n### Instruction:\nPlease can you cancel WD-3296/12/22 from this warehouse order? It blocks closing the warehouse order. This is a known DHP issue that occurs when a user selects a pallet and after that clicks on dismiss instead of save.\r\n\n\n### Response:\n[""Comment 1: [\'!afbeelding!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Hi Thomas,Please"", ""Comment 4: try now.Regards\'"", ""Comment 5: \'Thanks! you can close the ticket\'"", ""Comment 6: \'Thank you\'"", ""Comment 7: \'Hello"", ""Comment 8: this incident is related to this request GDC-588.\']""]\nRelated Issues:\n[\'DAP-13109\']\n\n### End'}"
810,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8221\n\n### Instruction:\nDOC-ID 81567\xa0(SI000044457) is duplicated on Financial Statement\r\n\r\nRound ID 30498\r\n\r\nFinancial Statement ID 81559\r\n\r\n\xa0\n\n### Response:\n[""Comment 1: [\'!image-2023-01-02-11-25-19-060!\'"", ""Comment 2: \'Do sprawdzenia selecty na FS i na Rundzie.Wygląda na to"", \'Comment 3: że na Rundzie jest ok\', ""Comment 4: a na FS jest zduplikowane i jest niepoprawnie.\'"", \'Comment 5: ""I looked into Relation Table and I don\\\'t see that type of relation\', ""Comment 6: so I have a question about how we should handle it.[https://app.box.com/file/1002580990454?s=kf5ux29gz5g5k2ykm5a6fz47a75n7741]In relation table we have Sales Invoices with Regular type for Round Category = Expeneses which are generated from Purchase Invoice - column \'J\' in Excel file. Until now we didn\'t differs that SI Regular for Expenses was generated from other document or no"", \'Comment 7: so that kind of SI (not generated from PI\', ""Comment 8: not like scenario in \'J\' column) were visible on the Round and Financial statement (however we have some inconsistency between Round and Financial statement).Should that kind of Sales Invoices be visible on Round"", \'Comment 9: Financial Statement\', \'Comment 10: Saldo to Pay and treated also like Sales Invoices in column \\\'J\\\' in excel file?Maybe we should also update Relation Table file if that kind of Sales Invoices like ID 81567(SI000044457) should be collected?!image-2023-01-02-15-09-15-489.png!""\', ""Comment 11: \'It is a similar situation as column Z"", \'Comment 12: but instead of Feed it is in the category Expenses\', ""Comment 13: You indeed may add this relation to the table.However it should indeed never appear twice on the FS whatever the underlyning relation is.\'"", ""Comment 14: \'Do dodania w tabeli relacji kolumna z obsługą faktury takiej jak w przykładzie"", \'Comment 15: w selectach trzeba rozróżniać czy SI Regular Expenses jest generowany z innego dokumentu czy nie. Selecty powinny mieć wykluczające się warunki\', ""Comment 16: aby 2 selecty nie zbierały tej samej faktury.\'"", ""Comment 17: \'[~damian.swistek@kotrak.com],uzupełniłem selecty"", ""Comment 18: dla wartości SI Regular Expenses generowany z innego dokumentu.Dokładnie w miejscach na bazie prod oraz test:Financial Statement - zmienione;KR_Printout_FS_TotalExpenses - zmienione;KR_CalculateSaldo2Pay - zmienione;KR_FinancialStatementSaldo - zmienione.\'"", \'Comment 19: ""We\\\'ve modified conditions for displaying invoices on Expeneses section.I\\\'ve added also relation in Relation Table document - column \\\'P\\\' - SI Regular Expenses.[~mbovene@deheus.com]could you provide descritption for this scenario in relation table - [https://app.box.com/file/1002580990454?s=kf5ux29gz5g5k2ykm5a6fz47a75n7741]It has been changed on test and production environment.!image-2023-02-07-15-20-15-456.png!Please verify that everything is correct and confirm if we can close the task.Regards""\', ""Comment 20: \'Done\'"", ""Comment 21: \'[~mbovene@deheus.com]could you confirm that we can close the task or you need to verify it?\'"", ""Comment 22: \'You can close it.\']""]\nRelated Issues:\n[]\n\n### End'}"
811,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8220\n\n### Instruction:\nHi\r\n\r\nWe are trying to confirm the Stocktaking Location STK-4/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\nThank you very much\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: \'Dla dokumentu STK-4/1/23 Communication Errors -> WMS"", ""Comment 4: dla modułu stock brak błędów!image-2023-01-02-11-44-10-672.png!\'"", ""Comment 5: \'!image-2023-01-02-11-58-08-602.png!\'"", ""Comment 6: \'Hi,Should barcode87-W000R6 be on stock?Regards\'"", \'Comment 7: ""I\\\'m not finding this UL in DHPSo you can remove it from stock""\', ""Comment 8: \'!image-2023-01-02-12-12-48-693.png!\'"", ""Comment 9: \'Please"", ""Comment 10: try to confirm now and let me know.Regards\'"", \'Comment 11: ""Same error :\\\'(""\', ""Comment 12: \'!image-2023-01-02-13-28-20-524.png!\'"", ""Comment 13: \'Please"", ""Comment 14: try now\'"", \'Comment 15: ""{code:java}update [DHPlantStockBusinessLogicMain].[dbo].[StocktakingElements] set IsCancelled = 1 where id = \\\'6F53857F-49A7-4BBB-9009-70DEEE88A2F3\\\' and No = 71{code}{code:java}update dbo.StocktakingSubElements set IsCancelled = 1 where id = \\\'6F53857F-49A7-4BBB-9009-70DEEE88A2F3\\\' and StockUnitId = \\\'D8FAD292-28E9-4B65-A1DA-40D089F44768\\\'{code}""\', ""Comment 16: \'Same error {:(}\'"", ""Comment 17: \'{code:java}2023-01-02 10:07:42 (35fe9e01-5719-4f64-a86b-b693c6405b4a/Plant.Stock.BusinessLogic/BR-4-SV-VM0204/22420/255) [Error] Kotrak.Common.Infrastructure.ICommandRunEnvironment - Error during Void Run[SetStocktakingProcessableCommand](Plant.Stock.BusinessLogic.Application.Interfaces.Stocktaking.Commands.SetStocktakingProcessableCommand) methodMicrosoft.Data.SqlClient.SqlException (0x80131904): Violation of PRIMARY KEY constraint \\\\\'PK_StocktakingElements\\\\\'. Cannot insert duplicate key in object \\\\\'dbo.StocktakingElements\\\\\'. The duplicate key value is (6f53857f-49a7-4bbb-9009-70deee88a2f3"", ""Comment 18: 1).Violation of PRIMARY KEY constraint \\\\\'PK_StocktakingSubElements\\\\\'. Cannot insert duplicate key in object \\\\\'dbo.StocktakingSubElements\\\\\'. The duplicate key value is (6f53857f-49a7-4bbb-9009-70deee88a2f3"", \'Comment 19: 1\', \'Comment 20: 1).The statement has been terminated.The statement has been terminated.   at Microsoft.Data.SqlClient.SqlConnection.OnError(SqlException exception\', \'Comment 21: Boolean breakConnection\', \'Comment 22: Action`1 wrapCloseInAction)   at Microsoft.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj\', \'Comment 23: Boolean callerHasConnectionLock\', \'Comment 24: Boolean asyncClose)   at Microsoft.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior\', \'Comment 25: SqlCommand cmdHandler\', \'Comment 26: SqlDataReader dataStream\', \'Comment 27: BulkCopySimpleResultSet bulkCopyHandler\', \'Comment 28: TdsParserStateObject stateObj\', \'Comment 29: Boolean& dataReady)   at Microsoft.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds\', \'Comment 30: RunBehavior runBehavior\', \'Comment 31: String resetOptionsString\', \'Comment 32: Boolean isInternal\', \'Comment 33: Boolean forDescribeParameterEncryption\', \'Comment 34: Boolean shouldCacheForAlwaysEncrypted)   at Microsoft.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior\', \'Comment 35: RunBehavior runBehavior\', \'Comment 36: Boolean returnStream\', \'Comment 37: Boolean isAsync\', \'Comment 38: Int32 timeout\', \'Comment 39: Task& task\', \'Comment 40: Boolean asyncWrite\', \'Comment 41: Boolean inRetry\', \'Comment 42: SqlDataReader ds\', \'Comment 43: Boolean describeParameterEncryptionRequest)   at Microsoft.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior\', \'Comment 44: RunBehavior runBehavior\', \'Comment 45: Boolean returnStream\', \'Comment 46: TaskCompletionSource`1 completion\', \'Comment 47: Int32 timeout\', \'Comment 48: Task& task\', \'Comment 49: Boolean& usedCache\', \'Comment 50: Boolean asyncWrite\', \'Comment 51: Boolean inRetry\', \'Comment 52: String method)   at Microsoft.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion\', \'Comment 53: Boolean sendToPipe\', \'Comment 54: Int32 timeout\', \'Comment 55: Boolean& usedCache\', \'Comment 56: Boolean asyncWrite\', \'Comment 57: Boolean inRetry\', \'Comment 58: String methodName)   at Microsoft.Data.SqlClient.SqlCommand.ExecuteNonQuery()   at Microsoft.EntityFrameworkCore.Storage.RelationalCommand.ExecuteNonQuery(RelationalCommandParameterObject parameterObject)   at Microsoft.EntityFrameworkCore.RelationalDatabaseFacadeExtensions.ExecuteSqlRaw(DatabaseFacade databaseFacade\', \'Comment 59: String sql\', \'Comment 60: IEnumerable`1 parameters)   at Plant.Stock.BusinessLogic.Infrastructure.EF.Stocktaking.StocktakingRepositoryExtensions.CreateStocktakingElements(DbContext context\', \'Comment 61: Guid stocktakingId\', \'Comment 62: Nullable`1 correlationId\', \'Comment 63: Boolean splitInventoryElementPerInternalSerialNumber) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Infrastructure.EF\\\\\\\\Stocktaking\\\\\\\\StocktakingRepositoryExtensions.cs:line 118   at Plant.Stock.BusinessLogic.Infrastructure.EF.Stocktaking.Repositories.StocktakingEfRepository.CreateStocktakingElements(Guid stocktakingId\', \'Comment 64: Nullable`1 correlationId) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Infrastructure.EF\\\\\\\\Stocktaking\\\\\\\\Repositories\\\\\\\\StocktakingEfRepository.cs:line 45   at Plant.Stock.BusinessLogic.Infrastructure.Persistance.Stocktaking.Repositories.StocktakingRepository.CreateStocktakingElements(AggregateId stocktakingId\', \'Comment 65: Nullable`1 correlationId) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Infrastructure.Persistance\\\\\\\\Stocktaking\\\\\\\\Repositories\\\\\\\\StocktakingRepository.cs:line 56   at Plant.Stock.BusinessLogic.Application.Stocktaking.StocktakingService.SetStocktakingProcessable(AggregateId stocktakingId) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Application\\\\\\\\Stocktaking\\\\\\\\StocktakingService.cs:line 118   at Plant.Stock.BusinessLogic.Application.Stocktaking.CommandHandlers.SetStocktakingProcessableCommandHandler.Handle(SetStocktakingProcessableCommand command) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Application\\\\\\\\Stocktaking\\\\\\\\CommandHandlers\\\\\\\\SetStocktakingProcessableCommandHandler.cs:line 26   at Kotrak.Common.Infrastructure.Commands.CommandEnvironment.Run[TCommand](TCommand command)   at Kotrak.Common.Infrastructure.Commands.Decorators.IntercontextEventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command)   at Kotrak.Common.Infrastructure.Commands.Decorators.EventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command)   at Kotrak.Common.Infrastructure.Commands.Decorators.ValidationCommandEnvironmentDecorator.Run[TCommand](TCommand command)   at Castle.DynamicProxy.AbstractInvocation.Proceed()   at Kotrak.Common.Infrastructure.Interceptors.LoggingInterceptor`1.Intercept(IInvocation invocation)ClientConnectionId:ab80d56e-caf7-486a-b541-2f07ae1ee1b2Error Number:2627,State:1,Class:142023-01-02 10:07:42 (/Plant.Stock.BusinessLogic/BR-4-SV-VM0204/22420/4) [Error] Serilog.AspNetCore.RequestLoggingMiddleware - HTTP ""POST"" ""/api/Stocktaking/setStocktakingProcessable"" responded 500 in 37.7491 ms{code}\\\'\', ""Comment 66: \'Please"", ""Comment 67: check now :)\'"", ""Comment 68: \'Same error :(I tried to use the incognito window because of clean cache"", ""Comment 69: but the error is the same!image-1!\'"", \'Comment 70: \\\'w WMS leci teraz taki błąd:{code:java}2023-01-02 10:34:23 (/Plant.WMS.BusinessLogic/BR-4-SV-VM0204/22672/171) [Error] Serilog.AspNetCore.RequestLoggingMiddleware - HTTP ""POST"" ""/api/unitLoadsList"" responded 500 in 187.0303 ms2023-01-02 10:34:25 (/Plant.WMS.BusinessLogic/BR-4-SV-VM0204/22672/216) [Error] Serilog.AspNetCore.RequestLoggingMiddleware - HTTP ""POST"" ""/api/unitLoadsList"" responded 500 in 76.1009 ms2023-01-02 10:34:26 (/Plant.WMS.BusinessLogic/BR-4-SV-VM0204/22672/171) [Error] Serilog.AspNetCore.RequestLoggingMiddleware - HTTP ""POST"" ""/api/unitLoadsList"" responded 500 in 71.7163 ms2023-01-02 10:35:20 (b4d6d089-1c96-49df-97be-1a309d8ad52e/Plant.WMS.BusinessLogic/BR-4-SV-VM0204/22672/162) [Error] Kotrak.Common.Infrastructure.ICommandRunEnvironment - Error during Void Run[RegisterLocationStocktakingCommand](Plant.WMS.BusinessLogic.Application.Interfaces.WarehouseStocktaking.RegisterLocationStocktakingCommand) methodKotrak.Extensions.Validation.Abstractions.ValidationException: Validation failed: -- Warehouse stocktaking should be in processable status -- Warehouse stocktaking should be in progress ---> Plant.WMS.BusinessLogic.DomainAbstractions.WarehouseStocktaking.WarehouseStocktakingInvalidOperationException: Validation failed: -- WarehouseStocktakingShouldBeProcessableMessage -- WarehouseStocktakingShouldBeInProgressMessage   at Plant.WMS.BusinessLogic.Domain.WarehouseStocktaking.WarehouseStocktaking.StartRealization() in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Domain\\\\\\\\WarehouseStocktaking\\\\\\\\WarehouseStocktaking.cs:line 78   at Plant.WMS.BusinessLogic.Domain.WarehouseStocktaking.Services.StocktakingDomainService.RegisterLocationStocktaking(WarehouseOrder warehouseOrder\', \'Comment 71: WarehouseStocktaking warehouseStocktaking\', \'Comment 72: UnitLoad unitLoad\', \'Comment 73: Quantity quantity) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Domain\\\\\\\\WarehouseStocktaking\\\\\\\\Services\\\\\\\\StocktakingDomainService.cs:line 169   at Plant.WMS.BusinessLogic.Domain.WarehouseStocktaking.Services.StocktakingDomainService.RegisterLocationStocktakingWithMovement(RegisterLocationStocktakingWithMovementDataStructure dataStructure) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Domain\\\\\\\\WarehouseStocktaking\\\\\\\\Services\\\\\\\\StocktakingDomainService.cs:line 122   at Plant.WMS.BusinessLogic.Application.WarehouseStocktaking.WarehouseStocktakingService.RegisterLocationStocktakingWithMovement(AggregateId locationId\', \'Comment 74: UnitLoad unitLoad\', \'Comment 75: Quantity quantity\', \'Comment 76: WarehouseStocktaking warehouseStocktaking\', \'Comment 77: WarehouseOrder warehouseOrder) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Application\\\\\\\\WarehouseStocktaking\\\\\\\\WarehouseStocktakingService.cs:line 330   at Plant.WMS.BusinessLogic.Application.WarehouseStocktaking.WarehouseStocktakingService.RegisterLocationStocktaking(AggregateId warehouseStocktakingId\', \'Comment 78: AggregateId locationId\', \'Comment 79: AggregateId unitLoadId\', ""Comment 80: Quantity quantity) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Application\\\\\\\\WarehouseStocktaking\\\\\\\\WarehouseStocktakingService.cs:line 114   at Plant.WMS.BusinessLogic.Application.WarehouseStocktaking.Handlers.RegisterLocationStocktakingCommandHandler.Handle(RegisterLocationStocktakingCommand command) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Application\\\\\\\\WarehouseStocktaking\\\\\\\\Handlers\\\\\\\\RegisterLocationStocktakingCommandHandler.cs:line 32   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){code}\'"", ""Comment 81: \'!image-2023-01-02-15-01-53-402.png!\'"", \'Comment 82: ""I tried to cancel this STK \', \'Comment 83: remove the UL you informed and open a new STK-LOHowever\', ""Comment 84: system doesn\'t allowWhat do you think about this? Cancel this STK"", \'Comment 85: we remove this UL you informed an dopen new STK?""\', \'Comment 86: ""Maicon\', \'Comment 87: we are investigating with dev this issue\', \'Comment 88: I\\\'ll let you know as soon as possible""\', ""Comment 89: \'Do you have any error while cancelling STK?\'"", \'Comment 90: ""I tried to cancel\', \'Comment 91: the DHP showed *Contact system admin* message.Now I try to do it again and there\\\'s no option!image-2!""\', ""Comment 92: \'Maicon,I have closed without realisation this STK. Please"", ""Comment 93: try to create a new one and let us knowRegards\'"", \'Comment 94: ""{code:java}SELECT *        FROM [DHPlantStockBusinessLogicMain].[dbo].[StockUnits] where id = \\\'d8fad292-28e9-4b65-a1da-40d089f44768\\\' or UnitLoadId = \\\'6293ec84-ebf4-4673-8daa-d0c8bb9e70ab\\\'   6293ec84-ebf4-4673-8daa-d0c8bb9e70ab{code}{code:java}SELECT su.QuantityOnHandValue\', \'Comment 95: su.ReservedQuantityValue\', \'Comment 96: su.LogisticStatus,su.ReservationSourceDocumentNumbers,ul.Barcode,su.Id FROM [DHPlantWmsBusinessLogicMain].[dbo].[UnitLoads] ul inner join [DHPlantWmsBusinessLogicMain].dbo.StockUnits su on ul.id=su.UnitLoadId where ul.barcode in( \\\'87-W000R6\\\' ) SELECT QuantityOnhand,Quantity,* FROM [DHPlantStockBusinessLogicMain].[dbo].[StockUnits] where barcode in( \\\'87-W000R6\\\' ) select * from dbo.StockUnits sinner join dbo.StockUnitReservations sr on sr.Id = s.Idwhere s.Barcode = \\\'87-W000R6\\\'{code}{code:java}SELECT *  FROM [DHPlantStockBusinessLogicMain].[dbo].[Stocktakings] where id = \\\'0e7f9dfa-29ad-429a-b027-c2ef81ce909b\\\' or Document =\\\'STK-4/1/23\\\'{code}{code:java}/****** Script for SelectTopNRows command from SSMS ******/ SELECT TOP (1000) [Id] ,[No] ,[ItemId] ,[SerialNumber] ,[ExpiryDate] ,[QuantityBefore] ,[QuantityBeforeUnit] ,[CorrelationId] ,[QuantityAfter] ,[QuantityAfterUnit] ,[IsCancelled] ,[InternalSerialNumber] FROM update [DHPlantStockBusinessLogicMain].[dbo].[StocktakingElements] set Iscancelled = 0 where id = \\\'6F53857F-49A7-4BBB-9009-70DEEE88A2F3\\\' and No = 71 or id = \\\'6f53857f-49a7-4bbb-9009-70deee88a2f3\\\' A4018A7F-5DDC-468E-90A5-DA5AD769A4D2{code}{code:java}--select * delete from dbo.StocktakingSubElements where id = \\\'6F53857F-49A7-4BBB-9009-70DEEE88A2F3\\\' and StockUnitId = \\\'D8FAD292-28E9-4B65-A1DA-40D089F44768\\\'{code}""\', ""Comment 97: \'Hi AleksandraNew STK-11/1/23 was created and confirmed.Thank you very muchYou can close this task\']""]\nRelated Issues:\n[\'DGS-8246\', \'DAP-13153\']\n\n### End'}"
812,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8219\n\n### Instruction:\nProszę o sprawdzenie co się stało z numeracją VT? Przeskoczyła na starą, część VT jest/była z zeszłego roku, ale otrzymaliśmy w piątek potwierdzenie od Was, że nie musimy ich zamykać, mogą zostać, numeracja i VT i WZ miała iść poprawnie. Przy poprawie pamiętajcie o tym, że samochody cały czas wjeżdżają i wyjeżdżają, zamkniętych VT już nie poprawiajcie\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \' !screenshot-1! \'"", ""Comment 4: \'Grodzisk to samo!image-1!\'"", ""Comment 5: \'The question was only about the date when WZ to XL documents would be generated.If VTs are closed after the new year"", ""Comment 6: the numbering will be wrong.\'"", ""Comment 7: \'24 - Spytkowice:Change for VT 20543/1/2023 to VT 48/1/2023Change for VT 20502/12/2023 to VT 20502/12/2022.\'"", ""Comment 8: \'!image-2!\'"", ""Comment 9: \'tylko Spytkowice i Grodzisk do poprawy są\'"", ""Comment 10: \'GrodziskChange for VT 25180/12/2023 to VT 25180/12/2022\'"", ""Comment 11: \'list of changes"", ""Comment 12: can we change to p2 for changes in dhc and xl?[^DGS-8219.xlsx]\'"", ""Comment 13: \' [^DGS-8219.xlsx] \'"", ""Comment 14: \'task to be closed\']""]\nRelated Issues:\n[]\n\n### End'}"
813,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8218\n\n### Instruction:\nWe got reported no trips are arriving in DHP Utrecht. For example trip id 00955305\r\n\r\nAdditionally, intakes are also not coming through.\r\n\r\nPlease check, thanks!\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 2: \\\'{code:java}2023-01-02 00:00:52 (/Plant.DHC.Integration/DHVD01AP183/3840/14) [Error] Microsoft.EntityFrameworkCore.Query - An exception occurred while iterating over the results of a query for context type \\\\\\\'""Plant.Integration.DhcService.EF.IdentityMapping.IdentityMappingContext""\\\\\\\'.""""""Microsoft.Data.SqlClient.SqlException (0x80131904): A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider\', ""Comment 3: error: 40 - Could not open a connection to SQL Server) ---> System.ComponentModel.Win32Exception (53): The network path was not found.{code} !screenshot-1! \'"", ""Comment 4: \'There was a database connection error in the log: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 5: error: 40 - Could not open a connection to SQL ServerAfter restarting the application pool DHPintergratonDHCdata passed to the plant.\'"", ""Comment 6: \'Thanks for solving. Any idea why this happened?\'"", ""Comment 7: \'looks like database connection problems - network problem.But it should be verified if they were any.\'"", ""Comment 8: \'Issue related with DGS-8236 - this task has been closed.\']""]\nRelated Issues:\n[\'DGS-8236\']\n\n### End'}"
814,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8217\n\n### Instruction:\nI tried to create an opening balance for Sneek, but it hangs on the status \'processing\' Can you check and make sure it is executed? \n\n### Response:\n[""Comment 1: [\'!afbeelding!\'"", \'Comment 2: ""Sorry\', ""Comment 3: never mind: It\'s executed now"", \'Comment 4: took some time""]\']\nRelated Issues:\n[]\n\n### End'}"
815,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8216\n\n### Instruction:\nFinancial Statement ID 78050\r\n\r\nAfter clicking a button, the system displays an error below\r\n\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Odtworzone na IBIP_DH_TEST na tym samym dokumencie o ID = 78050"", \'Comment 4: w procedurzeKR_calculatetechresults wyliczamy parametr@Hakdermatitus (pobierane są tu po przecinku wartości z podlinkowanych do tej rundy dokumentów SR). W tym przypadku jest ich 18 i wartość\', ""Comment 5: która ma być zaktualizowana w poluDoc_ShortStringColumn1 (128 znaków) na FS jest większa i ma długość 134 znaki.\'"", \'Comment 6: ""Hi,Issue with this documents is related to calculating field \\\'Hakdermatitus\\\'.In\\\'Hakdermatitus\\\' is calculated field from connected Slaughtery Reports. So there are 18 Slaughery Reports for this Financial statement and system try to join values and insert in field\\\'Hakdermatitus\\\' on Financial Statement\', ""Comment 7: it should be like \'9,60 %"", \'Comment 8: 0,00 %\', ""Comment 9: ...\'But field\'Hakdermatitus\' on Financial Statement is too short (128 characters) while in this case is 134 characters.So"", \'Comment 10: solution could one of these below depends how it is useful: * change field Hakdermatitus for longer field in database and move old values to this field\', \'Comment 11: * change field Hakdermatitus to dynamic text (data will not be saved in database but only displaying on Financial statement dynamically from SR values)\', \'Comment 12: * add a column to list of Slaughtery reports on Financial statement with \\\'Hakdermatitus\\\' value.Please let us know how we should handle this.Technical result on FS:!image-2023-01-03-09-33-13-881.png!Field on slaughtery Report:!image-2023-01-03-09-35-04-835.png!Field on FS when there are a lot o SR\\\'s:!image-2023-01-03-09-45-41-962.png!""\', \'Comment 13: ""Please go for your third solution. You mean to create a table with all SR\\\'s and their scores?""\', \'Comment 14: ""The table already exists on Financial statement\', \'Comment 15: so I mean that we could add only new column \\\'Hakdermatitus\\\' to this table and then user will see information in table instead on field at the document.Maybe column \\\'Hakdermatitus\\\' can replace column \\\'Ras\\\' if it\\\'s not used (I\\\'m not sure that is needed) or we can add it as a new column?!image-2023-01-03-11-42-37-074.png!""\', ""Comment 16: \'You can indeed add a new column.Ras is sometimes needed"", ""Comment 17: so just add a new column.\'"", ""Comment 18: \'Dodanie kolumny dla listy SR dla MAS NL i MAS BE. Zakomentowanie w procedurach TechnicalResults wypełnianie pola. Usunięcie kontrolki z formularza. Zmiany wykonane na bazie testowej IBIP_DH_TEST.\'"", ""Comment 19: \'[~mbovene@deheus.com]"", ""Comment 20: all changes have been done on test environment. You can feel free to test it.\'"", ""Comment 21: \'Ready for UAT tests\'"", ""Comment 22: \'Great"", ""Comment 23: this works good.\'"", ""Comment 24: \'Functionality moved on production environment.You can feel free to test it.Best regards,Grzegorz\']""]\nRelated Issues:\n[]\n\n### End'}"
816,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8215\n\n### Instruction:\nMitch: Could you please plan to change this in Intense? If you have any questions please let me know. The sector would like to implement this before the end of January. Do you think that is possible?\r\n\r\nAfter your response I will add a task in JIRA.\n\n### Response:\n[""Comment 1: [\'[^New format printout Financial Statement-1.msg] _(512 kB)_\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Tutaj trzeba się upewnić"", \'Comment 4: czy zmiany będą dotyczyć również Belgii\', ""Comment 5: bo Steffen na bieżąco zgłasza prośby o modyfikacje i je implementujemy. W tej chwili wydruki w MAS BE wyglądają inaczej niż w pozostałych sektorach.\'"", ""Comment 6: \'Do zmiany wydruki dla MAS NL i MAS BE: * Financial Statement (do omówienia niejasne zmiany) * Saldo to pay (nie dostaliśmy jeszcze wzoru)\'"", ""Comment 7: \'[^Nieuw koppeloverzicht 20-12-2022_comments.xlsx]\'"", ""Comment 8: \'Do wykonania wydruki do MAS NL i MAS BE dla Financial Statement (na tą chwilę nie są potrzebne zmiany w wydrukach Saldo to Pay).Celem wydruku jest m. in. to"", \'Comment 9: żeby dane były skompresowane do 1 strony (jeśli to możliwe w zależności od ilości danych)\', \'Comment 10: dlatego część informacji jest zgrupowana\', \'Comment 11: a niektóre sekcje pominięte/ujęte inaczej.Tworzymy nowy wydruk\', \'Comment 12: który będzie podpięty jako dodatkowy wydruk do wyboru przez użytkownika. Stare wydruki zostawiamy bez zmian.W wydruku dla MAS BE uwzględniamy te zmiany\', \'Comment 13: które są tutaj + to co jest w tasku https://helpdesk.kotrak.com/browse/DGS-8075W pliku dodane komentarze do niektórych pól\', ""Comment 14: wydruk omówiony z Mitchem.[^Nieuw koppeloverzicht 20-12-2022_comments.xlsx]FS w MAS NL - ID 72604\'"", ""Comment 15: \'[~damian.swistek@kotrak.com]"", ""Comment 16: dodano wydruk Financial Statement 2 (MAS) na bazie testowej. Do przetestowania przez klienta.\'"", \'Comment 17: ""Printout \\\'Financial Statement 2\\\' is ready now in MAS NL on UAT environment\', \'Comment 18: so it\\\'s possible to test it.!image-2023-01-12-14-43-55-417.png!""\', ""Comment 19: \'Czeka na sprawdzenie przez DH we wtorek 17.01.2023. Po akceptacji wydruku w MAS NL"", ""Comment 20: będzie można przystąpić do stworzenia wydruku dla MAS BE.\'"", ""Comment 21: \'wzór starego wydruku używanego przez Coppens[^3860_huna_v2206.pdf]\'"", \'Comment 22: ""Wysłane do klienta zmiany ze spotkania:Adjustments for printout after meeting: # Printout should be in portrait orientation # If it\\\'s possible printout should be by default open with option \\\'Fit for 1 page\\\' (option available on printout preview) # All columns with numbers shoul be align to right # Field \\\'Tot hokoppervlak\\\' - to verify # Header of the report should be on each page (if there will be more than 1 page) # Percentage values in column \\\'Aandeel totaal (%)\\\' # Fields from sectionTechnische gegevens should have 3 decimal places (after comma) ## daggroei: ## doorgroei na 1e keer uitladen: ## voederconversie netto: ## vc-1500g netto: # Additional subtotal row forVoerverbruik (sectionVoerleveringen) # Only partly moved feed from round should be displayed on printout. Feed moved with whole delivery shouldn\\\'t be presented on printout for this round. # Voerverbruik -> \\\'Begin voorraad\\\' should be divided for 2 rows: ## Begin voorraad voer: ## Begin voorraad tarwe: (only item group = \\\'Raw materials\\\') # Voerverbruik -> \\\'Eind voorraad\\\' should be divided for 2 rows: ## Begin voorraad voer: ## Begin voorraad tarwe:(only item group = \\\'Raw materials\\\') # All values should be presented with positive numbers: ## \\\'Voerverbruik\\\' section -> Eind voorraad voer: ## \\\'Aflevergegevens slachterij\\\' section ### Aantal ### Gewicht (netto) ### Kg afkeur ### Aantal afkeur ### Bedrag Excl. BTW ### Gemiddeld gewicht ### Prijs excl. BTW # Calculation changes from \\\'Technische gegevens\\\' section for field: ## doorgroei na 1e keer uitladen: (please send us calculation for this field) # Labels from section \\\'Technische gegevens\\\' shouldn\\\'t be bolded. Only label for section should be bolded.""\', \'Comment 23: ""Uwagi do wydruku po spotkaniu z klientem[^FS_2_new.xlsx]Punkty do zmiany w Excelu + excel od klienta z dodatkowymi wytycznymi co do sekcji technical result (dodany także do pliku[^FS_2_new.xlsx]|Remarks from meeting to adjust:||1.|Fields which should have values with whole numbers : \\\'Tot hokoppervlak\\\'\', ""Comment 24: \'Aantal\'"", ""Comment 25: \'Gewicht\'"", ""Comment 26: \'Kg afkeur\'"", ""Comment 27: \'Aantal afkeur\'"", ""Comment 28: \'Aandeel totaal (%)\'||2.|Fields which should have € sing before number: \'Prijs excl. BTW\',||3.|Tarw (row 27) - value in column \'Bedrag excl. BTW\' to verify||4.|Tarwe instead of Tarwe/stro - to fix in Milas||5.|Label \'Eind voorraad:\' - to remove||6.|Begin voorraad voer:\' and \'Begin voorraad tarwe:\' - should be \'eindvoorr\' instead of \'begin\'||7.|Gemidel gewicht - should be 3 digits after comma"", \'Comment 29: label should be in one line instead of two\', \'Comment 30: other fields also in one line||8.|Bedrag excl. BTW\\\' - should be filled for begin and end in section \\\'Voerverbruik\\\'||9.|Aflevergegevens slachterij\\\' section - if \\\'Referentie\\\' and \\\'Datum\\\' is the same in more than 1 row it should be sum of rows and show in 1 row. Ascending dates - oldest dates first||10.|Financial statement document - to rename field \\\'Feed profit\\\' -> \\\'Feed profit per broiler\\\'||11.|Financial statement document- to add field \\\'Feed profit\\\' (\\\'Voerwinst\\\' on printout) - calculation= (total value first loaders + total value all loaders) - total value feed - total value DOC\\\'s||12.|To remove - \\\'percentage mais\\\'|""\', ""Comment 31: \'Mamy część danych do wyliczeń technical results:[^Technical results formulas financial statement.xlsx]\'"", \'Comment 32: ""Tutaj komentarze do niektórych pól z Tech results: * Voerwinst - tutaj będzie potrzebna zmiana wyliczeń w technical results na dokumencie FS * Tarwe (%) - pobieramy złe pole - \\\'Percentage corn\\\' zamiast \\\'Percentage wheat\\\'Czekamy jeszcze na wyliczenia dla pól: * Doorgroei na 1e keer uitladen (g/d) * Hakdermatitis (%) * Score voetzoollaesies[^Technical results formulas financial statement_DŚ.xlsx]Bazowym dokumentem jest FS o ID 79562 z IBIP_DH_TESTDo sprawdzenia move feed na tym dokumencie - nie przeniosły się wartości kwotowe na minus - tylko waga.Wcześniej nie było widać sekcji eindvoorr voer - nie było to przesunięte przez feed sale\', \'Comment 33: a fakturą.Na wydruku do dodania kolumna \\\'Uitv\\\'z checkboxem za kolumną \\\'Referentie\\\'!image-2023-01-30-09-34-58-663.png!""\', \'Comment 34: ""Hi Mitch,Few questions about FS printout: * \\\'Voerleveringen\\\' - on screen there are my reamarks about presenting these values and calculations. Please verify these remarks. * Column with \\\'price\\\' for subtotals section \\\'Voerverbruik\\\' !image-2023-01-30-12-58-31-017.png! * Technical results for document in Intense - Feed profit calculationShould we change procedure for calculations of: ** Total value of first loader ** Total value of all loaderNow values are summed from invoices with Item = \\\'SLAC\\\' minus Item = \\\'AFKK\\\'When we change calculations on: sum from invoices with all Items (except item = \\\'AFKK\\\'\', ""Comment 35: should we do it like that with AFKK?) minus Item = \'AFKK\' the values for this example (FS-M/0219"", \'Comment 36: ID= 79562 on IBIP_DH_TEST) will be like these: *** Total value of first loader =136224.50 *** Total value of all loader =80922.40 **** *Sum =217146.90* *** Average price delivered broilers per kg - this value will also change because it based on these 2 above!image-2023-01-30-13-22-25-746.png!After confirming these change withFeed profit calculation\', \'Comment 37: I will create a separate task to adjust these changes.""\', \'Comment 38: ""Confirmed in conversation with Mitch: * {quote}\\\'Voerleveringen\\\' - on screen there are my reamarks about presenting these values and calculations. Please verify these remarks{quote}Confirmed - it\\\'s ok{quote}Column with \\\'price\\\' for subtotals section \\\'Voerverbruik\\\'{quote}Confirmed - it\\\'s not needed on printout!image-2023-01-30-14-31-14-976.png!Now printout should be like example from Coppens (we also provide value for Beginvorr voer (now it\\\'s on feed sals with mark that it\\\'s moved from other round\', \'Comment 39: we deleted invoice for this value\', \'Comment 40: it was before provided by invoice)Plese verify printout.Now we only need to adjust tech results field and we\\\'re waiting for calculation formula: * Doorgroei na 1e keer uitladen (g/d)For adjustments in technical results I\\\'ve created a taskhttps://helpdesk.kotrak.com/servicedesk/customer/portal/56/DGS-8428""\', ""Comment 41: \'Hi Damian,I have got additional feedback. Here it is:- Remove product number from feed name (now there is a number after the product name)- Always show starting stock and ending stock on the printout (wheat and feed"", \'Comment 42: also if 0) + price and amount- Note VC calculation\', \'Comment 43: this is now done with subtotal not with ultimate total value of the feed (including end stock)- Column text ""gemiddeld gewicht"" for slaughter data\', \'Comment 44: d falls on the next line. Please put it on the same line.- Average age two decimal places- For technical data: “Gewicht (g)” please make it (kg)”. Multiply value to kg (x 1.000) and remove text ""grams"" behind the value. - Groei (g/d) 2 decimal places- Doorgroei na uitladen  2 decimals- Uitval. Please change the . for a ,- Hakdermatitis 2 decimals- Kg per m2 2 decimals- At the very bottom right of the page: De Heus Voeders B.V. (in front of the date and time)\\\'\', ""Comment 45: \'Przesłany plik z ostatnimi wyliczeniami do technical results[^Technical results formulas financial statement-1.xlsx]\'"", ""Comment 46: \'{quote}I have got additional feedback. Here it is: - Remove product number from feed name (now there is a number after the product name) - Always show starting stock and ending stock on the printout (wheat and feed"", \'Comment 47: also if 0) + price and amount - Note VC calculation\', \'Comment 48: this is now done with subtotal not with ultimate total value of the feed (including end stock) - Column text ""gemiddeld gewicht"" for slaughter data\', \'Comment 49: d falls on the next line. Please put it on the same line. - Average age two decimal places - For technical data: “Gewicht (g)” please make it (kg)”. Multiply value to kg (x 1.000) and remove text ""grams"" behind the value. - Groei (g/d) 2 decimal places - Doorgroei na uitladen 2 decimals - Uitval. Please change the . for a \', \'Comment 50: - Hakdermatitis 2 decimals - Kg per m2 2 decimals - At the very bottom right of the page: De Heus Voeders B.V. (in front of the date and time){quote}All of this remarks above are adjusted right now. We have only question about this point: * {quote}Note VC calculation\', ""Comment 51: this is now done with subtotal not with ultimate total value of the feed (including end stock){quote}what does it mean? calculations on printout are the same like on old printout for Coppens - 1,544Regarding the calculation of \\\\\'Doorgroei na 1e keer uitladen (g/d)\\\\\'Is this formula good? at first we take first loaders"", \'Comment 52: then we substract all loaders?(1000 x ((A""/""C"")-(""B""/D""))/(""F""-""E"")!image-2023-02-01-12-10-11-489.png!In our example in Intense value is calculater right now with minus sign and in these case we don\\\\\\\'t show value on printout.Calculated value is-90.4442 right now.Should we show the value even if it\\\\\\\'s negative value? With what sign? negative or positive always?!image-2023-02-01-12-13-34-225.png!\\\'\', \'Comment 53: \\\'what does it mean? calculations on printout are the same like on old printout for Coppens - 1,544.  --> Without the minus? That\\\\\\\'s good. Although you change the value of the lines on the feed deliveries (you did not substract the endstock anymore)  this should not change the calculations. Regarding the calculation of \\\\\\\'Doorgroei na 1e keer uitladen (g/d)\\\\\\\'It should be the other way around. First we all loaders and than substract first loaders:(1000 x ((B""/""D"")(""A""/C""))/(""F""""E"")In our example in Intense value is calculater right now with minus sign and in these case we don\\\\\\\'t show value on printout.The calculated value I get is 97,52Should we show the value even if it\\\\\\\'s negative value? With what sign? negative or positive always? --> No it can never be a negative value. That means the animals are shrunk.\\\'\', \'Comment 54: ""[~grzegorz.materla@kotrak.com]zmieniłem formułę dla\\\'Doorgroei na 1e keer uitladen (g/d)\\\' w procedurze""\', ""Comment 55: \'Formula has been changed and now we get proper value on printout.We also verified Feed profit value from example on IBIP_DH_TEST and there were bad data for Feed sale line (positive instead of negative) - [https://helpdesk.kotrak.com/servicedesk/customer/portal/56/DGS-8428]Now printout should looks good"", ""Comment 56: please verify and confirm that values are correct.\'"", ""Comment 57: \'!image-2023-02-02-15-26-28-382.png!\'"", ""Comment 58: \'Doogroei g/d is still 2 decimals"", ""Comment 59: should be 0.Also why is the second line in the slaughtery marked as Uitl? That should not be the case.\'"", \'Comment 60: \\\'{quote}The number after ""Ronde:"" is not correct. This is the FS number. It should be the ""Round number"".!image-2023-02-03-09-17-35-925.png!{quote}!image-2023-02-03-09-18-25-289.png!This is related to FS printout.\\\'\', ""Comment 61: \'[~damian.swistek@kotrak.com] zrobione ;)\'"", ""Comment 62: \'[~mbovene@deheus.com],all adjustements have been done on test environment. The printout has been moved to production environment.You can feel free to test it.Best regards,Grzegorz\'"", ""Comment 63: \'Do sprawdzenia!image-2023-02-04-11-06-24-566.png!\'"", ""Comment 64: \'Feed profit calculations[^Feed_profit_calculations.xlsx]\'"", \'Comment 65: ""* {quote}Feed profit per chick should be (second metric): 50,917.35/67263 = 0,7569{quote} * {quote}Suggestions where things might go wrong: o Divide by number of chicks delivered (not number of day-old chicks set up) o Total amount excluding VAT feed (140972.01) not subtotal (141312.39){quote}Could you please verify attachment [^Feed_profit_calculations.xlsx]and indicate how we should calculate these fields:There are calculations for 2 fields which are on \\\'Tech Results\\\' tab on FS document. * Feed profit per broiler * Feed profit!image-2023-02-06-15-14-49-034.png!This is also related to renaming and adding new field and changing \\\'Feed profit\\\' calculations (now after renaming it\\\'s field - \\\'Feed profit per broiler\\\') and changing calculations[https://helpdesk.kotrak.com/servicedesk/customer/portal/56/DGS-8053]!image-2023-02-06-15-19-12-728.png! * {quote}Heel dermatitis 2,00 not 2.00 (dot --> comma){quote} * {quote}Gewicht (kg) : 174620 / 67263 = 2,596 (not 2,600){quote}It\\\'s adjusted and looks good!image-2023-02-06-15-20-24-454.png!""\', ""Comment 66: \'Do zmiany wyliczanie Feed profit per broiler w procedurzeKR_calculatetechresults jak w pliku od Mitcha[^Feed_profit_calculations_MB.xlsx]\'"", \'Comment 67: ""Technical results calculations on Financial statement document has been changed for field \\\'Feed profit per broiler\\\'.*Feed profit* = (ABS(@AmountFL) + ABS(@AmountAL)) - ABS(@AmountOfFeed) - ABS(@AmountDOCNet)) - old calculations - OK*Feed profit per broiler* = Feed profit/(@NumberOfBroilersFL + @NumberOfBroilersAL) - new calculations - OKOld calculations for Feed profit per broiler - changed and not actual(ABS(@TotalSLAC) - ABS(@AmountDOCNet) - ABS(@TotalIncludeFeedProfitItems) - ABS(@AmountOfFeed)) /(@NumberOfBroilersFL + @NumberOfBroilersAL) Now on printout is different value for \\\'Voerwinst per kuiken\\\' and it\\\'s calculated in a new way.!image-2023-02-07-14-10-54-481.png!""\', ""Comment 68: \'Do zmiany procedura KR_calculatetechresults_MASBE z wyliczaniem Feed profit i Feed profit per broiler - w MAS NL dodane zostało nowe pole"", ""Comment 69: a dla starego została zmieniona nazwa jak na screenie. Podobnie do zrobienia w MAS BE.!image-2023-02-06-15-19-12-728.png!\'"", ""Comment 70: \'Potwierdzone przez Richarda"", \'Comment 71: że wydruk zaakceptowany i można przystąpić do tworzenia wydruku FS dla MAS BE. Potwierdzone także\', ""Comment 72: że Feed profit powinno być zmienione analogicznie w MAS BE jak w MAS NL\'"", ""Comment 73: \'Financial statement printout for MAS BE sector is ready to verify on test environment (IBIP_DH_TEST)\'"", ""Comment 74: \'Do przerzucenia także na prod wydruk FS dla sektora MAS BE\'"", ""Comment 75: \'Financial statement printout for MAS BE sector is ready to verify on prod environment (IBIP_DH)!https://attachments.office.net/owa/damian.swistek%40kotrak.com/service.svc/s/GetAttachmentThumbnail?id=AAMkADY2ZTAxMzM3LTE0YjctNGI0Ni1hYjIxLWE3MDFjOTVkNmExNwBGAAAAAAA%2FcPjpt4lNRZFonusrO6C9BwA5bA29TyJrQIX6A6F8SkSqAAAAAAEJAAA5bA29TyJrQIX6A6F8SkSqAAS37XAYAAABEgAQAHbHPL6Ir1ZKpUWQ1nbF0BY%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 76: \'!image-2023-02-13-13-36-26-940.png!\'"", ""Comment 77: \'To change on FS printout in MAS NL and MAS BE:!image-2023-02-13-13-37-34-741.png!\'"", ""Comment 78: \'[~damian.swistek@kotrak.com]"", ""Comment 79: [~mbovene@deheus.com],I made changes in prod and test environment.You can feel free to test it.Best regards,Grzegorz\'"", \'Comment 80: ""Zmiany z maila do implementacji najpierw na test\', ""Comment 81: a później po weryfikacji na prod.[^RE_ Financial Statement printout_ Begin and End stock.eml]Do dodania na Feed sale checkboxy \'BV\' i \'EV\'"", \'Comment 82: które będą weryfikowane przy wydruku i w zależności od ich ustawienia będą pokazywane w odpowiedniej sekcji na wydruku FS.""\', ""Comment 83: \'Changes to implement for Feed sale lines and handling lines on FS printout.!image-2023-02-14-15-34-49-788.png! \'"", ""Comment 84: \'[~mbovene@deheus.com],I added new columns in Feed Sale elements: BV"", \'Comment 85: EV and made changes on printouts for sectors: MAS NL and MAS BE. If you dont see it on view\', \'Comment 86: you can add it (right click on header of column -> column chooser). You can feel free to test printouts on test environment.Best regards\', ""Comment 87: Grzegorz\'"", ""Comment 88: \'This works fine"", ""Comment 89: can be deployed to PROD.\'"", ""Comment 90: \'[~mbovene@deheus.com],the modification has been deployed to PROD. You can feel free to test it.Best regards,Grzegorz\'"", \'Comment 91: \\\'Remarks from Mitch:!image-2023-03-01-14-02-07-821.png! # Should be an average of the totals above in this case of 45.955,70 divided by 100.997 # Should be an average of the Eindvoorraad voer and Eindvoorr voorraad tarwe in this case of 45.518,99 divided by 99.873 (please note that ""Eindvoorr voorraad tarwe"" should be renamed into ""Eindvoorraad tarwe"") # Should be the average\', \'Comment 92: the 1 is not correct. Correct calculation is 98/2,575\', \'Comment 93: so the total ""Kg afkeur"" divided by ""Gemiddeld gewicht"" # Should be the total SUM of the values above\', ""Comment 94: there could be multiple lines in this section.You can directly develop this in PROD.\'"", \'Comment 95: ""[~mbovene@deheus.com],we\\\'ve done all modification. You can feel free to test it on prod Intense environment.Best regards,Grzegorz""\', \'Comment 96: ""[~mbovene@deheus.com]We know why there is a difference between values on Technical Results - field \\\'Average weight in gram\\\' and \\\'Gemiddet gewicht\\\' field on new FS printout (summary line \\\'Total\\\' for section Slaughtery) - based onFS-M/0634 document. * For technical results when value is taken value from Slaughtery report directly (Net Weight) - as we discussed it\\\'s correct. * For printout weight is taken from invoices and we include only lines with item = \\\'SLAC\\\'\', \'Comment 97: then weight for line with item \\\'VOER\\\' is not included in this calculation.*Should this be changed and item = \\\'VOER\\\' should be included in calculations*(we\\\'ve checked that this item on invoices is generated from SR and values are taken from field \\\'Food discount in kg\\\'). If this item is only using for this purposes we can include also weight from this item to calculations and in this case it will be correct value (as on technical results on FS document).FSFS-M/0634 (ID 102037) * Technical results on FS!image-2023-03-02-10-39-11-996.png! * FS new printout!image-2023-03-02-10-41-36-465.png!SR/5198!image-2023-03-02-10-42-41-317.png!PI from SR!image-2023-03-02-10-48-16-912.png!""\', ""Comment 98: \'Yes"", \'Comment 99: VOER should be included. That makes in the ""Net weight"".  Indeed it is related to the Food discount.\\\'\', \'Comment 100: ""[~mbovene@deheus.com],we\\\'ve made changes in procedure for new FS printouts in MAS NL and MAS BE included VOER calculations.You can feel free to test it in test and prod environment.Best regards,Grzegorz""\', ""Comment 101: \'Hi"", \'Comment 102: regarding the sequence of lines we have another one. It must be sorted on full date\', ""Comment 103: not only on the first number:!image!\'"", \'Comment 104: ""For the \\\'Opzetgegevens\\\' we would like to move the columns from \\\'Aantal\\\' to \\\'Bedrag excl. BTW\\\' to the left so that they are aligned with the columns for \\\'Voerverbruik\\\'. The most right column will remain empty then. !image-1!""\', \'Comment 105: ""Additional requirement for printout and technical results:{quote}Another thing we totally forgot in our requirements\', \'Comment 106: we need to exclude BTWF from all of the PDF\\\'s and the technical result calculations like voerwinst (=feedprofit):!image-2023-03-06-08-45-08-767.png!Are you able to exclude the code BTWF (it is about financed VAT and has nothing to do with profits).It must be excluded on the printout because we are not looking at the values including VAT (because BTWF is still in the totals). And we should make it excluding VAT.{quote}""\', \'Comment 107: \\\'1. In the field ""Ras"" on the category ""Opzetgegevens"" we would like to see the item name of the respective DOC item code. Now it is the manually adjusted description which is some times too long.2. Could we add a field on the customer card (below ""Loan customer No.) which we call ""Name Abbreviation""? In this field the user can manually set the abbreviation. We would like to display this field on the ""Referentie"" in the Aflevergegevens slachterij. Now we are dealing with very long names that can\\\\\\\'t be placed on one line.3. We would like to add two empty columns to the \\\\\\\'Technische gegevens"". The labels and the value we would like to see closer together.4. Please delete the word ""BTW"" from all labels5. Please delete the word ""afkeur"" in ""Aantal afkeur"".6. Please change ""gemiddeld gewicht"" into ""Gem. gewicht"".7. Please change ""Begin voorraad voer:"" in ""Beginvoorraad voer:"" and ""Begin voorraad tarwe:"" in ""Beginvoorraad tarwe:""8. Could you move everything one line down?The goal of many of these changes is to get all information on just one line instead of 2 lines. Please note: there are still other tasks that should be handled in this topic.  \\\'\', ""Comment 108: \'[~mbovene@deheus.com]All adjustments from last 4 comments have been implemented on test environment.After confirmation that is good on test environment we can move it also to production environment.\'"", ""Comment 109: \'Just 1 thing"", \'Comment 110: see comment 6 below. You can move all to PROD.1. In the field ""Ras"" on the category ""Opzetgegevens"" we would like to see the item name of the respective DOC item code. Now it is the manually adjusted description which is some times too long. DONE2. Could we add a field on the customer card (below ""Loan customer No.) which we call ""Name Abbreviation""? In this field the user can manually set the abbreviation. We would like to display this field on the ""Referentie"" in the Aflevergegevens slachterij. Now we are dealing with very long names that can\\\\\\\'t be placed on one line. DONE3. We would like to add two empty columns to the \\\\\\\'Technische gegevens"". The labels and the value we would like to see closer together. DONE4. Please delete the word ""BTW"" from all labels. DONE5. Please delete the word ""afkeur"" in ""Aantal afkeur"". DONE6. Please change ""gemiddeld gewicht"" into ""Gem. gewicht"". --> Please change to ""Gem. gew."" just to make it shorter.7. Please change ""Begin voorraad voer:"" in ""Beginvoorraad voer:"" and ""Begin voorraad tarwe:"" in ""Beginvoorraad tarwe:"" DONE8. Could you move everything one line down? DONEFor the \\\\\\\'Opzetgegevens\\\\\\\' we would like to move the columns from \\\\\\\'Aantal\\\\\\\' to \\\\\\\'Bedrag excl. BTW\\\\\\\' to the left so that they are aligned with the columns for \\\\\\\'Voerverbruik\\\\\\\'. The most right column will remain empty then. DONE\\\'\', ""Comment 111: \'[~mbovene@deheus.com],the printouts have been moved into prod Intense environment.You can feel free to test it.Best regards,Grzegorz\'"", \'Comment 112: \\\'This is still not correct on PROD:* Please change ""Begin voorraad voer:"" in ""Beginvoorraad voer:"" and ""Begin voorraad tarwe:"" in ""Beginvoorraad tarwe:""Next to this the department would like to use the new field ""Name Abbreviation"" in de Broederij (translated: Hatchery) section on the PDF as well. When this field is filled we should not mention the complete name of the corresponding hatchery but this abbreviation. !image-2!\\\'\', \'Comment 113: \\\'{quote}This is still not correct on PROD: * Please change ""Begin voorraad voer:"" in ""Beginvoorraad voer:"" and ""Begin voorraad tarwe:"" in ""Beginvoorraad tarwe:""Next to this the department would like to use the new field ""Name Abbreviation"" in de Broederij (translated: Hatchery) section on the PDF as well. When this field is filled we should not mention the complete name of the corresponding hatchery but this abbreviation.!image-2!{quote}This remarks have been adjusted on Prod environment.\\\'\', \'Comment 114: \\\'{quote}This is still not correct on PROD: * Please change ""Begin voorraad voer:"" in ""Beginvoorraad voer:"" and ""Begin voorraad tarwe:"" in ""Beginvoorraad tarwe:""Next to this the department would like to use the new field ""Name Abbreviation"" in de Broederij (translated: Hatchery) section on the PDF as well. When this field is filled we should not mention the complete name of the corresponding hatchery but this abbreviation.!image-2!{quote}Do wgrania też powyższe zmiany na TEST.\\\'\', ""Comment 115: \'[~damian.swistek@kotrak.com],zmiany również wgrane na TEST :).\'"", ""Comment 116: \'To change:{quote}We need to change something on the new financial statement.{quote}{quote}On the old printout you can clearly see the unit price of 1.23.Hovewer on the new overview the unit prices are a bit lower. This is because the “Bedrag excl.” is divided by the “Kg afkeur””. However"", ""Comment 117: this amount also includes all disapproves (AFKK/Afkeur).The calculation of the prices must be the “Bedrag excl.” divided by the (“Gewicht”-“Kg afkeur” so that the unit price is € 1.23.!image-2023-03-29-13-33-00-150.png!!image-2023-03-29-13-33-20-938.png!{quote}!image-2023-03-29-13-33-00-150! !image-2023-03-29-13-33-20-938!\'"", \'Comment 118: \\\'[~damian.swistek@kotrak.com],parametr ""Gem.gew"" jest liczony wg.:!image-2023-03-31-14-47-29-323.png!Zmienione to zostało na życzenie klienta.\\\'\', ""Comment 119: \'[~mbovene@deheus.com],the modification added to the Financial Statement prints (MAS NL and MAS BE) in TEST Intense environment.You can verify it.Best regards,Grzegorz\'"", ""Comment 120: \'[~damian.swistek@kotrak.com],zmieniłem to wyliczenie i aktualnie wyliczamy to tak:!image-2023-03-31-14-59-24-318.png!Zmiana wprowadzona na test"", ""Comment 121: czekamy na info od klienta.\'"", \'Comment 122: \\\'The ""Gem. gew."" is calculated wrong. This shouldn\\\\\\\'t have changed. !image-3!\\\'\', \'Comment 123: \\\'Also the ""Prijs excl."" is not calculated correct.\\\'\', \'Comment 124: \\\'I have the feeling that what is now presented in the column ""Gem. gew."" should have been in the column ""Prijs excl.""\\\'\', ""Comment 125: \'The change have been made on Test environment in MAS NL and MAS BE sectors.Please verify values of these 3 columns also when AFKH will be booked on some invoices.Now calculations looks like that: * Kg afkeur - weight of AFKK and also AFKH items are included - there are sum of these weigt from invoices. * Gem. gew. - Gewicht/Aantal"", ""Comment 126: in this case (35380/18700) = 1,892 * Prijs excl. - Bedrag excl. / Gewicht - Kg afkeur = 25664,3 € / 35380 - 15000 = 1,26 €!image-2023-04-07-12-58-20-393.png!Calculations of average weights have been also changed in task:https://helpdesk.kotrak.com/servicedesk/customer/portal/56/DGS-8732\'"", ""Comment 127: \'Zmienione na bazie testowej:!image-2023-04-07-12-58-20-393.png! * Kg afkeur - proceduryKR_Printout_FS2_Slaughtery iKR_Printout_FS2_Slaughtery_MAS_BE - dodana obsługa itemu AFKH!image-2023-04-07-13-20-19-089.png! * Gem. gew. -zmienione na wydruku!image-2023-04-07-13-20-34-469.png! * Prijs excl. - zmienione na wydruku!image-2023-04-07-13-18-20-314.png!\'"", \'Comment 128: ""After confirmation during today\\\'s call changes have been moved to production environmnent for MAS NL and MAS BE sectors.""\', ""Comment 129: \'Can be closed\']""]\nRelated Issues:\n[\'DGS-8053\', \'DGS-8428\', \'DGS-8325\', \'DGS-8067\', \'DGS-8641\', \'DGS-8732\', \'DGS-8714\', \'DGS-8877\']\n\n### End'}"
817,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8214\n\n### Instruction:\nGoodmorning,\r\n\r\nPlease, could you create an openingsbalance for item: 080017-Z25 with quantity of 17500 kg and for item: 303902-Z20 with a quantity of 1000 kg.\r\nBoth for the plant Andel.\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: \'!image-2023-01-02-10-10-00-311.png!!image-2023-01-02-10-10-16-732.png!!image-2023-01-02-10-10-00-311! !image-2023-01-02-10-10-16-732!\'"", ""Comment 3: \'Dear Gerard,Opening Balance for item 303902-Z20 has been created:!image-2023-01-02-10-16-07-127.png!Please"", ""Comment 4: let us know if item080017-Z25 should be bulk or pallet.Regards\'"", ""Comment 5: \'Hi Aleksandra,for item: 080017-Z25 is pallet.Regards,Gerard\'"", ""Comment 6: \'Opening balance for item080017-Z25 has been created.Regards!image-2023-01-02-11-20-56-140.png!\'"", ""Comment 7: \'Hello Aleksandra,Thanks!.Please"", ""Comment 8: close this ticket.Regards,Gerard\'"", ""Comment 9: \'Thank you.Regards\']""]\nRelated Issues:\n[]\n\n### End'}"
818,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8213\n\n### Instruction:\nHi, \r\n\r\n      On 2023, business would like to start with opening balance on clean DB. So, we do attach ""DHF_MM"". Application is able to do Sale Order, IR+ document. While generate SOR, we do receive error for ""WR-"" generation. Error message in attached. Please check. \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: \'Can you specify which database it is from the list of databases? !screenshot-1! \'"", ""Comment 4: \' !screenshot-2! \'"", ""Comment 5: \'This is in Food Sector. IP of Database is 10.95.1.42. And highlighted database is new one.!image-3!\'"", ""Comment 6: \'Hi"", ""Comment 7: We are not able to access to Application anymore. Please check!image-4!\'"", ""Comment 8: \'please check I connected this database one more time.\'"", ""Comment 9: \'please verify how it works now\'"", ""Comment 10: \'Most of Items are works now. Still attached items has issue. Please kindly check[^DHF_MM_Code_Issue_230103.xlsx] _(9 kB)_\'"", ""Comment 11: \'Regarding the sent list"", ""Comment 12: which document has an error when generating?Please give an example.\'"", ""Comment 13: \'When we generate WR- document from SOR and WR- document cannot confirm for those codes. Please reference attached as example. !image-5!\'"", ""Comment 14: \'RCA will be needed"", \'Comment 15: the stocks have been corrected\', \'Comment 16: but there may be new cases\', ""Comment 17: the problematic ones are:883486100031883486100033883486100043883486100045883486100050883486200047883486200064883486500010883486900072883486500022. Please confirm to create RCA.\'"", ""Comment 18: \'!image-2023-01-04-10-28-41-140.png!\'"", \'Comment 19: ""The operation of creating a new database and how it was made on your side was incorrect.Creating a new database from a copy and deleting data from the database is a mistake.The database has lost data integrity\', ""Comment 20: such operation is not allowed.It\'s not reversible for such operations and you also don\'t have a list of operations.- a new database should be done with information about the requirements for the newly created one.- the database has lost data integrity"", \'Comment 21: gives the result below with the number of errors(please look at the number of errors and it\\\'s still in progress): !screenshot-3! - as a result of such an operation the manufacturer\\\'s support will not be provided when it comes to XL.A GDC should be created.""\', ""Comment 22: \'Hi"", ""Comment 23: I see the issue. You can close to this ticket. I will raise GDC when I need it later. Thank you for your support.\']""]\nRelated Issues:\n[]\n\n### End'}"
819,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8212\n\n### Instruction:\nDears,\r\n\r\ni am trying to upload the attached file for new stock taking and i am getting the attached error.\r\n\r\nplease help as this we can\'t continue productuin, intake, and dispatch before new balances is in DHP.\n\n### Response:\n[""Comment 1: [\'[^DHP 3.0 - stocktaking Dec.xlsx] _(16 kB)_!image!\'"", \'Comment 2: ""Dears,i found an issue in item code 20\', \'Comment 3: i changed it\\\'s unit of measue to kg then balanced was upoloaded but can\\\'t be regisetred.i got new error as attached!!image-1!""\', ""Comment 4: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 5: \'Dears,i think the error is just making the user confused!you can close this issue as balaces was uploaded succesfully.\']""]\nRelated Issues:\n[]\n\n### End'}"
820,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8211\n\n### Instruction:\nWe have problem to delete the current inventory INV-338/2022, when we try to delete, system shows an error message.\r\nWe can\'t have any document opened to do the full inventory.\r\nCould you please delete this document?\r\n\r\nThank you\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello"", ""Comment 3: We kindly inform you that wecurrentlyare processing another Priority1 task. underDGS-8210We will revert to processing your task as soon as possible.Regards\'"", ""Comment 4: \'Please verify"", ""Comment 5: now it should be ok.\'"", \'Comment 6: ""Hi ŁukaszNow it\\\'s OK! You can close this task.Thank you very much""]\']\nRelated Issues:\n[]\n\n### End'}"
821,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8210\n\n### Instruction:\nWe have problem to close production SUR1461-P-MD, 0871201222006. System not allow to add reservations and not allow to close production too. The tab resources already have lot number for ingredients, looks like production closed with wrong status.\r\nCould you check why we have this error and fix it?\r\nThank you\r\n\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!!image-1!!image-2!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'z Loga{code:java}2022-12-30 15:09:55 (189e8e3a-6d92-4756-89f8-dbb1b0acca30/Plant.Prod.BusinessLogic/BR-4-SV-VM0204/24192/181) [Error] Kotrak.Common.Infrastructure.ICommandRunEnvironment - Error during Void Run[CreateProductionLotCommand](Plant.Prod.BusinessLogic.Application.Interfaces.ProductionLots.Commands.CreateProductionLotCommand) methodSystem.AggregateException: One or more errors occurred. (Response status code does not indicate success: 400 (Bad Request).) ---> Refit.ApiException: Response status code does not indicate success: 400 (Bad Request).   at Refit.RequestBuilderImplementation.<>c__DisplayClass14_0`2.<<BuildCancellableTaskFuncForMethod>b__0>d.MoveNext() in /_/Refit/RequestBuilderImplementation.cs:line 313   --- End of inner exception stack trace ---   at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions)   at System.Threading.Tasks.Task`1.GetResultCore(Boolean waitCompletionNotification)   at Plant.Prod.BusinessLogic.Infrastructure.ContextIntegration.ApiServices.StockEngine.StockEngineApi.ConfirmProductionLot(AggregateId productionLotId"", \'Comment 4: IEnumerable`1 settlementBasicData) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Infrastructure.ContextIntegration\\\\\\\\ApiServices\\\\\\\\StockEngine\\\\\\\\StockEngineApi.cs:line 178   at Castle.Proxies.Invocations.IStockEngineApi_ConfirmProductionLot.InvokeMethodOnTarget()   at Castle.DynamicProxy.AbstractInvocation.Proceed()   at Kotrak.Common.Infrastructure.Interceptors.ApiReferenceExceptionInterceptor.Intercept(IInvocation invocation)   at Castle.DynamicProxy.AbstractInvocation.Proceed()   at Castle.Proxies.IStockEngineApiProxy.ConfirmProductionLot(AggregateId productionLotId\', \'Comment 5: IEnumerable`1 settlementBasicData)   at Plant.Prod.BusinessLogic.Domain.ProductionLots.ConfirmProductionLotDomainService.ConfirmProductionLotWithStockEngineApiCall(ProductionLot productionLot\', \'Comment 6: ConfirmProductionLotActionData data\', \'Comment 7: Func`3 stockEngineApiCall) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Domain\\\\\\\\ProductionLots\\\\\\\\ConfirmProductionLotDomainService.cs:line 122   at Plant.Prod.BusinessLogic.Domain.ProductionLots.ConfirmProductionLotDomainService.ConfirmProductionLot(ProductionLot productionLot\', \'Comment 8: ConfirmProductionLotActionData data) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Domain\\\\\\\\ProductionLots\\\\\\\\ConfirmProductionLotDomainService.cs:line 68   at Plant.Prod.BusinessLogic.Application.ProductionLots.ProductionLotService.CreateProductionLot(CreateProductionLotActionData data) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Application\\\\\\\\ProductionLots\\\\\\\\ProductionLotService.cs:line 187   at Plant.Prod.BusinessLogic.Application.ProductionLots.CommandHandlers.CreateProductionLotCommandHandler.Handle(CreateProductionLotCommand command) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Application\\\\\\\\ProductionLots\\\\\\\\CommandHandlers\\\\\\\\CreateProductionLotCommandHandler.cs:line 51   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)2022-12-30 15:09:55 (/Plant.Prod.BusinessLogic/BR-4-SV-VM0204/24192/181) [Error] Serilog.AspNetCore.RequestLoggingMiddleware - HTTP ""POST"" ""/api/productionLot/create"" responded 500 in 1116.1225 ms{code}\\\'\', \'Comment 9: ""Host{code:java}022-12-30 15:04:16 (1d749a6a-4578-4479-a4ca-f90e61604607/Plant.Prod.BusinessLogic/BR-4-SV-VM0204/24192/217) [Warning] Microsoft.EntityFrameworkCore.Query - Compiling a query which loads related collections for more than one collection navigation\', ""Comment 10: either via \'Include\' or through projection"", ""Comment 11: but no \'QuerySplittingBehavior\' has been configured. By default"", ""Comment 12: Entity Framework will use \'QuerySplittingBehavior.SingleQuery\'"", ""Comment 13: 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))\'.2022-12-30 15:04:16 (1d749a6a-4578-4479-a4ca-f90e61604607/Plant.Prod.BusinessLogic/BR-4-SV-VM0204/24192/217) [Warning] Microsoft.EntityFrameworkCore.Query - Compiling a query which loads related collections for more than one collection navigation"", ""Comment 14: either via \'Include\' or through projection"", ""Comment 15: but no \'QuerySplittingBehavior\' has been configured. By default"", ""Comment 16: Entity Framework will use \'QuerySplittingBehavior.SingleQuery\'"", ""Comment 17: 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))\'.2022-12-30 15:04:16 (1d749a6a-4578-4479-a4ca-f90e61604607/Plant.Prod.BusinessLogic/BR-4-SV-VM0204/24192/217) [Warning] Microsoft.EntityFrameworkCore.Query - Compiling a query which loads related collections for more than one collection navigation"", ""Comment 18: either via \'Include\' or through projection"", ""Comment 19: but no \'QuerySplittingBehavior\' has been configured. By default"", ""Comment 20: Entity Framework will use \'QuerySplittingBehavior.SingleQuery\'"", \'Comment 21: 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 22: \'!image-2022-12-30-19-24-25-193.png!\'"", ""Comment 23: \'!image-2022-12-30-19-25-49-744.png!\'"", ""Comment 24: \'!image-2022-12-30-19-30-37-868.png!\'"", ""Comment 25: \'DearPriscyla,What status should be correct?Regards\'"", \'Comment 26: ""Aleksandra,I don\\\'t know what happened with this production\', \'Comment 27: do you know?Should be possible confirm production (editing the reservations) or with confirmed.Please confirm production if is better. Thank you""\', ""Comment 28: \'Would it be possible to cancel this PLR and create a new one?Regards\'"", ""Comment 29: \'No"", ""Comment 30: we already created all documents with this lot number and loaded in VT.\'"", ""Comment 31: \'Aleksandra,could you confirm the production?\'"", ""Comment 32: \'Hi Priscyla,The operation of system was in line with the assumptions.. In this one case"", \'Comment 33: we changed the configuration of DHP. Production settlement basing on ""Mixed"" (standard - ""By delivery"").!image-2022-12-30-22-06-52-598.png!After the change\', \'Comment 34: the production was confirmed. If we need to change the configuration permanently\', ""Comment 35: please let me know.!image-2022-12-30-22-06-35-709.png!Please verify and please give us a feedback.!image-2022-12-30-22-06-52-598!\'"", \'Comment 36: ""Hi ŁukaszWe can\\\'t change to Mixed. There\\\'s an internal quality rule that demands to be *By Delivery* as it is now.Thank you!You can close this task""]\']\nRelated Issues:\n[\'DGS-8475\']\n\n### End'}"
822,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8209\n\n### Instruction:\nwe have problem with reservation for item GLN2217-S25, barcode 88-W0FB4D, we don\'t have any document opened but we have reservation for the item.  \r\n It\'s urgent because we have full inventory on monday. Could you please fix this item reservation?\r\n\r\nThank you\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'!image-2022-12-30-15-20-44-196.png!\'"", ""Comment 4: \'Hi,Reservation has been corrected.Please"", ""Comment 5: verify.Regards\'"", ""Comment 6: \'[^dgs-8209.xlsx]\'"", ""Comment 7: \'[^dgs-8209.xlsx]\'"", \'Comment 8: ""Hello,I checked and now it\\\'s correct. You can close this task.thank you.""]\']\nRelated Issues:\n[]\n\n### End'}"
823,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8208\n\n### Instruction:\nplease check why did system asigne the old serial number, truck was loaded only one delivery 0211301222017  \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: \'Kolejny przykład błędnie przypisanej serii"", ""Comment 4: powinna być 0211030123031!image-1!\'"", ""Comment 5: \'{code:java}SELECT TOP (1000) [Del_SerialNumber],[Del_Id],*       FROM [DHP_Grodzisk].[dbo].[Delivery]  where Del_Id in( select vte_vtdid   FROM [DHP_Grodzisk].[dbo].[VehicleTicketElement]  where VtE_VtHId=196250)  select vte_vtdid,VtE_Series,*   FROM [DHP_Grodzisk].[dbo].[VehicleTicketElement]  where VtE_VtHId=196250  select *  FROM [DHP_Grodzisk].[dbo].[VehicleTicketHeader]  where VtH_Id = 196250{code} !screenshot-1!  !screenshot-2! \'"", ""Comment 6: \'Hello.You can see in the log that changes were made: !screenshot-3!  !screenshot-4! it looks like the operator changed the field from the DHP level - can you contact the operator? Were such changes made?Regards.\'"", ""Comment 7: \'yes"", \'Comment 8: operators do some changes on VT items\', ""Comment 9: they correct serial numbers and deliveries to the correct ones after the truck is already loaded and leaves the factory\'"", ""Comment 10: \'Can we get information before the changes?to my phone 538 212 172 for example.\'"", ""Comment 11: \'the screens below are before the changes\'"", ""Comment 12: \'According to the change log the delivery number 0211301222017 was added as the first,0211291022014 was as the second.The old serial number - what do you mean? Thanks.\'"", ""Comment 13: \'1. old series - 02112910220142. According to the change log the delivery number 0211301222017 was added as the first"", ""Comment 14: 0211291022014 was as the second - by whom?\'"", ""Comment 15: \'you can check the change logs by date as below([dbo].[VehicleTicketElementLog]) !screenshot-5!  !screenshot-6! \'"", ""Comment 16: \'yes"", ""Comment 17: but the uses are NULL!image-2!\'"", ""Comment 18: \'klient przekazał że zmiana przez operatora odpada :P\'"", ""Comment 19: \'[~piotr.gaczorek@kotrak.com],Są dwa sposoby automatycznego uzupełniania numeru serii na podstawie informacji z produkcji:# na podstawie komunikatu z PCS jaki konkretny numer serii procedura FinishTransfer parametr @predictedLotNumber# jeżeli @predictedLotNumber jest pusty to informacja na temat numerów seryjnych pobierana jest z tabeli VehicleTicketElementRelease czyli to co zostało wyliczone na podstawie FIFO w oparciu o stany magazynowe silosów na ekspedycji - jeżeli numery seryjne są błędne może to wynika z błędnych stanów magazynowych na tych zbiornikach. Informacje o serial rozdzielone są przecinkiem (procedura: FinishTransfer).Jeżeli chcą analizować dlaczego to trzeba każdy przypadek z osobna przeanalizować. Proces jest czasochłonny i dość skomplikowany.\'"", ""Comment 20: \'Mam takie  !screenshot-7! Przykład -   select *  FROM [DHP_Grodzisk].[dbo].[VehicleTicketHeader]  where VtH_Id = 196250Skąd dostawa z X. !image-2023-01-10-08-13-36-745!\'"", ""Comment 21: \'The analysis will be performed by the developers only because of the complexity of completing the series field. Each case must be analyzed separately. The valuation of a single case analysis is 3-4 hours (currently 1.5 hours are logged in).Please accept and provide an example VT for analysis or can it be the one discussed earlier(VtH_Id = 196250)?\'"", ""Comment 22: \'yes"", ""Comment 23: it can be\'"", ""Comment 24: \'jest akceptacja - czy do Ciebie"", ""Comment 25: albo Tomka?\'"", ""Comment 26: \'[~piotr.gaczorek@kotrak.com] do Tomka Nojka przypisz. Na razie przepnę na Ciebie jak Tomek wróci bo jest na urlopie to z nim pogadaj proszę.\'"", ""Comment 27: \'any news?\'"", ""Comment 28: \'Dla VT-25282/12/22 PCS zarejestrował o godzinie 11:39 załadunek 23 460 kg z dwóch zbiorników: * 13 600 kg ze zbiornika ekspedycyjnego nr 820 *  9 860 kg ze zbiornika ekspedycyjnego nr 814Dla zbiornika 820 po ostatnim czyszczeniu PCS zarejestrował transfer 14 000 kg z produkcji 0211301222017 (zaznaczono kolorem niebieskim).Numer seryjny tej produkcji został wpisany do serii elementu VT prawidłowo.Dla zbiornika 814 po ostatnim czyszczeniu nie zarejestrowano żadnego transferu z produkcji"", \'Comment 29: więc system nie wiedział jaką produkcję rozliczyć dla wydania luzu.W takiej sytuacji system szuka ostatniej produkcji\', \'Comment 30: która była na tym zbiorniku i dotyczy tej samej paszy\', \'Comment 31: która jest na elemencie VT.Dla analizowanego przypadku ostatnią produkcją na zbiorniku 814 z ArticleId = 27714 był lot 0211291022014 (zaznaczono kolorem czerwonym).Taki też numer seryjny został wpisany na elemencie VT.Transfer produkcji 0211301222017 do zbiornika 814 został zarejestrowany przez PCS o 11:55\', \'Comment 32: czyli 16 minut po zarejestrowaniu załadunku na samochód (zaznaczono kolorem zielonym).Gdyby został zarejestrowany wcześniej\', ""Comment 33: wydanie luzu na VT zostałoby rozliczone prawidłowo.!image-2023-01-24-15-53-30-599.png!\'"", ""Comment 34: \'[~tomasz.nojek@kotrak.com] wielkie dzięki!\'"", ""Comment 35: \'Tomek wszystko jasne"", \'Comment 36: ten przykład chyba nie był najlepszym\', \'Comment 37: rzeczywiście powinno być tak jak piszesz. Zerknij może lepiej na VT 1510/01/23. Tutaj system przypisał produkcję z września\', ""Comment 38: która na dodatek zasypana była na inny zbiornik!image-3!!image-4!!image-5!\'"", ""Comment 39: \'Hi Ewelina"", ""Comment 40: we need 3h for analysis next example - please confirm.\'"", ""Comment 41: \'ok"", \'Comment 42: but we will see where was a problem. I can add that 3h is too much\', \'Comment 43: we have many similar examples no registered\', ""Comment 44: if we start to register each example we will pay much may. We will see the result of these analisies and decide what later \'"", ""Comment 45: \'jest potwierdzenie na kolejny przypadek.\'"", ""Comment 46: \'[~ewardega@deheus.com]W przypadkuVT-1510/01/23 transfer lotu0211230123023 z produkcji do zbiornika ekspedycyjnego855 (zaznaczono kolorem niebieskim) został zarejestrowany półtorej godziny po rozpoczęciu załadunku na samochód (zaznaczono kolorem zielonym). Zgodnie z informacjami z PCS zbiornik 855 był pusty w momencie załadunku (brak transferów z produkcji po ostatnim czyszczeniu zbiornika - zaznaczono kolorem czerwonym)"", \'Comment 47: więc system nie wiedział który lot zarejestrować na elemencie VT. Ponieważ na zbiorniku ekspedycyjnym 855 nigdy nie było paszyDD0A2H00K-L00\', \'Comment 48: to system wybrał losowy lot (może po FIFO na stanie magazynowym\', ""Comment 49: nie jestem pewien).!image-2023-01-25-13-16-36-440.png!\'"", ""Comment 50: \'[~maciej.dobrzanski@kotrak.com]  [~piotr.gaczorek@kotrak.com]Przygotowałem [skrypt|https://kotrak-my.sharepoint.com/:u:/p/tomasz_nojek/EfNWQUyPrwpElel6vhVkRFMB4iRH9cXWXMg8NAroulKOzg?e=HNGxWr]"", \'Comment 51: który przyspieszy analizę kolejnych VT - mniej więcej 30 min na VT. Może nie obsługuje wszystkich możliwości\', \'Comment 52: ale dla zdecydowanej większości przypadków wystarczy.Wywołanie procedury na bazie Exchange:{code:java}SELECT *FROM dbo.BulkDispatchCheck(1510\', ""Comment 53: 2023)ORDER BY Id;{code}\'"", ""Comment 54: \'właśnie potrzebujemy odpowiedzi na to Twoje kluczowe pytanie:) raczej nie FIFO po stanie magazynowym"", \'Comment 55: bo były tylko w ogóle dwie produkcje i nie było na stanie\', \'Comment 56: tylko przypisał do ostatniego lotu w ogóle\', \'Comment 57: nie ważne\', \'Comment 58: że na stanie nie było. Możesz nam to potwierdzić? A co w przypadku takiej sytuacji\', \'Comment 59: gdyby to była pierwsza produkcja\', \'Comment 60: załadunek w trakcie produkcji i komunikaty z PCS o zasypach na silos z jakiegoś powodu przyszły z opóźnieniem\', ""Comment 61: co wtedy system przypisze? nie ma nic w historii tego towaru \'"", ""Comment 62: \'wiedziałam"", \'Comment 63: że kto jak kto ale Tomek nie potrzebuje 3h\', ""Comment 64: 1h była enough:)\'"", ""Comment 65: \'{code:java}if (@delId is null)begin    set @delId = (select top 1 Del_Id from dbo.Delivery where Del_ArtId = @artId and Del_PlhId is not null order by Del_Id)end{code}Jeżeli na danym zbiorniku ekspedycyjnym nigdy nie było tego towaru"", \'Comment 66: to system bierze pierwszą (najstarszą w systemie) dostawę dla tego towaru\', \'Comment 67: która pochodzi z produkcji. Gdyby to była pierwsza produkcja na ten towar (czyli jedyna w systemie)\', \'Comment 68: to system wybrałby właśnie ją. Jeżeli w systemie nie byłoby żadnej dostawy dla tego towaru\', ""Comment 69: to poleciałby błąd i załadunek nie zostałby zarejestrowany.\'"", ""Comment 70: \'dzięki Tomek"", ""Comment 71: clear:) task do zamknięcia\'"", ""Comment 72: \'[[DHP 2.X] Serie na VT"", \'Comment 73: pobieranie dostaw dla realizacji VT\', \'Comment 74: seria\', ""Comment 75: serial number.|onenote:https://kotrak.sharepoint.com/sites/erpasysta/Shared%20Documents/Baza%20wiedzy/Baza%20Wiedzy%20-%20ERPSD/Klienci/DEHEUS/DEHEUS%20APPLICATIONS/Polska/Baza%20wiedzy/DHP.one#%5bDHP%202.X%5d%20Serie%20na%20VT,%20pobieranie%20dostaw%20dla&section-id=\\\\\\\\{F3B54834-6A02-4FD8-B2D4-74ADCAEDC4E9}&page-id=\\\\\\\\{48D92B44-27F3-4D3B-8D4F-22E9B7C48076}&end] ([Widok sieci Web|https://kotrak.sharepoint.com/sites/erpasysta/_layouts/OneNote.aspx?id=%2Fsites%2Ferpasysta%2FShared%20Documents%2FBaza%20wiedzy%2FBaza%20Wiedzy%20-%20ERPSD&wd=target%28Klienci%2FDEHEUS%2FDEHEUS%20APPLICATIONS%2FPolska%2FBaza%20wiedzy%2FDHP.one%7CF3B54834-6A02-4FD8-B2D4-74ADCAEDC4E9%2F%5BDHP%202.X%5D%20Serie%20na%20VT%2C%20pobieranie%20dostaw%20dla%7C48D92B44-27F3-4D3B-8D4F-22E9B7C48076%2F%29])\']""]\nRelated Issues:\n[\'DGS-8279\']\n\n### End'}"
824,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8207\n\n### Instruction:\nGood afternoon,\r\n\r\nplease would you create an openingsbalance for item: 505020-Z20 with a quantity of 100 kg en for item: 303040-Z20 a quantity of 500 kg. Both for plant Andel.\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: \'Hi,Opening balances have been created.Regards!image-2023-01-02-07-26-47-162.png!!image-2023-01-02-07-28-58-588.png!\'"", ""Comment 3: \'Good morning Aleksandra,Happy New Year !!Thanks for yor support.Kind regards,Gerard\'"", ""Comment 4: \'Aleksandra,You may close this ticket.Regards,Gerard\'"", ""Comment 5: \'Thank you for your information.All the best in New Year!Regards\']""]\nRelated Issues:\n[]\n\n### End'}"
825,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8206\n\n### Instruction:\nTheo reported some Feed Sale lines are missing in Intense (enclosed prnscreen). Damian prepared a list of deleted feed sale lines (request during Kotrak\'s visit at DH).\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'[^Deleted_FeedSale_positions.xlsx]\'"", ""Comment 3: \'[^Feed Sales Lines Updated- Duplicated Lines Deleted.msg]\'"", ""Comment 4: \'Waiting for feedback from DH\'"", ""Comment 5: \'16.12.2022 wysłane przez Tomka także zestawienie Deleted_FeedSale_positions z usuniętymi liniami feed sale\'"", ""Comment 6: \'Confirmed that can be closed.\']""]\nRelated Issues:\n[]\n\n### End'}"
826,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8205\n\n### Instruction:\nHello, \r\n\r\nplease link the attached lots to the relevant job orders \r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'hello"", ""Comment 4: please link 0705291222003 as well!image-1!\'"", ""Comment 5: \'Hello Thabile,PLRs are linked to JO. Please"", ""Comment 6: verify.Regards\'"", ""Comment 7: \'Hello,Can we close this task?Regards\'"", ""Comment 8: \'Hello"", ""Comment 9: please can  you link this one as well !image-2!\'"", ""Comment 10: \'Hello,Documents are linked. Please"", ""Comment 11: verify.!image-2023-01-03-10-10-56-831.png|width=1163,height=225!Regards\'"", ""Comment 12: \'Hello"", ""Comment 13: all documents are linked thank you. \']""]\nRelated Issues:\n[]\n\n### End'}"
827,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8204\n\n### Instruction:\nHi,\r\nWe can not create Version 0 sub x in DHC.\r\nPlease kindly help check because we have to change bag for missing stock\r\ntask should be P1\r\nWe have 3 codes same issue:\r\nRD151-B10\r\nRD152-B10\r\nRD153-B10\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,there is already such additional technology.!image-2022-12-30-08-19-52-487.png!We can change the Technology Code to create another subversion.Please confirm.\'"", \'Comment 4: ""hi,That\\\'s problem. we need create Sub 1 but they not allow us to do that""\', ""Comment 5: \'hi,I know how to do it"", ""Comment 6: please close the ticket\'"", ""Comment 7: \'[Additional Technology Can not create Version|onenote:https://kotrak.sharepoint.com/sites/erpasysta/Shared%20Documents/Baza%20wiedzy/Baza%20Wiedzy%20-%20ERPSD/Klienci/DEHEUS/DEHEUS%20APPLICATIONS/Wietnam/Baza%20wiedzy.one#Additional%20Technology%20Can%20not%20create%20Version&section-id=\\\\\\\\{2B12CDB9-0ACA-4E3F-B40E-E88F97AD3C58}&page-id=\\\\\\\\{510A4A06-A670-4CFB-B12E-6C3DFA1DBCE9}&end] ([Widok sieci Web|https://kotrak.sharepoint.com/sites/erpasysta/_layouts/OneNote.aspx?id=%2Fsites%2Ferpasysta%2FShared%20Documents%2FBaza%20wiedzy%2FBaza%20Wiedzy%20-%20ERPSD&wd=target%28Klienci%2FDEHEUS%2FDEHEUS%20APPLICATIONS%2FWietnam%2FBaza%20wiedzy.one%7C2B12CDB9-0ACA-4E3F-B40E-E88F97AD3C58%2FAdditional%20Technology%20Can%20not%20create%20Version%7C510A4A06-A670-4CFB-B12E-6C3DFA1DBCE9%2F%29])\']""]\nRelated Issues:\n[]\n\n### End'}"
828,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8203\n\n### Instruction:\nWe have some documents in Warehouse Orders with execution pending, but the VTs were already closed.\r\n\r\nCould you please close the Warehouse orders?\r\n\r\nThank you\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'close these documents are urgent because on monday we have full inventory and the barcodes are reserved yet.\'"", ""Comment 3: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 4: \'VT są z IX a eventy od X !screenshot-1!  !screenshot-2! \'"", ""Comment 5: \'Please check and send a feedback "", ""Comment 6: all documents should be now in correct status.\'"", ""Comment 7: \'Hello Piotr,I checked and now is correct. You can close this task. Thank you.\'"", ""Comment 8: \'[[DHP 3.0]Incorrect WO status|onenote:https://kotrak.sharepoint.com/sites/erpasysta/Shared%20Documents/Baza%20wiedzy/Baza%20Wiedzy%20-%20ERPSD/Klienci/DEHEUS/DEHEUS%20APPLICATIONS/RPA/Baza%20wiedzy.one#%5bDHP%203.0%5dIncorrect%20WO%20status&section-id=\\\\\\\\{A2F09CD6-A23A-42F3-92F5-ED66B521455B}&page-id=\\\\\\\\{325B9921-0AB5-4E36-A871-095DF356E2F1}&end] ([Widok sieci Web|https://kotrak.sharepoint.com/sites/erpasysta/_layouts/OneNote.aspx?id=%2Fsites%2Ferpasysta%2FShared%20Documents%2FBaza%20wiedzy%2FBaza%20Wiedzy%20-%20ERPSD&wd=target%28Klienci%2FDEHEUS%2FDEHEUS%20APPLICATIONS%2FRPA%2FBaza%20wiedzy.one%7CA2F09CD6-A23A-42F3-92F5-ED66B521455B%2F%5BDHP%203.0%5DIncorrect%20WO%20status%7C325B9921-0AB5-4E36-A871-095DF356E2F1%2F%29])\']""]\nRelated Issues:\n[]\n\n### End'}"
829,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8202\n\n### Instruction:\nWe need to cancel some production, was not produced and we cancelled in PCS, but it\'s not possible cancel in DHP because the status is finished.\r\nWe need to have these productions cancelled till tomorrow, because on monday we have full inventory (Yearly). Lot number attached.\r\n\r\nCould you please cancel the production in DHP?\r\n\r\nThank you\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'{code:java}08710111220090871271022001087125102202208712712220120871291222002{code}\'"", \'Comment 4: ""PLR\\\'s have been canceled.""\', ""Comment 5: \'Hello Piotr,I checked and now they are correct. You can close this task. Thank you.\'"", ""Comment 6: \'[[DHP 3.0] anulowanie PLR|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%20anulowanie%20PLR&section-id=\\\\\\\\{05DF1439-683C-45FE-8260-61E2EC66DC91}&page-id=\\\\\\\\{C767319F-E126-406E-9C0F-3F94070E64EC}&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%20anulowanie%20PLR%7CC767319F-E126-406E-9C0F-3F94070E64EC%2F%29])\']""]\nRelated Issues:\n[]\n\n### End'}"
830,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8201\n\n### Instruction:\nWe need to cancel production 0851291122001, was not produced and we cancelled in PCS, but it\'s not possible cancel in DHP because the status is finished.\r\n\r\nCould you please cancel the production in DHP?\r\n\r\nThank you\n\n### Response:\n[""Comment 1: [\'We need to have this production cancelled till tomorrow"", ""Comment 2: because on monday we have full inventory (Yearly)\'"", ""Comment 3: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 4: \'PLR has been canceled.\'"", ""Comment 5: \'[[DHP 3.0] anulowanie PLR|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%20anulowanie%20PLR&section-id=\\\\\\\\{05DF1439-683C-45FE-8260-61E2EC66DC91}&page-id=\\\\\\\\{C767319F-E126-406E-9C0F-3F94070E64EC}&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%20anulowanie%20PLR%7CC767319F-E126-406E-9C0F-3F94070E64EC%2F%29])\'"", ""Comment 6: \'Hello Piotr,I checked and now is correct. Thank you.\'"", ""Comment 7: \'Thank you for confirmation.\']""]\nRelated Issues:\n[]\n\n### End'}"
831,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8200\n\n### Instruction:\nA few weeks ago I asked to delete some rounds, while the next round was on a new contract, bet the next round was already opened on the new round. The rounds were deleted, but the round number didn\'t change. So at the moment of creation, round 1 on the new contract had number 3 and round 2 on the old contract had number 2. As this one was deleted, round 1 on the new contract should become round 2 in total. This is the case for the following rounds:\r\nB004922/0235/0001 (ID 79108): round number 3 --> 2 \r\nB003437/0224/0001 (ID 74838): round number 4 --> 3\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: \'Documents numbers are updated\']""]\nRelated Issues:\n[]\n\n### End'}"
832,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8199\n\n### Instruction:\nMatching invoice and payment gives warning\r\n\r\nAftherwards there are problems with age analysis.\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: \'HiThese documents cannot be matched because they differ in currency"", ""Comment 4: some of them are entered in EUR and some in USD. !screenshot-1!  !screenshot-2!  !screenshot-3!  !screenshot-4! I could reset the USD value on each of these documents and settle them. The value on account USD31-00909 will be zero.orI could enter AN documents with the same currencies and rates for each of these entries and match them.Best Regards,Beata\'"", ""Comment 5: \'Requester is checking\'"", ""Comment 6: \'Is it possible for the user to do it by himself?!image-1!\'"", ""Comment 7: \'[^Clearings.docx]\'"", ""Comment 8: \'I am attaching a short instruction on how to settle these documents. [^Clearings.docx] Please"", \'Comment 9: check this\', ""Comment 10: and give me some feedback if it is understandable?\'"", ""Comment 11: \'I have asked the user if it is oke.Waiting for an answer\'"", ""Comment 12: \'Can be closed\']""]\nRelated Issues:\n[]\n\n### End'}"
833,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8198\n\n### Instruction:\nThis  VTs listed didn`t reached to DHC but they are closed on DHP and processed.  \r\n                \r\n+ missing VTs     \r\n26-Dec-2022 (VTs 1182-1242)                     \r\n27-Dec-2022  (VTs 1243-1270)       \r\n28-Dec  (VTs 1346-1363)\r\n\n\n### Response:\n[""Comment 1: [\' Hey Dear  We were about to send annual and monthly financial report but this incident is holding us Back ;  {color:#172B4D}This VTs listed didn`t reached to DHC but they are closed on DHP and processed.{color} {color:#172B4D}+ missing VTs 26-Dec-2022 (VTs 1182-1242) 27-Dec-2022 (VTs 1243-1270) 28-Dec (VTs 1346-1363){color}  Thanks in advance for accepting to help us !\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'!image-2022-12-29-15-04-59-681.png!\'"", ""Comment 4: \'!image-2022-12-29-15-08-06-169.png!\'"", ""Comment 5: \'!image-2022-12-29-15-10-36-852.png!\'"", ""Comment 6: \'!image-2022-12-29-15-16-05-288.png!\'"", \'Comment 7: \\\'Z Integration też leciał timeout{code:java}2022-12-29 10:48:15 (29382dc5-8a05-4683-86b0-ae9a945d56b5/Plant.DHC.Integration/ETDB04/13920/9) [Error] Kotrak.Integration.IntegrationPluginCommon.IntercontextCommunication.Inbound.InboundIntercontextErrorHandler - Error during handling message of type ""Plant.VC.BusinessLogic.DomainAbstractions.VehicleTickets.DomainEvents.VehicleTicketReleasedForIntakeEvent""\', \'Comment 8: retry no 0Kotrak.Integration.IntegrationPluginCommon.Interfaces.ConnectionBrokenException: Internal server error ---> System.ServiceModel.FaultException: Internal server error   at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime operation\', \'Comment 9: ProxyRpc& rpc)   at System.ServiceModel.Channels.ServiceChannel.Call(String action\', \'Comment 10: Boolean oneway\', \'Comment 11: ProxyOperationRuntime operation\', \'Comment 12: Object[] ins\', \'Comment 13: Object[] outs\', \'Comment 14: TimeSpan timeout)   at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(MethodCall methodCall\', \'Comment 15: ProxyOperationRuntime operation)   at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(MethodInfo targetMethod\', \'Comment 16: Object[] args)--- End of stack trace from previous location where exception was thrown ---   at System.Reflection.DispatchProxyGenerator.Invoke(Object[] args)   at generatedProxy_1.PushDraftVehicleTicket(Package`1 )   at Plant.Integration.DhcService.Communication.BasePushService`1.PushPackage(IDhcService dhcService\', \'Comment 17: Package`1 package) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\e810c04f78ab209c\\\\\\\\Plant.Integration.DhcService\\\\\\\\Plant.Integration.DhcService.Communication\\\\\\\\BasePushService.cs:line 28   --- End of inner exception stack trace ---   at Plant.Integration.DhcService.Communication.BasePushService`1.PushPackage(IDhcService dhcService\', \'Comment 18: Package`1 package) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\e810c04f78ab209c\\\\\\\\Plant.Integration.DhcService\\\\\\\\Plant.Integration.DhcService.Communication\\\\\\\\BasePushService.cs:line 36   at Plant.Integration.DhcService.Communication.BasePushService`1.CallService(IDhcService dhcService\', \'Comment 19: Package`1 package) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\e810c04f78ab209c\\\\\\\\Plant.Integration.DhcService\\\\\\\\Plant.Integration.DhcService.Communication\\\\\\\\BasePushService.cs:line 60   at Plant.Integration.DhcService.Application.PushDataFilter`1.Process(PackageIntegrationState input) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\e810c04f78ab209c\\\\\\\\Plant.Integration.DhcService\\\\\\\\Plant.Integration.DhcService.Application\\\\\\\\PushDataFilter.cs:line 28   at Kotrak.Integration.Pipeline.PredefinedFilters.FilterBase`1.Execute(T input)   at Kotrak.Integration.Pipeline.PredefinedFilters.FilterBase`1.Execute(T input)   at Kotrak.Integration.Pipeline.Pipeline`1.Excecute(T input)   at Plant.Integration.DhcService.Infrastructure.Handlers.BaseInboundMessageHandler`1.Handle(TEvent message) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\e810c04f78ab209c\\\\\\\\Plant.Integration.DhcService\\\\\\\\Plant.Integration.DhcService.Infrastructure\\\\\\\\Handlers\\\\\\\\BaseInboundMessageHandler.cs:line 33   at Kotrak.Integration.IntegrationPluginCommon.IntercontextCommunication.Inbound.IntercontextInboundHandler`2.Handle(InternalStorageDto message)2022-12-29 10:55:39 (0a9b51a6-9088-4cd1-8c13-8112b9071651/Plant.DHC.Integration/ETDB04/13920/9) [Error] Plant.Integration.DhcService.Infrastructure.Handlers.BaseInboundMessageHandler - DraftVehicleTicketIntakePipelineExecutor execution errorKotrak.Integration.IntegrationPluginCommon.Interfaces.ConnectionBrokenException: Internal server error ---> System.ServiceModel.FaultException: Internal server error   at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime operation\', \'Comment 20: ProxyRpc& rpc)   at System.ServiceModel.Channels.ServiceChannel.Call(String action\', \'Comment 21: Boolean oneway\', \'Comment 22: ProxyOperationRuntime operation\', \'Comment 23: Object[] ins\', \'Comment 24: Object[] outs\', \'Comment 25: TimeSpan timeout)   at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(MethodCall methodCall\', \'Comment 26: ProxyOperationRuntime operation)   at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(MethodInfo targetMethod\', \'Comment 27: Object[] args)--- End of stack trace from previous location where exception was thrown ---   at System.Reflection.DispatchProxyGenerator.Invoke(Object[] args)   at generatedProxy_1.PushDraftVehicleTicket(Package`1 )   at Plant.Integration.DhcService.Communication.BasePushService`1.PushPackage(IDhcService dhcService\', \'Comment 28: Package`1 package) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\e810c04f78ab209c\\\\\\\\Plant.Integration.DhcService\\\\\\\\Plant.Integration.DhcService.Communication\\\\\\\\BasePushService.cs:line 28   --- End of inner exception stack trace ---   at Plant.Integration.DhcService.Communication.BasePushService`1.PushPackage(IDhcService dhcService\', \'Comment 29: Package`1 package) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\e810c04f78ab209c\\\\\\\\Plant.Integration.DhcService\\\\\\\\Plant.Integration.DhcService.Communication\\\\\\\\BasePushService.cs:line 36   at Plant.Integration.DhcService.Communication.BasePushService`1.CallService(IDhcService dhcService\', ""Comment 30: Package`1 package) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\e810c04f78ab209c\\\\\\\\Plant.Integration.DhcService\\\\\\\\Plant.Integration.DhcService.Communication\\\\\\\\BasePushService.cs:line 60   at Plant.Integration.DhcService.Application.PushDataFilter`1.Process(PackageIntegrationState input) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\e810c04f78ab209c\\\\\\\\Plant.Integration.DhcService\\\\\\\\Plant.Integration.DhcService.Application\\\\\\\\PushDataFilter.cs:line 28   at Kotrak.Integration.Pipeline.PredefinedFilters.FilterBase`1.Execute(T input)   at Kotrak.Integration.Pipeline.PredefinedFilters.FilterBase`1.Execute(T input)   at Kotrak.Integration.Pipeline.Pipeline`1.Excecute(T input)   at Plant.Integration.DhcService.Infrastructure.Handlers.BaseInboundMessageHandler`1.Handle(TEvent message) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\e810c04f78ab209c\\\\\\\\Plant.Integration.DhcService\\\\\\\\Plant.Integration.DhcService.Infrastructure\\\\\\\\Handlers\\\\\\\\BaseInboundMessageHandler.cs:line 332{code}\'"", ""Comment 31: \'Brak errorow dla vt"", ""Comment 32: logi textowe tez puste!image-2022-12-29-16-28-22-125.png!\'"", ""Comment 33: \'Naglowki wskazanych VT (prawie 100 VT"", \'Comment 34: sa w DHC i Service\', ""Comment 35: natomiast nie przeszly elementy!image-2022-12-29-16-29-41-955.png!\'"", ""Comment 36: \'jeszcze z modułu VC z wczoraj{code:java}2022-12-28 19:47:00 (/Plant.VC.BusinessLogic/ETDB04/9872/4) [Error] Kotrak.Common.Infrastructure.CleanEventsTask - Problem with data cleaning task executionSystem.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.SqlInternalConnection.OnError(SqlException exception"", \'Comment 37: Boolean breakConnection\', \'Comment 38: Action`1 wrapCloseInAction)   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj\', \'Comment 39: Boolean callerHasConnectionLock\', \'Comment 40: Boolean asyncClose)   at System.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject stateObj\', \'Comment 41: UInt32 error)   at System.Data.SqlClient.TdsParserStateObject.ReadSniSyncOverAsync()   at System.Data.SqlClient.TdsParserStateObject.TryReadNetworkPacket()   at System.Data.SqlClient.TdsParserStateObject.TryPrepareBuffer()   at System.Data.SqlClient.TdsParserStateObject.TryReadByte(Byte& value)   at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior\', \'Comment 42: SqlCommand cmdHandler\', \'Comment 43: SqlDataReader dataStream\', \'Comment 44: BulkCopySimpleResultSet bulkCopyHandler\', \'Comment 45: TdsParserStateObject stateObj\', \'Comment 46: Boolean& dataReady)   at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds\', \'Comment 47: RunBehavior runBehavior\', \'Comment 48: String resetOptionsString)   at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior\', \'Comment 49: RunBehavior runBehavior\', \'Comment 50: Boolean returnStream\', \'Comment 51: Boolean async\', \'Comment 52: Int32 timeout\', \'Comment 53: Task& task\', \'Comment 54: Boolean asyncWrite\', \'Comment 55: SqlDataReader ds)   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior\', \'Comment 56: RunBehavior runBehavior\', \'Comment 57: Boolean returnStream\', \'Comment 58: TaskCompletionSource`1 completion\', \'Comment 59: Int32 timeout\', \'Comment 60: Task& task\', \'Comment 61: Boolean asyncWrite\', \'Comment 62: String method)   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion\', \'Comment 63: Boolean sendToPipe\', \'Comment 64: Int32 timeout\', \'Comment 65: Boolean asyncWrite\', \'Comment 66: String methodName)   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()   at Microsoft.EntityFrameworkCore.Storage.Internal.RelationalCommand.Execute(IRelationalConnection connection\', \'Comment 67: DbCommandMethod executeMethod\', \'Comment 68: IReadOnlyDictionary`2 parameterValues)   at Microsoft.EntityFrameworkCore.Storage.Internal.RelationalCommand.ExecuteNonQuery(IRelationalConnection connection\', \'Comment 69: IReadOnlyDictionary`2 parameterValues)   at Microsoft.EntityFrameworkCore.RelationalDatabaseFacadeExtensions.ExecuteSqlCommand(DatabaseFacade databaseFacade\', \'Comment 70: RawSqlString sql\', ""Comment 71: IEnumerable`1 parameters)   at Kotrak.Common.Infrastructure.EF.EventRepository.GenericEventRepositoryEf`2.CleanData(TimeSpan removeOlderThen)   at Kotrak.Common.Infrastructure.CleanEventsTask.<ExecuteAsync>b__9_0()ClientConnectionId:dc8a9430-46b6-44e7-aa8c-881cd0a74da2Error Number:-2,State:0,Class:11{code}\'"", \'Comment 72: ""Errors DHC{code:java}Error mapping types.Mapping types:VehicleTicketDispatchClosedEvent -> VehicleTicketPlant.VC.BusinessLogic.DomainAbstractions.VehicleTickets.DomainEvents.VehicleTicketDispatchClosedEvent -> Evolution.DHCService.Contracts.VehicleTicketType Map configuration:VehicleTicketDispatchClosedEvent -> VehicleTicketPlant.VC.BusinessLogic.DomainAbstractions.VehicleTickets.DomainEvents.VehicleTicketDispatchClosedEvent -> Evolution.DHCService.Contracts.VehicleTicketProperty:Elements -> Error mapping types.Mapping types:IEnumerable`1 -> IEnumerable`1System.Collections.Generic.IEnumerable`1[[Plant.VC.BusinessLogic.DomainAbstractions.VehicleTickets.DomainEvents.VehicleTicketPackedDispatchElementChangedEvent\', \'Comment 73: Plant.VC.BusinessLogic.DomainAbstractions\', \'Comment 74: Version=7.6.0.0\', \'Comment 75: Culture=neutral\', \'Comment 76: PublicKeyToken=null]] -> System.Collections.Generic.IEnumerable`1[[Evolution.DHCService.Contracts.VehicleTicketElement\', \'Comment 77: Evolution.DHCService.Core\', \'Comment 78: Version=1.0.0.0\', \'Comment 79: Culture=neutral\', ""Comment 80: PublicKeyToken=null]] -> Error mapping types.Mapping types:VehicleTicketPackedDispatchElementChangedEvent -> VehicleTicketElementPlant.VC.BusinessLogic.DomainAbstractions.VehicleTickets.DomainEvents.VehicleTicketPackedDispatchElementChangedEvent -> Evolution.DHCService.Contracts.VehicleTicketElementType Map configuration:VehicleTicketPackedDispatchElementChangedEvent -> VehicleTicketElementPlant.VC.BusinessLogic.DomainAbstractions.VehicleTickets.DomainEvents.VehicleTicketPackedDispatchElementChangedEvent -> Evolution.DHCService.Contracts.VehicleTicketElementProperty:Id -> The instance of entity type \'VehicleTicketElementIdentityEntity\' cannot be tracked because another instance with the same key value for {\'PlantId\'"", ""Comment 81: \'PlantIdNo\'} is already being tracked. When attaching existing entities"", \'Comment 82: ensure that only one entity instance with a given key value is attached. Consider using \\\'DbContextOptionsBuilder.EnableSensitiveDataLogging\\\' to see the conflicting key values.{code}""\', ""Comment 83: \'Hi,We have analised your issue. We need to resend them all again via rabbit. It is very time consuming and we may finish it tomorrow. Are any of those vts more important than the others?Regards\'"", \'Comment 84: ""{code:java}SELECT  distinct v.DocumentNumber FROM [Evolution_DHCountry].[dbo].[VehicleTickets] v  left join  [Evolution_DHCountry].[dbo].[VehicleTicketElements] ve  on v.id=ve.vehicleticketid  where v.CreateDate>\\\'2022-12-24 00:00\\\'--DocumentNumber like \\\'%1242%\\\'  and v.Status in(1,2)  and ve.VehicleTicketId is null{code}""\', ""Comment 85: \'Dla 1190 tylko intakeclosed event!image-2022-12-29-18-10-47-111.png!\'"", ""Comment 86: \'Hi,The good news is that all VTs should be in DHC now. We need to investigate only VT-1190.Regards\'"", ""Comment 87: \'Is the status correct?!image-2022-12-29-19-49-37-643.png!Regards\'"", ""Comment 88: \'Dear  Now all the VTs are back in DHC and I personally checked them all one by one .  Thanks very much again for the service . Problem solved ! Regards\']""]\nRelated Issues:\n[]\n\n### End'}"
834,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8197\n\n### Instruction:\nCześć\r\n\r\nChce zaktualizować strukturę podległościową, tj. przepiąć centrum podległościowe pracownika na pion drobiu i pojawia się komunikat (poniżej screen, który uniemożliwia zapisanie). Dodam, że pracownik (Białas Szymon) ma umowę na czas nieokreślony.\r\n\r\nNa innym pracowniku jest ok.\n\n### Response:\n[""Comment 1: [\'!image-1!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Wioletta fix it by herself"", ""Comment 4: please close the task.\']""]\nRelated Issues:\n[]\n\n### End'}"
835,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8196\n\n### Instruction:\nAn additional technology VE303436 was created on 12 December for derived item 303436. Code to produce is 303641.\r\nIn DHP the version 0 recipe shows 303436 as ingredient. As a result. incorrect itemcode was sent to PCS and additional Lot reports are generated by DHP for 303436 that consumes 303436...\r\nPlease check why the incorrect RM /correct recipe in DHP so that it has 303641 as an ingredient. It is also ok if you remove the additional technology VE303436 in DHC, then I will create a new one.\r\n\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!!image-1!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 3: ""Hi Bob,I have analised this case. Removing / deleting additional technology requires deleteing all PLRs that have already used this item / technology. In Plant there are approimately 100 PLR. Fortunately\', ""Comment 4: I don\'t see any PLR related in DHC.Do you agree for removing all those PLRs and update the stock and dliveries?Please"", \'Comment 5: let me know.Regards""\', \'Comment 6: ""{color:#000000}Hi Aleksandra,{color} {color:#000000}{color}  {color:#000000}Yes\', ""Comment 7: it is ok to remove PLR\'s for this additional technology"", \'Comment 8: because FP produced and RM consumed is the same. Most of them I already confirmed with quantity 0.1 / no RM consumption\', \'Comment 9: but there will be a number of tem in status Created. I think it is correct that notne of them were sent to DHC.{color} {color:#000000}All of these Lot reports may be removed if needed. As far as I can see now\', \'Comment 10: it will not impact FP/RM usage.{color} {color:#000000}{color}   {color:#000000}{color}     {color:#000000}       {color}{color:black}{color} {color:#000000} {color}{color:black}Best regards | Met vriendelijke groeten,{color}{color:#000000}{color}{color:black}  Bob Kennedy{color} {color:#000000}{color}{color:black}Informatie analist{color}{color:#000000} {color}{color:black}{color}{color:#000000} {color}{color:#000000} {color} |{color:#000000}{color} {color:#000000}{color}De Heus Voeders{color:#000000} <[http://www.de-heus.nl/]>{color}{color:black}{color}{color:#000000} {color}{color:#000000} {color}|{color:#000000}{color}{color:#006FB7} * De Heus Voeders B.V.*{color}{color:#000000}{color}{color:#006FB7}{color} {color:#000000}{color}{color:#006FB7} Postbus 396 6710 BJ Ede{color}{color:#000000}{color}{color:#006FB7} Rubensstraat 1756717 VE Ede  *M* 06 - 53 224 931 KvK 14626985{color}{color:#000000}{color}{color:black} {color}{color:#000000}{color}{color:#006FB7} _ Op dit e-mailbericht en eventuele bijlage(n) is de disclaimer van toepassing_{color}{color:#000000}{color}{color:#006FB7}{color} {color:#000000}{color}{color:#006FB7} _ gepubliceerd op de website van_{color} [{color:#006FB7} _De Heus Voeders_{color}|http://www.de-heus.nl/maildisclaimer]{color:#006FB7} _._{color}{color:#000000}{color}{color:#006FB7}{color} {color:#000000} {color}{color:#000000} {color}| |{color:#000000}{color}{color:black}{color} image007.jpg@01D62AA3.AD14DDB0{color:black}{color}{color:#000000} {color}{color:#000000} {color}| |{color:#000000}{color}{color:black}{color} image004.jpg@01D62AA3.AD2CAB70{color:black}{color}{color:#000000} {color}{color:#000000} {color}| {color:#000000}{color} ---- {color:#000000} *From:* Aleksandra Przybyłek (Jira) <jira@kotrak.com>  *Sent:* Friday\', \'Comment 11: December 30\', \'Comment 12: 2022 3:11 PM  *To:* Kennedy\', \'Comment 13: Bob <BKennedy@deheus.com>  *Subject:* DGS-8196 Recipe for derived item in DHP different then additional technology in DHC{color}  |{color:#ffffff} CAUTION: This message originated from outside the organisation. Please do not click on links or open attachments unless you trust the sender and know the content is safe.{color} |""\', ""Comment 14: \'Additional Technology has been removed. Please"", ""Comment 15: verify.I will check logs and db if I can find any infrmation due to this mismatch.Regards\'"", ""Comment 16: \'Thank you. Lot reports for incorrect additional technology are now indeed removed. This ticket can be closed.\']""]\nRelated Issues:\n[]\n\n### End'}"
836,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8195\n\n### Instruction:\nHi,\r\n\r\nIs it possible to change category on 3 doc\'s?\r\nIt was posted on Calves, but should be in Slaughtery.\r\nID\'s 79221 / 79222 / 79223\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'The Round category has been adjusted as requested.\']""]\nRelated Issues:\n[]\n\n### End'}"
837,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8194\n\n### Instruction:\nPróbowano wystawić FV z CDN jedna WZ-783/12/22/D kwota brutto i netto widnieje 0 a jak się wejdzie w nią widnieją kwoty.\r\n\r\nFV nie wyszła na fiskalu, ponieważ jest wartość brutto błędna.\r\n\r\nProśba o rozwiązanie problemu\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'--update cdn.tranag --set trn_nettor=33038.8"", ""Comment 3: trn_vatr=2643.1--where TrN_GIDNumer in (12617933)\'"", ""Comment 4: \'Please verify.\'"", ""Comment 5: \'Podczas fiskalizacji pojawil sie taki blad :!image!\'"", ""Comment 6: \'Please try again if the problem still occurs"", ""Comment 7: are you able to cancell this SOR and created again?\'"", ""Comment 8: \'This error is still when i try print\'"", ""Comment 9: \'Did you cancell this WZ and erpint create the new one and there is still this error?\'"", ""Comment 10: \'Task to close\']""]\nRelated Issues:\n[]\n\n### End'}"
838,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8193\n\n### Instruction:\nGoodmorning,\r\n\r\nPlease, create an openingsbalance for item: 0473 on plant Maasbracht. Quantity 500 kg.\r\n\r\nRegards,\r\n\r\nGerard\n\n### Response:\n[""Comment 1: [\'Opening balance for item 0473 has been created.\'"", ""Comment 2: \'Hello Piotr,Thanks for support on this.You may close this ticketRegards,Gerard\']""]\nRelated Issues:\n[]\n\n### End'}"
839,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8192\n\n### Instruction:\nGoodmorning,\r\n\r\nPlease, could you help me.\r\nI think there is a synchronisation problem between these applications.\r\n\r\nI \'am waiting for a recipe on plant Ravenstein, recipe 167259.\r\n\r\nRegards,\r\n\r\nGerard\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Item is missing in DHC: !screenshot-1! so and linking !screenshot-2! Can  you check please ?\'"", ""Comment 3: \'Hello Piotr,Okay!Thanks for support. Problem is solved.You may close this ticketRegards,Gerard\'"", ""Comment 4: \'Thank you for confirmation,Regards.\']""]\nRelated Issues:\n[]\n\n### End'}"
840,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8191\n\n### Instruction:\nWyskoczył komunikat barcode cannot by null or empty nr 6150032\r\n\r\nProszę o szybką pomoc\n\n### Response:\n[""Comment 1: [\'Hello"", ""Comment 2: We kindly inform you that wecurrentlyare processing another Priority1 task.DGS-8189We will revert to processing your task as soon as possible.Regards\'"", ""Comment 3: \'Please check should be ok now?\'"", \'Comment 4: ""It\\\'s Ok ""]\']\nRelated Issues:\n[]\n\n### End'}"
841,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8190\n\n### Instruction:\nGoodmorning,\r\n\r\nCould you have a look at this error please?\r\nCan you resolve the problem and tell me the reason of this?\r\n\r\nRegards,\r\n\r\nGerard\n\n### Response:\n[""Comment 1: [\'!Knipsel2.PNG|thumbnail!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'does the problem persist?Does the problem only affect a specific VT?\'"", ""Comment 4: \'Hello Aleksandra,only at this VT.\'"", \'Comment 5: \\\'2022-12-29 07:57:04 (e1bd1aa8-d8cc-4c1c-84b5-dd01c6f782f9/Plant.VC.BusinessLogic/DHVD01AP179/6320/196) [Error] Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware - Error during request{ ""scheme"": ""http""\', \'Comment 6: ""host"": { ""Value"": ""dhvd01ap179:82""\', \'Comment 7: ""HasValue"": true\', \'Comment 8: ""Host"": ""dhvd01ap179""\', \'Comment 9: ""Port"": 82 }\', \'Comment 10: ""path"": ""/api/VehicleTicket/releaseDispatch""\', \'Comment 11: ""queryString"": []\', \'Comment 12: ""requestBody"": ""\\\\\\\\{\\\\\\\\""id\\\\\\\\"":\\\\\\\\""d5f57e8f-7e86-4fea-9fad-054a70a469f4\\\\\\\\"",\\\\\\\\""date\\\\\\\\"":\\\\\\\\""2022-12-29T06:57:05.725Z\\\\\\\\""}""}.System.InvalidOperationException: Nullable object must have a value.[[DHP 3.0] VT procesowanie System.InvalidOperationException: Nullable object must have a value.|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%20VT%20procesowanie%20System.InvalidOperationException%20Nullable%20object&section-id=\\\\\\\\{05DF1439-683C-45FE-8260-61E2EC66DC91}&page-id=\\\\\\\\{AA5B5141-139E-4A0C-A66A-37DAE9560CF5}&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%20VT%20procesowanie%20System.InvalidOperationException%3A%20Nullable%20object%7CAA5B5141-139E-4A0C-A66A-37DAE9560CF5%2F%29])\\\'\', ""Comment 13: \'Please check?\'"", \'Comment 14: ""I\\\'am waiting for feedback""\', \'Comment 15: ""Hi Aleksandra,This issue was only for this VT.Further analyse on our side is done. This was a accident. For this time it\\\'s an accident. If it happens again than we have to investigate.Please close this ticket.Regards,Gerard""]\']\nRelated Issues:\n[]\n\n### End'}"
842,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8189\n\n### Instruction:\nGoodmorning,\r\n\r\nWe try to close this VT and get this this error.\r\nCould you help us to resolve this please, and tell me the reason of this error?\r\n\r\nKind regards,\r\n\r\nGerard\n\n### Response:\n[""Comment 1: [\'!Knipsel.PNG|thumbnail!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Hello,Please verify"", ""Comment 4: we had no problem with closing VT-477/11/12We closed from the DHP applicationRegards\'"", ""Comment 5: \'Goodmorning Adrian,I asked for confirmation at our side. And waiting for it.Regards,Gerard\'"", ""Comment 6: \'Hello Adrian,VT is okay. Please close this serviceticket.Thanks for support on it.Regards,Gerard\'"", ""Comment 7: \'This ticket/VT should be treated as an incident,the next time an error occurs an RCA will be created.Regards.\'"", ""Comment 8: \'Hello Piotr,Okay!Regards.\']""]\nRelated Issues:\n[]\n\n### End'}"
843,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8188\n\n### Instruction:\nGoodmorning,\r\n\r\nPlease, could you create an openingsbalance for item 0458 on plant Ravenstein. Quantity is 15950 kg.\r\n\r\nRegards,\r\n\r\nGerard\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Openings balance for item 0458 has been created.\'"", ""Comment 3: \'Goodmorning Piotr,thanks for your support on this. You may close this ticket.Regards,Gerard\'"", ""Comment 4: \'Good morning.Thank you for confirmation.Regards.\']""]\nRelated Issues:\n[]\n\n### End'}"
844,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8187\n\n### Instruction:\nHi\r\n\r\nWe have some ULs with differing reservations between Stock and WMS engine.\r\n\r\n{quote}\r\n85-OB00NK\r\n85-OB00NI\r\n{quote}\r\n\r\nCould you fix that please?\r\n\r\nThank you\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 2: ""{code:java}SELECT su.QuantityOnHandValue\', \'Comment 3: su.ReservedQuantityValue\', \'Comment 4: su.LogisticStatus,su.ReservationSourceDocumentNumbers,ul.Barcode,su.Id  FROM [DHPlantWmsBusinessLogicMain].[dbo].[UnitLoads] ul  inner join [DHPlantWmsBusinessLogicMain].dbo.StockUnits su on ul.id=su.UnitLoadId  where ul.barcode in(  \\\'85-OB00NK\\\',\\\'85-OB00NI\\\'  )  SELECT QuantityOnhand,Quantity,*  FROM [DHPlantStockBusinessLogicMain].[dbo].[StockUnits]  where barcode in(  \\\'85-OB00NK\\\',\\\'85-OB00NI\\\'  )SELECT *FROM DHPlantStockBusinessLogicMain.dbo.ProductionLots Pleft JOIN DHPlantStockBusinessLogicMain.dbo.StockUnitReservations R ON P.Id = R.SourceDocumentIdWHERE P.lotnumber=\\\'0855131022009\\\'ORDER BY P.StartDate DESC;{code}!image-2022-12-29-11-05-50-650!""\', ""Comment 5: \' !screenshot-1! \'"", \'Comment 6: ""It\\\'s already released,please confirm that the stock module has the correct data and the wms needs to be corrected.""\', \'Comment 7: ""Hi PiotrI\\\'m still finding it on WMS engine!image!""\', \'Comment 8: ""Hello\', \'Comment 9: I just wanted to confirm but i see it\\\'s fine now.I changed the status to released.!image-2022-12-30-08-57-14-181.png!""\', \'Comment 10: ""Hi PiotrNow it\\\'s OK. Thank you very much.You can close this task""]\']\nRelated Issues:\n[]\n\n### End'}"
845,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8186\n\n### Instruction:\nHi\r\n\r\nWe have this WO(IP)-27/12/22\r\nThe PLR 0856031222001 were canceled but the user wrongly registered the 3 ULs of it.\r\nWe are trying to close the WO(IP) without realization, but DHP shows an error message: *Error! Invalid intake status to close warehouse order without realization*\r\n\r\nWhen I try to remove the registered UL from _Intake from production processing_ screen, there\'s this error message: *Error! Warehouse intake should be in progress*\r\n\r\nCould you please clear the registered ULs and Close this WO(IP) without realization?\r\n\r\nThank you very much\n\n### Response:\n[""Comment 1: [\'!image!!image-1!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Hello,\\\\r\\\\rWe are investigating your issue. We will inform you about the solution as soon as possible.\\\\r\\\\rRegards\'"", ""Comment 4: \'https://helpdesk.kotrak.com/browse/DAP-11559\'"", ""Comment 5: \'!executed.PNG|thumbnail!\'"", ""Comment 6: \'In the case given"", \'Comment 7: there is a WI document in an executed state\', \'Comment 8: from what we can see the WOPI document was reopened.!image-2022-12-29-10-23-41-425.png!After reopen you mayonly add some ULs\', ""Comment 9: but you cannot delete those that have already been registered.To reduce the states in this situation create Stockaging.Is this information sufficient?\'"", ""Comment 10: \'HIWe made the STK of ULs from lot number 0856031222001.However the WO(IP) still with status = *Processable* and also one delivery in Stock engine with SU with 1 kg with status = *InProgress*.Could you please fix that?Thank you!image-2!\'"", ""Comment 11: \'!image-2022-12-30-10-37-49-378.png!\'"", ""Comment 12: \'deliveryid?id=bd050587-30cf-42a6-a460-6c215a44e7eb\'"", ""Comment 13: \'!staplr.PNG|thumbnail!\'"", ""Comment 14: \'The PRL is in status created - please confim it!staplr.PNG!When you create a PLR"", \'Comment 15: you create a bulk SU\', \'Comment 16: which in this case was 3001kg. They registered 3 pallets of 1000kg on the WO(IP)\', ""Comment 17: so there was 1kg left on the bulky SU- that correct.After you confirm this PLr this 1kg will be on stock and you will be able to make a stockaging.For WOPI you may only set status to complete\'"", \'Comment 18: ""HiPlease revisit the initial description of this task:bq. The PLR 0856031222001 were *canceled* but the user *wrongly* registered the 3 ULs of it.This PLR was created\', ""Comment 19: but canceled because we didn\'t need it anymore. However"", ""Comment 20: the user has mistakenly registered the ULs of this PLR.We\'ll not use this PLR; there was no RM consumption.  We\'ll not use this ULs; these registered ULs were were discarded in the trash can.When we open the Production Reports screen this PLR is not being displayed. I don\'t know why DHP has this _Created_ status even after we canceled this PLR.So"", ""Comment 21: once again: *Could you please clear the registered ULs and Close this WO(IP) without realization?*If this isn\'t possible"", \'Comment 22: could you please change the status of the WO(IP) to _Canceled_ or _Finished_ or anything else to clear it from the WO List screen?Thank you very much""\', ""Comment 23: \'Hod did user cancelled it if that have still created status?Did you change something in db ?We fixed the status for PRL for cancel and set wopi for executed.I add also description in case there will be some problems in futureLet me know if we may close the task.!image-2022-12-30-14-43-43-846.png!!image-2022-12-30-14-43-43-846!\'"", \'Comment 24: ""update  [DHPlantWmsBusinessLogicMain].[dbo].[WarehouseOrderElements]  set status=50 where id=\\\'ef95ed65-108b-493e-8881-ac09421c9532\\\'update [DHPlantWmsBusinessLogicMain].[dbo].[WarehouseOrders]  set status =50 \', \'Comment 25: Description=\\\' changed due dgs-8186\\\' where id=\\\'ef95ed65-108b-493e-8881-ac09421c9532\\\'""\', \'Comment 26: ""Hi AgnieszkaWe used the functionality ti cancel the PLR. We are not authorized to make changes in DB.Now it\\\'s OK. You can close this task.Thank you very much!image-3!""]\']\nRelated Issues:\n[\'DAP-13138\']\n\n### End'}"
846,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8185\n\n### Instruction:\nHi\r\n\r\nWe have this *88-W0F57Q* Unit load.\r\nWhen verifying the WMS engine, we have 750kg on Quantity On Hand value and no Reservations for this UL.\r\nHowever, looking to Stock engine, this UL have 0kg on Quantity On Hand value and a WM document on Reservation for this UL.\r\n\r\nChecking with the plant, the right information is in WMS engine. Could you please fix that?\r\n\r\nThank you very much\n\n### Response:\n[""Comment 1: [\'!image!!image-1!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Barcode*88-W0F57Q*is fixed"", ""Comment 4: please verify.Regards\'"", ""Comment 5: \'W WMS prawidłowo:!image-2022-12-28-20-15-37-415.png!!image-2022-12-28-20-15-37-415!\'"", \'Comment 6: ""HiI confirm that it\\\'s fixed! Thank you!Is there anything that I can do myself for a future case like this?You can close this taskThank you very much""\', ""Comment 7: \'Thank you. As I mentioned in DGS-8184"", ""Comment 8: dev are working on permament fix.Regards\']""]\nRelated Issues:\n[\'DGS-8087\', \'DGS-8168\']\n\n### End'}"
847,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8184\n\n### Instruction:\nHi\r\n\r\nWe have a recurring problem, same from DGS-8087.\r\n\r\nSome items/Unit load are with wrong reservation. The productions are closed but they are still reserving some unit loads.\r\n\r\nProduction of Lot Number:\r\n0871261222004\r\n0871221222008\r\n\r\nCould you check why reservation was not done when productions were closed, check if we have more productions with the same error and fix it?\r\n\r\nIt\'s urgent because system not allow to move or make inventory for unit load with reservation.\r\n\r\nThank you\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 please provide me with barcodes that causes the issue in PLRs:08712612220040871221222008?Regards\'"", ""Comment 3: \'Root cause analysis is under:DGS-8168\'"", ""Comment 4: \'HiYou can find attached the ULs for each PLRs.About RCA 8168. Do I need to register this DGS 8184 in there or there is any other thing that I should do about ti?Thank you[^ULs from 0871261222004.xlsx] _(6 kB)_[^ULs from 0871221222008.xlsx] _(7 kB)_\'"", ""Comment 5: \'I have linked those tickets"", \'Comment 6: however now I can unblock the process. Under RCA task\', ""Comment 7: analysis is taken and permament solution is worked on.\'"", ""Comment 8: \'{code:java}SELECT *FROM DHPlantStockBusinessLogicMain.dbo.ProductionLots PJOIN DHPlantStockBusinessLogicMain.dbo.StockUnitReservations R ON P.Id = R.SourceDocumentIdWHERE P.ProductionLotStatus = 4ORDER BY P.StartDate DESC;{code}W Toledo są takie dwa:08712612220040871221222008\'"", \'Comment 9: ""Data has been corrected for Toledo and this two PLR\\\'s 08712612220040871221222008and as Aleksandra mentioned RCA is already created DGS-8168""\', \'Comment 10: ""Hi PiotrNow it\\\'s OK.You can close this taskThank you very much""]\']\nRelated Issues:\n[\'DGS-8087\', \'DGS-8168\']\n\n### End'}"
848,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8183\n\n### Instruction:\nHi\r\n\r\nCould you please update asap the translation files for 8.3 release version on the following plants?\r\nItaberaí\r\nApucarana\r\nToledo\r\nGuararapes\r\n\r\nAs far as I know, the source is BRT-1011 and BRT-1012\r\n\r\nThank you very much\n\n### Response:\n[""Comment 1: [\'Hi Maicon,Please be informed that we have forwarded the issue to the development team in order to internal analysis.We are waiting for more details and will be back with further information as soon as possible.Regards\'"", ""Comment 2: \'Dear [~mberbert@deheus.com]* TO Prod was updated 15.12.2022 and currently on Mobile you have the latest translations ** We can update today Web translations file only* AP"", \'Comment 3: IT\', \'Comment 4: GU - we need to update file for translations for Web + we need to update Mobile app - that is why the best way will be update the version 8.3 to the lates version (Web+Mobile)* Do you want to update 8.3 to the latest on Prod: AP\', \'Comment 5: IT\', \'Comment 6: GU?** if yes\', ""Comment 7: we can plan the update for tomorrow morning.\'"", ""Comment 8: \'Dear [~marcin.kleszcz@kotrak.com]** TO Prod: Thank you for mobile update! You can update the web today** AP IT GU: You can update it to the latest version + translations + mobile tomorrow in your morningThank you very much\'"", ""Comment 9: \'HelloAll DHPs are up to date.Thank you very muchYou can close this task\'"", ""Comment 10: \'Dear [~mberbert@deheus.com]this task was related to the update of DHP3.0.That is why it was realized on DIM project.As we have discussed on Teams"", \'Comment 11: estimation for this update: *3hours* for: AP\', \'Comment 12: IT\', ""Comment 13: GU.Thanks \'"", ""Comment 14: \'Dear [~marcin.kleszcz@kotrak.com]OK!Thank you very much\']""]\nRelated Issues:\n[]\n\n### End'}"
849,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8182\n\n### Instruction:\nHej\r\n\r\nNie przechodzą trasy z dhc do hdp, serwisy restartowane, kolejki nie widzę.\r\nNp 12967/22/S, 12935/22/S, 12914/22/S, 7479/22/I.\r\n\r\nRafał Boniecki\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: \'All routes passed. Did you do anything?\'"", ""Comment 3: \'No"", \'Comment 4: just verified the issue. Regarding12967/22/S\', \'Comment 5: I cannot see it under the database nor in DHC. Was the number correct?Also\', \'Comment 6: when ticket raised\', ""Comment 7: route12935/22/S has already been in DHP.Regards\'"", ""Comment 8: \'Can we close this task"", ""Comment 9: btw? :)\'"", ""Comment 10: \'12957 btw...so dhc had a long delay...to close"", ""Comment 11: thanks.\'"", ""Comment 12: \'Thank you\']""]\nRelated Issues:\n[]\n\n### End'}"
850,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8181\n\n### Instruction:\nI made an elements to sales invoice en I get an error, \r\nI get the sales invoices but the numbers are not in de PI-RLM/2022/2150\r\n(SI-RLM/2022/3612......2852)\n\n### Response:\n[""Comment 1: [\'[^Map3.pdf] _(225 kB)_\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Hello Anja,Could you describe when this errors ocurred (page 1 of attachment) or this errors are not related with this topic?I see on the page 2 of attachment and in Intense that Sales invoices have been generated properly but are not linked to the source Purchase Invoice"", ""Comment 4: right?Are there any errors when you created Sales Invoices from Purchase invoices?\'"", ""Comment 5: \'{color:black}Errors came when i create de SI on the tab of ‘Elements to Sales Invoice’{color} {color:black}{color} {color:black}These SI have to link at PI-RLM/2022/2150{color} !image001!{color:black}{color} {color:black}{color} {color:black}{color} {color:black}{color} {color:black}{color} !image008!{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} Anja{color} |{color:#000001} {color} |{color:#000001} Verdam,{color} |  {color:#000001}MedewerkerContractadministratie{color} | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image002!{color:black} <[https://www.de-heus.nl/]>{color} | |  *{color:#006FB7} *DEHEUSVOEDERSB.V.*{color}* | | | |{color:#000001} Postbus396 6710BJEde \\\\u200b{color} | |{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} | | |{color:#000001} M:{color}{color:#000001}{color}{color:#000001}0641399917{color}{color:#000001} <tel:06%2041%20399%20917>{color} | |{color:#000001} T:0318675564{color} |  {color:#000001}KvK14626985{color}   _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | | !image003! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | | !image004! <[https://twitter.com/de_heus_voeders]>{color:black}{color} | | !image005! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image006! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} | |{color:black}{color} !image007.jpg|thumbnail!{color:black}{color} |      *Van:* Damian Świstek (Jira) <jira@kotrak.com>   *Verzonden:* donderdag 29 december 2022 12:35  *Aan:* Verdam"", ""Comment 6: Anja <AVerdam@deheus.com>  *Onderwerp:* DGS-8181 error - sales invoice numbers   |  *{color:white} *CAUTION: This message originated from outside the organisation. Please do not click on links or open attachments unless you trust the sender and know the content is safe.*{color}* |   \'"", ""Comment 7: \'Now it should be ok"", \'Comment 8: there are linked documents on Purchase Invoices.\\\\r\\\\rWe cannot repeat this error on test environment.\\\\r\\\\rIf there will be another situation like this\', ""Comment 9: please create a task.\']""]\nRelated Issues:\n[]\n\n### End'}"
851,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8180\n\n### Instruction:\nGood afternoon,\r\n\r\nwould you so kind to delete the user: loodssneek on plant: Sneek\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: \'Dear Gerard,Could you please provie me with the first name and last name of the userloodssneek ? I cannot see this login neither in Sneek nor in DHC.Regards\'"", ""Comment 3: \'!image-2022-12-28-15-51-14-375.png!!image-2022-12-28-15-51-50-074.png!\'"", ""Comment 4: \'Dear Aleksandra,the first name is: Loods and the second name is: SneekRegards\'"", \'Comment 5: ""But this user has status: inactve\', \'Comment 6: isn\\\'t it fine?Regards!image-2022-12-28-16-40-40-245.png!""\', ""Comment 7: \'Goodmorning Aleksandra,Yes"", \'Comment 8: that is correct!Forget the deletion of this account\', ""Comment 9: but please change the password for me to: Heus2022!and I wil activate this account later to on.Regards,Gerard\'"", ""Comment 10: \'Good afternoon Gerard,The password has been changed as requested.Regards\'"", ""Comment 11: \'Good afternoon Aleksandra,Thanks for support on this.You may close this ticketKind regards,Gerard\'"", ""Comment 12: \'Thank you.Regards\']""]\nRelated Issues:\n[]\n\n### End'}"
852,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8179\n\n### Instruction:\nGood afternoon,\r\n\r\nPlease, could you help me? See also image.\r\n\r\nI am unable to book out this sales order.\r\n\r\nKind regards,\r\n\r\nGerard\n\n### Response:\n[""Comment 1: [\'!image001!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Can you be more specific what exactly cannot be done on this order?\'"", \'Comment 4: ""Dear Piotr,i asked my collegue for more detailinformation. I\\\'am waiting.Regards""\', \'Comment 5: ""Hello Piotr,hereby more detailinormation about this Salesorder.The problem is that the button to create a full SOR is grey\', \'Comment 6: so my collegue can\\\'t create a full SOR for this order.Could you help us?Regards,Gerard!Knipsel3!""\', ""Comment 7: \'This SO is from allocation:SourceDocumentNumber\\\\tPONumberPORI-77/08/2022/VIMP\\\\tPO-17/08/2022/INTand system allows only creation SOR from POR documents that where done manually by user.This one was created by ERPintegrator.\'"", \'Comment 8: ""{code:java}SELECT [AllocationId],*       FROM [CDNXL_DHNL_PROD].[Kotrak].[ZamElemExtensions]  where GidNumer=22411   select *   FROM [CDNXL_DHNL_PROD].[Kotrak].[Allocations]  where id=\\\'29211\\\'{code}""\', \'Comment 9: ""Good afternoon,my collegue doesn\\\'t understand your explanation. Could you give us more clearly information\', \'Comment 10: so that he understood what he has todo?Kind regards,Gerard ""\', ""Comment 11: \'This order can only be used for VT(SOR will be generated from VT automatically)  or generated from the XL directly not the GUI(DH CDN).\'"", ""Comment 12: \'Hello"", ""Comment 13: do you have any update for our last comment?Thank you and regards.\'"", \'Comment 14: ""Goodmorning Piotr,yesterday I asked my collegue. I\\\'am waiting for a feedback from him. But last week a lot of people are not at the Office (holidays). So\', \'Comment 15: if feedback is available you got an answer related to this issue from me. Please\', \'Comment 16: do not close this one.Regards,Gerard ""\', ""Comment 17: \'Good morning"", ""Comment 18: thanks for the reply -  so we wait :)Regards.\'"", ""Comment 19: \'Hello"", ""Comment 20: do you have any update for this ticket?Thank you and regards.\'"", ""Comment 21: \'Hello,We are closing this task as we haven’treceivedany replyfromyouforalong time. If the issueappearsagain"", ""Comment 22: please raise another task.Regards\']""]\nRelated Issues:\n[]\n\n### End'}"
853,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8178\n\n### Instruction:\n101662 has an active round, but I can\'t select.\r\nID 80984\r\nI will write an e-mail with screenshots\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!!image-1!\'"", ""Comment 2: \'Hello ChristineThe customer selected in the invoice is Customer Other. There is no relation like this in the relation table. We never use Customer Other in NAS.If we have a sales invoice"", ""Comment 3: we always deal with either Customer Farmer or Customer Slaughtery/Cattle Trader\'"", \'Comment 4: ""Hello Christine\', \'Comment 5: You can try now to change it. Please let me know if this resolves the problem.RegardsEwa From: Jong\', \'Comment 6: Christine de <CJong@deheus.com>Sent: Thursday\', \'Comment 7: December 29\', \'Comment 8: 2022 8:36 AMTo: Ewa Mucha <ewa.mucha@kotrak.com>; JIRA <jira@kotrak.com>Subject: RE: DGS-8178 Not able to select a round numberGoodmorning,How can I change the BP_Category?It is greyIf I understand correctly I have to change this to Slaughtery/Cattle traderMetvriendelijkegroet,\\\\u200b\\\\u200bChristinede\\\\t\\\\tJongMedewerkerContractadministratie[1]\\\\tDEHEUSVOEDERSB.V.Postbus3966710BJEde\\\\u200b\\\\tRubensstraat1756717VEEde\\\\u200b\\\\tT:0318675567KvK14626985Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassinggepubliceerdopdewebsitevan[2]DeHeusVoeders.[3]\\\\t[4]\\\\t[5]\\\\t[6]Van: Jong\', \'Comment 9: Christine deVerzonden: woensdag 28 december 2022 15:14Aan: Ewa Mucha <[7]ewa.mucha@kotrak.com>; [8]jira@kotrak.comOnderwerp: FW: DGS-8178 Not able to select a round numberHi Ewa,Why were we able to make postings? Please see my e-mail 14:06 with below screenshot.Metvriendelijkegroet,\\\\u200b\\\\u200bChristinede\\\\t\\\\tJongMedewerkerContractadministratie[9]\\\\tDEHEUSVOEDERSB.V.Postbus3966710BJEde\\\\u200b\\\\tRubensstraat1756717VEEde\\\\u200b\\\\tT:0318675567KvK14626985Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassinggepubliceerdopdewebsitevan[10]DeHeusVoeders.[11]\\\\t[12]\\\\t[13]\\\\t[14]Van: Ewa Mucha (Jira) <[15]jira@kotrak.com>Verzonden: woensdag 28 december 2022 14:18Aan: Jong\', \'Comment 10: Christine de <[16]CJong@deheus.com>Onderwerp: DGS-8178 Not able to select a round numberCAUTION: 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.—-—-—-— Reply above this line. Ewa Mucha commented:Hello ChristineThe customer selected in the invoice is Customer Other. There is no relation like this in the relation table. We never use Customer Other in NAS.If we have a sales invoice\', ""Comment 11: we always deal with either Customer Farmer or Customer Slaughtery/Cattle Trader[17]View request ·[18]Turn off this request\'s notifications This is shared with Christine de Jong"", \'Comment 12: Tomasz Kozioł\', \'Comment 13: Ewa Mucha\', \'Comment 14: and Mitch van Bovene. KOTRAK\', \'Comment 15: powered by [19]Jira Service Desk\', \'Comment 16: sent you this message. ----------------------------------------------------------------------------------------[1] https://www.de-heus.nl/[2] https://www.de-heus.nl/privacy-beleid[3] https://www.facebook.com/deheusvoeders[4] https://twitter.com/de_heus_voeders[5] https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ[6] https://www.linkedin.com/company/de-heus-voeders-b-v-/[7] mailto:ewa.mucha@kotrak.com[8] mailto:jira@kotrak.com[9] https://www.de-heus.nl/[10] https://www.de-heus.nl/privacy-beleid[11] https://www.facebook.com/deheusvoeders[12] https://twitter.com/de_heus_voeders[13] https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ[14] https://www.linkedin.com/company/de-heus-voeders-b-v-/[15] mailto:jira@kotrak.com[16] mailto:CJong@deheus.com[17] https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhelpdesk.kotrak.com%2Fservicedesk%2Fcustomer%2Fportal%2F56%2FDGS-8178%3Fsda_source%3Dnotification-email&data=05%7C01%7CCJong%40deheus.com%7C05c47bc662644931fd4508dae8d5f60b%7C1004261bdfb74f37830f7438cb8a1b69%7C1%7C0%7C638078302907040392%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=mBR8zr%2B7dK8p1MV5GOh%2FHNEFvwPo1JY2kkMMD2jpTEo%3D&reserved=0[18] https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhelpdesk.kotrak.com%2Fservicedesk%2Fcustomer%2Fportal%2F56%2FDGS-8178%2Funsubscribe%3Fjwt%3DeyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJxc2giOiI1N2E1OWZhN2Y0MmUyNmRlZmZkNDk0ZDNkMThkMjNiMDc5NmE2NTI4ZWJhNzkzZmM3ZTU3OTM4N2RhY2RlNGZjIiwiaXNzIjoic2VydmljZWRlc2stand0LXRva2VuLWlzc3VlciIsImNvbnRleHQiOnsidXNlciI6IkpJUkFVU0VSMzQwMTkiLCJpc3N1ZSI6IkRHUy04MTc4In0sImV4cCI6MTY3NDY1MjY0NiwiaWF0IjoxNjcyMjMzNDQ2fQ.G7GkQSALwjpo2w6qa5mZRmHf5gDVX8VECHZYi_zktyQ&data=05%7C01%7CCJong%40deheus.com%7C05c47bc662644931fd4508dae8d5f60b%7C1004261bdfb74f37830f7438cb8a1b69%7C1%7C0%7C638078302907196631%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=0aiEK0VOInnPeH%2BxsEo1WxoMvYQFccx0x04dYUf9Ew8%3D&reserved=0[19] https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.atlassian.com%2Fsoftware%2Fjira%2Fservice-desk%2Fpowered-by%3Futm_medium%3Demail%26utm_source%3Dservice-desk_email-notification_server%26utm_campaign%3Dservice-desk_email-notification_server&data=05%7C01%7CCJong%40deheus.com%7C05c47bc662644931fd4508dae8d5f60b%7C1004261bdfb74f37830f7438cb8a1b69%7C1%7C0%7C638078302907196631%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=NenXnEq84pZKtMKHTvWUqgfvoILFf%2BWxaRyCuYynerY%3D&reserved=0""]\']\nRelated Issues:\n[]\n\n### End'}"
854,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8177\n\n### Instruction:\nHi\r\n\r\nWe have a problem with DHC x DHP Orders integration with Foreigh document numbers:\r\nOVE-071931\r\nOVE-071909\r\n\r\nThey were integrated from ERP to DHC with success, however they weren\'t integrated from DHC to DHP because the OrderElements wasn\'t liked yet.\r\nWhen items were linked, DHC didn\'t tried to resend to DHP.\r\nThis is happening a lot, but we never have time to analyze it.\r\nCould you please check why DHC is not resending blocked orders to DHP after the link process?\r\nAnd then, please, after finding the root cause of the problem, send this Orders because factory needs to plan the production.\r\n\r\nThank you very much\n\n### Response:\n[""Comment 1: [\'[~przemyslaw.przybyszewski@kotrak.com]zamówienia z oryginalnego taska"", \'Comment 2: przeszły dopiero po tym jak ponownie wysłali je ze swojego erp jednak Brazyli twierdzi \', \'Comment 3: że po linkowaniu\', \'Comment 4: zamówienie powinny same się resendować - tutaj to nie zadziałało.Tak to pamięta Brazylia:""As far as I remember\', \'Comment 5: Przemysław Przybyszewski informed that this resend after linking is a DHC functionality. However\', \'Comment 6: as I described in this DGS\', \'Comment 7: this is not working. And I don\\\\\\\'t know where is the log description about why it didn\\\\\\\'t work.""Da radę zweryfikować czy to się faktycznie ma ponownie samo wysyłać- zaciągac i cos nie zadziałało\', ""Comment 8: czy jednak sami powinni to ponownie wysłać?\'"", ""Comment 9: \'powinno się samo wysyłać. potrzebujemy przykład na którym mogli byśmy to przeanalizować (taki gdzie jeszcze nie zdążyli wysłać ponownie itema) być moze w wersji którą mieli był jakiś babol"", ""Comment 10: jeśli wystąpi w DHC które mają obecnie to niech poinformują.\'"", ""Comment 11: \'Could you provide new example of similar situation?From what we know the current DHC version this problem should not occur.,\'"", \'Comment 12: ""Hi Agnieszka I\\\'ll start monitoring this case with this new 62.0 version for the next 2 weeks.I\\\'ll let you know.Thank you""\', ""Comment 13: \'Did you verify it"", ""Comment 14: may we close the task?\'"", \'Comment 15: ""Hi AgnieszkaWe didn\\\'t have new cases\', \'Comment 16: but there is some issue with DHCountry to DHCService engines. Because ERP send the information to DHC\', \'Comment 17: DHC returns a success message to ERP\', \'Comment 18: we can find the Order in DHCountry app\', \'Comment 19: but it doesn\\\'t send to DHP.We had DGS-8776 about Orders integrationAlso DGS-8820 with some situation about DHC to DHP integration of RecipesI thing we should leave this RCA open and investigate further. What do you propose?Thank you""]\']\nRelated Issues:\n[\'DGS-8159\']\n\n### End'}"
855,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8176\n\n### Instruction:\nGood afternoon,\r\n\r\nplease, would you so kind to make an openingbalance for item: 080240-Z15 plant: Sneek. Quantity 500.\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: \'Hello,Opening balance has been created for item. Please"", ""Comment 3: verify.Regards!image-2022-12-28-14-55-49-489.png!!image-2022-12-28-14-55-49-489!\'"", ""Comment 4: \'Dear Aleksandra,thanks for your support. You may close this ticket.Regards,Gerard\']""]\nRelated Issues:\n[]\n\n### End'}"
856,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8175\n\n### Instruction:\nWitam\r\nPodczas proby zamkniecia VT-19065/12/22 pojawia sie komunikat ajak w załączniku\r\nNie mozna usunac tez ani anulowac elementu.\r\nJeden z elementów dopisany jest dwukrotnie do komory 8 \r\nProsze o szybkie rozwiazanie - kierowca na wadze\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: \'can i get phone number to factory?\'"", ""Comment 4: \'728906880\'"", ""Comment 5: \'Vt was closed"", ""Comment 6: I had a profiler started for this error but it failed to repeat.Were there any changes made on your side in the meantime?Thanks.\'"", ""Comment 7: \'Nie po mojej stronie nic nie było robione. User zamknął VT czy Ty od bazy ??\'"", ""Comment 8: \'The operator closed VT"", ""Comment 9: I closed the load from the application to cause an error.\'"", ""Comment 10: \'Task to close\']""]\nRelated Issues:\n[]\n\n### End'}"
857,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8174\n\n### Instruction:\nHi Theo and Ewa,\r\n \r\nFor this round a lot of things went wrong in moving feed. Forth and back between the different rounds.\r\n \r\nAre we able to send all feed invoices (see the invoices in the attachment that are not red) again from Milas to Intense? I think we need to clear the feed and also some specials that are booked in expenses in Intense first. I am not sure what the right order of things and approach is, that is why I am mailing the both of you.\r\n \r\nRegards,\r\n \r\nMitch\r\n \r\n\n\n### Response:\n[""Comment 1: [\'!image-2022-12-28-11-59-33-975.png!\'"", ""Comment 2: \'!image-2022-12-28-11-59-52-955.png!\'"", ""Comment 3: \'skonsultowae z Damianem 22.12: robimy na spokojnie.trzeba by jeszcze S2P usuwać"", \'Comment 4: potem linie z Feed sale\', \'Comment 5: czyli powyłączać blokady\', ""Comment 6: żebyśmy to mogli zrobić i wyrzucić wszystkie te linie z Feed sale.\'"", ""Comment 7: \'This will be handled after Damian finalizes a change request related to S2P[~damian.swistek@kotrak.com]FYI\'"", ""Comment 8: \'What is the current status?\'"", ""Comment 9: \'Do sprawdzenia które dokumenty można usunąć.\'"", ""Comment 10: \'[^InvoicesToDelete_FS_09012023-1.xlsx]\'"", ""Comment 11: \'[~mbovene@deheus.com]"", \'Comment 12: I send the list of all this documents related to other objects in Intense. Lines with value ""NULL"" in column ExportedToMilas can be delete but other lines can\\\\\\\'t\', ""Comment 13: because they have been exported to Milas.[^InvoicesToDelete_FS_09012023-1.xlsx]\'"", ""Comment 14: \'{color:black}Ha Grzegorz,{color}  {color:black}{color} {color:black}It’s already solved yet. No futher action needed. Thanks!{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Rick{color} |{color:#000001} {color} |{color:#000001} Reimerink{color} |  {color:#000001}SpecialistOpfokenVermeerdering{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}0622854366{color}{color:#000001} <tel:06%2022%20854%20366>{color} |  {color:#000001}KvK14626985{color}   _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | | !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | | !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} | | !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} |      *Van:* Grzegorz Materla (Jira) <jira@kotrak.com>   *Verzonden:* dinsdag 10 januari 2023 08:39  *Aan:* Reimerink"", ""Comment 15: Rick <rreimerink@deheus.com>  *Onderwerp:* DGS-8174 RE: Jacobs Migielsen feed sale leeghalen   |  *{color:white} *CAUTION: This message originated from outside the organisation. Please do not click on links or open attachments unless you trust the sender and know the content is safe.*{color}* |   !image006.gif!\'"", \'Comment 16: ""Hi [~rreimerink@deheus.com],thank you for information. So\', \'Comment 17: I\\\'m closing task.Have a nice day.Best regards,Grzegorz""]\']\nRelated Issues:\n[]\n\n### End'}"
858,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8173\n\n### Instruction:\nIn the migration from the eggs to 21-09-2022 is the Item CALA taken as a debet, this should have been credit.\r\nRound: 00651A/0006/0001\r\nCan you help?\n\n### Response:\n[""Comment 1: [\'Hello Bert"", ""Comment 2: could you please indicate which invoices should be adjusted?What exactly has to be changed?!image-2022-12-28-12-35-39-442.png!\'"", ""Comment 3: \'All invoices with the code CALA now have positive gross values while the calculation is -1 x price. These should all have negative gross values.Could you change all of these? \'"", ""Comment 4: \'do wyrzucenia do Excela wartości faktur z CALA jak było i jak będzie i do wysłania do potwierdzenia klientowi.\'"", \'Comment 5: ""[~mbovene@deheus.com]\', \'Comment 6: could you please confirm the lines from Excel\', \'Comment 7: which need\\\'s to change for negative gross values?[^CALA_LAS_ItemsForAdjustements.xlsx]""\', ""Comment 8: \'Could you mail me the file? I cannot open it somehow.\'"", ""Comment 9: \'Hi"", ""Comment 10: it is about row 2 till 48. The totals should be with a minus.\'"", ""Comment 11: \'Hi [~mbovene@deheus.com],At the begining I thought that we only need to change positive to negative sign for values. But I look into Eggs list and I see that before we display values the view data have math operation NetValue * (-1)"", \'Comment 12: VatValue * (-1) and GrossValue * (-1). So\', ""Comment 13: we need to change only the view of Eggs list or we should to update the values to positive on row for lines from Excel file?\'"", ""Comment 14: \'Hi"", \'Comment 15: you can see in the Excel that the new postings (from after 1-10-2022) are all with a positive unit\', ""Comment 16: a positive price and a negative net and gross value.All posings before 1-10-2022 should have the exact same format. Could you change these in that way? \'"", \'Comment 17: ""Hi [~mbovene@deheus.com],The view for Eggs list is good right now? I\\\'m asking becasue one thing is display on list but the other thing are values on documents. The lines on Eggs list have negative price and positive net and gross values\', \'Comment 18: because the invoice lines like price have positive and net and gross have negative values. For sure\', \'Comment 19: are you want to update net and gross invoice values from negative to positive values?If you dont understand what I am talking about\', \'Comment 20: we can call to each other on MS Teams.""\', ""Comment 21: \'YES"", ""Comment 22: I think it is correct right now.\'"", \'Comment 23: ""[~mbovene@deheus.com]\', \'Comment 24: I\\\'ve made changes on lines from Excel file so you can feel free to test.""\', ""Comment 25: \'Confirmed that can be closed.\']""]\nRelated Issues:\n[]\n\n### End'}"
859,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8172\n\n### Instruction:\nWe have an issue with a lot report produced as 15TN and confirmed as 30TN! Which have affected the finished product cost in ERP.\r\n\r\nAlthough the configurations allow 5% tolerance, the system have accepted this tolerance which is 100% higher.\r\n\r\nPCS Lot ID number= 202211230034\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 3: "" !screenshot-1!  !screenshot-2! Dosed jest ~15ton !screenshot-3! b10b0429-ede7-47f8-b275-b108ef7a1a90{code:java}SELECT       [Created]           ,[Event]      ,[EventType]          ,[UserName]      ,[CorrelationId]  FROM [DHPlantProdBusinessLogicEvents].[dbo].[ProductionLots]  where AggregateId=\\\'b10b0429-ede7-47f8-b275-b108ef7a1a90\\\'  and EventType like \\\'%ProductionLotQuantity%\\\'  order by Created{code} !screenshot-4! zmiana przez operatora m.gamal""\', ""Comment 4: \'na teście też tak można wyklikać.\'"", ""Comment 5: \'This field is not related with tolerance.Tolerance is related with this two columns !screenshot-5! and here there are no such differences.If a change to this is required please create a GDC.\'"", ""Comment 6: \'All information was provided in the last comment.This ticket  has been  closed.\']""]\nRelated Issues:\n[]\n\n### End'}"
860,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8171\n\n### Instruction:\n0692231222053 no reservations are assigned please assist in sending the PLR details to the stock module. \r\n\r\nalso kindly share details on how information is resent.\r\n\n\n### Response:\n[""Comment 1: [\'!image-1!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Checked message for create PLR in Stock module  !screenshot-1! In this case PrO is missing PRO-626/12/22  !screenshot-2! And order element (missing order in stock module)  !screenshot-3! Missing data for Business Partner related with Order.  !screenshot-4! Error for BPartner  !screenshot-5! And address was missing  !screenshot-6! *Messages resent from DHP application:*Address for BusinessPartnerOrderProductionOrderPLR finally(ProductionLotCreated and rest of messages for this plr).\'"", ""Comment 4: \'Hello"", \'Comment 5: thank you\', ""Comment 6: task can be closed\']""]\nRelated Issues:\n[\'DGS-8292\']\n\n### End'}"
861,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8170\n\n### Instruction:\nDokument  MMW-181/10/22/Y został odksiegowany przez pracownika ksiegowosci. Dane na dokumncie zostaly poprawione i przy probie ponownego zaksiegowania pojawia sie komunikat jak w załączniku\r\nProsba o rozwiazanie problemu\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Kolejne dokumenty z tym problemem - MMW-455/10/22/Y "", ""Comment 3: MMP-258/10/22/Ł\'"", ""Comment 4: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 5: \'{code:java}  FROM [CDNXL_DEHEUS].[CDN].[TraNag]  where      (TrN_GIDTyp=1603 AND TrN_GIDFirma=246785 AND TrN_GIDNumer=12310450)  select * from cdn.TraSElem where TrS_GIDNumer=12310450  select Dst_KosztUstalono,* from cdn.Dostawy where Dst_GIDNumer in(2699216,2699216,2699216,2699461){code} !screenshot-1! {code:java}  FROM [CDNXL_DEHEUS].[CDN].[TraNag]  where  TrN_GIDTyp=1603  AND TrN_GIDNumer>12310450 and trn_kosztustalono=0{code}\'"", ""Comment 6: \'On the documents was only deleted journal entry or something more has been done?\'"", ""Comment 7: \'Jedynie była przeprowadzona naprawa naglówka a nastepnie proba zaksiegowania!image-1!\'"", \'Comment 8: ""!image-2022-12-30-15-51-20-833.png!{code:java}USE [CDNXL_DEHEUS]GO/****** Object:  StoredProcedure [dbo].[DH_SP_NaprawNaglowekLista]    Script Date: 2022-12-30 15:48:41 ******/SET ANSI_NULLS ONGOSET QUOTED_IDENTIFIER ONGOALTER PROCEDURE [dbo].[DH_SP_NaprawNaglowekLista] (@SQLFiltr varchar(1024))AS--exec DH_SP_NaprawNaglowekLista \\\'(TrN_TrNTyp=6) AND TrN_RokMiesiac=201903\\\'BEGIN\\\\tSET NOCOUNT ON\\\\tdeclare @tabP table (gidtyp int\', ""Comment 9: gidnumer int)\\\\tdeclare @sql nvarchar(max)--,@sf nvarchar(1024)\\\\t--select @sf = \'(TrN_TrNTyp=6) AND TrN_RokMiesiac=201810\'\\\\tselect @sql = N\'select trn_gidtyp,trn_gidnumer from cdn.tranag where \'+@SQLFiltr+\' and trn_gidtyp in (1603,1604,1616,1617)\'\\\\tinsert into @tabP\\\\texec sp_executesql @sql\\\\tDeclare @Wynik bit"", \'Comment 10: @GidNumer int\', \'Comment 11: @GidTyp smallint\\\\tset @Wynik = 0\\\\t\\\\t--//\\\\t--select distinct gidtyp from @tabP\\\\t--select * from cdn.tranag where (TrN_TrNTyp=6) AND TrN_RokMiesiac=201903\\\\tif (select count(distinct gidtyp) from @tabP) = 1\\\\tbegin\\\\t\\\\tIF (select distinct gidtyp from @tabP) IN (1604,1617) -- MMP\', \'Comment 12: PW\\\\t\\\\tBEGIN\\\\t\\\\t\\\\tupdate n\\\\t\\\\t\\\\tset TrN_NettoP = TrS_KosztKsiegowy\\\\t\\\\t\\\\tFrom CDN.TraNag n inner join\\\\t\\\\t\\\\t(Select SUM(CDN.TraSElem.TrS_KosztKsiegowy) as TrS_KosztKsiegowy\', \'Comment 13: TrS_GidNumer\\\\t\\\\t\\\\t\\\\tFrom CDN.TraSelem where TrS_gidTyp IN (1604\', \'Comment 14: 1617)\\\\t\\\\t\\\\t\\\\tGroup By TrS_GidNumer\\\\t\\\\t\\\\t) e on TrN_GidNumer = TrS_GidNumer\\\\t\\\\t\\\\tjoin @tabP on TrN_GidNumer = gidnumer\\\\t\\\\t\\\\twhere TrN_NettoP <> TrS_KosztKsiegowy\\\\t\\\\t\\\\t\\\\t\\\\t\\\\tset @Wynik = 1\\\\t\\\\tEND\\\\t\\\\tELSE IF (select distinct gidtyp from @tabP) IN (1603\', \'Comment 15: 1616) -- MMW\', \'Comment 16: RW\\\\t\\\\tBEGIN\\\\t\\\\t\\\\tupdate n\\\\t\\\\t\\\\tset TrN_NettoR = TrS_KosztKsiegowy\\\\t\\\\t\\\\tFrom CDN.TraNag n inner join\\\\t\\\\t\\\\t(Select SUM(CDN.TraSElem.TrS_KosztKsiegowy) as TrS_KosztKsiegowy\', \'Comment 17: TrS_GidNumer\\\\t\\\\t\\\\t\\\\tFrom CDN.TraSelem where TrS_gidTyp IN (1603\', \'Comment 18: 1616)\\\\t\\\\t\\\\t\\\\tGroup By TrS_GidNumer\\\\t\\\\t\\\\t) e on TrN_GidNumer = TrS_GidNumer\\\\t\\\\t\\\\tjoin @tabP on TrN_GidNumer = gidnumer\\\\t\\\\t\\\\twhere TrN_NettoR <> TrS_KosztKsiegowy\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t\\\\t\\\\tset @Wynik = 1\\\\t\\\\tEND    end\\\\tupdate e set \\\\t\\\\tTre_KosztKsiegowy = TrS_KosztKsiegowy,\\\\t\\\\tTre_KosztRzeczywisty = TrS_KosztRzeczywisty\', \'Comment 19: \\\\t\\\\ttre_wartoscporabacie = TrS_KosztKsiegowy\', \'Comment 20: \\\\t\\\\tTre_ksiegowanetto = TrS_KosztKsiegowy\', \'Comment 21: \\\\t\\\\tTrE_Rzeczywistanetto = TrS_KosztKsiegowy,\\\\t\\\\tTrE_KsiegowaBrutto = TrS_KosztKsiegowy\\\\tFrom CDN.TraElem e inner join\\\\t(Select SUM(CDN.TraSElem.TrS_KosztKsiegowy) as TrS_KosztKsiegowy\', \'Comment 22: \\\\t\\\\t\\\\tSUM(CDN.TraSElem.TrS_KosztRzeczywisty) as TrS_KosztRzeczywisty\', \'Comment 23: \\\\t\\\\t\\\\tTrS_GidNumer\', \'Comment 24: TrS_GidLp\\\\t\\\\tFrom CDN.TraSelem where TrS_gidTyp in (1603,1604\', \'Comment 25: 1616\', \'Comment 26: 1617)\\\\t\\\\tGroup By TrS_GidNumer\', \'Comment 27: TrS_GidLp\\\\t) s on TrE_GidNumer = Trs_GidNumer and TrE_GidLp = TrS_GidLp\\\\twhere \\\\t(\\\\t\\\\tTre_KosztKsiegowy <> TrS_KosztKsiegowy \\\\t\\\\tor Tre_KosztRzeczywisty <> TrS_KosztRzeczywisty \\\\t\\\\tor TRE_ksiegowanetto <> TrS_KosztKsiegowy\\\\t) \\\\tand exists(select * from cdn.Tranag join @tabP on TrN_GidNumer = gidnumer where trn_gidtyp = tre_gidtyp and trn_gidnumer = tre_gidnumer)\\\\t    IF @Wynik = 1    BEGIN\\\\t\\\\tSelect 1 as Lp\', ""Comment 28: \'Dokumenty został zmodyfikowane\'    END    ELSE    BEGIn\\\\t\\\\tSelect 1 as Lp"", \'Comment 29: \\\'Dokumenty nie został zmodyfikowane.\\\'    END\\\\t\\\\tSET NOCOUNT offEND{code}""\', ""Comment 30: \'{code:java} select  trn_kosztustalono,* FROM [CDNXL_DEHEUS].[CDN].[TraNag]  where  TrN_GIDTyp in(1603,1604)  AND trn_kosztustalono=0{code}KROdznaczKosztDokumentu\'"", ""Comment 31: \'It was a column for tranag (trn_kosztustalono should be =1) on the document but deleted journal entry not change that.\'"", ""Comment 32: \'Task to close\']""]\nRelated Issues:\n[]\n\n### End'}"
862,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8169\n\n### Instruction:\nFind attached the error johnson dhp\n\n### Response:\n[\'Comment 1: [""Helllo \', \'Comment 2: I don\\\'t see the attachment.What is the problem? Is it blocking the operation of the application ?Regards""\', ""Comment 3: \'{color:#212121}This is the error{color} ----!20221228_082301.jpg|thumbnail!\'"", ""Comment 4: \'!image-2022-12-28-16-06-15-425.png!\'"", ""Comment 5: \'Baza wporzo"", ""Comment 6: a nie potrafię się do planta zalogować!image-2022-12-28-16-08-30-617.png!!image-2022-12-28-16-09-11-205.png!\'"", \'Comment 7: \\\'{code:java}2022-12-28 14:58:11 (/Plant.VC.BusinessLogic/GHAPP04/11000/8) [Warning] RawRabbit.Channel.ChannelFactory - Connection was shutdown by Application. ReplyText ""Connection close forced""{code}{code:java}2022-12-28 14:57:46 (/Plant.VC.BusinessLogic/GHAPP04/11000/1) [Warning] Microsoft.AspNetCore.DataProtection.Repositories.EphemeralXmlRepository - Using an in-memory repository. Keys will not be persisted to storage.2022-12-28 14:57:46 (/Plant.VC.BusinessLogic/GHAPP04/11000/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.2022-12-28 14:57:46 (/Plant.VC.BusinessLogic/GHAPP04/11000/1) [Warning] Microsoft.AspNetCore.DataProtection.KeyManagement.XmlKeyManager - No XML encryptor configured. Key {c647e576-05d2-4e87-9bca-807cedfe3d45} may be persisted to storage in unencrypted form.2022-12-28 14:58:14 (/Plant.VC.BusinessLogic/GHAPP04/16028/1) [Warning] Microsoft.AspNetCore.DataProtection.Repositories.EphemeralXmlRepository - Using an in-memory repository. Keys will not be persisted to storage.2022-12-28 14:58:14 (/Plant.VC.BusinessLogic/GHAPP04/16028/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.2022-12-28 14:58:14 (/Plant.VC.BusinessLogic/GHAPP04/16028/1) [Warning] Microsoft.AspNetCore.DataProtection.KeyManagement.XmlKeyManager - No XML encryptor configured. Key {85bae519-fb29-43dd-806d-2d23d27e4618} may be persisted to storage in unencrypted form.{code}\\\'\', ""Comment 8: \'Please"", ""Comment 9: verify now. I have restarted applicationRegards\'"", ""Comment 10: \'it is working"", ""Comment 11: thanks\'"", ""Comment 12: \'please close\']""]\nRelated Issues:\n[]\n\n### End'}"
863,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8168\n\n### Instruction:\nWe have problem with some items/Unit load with wrong reservation. The productions are closed but they still are reserving some unit load. \r\n\r\nExample production 0881031122029, 0881031122030 and 0881031122038\r\n\r\nCould you check why reservation was not done when productions were closed, check if we have more productions with the same error and fix it?\r\n\r\nIt\'s urgent because system not allow to move or make inventory for unit load with reservation.\r\n\r\nThank you\r\n\r\n\n\n### Response:\n[""Comment 1: [\'[~tomasz.nojek@kotrak.com]"", ""Comment 2: [~maciej.dobrzanski@kotrak.com]* pierwszy update w AP do wersji 8.3 był zrobiony 02.12.2022* ostatni update w AP do wersji 8.3 był zrobiony 11.01.2023\'"", ""Comment 3: \'[~psilva@deheus.com]"", ""Comment 4: Maiconfix for it was done to the release 8.5\'"", ""Comment 5: \'Hi [~marcin.klesz@kotrak.com]Thank you very much\'"", ""Comment 6: \'We need to wait for an update to 8.5After that we can check if we have some data to be verified yet.\'"", ""Comment 7: \'Ok"", ""Comment 8: we are waiting update in all units. Thank you.\']""]\nRelated Issues:\n[\'DGS-8087\', \'DGS-8102\', \'DAP-13157\', \'DGS-8184\', \'DGS-8185\']\n\n### End'}"
864,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8167\n\n### Instruction:\nCan you change all the feed from 806514/0004/0001 to 00651A/0006/0001\r\n\r\nThankx\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Hello BertCould you please confirm the lines from the Excel must be moved from Feed Sale 806514/0004/0001 to 00651A/0006/0001?[^feed sale 80651400040001-1.xls]\'"", ""Comment 3: \'Yes"", ""Comment 4: I confirm.\'"", ""Comment 5: \'[~damian.swistek@kotrak.com]\'"", ""Comment 6: \'[~mbovene@deheus.com]"", ""Comment 7: I did it for all lines of Feed Sale. You can feel free to test it.\'"", ""Comment 8: \'OK!\'"", ""Comment 9: \'[~mbovene@deheus.com]"", ""Comment 10: everything is ok? Can we close the task?\'"", ""Comment 11: \'Yes\']""]\nRelated Issues:\n[]\n\n### End'}"
865,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8166\n\n### Instruction:\nCan you set ID 80567 back to entry?\n\n### Response:\n[""Comment 1: [\'[~khuibers@deheus.com]"", ""Comment 2: this document is in your Inbox now. Could you check and send me feedback?\'"", ""Comment 3: \'I close this task!image-2022-12-30-09-52-49-445.png!\']""]\nRelated Issues:\n[]\n\n### End'}"
866,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8165\n\n### Instruction:\nI can not reverse SR ID 53785, can you check this? \n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Grzesiu"", \'Comment 4: sprawdzisz jaka jest dostępność akcji ""Reverse Slaughtery Report"" i czemu tutaj jest ona niedostępna? ID 53785\\\'\', ""Comment 5: \'Runda nie jest aktywna"", ""Comment 6: a to jest waurnek mozliwosci skorzystania z Reversa ;)\'"", ""Comment 7: \'[~DGeerenstein@deheus.com]"", ""Comment 8: Round document linked with this Slaughtery Report is not in Active status. In this case the Reverse SR is not avaliable.\'"", ""Comment 9: \'Dirco"", \'Comment 10: was S2P SP-M/0090 settled in MILAS? If NO\', ""Comment 11: would you like us to reopen a Round 001291/0009/0001 and its Feed Sale?\'"", ""Comment 12: \'[~DGeerenstein@deheus.com]could we close the task?\'"", ""Comment 13: \'[~DGeerenstein@deheus.com]could you confim?\'"", ""Comment 14: \'Dirco has been on sick leave since that day. I will check if it is correct.\'"", ""Comment 15: \'Can be closed.\']""]\nRelated Issues:\n[]\n\n### End'}"
867,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8164\n\n### Instruction:\nGoodmorning,\r\n\r\nWould you so kind to create an opening balance for item 1106 on plant Andel. Quantity is 500.\r\n\r\nKind regards,\r\n\r\nGerard Geerts\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: \'Opening balance has been created: !screenshot-1! \'"", ""Comment 3: \'[[DHP 3.0] Dodanie zasobu dla towaru gdzie ma zerowy stan,nowy towar.|onenote:https://kotrak.sharepoint.com/sites/erpasysta/Shared%20Documents/Baza%20wiedzy/Baza%20Wiedzy%20-%20ERPSD/Klienci/DEHEUS/DEHEUS%20APPLICATIONS/Holandia%20Premix%20i%20AS400/Baz%20wiedzy%20z%20AS400.one#%5bDHP%203.0%5d%20Dodanie%20zasobu%20dla%20towaru%20gdzie%20ma&section-id=\\\\\\\\{9BB564BA-0B58-4580-B9E0-F3CF9D6D80A7}&page-id=\\\\\\\\{D1C537B5-AE6F-4968-90A4-A0999AF8CCF5}&end] ([Widok sieci Web|https://kotrak.sharepoint.com/sites/erpasysta/_layouts/OneNote.aspx?id=%2Fsites%2Ferpasysta%2FShared%20Documents%2FBaza%20wiedzy%2FBaza%20Wiedzy%20-%20ERPSD&wd=target%28Klienci%2FDEHEUS%2FDEHEUS%20APPLICATIONS%2FHolandia%20Premix%20i%20AS400%2FBaz%20wiedzy%20z%20AS400.one%7C9BB564BA-0B58-4580-B9E0-F3CF9D6D80A7%2F%5BDHP%203.0%5D%20Dodanie%20zasobu%20dla%20towaru%20gdzie%20ma%7CD1C537B5-AE6F-4968-90A4-A0999AF8CCF5%2F%29])\'"", ""Comment 4: \'Hello Piotr,thanks for your support.You may close this ticket.Kind regards,Gerard\']""]\nRelated Issues:\n[]\n\n### End'}"
868,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8163\n\n### Instruction:\nGood morning,\r\n\r\nWe have a problem with article 0694.\r\n\r\nErrors:\r\nRecipeImport, product of ID 26470 and code \'702082.NL\', ingredient of ID 72193 for article \'0694\' - Could not link item \'0694\' to BestMix item \'0694\' (ID 72193) because it is already linked to BestMix item \'00694\' (ID 5694).\r\n\r\nWould you be so kind as to link Bestmix item 0694 with Erp item 0694?\r\n\r\nKind regards,\r\n\r\nGerard Geerts\r\n\r\n\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Hello,What should be the linked code?Is it correctly linked?I see two codes in the notification00694"", ""Comment 3: 0694Which is the correct code ?!image-2022-12-27-10-48-57-055.png!!image-2022-12-27-10-49-31-412.png!Regards\'"", ""Comment 4: \'Hello Adrian,Raw material codes have 4 digits"", ""Comment 5: so 0694 is the correct one.Kind regards,Gerard\'"", ""Comment 6: \'Is the problem with importing the DHH recipe or writing it in DHC?\'"", ""Comment 7: \'Writing it in DHC\'"", ""Comment 8: \'Hi Gerard,Could you please let me know for what item recipe is missing? Was it sent from DHH?Regards\'"", \'Comment 9: ""Goodmorning Aleksandra,Maybe this information will help you to investigate the problem? Item that formulation tried to send is 702082Error message they received (I think in Dhh):Recipe imported from file: \\\'R-08-702082-0001.xml\\\' Errors:RecipeImport\', ""Comment 10: product of ID 26470 and code \'702082.NL\'"", \'Comment 11: ingredient of ID 72193 for article \\\'0694\\\' - Could not link item \\\'0694\\\' to BestMix item \\\'0694\\\' (ID 72193) because it is already linked to BestMix item \\\'00694\\\' (ID 5694).Kind regards,Gerard""\', ""Comment 12: \'!bestmix code_dhh.PNG|thumbnail! !bestmix code_dhh-1.PNG|thumbnail!\'"", ""Comment 13: \'!linkin0694.PNG|thumbnail! !bestimx codes_dhc.PNG|thumbnail!\'"", ""Comment 14: \'The error is during import from bestmix to DHHolding not DHC.I changed it in task ?!image-2022-12-28-08-09-06-323.png|width=779,height=145!The error indicates errors in the XML file.  Is it possible to verify them by Bestmix users ? Did they used a correct bestmix code ?Because according to the error there should be a bestmix code \\\\\'0694\\\\\' but in DHH and DHC there is only bestmix code started with double \\\\\'00\\\\\'- \\\\\'00694\\\\\' and that bestmix code has been linked with base item \\\\\'0694\\\\\'.In DHH!image-2022-12-28-08-14-24-313.png!In DHC:!linkin0694.PNG!Base Item in DHC can not be set as the Base Item for more then 1 bestmix code.There is no possibility to linked 0694 bestmix code with item 0694 because bestmix code 0694 was not created nor in DHH nor send to DHC.Is it possible that in this situation there was a mistake"", \'Comment 15: a ""typo"" when creating the XML file?Please verify first of all whether you used the correct bestmix code - 0694 - or whether it should have been 00694. If it turns out that bestmix code 0694 should have been created and linked to baseitem 0694 in DHC\', ""Comment 16: please let me know.The bestmix item should also be added by import via bestmix user to DHH.\'"", ""Comment 17: \'I also checked in DHH database that the external id72193 is for item with bestmixcode6000694 this item is not mapped.!image-2022-12-28-08-46-00-035.png!This code is not in the DHC.\'"", ""Comment 18: \'Good afternoon Agnieska,I asked the Bestmix-user to check this. After a response from him/her I will inform you.Regards,Gerard\'"", ""Comment 19: \'Hi,Waiting for your feedback then.Regards\'"", ""Comment 20: \'Hello,Kindly approve lowering priority of this task to P2 as P1 issues are only those with a critical or a blocking impact on business processes . This seems not to be the case in this issue so we suggest decreasing the issue priority.Regards\'"", ""Comment 21: \'Hello,is okayRegards\'"", ""Comment 22: \'Thank you for your information. Can we close this task?Regards\'"", \'Comment 23: ""I mean it\\\'s ok\', \'Comment 24: we can lower or you got the info from DHH that it is okay now.Regards""\', \'Comment 25: ""Goodmorning Aleksandra,I\\\'am waiting for feedback from our Bestmix user.After that you got an answer from me\', \'Comment 26: if we can close this ticket.RegardsGerard""\', ""Comment 27: \'Goodmorning Aleksandra,please"", ""Comment 28: delete this link (0694 - 00694).Regards,Gerard\'"", \'Comment 29: ""is it about linking in DHC?Are you aware that after linking :- all objects that contain the 0694 commodity etc. will not be transferred to DHP?Do you want to link as baseitem 0684 with bstmix code 0694? If so\', \'Comment 30: have you verified the codes you are sending on the basis of the information we sent you?Does the bestmix code \\\'0694\\\' exist in DHH and you send it to dhc ( or will send it)?""\', ""Comment 31: \'Dear Agnieszka,I needed feedback to get an answer for you.Please"", ""Comment 32: delete de link on DHH 0694 - 00694.Reagards,Gerard\'"", ""Comment 33: \'Please provide a screenshoot from{color:#de350b}*DHH*{color:#172b4d}where will be visible a place you need to be changed.{color}{color}{color:#de350b}{color:#172b4d}Linkin item is typical funcionality in {color:#00875a}*DHC.*{color}{color}{color}\'"", ""Comment 34: \'Dear Agnieszka,This it what i saw in DHH.Regards,Gerard!image!\'"", ""Comment 35: \'[[DHH] Item relink|#%5bDHH%5d%20Item%20relink&section-id=\\\\\\\\{5ED4D707-EBBC-46B1-96F0-D5469A4C1D69}&page-id=\\\\\\\\{2096B3FD-1DE0-4D7F-ACE2-8A534B75C6FC}&end] ([Widok sieci Web|https://kotrak.sharepoint.com/sites/erpasysta/_layouts/OneNote.aspx?id=%2Fsites%2Ferpasysta%2FShared%20Documents%2FBaza%20wiedzy%2FBaza%20Wiedzy%20-%20ERPSD&wd=target%28Klienci%2FDEHEUS%2FDEHEUS%20APPLICATIONS%2FHolandia%20Holding%20-%20Centrala%2FBaza%20wiedzy.one%7C5ED4D707-EBBC-46B1-96F0-D5469A4C1D69%2F%5BDHH%5D%20Item%20relink%7C2096B3FD-1DE0-4D7F-ACE2-8A534B75C6FC%2F%29]),[[DHH/DHC] Itemy nie przechodzą do AS400|onenote:https://kotrak.sharepoint.com/sites/erpasysta/Shared%20Documents/Baza%20wiedzy/Baza%20Wiedzy%20-%20ERPSD/Klienci/DEHEUS/DEHEUS%20APPLICATIONS/Holandia%20Holding%20-%20Centrala/Baza%20wiedzy.one#%5bDHH/DHC%5d%20Itemy%20nie%20przechodz%C4%85%20do%20AS400&section-id=\\\\\\\\{5ED4D707-EBBC-46B1-96F0-D5469A4C1D69}&page-id=\\\\\\\\{3D17ABC1-0EC3-49F6-AB5E-A41A33A2AABB}&end] ([Widok sieci Web|https://kotrak.sharepoint.com/sites/erpasysta/_layouts/OneNote.aspx?id=%2Fsites%2Ferpasysta%2FShared%20Documents%2FBaza%20wiedzy%2FBaza%20Wiedzy%20-%20ERPSD&wd=target%28Klienci%2FDEHEUS%2FDEHEUS%20APPLICATIONS%2FHolandia%20Holding%20-%20Centrala%2FBaza%20wiedzy.one%7C5ED4D707-EBBC-46B1-96F0-D5469A4C1D69%2F%5BDHH%5C%2FDHC%5D%20Itemy%20nie%20przechodz%C4%85%20do%20AS400%7C3D17ABC1-0EC3-49F6-AB5E-A41A33A2AABB%2F%29])\'"", ""Comment 36: \'Please contact your Global Nutrion branch. The employees of this division have access to remove linking of this product from the dhh holding application.!image-2022-12-30-15-16-27-948.png!\'"", ""Comment 37: \'Dear Agnieszka,this issue is solved by our Nutrition Department.Thanks for support on this"", ""Comment 38: please close this ticketKind regards,Gerard\']""]\nRelated Issues:\n[]\n\n### End'}"
869,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8162\n\n### Instruction:\nWe have problem to print dummy label in all units with DHP 3.0. The labels are always duplicating, we already checked the printers, but still have problem.\r\n\r\nCould you please check why they are duplicating?\r\n\r\nThank you\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 3: \\\'Please give us more details related to this issue.Did duplicated labels are generated on one computer or on multiple machines.Did this happen all each time You are trying to generate dummy label.Did generated labels got the same barcode. Please provide us an example of such barcode. Please provide us with scan of duplicated labels.How printers are configured. Are set to print one label or to create multiple copies of printout.Exacly how do you set parameter ""Select number of pallet to print"" while printing dummy label.!image-2022-12-27-09-03-26-843.png!I\\\\\\\'ve checked label definition and there is no issue with it. Definition is ready to generate one set of prepared dummy labels.If there are multiple labels to print\', ""Comment 4: they will always be print it in two columns.\'"", ""Comment 5: \'Hi Bartłomiej*Did duplicated labels are generated on one computer or on multiple machines.*bq. There\\\\\'s no pattern on it. No matter the computer"", \'Comment 6: the printer is duplicating the labels*Did this happen all each time You are trying to generate dummy label.*bq. Yes! No matter the quantity\', \'Comment 7: 10 or 100 or 1000 new dummy label\', \'Comment 8: the printer reprint the queue of dummy labels*Did generated labels got the same barcode. Please provide us an example of such barcode. Please provide us with scan of duplicated labels.*bq. I requested the scan of these duplicated labels to the factory*How printers are configured. Are set to print one label or to create multiple copies of printout.*bq. The printer is the ZDesigner ZT230-300dpi ZPL. We don\\\\\\\'t have option to create multiple copies of printout*Exacly how do you set parameter ""Select number of pallet to print"" while printing dummy label.*bq. We type the number we want\', \'Comment 9: for example: 100\', ""Comment 10: then we click in the blue button *PRINT*!image-1!\'"", ""Comment 11: \'Hi Maicon,Do we have scans of duplicated labels? Those scans can tell us a lot in terms of how printer behave.\'"", ""Comment 12: \'Jako"", \'Comment 13: że w wersji DHP 3.0 mamy ten sam mechanizm przeniesiony z DHP 2.7\', \'Comment 14: a pamiętam jedynie\', ""Comment 15: że podobne zgłoszenia były również z DHPL na początku implementacji w 2013-2014 roku. Później były robione jakieś zmiany aby temu zapobiegać ale szczegóły może będzie pamiętał Przemek Przybyszewski. Generalnie jeśli wysyłamy listę kodów do drukarki to prawdopodobnie sama drukarka z tego co pamiętam dublowała te etykiety. Nie mamy pełnej kontroli wydruku z drukarki i odpowiedzi na błędy ewentualne.\'"", ""Comment 16: \'Hi BartłomiejHere goes the scans.Thank you!DuplicatedDummyLabel!!DuplicatedDummyLabel_edited!\'"", ""Comment 17: \'!image-2022-12-30-09-44-30-758.png!\'"", ""Comment 18: \'kopiowane są całe sekcje co wskazuje na wadliwe działanie drukarki... drukarka wyrzuca 2 kopie labelek generowanych w pakiecie po 10 sztuk.w bazie w tabeli[DHPlantWmsBusinessLogicMain].dbo.DummyLabels te kody są tylko 1 raz\'"", \'Comment 19: \\\'Hi Maicon,Can You send me an printer configuration as well?Especially how reprint mode option is set.Also please let me know if You can recreate this issue ""on demand"". Please let me know what steps are needed to recreate this issue.\\\'\', \'Comment 20: ""Hi BartłomiejI don\\\'t think the printer has this configuration. I searched but didn\\\'t find it.About the steps to recreate this issue\', \'Comment 21: we just open the _Unit loads_ screen in WMS engine\', \'Comment 22: click in the *Print dummy label* button and then the printer starts printing.??FYI: We use this same printer to other applications like STARLIMS\', \'Comment 23: and there\\\'s no such issue with these applications. Only when we send from DHP 3.0 dummy labels??!image-2!!image-3!!image-4!!image-5!!image-6!!image-7!""\', ""Comment 24: \'According to printer manual those are the steps you should do to print this configuration!image-2022-12-30-13-39-20-333.png!!image-2022-12-30-13-39-32-518.png!!image-2022-12-30-13-39-45-073.png!\'"", \'Comment 25: ""Hi Maicon,I renew my request for printer configuration information.Especially how reprint mode option is set.I\\\'ve send you description how it is described in manual.""\', ""Comment 26: \'Hi BartłomiejUnfortunatelly the printer configuration is in portuguese"", ""Comment 27: but I checked the *reprint mode option* and is DISABLED as you can see in the screenshot.What is the next step?!image-8![^printer settings zt230.pdf] _(36 kB)_\'"", ""Comment 28: \'Dane w bazie danych wyglądają prawidłowo. Definicja wydruku również wygląda prawidłowo.Konfiguracja zebry wydaje się poprawna.Wygląda na problem ze sporadyczna duplikacją wysyłanych na drukarkę wydruków...\'"", ""Comment 29: \'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 30: \'HiHere is the printers docs from spoolThank you[^PRINTERSpool.zip] _(17 kB)_\'"", \'Comment 31: \\\'{""parameters"":[{""name"":""businessUnitId"",""value"":""886b344a-1a75-4b04-8c67-5c5410642429""},{""name"":""Barcode"",""value"":""85-W02506""}],""printoutId"":""55b75d01-9add-4cbd-b294-3a702ade9d98"",""copies"":1}\\\'\', ""Comment 32: \'[~bartlomiej.brzek@kotrak.com],Znaleźliśmy błąd w aplikacji. Fix będzie zaimplementowany w wersji 8.5.Procedowany jest w tasku: DAP-13204\'"", ""Comment 33: \'Hello,We have found application bug. The fix ill be implemented in version 8.5.Please"", ""Comment 34: let us know if we can close this task.Regards\'"", ""Comment 35: \'Hi AleksandraYou can close this taskThank you very much\'"", ""Comment 36: \'Thank you.Regards\']""]\nRelated Issues:\n[\'DAP-13204\']\n\n### End'}"
870,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8161\n\n### Instruction:\nHi, \r\n\r\nWe would like to add new database on CDN XL and we try it from CDN MGR. \r\nAfter we click ""Create Database"", application is hang. Sometimes, it will appear after 2 hour waiting. Sometime, totally not appear in 3 or 4 hours. \r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image-1!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Hello Clara"", ""Comment 4: Please run CDN MGR as Administrator!image-2022-12-27-07-07-21-041.png|width=529,height=236!Please choose the option Connect Data Base.Select the environment base on SQL.I understand you want to add an existing base ? Regards.\'"", ""Comment 5: \'Hi"", \'Comment 6: You are right\', ""Comment 7: we would like to add existing base. I do follow as per your suggestion.Application is not response any. I do wait about 30 minutes. And freeze as attached. !image!\'"", ""Comment 8: \'Hello,Please tell me where location"", \'Comment 9: this base is in server 10.95.1.18 ??CDNMGR application is on a server\', \'Comment 10: terminal\', ""Comment 11: workstation?Regards\'"", ""Comment 12: \'Hi"", \'Comment 13: This is Food Business. And CDN XL version is 2020.1) Production Server => 10.95.1.41:33392) Test Server => 10.95.5.8CDNMGR application is on Terminal Server.Regards\', ""Comment 14: Clara\'"", ""Comment 15: \'Hi"", \'Comment 16: Clara\', ""Comment 17: please open application CDN XLSystem - Key !image-2022-12-27-10-56-00-010.png!Enter your license key hereCDNMGR application should work correctly Please check\'"", \'Comment 18: \\\'I do try 2 days in Test Environment. Once I click ""Klucz"" (highlighted one)\', \'Comment 19: application is hanged. ""No response"" at all. \\\'\', ""Comment 20: \'zmiana z nazwy na adres !screenshot-1! \'"", ""Comment 21: \'After the chat on teams"", ""Comment 22: please check how the connection of databases and translations looks like in XL.Regards.\'"", ""Comment 23: \'Now is working well. ThanksYou can close the this ticket. \']""]\nRelated Issues:\n[]\n\n### End'}"
871,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8160\n\n### Instruction:\nBrak mozliwości odpiecia awizacji z VT\r\nVT-18854/12/22\r\nWytwornia Podkonice\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Chodzi o wytwornie Podkonice ( w tasku omyłkowo wybrany Janowiec )\'"", ""Comment 3: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 4: \'Please verify.\'"", ""Comment 5: \'Thanks. Task to closeWhere was a problem ??\'"", \'Comment 6: ""Item \\\'SILOS BAG\\\' had Packingform=4 for which the disconnect option is not displayed.I changed back to Packingform=2 for the VT element.""\', ""Comment 7: \'[[DHP] Brak możliwości odpięcia awizacji z VT / odpinanie awizacji|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%20Brak%20mo%C5%BCliwo%C5%9Bci%20odpi%C4%99cia%20awizacji%20z%20VT%20/%20odpinanie&section-id=\\\\\\\\{F3B54834-6A02-4FD8-B2D4-74ADCAEDC4E9}&page-id=\\\\\\\\{B055159F-C936-4779-B1BC-FE1E946260F9}&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%20Brak%20mo%C5%BCliwo%C5%9Bci%20odpi%C4%99cia%20awizacji%20z%20VT%20%5C%2F%20odpinanie%7CB055159F-C936-4779-B1BC-FE1E946260F9%2F%29])\']""]\nRelated Issues:\n[]\n\n### End'}"
872,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8159\n\n### Instruction:\nHi\r\n\r\nWe have a problem with DHC x DHP Orders integration with Foreigh document numbers:\r\nOVE-071931\r\nOVE-071909\r\n\r\nThey were integrated from ERP to DHC with success, however they weren\'t integrated from DHC to DHP because the OrderElements wasn\'t liked yet.\r\nWhen items were linked, DHC didn\'t tried to resend to DHP.\r\nThis is happening a lot, but we never have time to analyze it.\r\nCould you please check why DHC is not resending blocked orders to DHP after the link process?\r\nAnd then, please, after finding the root cause of the problem, send this Orders because factory needs to plan the production.\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: ""{quote}SELECT * FROM Evolution_DHCountry.[dbo].[Orders] where ForeignDocumentNumber in (\\\'OVE-071931\\\',\\\'OVE-071909\\\')SELECT * FROM Evolution_DHCService.[dbo].[Orders] where ForeignDocumentNumber in (\\\'OVE-071931\\\',\\\'OVE-071909\\\')SELECT * FROM Evolution_DHCountry.[dbo].[OrderElements] where OrderId in (\\\'6C87646B-94BB-432C-86A4-2E7A661FB15F\\\',\\\'CA8D93F4-F52C-4B34-BA03-7DDCACA1A56C\\\')SELECT * FROM Evolution_DHCService.[dbo].[OrderElements] where OrderId in (\\\'6C87646B-94BB-432C-86A4-2E7A661FB15F\\\',\\\'CA8D93F4-F52C-4B34-BA03-7DDCACA1A56C\\\')SELECT * FROM Evolution_DHCountry.[dbo].Items where id in (\\\'C87923B7-BD1D-46D1-9B88-0FD5BF96E7D6\\\',\\\'DBC571BF-6860-4260-A709-577233D8D28E\\\')SELECT * FROM Evolution_DHCService.[dbo].Items where id in (\\\'C87923B7-BD1D-46D1-9B88-0FD5BF96E7D6\\\',\\\'DBC571BF-6860-4260-A709-577233D8D28E\\\')SELECT * FROM Evolution_DHCountry.[dbo].dhhItems where id in (\\\'E3BD4A01-45C2-400C-B5AE-465FAFB9D073\\\',\\\'C83D7CB2-449A-407F-8481-1B2D2F4B31E0\\\')SELECT * FROM Evolution_DHCService.[dbo].DhhItems where id in (\\\'E3BD4A01-45C2-400C-B5AE-465FAFB9D073\\\',\\\'C83D7CB2-449A-407F-8481-1B2D2F4B31E0\\\')select * from Evolution_DHCService.[dbo].OrderExportInfoes where entityid in (\\\'6C87646B-94BB-432C-86A4-2E7A661FB15F\\\',\\\'CA8D93F4-F52C-4B34-BA03-7DDCACA1A56C\\\')SELECT * FROM Evolution_DHCountry.[dbo].Recipes where id in (\\\'FF3675A0-D86C-4546-9B6F-9B4F0CDA2FEF\\\',\\\'C2DE340B-607C-43E8-906B-6A2CC09B33D6\\\')SELECT * FROM Evolution_DHCService.[dbo].Recipes where id in (\\\'FF3675A0-D86C-4546-9B6F-9B4F0CDA2FEF\\\',\\\'C2DE340B-607C-43E8-906B-6A2CC09B33D6\\\')SELECT * FROM Evolution_DHCountry.[dbo].ProductionRecipes where id in (\\\'926E0EDF-6581-441A-9D8D-1F0AC6BDC7D7\\\',\\\'1C8B8692-049F-4FBA-9311-622722B5A678\\\')SELECT * FROM Evolution_DHCService.[dbo].ProductionRecipes where id in (\\\'926E0EDF-6581-441A-9D8D-1F0AC6BDC7D7\\\',\\\'1C8B8692-049F-4FBA-9311-622722B5A678\\\')SELECT * FROM Evolution_DHCountry.[dbo].Technologies where ItemId in (\\\'C87923B7-BD1D-46D1-9B88-0FD5BF96E7D6\\\',\\\'DBC571BF-6860-4260-A709-577233D8D28E\\\')SELECT * FROM Evolution_DHCService.[dbo].Technologies where ItemId in (\\\'C87923B7-BD1D-46D1-9B88-0FD5BF96E7D6\\\',\\\'DBC571BF-6860-4260-A709-577233D8D28E\\\'){quote}Brak wpisów po stronieEvolution_DHCService w tabelach:Orders\', \'Comment 3: OrderElements,ProductionRecipes orazTechnologiesBrak wpisów wEvolution_DHCService.[dbo].OrderExportInfoesPróby wywołania resynchronizacji spełzły na niczym""\', ""Comment 4: \'HiDo we have any news about this issue?Thank you\'"", \'Comment 5: ""I found one more Sales Order that didn\\\'t integrate:OVE-071921""\', ""Comment 6: \'Could you please resend all 3 order again to dhc from your erp?\'"", \'Comment 7: ""Hi AgnieszkaI just resend and it worked.However I need to know why this happened and keeps happening.This is not the first time and this is really complicated because the factory doesn\\\'t receive the Order in DHP\', \'Comment 8: so they do not plan the production\', \'Comment 9: when the customer arrives to get load the product is not ready.We are over and over having such problem\', \'Comment 10: so we need this fixed or at least\', \'Comment 11: an alert message for someone acts when the order get blocked for unlinking product.Thank you""\', ""Comment 12: \'Hello,Yes when the order is already in DHC Country and some item is not linked"", ""Comment 13: after linkin it correctly it should be resend. This is the best way to update everything related to that item and order.In this task we have focused on clearingandunblocking the process.If You need to make some changes - like error messages -please create a GDC task.May we close the task?\'"", \'Comment 14: ""Hi AgnieszkaI\\\'m sorry! I don\\\'t if I was clear\', ""Comment 15: but I need you to investigate why this *after linkin it correctly it should be resend* didn\'t happened.As far as I remember"", \'Comment 16: [~przemyslaw.przybyszewski@kotrak.com] informed that this resend after linking is a DHC functionality. However\', \'Comment 17: as I described in this DGS\', \'Comment 18: this is not working. And I don\\\'t know where is the log description about why it didn\\\'t work.Could you please investigate it?Thank you""\', ""Comment 19: \'I raised RCA task to inestigate this issueDGS-8177.May we close this task andIn this task we have focused on clearingandunblocking the process.So may we close this one and procceed analisys in RCa task?\'"", ""Comment 20: \'Thank you for this RCA.You can close this task.\']""]\nRelated Issues:\n[\'DGS-8177\']\n\n### End'}"
873,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8158\n\n### Instruction:\nHi Damian,\r\n\r\nWe come to the conclusion that registration bookings on one side don\'t come on the round. \r\nThe thing we talked about was ID80291.\r\n\r\nThanks very much for your help.\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: ""Z rozmowy z Christine i Richardem wynika\', \'Comment 3: że powinniśmy dodać w NAS\', \'Comment 4: gdzie jest to najpilniejsze obsługę faktur typu Registered\', ""Comment 5: które są \'Booked on one side\' i powinno to być dodane dla wszystkich kategorii (Calves"", \'Comment 6: Expenses\', \'Comment 7: Slaughtery\', \'Comment 8: Feed). Niedawno dodawaliśmy już obsługę takiej relację do NAS dla kategorii Slaughtery https://helpdesk.kotrak.com/browse/DGS-8047Na Rundzie i FS pokazujemy tylko faktury\', \'Comment 9: które są wygenerowane z innych i dlatego nie są widoczne te\', \'Comment 10: które są stworzone z ręki w Intense bez dokumentu wiodącego.Z tego co zrozumiałem to faktury takie tworzone są po to\', \'Comment 11: aby skorygować błędne dane\', \'Comment 12: prawdopodobnie z migracji.Do analizy wewnętrznej z [~ewa.mucha@kotrak.com] i ewentualnie do ustalenia czy powinniśmy to także przewidzieć w innych sektorach.""\', ""Comment 13: \'Dodanie relacji wiąże się ze zmianami na: * listach umieszczonych na zakładkach rundy oraz tekstami dynamicznymi * listach na zakładkach Financial Statement (general"", \'Comment 14: details) * saldo Financial Statement * wydruk FS * jeśli relacja dotyczy MAS NL albo BE\', ""Comment 15: to do sprawdzenia Technical ResultsPodczas dodania nowej relacji należy określić strony faktury: * jeśli PI to jaki typ customer w polu Supplier * jeśli SI to jaki typ customer w polu Customer * w przypadku każdej faktury jak sparametryzowany item dla każdej relacji\'"", ""Comment 16: \'We need more details to handle this request:1.Customer details in PI/SI2. Item detailsThe new relations have to be added to the relation table"", ""Comment 17: after that we can start working on that.\'"", ""Comment 18: \'Hi Ewa"", \'Comment 19:   # I don’t want to correct the PI\', \'Comment 20: cause the supplier was already paid. So no correction on {color:black}PI-RLN/2022/0487 ID58237{color} {color:black}SI-RTN/2022/0183 ID58249 was already credited with CSI-N/2022/0044 ID80287{color}{color:black}{color} !image007!{color:black}{color}{color:black}{color} {color:black}{color} # {color:black} It is on category calves.{color}  {color:black}{color} {color:black}{color} {color:black}Only we need to be able to create a booking on one side on all categories. Registration sales as well as purchases.{color} {color:black}If we want to correct a posting.{color} |{color:black} {color} |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Christinede{color} |{color:#000001} {color} |{color:#000001} Jong{color} |  {color:#000001}MedewerkerContractadministratie{color} | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.de-heus.nl/]>{color} | |  *{color:#006FB7} *DEHEUSVOEDERSB.V.*{color}* | | | |{color:#000001} Postbus396 6710BJEde \\\\u200b{color} | |{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} | | |{color:#000001} T:0318675567{color} |  {color:#000001}KvK14626985{color}   _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | | !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | | !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} | | !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} | |{color:black}{color} !image006.jpg|thumbnail!{color:black}{color} |      *Van:* Ewa Mucha (Jira) <jira@kotrak.com>   *Verzonden:* donderdag 29 december 2022 14:13  *Aan:* Jong\', ""Comment 21: Christine de <CJong@deheus.com>  *Onderwerp:* DGS-8158 Registered sale booked on one side   |  *{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 22: ""We should have the possibility to link a new invoice to the original source document whenever an invoice has been credited. Can we create a functionality like this?I don\\\'t feel like changing the relationship table is the best solution for this. Because this will imply that we need all one-sided documents to be added to the round overviews as well.""\', ""Comment 23: \'{color:black}Hello,{color} {color:black}{color} {color:black}Short summary of the Intense ticket:{color} {color:black}A purchase invoice was posted on a wrong customer. PI-RLN/2022/0487 was posted on 101685 Schut but should be on 101662 Spijker.{color} {color:black}Because the PI (ID58237) was already posted in MILAS and also paid to the supplier"", ""Comment 24: I only wanted to correct the registered sale by making a credit of the wrong and a correct registered sale on one side. Problem was this wasn’t visible on the round.{color} {color:black}Wrong (ID58249) / Credit (ID80287){color} {color:black}{color} {color:black}From Mitch I understood that that process is modified now. Process should be making a credit of the wrong document.{color}  {color:black}Next step is creation of the good posting from the original document. In this case on the regular PI the button create sales invoice will be open again.{color} {color:black}{color} {color:black}I saw that the original Printout OnBase is missing in this CSI. This should not be the case. For audit purposes this should always be linked.{color}{color:black}{color} !image001!{color:black}{color}{color:black}{color} {color:black}{color} {color:black}{color} {color:black}Thanks for your help and support!{color} {color:black}{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Christinede{color} |{color:#000001} {color} |{color:#000001} Jong{color} |  {color:#000001}MedewerkerContractadministratie{color} | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}{color:blue}{color}!image002!{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} !image003!{color:blue}{color} <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | |{color:blue}{color} !image004!{color:blue}{color} <[https://twitter.com/de_heus_voeders]>{color:black}{color} | |{color:blue}{color} !image005!{color:blue}{color} <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | |{color:blue}{color} !image006!{color:blue}{color} <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} |   !image001-1!\'"", \'Comment 25: \\\'""I saw that the original Printout OnBase is missing in this CSI. This should not be the case. For audit purposes this should always be linked.""Do you mean that Printout OnBase link should be always copied from PI to SI (like now it is)\', \'Comment 26: and later if we Credit Sales Invoice it should be copied to Credit Sales Invoice (CSI)?Summarized\', ""Comment 27: solution will be if we enable create again SI from PI (we should check that there are SI credited by CSI) and then it should be possible to create again SI and chage Round number and Customer (PI -> SI). Is it right?We should applied this solution to all cases for SI -> PI and PI -> SI.Linked to theDGS-8257\'"", ""Comment 28: \'{color:black}Hi Damian,{color} {color:black}{color} {color:black}Yes this link should be also on the credit. For audit purposes"", \'Comment 29: internal as well as external\', \'Comment 30: it is good to see the total flow and linked documents.{color} {color:black}{color} {color:black}And in case the flow is modified\', \'Comment 31: so we can create a new document after crediting\', \'Comment 32: this OnBase linked document should also be on the new created document.{color} {color:black}I hope you understand what I mean.{color} {color:black}{color} {color:black}In case not\', \'Comment 33: please ask Mitch to clarify{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:* Damian Świstek (Jira) <jira@kotrak.com>   *Verzonden:* maandag 9 januari 2023 11:41  *Aan:* Jong\', ""Comment 34: Christine de <CJong@deheus.com>  *Onderwerp:* DGS-8158 Registered sale booked on one side   |  *{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 35: \'From now"", ""Comment 36: we are moving the link to onbase to all credit invoices.\'"", ""Comment 37: \'[~tomasz.zygon@kotrak.com]do sprawdzenia dokument PI58237"", \'Comment 38: z którego wygenerowane jest SI\', \'Comment 39: które zostało skorygowane przez CSINie widzę tam\', ""Comment 40: żeby dało się ponownie wystawić SI z tego PI.Powinno być to widoczne wg taskaDGS-8257\'"", \'Comment 41: ""Hi [~CJong@deheus.com],Could you check that it works properly right now and it\\\'s sufficient and we can close the task?We\\\'ve added recently possibility to generate invoice from invoice if there exist generated invoices which are credited ([https://helpdesk.kotrak.com/servicedesk/customer/portal/56/DGS-8257)]You should be able to do the scenario mentioned before:PI -> SI -> CSIFrom PI you should be able to create again SI with proper data.It should be possible from PI document use action \\\'Create Sales Invoice_(NAS)\\\'!image-2023-02-07-14-42-42-659.png!AlsoPrintout OnBase link will be copied on Credit invoices for new documents.Regards""\', ""Comment 42: \'{color:black}Good morning,{color} {color:black}{color} {color:black}Perfect this is a good approach.{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) <jira@kotrak.com>   *Verzonden:* dinsdag 7 februari 2023 13:05  *Aan:* Jong"", ""Comment 43: Christine de <CJong@deheus.com>  *Onderwerp:* DGS-8158 Registered sale booked on one side   |  *{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 44: \'{color:black}Hi Damian,{color} {color:black}{color} {color:black}I don’t know how to test this right now. I don’t have an example to credit.{color} {color:black}You can close the task. If a problem a occurs we’ll contact you.{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Christinede{color} |{color:#000001} {color} |{color:#000001} Jong{color} |  {color:#000001}MedewerkerContractadministratie{color} | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.de-heus.nl/]>{color} | |  *{color:#006FB7} *DEHEUSVOEDERSB.V.*{color}* | | | |{color:#000001} Postbus396 6710BJEde \\\\u200b{color} | |{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} | | |{color:#000001} T:0318675567{color} |  {color:#000001}KvK14626985{color}   _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | | !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | | !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} | | !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} |      *Van:* Damian Świstek (Jira) <jira@kotrak.com>   *Verzonden:* dinsdag 7 februari 2023 14:45  *Aan:* Jong"", ""Comment 45: Christine de <CJong@deheus.com>  *Onderwerp:* DGS-8158 Registered sale booked on one side   |  *{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!\']""]\nRelated Issues:\n[\'DGS-8257\']\n\n### End'}"
874,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8157\n\n### Instruction:\nBoth recipes are in DHC but don\'t arrive in DHP Meppel.\r\nRecipes look fine to me.\r\n\r\nPlease investigate.\r\n\r\nKind regards,\r\nRob.\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'kolejka była na dhcservice !screenshot-1! 119132\\\\t119132.NL140282\\\\t140282.NL140103\\\\t140103.NL140237\\\\t140237.NL\'"", ""Comment 3: \'Please check DHCService must have processed the messages. A service restart was required.\'"", ""Comment 4: \'Hi Piotr"", \'Comment 5: it worked\', \'Comment 6: the recipes arrived in DHP Meppel.Thanks for the support\', ""Comment 7: the ticket can be closed.\']""]\nRelated Issues:\n[]\n\n### End'}"
875,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8156\n\n### Instruction:\nGoodmorning,\r\n\r\nI think that we have got a problem between DHC & DHP. Orders are not available in DHP. Ordrnumber 427 and 428.\r\n\r\nPlease, could you hav e look at it?\r\n\r\nKind regards\r\n\r\nGerard Geerts\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'!image-2022-12-23-11-26-18-959.png!\'"", ""Comment 3: \'select top 100 * from OrderExportInfoes order by SendDate desc\'"", \'Comment 4: \\\'dla 426/12 :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 UPDATE statement conflicted with the FOREIGN KEY constraint ""FK_dbo.Orders_dbo.Addresses_MainBusinessPartnerAddressId"". The conflict occurred in database ""Evolution_DHCountry""\', \'Comment 5: table ""dbo.Addresses""\', ""Comment 6: column \\\\\'Id\\\\\'.The statement has been terminated.\'"", \'Comment 7: ""select * from OrderExportInfoes where EntityId in (\\\'E70EDE86-7451-4B39-9F5C-814CC66839B1\\\',\\\'4CCEB130-0886-4D7A-8F85-3818E85E4204\\\') – nie ma ich w export inofeoes""\', ""Comment 8: \'!image-2022-12-23-11-58-49-329.png!\'"", ""Comment 9: \'dhc service veghel2022-12-22 22:54:03,344 [6] FATAL Evolution.DHCService.Client.SynchronizationService [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\156434433\\\\\\\\DHAPPSV3-DHCSC25-JOB1\\\\\\\\Evolution.DHCService.Client\\\\\\\\Evolution.DHCService.Client\\\\\\\\SynchronizationService.cs:51] - System.AggregateException: One or more errors occurred. ---> System.Data.SqlClient.SqlException: 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 10: error: 40 - Could not open a connection to SQL Server) ---> System.ComponentModel.Win32Exception: The I/O operation has been aborted because of either a thread exit or an application request --- End of inner exception stack trace --- at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity\', \'Comment 11: SqlConnectionString connectionOptions\', \'Comment 12: SqlCredential credential\', \'Comment 13: Object providerInfo\', \'Comment 14: String newPassword\', \'Comment 15: SecureString newSecurePassword\', \'Comment 16: Boolean redirectedUserInstance\', \'Comment 17: SqlConnectionString userConnectionOptions\', \'Comment 18: SessionData reconnectSessionData\', \'Comment 19: DbConnectionPool pool\', \'Comment 20: String accessToken\', \'Comment 21: Boolean applyTransientFaultHandling\', \'Comment 22: SqlAuthenticationProviderManager sqlAuthProviderManager) at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options\', \'Comment 23: DbConnectionPoolKey poolKey\', \'Comment 24: Object poolGroupProviderInfo\', \'Comment 25: DbConnectionPool pool\', \'Comment 26: DbConnection owningConnection\', \'Comment 27: DbConnectionOptions userOptions) at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnectionPool pool\', \'Comment 28: DbConnection owningObject\', \'Comment 29: DbConnectionOptions options\', \'Comment 30: DbConnectionPoolKey poolKey\', \'Comment 31: DbConnectionOptions userOptions) at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject\', \'Comment 32: DbConnectionOptions userOptions\', \'Comment 33: DbConnectionInternal oldConnection) at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject\', \'Comment 34: DbConnectionOptions userOptions\', \'Comment 35: DbConnectionInternal oldConnection) at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject\', \'Comment 36: UInt32 waitForMultipleObjectsTimeout\', \'Comment 37: Boolean allowCreate\', \'Comment 38: Boolean onlyOneCheckConnection\', \'Comment 39: DbConnectionOptions userOptions\', \'Comment 40: DbConnectionInternal& connection) at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject\', \'Comment 41: TaskCompletionSource`1 retry\', \'Comment 42: DbConnectionOptions userOptions\', \'Comment 43: DbConnectionInternal& connection) at System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection\', \'Comment 44: TaskCompletionSource`1 retry\', \'Comment 45: DbConnectionOptions userOptions\', \'Comment 46: DbConnectionInternal oldConnection\', \'Comment 47: DbConnectionInternal& connection) at System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection\', \'Comment 48: DbConnectionFactory connectionFactory\', \'Comment 49: TaskCompletionSource`1 retry\', \'Comment 50: DbConnectionOptions userOptions) at System.Data.ProviderBase.DbConnectionClosed.TryOpenConnection(DbConnection outerConnection\', \'Comment 51: DbConnectionFactory connectionFactory\', \'Comment 52: TaskCompletionSource`1 retry\', ""Comment 53: DbConnectionOptions userOptions) at System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource`1 retry) at System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry) at System.Data.SqlClient.SqlConnection.Open()\'"", ""Comment 54: \'Przy probie restartu :!image-2022-12-23-12-18-46-851.png!\'"", ""Comment 55: \'Failed to stop service. System.AggregateException: One or more errors occurred. ---> System.Data.SqlClient.SqlException: 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 56: error: 40 - Could not open a connection to SQL Server) ---> System.ComponentModel.Win32Exception: The I/O operation has been aborted because of either a thread exit or an application request --- End of inner exception stack trace --- at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity\', \'Comment 57: SqlConnectionString connectionOptions\', ""Comment 58: SqlCredential credential\'"", ""Comment 59: \'ping ok !image-2022-12-23-12-26-20-604.png!\'"", ""Comment 60: \'!image-2022-12-23-12-27-11-746.png!\'"", ""Comment 61: \'Hello,Please check should be ok now "", \'Comment 62: could you tell me if there was any works or network issues about 22:54 yestserday.This service SQLBrowser on DB plant server was set as disbaled:!image-2022-12-23-12-55-31-053.png!So other application was not able to communicate with plant database.For now I set it as manual\', \'Comment 63: ( startup type)\', ""Comment 64: but verify if that is ok( and change it to automatic f.e.)\'"", ""Comment 65: \'Hello Agnieska,So far as i know"", ""Comment 66: yesterdagevening we got our patch window. I will asked our Servicedesk if there is any relation to this.\'"", ""Comment 67: \'Could you verify if orders are ok in dhp?\'"", \'Comment 68: ""Hello Agnieszka,yes\', \'Comment 69: orders are received in DHP.I made a request to our servicedesk to check if there were issues on the DB09.But didn\\\'t  recieve a response for sofar.For this you may close this ticket and thanks for support on it.Kind regards,Gerard ""]\']\nRelated Issues:\n[]\n\n### End'}"
876,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8155\n\n### Instruction:\nWe are finding it difficult to post this particular entry on Cash Register 04.\r\n\r\nWe can not read the error since it is not in English.\r\n\r\nplease help .\r\n\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!!image-1!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 3: ""HelloI don\\\'t have a license to log in to the ERP system\', \'Comment 4: could someone log out?""\', \'Comment 5: ""entry is posted.The problem is that the register account changed but it shouldn\\\'t. The new account is EUROACCO-AS124130-03\', \'Comment 6: the old account is E99999999-AS124130-08,generally when we create new accounts we also should create new bank  register.""\', ""Comment 7: \'Thank you"", ""Comment 8: kindly close ticket\']""]\nRelated Issues:\n[]\n\n### End'}"
877,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8154\n\n### Instruction:\nIFi BP_TYPE = CUSTOMER\r\nAND\r\nBP_CATEGORY = FARMER \r\n""Technical Results""  = 1\r\nupdate must be done on ""Technical Results"" field in Customer Card\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: \'661 Customers/Farmers have been updated\']""]\nRelated Issues:\n[]\n\n### End'}"
878,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8153\n\n### Instruction:\nHi, we\'ve a lots of awd in Active status in gui, but it should be Realized (PZ generated to awd).\r\nThe same status in dhc. Any idea why? It must be corrected....\r\n\r\nRafał Boniecki\r\n\n\n### Response:\n[\'Comment 1: [""Są nowe w logu:2022-12-21 12:35:15,845 [73] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GeneratePurchaseOrderReceipt [(null)] - Extension for document started - PZ-457/12/22/D [Firma:246785 - TYP:1489/NUMER:12600421/LP:0] Evolution.ErpIntegrator.Extensions.MYShipmentNoticeUpdate.MYShipmentNoticeUpdate 2022-12-21 12:35:15,880 [73] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Interfaces.ExtensionsHelper [(null)] - Shipment Notification processing started for PZ-457/12/22/D 2022-12-21 12:35:15,880 [73] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Interfaces.ExtensionsHelper [(null)] - EXECUTE [Kotrak].[ExecuteShipmentNotificationDHC3] \\\'XL Integrator 1.0\\\',12600421,1489,2608734 2022-12-21 12:35:15,927 [73] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Interfaces.ExtensionsHelper [(null)] - Shipment Notification processing finished for PZ-457/12/22/D 2022-12-21 12:35:15,927 [73] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GeneratePurchaseOrderReceipt [(null)] - Extension for document completed - PZ-457/12/22/D [Firma:246785 - TYP:1489/NUMER:12600421/LP:0] Evolution.ErpIntegrator.Extensions.MYShipmentNoticeUpdate.MYShipmentNoticeUpdate 2022-12-21 12:35:15,927 [73] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GeneratePurchaseOrderReceipt [(null)] - Extension for document started - PZ-457/12/22/D [Firma:246785 - TYP:1489/NUMER:12600421/LP:0] Evolution.ErpIntegrator.Extensions.PLAdvanceLogger.PLAdvanceLogerExtension 2022-12-21 12:35:15,927 [73] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GeneratePurchaseOrderReceipt [(null)] - Extension for document completed - PZ-457/12/22/D [Firma:246785 - TYP:1489/NUMER:12600421/LP:0] Evolution.ErpIntegrator.Extensions.PLAdvanceLogger.PLAdvanceLogerExtension 2022-12-21 12:35:16,005 [73] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2021.Transactions.XLTransaction [(null)] - XL transaction commited\', \'Comment 2: token ID - d:eJj^@U]1GGL<Q.T2klg=5---0EJ]-- 2022-12-21 12:35:16,005 [73] DEBUG Evolution.ErpIntegrator.DHC.DHC30.Database.DhcTransaction [(null)] - DHC transaction commit started 2022-12-21 12:35:16,005 [73] DEBUG Evolution.ErpIntegrator.DHC.DHC30.Database.DhcTransaction [(null)] - DHC transaction commit finishedJak puściłem ten sam ponownie przeszło: EXECUTE [Kotrak].[ExecuteShipmentNotificationDHC3] \\\'XL Integrator 1.0\\\',12600421,1489,2608734!image-2022-12-23-08-42-37-008.png!!image-2022-12-23-08-42-37-008!""\', ""Comment 3: \'aktualna lista: |status|foreignnumber|DocumentStatus|TrN_GIDNumer|TrN_GIDTyp|id||80|AWD-89219/11/22|5|12579497|1490|2602814||80|AWD-90810/11/22|5|12580291|1490|2604418||80|AWD-93228/12/22|5|12596857|1490|2606848||80|AWD-93230/12/22|5|12595453|1490|2606850|\'"", ""Comment 4: \'|status|foreignnumber|DocumentStatus|TrN_GIDNumer|TrN_GIDTyp|id||80|AWD-95153/12/22|5|12660329|1490|2608794||80|AWD-97112/12/22|5|12655579|1490|2610778|\'"", ""Comment 5: \'[~piotr.gaczorek@kotrak.com]analiza przyczyn zajmie 8h. Potrzebujemy budżet na realizację.\'"", ""Comment 6: \'Hello"", ""Comment 7: the analysis is problematic due to the occurrence of a problem for individual documents.We need 8 hours for the analysis.Please accept costs.Regards.\'"", ""Comment 8: \'Akceptuję koszt analizy. Co w przypadku błędu aplikacji?\'"", ""Comment 9: \'mamy akceptację\'"", ""Comment 10: \'Hej"", ""Comment 11: nie były poprawnie puszczone skrypty w erpintegratorze. Podegraliśmy skrypt i powinno to pomóc. \'"", ""Comment 12: \'[~slawomir.naczynski@kotrak.com] to wina klienta? Jak PL sami robią aktualizacje.\'"", ""Comment 13: \'Hello"", \'Comment 14: after analyzing the developers it turned out that the problem was an incorrect update of Erpintegrator.Looks like there were problems with the update?Corrective action has been taken\', ""Comment 15: the problem should not occur now.\'"", ""Comment 16: \'ok"", ""Comment 17: thanks\']""]\nRelated Issues:\n[\'DGS-8032\']\n\n### End'}"
879,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8152\n\n### Instruction:\nHello,\r\n\r\nIt seems that payment method in NAS is automatically set for settlement.\r\nCan this be changed to PB-AA when posting is an regular purchase?\r\nWe always pay these invoices in NAS. No settlement.\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Could you please provide the ID of the invoice?\'"", ""Comment 3: \'Dodane do listy z podsumowaniem wysłanej do klienta.\'"", ""Comment 4: \'Hi"", ""Comment 5: it is already solved. Please remark this as done\']""]\nRelated Issues:\n[]\n\n### End'}"
880,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8151\n\n### Instruction:\nHello\r\n\r\nWe have this VT-2574/22 on Toledo plant, and when we try to RELEASE FOR INTAKE, an error message is being displayed.\r\nThis is not the first case in Toledo neither in 8.3 version. We have similar cases in Apucarana and Guararapes.\r\nIn the last time this happened, we deleted the current VT and created new one, however we need to know what is happening.\r\nCould you please fix this one and verify it?\r\nThe truck are waiting and there are some documents already printed and linked to internal process to the supplier. We cannot cancel this VT to create a new one.\r\n\r\nThank you very much\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,\\\\r\\\\rWe are investigating your issue. We will inform you about the solution as soon as possible.\\\\r\\\\rRegards\\\\r\\\\r\'"", \'Comment 3: \\\'{code:java}2022-12-22 08:28:46 (89a3ca3e-fe20-43ee-9386-53a410023c51/Plant.VC.BusinessLogic/BR-4-SV-VM0204/23384/228) [Error] Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware - Error during request{  ""scheme"": ""http""\', \'Comment 4:  ""host"": {    ""Value"": ""br-4-sv-vm0204:82""\', \'Comment 5:    ""HasValue"": true\', \'Comment 6:    ""Host"": ""br-4-sv-vm0204""\', \'Comment 7:    ""Port"": 82  }\', \'Comment 8:  ""path"": ""/api/VehicleTicket/releaseIntake""\', \'Comment 9:  ""queryString"": []\', \'Comment 10:  ""requestBody"": ""{\\\\\\\\""id\\\\\\\\"":\\\\\\\\""e70500a8-6cde-404c-a55a-3be11f450b5a\\\\\\\\"",\\\\\\\\""date\\\\\\\\"":\\\\\\\\""2022-12-22T11:28:38.746Z\\\\\\\\""}""}.System.InvalidOperationException: Nullable object must have a value.   at Plant.VC.BusinessLogic.Domain.VehicleTickets.Factories.VehicleTicketDomainEventFactory.CreateVehicleTicketReleasedForIntakeEvent(VehicleTicket vehicleTicket) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\67ba263564c33499\\\\\\\\Plant.VC.BusinessLogic\\\\\\\\Plant.VC.BusinessLogic.Domain\\\\\\\\VehicleTickets\\\\\\\\Factories\\\\\\\\VehicleTicketDomainEventFactory.cs:line 540   at Plant.VC.BusinessLogic.Domain.VehicleTickets.VehicleTicket.ReleaseForIntake(DateTime date) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\67ba263564c33499\\\\\\\\Plant.VC.BusinessLogic\\\\\\\\Plant.VC.BusinessLogic.Domain\\\\\\\\VehicleTickets\\\\\\\\VehicleTicket.cs:line 527   at Plant.VC.BusinessLogic.Application.VehicleTickets.Services.VehicleTicketService.ReleaseVehicleTicketIntake(AggregateId vehicleTicketId\', \'Comment 11: DateTime date) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\67ba263564c33499\\\\\\\\Plant.VC.BusinessLogic\\\\\\\\Plant.VC.BusinessLogic.Application\\\\\\\\VehicleTickets\\\\\\\\Services\\\\\\\\VehicleTicketService.cs:line 197   at Plant.VC.BusinessLogic.Application.VehicleTickets.CommandHandlers.ReleaseVehicleTicketIntakeCommandHandler.Handle(ReleaseVehicleTicketIntakeCommand command) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\67ba263564c33499\\\\\\\\Plant.VC.BusinessLogic\\\\\\\\Plant.VC.BusinessLogic.Application\\\\\\\\VehicleTickets\\\\\\\\CommandHandlers\\\\\\\\ReleaseVehicleTicketIntakeCommandHandler.cs:line 24   at Kotrak.Common.Infrastructure.Commands.CommandEnvironment.Run[TCommand](TCommand command)   at Kotrak.Common.Infrastructure.Commands.Decorators.IntercontextEventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command)   at Kotrak.Common.Infrastructure.Commands.Decorators.EventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command)   at Kotrak.Common.Infrastructure.Commands.Decorators.ValidationCommandEnvironmentDecorator.Run[TCommand](TCommand command)   at Castle.DynamicProxy.AbstractInvocation.Proceed()   at Kotrak.Common.Infrastructure.Interceptors.LoggingInterceptor`1.Intercept(IInvocation invocation)   at Castle.DynamicProxy.AbstractInvocation.Proceed()   at Kotrak.Common.Infrastructure.Commands.Decorators.HistoryGateDecorator.Dispatch[TCommand](TCommand command)   at Plant.VC.BusinessLogic.Infrastructure.Api.Controllers.VehicleTicketController.ReleaseIntake(ReleaseVehicleTicketIntakeViewModel viewModel) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\67ba263564c33499\\\\\\\\Plant.VC.BusinessLogic\\\\\\\\Plant.VC.BusinessLogic.Infrastructure.Api\\\\\\\\Controllers\\\\\\\\VehicleTicketController.cs:line 384   at lambda_method243521(Closure \', \'Comment 12: Object \', \'Comment 13: Object[] )   at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor.SyncActionResultExecutor.Execute(IActionResultTypeMapper mapper\', \'Comment 14: ObjectMethodExecutor executor\', \'Comment 15: Object controller\', \'Comment 16: Object[] arguments)   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeActionMethodAsync()   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next\', \'Comment 17: Scope& scope\', \'Comment 18: Object& state\', \'Comment 19: 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 20: Scope& scope\', \'Comment 21: Object& state\', \'Comment 22: 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 23: Task lastTask\', \'Comment 24: State next\', \'Comment 25: Scope scope\', \'Comment 26: Object state\', \'Comment 27: Boolean isCompleted)   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker\', \'Comment 28: Task task\', \'Comment 29: IDisposable scope)   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker\', \'Comment 30: Task task\', \'Comment 31: IDisposable scope)   at Microsoft.AspNetCore.Routing.EndpointMiddleware.<Invoke>g__AwaitRequestTask|6_0(Endpoint endpoint\', \'Comment 32: Task requestTask\', \'Comment 33: ILogger logger)   at Swashbuckle.AspNetCore.SwaggerUI.SwaggerUIMiddleware.Invoke(HttpContext httpContext)   at Swashbuckle.AspNetCore.Swagger.SwaggerMiddleware.Invoke(HttpContext httpContext\', ""Comment 34: ISwaggerProvider swaggerProvider)   at Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware.Invoke(HttpContext httpContext){code}\'"", ""Comment 35: \'ArrivalDate should be added to this VT - please specify what it should be. I will add it.\'"", \'Comment 36: ""Hi PiotrCan be the same as Arrival Weighing Date.Do you know why system didn\\\'t stored the ArrivalDate?Thank you""\', ""Comment 37: \'please check it first"", ""Comment 38: thanks.I added the date.\'"", ""Comment 39: \'Checked: It worked! Thank you\'"", ""Comment 40: \'[[DHP 3.0] VT procesowanie System.InvalidOperationException: Nullable object must have a value.|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%20VT%20procesowanie%20System.InvalidOperationException%20Nullable%20object&section-id=\\\\\\\\{05DF1439-683C-45FE-8260-61E2EC66DC91}&page-id=\\\\\\\\{AA5B5141-139E-4A0C-A66A-37DAE9560CF5}&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%20VT%20procesowanie%20System.InvalidOperationException%3A%20Nullable%20object%7CAA5B5141-139E-4A0C-A66A-37DAE9560CF5%2F%29])\'"", ""Comment 41: \'In this task we have focused on clearingandunblocking the process.If there are more we will create RCA - this one should be treated as an incident.\'"", ""Comment 42: \'Deal!You can close this taskThank you very much\']""]\nRelated Issues:\n[]\n\n### End'}"
881,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8150\n\n### Instruction:\nWarehouse order WO(PD)-983/12 for VT-1365/12/22 cannot be closed. Status of VT and WO seems to be ok. User selected stock from warehouse. Issue seems to be that user dismissed the task after selecting a pallet. However, user wishes to complete the dispatch, so that documents can be printed (Bulk is already registered on VT.\r\n\r\nPlease support us to complete this dispatch.\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: \'!image-2022-12-22-11-38-57-472.png!!image-2022-12-22-11-39-19-198.png!\'"", ""Comment 4: \'!image-2022-12-22-11-39-36-562.png!\'"", ""Comment 5: \'Hi,Please"", \'Comment 6: check with the user\', ""Comment 7: Dispatch is completed now.!image-2022-12-22-12-11-47-487.png!Regards\'"", ""Comment 8: \'{color:#000000}Thank you. Indeed WO and VT are now completed/closed.{color}   {color:#000000}This task can be closed.{color}   {color:#000000}{color}     {color:#000000}       {color}{color:black}{color} {color:#000000} {color}{color:black}Best regards | Met vriendelijke groeten,{color}{color:#000000}{color}{color:black}  Bob Kennedy{color} {color:#000000}{color}{color:black}Informatie analist{color}{color:#000000} {color}{color:black}{color}{color:#000000} {color}{color:#000000} {color} |{color:#000000}{color} {color:#000000}{color}De Heus Voeders{color:#000000} <[http://www.de-heus.nl/]>{color}{color:black}{color}{color:#000000} {color}{color:#000000} {color}|{color:#000000}{color}{color:#006FB7} * De Heus Voeders B.V.*{color}{color:#000000}{color}{color:#006FB7}{color} {color:#000000}{color}{color:#006FB7} Postbus 396 6710 BJ Ede{color}{color:#000000}{color}{color:#006FB7} Rubensstraat 1756717 VE Ede  *M* 06 - 53 224 931 KvK 14626985{color}{color:#000000}{color}{color:black} {color}{color:#000000}{color}{color:#006FB7} _ Op dit e-mailbericht en eventuele bijlage(n) is de disclaimer van toepassing_{color}{color:#000000}{color}{color:#006FB7}{color} {color:#000000}{color}{color:#006FB7} _ gepubliceerd op de website van_{color} [{color:#006FB7} _De Heus Voeders_{color}|http://www.de-heus.nl/maildisclaimer]{color:#006FB7} _._{color}{color:#000000}{color}{color:#006FB7}{color} {color:#000000} {color}{color:#000000} {color}| |{color:#000000}{color}{color:black}{color} image007.jpg@01D62AA3.AD14DDB0{color:black}{color}{color:#000000} {color}{color:#000000} {color}| |{color:#000000}{color}{color:black}{color} image004.jpg@01D62AA3.AD2CAB70{color:black}{color}{color:#000000} {color}{color:#000000} {color}| {color:#000000}{color} ---- {color:#000000} *From:* Aleksandra Przybyłek (Jira) <jira@kotrak.com>  *Sent:* Thursday"", \'Comment 9: December 22\', \'Comment 10: 2022 12:13 PM  *To:* Kennedy\', ""Comment 11: Bob <BKennedy@deheus.com>  *Subject:* DGS-8150 Warehouse order for dispatch cannot be completed{color}  |{color:#ffffff} CAUTION: This message originated from outside the organisation. Please do not click on links or open attachments unless you trust the sender and know the content is safe.{color} |\']""]\nRelated Issues:\n[]\n\n### End'}"
882,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8149\n\n### Instruction:\nHello,\r\n\r\nIn sneek we have a lot of old lot reports with status created, due to missing stock at the time. Is it possible to run a script to confirm all those? Because doing it manually takes a lot of time\r\n\r\nThanks in advance\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'W Sneeku są 62 takie. Wystarczy sam update na statusie?!image-2022-12-22-14-18-07-297.png!\'"", ""Comment 3: \'!image-2022-12-23-07-53-53-692.png!!image-2022-12-23-07-54-03-419.png!\'"", ""Comment 4: \'Ten dało się confirm!image-2022-12-23-12-45-20-530.png!!image-2022-12-23-12-45-55-322.png!!image-2022-12-23-12-45-55-322!\'"", ""Comment 5: \'Hi Thomas,I have analised your case and also consulted with Dev Team. The possible script would confirm only those Created PLRs which have source documents closed and stock is correct.Please"", ""Comment 6: let me know if you need any further assistance.Regards\'"", ""Comment 7: \'Thanks"", ""Comment 8: ticket can be closed\']""]\nRelated Issues:\n[]\n\n### End'}"
883,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8148\n\n### Instruction:\nIn round 003651/0002/0001 there are a lot of bookings on RAAP, most (if not all) of them are coming from the AS/400. In the migration files we made a mistake.\r\n\r\nAlll the quantities and net values should be positive. Also they should be moved from the category Eggs to the category Expenses. Is this possible?\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: \'Przygotować liste w Excelu wszystkich pozycji"", \'Comment 3: które zachodzą na zakładkę EGGS na rundzie003651/0002/0001 i mają item kodRAAPOznaczyć\', \'Comment 4: która pozycja jest wysłana z MILASA\', \'Comment 5: a która migrowanaNmer faktury\', \'Comment 6: item kod\', \'Comment 7: ilość\', \'Comment 8: waga\', \'Comment 9: cena netto\', \'Comment 10: wartość netto\', \'Comment 11: wartość vat\', ""Comment 12: wartość brtto\'"", ""Comment 13: \'Mitch"", ""Comment 14: could you please review the attachment?Red - lines in Eggs with some negative valuesthey must be moved to Expensive with all positive values - GreenCould you confirm?[^Analysis.csv]\'"", ""Comment 15: \'Dodane do listy z podsumowaniem wysłanej do klienta.\'"", \'Comment 16: ""Yes indeed\', \'Comment 17: (I don\\\'t see colors in your document) all negative lines with RAAP should be  positive. Also they must be presented in the category Expenses.""\', ""Comment 18: \'[~damian.swistek@kotrak.com]jakbyś miał pytania"", ""Comment 19: to daj znać\'"", ""Comment 20: \'We have changed the data on all documents from the list"", ""Comment 21: but should we also make these changes on the indicated [^Source documents.csv]for these documents?\'"", ""Comment 22: \'Can be closed.\']""]\nRelated Issues:\n[]\n\n### End'}"
884,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8147\n\n### Instruction:\nLocation Utrecht reports that VTs for intakes are not send to pcs, and dispatch messages from PCS are not arriving in DHP. Can you please check what\'s going on?\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: \\\'Z modułu VC{code:java}2022-12-22 01:02:20 (/Plant.VC.BusinessLogic/DHVD01AP183/37620/13) [Warning] RawRabbit.Channel.ChannelFactory - Connection was shutdown by Library. ReplyText ""Unexpected Exception""2022-12-22 01:07:16 (/Plant.VC.BusinessLogic/DHVD01AP183/37620/185) [Warning] RawRabbit.Channel.ChannelFactory - Connection was shutdown by Library. ReplyText ""Unexpected Exception""2022-12-22 05:01:39 (/Plant.VC.BusinessLogic/DHVD01AP183/37620/252) [Warning] RawRabbit.Channel.ChannelFactory - Connection was shutdown by Library. ReplyText ""Unexpected Exception""2022-12-22 05:38:47 (/Plant.VC.BusinessLogic/DHVD01AP183/37620/222) [Warning] RawRabbit.Channel.ChannelFactory - Connection was shutdown by Library. ReplyText ""Unexpected Exception""2022-12-22 06:15:16 (/Plant.VC.BusinessLogic/DHVD01AP183/37620/17) [Warning] RawRabbit.Channel.ChannelFactory - Connection was shutdown by Library. ReplyText ""Unexpected Exception""2022-12-22 07:00:52 (/Plant.VC.BusinessLogic/DHVD01AP183/37620/180) [Warning] RawRabbit.Channel.ChannelFactory - Connection was shutdown by Library. ReplyText ""Unexpected Exception""2022-12-22 07:01:33 (/Plant.VC.BusinessLogic/DHVD01AP183/37620/128) [Warning] RawRabbit.Channel.ChannelFactory - Connection was shutdown by Library. ReplyText ""Unexpected Exception""2022-12-22 07:02:07 (/Plant.VC.BusinessLogic/DHVD01AP183/37620/248) [Warning] RawRabbit.Channel.ChannelFactory - Connection was shutdown by Library. ReplyText ""Unexpected Exception""2022-12-22 07:03:20 (/Plant.VC.BusinessLogic/DHVD01AP183/37620/145) [Warning] RawRabbit.Channel.ChannelFactory - Connection was shutdown by Library. ReplyText ""Unexpected Exception""2022-12-22 08:32:56 (/Plant.VC.BusinessLogic/DHVD01AP183/37620/227) [Warning] RawRabbit.Channel.ChannelFactory - Connection was shutdown by Library. ReplyText ""Unexpected Exception""2022-12-22 08:33:39 (/Plant.VC.BusinessLogic/DHVD01AP183/37620/181) [Warning] RawRabbit.Channel.ChannelFactory - Connection was shutdown by Library. ReplyText ""Unexpected Exception""{code}\\\'\', ""Comment 3: \'Thomas,Please check now. It should work now.Has the server been restarted? Or was there any lack of electricity? Rabbit was not running and we also restared application pools.Reagrds\'"", \'Comment 4: ""I don\\\'t think so. Patch evening is tonight. Can we check and restart Rabbitmq ourselves?""\', ""Comment 5: \'Yes"", \'Comment 6: it is a Windows service. But after starting Rabbitmq\', \'Comment 7: all application pools need to be restarted. In my opinion\', ""Comment 8: it is better to do it on our side.\'"", ""Comment 9: \'Oke clear"", ""Comment 10: thanks for your help\'"", ""Comment 11: \'No problem\']""]\nRelated Issues:\n[]\n\n### End'}"
885,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8146\n\n### Instruction:\nWe got the task from Richard to put all invoices on payment method ""NB"", due to some changes in Milas. Sadly we were too quick and we archived one that was on ""Settlement"". Can you put PI-RLB/2022/1249 (ID79390) back to entry? Than we can modify this\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Document is again in first owner from intense.\']""]\nRelated Issues:\n[]\n\n### End'}"
886,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8145\n\n### Instruction:\nAs per conversation between Beata and Nosipho, see accounts that need resolution in attached screenshot.\n\n### Response:\n[""Comment 1: [\'!image!\'"", \'Comment 2: ""HelloRegarding 010-40-10-11367We discussed this on teams but I didn\\\'t get any response.As I know this was the deposit that you paid\', \'Comment 3: the vendor refunded you the deposit \', \'Comment 4: so there has to be PI correction in the system\', ""Comment 5: but there isn\'t "", \'Comment 6: so the best way to clear this amount is to create Accounting Note with 010-40-10-11367 DT\', ""Comment 7: and you should decide what should be the opposite account .Such a document could be settled with 20/HSBC/223/56Regarding 010-40-10-12039I don\'t know exactly which documents should be cleared on this account.010-40-10-11066The best/easist way is to create Accounting Note: 010-40-10-11066 DT.If you want"", \'Comment 8: I can do it first on DEV or Nightly database?""\', ""Comment 9: \'Hello,Please see more detailed document.[^Creditors Clean Up - December.docx] _(361 kB)_\'"", \'Comment 10: ""HelloRegarding accounts:010-15-10-11367010-40-10-11367The bank entry from 2020 was reposted from 010-15 to 010-40\', \'Comment 11: so the Trial balance now does not match with the documents in the clearing window. In this case\', \'Comment 12: we should change the OB as well.I could change  account in OB (2021,2022): 010-15-10-11367 to 010-40-10-11367 (on database). Nothing will changed in terms of values on the TSU PROTECTION SERV accounts\', ""Comment 13: the value will be just transferred from one account to another account of the same vendor.For me it\'s ok.Of course it could be done in the system by using option: tranfer of opening balance (2021"", \'Comment 14: 2022). The system will make Opening Balance Correction.""\', ""Comment 15: \' !screenshot-1! I will write instruction about how to fix this.\'"", ""Comment 16: \'Please see updated document.[^Creditors Clean Up - December-1.docx] _(848 kB)_\'"", \'Comment 17: ""Regarding accounts:010-15-10-11367010-40-10-11367I fixed this on Nightly database as we agreed.At the beginning I had to remove the changes made in 2020\', \'Comment 18: we agreed that the Finance doesn\\\'t allow to change anything in old periods.All changes must be done in 2022After that:I changed period to 2022 and changed date to 2022-12-31Then I made AN document like on the screenshot below and post it. !screenshot-2! Then go to the Clearing windows to clear those entries on 010-15-10-11367 account. !screenshot-3! The value was transferred from 010-15 to 010-40 without changing anything in old period so we don\\\'t have to change OB.""\', ""Comment 19: \'Regarding  010-40-10-03887 CHEMFIT FINEDocument PI-5414/19/RMP has value 196 417,24when we sum up the posted value"", \'Comment 20: we also have 196 417,24Settled value is 196 417\', \'Comment 21: 22unpaid value should be 0,02 \', \'Comment 22: we can just settled those duplicated payments and it should be ok.How to do this:* Go to the Payment Plan\', \'Comment 23: find this payments on the list* open payment by using Loop icon\', \'Comment 24: * uncheck ""Dont settle"" !screenshot-4! * Then just setlle those duplicated payments\', ""Comment 25: you can do it on Payment Plan or in Clearing window !screenshot-5! \'"", ""Comment 26: \'!image-1!\'"", ""Comment 27: \'waiting for answer about 010-40-10-03887  CHEMFIT FINE\'"", \'Comment 28: ""Hello,Finance did not get a chance to check\', \'Comment 29: they\\\'ve been busy with Year End Closure.Can we please try again next week Tuesday?""\', ""Comment 30: \'[^Creditors Clean Up - VICTORY MILLING.docx]\'"", \'Comment 31: ""HelloI\\\'m attaching the short instruction how to clear VICTORY MILLING account. [^Creditors Clean Up - VICTORY MILLING.docx] ""\', ""Comment 32: \'Hello NosiphoCould you please confirm if we can close this task?Regards\'"", ""Comment 33: \'You may close the ticket. Thank you for the help.\']""]\nRelated Issues:\n[]\n\n### End'}"
887,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8144\n\n### Instruction:\nVersion 3 receptura DT218X00S\r\nWygenerowana w DHC, nie ma jej w DHP.\r\nZ poprzednimi wersjami był ten sam problem ze nie przechodziły do DHP, coś je blokuje. \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: \'The delay is caused by the amount of messages for the DHC service you have to wait for them to process. !screenshot-1! \'"", ""Comment 3: \' !screenshot-2! \'"", ""Comment 4: \'Task to close \']""]\nRelated Issues:\n[]\n\n### End'}"
888,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8143\n\n### Instruction:\nWe have some lot reports in DHP that are not finished from PCS. In DHP we try to Finish the Lot report. When we finish the Lot report the produced quantity is set to 0. It is possible to edit the Finished Lot report and fix the produced quantity, but in our case, Lot reports are sent to DHC/Milas in status finished. So, with quantity 0. This results in issues with FP stock in Milas.\r\n\r\nPlease check / inform us how we can keep the correct quantity in the Lot report in case we put a Lot report with status In Progress to Finished.\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Please note that the issue occurs in production Dhp’s. The attached example is from Dhp test from my check of the issue.  {quote}Op 21 dec. 2022 om 18:35 heeft Adrian Kozak (Jira) <jira@kotrak.com> het volgende geschreven:  {quote}  {quote} \\\\ufeff |{color:#ffffff} CAUTION: This message originated from outside the organisation. Please do not click on links or open attachments unless you trust the sender and know the content is safe.{color} |{color:#999999}{color}{color:#999999}{color}{color:#7a869a}{color}{color:#7a869a}{color}  {quote}\'"", ""Comment 4: \'Please let me know what is the reason that the production is not finished from PCS.Is the problem with the PCS provider?\'"", ""Comment 5: \'{color:#000000}Indeed"", \'Comment 6: in some cases the message with last batch = true indication cannot be processed.{color} {color:#000000}PCS sends a separate message (with qty 0,001Kg) and last batch = true flag\', \'Comment 7: to indicate that production is finished{color} {color:#000000}Sometime multiple messages are send in one message. In case of of the messages e.g. does not have correct code or recipeId\', \'Comment 8: then I found that the entire message is not processed.{color}   {color:#000000}Because there is high pressure on confirming Lot reports\', \'Comment 9: plant manager tries to finish/confirm these lot reports manually.{color}   {color:#000000}{color}     {color:#000000}       {color}{color:black}{color} {color:#000000} {color}{color:black}Best regards | Met vriendelijke groeten,{color}{color:#000000}{color}{color:black}  Bob Kennedy{color} {color:#000000}{color}{color:black}Informatie analist{color}{color:#000000} {color}{color:black}{color}{color:#000000} {color}{color:#000000} {color} |{color:#000000}{color} {color:#000000}{color}De Heus Voeders{color:#000000} <[http://www.de-heus.nl/]>{color}{color:black}{color}{color:#000000} {color}{color:#000000} {color}|{color:#000000}{color}{color:#006FB7} * De Heus Voeders B.V.*{color}{color:#000000}{color}{color:#006FB7}{color} {color:#000000}{color}{color:#006FB7} Postbus 396 6710 BJ Ede{color}{color:#000000}{color}{color:#006FB7} Rubensstraat 1756717 VE Ede  *M* 06 - 53 224 931 KvK 14626985{color}{color:#000000}{color}{color:black} {color}{color:#000000}{color}{color:#006FB7} _ Op dit e-mailbericht en eventuele bijlage(n) is de disclaimer van toepassing_{color}{color:#000000}{color}{color:#006FB7}{color} {color:#000000}{color}{color:#006FB7} _ gepubliceerd op de website van_{color} [{color:#006FB7} _De Heus Voeders_{color}|http://www.de-heus.nl/maildisclaimer]{color:#006FB7} _._{color}{color:#000000}{color}{color:#006FB7}{color} {color:#000000} {color}{color:#000000} {color}| |{color:#000000}{color}{color:black}{color} image007.jpg@01D62AA3.AD14DDB0{color:black}{color}{color:#000000} {color}{color:#000000} {color}| |{color:#000000}{color}{color:black}{color} image004.jpg@01D62AA3.AD2CAB70{color:black}{color}{color:#000000} {color}{color:#000000} {color}| {color:#000000}{color} ---- {color:#000000} *From:* Piotr Gaczorek (Jira) <jira@kotrak.com>  *Sent:* Thursday\', \'Comment 10: December 22\', \'Comment 11: 2022 12:45 PM  *To:* Kennedy\', \'Comment 12: Bob <BKennedy@deheus.com>  *Subject:* DGS-8143 On closing of Lot report with status In progress in DHP\', ""Comment 13: quantity is set to 0{color}  |{color:#ffffff} CAUTION: This message originated from outside the organisation. Please do not click on links or open attachments unless you trust the sender and know the content is safe.{color} |\'"", ""Comment 14: \'W nawiązaniu do odp klienta"", \'Comment 15: czy jest możliwość kończenia produkcji z UI\', ""Comment 16: jak PCS ma problem z przesłaniem message?\\\\r\\\\rDzięki.\'"", ""Comment 17: \'Hej,Po rozmowie z [~wojciech.wojerz@kotrak.com]dowiedziałem sie że nie ma takiego procesu aby w ten sposób zakończyć produkcje. Jedynym rozwiązaniem byłoby skorzystanie z procedury api.FinishProduction\'"", ""Comment 18: \'There is no such solution available for DHP"", \'Comment 19: a change as GDC is required.If we are to make a change on the PLR\', ""Comment 20: then only from our side with the PLR list.\'"", ""Comment 21: \'All information was provided in the last comment.This ticket  has been  closed.\']""]\nRelated Issues:\n[]\n\n### End'}"
889,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8142\n\n### Instruction:\nBrak receptury DT218X00S ( w wersji bazowej oraz wersji L00 ) w DHP\r\nReceptura w DHC zaakceptowana oraz zlinkowana.\r\nReceptura potrzebna dzis do produkcji \n\n### Response:\n[""Comment 1: [\'Hello"", ""Comment 2: We kindly inform you that wecurrentlyare processing another Priority1 task.We will revert to processing your task as soon as possible.Regards\'"", ""Comment 3: \'Aby News ??\'"", ""Comment 4: \'Poprzednie P1 zostało ponad pół godziny temu zamknięte \'"", ""Comment 5: \'Both recipes are synchronised to DHP!image-2022-12-21-18-14-00-431.png!Please verify.\'"", ""Comment 6: \'Na screenie widze ze jest wersja 1 recepturyW DHH widziałem ze NL wysłało tez 2 wersje\'"", ""Comment 7: \'There is version 2 in DHP as well!image-2022-12-21-18-19-13-049.png!\'"", ""Comment 8: \'Task to close\']""]\nRelated Issues:\n[]\n\n### End'}"
890,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8141\n\n### Instruction:\nDzień dobry, \r\nproszę o pomoc w ZPM(S)-5217/12/22 brak elementów składanek VT-25515/12/22. \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 close task.\'"", ""Comment 3: \'Analiza problemu nie wykazała jego przyczyny. Prawdopodobnie błędy związane z nieprawidłową realizacją procesu.\'"", ""Comment 4: \'[~bartlomiej.brzek@kotrak.com] wklej te selecty co robiłeś podczas rozmowy.\'"", ""Comment 5: \'Będzie z tym problem... nie zdążyłem skopiować :(\'"", ""Comment 6: \'Hello,why this ticket was opened?\']""]\nRelated Issues:\n[]\n\n### End'}"
891,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8140\n\n### Instruction:\nPlease change the <payment form Intense> for :\r\n\r\n  - all Suppliers where the <Code> starts with LBXXXXX from Bank transfer into    \r\n    ABN_EUR\r\n- all Customers where the <payment form Intense> from Settlement into NB\r\n\r\nNote: ONLY IN THE MASBE sector.\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: \'Update dataaccording to the guidelineschange the <payment form Intense> for : - all Suppliers where the <Code> starts with LBXXXXX from Bank transfer intoABN_EUR - all Customers where the <payment form Intense> from Settlement into NBNote: ONLY IN THE MASBE sector.\'"", \'Comment 3: ""update customers set Cst_PaymentForm= 1178where Cst_FrmID=5 and Cst_PaymentForm=743 and Cst_IntColumn5=318 and Cst_Name like \\\'LB%\\\'update customers set Cst_PaymentForm=1029where Cst_FrmID=5 and Cst_PaymentForm= 742 and Cst_IntColumn5=317""]\']\nRelated Issues:\n[]\n\n### End'}"
892,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8139\n\n### Instruction:\nWhen a customer is set to Inactive it should not appear in any dropdown in Intense. Now this is still the case.\n\n### Response:\n[""Comment 1: [\'!image-1!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Hi Mitch"", ""Comment 4: where do you this customer in the dropdown?\'"", ""Comment 5: \'Dodano do listy z podsumowaniem wysłanej do klienta.\'"", ""Comment 6: \'[~mbovene@deheus.com]could you check this?\'"", ""Comment 7: \'I have asked Christine but still no reply. You can close this task.\'"", ""Comment 8: \'I close the task.\']""]\nRelated Issues:\n[]\n\n### End'}"
893,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8138\n\n### Instruction:\nUnable to release VT-318/12/2022/KB\r\nFor PO-660/22/KBG\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: ""{code:java}2022-12-21 14:23:47,795 [19] INFO  Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.ExternalOrderTransactions.CdnXL2019ExternalOrderTransactionRepository [(null)] - PurchaseOrderReceipt created: Firma:556290 - TYP:1489/NUMER:4033442/LP:0 POR-2666/22/KBP2022-12-21 14:23:47,811 [19] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.ExternalOrderTransactions.CdnXL2019ExternalOrderTransactionRepository [(null)] - Element creating: Code:2303020 Q:34.0999602022-12-21 14:23:47,811 [19] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.ExternalOrderTransactions.CdnXL2019ExternalOrderTransactionRepository [(null)] - No deliveries found.2022-12-21 14:23:47,811 [19] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.ExternalOrderTransactions.CdnXL2019ExternalOrderTransactionRepository [(null)] - Catalog Price from elem: 2025.0000\', \'Comment 4: exRates: 12022-12-21 14:23:47,811 [19] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.ExternalOrderTransactions.CdnXL2019ExternalOrderTransactionRepository [(null)] - Catalog Price after currency recalc: 2025.0000\', \'Comment 5: exRates: 12022-12-21 14:23:47,998 [19] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.PurchaseOrderReceipts.CdnXL2019PurchaseOrderReceiptRepository [(null)] - Error occurred - document Firma:556290 - TYP:1489/NUMER:4033442/LP:0 will be deleted2022-12-21 14:23:47,998 [19] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.ExternalOrderTransactions.CdnXL2019ExternalOrderTransactionRepository [(null)] - PurchaseOrderReceipt closing: Firma:556290 - TYP:1489/NUMER:4033442/LP:0 (-1)2022-12-21 14:23:48,045 [19] ERROR Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.PurchaseOrderReceipts.CdnXL2019PurchaseOrderReceiptRepository [(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 6: 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.PurchaseOrderReceipts.CdnXL2019PurchaseOrderReceiptRepository.CloseDocument(XLPurchaseOrderReceipt header\', \'Comment 7: DocumentStatus status) in C:\\\\\\\\TeamCity\\\\\\\\buildAgent\\\\\\\\work\\\\\\\\57a7e278b67a115c\\\\\\\\Evolution.ErpIntegrator\\\\\\\\CdnXL\\\\\\\\Evolution.ErpIntegrator.CdnXL.CdnXL2019\\\\\\\\Documents\\\\\\\\PurchaseOrderReceipts\\\\\\\\CdnXL2019PurchaseOrderReceiptRepository.cs:line 83   at Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.PurchaseOrderReceipts.CdnXL2019PurchaseOrderReceiptRepository.CreatePORWithElements(PurchaseOrderReceipt purchaseOrderReceipt\', \'Comment 8: Boolean confirmDoc) in C:\\\\\\\\TeamCity\\\\\\\\buildAgent\\\\\\\\work\\\\\\\\57a7e278b67a115c\\\\\\\\Evolution.ErpIntegrator\\\\\\\\CdnXL\\\\\\\\Evolution.ErpIntegrator.CdnXL.CdnXL2019\\\\\\\\Documents\\\\\\\\PurchaseOrderReceipts\\\\\\\\CdnXL2019PurchaseOrderReceiptRepository.cs:line 312022-12-21 14:23:48,045 [19] DEBUG Evolution.ErpIntegrator.DHC.DHC30.Database.DhcTransaction [(null)] - DHC transaction rollback staeted2022-12-21 14:23:48,045 [19] DEBUG Evolution.ErpIntegrator.DHC.DHC30.Database.DhcTransaction [(null)] - DHC transaction rollback finished2022-12-21 14:23:48,061 [19] 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 - -12022-12-21 14:23:48,061 [19] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2019.Transactions.XLTransaction [(null)] - XL transaction rollbacked\', \'Comment 9: token ID - Z<?L_YfD?aS;[\\\\\\\\\\\\\\\\jV:/_V]5----YNM--2022-12-21 14:23:48,108 [19] ERROR Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GeneratePurchaseOrderReceipt [(null)] - Error of type XLApiException has been thrown (XLDodajPozycje:17).API Name - XLDodajPozycjeAPI Result - 17Flags - 12ERRORS:|Missing quantity (failed to retrieve the item or the entire execution was forced). (DodajPozycje-17) - (2303020)Error of type Evolution.ErpIntegrator.CdnXL.CdnXL2019.XLApiException has been thrown (XLDodajPozycje:17).API Name - XLDodajPozycjeAPI Result - 17Flags - 12ERRORS:|Missing quantity (failed to retrieve the item or the entire execution was forced). (DodajPozycje-17) - (2303020)   at Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.ExternalOrderTransactions.CdnXL2019ExternalOrderTransactionRepository.AddElement(Int32 XLdocNumber\', \'Comment 10: XLExternalOrderTransactionElement element) in C:\\\\\\\\TeamCity\\\\\\\\buildAgent\\\\\\\\work\\\\\\\\57a7e278b67a115c\\\\\\\\Evolution.ErpIntegrator\\\\\\\\CdnXL\\\\\\\\Evolution.ErpIntegrator.CdnXL.CdnXL2019\\\\\\\\Documents\\\\\\\\ExternalOrderTransactions\\\\\\\\CdnXL2019ExternalOrderTransactionRepository.cs:line 332   at Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.PurchaseOrderReceipts.CdnXL2019PurchaseOrderReceiptRepository.AddElement(Int32 XLdocNumber\', \'Comment 11: XLPurchaseOrderReceiptElement porElement) in C:\\\\\\\\TeamCity\\\\\\\\buildAgent\\\\\\\\work\\\\\\\\57a7e278b67a115c\\\\\\\\Evolution.ErpIntegrator\\\\\\\\CdnXL\\\\\\\\Evolution.ErpIntegrator.CdnXL.CdnXL2019\\\\\\\\Documents\\\\\\\\PurchaseOrderReceipts\\\\\\\\CdnXL2019PurchaseOrderReceiptRepository.cs:line 75   at Evolution.ErpIntegrator.CdnXL.CdnXL2019.Documents.PurchaseOrderReceipts.CdnXL2019PurchaseOrderReceiptRepository.CreatePORWithElements(PurchaseOrderReceipt purchaseOrderReceipt\', \'Comment 12: Boolean confirmDoc) in C:\\\\\\\\TeamCity\\\\\\\\buildAgent\\\\\\\\work\\\\\\\\57a7e278b67a115c\\\\\\\\Evolution.ErpIntegrator\\\\\\\\CdnXL\\\\\\\\Evolution.ErpIntegrator.CdnXL.CdnXL2019\\\\\\\\Documents\\\\\\\\PurchaseOrderReceipts\\\\\\\\CdnXL2019PurchaseOrderReceiptRepository.cs:line 37   at Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GeneratePurchaseOrderReceipt.OnExecute(VehicleTicket vehicleTicket){code}Sprawdziłem z innym intake VT co się zrobił kierunek jest taki sam\', \'Comment 13: powiązanie do zamówienia też\', \'Comment 14: podobnie dla generowania PZ z PO.{code:java}  FROM [DHCountry_RSA_PROD].[dbo].[VehicleTicketElements] where VehicleTicketId in(select id   FROM [DHCountry_RSA_PROD].[dbo].[VehicleTickets]  where DocumentNumber like \\\'314/12/2022/KB\\\' or DocumentNumber like \\\'318/12/2022/KB\\\'){code} !screenshot-1! {code:java} FROM [DHCountry_RSA_PROD].[dbo].[Orders] where id in(\\\'628F60FE-E985-40EA-98BD-78F33AF048EC\\\',\\\'56E5BD34-A6F4-4F38-8D02-BFECA6CECE85\\\'){code} !screenshot-2! ""\', ""Comment 15: \'Morning. Any progress on this issue? Is there any thing you want me to check or do on our side?\'"", ""Comment 16: \'You may close the ticket. It seems like the deviation percentage is no longer working on DHC.\'"", \'Comment 17: ""But it doesn\\\'t work at all or for this order?I see that the quantity on the order has changed.""]\']\nRelated Issues:\n[]\n\n### End'}"
894,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8137\n\n### Instruction:\nHi\r\n\r\nFrom Iwona\r\n\r\nRafał Boniecki\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 3: ""!image-2022-12-22-07-30-33-048.png!will take 6 rbg!image-2022-12-22-07-30-54-079.png!will take 3 rbgPricing doesn\\\'t contains tests. (Tests will be running by de heus)Please accept costs.""\', ""Comment 4: \'!image-1!\'"", ""Comment 5: \'NA bazie testowej z poziomu ZO została dodana nowa funkcja:!image-2022-12-23-14-27-37-787.png!Należy wybrać pracownika i nacisnąć piorun:!image-2022-12-23-14-28-29-768.png!Proszę o testy i informację zwrotną czy można przenieść na bazę produkcyjną.Druga funkcja w trakcie realizacji\'"", ""Comment 6: \'hi"", ""Comment 7: on what database and terminal server did you implement new function?\'"", \'Comment 8: ""as usual onSQL05-20\\\\\\\\cdnxl_deheusbut as a can see you overwrite this database 28th of december. On wchich database i can maje changes (you don\\\'t have plans to overwrite it)?""\', \'Comment 9: ""You can work on the same database. We don\\\'t plan any refresh DB in the near future.""\', ""Comment 10: \'Is on test database again\'"", ""Comment 11: \'Iwona tego nie widzi"", ""Comment 12: ma dzwonić do Ciebie !image-2!\'"", ""Comment 13: \'trzeba wejść na dokument ZO tak jak pisałam wcześniej. Dałam jej znać!image-2023-01-03-13-45-23-121.png!\'"", ""Comment 14: \'[XL/946895|https://www.asysta.comarch.pl/ObslugaZgloszen/Zgloszenia/FormularzZgloszenia.aspx?ZglID=tSYog8F%2b6yR2R4ogcziIHw%3d%3d&rfId=20]\'"", ""Comment 15: \'!image-3!\'"", ""Comment 16: \'+ nowy filtr po osobie odpowiedzialnej\'"", ""Comment 17: \'!image-2023-01-10-14-02-17-065.png!\'"", ""Comment 18: \'Dzień dobry,Hello # Mechanizm do zmiany osoby odpowiedzialnej został przeniesiony na bazę produkcyjnąThe mechanism for changing the responsible person has been transferred to the production base2. Został dodany nowy filtr do analizy osoby odpowiedzialnej na bazie testowej i produkcyjnej. Proszę o weryfikację.There is new filter on production and test database. Please verify.!image-2023-01-11-08-22-50-166.png!3. Na bazie testowej został dodany mechanizm do zmiany MPK. Dostępny spod księgi inwentarzowej -> wydruk -> zmiana MPK. Proszę o testyA mechanism for changing cost centers has been added on a test database. Available from księgi inwentarzowej -> wydruk -> zmiana MPK. Please test!image-2023-01-11-08-21-52-111.png!\'"", ""Comment 19: \'!image-4!\'"", ""Comment 20: \'All solutions has been transffered into production database. Can we close this ticket?\'"", ""Comment 21: \'Yes. Thanks a lot.\']""]\nRelated Issues:\n[]\n\n### End'}"
895,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8136\n\n### Instruction:\nWe created a SI from PI RLB/2022/1241, but the system automatically makes a registered sale when we use B005059 De Heus Voeders as reference. We need a regular sale, so can you Put SI-RTB/2022/0001 (ID 79282) back to entry?\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: \'Done"", ""Comment 3: document is in entry staus. !image-2022-12-21-14-10-32-193.png!\'"", ""Comment 4: \'I close it.\']""]\nRelated Issues:\n[]\n\n### End'}"
896,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8135\n\n### Instruction:\nBlocking Customer/ Round Number fields in Feed Sales All Sectors\n\n### Response:\n[""Comment 1: [\'Planned after new UAT is ready.\'"", ""Comment 2: \'Done in UAT and Production database for all sectors.\']""]\nRelated Issues:\n[]\n\n### End'}"
897,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8134\n\n### Instruction:\nHi,\r\n\r\nWe are missing shipping notice L000069384 in DHP. This SN is in DHC though. Can you please check why it isn\'t arriving in DHP?\r\n\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 2: ""select * from ShippingNotices where ForeignNumber like \\\'%L000069384\\\'select * from ShippingNoticeElements where ShippingNoticeId=\\\'8118F5B6-C1B5-4619-9302-C903F99BF12B\\\'""\', \'Comment 3: \\\'An error occurred while saving the entity changes. See the inner exception for details. -> The INSERT statement conflicted with the FOREIGN KEY constraint ""FK_ShippingNoticeElementOrders_OrderElements_OrderId_OrderNo"". The conflict occurred in database ""DHPlantVCBusinessLogicMain""\', \'Comment 4: table ""dbo.OrderElements"".The statement has been terminated.\\\'\', ""Comment 5: \'select * from OrderIdentityMappings mleft join [DHPlantVCBusinessLogicMain].[dbo].[Orders] o on o.id=m.PlantIdwhere LongId in (154137,154310,154228,153547,154760,154310,154848,154137,154848,153509,154361,154310,154137,154310,154310,154848,154190,154137,154228,154848,154310,154228,154190,154310,154361,153547,154190,154671,154848,154753,154310,154137,154848,154310,154228,154089,153974,153509,153974)\'"", ""Comment 6: \'do vt nie wpadlo zamowieniaSO000031691\'"", ""Comment 7: \'!image-2022-12-21-10-50-53-874.png!\'"", \'Comment 8: \\\'An error occurred while saving the entity changes. See the inner exception for details. -> The INSERT statement conflicted with the FOREIGN KEY constraint ""FK_Orders_ContactDatas_MainBusinessPartnerId_MainBusinessPartnerContactDataId"". The conflict occurred in database ""DHPlantVCBusinessLogicMain""\', \'Comment 9: table ""dbo.ContactDatas"".The statement has been terminated.\\\'\', ""Comment 10: \'baza dhc service adres uzyty na orderze jest [rzypisany do inego kontrahenta!image-2022-12-21-11-48-39-332.png!\'"", ""Comment 11: \'The reason for the problem is an unsynchronised order SO000031691.There is a discrepancy on this order as you can see on the bass projections the main address of the order belongs to the BP with code 101699 and the main BP on the order is the contractor with code 999902"", ""Comment 12: in this situation I would like to ask you to change - resend the order or re-send the addresses so that they match and feedback.!image-2022-12-21-13-08-13-301.png!\'"", ""Comment 13: \'Hi Aleksandra"", \'Comment 14: we have done some research. Together with @Tdankers and @Bkennedy\', ""Comment 15: but we have sent the correct values. The delivery address of the food is:101699NEDERLANDS PLUIMVEEMUSEUMHessenweg 2 A3771 RB BarneveldCan you change the Business Partner for 101699 to these values?\'"", ""Comment 16: \'Can it be that it goes wrong because of two adresses in DHC and DHP for code 101699\'"", ""Comment 17: \'So you wish to change Main Bussiness Partner to 101699 from 999902?!image-2022-12-21-15-02-10-492.png!\'"", \'Comment 18: ""No\', \'Comment 19: I wish the Main Business Partner to remain 101699. The 999902 is not relevant. But I want the Business Partner\\\'s full address to be:Nederlands PluimveemuseumHessenweg 2 A3771 RB BarneveldThere should not be any relation to 999902. ""\', \'Comment 20: ""So the main business partner ID in this order needs to be changed to 101699.I can\\\'t do that in the ERP\', \'Comment 21: cause it is already there.""\', ""Comment 22: \'Hello,after fixing order Main Bussiness Partner"", ""Comment 23: and resending order I resend also a ASN please check!image-2022-12-22-13-47-58-345.png!\'"", ""Comment 24: \'Great! Thanks Aleksandra!\']""]\nRelated Issues:\n[]\n\n### End'}"
898,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8133\n\n### Instruction:\nPlease remove the additional technology RA967329\r\n\r\nAn incorrect additional technology RA967329 was created (refers to final product 967323 and derived 967323. \r\nTo send the order with correct codes we created additional technology RA967329-1. This one is ok.\r\n\r\nHowever, plant must also receive a new recipe for 967323 because a RM is missing in the plant. This new recipe not send because of the incorrect additional technology\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'!image-2022-12-21-09-21-16-470.png!!image-2022-12-21-09-21-16-470!\'"", ""Comment 4: \'Any update?\'"", ""Comment 5: \'Yes"", \'Comment 6: we are working on it\', ""Comment 7: deleteing technology requires a lot of other activities to have process correct.\'"", ""Comment 8: \'Additional Technology has been removed.The process takes some time as we need to find technology in all possible data bases and also verify if there are any PLRs related to questioned technology.Regards\'"", ""Comment 9: \'Ok"", ""Comment 10: thank you. Recipe is now send to PCS. This ticket can be closed.\'"", ""Comment 11: \'Thank you.\']""]\nRelated Issues:\n[]\n\n### End'}"
899,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8132\n\n### Instruction:\nCould you delete B004922/0064/0002 (ID 62046)? We have a new contract created for this customer (B004922/0235/0001, ID 79108), which should be round number 2. I moved all the feed to the first round of the new contract and there is no delivery that should be invoiced so round B004922/0064/0002 (ID 62046) is completely empty now. Also, is there a possibility that we could do this (following a few guidlines maybe) ourselves in the future?\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Round and feed sale to be deleted.\'"", ""Comment 3: \'Done. Round and feed sales have been removed.\'"", ""Comment 4: \'!image-2022-12-21-09-58-54-381.png!\'"", ""Comment 5: \'The Round and linked Feed Sale have been deleted.Mitch,what do you think about giving users rights to delete rounds?\'"", ""Comment 6: \'In my opinion Steffen"", \'Comment 7: Koen\', ""Comment 8: Bessel and Bert should be able to delete rounds. However it is important that the round is empty. If there are bookings on the round they should first be moved to another round before we could delete them.\'"", ""Comment 9: \'Mitch"", ""Comment 10: what happens if the round number 2 was sent to MILAS and then deleted in Intense? Will the round number in MILAS be updated with the previous round 1?\'"", ""Comment 11: \'Dodane do listy z podsumowaniem dla klienta.\'"", \'Comment 12: ""No\', \'Comment 13: unfortunately when the round is deleted in Intense it won\\\'t automatically update the round overviews in Milas.The user needs to resend the previous round (in this case round 1) again from Milas to Intense.If this is not done and Milas is trying to send the feed sales invoices to Intense it will generate an error report in there because it cannot find the indicated round in Milas.""\', ""Comment 14: \'Runda 1 AktywnaRunda 2 Aktywna Userzy chca usnac runde numer 2 i powinni to moc zrobic"", \'Comment 15: tylko jesli nie ma na Rundzie numer 2 zadnych faktur. Po usunieciu R2 MILAS musialby dostac informacje\', \'Comment 16: ze aktualna runda to R1. Wprzeciwnym wypadku caly czas bedzie wysylac dane na R2\', ""Comment 17: ktorej nie ma.Runda 1 ZamknietaRunda 2 Aktywna- czy wtedy usuniecie powinno byc mozliwe? Moim zdaniem nie\'"", ""Comment 18: \'This is related to another task. Is it solved right now @Damian?\'"", \'Comment 19: ""Yes\', ""Comment 20: exactly.We\'re working on solution in this task"", \'Comment 21: then it will be automatically sending last round number of customer if someone delete round.It will be handled in this task https://helpdesk.kotrak.com/browse/DHNLC-1230and then we can close both tasks I think if it will be sufficient solution for these cases.""\', ""Comment 22: \'Can be closed.\']""]\nRelated Issues:\n[]\n\n### End'}"
900,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8131\n\n### Instruction:\nGood morning,\r\n\r\nI am unable to book out these sales orders. SO-284/12/2022 and SO-285/12/2022 and SO-286/12/2022\r\nThis is strange because I could just make the orders based on the stock indicated in the allocation list. (so the stock is there)\r\n\r\nWhen I want to create the SORs I get the following message (for all three SOs, see image.\r\n\r\nPlease, could you help me?\r\n\r\nKind regards,\r\n\r\nGerard Geerts\n\n### Response:\n[""Comment 1: [\'!Premix_issue!\'"", ""Comment 2: \'Hello,\\\\r\\\\rWe are investigating your issue. We will inform you about the solution as soon as possible.\\\\r\\\\rRegards\\\\r\\\\r\'"", ""Comment 3: \'Hello,Kindly approve lowering priority of this task to P2 as P1 issues are only those with a critical or a blocking impact on business processes . This seems not to be the case in this issue so we suggest decreasing the issue priority.Regards\'"", ""Comment 4: \'Hello Aleksandra,Oké!.Regards,Gerard \'"", ""Comment 5: \'Thank you\'"", ""Comment 6: \'This item has no stock in XL for EX warehouse. !screenshot-1! \'"", ""Comment 7: \'Good morning Piotr,thanks for your support. You may close this ticket.I wish you a Merry Cristmas and a Happy New Year.Enjoy your holidays.Kind regards,Gerard \'"", ""Comment 8: \'Thank you"", ""Comment 9: I wish you tooa Merry Christmas and a Happy New Year.Regards,\']""]\nRelated Issues:\n[]\n\n### End'}"
901,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8130\n\n### Instruction:\nHi\r\n\r\nThe integration between DHC x DHP in Toledo factory has stoped.\r\nWe have VTs, PLRs and Medicated control not synchronized from DHC.\r\nVT-2538/22 / VT-2542/22 / Others VTs\r\n0871191222035 / 0871191222032 / Others PLRs\r\n4/71917-01 / Others Medicated controls\r\n\r\nCould you check it please?\r\n\r\nThank you\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 2: ""Hi PiotrLooking to Linked servers in the database\', \'Comment 3: seems that this wasn\\\'t updated by KOTRAK.I don\\\'t know if this has any relation to the connection.!image!""\', \'Comment 4: ""For the service there are errors with the connection to the sql server,and as you can see it was restarted a few hours ago !screenshot-1! Can you do a application pool restart for PlantIntegrationDhcService?I don\\\'t have permissions on my account.""\', ""Comment 5: \'Hi PiotrI have already restarted"", ""Comment 6: but I did it again right now.Unfortunatelly no success until nowThank you\'"", \'Comment 7: ""PLR\\\'s are in DHC now  !screenshot-2! VT\\\'s !screenshot-3! We have also restarted the application pool for PlantIntegrationDhcService""\', ""Comment 8: \'Hi PiotrI can see these documents on DHP/DHC.Did you only restarted PlantIntegrationDhcService in IIS?Thank you\'"", ""Comment 9: \' !screenshot-4! \'"", ""Comment 10: \'Did you only restarted PlantIntegrationDhcService in IIS?Yes"", \'Comment 11: stopped site and application pool\', ""Comment 12: then started app. pool and site.And finally browse website.\'"", ""Comment 13: \'[~mberbert@deheus.com]I repeat the request for an admin on the toledo DHP server"", ""Comment 14: as you can see today it is important that we have such permissions.Thank you.\'"", ""Comment 15: \'This ticket has been closed.\'"", ""Comment 16: \'[~lalmeida1@deheus.com]\']""]\nRelated Issues:\n[]\n\n### End'}"
902,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8129\n\n### Instruction:\nVT printouts is taking a long time to load\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 2: ""Hello,I would like additional information:- does the preview also take a long time to generate or only the printout?,- the problem only applies to VT\\\'s. I would like some examples - is the problem for every VT?,- is the problem on every server?Thank you and regards.""\', ""Comment 3: \'Please it is fine now"", \'Comment 4: kindly close  !image002!    *From:* Piotr Gaczorek (Jira) <jira@kotrak.com>   *Sent:* Friday\', \'Comment 5: December 23\', \'Comment 6: 2022 8:27 AM  *To:* Feyi\', ""Comment 7: Solomon <SFeyi@koudijs.com.gh>  *Subject:* DGS-8129 Vt printouts taking a very longtime to load   |  *{color:white} *CAUTION: This message originated from outside the organisation. Please do not click on links or open attachments unless you trust the sender and know the content is safe.*{color}* |   \']""]\nRelated Issues:\n[]\n\n### End'}"
903,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8128\n\n### Instruction:\nHi\r\n\r\nWe uploaded the pricelist to DHC but it\'s not updating in DHH.\r\nIMPORTANT: We changed the local IP in DHC server today. Mr Przemek made some change in communication with DHH to make Recipes integrate, now we have this Price List issue.\r\n\r\nCould you please check it?\r\nThank you very much\n\n### Response:\n[""Comment 1: [\'!image!!image-1!\'"", ""Comment 2: \'We need for ready for tomorrow morning.Thank you\'"", ""Comment 3: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 4: \'!image-2022-12-21-10-31-17-765.png!!image-2022-12-21-10-30-12-649.png!!image-2022-12-21-10-30-42-577.png!\'"", ""Comment 5: \'W DHC mamy processed successfull ale po prod area id w bazie holdingu nie ma tej pricelisty!image-2022-12-21-11-00-24-366.png!!image-2022-12-21-11-00-44-218.png!\'"", ""Comment 6: \'Wprawdzie Maicon podał tegotygodniową"", ""Comment 7: ale zeszłotygodniowej też nie ma\'"", ""Comment 8: \'Dear Maicon,We have analised your case and it looks there is no communication from DHC to DHH. In taht case"", ""Comment 9: please contact Valid.Regards\'"", ""Comment 10: \'Dear AleksandraYesterday Przemek needed to make some configuration in DHH about this DHC Recipes communication.Does him need to replicate this configuration in DHH also for Price list?Could you check with him first?Thank you\'"", ""Comment 11: \'Is the filter fine? I have consulted with Przemek. Price List from last week is in DB"", ""Comment 12: please verify!image-2022-12-21-14-21-06-171.png!\'"", ""Comment 13: \'HiThe filter was correct. I myself checked it when we raised this DGS.But OK! Now the information is there. You can close this task.Thank you very much.\'"", ""Comment 14: \'Thank you.Regards\']""]\nRelated Issues:\n[]\n\n### End'}"
904,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8127\n\n### Instruction:\nWrong final product in additional technology VE307499.\r\nShould be 307499 instead of 303436\r\n\r\nCan you please fix this asap, there are peol[ple waiting on it.\r\n\r\nThanks in advance,\r\nRob.\n\n### Response:\n[""Comment 1: [\'Hello"", ""Comment 2: We kindly inform you that wecurrentlyare processing another Priority1 task.We will revert to processing your task as soon as possible.Regards\'"", ""Comment 3: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 4: \'Provided additional technology has been modified. Please check.\'"", \'Comment 5: ""It\\\'s OK now\', \'Comment 6: the ticket can be closed.Thanks for the support.""]\']\nRelated Issues:\n[]\n\n### End'}"
905,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8126\n\n### Instruction:\nDear Sirs,\r\n\r\nin Bestmix we have 2 plants but in DHH we combined it into 1.\r\nI did the customization in DHH.\r\nPlease do your part in DHC - see screenshot I attached\r\nCode 0511\r\nParent production area  051\r\n\r\nPlease treat it as a priority - go live project\r\n\r\nSince I am on holiday since tomorrow, please contact Rob Hughan\r\nrhughan@deheus.com\r\n\r\nKind regards,\r\nDiana Cielecka\r\n\n\n### Response:\n[""Comment 1: [\'!image-1!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'!image-2022-12-21-08-33-07-537.png!\'"", ""Comment 4: \'!image-2022-12-21-08-42-57-261.png!!image-2022-12-21-08-43-15-554.png!\'"", ""Comment 5: \'!image-2022-12-21-12-07-18-661.png!\'"", ""Comment 6: \'Dear DianaPlease"", ""Comment 7: check if it is fine for you.Regards\'"", ""Comment 8: \'{color:black}Goodmorning,{color} {color:black}{color} {color:black}My colleague created this ticket"", ""Comment 9: but I am unable to view it:{color} !image001!{color:black}{color} {color:black}{color} {color:black}Can you add me to see it?{color} | |{color:#000001} Kindregards,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Rob{color} |{color:#000001} {color} |{color:#000001} Hughan{color} |  {color:#000001}ApplicationEngineer{color} | | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}{color:blue}{color}!image002!{color:blue}{color}{color:black} <[https://www.deheus.com/]>{color} | |  *{color:#006FB7} *DEHEUSANIMALNUTRITIONB.V.*{color}* | | | |{color:#000001} P.O.Box396 6710BJEde TheNetherlands{color} | |{color:#000001} Rubensstraat175 6717VEEde TheNetherlands{color} | | |{color:#000001} M:{color}{color:#000001}{color}{color:#000001}+310621127007{color}{color:#000001} <tel:+31%200621127007>{color} |  {color:#000001}CoC16011201{color}   _{color:#000001} _Thise‑mailmessageanditsattachmentsaresubjecttothedisclaimer_ _publishedonthewebsiteof_{color}_{color:#000001} _+{color}[{color:#000001}{color}{color:#000001} _+ DeHeusAnimalNutrition+_{color}{color:#000001} {color}|https://www.deheus.com/disclaimer]{color:#000001} {color}+__{color:#000001} _._{color}_ | |{color:blue}{color} !image003!{color:blue}{color} <[https://www.facebook.com/deheusanimalnutrition]>{color:black}{color} | |{color:blue}{color} !image004!{color:blue}{color} <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | |{color:blue}{color} !image005!{color:blue}{color} <[https://www.linkedin.com/company/royal-de-heus/mycompany/]>{color:black}{color} | |{color:blue}{color} !image006!{color:blue}{color} <[https://www.instagram.com/de_heus_animal_nutrition/]>{color:black}{color} | |{color:black}{color} !image007.jpg|thumbnail!{color:black}{color} |   \'"", \'Comment 10: ""Hi Aleksandra,I can\\\'t check as I do not have access to DHC. If you send me the screens shot from the system\', \'Comment 11: the same I sent you with the changes I requested I will be able to approve it.Please treat is us priority 1. We need to send the recipes asap.Please ass a copy to my friend ROB as I AM ON HOLIDAYS!Kind regrardsDiana""\', ""Comment 12: \'Olu"", \'Comment 13: chodziło aby spiąć 511 z parentem 51\', ""Comment 14: na twoim screenie widać że 511 jest spięty z parentem 442. Przepiąłem na 51 na produkcji w VN. Jak na razie obowiązują ustalenia ze takich zmian dokonuje lokalne IT a my ich wspieramy w tym jak taka konfiguracja powinna wyglądać żeby osiągnęli zamierzony cel.\'"", ""Comment 15: \'Dzięki Przemku"", \'Comment 16: Na razie to lokalne IT się dre\', \'Comment 17: że jest na wakacjach. Co do spinania\', \'Comment 18: bo ja tylko przeedetywałam w Holdingu BP i Production Area (czyli spacja / check żeby save było active)\', \'Comment 19: myślisz\', \'Comment 20: że coś nagmerałam przy okazji? :)w sumie to nawet nie wiem\', ""Comment 21: jak tego parenta dodać :Pwięc to raczej nie ja :P\'"", ""Comment 22: \'Done. Rob is added as a Participant.\'"", ""Comment 23: \'generalnie to dostałem maila z którego wynika ze nie powinno to zostać ustawione jako parent ale ok"", ""Comment 24: jak chcieli to tak mają.\'"", ""Comment 25: \'Wiesz"", \'Comment 26: z tym nie dyskutuję\', \'Comment 27: raczej zakładam\', \'Comment 28: że Diana zrobiła to źle\', \'Comment 29: a potem zgłosiła\', ""Comment 30: że nie pykło.\'"", ""Comment 31: \'Mniejsza z tym"", ""Comment 32: dzięki za pomoc :):*\'"", ""Comment 33: \'Hi,Can we close this task?Regards\'"", ""Comment 34: \'pease close the task\']""]\nRelated Issues:\n[]\n\n### End'}"
906,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8125\n\n### Instruction:\nOrder SO-8150/12/22 (external ordernumber SO000041513) contains three lines, all with a special. For third orderline, the one time recipe is sent to PCS. For first two lines (both for item 303436 with special 702072), the one time recipe is generated (we see it in DHP) but it does not seem to be exported to PCS. \r\nProduction for this order must start. Please check why the one time recipes for order lines 1 and 2 (for item 303436) are not exported to PCS and - if possible - export the recipes so that the plant can start production.\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!!image-1!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 3: ""NIe ma tych receptur w tabeli export\', \'Comment 4: w [DHPlantPCSBusinessLogicMain].[dbo].[Recipes] są :{code:java} select *  FROM [DHPlantPCSBusinessLogicMain].[dbo].[Recipes]  where  OrderId=\\\'89C78DF4-E281-4183-ADD0-F741382EA25C\\\'{code} !screenshot-1! Nie ma ich w eksporcie:{code:java}  select * FROM [DHPlantPCSBusinessLogicMain].[dbo].[ExportRecipes]where EntityId in(46936,46940,46939,46935){code} !screenshot-2! tutaj też nic nie pokazuje:{code:java}select *  FROM [DHPlantPCSBusinessLogicMain].[dbo].[WebApiRequestLog]  where path like \\\'%recipe%\\\' and body like \\\'%46939%\\\'  order by 1 desc{code} !screenshot-3! ""\', ""Comment 5: \'Hello,Correct synchronization of export to PCS is to synchronize the recipe "", \'Comment 6: flag error for these recipes Related to the commodity did not have the associated production definition flag.There is a flag on the recipeProduction will resume if the recipe flag is modified\', ""Comment 7: so they will not be sent to PCSPlease correct the recipe.These are the assumptions in your production.Regards\'"", \'Comment 8: ""{code:java}SELECT TOP 100  R.*FROM dbo.Recipes RINNER JOIN dbo.Items I ON I.Id = R.ItemIdWHERE-- R.EntityId NOT IN (SELECT E.EntityId FROM dbo.ExportRecipes E)    AND    R.IsProductDefinition = 0    AND I.IsDerived = 0    --AND NOT EXISTS     --(    --    SELECT *    --    FROM dbo.Recipes ZR    --    WHERE ZR.IsProductDefinition = 1    --        AND ZR.ItemId = R.ItemId    --)\\\\tand r.EntityId = 46934ORDER BY R.EntityIdselect * from dbo.Recipeswhere itemid = \\\'2BA9DE6F-A5D0-41E6-882F-C2ED8D1DE942\\\'{code}""\', ""Comment 9: \'Is productionDefinition ma być 0 inne wcześniej receptury.Do weryfikacji klienta receptura !image-2022-12-20-17-28-24-227.png!\'"", ""Comment 10: \'Hi Adrian"", \'Comment 11: Ok\', \'Comment 12: I now see that invalid additional technology VE307499 was created for 303436 for Veghel. We cannot (yet) remove or undo this additional technology in the application. Can you please remove the additional technology VE307499. After this\', ""Comment 13: the one time recipes I think should be sent to PCS\'"", ""Comment 14: \'Or can you update the flag in the two recipes in DHP"", ""Comment 15: so that it will be exported?\'"", ""Comment 16: \'Ok removed VE307499. Please verify. The problem has been resolved? Regards\'"", ""Comment 17: \'Thank you. Recipes were sent to Pcs. This ticket can be closed.  {quote}Op 20 dec. 2022 om 18:12 heeft Adrian Kozak (Jira) <jira@kotrak.com> het volgende geschreven:  {quote}  {quote} \\\\ufeff |{color:#ffffff} CAUTION: This message originated from outside the organisation. Please do not click on links or open attachments unless you trust the sender and know the content is safe.{color} |{color:#999999}{color}{color:#999999}{color}{color:#7a869a}{color}{color:#7a869a}{color}  {quote}\']""]\nRelated Issues:\n[]\n\n### End'}"
907,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8124\n\n### Instruction:\nOn the customer card we have a checkbox to indicate whenever a customer needs to have his technical results created. It looks like this checkbox is marked at all cases and is not editable. \r\n\r\nThis field should be editable by all users.\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'MitchIf the checkbox is not marked"", ""Comment 4: the Technical Results tab should to be hidden in Financial Statement?\'"", ""Comment 5: \'It should be atleast not be shared with the customer. So creating a PDF should be not possible.For internal purposes it can be helpfull to have this calculations either way.\'"", ""Comment 6: \'Checkbox Techical Results in Customer Card # Checkbox must be visible only in MAS NL and MAS BE for BP_Category = Farmer (only in these two sectors TR are calculated) # Checkbox must be available for editing for role Customer Edit # If the checkbox = 1 the Technical Result printout can be generated by a user Otherwise"", \'Comment 7: the TR can be calculated in Financial Statement\', ""Comment 8: but the printout for Technical Results cannot be generated\'"", ""Comment 9: \'1. Checkbox is now visible only in MAS NL and MAS BE for BP_Category =Farmer2. Checkbox is now editable for all users with Customer edit role.3.If the checkbox is marked the Technical Result printout can be generated by a userOtherwise"", \'Comment 10: the TR can be calculated in Financial Statement\', ""Comment 11: but the printout for Technical Results cannot be generated.\']""]\nRelated Issues:\n[]\n\n### End'}"
908,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8123\n\n### Instruction:\nSlaughter report “BN2233402 1480672” of 15 Dec gives an error on the Capacity (stockingDensityPerM2) field. \r\n\r\nIt contains the value 2.5, but according to Intense only integer values are allowed. This should be adjusted. We can have all kinds of numbers in this field.\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Podczas synchronizacji z Kofax do Intense wartość Capacity trafia w złe pole - Doc_IntColumn20"", ""Comment 3: które w Intense jest flagą (0/1).Docelowo powinno to wyglądać następująco:Jeżeli z Kofax synchronizujemy wartość Capacity -> Ustaw flagę Doc_IntColumn20 = 1 oraz uzupełnij wartość w polu Doc_ShortStringColumn4. Wartość Capacity wg. informacji od klienta jest typu decimal.Pozdrawiam,Grzegorz\'"", ""Comment 4: \'Czy to będzie poprawione?\'"", ""Comment 5: \'[~tomasz.koziol@kotrak.com]"", ""Comment 6: [~michal.kordys@kotrak.com] :)\'"", ""Comment 7: \'Wrzucone na wewnętrzną listę podsumowującą,\'"", ""Comment 8: \'DHNLC-1207\'"", ""Comment 9: \'Ready for UAT tests\'"", ""Comment 10: \'Can be closed.\']""]\nRelated Issues:\n[]\n\n### End'}"
909,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8122\n\n### Instruction:\nSI RLM/2022/2002 should be linked to PI RLM/2022/1110 (this should be the leading doc).\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'SI-RLM/2022/2002 is linked to PI-RLM/2022/1110!image-2022-12-21-11-12-50-539.png!\']""]\nRelated Issues:\n[]\n\n### End'}"
910,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8121\n\n### Instruction:\nIn some sectors we have a checkbox on the round that is called ""Active"". The checkbox should be checked whenever the round is active and should be unchecked whenever the round is closed.\r\n\r\nNow this is empty at all rounds.\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'-All rounds have been updated.-If round status was set to closed then the active field was set to 0 if round status was set to active then the field was set to 1.-At this point"", ""Comment 4: each round that changes from active to closed automatically changes the active field.-Every new round get marked field active.\']""]\nRelated Issues:\n[]\n\n### End'}"
911,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8120\n\n### Instruction:\nIf ERP Document number in Invoice is equal to 1000000305 the user should be able to adjust the ERP document number in  Invoice (ligthening icon action ) \r\n\r\nThe same for Feed Sale positions*\n\n### Response:\n[""Comment 1: [\'* Na fakturach PI"", ""Comment 2: SI powinna być możliwa edycja pola Document Number ERP (Doc_ShortStringColumn20) jeżeli pole Doc_SetID IS NOT NULL - akcja spod pioruna\'"", ""Comment 3: \'* -Na Feed sale powinna być możliwa edycja pola Document No. (ELM_ShortStringColumn2) jeżeli pozycja Feed sale (Del_ID) nie znajduje się w mapowaniach w tabeli w kolumnie ID tabeli AgraSyncIdentityMappingsProd.dbo.FeedSaleMappings-Na tą chwilę jest już blokowana cała zakładka w tym pole Document No. poprzez funkcję"", \'Comment 4: która sprawdza czy dana pozycja przyszła z Milasa\', \'Comment 5: więc powinno to wystarczyć i pozostałe pozycje\', ""Comment 6: które nie pochodzą z Milas powinny być możliwe do edycji.\'"", ""Comment 7: \'Na ten moment na produkcyjnym środowisku!image-2022-12-22-14-24-08-546.png!!image-2022-12-22-14-24-00-116.png!\'"", ""Comment 8: \'[~tomasz.zygon@kotrak.com] # W jakich sektorach zostały wprowadzone zmiany i na jakich dokumentach? W jaki sposób zmienić numer zmigrowanej faktury"", ""Comment 9: która jest w archiwum? W tasku informacja o akcji spod pioruna. # Czy zmiany są również wprowadzone na TEST?\'"", ""Comment 10: \'Na IBIP_DH_TEST powinno to działać"", ""Comment 11: a na produkcyjnym póki co zmiany są wykomentowane i czekało to na implementację zmian z taska z S2P - https://helpdesk.kotrak.com/browse/DHNLC-1206\'"", ""Comment 12: \'DHNLC-1210Implemented on IBIP_DH_TEST"", ""Comment 13: to be tested by DH\'"", ""Comment 14: \'Ready for UAT tests\'"", \'Comment 15: ""I can\\\'t test this because I cannot find a document with number 1000000305. Which document did you use to test this with?""\', \'Comment 16: ""You can try on some invoices from migration\', \'Comment 17: for example on some from this list. It\\\'s possible for migration invoices.32762 SI-RLM/2022/036732753 PI-RLM/2022/036532744 SI-RLM/2022/036532743 SI-RLM/2022/036432742 SI-RLM/2022/036332741 SI-RLM/2022/036232740 SI-RLM/2022/036132739 SI-RLM/2022/036032738 SI-RLM/2022/035932737 SI-RLM/2022/035832736 SI-RLM/2022/035732735 SI-RLM/2022/035632734 SI-RLM/2022/035532733 SI-RLM/2022/035432732 SI-RLM/2022/035332731 SI-RLM/2022/035232730 SI-RLM/2022/035132729 SI-RLM/2022/035032728 SI-RLM/2022/034932727 SI-FNM/2022/0022""\', ""Comment 18: \'Sprawdzone przez klienta"", ""Comment 19: można wrzucać na PROD. !image-2023-01-13-12-27-05-676.png!\'"", ""Comment 20: \'Done at production database.\']""]\nRelated Issues:\n[]\n\n### End'}"
912,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8119\n\n### Instruction:\n VT-246/12/22 has status closed, but the related warehouse order has status execution pending. It doesn\'t close and the related stock units stay in progress. Please close this WO so that the stock units have status on stock\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!afbeelding!!afbeelding-2!!afbeelding-3!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'!image-2022-12-20-14-29-03-028.png!\'"", ""Comment 4: \'Hi Thomas,It should be fine now. Please"", ""Comment 5: verifyRegards\'"", ""Comment 6: \'Yes it is fine"", ""Comment 7: thanks. Any idea what causes this and how to prevent this from happening?\'"", ""Comment 8: \'W sumie 11 eventów reopen WO!image-2022-12-21-13-17-01-192.png!!image-2022-12-21-13-21-01-621.png!Tu jest aż 10 minut!image-2022-12-21-13-21-45-401.png!\'"", ""Comment 9: \'Hi Thomas,I have verified logs and I can see Warehouse Order has been reopened several time. Do you have any knowledge if someone from your Team reopened WO(PI)-5/12/22?Regards\'"", ""Comment 10: \'Could be me in this case"", ""Comment 11: I tried reopening and closing a few times\'"", ""Comment 12: \'Can we close this task?Regards\'"", ""Comment 13: \'Please close\'"", ""Comment 14: \'Thank you.\']""]\nRelated Issues:\n[]\n\n### End'}"
913,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8118\n\n### Instruction:\nPlease set ID 76877 back to entry\r\nslaughtery report SRBe/1064\n\n### Response:\n[\'Comment 1: [""It\\\'s in Entry right now.""]\']\nRelated Issues:\n[]\n\n### End'}"
914,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8117\n\n### Instruction:\nAttached ASN is not handled as warehouse intake, can you check? settlement is pieces, item is in pcs: so I expect it to be handled in DHP?\n\n### Response:\n[""Comment 1: [\'!afbeelding!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 3: \\\'Hi,Is the packing form correct then? Shouldn\\\\\\\'t it be ""packed"" ? You would probably need to cancel this ASN and make a new one.!image-2022-12-21-11-25-09-173.png!\\\'\', ""Comment 4: \'Indeed you;re right: I was able to change it to piece. But I cannot delete the VT: Can you do this?\'"", ""Comment 5: \'Why delete? VT should be cancelled. Please"", ""Comment 6: let me know if you are able to cancel the VT.Regards\'"", ""Comment 7: \'Ah sorry"", ""Comment 8: I mean cancel\'"", ""Comment 9: \'Please"", ""Comment 10: try now. You shuld be able to cancel VT now. Let me know about the result.Regards\'"", ""Comment 11: \'Ticket can be closed\']""]\nRelated Issues:\n[]\n\n### End'}"
915,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8116\n\n### Instruction:\nFSK 31 oraz 66/12/22/PK nie można zaksięgować.  Są to korekty danych \r\nDla przykładu 66/11/22/PK, księguje się bez problemu, również jest to korekta danych\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Hi,On invoice 66/11/22/PK payment has been corrected (from casch to transfer) that is why invoice has been posted on accounts related with payment!image-2022-12-20-14-41-47-600.png!!image-2022-12-20-14-44-42-360.png!Correction invoicesFSK 31 and 66/12/22/PK is related only with the customer data. Customer is still the same. There is no amounts to be posted.If you want to post this documents please give us information on accounts and amounts.\'"", ""Comment 3: \'thank you. You can close this task\']""]\nRelated Issues:\n[]\n\n### End'}"
916,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8115\n\n### Instruction:\nUser wants to create a VT for calloff CL000008902 in DHP. VT is not created, an error message shows. Maybe this is related to the fact that the calloff is for location 98 instead of location 5? can you advise how to solve?\n\n### Response:\n[""Comment 1: [\'!afbeelding!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'I think we miss destination site for Andel Mest?\'"", ""Comment 4: \'Also can you check if configuration is correct for dispatches for location 098?\'"", \'Comment 5: \\\'2022-12-20 13:50:40 (7ac126a3-e950-4e5f-8f37-9522b2443b61/Plant.VC.BusinessLogic/DHVD01AP184/20836/220) [Error] Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware - Error during request{ ""scheme"": ""http""\', \'Comment 6: ""host"": { ""Value"": ""dhvd01ap184:82""\', \'Comment 7: ""HasValue"": true\', \'Comment 8: ""Host"": ""dhvd01ap184""\', \'Comment 9: ""Port"": 82 }\', \'Comment 10: ""path"": ""/api/VehicleTicket/createVehicleTicketFromShippingNotice""\', \'Comment 11: ""queryString"": []\', \'Comment 12: ""requestBody"": ""\\\\\\\\""7d2730b1-a089-42f9-85a3-14e62543d118\\\\\\\\""""}.System.ArgumentException: DefaultDestinationSiteIsNotConfigured\\\'\', ""Comment 13: \'This look like the same issue with configuratio like here :in task DGS-8036this is for bulk :!image-2022-12-20-13-57-24-528.png!There is no unit in configuration for feed 098 :Please add it in WMS->configuration-> storage locationsThis plant need to be add and set in vt configuration!image-2022-12-20-14-00-17-271.png!\'"", ""Comment 14: \'Indeed"", \'Comment 15: I added storage location Andel Mest\', ""Comment 16: that solved it: Thanks!!afbeelding-2!\']""]\nRelated Issues:\n[\'DGS-8036\']\n\n### End'}"
917,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8114\n\n### Instruction:\nThe round in the NAS is already closed. However we can still select this number on documents, in  this example in the Elements to sales functionality.\r\nClosed rounds should never be selectable on any other document.\r\n\n\n### Response:\n[""Comment 1: [\'!image!!image-1!\'"", \'Comment 2: \\\'I have verified and fixed the ""round"" fields on the documents. The elements that required fix were loan payments and purchase invoice elements.\\\']\']\nRelated Issues:\n[]\n\n### End'}"
918,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8113\n\n### Instruction:\nHello,\r\n\r\nI am not able to move invoices to another round.\r\nScreenshot is from Richard. He has this rights.\r\n\r\nThanks for your support\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Now"", ""Comment 4: you should be able to update round number on this invoice from Action -> Update round number on InvoicePlease verify and confirm that it works.!image-2022-12-20-11-29-51-637.png!\'"", ""Comment 5: \'Na tą chwilę został zmieniony parametr dla akcji: Update round number on Invoice i rundy są wyświetlane dla warunków w następujący sposób. * jeśli Sales invoice i Customer (Doc_CstID) = Slaughter --> rundy pobierane z pola Reference (Doc_IntColumn8) * jeśli Sales invoice i Customer (Doc_CstID) != Slaughter --> rundy pobierane z pola Customer (Doc_CstID) * jeśli Purchase invoice i Reference(Doc_CstID) != (Farmer"", \'Comment 6: Pas Farmer\', \'Comment 7: Oppas Farmer) --> rundy pobierane z pola Supplier (Doc_IntColumn8) * jeśli Purchase invoice i Reference(Doc_CstID) = (Farmer\', \'Comment 8: Pas Farmer\', ""Comment 9: Oppas Farmer) --> rundy pobierane z pola Reference (Doc_CstID)\'"", ""Comment 10: \'{color:black}Hi Damian,{color} {color:black}{color} {color:black}Indeed for moving documents it works. Only in category Slaughtery we are not able to move.{color} {color:black}We need this action to have the correct posting on our round.{color} {color:black}{color} {color:black}Thanks for your support.{color} {color:black}{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Christinede{color} |{color:#000001} {color} |{color:#000001} Jong{color} |  {color:#000001}MedewerkerContractadministratie{color} | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.de-heus.nl/]>{color} | |  *{color:#006FB7} *DEHEUSVOEDERSB.V.*{color}* | | | |{color:#000001} Postbus396 6710BJEde \\\\u200b{color} | |{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} | | |{color:#000001} T:0318675567{color} |  {color:#000001}KvK14626985{color}   _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | | !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | | !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} | | !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} | |{color:black}{color} !image006.jpg|thumbnail!{color:black}{color} |      *Van:* Damian Świstek (Jira) <jira@kotrak.com>   *Verzonden:* dinsdag 20 december 2022 11:32  *Aan:* Jong"", ""Comment 11: Christine de <CJong@deheus.com>  *Onderwerp:* DGS-8113 Rights to move invoices to another round   |  *{color:white} *CAUTION: This message originated from outside the organisation. Please do not click on links or open attachments unless you trust the sender and know the content is safe.*{color}* |   !image007!\'"", ""Comment 12: \'Hi Christine,So it means you can update round number for invoices or do you have some example where you cannot update round on invoice?\'"", ""Comment 13: \'{color:black}Hi Damian,{color} {color:black}{color} {color:black}Yes for invoices it works"", \'Comment 14: but not in category Slaughtery.{color} {color:black}I don’t know why this differs from other categories as NAS doesn’t work with SR like in MAS{color} {color:black}{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Christinede{color} |{color:#000001} {color} |{color:#000001} Jong{color} |  {color:#000001}MedewerkerContractadministratie{color} | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.de-heus.nl/]>{color} | |  *{color:#006FB7} *DEHEUSVOEDERSB.V.*{color}* | | | |{color:#000001} Postbus396 6710BJEde \\\\u200b{color} | |{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} | | |{color:#000001} T:0318675567{color} |  {color:#000001}KvK14626985{color}   _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | | !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | | !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} | | !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} | |{color:black}{color} !image006.jpg|thumbnail!{color:black}{color} |      *Van:* Damian Świstek (Jira) <jira@kotrak.com>   *Verzonden:* dinsdag 20 december 2022 13:52  *Aan:* Jong\', ""Comment 15: Christine de <CJong@deheus.com>  *Onderwerp:* DGS-8113 Rights to move invoices to another round   |  *{color:white} *CAUTION: This message originated from outside the organisation. Please do not click on links or open attachments unless you trust the sender and know the content is safe.*{color}* |   \'"", ""Comment 16: \'Christine"", ""Comment 17: could you please provide the ID of the invoice in which you cannot change the Round Number?Thank you in addvance!\'"", ""Comment 18: \'Dodane do listy z podsumowaniem wysłanej do klienta.\'"", ""Comment 19: \'{color:black}Hi Ewa,{color} {color:black}{color} {color:black}We wanted to close the round on 800629/0002/0001. This is why we need to move several invoices from one round to another.{color}  {color:black}I was working on this with Richard.{color} {color:black}{color} {color:black}I now think we made the wrong approach. We have to do it from document tab.{color}  {color:black}It is not possible from inside the round.{color} {color:black}{color} {color:black}Strange thing is Richard saw possibilities (read: rights to do this) I was not able to.{color} {color:black}But working on too many things I can’t specify what the problem was{color} {color:black}☹{color}{color:black}{color} {color:black}{color} {color:black}Richard is on leave. We will continue after his break.{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Christinede{color} |{color:#000001} {color} |{color:#000001} Jong{color} |  {color:#000001}MedewerkerContractadministratie{color} | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.de-heus.nl/]>{color} | |  *{color:#006FB7} *DEHEUSVOEDERSB.V.*{color}* | | | |{color:#000001} Postbus396 6710BJEde \\\\u200b{color} | |{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} | | |{color:#000001} T:0318675567{color} |  {color:#000001}KvK14626985{color}   _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | | !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | | !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} | | !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} | |{color:black}{color} !image006.jpg|thumbnail!{color:black}{color} |      *Van:* Ewa Mucha (Jira) <jira@kotrak.com>   *Verzonden:* donderdag 22 december 2022 09:42  *Aan:* Jong"", ""Comment 20: Christine de <CJong@deheus.com>  *Onderwerp:* DGS-8113 Rights to move invoices to another round   |  *{color:white} *CAUTION: This message originated from outside the organisation. Please do not click on links or open attachments unless you trust the sender and know the content is safe.*{color}* |   \'"", ""Comment 21: \'Waiting for Richard\'"", ""Comment 22: \'Sorry I forgot to reply. You can resolve this as done.\']""]\nRelated Issues:\n[]\n\n### End'}"
919,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8112\n\n### Instruction:\nPlease remove additional technology UT508095.\r\n\r\nThank you,\r\nRob.\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Hello"", ""Comment 3: additional technology has been removed.\'"", ""Comment 4: \'Thank you Piotr"", ""Comment 5: the ticket can be closed.\']""]\nRelated Issues:\n[]\n\n### End'}"
920,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8111\n\n### Instruction:\nHello,\r\n\r\nitems 505330-z20 and 086426-z20 are on stock in Andel, see example for item 086426-z20. However, when item needs to be picked on warehouse order, system shows no available pallets. Can this be solved, and can you indicate the reason for this?\n\n### Response:\n[""Comment 1: [\'!afbeelding!!afbeelding-2!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'You can close this ticket for now: Packed goods are taken in as Bulk"", ""Comment 4: so thats why it cannot be processed on the WO\']""]\nRelated Issues:\n[]\n\n### End'}"
921,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8110\n\n### Instruction:\nHi,\r\n\r\nWe need to get Draft PLR report but the current DHP version does not support this kind of report. I registered a ticket in Jira Servicedesk but this process takes a long time to complete usually and It is so important to us that this upgrade is done asap.\r\nAccording to the above explanation, I will be grateful if the process of starting the update will be done sooner.\r\n\r\nThanks and regards.\r\n\n\n### Response:\n[""Comment 1: [\'Hello,\\\\r\\\\rWe are investigating your issue. We will inform you about the solution as soon as possible.\\\\r\\\\rRegards\\\\r\\\\r\'"", ""Comment 2: \'Could you please provide me a ticket number that you have raised for applications upgrade?Regards\'"", ""Comment 3: \'Yes. it is GDC-762\'"", ""Comment 4: \'Dear Ramin,I can see GDC task is assigned to Theo Berendsen. The only way to push this upgrade is to contact with Theo directly. Service Desk can do nothing to push the proccess as it is not approved"", \'Comment 5: in this case\', \'Comment 6: by Theo.Please\', ""Comment 7: confirm if I can close P1 task.Regards\'"", ""Comment 8: \'Dear Aleksandra,Thanks for your explanation.Before closing this ticket would you please tell me how much is this update cost?\'"", \'Comment 9: ""All necessary information like costs and date of upgrade is usually delivered within GDC task. I\\\'ll try to get some more information\', \'Comment 10: who you should contact directly as these are not in Service Desk scope and we do not have that information.Regards""\', ""Comment 11: \'Hi,For costs estiamtion"", \'Comment 12: please contact directly [marcin.kleszcz@kotrak.com|mailto:marcin.kleszcz@kotrak.com]Please\', ""Comment 13: confirm if I can close this task.Regards\'"", ""Comment 14: \'Hi Aleksandra.Many thanks for your reply.Please close this ticket.\'"", ""Comment 15: \'Thank you\']""]\nRelated Issues:\n[]\n\n### End'}"
922,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8109\n\n### Instruction:\nUrosły raporty PCS. Błąd rap BGB Already exists last big bag for this production.\r\nProblem jest z lotem 221219003\r\n\r\n998,8 kod 27-663YI\r\nProszę o pilną pomoc.\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'W razie pytan prosze kontaktowac sie z pracownikiem Produkcji : 781290728\'"", ""Comment 3: \'Any news ??\'"", ""Comment 4: \'Any news ?? Production are stopped .\'"", ""Comment 5: \'Production is currently running. Messages are being processed.Please let us know if we can close this issue.\'"", ""Comment 6: \'Thanks. Task to close\'"", ""Comment 7: \'Temat na retro"", ""Comment 8: co tu się podziało? dlaczego Bartek dogenerował 13 etykietę i zmienił jej status na ostatni jak i tak jest nieaktywna i została się na rolkach. Dlaczego dogenerowanie fikcyjnej etykiety i zmiana statusu rozwiązała problem?!image!!image-1!\']""]\nRelated Issues:\n[]\n\n### End'}"
923,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8108\n\n### Instruction:\nFor this S2P, I moved a part of a feed delivery to the next round, because I want the final stock to be paid on the next round. When I now gather the S2P, the gross value of this line is the total invoice value, but the remaining value is the value that should be paid this round. Finally the value \'paid\' is the value that should be financially transmitted to the next round (basically like moving feed to the next round, but this time just a part of the delivery). How should we solve this?\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Change request will be handled under https://helpdesk.kotrak.com/browse/DHNLC-1206\'"", ""Comment 4: \'It will be handled on UAT and tested with Theo in January. After tests this can be deployed on PROD.\'"", ""Comment 5: \'New requirements related to this taks are in https://helpdesk.kotrak.com/browse/DHNLC-1226,requirements fromhttps://helpdesk.kotrak.com/browse/DHNLC-1206are outdated.\'"", \'Comment 6: ""Changes from task https://helpdesk.kotrak.com/browse/DHNLC-1226have been deployed on test and prod environment and confirmed in this task that works.Please verify that we can close this taks.Below are requirements fromhttps://helpdesk.kotrak.com/browse/DHNLC-1226{quote}*The new view is that even if the feed is partly moved from this round to the next round that the total remaining value of this invoice should be settled within this round. Only when a complete feed delivery is moved it should be part of the next S2P.*Example: # On Round 1 has been sent invoice DocNo123 with Weight 100kg from Milas or line has been added manually by user in Intense # From Round 1 to Round 2 has been moved 30 kg from the DocNo123Values on Round\', \'Comment 7: Financial Statement\', \'Comment 8: Saldo to pay:--------- * Round 1Round 1 (total 70kg) # DocNo 123 \', \'Comment 9: Weight 100kg # DocNo 123 \', \'Comment 10: Weight - 30kgFinancial Statement 1 (total 70kg) # DocNo 123 \', \'Comment 11: Weight 100kg # DocNo 123 \', \'Comment 12: Weight - 30kgSaldo to pay 1 (total 100kg) # DocNo 123 \', \'Comment 13: Weight 100kg----------- * Round 2Round 2 (total 30kg) # DocNo 123 \', \'Comment 14: Weight 30kgFinancial Statement 2 (total 30kg) # DocNo 123 \', ""Comment 15: Weight 30kgSaldo to pay 2 (total 0kg)No values for DocNo 123---------------------*One invoice should be shown on one line in the S2P. It cannot happen that one invoice is shown on multiple lines on the S2P. This leads to a lot of problems in calculating the right saldo to pay.*Example in Intense database:SP-M/0274 - multiple line with SI000006301 on S2P was caused by grouping \'Due date\'. Procedure for calculating Saldo to pay is grouping documents also by \'Due dates\' from Feed sale lines.If there is the same number"", \'Comment 16: but with different due dates it is grouping separately.It should be changed and on S2P system should displays one invoice numer only once.*Feed sale issues and verifying manualy adding elements.*\\\'Due date\\\' on Feed sale lines sometimes are empty and that causes issues with displaying line for the same document number few times. It can happen when users add manually Feed sale lines on Feed sale document and don\\\'t fill the field \\\'Due date\\\'.Some fields should be mandatory if line on feed sale is adding manually by user in Intense.Automatically calculated fields: * Customer (\\\'Customer code\\\' field from document header)Mandatory if there is no MilasId: * Date of the document * Descirption * Weight * Net Value * Price * VAT * Vat Rate * Gross value * Quantity * Due dateNot editable: * Price per 100 kgThere should be also reorganized order of field on element edit view to facilitate adding fields in good order - to be sent by DH{quote}""\', ""Comment 17: \'Can be closed.\']""]\nRelated Issues:\n[]\n\n### End'}"
924,"{'prompt': ""Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8107\n\n### Instruction:\n[INTERNAL] Podsumowanie dyżuru\n\n### Response:\n['Comment 1: []']\nRelated Issues:\n[]\n\n### End""}"
925,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8106\n\n### Instruction:\nSO-102/12/2022 only 5 ton on SOR Should be 7 ton. ( 5 ton not showing)\r\nWhen display partial sor then 5ton is visible !!!\r\n\r\nWe see also differences in DH-CDN and CDN-XL\n\n### Response:\n[""Comment 1: [\'!image-3!!image-4!!image-5!!image-6!!image-7!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Can this issued SOR already for 5 tons be canceled?Were there problems when issuing this SO-49/12?Maybe the operator issued only SOR for one position.\'"", ""Comment 4: \'{color:black}Piotr,{color} {color:black}{color} {color:black}It is very strange in the beginning the 5000 kg is not shown.{color} {color:black}Afterwards it is shown.{color} {color:black}{color}{color:black}{color} [{color:black}@Thuis"", \'Comment 5: Ronnie{color}|mailto:RThuis@deheus.com]{color:black} Can you react on the comment off Piotr{color} {color:black}{color} {color:black}{color} !image007!{color:black}{color} {color:black}{color} !image008!!image009!{color:black}{color} {color:black}{color} {color:black}{color} {color:black}{color} | |{color:#000001} Kindregards,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Bert{color} |{color:#000001} {color} |{color:#000001} Kremers{color} |  {color:#000001}SystemAnalist{color}   _{color:#000001} _WorkingonMonday,Tuesday,Thursday_{color}_ | | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.deheus.com/]>{color} | |  *{color:#006FB7} *DEHEUSANIMALNUTRITIONB.V.*{color}* | | | |{color:#000001} P.O.Box396 6710BJEde TheNetherlands{color} | |{color:#000001} Rubensstraat175 6717VEEde TheNetherlands{color} | | |{color:#000001} M:{color}{color:#000001}{color}{color:#000001}+31653729893{color}{color:#000001} <tel:+31%206%2053%20729%20893>{color} | |{color:#000001} T:+31886370461{color} |  {color:#000001}ChamberofCommerce 16011201{color}   _{color:#000001} _Thise‑mailmessageanditsattachmentsaresubjecttothedisclaimer_ _publishedonthewebsiteof_{color}_{color:#000001} _+{color}[{color:#000001}{color}{color:#000001} _+ DeHeusAnimalNutrition+_{color}{color:#000001} {color}|https://www.deheus.com/disclaimer]{color:#000001} {color}+__{color:#000001} _._{color}_ | | !image002! <[https://www.facebook.com/deheusanimalnutrition]>{color:black}{color} | | !image003! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image004! <[https://www.linkedin.com/company/royal-de-heus/mycompany/]>{color:black}{color} | | !image005! <[https://www.instagram.com/de_heus_animal_nutrition/]>{color:black}{color} | |{color:black}{color} !image006.jpg|thumbnail!{color:black}{color} |      *Van:* Piotr Gaczorek (Jira) <jira@kotrak.com>   *Verzonden:* dinsdag 20 december 2022 08:13  *Aan:* Kremers\', ""Comment 6: Bert <bkremers@deheus.com>  *Onderwerp:* DGS-8106 SO-102/12/2022 only 5 ton on SOR Should be 7 ton. (SDNL-36456)   |  *{color:white} *CAUTION: This message originated from outside the organisation. Please do not click on links or open attachments unless you trust the sender and know the content is safe.*{color}* |   \'"", ""Comment 7: \'{color:black}Piotr,{color}{color:black}{color}  {color:black}{color} {color:black}What is the connection off SO-49/12/ with this problem?{color} {color:black}I suppose you mean SOR-49/12/{color}  {color:black}{color} {color:black}{color} !image001!!image002!!image010!{color:black}{color} !image003!{color:black}{color} {color:black}{color} {color:black}{color} {color:black}{color} | |{color:#000001} Kindregards,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Bert{color} |{color:#000001} {color} |{color:#000001} Kremers{color} |  {color:#000001}SystemAnalist{color}   _{color:#000001} _WorkingonMonday,Tuesday,Thursday_{color}_ | | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image011!{color:black} <[https://www.deheus.com/]>{color} | |  *{color:#006FB7} *DEHEUSANIMALNUTRITIONB.V.*{color}* | | | |{color:#000001} P.O.Box396 6710BJEde TheNetherlands{color} | |{color:#000001} Rubensstraat175 6717VEEde TheNetherlands{color} | | |{color:#000001} M:{color}{color:#000001}{color}{color:#000001}+31653729893{color}{color:#000001} <tel:+31%206%2053%20729%20893>{color} | |{color:#000001} T:+31886370461{color} |  {color:#000001}ChamberofCommerce 16011201{color}   _{color:#000001} _Thise‑mailmessageanditsattachmentsaresubjecttothedisclaimer_ _publishedonthewebsiteof_{color}_{color:#000001} _+{color}[{color:#000001}{color}{color:#000001} _+ DeHeusAnimalNutrition+_{color}{color:#000001} {color}|https://www.deheus.com/disclaimer]{color:#000001} {color}+__{color:#000001} _._{color}_ | | !image012! <[https://www.facebook.com/deheusanimalnutrition]>{color:black}{color} | | !image013! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image014! <[https://www.linkedin.com/company/royal-de-heus/mycompany/]>{color:black}{color} | | !image015! <[https://www.instagram.com/de_heus_animal_nutrition/]>{color:black}{color} | |{color:black}{color} !image016.jpg|thumbnail!{color:black}{color} |        *Van:* Kremers"", \'Comment 8: Bert   *Verzonden:* dinsdag 20 december 2022 08:43  *Aan:* dgs@help.kotrak.com; Thuis\', \'Comment 9: Ronnie <RThuis@deheus.com>  *Onderwerp:* SDNL-36456 : DGS-8106 SO-102/12/2022 only 5 ton on SOR Should be 7 ton.    {color:black}Piotr,{color} {color:black}{color} {color:black}It is very strange in the beginning the 5000 kg is not shown.{color} {color:black}Afterwards it is shown.{color} {color:black}{color}{color:black}{color} [{color:black}@Thuis\', \'Comment 10: Ronnie{color}|mailto:RThuis@deheus.com]{color:black} Can you react on the comment off Piotr{color} {color:black}{color} {color:black}{color} !image017!{color:black}{color} {color:black}{color} !image018!!image019!{color:black}{color} {color:black}{color} {color:black}{color} {color:black}{color} | |{color:#000001} Kindregards,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Bert{color} |{color:#000001} {color} |{color:#000001} Kremers{color} |  {color:#000001}SystemAnalist{color}   _{color:#000001} _WorkingonMonday,Tuesday,Thursday_{color}_ | | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image011!{color:black} <[https://www.deheus.com/]>{color} | |  *{color:#006FB7} *DEHEUSANIMALNUTRITIONB.V.*{color}* | | | |{color:#000001} P.O.Box396 6710BJEde TheNetherlands{color} | |{color:#000001} Rubensstraat175 6717VEEde TheNetherlands{color} | | |{color:#000001} M:{color}{color:#000001}{color}{color:#000001}+31653729893{color}{color:#000001} <tel:+31%206%2053%20729%20893>{color} | |{color:#000001} T:+31886370461{color} |  {color:#000001}ChamberofCommerce 16011201{color}   _{color:#000001} _Thise‑mailmessageanditsattachmentsaresubjecttothedisclaimer_ _publishedonthewebsiteof_{color}_{color:#000001} _+{color}[{color:#000001}{color}{color:#000001} _+ DeHeusAnimalNutrition+_{color}{color:#000001} {color}|https://www.deheus.com/disclaimer]{color:#000001} {color}+__{color:#000001} _._{color}_ | | !image012! <[https://www.facebook.com/deheusanimalnutrition]>{color:black}{color} | | !image013! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image014! <[https://www.linkedin.com/company/royal-de-heus/mycompany/]>{color:black}{color} | | !image015! <[https://www.instagram.com/de_heus_animal_nutrition/]>{color:black}{color} | |{color:black}{color} !image016.jpg|thumbnail!{color:black}{color}{color:black}{color} |      *Van:* Piotr Gaczorek (Jira) <[jira@kotrak.com|mailto:jira@kotrak.com]>   *Verzonden:* dinsdag 20 december 2022 08:13  *Aan:* Kremers\', ""Comment 11: Bert <[bkremers@deheus.com|mailto:bkremers@deheus.com]>  *Onderwerp:* DGS-8106 SO-102/12/2022 only 5 ton on SOR Should be 7 ton. (SDNL-36456)   |  *{color:white} *CAUTION: This message originated from outside the organisation. Please do not click on links or open attachments unless you trust the sender and know the content is safe.*{color}* |   !image001-1!!image002-1!!image003-1!!image004!!image005!!image006.jpg|thumbnail!!image007!!image008!!image009!\'"", ""Comment 12: \'Yes it was about SOR-49/12.Was it  about these fields - executed 5 tons and there are still 2 tons left? !screenshot-1! \'"", ""Comment 13: \'Hello,We are closing this task as we haven’treceivedany replyfromyouforalong time. If the issueappearsagain"", ""Comment 14: please raise another task.Regards\'"", ""Comment 15: \'Do not exist in DHP!!!image!\']""]\nRelated Issues:\n[]\n\n### End'}"
926,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8105\n\n### Instruction:\nOrder SO000040537 is not accepted by VC module in DHP. I checked business partner data in DHC, it seems to be correct:\r\n\r\nbut in DHP it is not accepted. And I\'m not sure what;s the reason: Can you check and advice how to solve?\n\n### Response:\n[""Comment 1: [\'!afbeelding!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Target Business Partner has incorrect address or target address is assigned to incorect Business Partner :) Please"", \'Comment 4: compare Business Partners Code in DHC:!image-2022-12-19-15-20-02-926.png!!image-2022-12-19-15-14-38-713.png!When you resend the order\', ""Comment 5: please wait a bit longer as all need some time to reprocess.Regards!image-2022-12-19-15-20-02-926!\'"", ""Comment 6: \'!image-2022-12-19-15-19-22-838.png!\'"", ""Comment 7: \'Hi Aleksandra"", \'Comment 8: In this case the target business adress is assigned to the target business partner\', \'Comment 9: exactly as I expect it to be and as it is on the order\', ""Comment 10: so no need to resend business partner?\'"", ""Comment 11: \'another example for location Veghel: SO000038550 is also not in VC module"", ""Comment 12: seems the same reason!afbeelding-1!\'"", \'Comment 13: \\\'Another one for location Andel: Target business partner address is linked to correct business partner and address is the current address. But again in DHP the order is not synced to VC module: An error occurred while saving the entity changes. See the inner exception for details. -> The INSERT statement conflicted with the FOREIGN KEY constraint ""FK_Orders_ContactDatas_MainBusinessPartnerId_MainBusinessPartnerContactDataId"". The conflict occurred in database ""DHPlantVCBusinessLogicMain""\', \'Comment 14: table ""dbo.ContactDatas"".The statement has been terminated.!afbeelding-2!\\\'\', \'Comment 15: ""Hi Thomas,Yes\', ""Comment 16: regarding\'SO000040537\' you are right"", \'Comment 17: my mistake. The issue is with main partner and probably payer as they are the same? In red I have marked addresses. As you can see from the first query\', \'Comment 18: Main has address id which is assigned in addresses table to Target.!image-2022-12-20-07-20-25-203.png!""\', \'Comment 19: ""Order\\\'SO000038550\\\' - address assigned to MAin and Payer seems to be incorrect!image-2022-12-20-07-40-27-326.png!""\', ""Comment 20: \'Can you please provide me with impacted SO for Andel? :)Regards\'"", \'Comment 21: ""Hi aleksandra\', \'Comment 22: yes adress for payer and main is incorrect: This is the case for every Sales order\', \'Comment 23: as from ERP only one address is send. This address is duplicated to all business partner fields. If you check others\', \'Comment 24: with no problems the situation will be the same. So in my opinion\', \'Comment 25: this couldn\\\'t be the reason the order is not accepted in VC module in DHP?""\', ""Comment 26: \'SO for Andel = SO000032891\'"", ""Comment 27: \'Als for Andel: SO000041124 is an example of a sales order where combination of main business partner and address is not correct: It is accepted by VC module in DHP\'"", ""Comment 28: \'ForSO000032891 Main and Payer have assigned address from Target!image-2022-12-20-13-13-10-242.png!!image-2022-12-20-13-13-10-242!\'"", ""Comment 29: \'RegardingSO000041124Generaly"", ""Comment 30: VC module validates if address is correct for specific Business Partner. That is why Orders do not drop to VC in DHP. Why this specific one dropped? I will have a look and investiagte. Let you know as soon as possible\'"", \'Comment 31: ""there are plenty of orders with different main and target BP\\\'s: As only the TargetBP address is send with the order\', \'Comment 32: there are always mismatches: So apperently it isn\\\'t a problem: Only a few fail and dont show up in VC module""\', ""Comment 33: \'SO000041124!image-2022-12-20-13-34-23-134.png!!image-2022-12-20-13-40-50-630.png!!image-2022-12-20-13-40-50-630!\'"", ""Comment 34: \'!image-2022-12-20-14-23-35-860.png!\'"", ""Comment 35: \'[~maciej.dobrzanski@kotrak.com]zwracam honor"", ""Comment 36: w plancie są poprawne informacje :)\'"", ""Comment 37: \'Hi Thomas,Sorry for my delay. RegardingSO000041124"", ""Comment 38: it has correct data in DHP (please see screenshot from DHP and screenshot from db). We think that first data on SO was correct that is why it dropped to DHP and after that data on SO has been changed in ERP system and synced to DHCRegards!image-2022-12-21-13-41-43-807.png!!image-2022-12-21-13-43-48-504.png!\'"", ""Comment 39: \'Hi Aleksandra"", ""Comment 40: If you check an order send today you will find the same situation: I can give you several examples. This cannot be the reason in my opinion\'"", ""Comment 41: \'Generalnie data commita z modify date w DHP jest spójna!image-2022-12-22-07-38-19-301.png!!image-2022-12-22-07-39-27-292.png!\'"", ""Comment 42: \'Wysłałam to zamówienie z OrderExportInfoes"", \'Comment 43: w eventach:{code:java}{""Id"":{""Id"":""109a4905-97aa-4921-b168-3f659df5a74b""},""MainBusinessPartnerId"":{""Id"":""fbea6d3f-77a9-43de-a1c9-1efa9c3a6b64""},""MainBusinessPartnerContactDataId"":2,""TargetBusinessPartnerId"":{""Id"":""450129fa-d186-4219-b3aa-290934bc217d""},""TargetBusinessPartnerContactDataId"":2,""FinalBusinessPartnerId"":null,""FinalBusinessPartnerContactDataId"":null,""DocumentNumber"":{""Number"":7783,""Day"":0,""Month"":12,""Year"":2022,""Series"":"""",""Prefix"":""SO""},""ForeignDocumentNumber"":""SO000041124"",""IssueDate"":""2022-12-19T00:00:00"",""ValidityDate"":""2022-12-22T01:00:00"",""RealisationDate"":""2022-12-22T01:00:00"",""OrderType"":1,""OrderStatus"":30,""Description"":""Hygienemaatregelen in acht nem\', \'Comment 44: en\', \'Comment 45: overall aan               \', \'Comment 46: Stofzak gebruiken! Ontluchings\', \'Comment 47: buizen zitten om de hoek. do ochtend lossen"",""OrderElementEvents"":[{""ItemId"":{""Id"":""6ebe0f95-d93e-439c-9523-fa7437bbdfad""},""Quantity"":{""Unit"":""kg"",""Value"":3000.000000},""RealisedQuantity"":{""Unit"":""kg"",""Value"":0.000000},""Description"":""007025 SPEEN OPTIMAAL KR""},{""ItemId"":{""Id"":""8561fb24-2ab6-4ebf-b95d-882fe4e8313a""},""Quantity"":{""Unit"":""kg"",""Value"":6000.000000},""RealisedQuantity"":{""Unit"":""kg"",""Value"":0.000000},""Description"":""008851 BIG VERHAGEN VETHUIZEN""}]}{code}EventType:{code:java}Plant.VC.BusinessLogic.DomainAbstractions.Orders.OrderChangedEvent{code}\\\'\', ""Comment 48: \'Errory tylko dla VT:!image-2022-12-23-13-38-32-651.png!!image-2022-12-23-13-38-57-691.png!\'"", ""Comment 49: \'!image-2022-12-23-13-43-58-091.png!!image-2022-12-23-13-43-23-795.png!\'"", ""Comment 50: \'Dear Thomas,We have verified logs and we do not have exact information if the address on OrderSO000041124 has been changed in ERP system after it arrived to DHC. What is more"", \'Comment 51: in this task we are focused on unblocking the process.Please\', ""Comment 52: also let us know if problem ith address wil be solved on your side.Regards\'"", ""Comment 53: \'Dear Thomas,Is there anything else we can do for you due to this task? Or can we close it?Regards\'"", ""Comment 54: \'Dear Thomas,Is there anything else we can do for you due to this task? Or can we close it?Regards\'"", ""Comment 55: \'please close this task\'"", ""Comment 56: \'Thank you.Regards\']""]\nRelated Issues:\n[\'DGS-8094\', \'DGS-7968\']\n\n### End'}"
927,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8104\n\n### Instruction:\nplease can you link these plrs they are generated as job orders but appear as if they have not. \r\n\r\nalso could you please share the steps on how the linking is done.\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'!image-2022-12-20-11-11-28-550.png!!image-2022-12-20-11-11-42-165.png!\'"", ""Comment 4: \'!image-2022-12-20-12-10-29-102.png!\'"", ""Comment 5: \'Hi,For the list below all PLRs had documnets JO"", ""Comment 6: IR+ and IR- in ERP so I have mapped them under db in DHC!image-2022-12-20-13-43-38-037.png!Regards\'"", ""Comment 7: \'Hello"", ""Comment 8: please assist with these as well!image-1!\'"", ""Comment 9: \'Hello,Done . Please"", ""Comment 10: verify\'"", ""Comment 11: \'Hello"", ""Comment 12: all documents are linked. thank you \']""]\nRelated Issues:\n[]\n\n### End'}"
928,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8103\n\n### Instruction:\nHi Ewa,\r\n\r\nWe got this problem.\r\n\r\nWe can’t move the feed from round 1 to round 2. Why not?\r\n\r\nMet vriendelijke groeten,\r\n\r\nBessel van den Broek\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", \'Comment 2: ""Feed sale document for Round005138/0001/0002 wasn\\\'t created before. We created yesterday feed sale document FE-P/0017 for this round.Now it should be possible to move feed to this round.Plase verify and confirm that is ok.""\', ""Comment 3: \'Dodane do listy z podsumowaniem wysłanej do klienta.\'"", \'Comment 4: ""[~bbroek@deheus.com]could you check?I think it\\\'s done but could we close the task?""\', ""Comment 5: \'Confirmed that can be closed.\']""]\nRelated Issues:\n[]\n\n### End'}"
929,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8102\n\n### Instruction:\nFor some RM we see that stock is reserved. However, the Lot reports that are shown in Reservation are already confirmed.\r\nExample: Andel, RM 0294, serial 0144 shows > 10 reservations on Lot reports from October. E.g. 0051071022003. These are already confirmed - we do not expect that stock is reserved for these Lot reports anymore.\r\nIn the Lot report I do see that for item 0294 stock was taken from serial 0144. So, perhaps the reservation was not confirmed?\r\n\r\nSame may have happened for other RM / other plants?\r\n\r\nCan you please check why the stock is reserved / how it can be confirmed or released? \r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!!image-1!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 3: ""{code:java}/****** Script for SelectTopNRows command from SSMS  ******/SELECT distinct s.[SourceDocumentNumber],p.ProductionLotStatus  FROM [DHPlantStockBusinessLogicMain].[dbo].[StockUnitReservations]  s   inner join [DHPlantStockBusinessLogicMain].[dbo].[StockUnits] su on su.Id=s.Id  left join [dbo].[ProductionLots] p on s.SourceDocumentNumber=p.LotNumber  where   --s.Id in (select id  FROM [DHPlantStockBusinessLogicMain].[dbo].[StockUnits]  --where Barcode like \\\'OB-%\\\') and   --s.SourceDocumentNumber like \\\'005%\\\' and   p.ProductionLotStatus=4{code} !screenshot-1! jest takich 23{code:java}declare @barcode nvarchar(max) = \\\'5-S00003\\\'select u.QuantityValue AS \\\'Wms Qty\\\'\', \'Comment 4:  s.Quantity\', \'Comment 5: s.QuantityOnHand\', \'Comment 6: sum(sr.QuantityValue),s.Quantity - s.QuantityOnHand as difffrom dbo.StockUnits sleft join DHPlantWmsBusinessLogicMain.dbo.Unitloads u on u.id = s.unitloadidleft join dbo.StockUnitReservations sr on sr.Id = s.Idwhere s.Barcode = @barcodegroup by u.QuantityValue\', \'Comment 7: s.Quantity\', ""Comment 8: s.QuantityOnHand--delete sr--from dbo.StockUnits s--inner join dbo.StockUnitReservations sr on sr.Id = s.Id--where s.Barcode = @barcode--update dbo.StockUNITS--SET QuantityOnhand = Quantity--where barcode = @barcodeselect u.QuantityValue AS \'Wms Qty\'"", \'Comment 9:  s.Quantity\', \'Comment 10: s.QuantityOnHand\', \'Comment 11: sum(sr.QuantityValue),s.Quantity - s.QuantityOnHand as difffrom dbo.StockUnits sleft join DHPlantWmsBusinessLogicMain.dbo.Unitloads u on u.id = s.unitloadidleft join dbo.StockUnitReservations sr on sr.Id = s.Idwhere s.Barcode = @barcodegroup by u.QuantityValue\', \'Comment 12: s.Quantity\', \'Comment 13: s.QuantityOnHand{code}""\', \'Comment 14: ""I corrected the data for plrs from the list below:|51071022003||51071022004||51071022005||51071022006||51071022007||51071022008||51071022009||51071022010||51071022011||51071022019||51071022020||51071022021||51071022023||51071022024||51071022025||51071022026||51071022028||51071022030||51071022032||51071022033||51081022002||51081022008||51241022018|Please verify for this plant.We\\\'ll check the other plants after your feedback.As for the analysis of the cause of the RCA will be needed - please let me know whether to do it.""\', ""Comment 15: \'RCA was created for cause analysis DGS-8168.\'"", ""Comment 16: \'RCA was created for cause analysis DGS-8168.This issue has been closed.\']""]\nRelated Issues:\n[\'DGS-8087\', \'DGS-8168\']\n\n### End'}"
930,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8101\n\n### Instruction:\nVT \'s are not going from DHXC to CDN\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are closing this task as it is duplicate to (DGS-8099).Please,follow above task.Regards\'"", ""Comment 3: \'What was the reason we had to open an incedent.I did this and now it is closed.!image-1!\'"", ""Comment 4: \'The type was changed in an earlier SR task dgs8099.There was no need to make a new one.\']""]\nRelated Issues:\n[\'DGS-8099\']\n\n### End'}"
931,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8100\n\n### Instruction:\nDzień dobry,\r\n \r\nproszę o sprawdzenie i wyeliminowanie błędu jaki pojawia się podczas dodawania nowej struktury podległościowej w pionie sprzedaży pozostałych Gatunków (komunikat błędu w załączniku).\r\n\r\nProblem taki nie występuje w pionie operacyjnym Biuro Obsługi Klienta. \r\n\n\n### Response:\n[""Comment 1: [\'!obraz!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Any news about issue?\'"", ""Comment 4: \'We are analysis issue\'"", ""Comment 5: \'Reason are different codes in Optima and XL.You can make full synchronizationa forom XL configuration (please firstly make this operation on test database)orYou can change names in XL in this window in that way they will be the same as they are in Optima and save. This albo should resolve issue. I checked andsubordinate structure is not using on any posting scheme"", ""Comment 6: all relations in standard database tabels are based on ID not on code.Before you make changes (manually or using synchronisation) you should check if you have any addins baased onsubordinate structure and using Code against ID.!image-2022-12-21-07-36-16-645.png!\'"", ""Comment 7: \'Po zmianie ręcznej w CDN można podłączać podległe zespoły w Optimie"", \'Comment 8: problem jest natomiast gdy zostanie utworzony nowy węzeł podległy\', ""Comment 9: nie ma możliwości utworzenia pod nim kolejnego ponieważ w strukturze podległościowej w CDN nie istnieje taki węzeł. Jak ma zostać to rozwiązane? Czy ma zostać taki węzeł utworzony ręcznie CDN? Czy ma zostać przeprowadzona synchronizacja przy każdorazowym utworzeniu węzła nadrzędnego?Na serwerze testowym po utworzeniu węzła głównego pojawia się w CDN testowym natomiast Makroregionu (węzła poniżej) po synchronizacji nie przechodzi do CDN.  \'"", ""Comment 10: \'*XL/943340**problem z synchronizacją między XL a Optimą*.Konsultacje z comarchem. Są zduplikowane dane w bazach. Comarch ma podesłać skrypty do rozwiązania problemu.\'"", \'Comment 11: ""There are some duplicated data between XL and Optima databases!image-2022-12-23-16-29-26-392.png!I\\\'m consulting solution for that witherp system manufacturer.I\\\'ll let you know as soon as possible on next steps.""\', ""Comment 12: \'Any news ??\'"", ""Comment 13: \'Temat był już analizowany w ramach task DGS-7400,Po przekazaniu pojawiających się komunikatów producent sugerował iż problem może wynikać z błędnego hasła dla cdndts"", \'Comment 14: co w Państwa opinii zostało wykluczone.Po wykonaniu synchronizacji w ramach baz testowych problem przy edycji atrybutów nie występował. Resynchronizacja była zalecana w ramach środowiska produkcyjnego\', \'Comment 15: lecz do dnia dzisiejszego nie ustalono terminu kiedy można ją wykonać.Na chwilę obecną zalecamy by w pierwszej kolejności ponownie wykonać synchronizację w ramach świeżych baz testowych (zarówno XL jak i Optimy) zweryfikować czy prawidłowo synchronizują się elementy struktury podległościowej\', \'Comment 16: pracowniczej i atrybutów a także czy miedzy systemami prawidłowo przekazywane są listy płac. Dopiero po potwierdzeniu prawidłowości tych procesów w ramach środowiska testowego zalecamy wykonanie resynchronizacji w ramach baz produkcyjnych.-----The topic has already been analyzed as part of task DGS-7400,We have sent error messages to producer\', \'Comment 17: the Comarch suggested that the problem may be due to the wrong password for cdndts\', \'Comment 18: what\', \'Comment 19: in your opinion\', \'Comment 20: should be excluded.After performing the synchronization within the test databases\', \'Comment 21: the problem with editing the attributes did not occur. Resynchronization was recommended in the production environment\', \'Comment 22: but we still did not receive information if and when should it be done on our or your side.At the moment\', \'Comment 23: we recommend that you first should perform the synchronization again within the fresh test databases (both XL and Optima) to verify whether the elements of the subordinate structure\', \'Comment 24: employee structure and attributes are synchronized correctly\', \'Comment 25: and whether payrolls are correctly transferred between the systems. Only after confirming the correctness of these processes within the test environment\', ""Comment 26: we recommend performing resynchronization within the production databases.\'"", ""Comment 27: \'Dzień dobry"", \'Comment 28: na obecnych bazach testowych problem z synchronizacją nie występuje\', \'Comment 29: nie były odświeżane bazy\', \'Comment 30: cdndts jest poprawny bez tego nie pobierałyby się listy płac\', ""Comment 31: a pobierają się prawidłowo. Proszę  o dalszą analizę problemu. \'"", ""Comment 32: \'Dzień dobryna testach nie było problemu po wykonaniu ponownej synchronizacji. Jeśli wykonują Państwo kopie zarówno optimy jak i XL do zintegrowania tych dwóch testowych środowisk niezbędna jest ponowna synchronizacja. Ze co było już przez nas zalecane kilka miesięcy temu. Środowiska testowe były integrowane już jakiś czas temu więc najlepszym rozwiązaniem w zaistniałej sytuacji będzie utworzenie nowych środowisk testowych i ich ponowna synchronizacja"", ""Comment 33: jeśli proces synchronizacji przebiegnie bez błędów a opisane problemy w taks {color:#172b4d}DGS-8100 i {color}{color:#172b4d}DGS-7400 nie będą występowały proponujemy wykonanie synchronizacji na środowisku produkcyjnym{color}\'"", ""Comment 34: \'Po odświeżeniu baz na tescie"", \'Comment 35: podczas wykonywania synchronizacji\', ""Comment 36: bład aktualizacji struktury atrybutów klas nie występuje:!image!\'"", \'Comment 37: \\\'Ponadto po wykonaniu synchronizacji na teście utworzone w Optimie Makroregiony w ""Pion Sprzedaży POZ.GAT."" nie pojawiły sie w CDNXL (mimo że etap synchronizacji struktury podległościowej nie zgłosił błędów).Raport z synchronizacji w załaczniku.[^Raport z Synchronizacja struktury organizacyjnej.7z] _(121 kB)_\\\'\', ""Comment 38: \'Proszę o wskazanie lokalizacji środowisk testowych w celu weryfikacji\'"", ""Comment 39: \'Środowiska sa te same co dotychczas:BazySQL05-20\\\\\\\\cdnxl_deheus (XL)sqL05-20\\\\\\\\cdn_DEHEUS (Optima)Optima na DEV-TS02-20"", ""Comment 40: podobnie XL (baza TEST_SQL5_XLDH).\'"", ""Comment 41: \'Trwa weryfikacja problemu: *XL/944430*\'"", ""Comment 42: \'Mamy jakieś wieści ?.Struktura musi wejść w życie 1-go stycznia a Kadry na chwilę obecna nie sa w stanie w zasadzie nic zrobić.\'"", ""Comment 43: \'Na razie temat jest dalej weryfikowany przez producenta. Jako obejście możemy zaproponować wprowadzanie tej struktury od strony XL"", ""Comment 44: wówczas synchronizacja działa poprawnie.\'"", ""Comment 45: \'Jesteśmy świadomi obejścia ale czy takie rozwiazanie nie wygeneruje problemów dalej"", ""Comment 46: gdy synchronizacja zacznie dzialać ?\'"", ""Comment 47: \'Jak tylko otrzymam informację od producenta niezwłocznie ją Państwu przekażę\'"", ""Comment 48: \'Dalsza weryfikacja zgłoszenia wykazała iż na Państwa bazie brakuje standardowych procedur"", \'Comment 49: zauważono brak procedury: ZnajdzDzialStrPodleglosciowej\', \'Comment 50: mimo uzupełnienia jej w ramach środowiska testowego błąd nadal występował\', ""Comment 51: wymagana jest w tym temacie dalsza weryfikacja. Trwają prace związane z dalszą analizą przyczyny problemu i braków na Państwa bazie\'"", ""Comment 52: \'Od producenta na chwilę obecną nie otrzymaliśmy dalszych wytycznych\'"", ""Comment 53: \'Czy mamy jakieś nowe wieści ?Temat jest naprawdę pilny.\'"", ""Comment 54: \'Cały czas jesteśmy na etapie weryfikacji.Proszę jeszcze o informację czy ta struktura jest wykorzystywana w XL?Bo jeśli nie to istnieje możliwość wyłączenia synchronizacji w tym zakresie przez zaznaczenie w XL parametru:!image-2023-01-02-14-08-00-177.png!wówczas od strony optimy będziemy mieć możliwość wprowadzania danych bez komunikatu o braku synchronizacji.\'"", ""Comment 55: \'Tak jest wykorzystywana.Ponadto przy właczonej blokadzie wyszarzy sie opcja do zapisów z Aplikacji Comarch HRM i zaczna sie problemy z E-Pracownikiem.!image-1!\'"", ""Comment 56: \'Udało się rozwiązać przyczynę problemu. Dodano do bazy brakująca procedurę i nadano jej odpowiednie uprawnienia.Proszę o weryfikację. Jeśli jakiś gałęzi brakuje w XL proszę je dodać przez edycję tych pozycji w Optimie (np. przez edycję nazwy - dodanie kropki/ zapisanie zmian/ usunięcie kropki)\'"", ""Comment 57: \'Wstępnie wygląda obiecująco.Do końca dnia będę miał potwierdzenie z kadr.\'"", ""Comment 58: \'Czy zgłoszenie można uznać za zakończone?\'"", ""Comment 59: \'Tak"", ""Comment 60: możemy.\']""]\nRelated Issues:\n[\'DGS-7400\']\n\n### End'}"
932,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8099\n\n### Instruction:\nVT \'s are not going from DHXC to CDN \r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Hi,This should be an incident. Please"", ""Comment 4: approve changing task type.Regards\'"", ""Comment 5: \'incident has be created Close this ticket\'"", ""Comment 6: \'Further analysis will be here.\'"", ""Comment 7: \'I was asked to open a incident what i did.Instead off closing this ticket you did close the the opend incident\'"", \'Comment 8: ""VT doesn\\\'t run through and no message has been shown.!image-1!""\', ""Comment 9: \'!image-2!\'"", \'Comment 10: ""Documents for VT\\\'s have been generated.""\', ""Comment 11: \'What did course the problem\'"", ""Comment 12: \'This issue is related with DGS-7827,after realization this task( DGS-7827) the problem should no longer occur.\'"", ""Comment 13: \'The mentioned problem are solved but a lot new prblems did occur.!image-3!\'"", ""Comment 14: \'Are LOT report the problem\'"", ""Comment 15: \'The second line gives problems.It is not know what exacly the problem isOther line have a lack off product\'"", ""Comment 16: \'Yes the reason is despite generating JO no IR- and IR+ in XL.Should we verify it?\'"", ""Comment 17: \'Can you correct IR- and IR+ ?So far i know you do this often.\'"", \'Comment 18: ""{code:java}  select *  FROM [Evolution_DHCountry].[dbo].[VehicleTickets]  where DocumentNumber like \\\'5767/12/2022%\\\'  or  DocumentNumber like \\\'5774/12/2022%\\\'or  DocumentNumber like \\\'5630/12/2022%\\\'  select DeliveryId,*   FROM [Evolution_DHCountry].[dbo].[VehicleTicketElements]  where VehicleTicketId in(\\\'B022E818-CE0E-41ED-8284-6251EE369B6F\\\',\\\'B5581C27-E4BC-4FAB-9E7F-71D30F2AFDC0\\\',\\\'AD02A43A-1F11-4441-832C-E8EA19FE8F8F\\\')SELECT     *  FROM [DhcErpPlugin].[dbo].[DeliverySyncs]   where DhcId in(\\\'DA4DD13D-B138-4857-922A-C26028D64A84\\\',\\\'2F76562D-F12A-4080-99C1-BB8657E931FD\\\',\\\'12F57728-881F-473F-8DCD-81911C8126F5\\\',\\\'388FF789-FF27-470D-A439-7BFE2DD6938E\\\',\\\'EF9CB350-A50F-49A8-85F5-B5EEC2B58D74\\\',\\\'4723C65A-A90E-41D0-937D-53B60039D894\\\'  ){code}""\', \'Comment 19: ""Hello\', \'Comment 20: for December 2022 there are three VT\\\'s on the list to generate.Out of resources due to invalid IR+ warehouse - should be on DCVE.Items:0113500716-B75000707-B1000IR+: !screenshot-1!  !screenshot-2!  !screenshot-3!  !screenshot-4! ""\', \'Comment 21: "" !screenshot-5! PORI-31/10/2022/VIMPPORI-37/10/2022/VIMPPORI-5/12/2022/VIMPPORI-65/12/2022/VIMPna styczeń: !screenshot-6! {code:java}  select  deliveryid,*  FROM [Evolution_DHCountry].[dbo].[VehicleTicketElements] t  where VehicleTicketId in(\\\'B2A3F2EC-83E3-4A8B-961F-97B8D27B2AA2\\\')  SELECT     *  FROM [DhcErpPlugin].[dbo].[DeliverySyncs]   where DhcId in(\\\'3E90283F-4F03-4375-AA8E-962FB8A57BE7\\\',\\\'E53E4B4E-A527-401C-A133-01530CAF381B\\\',\\\'29A47317-9828-4F21-A856-1FED9AEA1343\\\',\\\'D010E1FB-3ED5-4C6A-A2F5-639F808A448C\\\',\\\'A53FCCF1-89DB-4C49-AEBD-E6160D62DF91\\\'  )SELECT *select cdn.nazwaobiektu (Dst_TrnTyp\', \'Comment 22: Dst_TrnNumer,1,2)  FROM [CDNXL_DHNL_PROD].[CDN].[Dostawy]  where Dst_GIDNumer IN(42686\\\\t,45255\\\\t,44566\\\\t,42719){code}""\', ""Comment 23: \'Example : 01135R+ and R- are present.What is wrong?!image-4!!image-5!!image-6!!image-7!!image-8!!image-9!!image-10!\'"", ""Comment 24: \'VT - quantity!image-2023-01-25-08-29-32-430.png!Stocks in XL:!image-2023-01-25-08-29-51-102.png!but IR+ has been created for incorrect warehouse!image-2023-01-25-08-30-24-135.png!\'"", ""Comment 25: \'Ticket can be closed\']""]\nRelated Issues:\n[\'DGS-7827\', \'DGS-8101\']\n\n### End'}"
933,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8098\n\n### Instruction:\nThere seems to be a problem starting today regarding the feed sale document: feed lines move but also stay on the previous round? This withelds us from finishing a round.\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Hi Steffen"", ""Comment 4: please provide all IDs of the Feed Sales where you noticed this problem.\'"", ""Comment 5: \'In this case FE-B/0293 (ID 60043) and FE-B/0484 (ID 78139). Koen had the same problem with FE-B/0476 (ID 77545) and FE-B/0347 (ID 64455). These were the first we did so I think it counts for every feed sale.\'"", \'Comment 6: ""For Feed Sale FE-B/0153 (ID 31246) I don\\\'t get this problem. I don\\\'t know if it has anything to do with the updates you just did? However for the feed sales below the lines are still on both rounds.!image-1!""\', ""Comment 7: \'linked toDGS-8097\'"", ""Comment 8: \'Hi,I think that do it again after yesterday changes it should be good.Is it right now everything correct and we can close task?\'"", ""Comment 9: \'Hello Damian,I think it is all right indeed now. Yesterday morning"", \'Comment 10: we stopped after the 2 examples\', ""Comment 11: and these I could successfully move yesterday evening.\'"", ""Comment 12: \'Ok"", ""Comment 13: great.So I close the task. In case of any issues please let us know and report.\']""]\nRelated Issues:\n[]\n\n### End'}"
934,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8097\n\n### Instruction:\nI set 4 feed linens to another round B004145/0035/0003 to B004145/0035/0003 with move and Tick\r\nThe weight is now on both rounds\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'linked toDGS-8098\'"", ""Comment 4: \'Hi,\\\\r\\\\rI think that do it again after yesterday changes it should be good.\\\\r\\\\rIs it right now everything correct and we can close task?\'"", ""Comment 5: \'Dodane do listy z podsumowaniem tasków wysłanej do klienta.\'"", ""Comment 6: \'[~khuibers@deheus.com]could you check and verify?Could we close the task?\'"", ""Comment 7: \'Yes\']""]\nRelated Issues:\n[]\n\n### End'}"
935,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8096\n\n### Instruction:\nI accidently closed the round of the wrong customer. Could you please re-open round B002150/0187/0002 (ID 61574)? Thank you!\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 2: ""Round is reopened now. It\\\'s in inbox Brigitte Danneel as it was before""]\']\nRelated Issues:\n[]\n\n### End'}"
936,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8095\n\n### Instruction:\nPlease set ID-77165 back to entry\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Duplicated - DGS-8092\']""]\nRelated Issues:\n[]\n\n### End'}"
937,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8094\n\n### Instruction:\nThe order SO000040557 is not in the VC module of DHP, but is send to the PCS: The problem is already known, as a solution was advised to resend BP for the order. In this case I resend BP 100064 and BP 000168. But this doesn\'t bring a solution. Please check this example and advice what to do\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Error message dla wskazanego zamówienia:!image-2022-12-19-09-15-00-714.png!\'"", ""Comment 3: \'Dear Thomas,Please"", ""Comment 4: verify if address and Customers are correct:!image-2022-12-19-09-55-02-508.png!Under DB:!image-2022-12-19-09-56-50-536.png!Regards\'"", ""Comment 5: \'Oke"", ""Comment 6: so to understand: The address send with the order is not the current adress (is current) registered in DHC\'"", ""Comment 7: \'I think this screenshot would be clearer:Main BusinessPartnerID = PayerBusinessPartnerID =BB3FECBE-0583-4256-A7E5-982A1521B8ABTargetBusinessPartnerID =0FAD898B-A546-4D96-A2F4-B0C6BF1FFDEEbut target has the same address as Main and Payer but if you have a look at 3rd query"", ""Comment 8: only Target has correct address / address ID!image-2022-12-19-13-09-18-421.png!\'"", \'Comment 9: ""Oke\', \'Comment 10: I checked and changed so that the address is set to is current: Then I resend the order\', ""Comment 11:  but in DHP it\'s still not accepted bij VC module"", \'Comment 12: please check!afbeelding!""\', ""Comment 13: \'Ticket can be closed"", ""Comment 14: is solved now\'"", ""Comment 15: \'It is in DHP in VC now:!image-2022-12-19-14-08-40-345.png!\'"", ""Comment 16: \'Regards :)\'"", \'Comment 17: ""Sorry\', \'Comment 18: I haven\\\'t noticed your information that task can be closed.Thank you for your information.Regards""\', ""Comment 19: \'Can you check another example?\'"", ""Comment 20: \'Sure,I have received new task. So I will proceed under DGS-8105Regards\']""]\nRelated Issues:\n[\'DGS-8105\']\n\n### End'}"
938,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8093\n\n### Instruction:\non Dec 16/2022 We had a problem Verifying( Accept & Confirm)  Production lot reports on DHP . and was solved @adrina Kozak . but this particular PLRs couldn`t leave from DHC and reach ERP ; \r\nError says PLR skipped (NULL)  \r\n26 PLRs not yet Generated ! our finance Dep can`t do weekly report for this sake ; \r\nThanks in Advance  \r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Thanks very Much  Much Appreciated and I be here to contact and help as needed ;\'"", ""Comment 4: \'Technology 7700-B25 ver 439 is not generated. Please"", \'Comment 5: generate technology.!image-2022-12-19-11-57-08-777.png!For two others technologies\', \'Comment 6: I have resent Technology!image-2022-12-19-12-01-18-810.png!!image-2022-12-19-12-00-33-662.png!PLR should generate documents in a while\', \'Comment 7: if not\', ""Comment 8: please generate documents again:!image-2022-12-19-12-09-25-098.png!\'"", ""Comment 9: \'Please"", ""Comment 10: let us know if you need any further assistance.Regards\'"", ""Comment 11: \'Dear  I did generated Technology 7700-B25 Ver 439 ; it is generated I will wait a little and try Generate the PLR ;  Will tell ya the Updates and results  Thanks Again ;  !image001!     *From:* Aleksandra Przybyłek (Jira) <jira@kotrak.com>   *Sent:* Monday"", \'Comment 12: December 19\', ""Comment 13: 2022 14:11  *To:* Gemechis Terefe <gemechis@alemakoudijs.com>  *Subject:* DGS-8093 Production lot reports Re-submitted Dec 16/2022 Didn`t leave DHC or Reached to ERP . Not yet Generated .   !image002!!image003!!image004!!image005!\'"", ""Comment 14: \'Waiting for your feedback then.Regards\'"", ""Comment 15: \'Hey Dear  I did generated the Two 7700-B25 Ver 439 And 6630-B50-C   And also 8 PLRS are generated already  Will tell you the final Result ASAP Thanks Again       *From:* Gemechis Terefe !image001!!dhc 1.PNG|thumbnail!!dhc 2.PNG|thumbnail!!image002!!image003!!image004!!image005!\'"", ""Comment 16: \'Sure. Waiting for your feedback then.Regards\'"", ""Comment 17: \'Hello Dear  From 26 PLR only 9 is Generated and All 7700 layer phase one (17) are not yet generated .  I did Generate the Technology for 7700 and they are all generated .  But this one still not yet Generated Documents  !image001! !image002! !image003!   !image004! All this layer Super phase 1 are not yet Generated .  I tried to Generate the Documents many times "", \'Comment 18: We also did added like Limestone \', \'Comment 19: FulFat soya and Corn white …  But still I couldn`t Generate this documents from DHC  Hope to Hear from you .  Thanks  *From:* Aleksandra Przybyłek (Jira) <jira@kotrak.com>   *Sent:* Monday\', \'Comment 20: December 19\', ""Comment 21: 2022 15:50  *To:* Gemechis Terefe <gemechis@alemakoudijs.com>  *Subject:* DGS-8093 Production lot reports Re-submitted Dec 16/2022 Didn`t leave DHC or Reached to ERP . Not yet Generated .   !image001-1!!image002-1!!image003-1!!image004-1!\'"", ""Comment 22: \'Hi,PLRs with error message that technology is inactive have been generated / processed. There are some left but they are PLRs"", ""Comment 23: where quantity on VT was missing. This is to verify on your side.Reagrds\'"", ""Comment 24: \'Hello Dear  Problem Solved .Now all PLRS are Generated !  I used to check stalk missing from DHC log files with amount of Kg and inform Departments about it . But now since the Error message is only say PLR skipped (NULL) was hard to tell Missing Quantity . but Told Production and Finance Department to enter Row material and confirm for the for PZ seeing ThePLR. Then after putting Limestone "", \'Comment 25: Lime Fine \', \'Comment 26: Corn White\', ""Comment 27: FulFAT .. they all Generated ;  @Aleksandra Przybyłek Thanks So much for your Time . Thanks Jira service help desk portal.  Much Appreciated \'"", ""Comment 28: \'Thank you for your information :)In taht case"", ""Comment 29: I am closing this task.Regards\'"", ""Comment 30: \'Yes Pls ; You can close it ! Thanks very Much\']""]\nRelated Issues:\n[]\n\n### End'}"
939,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8092\n\n### Instruction:\nPlease set ID 77165 slaughtery report 1124 back to entry\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Hello It´s urgent"", ""Comment 3: we have to pay the customer\'"", \'Comment 4: ""It\\\'s in Entry now""]\']\nRelated Issues:\n[]\n\n### End'}"
940,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8091\n\n### Instruction:\nProszę o zmianę ilości towaru\xa0 do ZS -1025 ( Prochoń Małgorzata)\xa0\xa0z 3,990 na 5,180 i podłączenie 3 komory. Był doładunek i nie został doliczony.\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'!image-2022-12-17-07-01-15-564.png!!image-2022-12-17-07-00-40-077.png!WZ jest już w XL!image-2022-12-17-07-02-09-137.png!\'"", ""Comment 3: \'Please try to make another VT for missing quantity\'"", ""Comment 4: \'He spoke to the manager"", ""Comment 5: it is to be corrected on existing documents.\'"", ""Comment 6: \'Data has been corrected. Please verify\'"", ""Comment 7: \'Still to be improved: VT- 18581 ,załadunek – 39,740i waga wyjazdowa – 39,740 T\'"", ""Comment 8: \'Done. PLease let me know if I can close this ticket?\'"", \'Comment 9: ""It\\\'s ok\', \'Comment 10: please close task.""]\']\nRelated Issues:\n[]\n\n### End'}"
941,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8090\n\n### Instruction:\nThis is to check access to the Jira service Desk. \r\nTest Ticket \r\nMuch appreciated !   \n\n### Response:\n[""Comment 1: [\'Very Helpful !\'"", ""Comment 2: \'Dear Jira Service Desk This was just a test Ticket created to check the Jira portal Ethiopia . Thanks very much for your concern and Much appreciated .   I confirm to close this ticket back now . Thanks Again \'"", ""Comment 3: \'Hi,Thank you for your ticket.Regards\']""]\nRelated Issues:\n[]\n\n### End'}"
942,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8089\n\n### Instruction:\nProszę o przypisane\xa0 na zbiornikach symbole surowców (wytłuszczenie), których nie ma a są niezbędne abym mógł zadozować z nich surowce biorące udział w naważaniu.\r\nMy mamy taką możliwość zmiany, ale pod warunkiem 0 ilości na zbiorniku,\xa0a one są większe od 0 kg.\r\nZb 622004\xa0 2004 -\xa0 0818\xa0\xa0\xa0\xa0\xa0 \r\n622006\xa0 2006 – 21482\xa0\xa0\xa0\xa0\xa0 \r\n622008\xa0 2008\xa0 -\xa0 0641\xa0\xa0\xa0\xa0\xa0 \r\n623011\xa0 3011 -\xa0 0645\xa0\xa0\xa0\xa0\xa0 \r\nTemat pilny z powodu realizacji zam.produkcyjnych .\r\nDo uzupełnienia 4 pola zaznaczone na czerwono.\n\n### Response:\n[""Comment 1: [\'!silosy.bmp|thumbnail!\'"", ""Comment 2: \'Hello"", ""Comment 3: We kindly inform you that wecurrentlyare processing another Priority1 task.We will revert to processing your task as soon as possible.Regards\'"", ""Comment 4: \'Hi,Data has been filled :!image-2022-12-16-23-21-58-856.png!PLease verify and let us know if we can close this issue\'"", ""Comment 5: \'please close task\'"", ""Comment 6: \'[[DHP 2.X] Wizualizacja PCS - Tank data|onenote:https://kotrak.sharepoint.com/sites/erpasysta/Shared%20Documents/Baza%20wiedzy/Baza%20Wiedzy%20-%20ERPSD/Klienci/DEHEUS/DEHEUS%20APPLICATIONS/Polska/Baza%20wiedzy/DHP.one#%5bDHP%202.X%5d%20Wizualizacja%20PCS%20-%20Tank%20data&section-id=\\\\\\\\{F3B54834-6A02-4FD8-B2D4-74ADCAEDC4E9}&page-id=\\\\\\\\{001B9CF9-BE9E-4404-92B2-E01D738A0F63}&end] ([Widok sieci Web|https://kotrak.sharepoint.com/sites/erpasysta/_layouts/OneNote.aspx?id=%2Fsites%2Ferpasysta%2FShared%20Documents%2FBaza%20wiedzy%2FBaza%20Wiedzy%20-%20ERPSD&wd=target%28Klienci%2FDEHEUS%2FDEHEUS%20APPLICATIONS%2FPolska%2FBaza%20wiedzy%2FDHP.one%7CF3B54834-6A02-4FD8-B2D4-74ADCAEDC4E9%2F%5BDHP%202.X%5D%20Wizualizacja%20PCS%20-%20Tank%20data%7C001B9CF9-BE9E-4404-92B2-E01D738A0F63%2F%29])\']""]\nRelated Issues:\n[]\n\n### End'}"
943,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8088\n\n### Instruction:\nNie można aktywować etykiety na towar 915914-w25 1t numer kodu kreskowego etykiety to 27-65JQP.Dostawa z vt-24395.Komunikat na skanerze: „Aktywacja kodu kreskowego przekroczy ilość z dostawy 1t. Operacja została przerwana”\n\n### Response:\n[""Comment 1: [\'Hello"", ""Comment 2: We kindly inform you that wecurrentlyare processing another Priority1 task.We will revert to processing your task as soon as possible.Regards\'"", ""Comment 3: \'Please try now\'"", ""Comment 4: \'please close task\']""]\nRelated Issues:\n[]\n\n### End'}"
944,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8087\n\n### Instruction:\nWe have problem with some items/Unit load with wrong reservation. The productions are closed but they still are reserving some unit load. \r\n\r\nExample production 0881031122029, 0881031122030 and 0881031122038\r\n\r\nCould you check why reservation was not done when productions were closed, check if we have more productions with the same error and fix it?\r\n\r\nIt\'s urgent because system not allow to move or make inventory for unit load with reservation.\r\n\r\nThank you\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 3: \\\'""system not allow to move or make inventory for unit load with reservation."" Can you attach screenshot with error?\\\'\', ""Comment 4: \'Item21808 barcode 88-W0DY0Q!image-1!\'"", ""Comment 5: \'Please verify if problem still occurs for88-W0DY0Q and let me know. If changes helps then we will make the same on other barcodes\'"", \'Comment 6: ""we have the same error.It\\\'s not possible move item.!image-2!!image-3!""\', ""Comment 7: \'Please verify now if problem still occurs for88-W0DY0Q and let me know if I can make the same changes on other barcodes\'"", \'Comment 8: ""Hi MonikaFor 88-W0DY0Q the problem is solved\', \'Comment 9: however we still have problem with a couple of reservations.As you can find by yourself there\\\'s a lot of ULs with reservation for PLRs already confirmed and consumed.You can lower the priority of this task for P2 but we need all UL with already confirmed PLR reserved fixed by monday morning because we\\\'ll have many location stocktakings next week.Thank you very much!image-4!""\', ""Comment 10: \'All barcodes related with productions0881031122029"", ""Comment 11: 0881031122030 and 0881031122038 has been corrected. PLease provide us if you have another lot numbers with this kind of issue.\'"", \'Comment 12: ""HiWe found some barcodes in Stock engine\', \'Comment 13: but I don\\\'t know if this will have some impact on stocktaking routine.We also found new ULs with confirmed PLR. Do we need to raise a new DGS for that?0881031122036088104112200908810411220310881031122026088201112200208810311220400881031122023088103112203508810311220330881011122017088103112203408810311220270881031122037Thank you!image-5!!image-6!!image-7!""\', ""Comment 14: \'poprawa dla PLR:881011122017881031122023881031122026881031122027881031122029881031122030881031122033881031122034881031122035881031122036881031122037881031122038881031122040881041122009881041122031882011122002882260122004\'"", ""Comment 15: \'Reservations have been corrected for PLR from the list:881011122017881031122023881031122026881031122027881031122029881031122030881031122033881031122034881031122035881031122036881031122037881031122038881031122040881041122009881041122031882011122002882260122004Please verify.Please confirm to create an RCA for root cause analysis.\'"", ""Comment 16: \'{code:java}  SELECT  distinct s.[SourceDocumentNumber],p.ProductionLotStatus  FROM [DHPlantStockBusinessLogicMain].[dbo].[StockUnitReservations]  s   inner join [DHPlantStockBusinessLogicMain].[dbo].[StockUnits] su on su.Id=s.Id  inner join [dbo].[ProductionLots] p on s.SourceDocumentNumber=p.LotNumber  where   p.ProductionLotStatus=4{code}\'"", ""Comment 17: \'[[DHP 3.0] Stocktaking - Reserved StockUnits"", ""Comment 18: rezerwacja na stockach|onenote:https://kotrak.sharepoint.com/sites/erpasysta/Shared%20Documents/Baza%20wiedzy/Baza%20Wiedzy%20-%20ERPSD/Klienci/DEHEUS/DEHEUS%20APPLICATIONS/Brazil/Baza%20wiedzy.one#%5bDHP%203.0%5d%20Stocktaking%20-%20Reserved%20StockUnits,%20rezerwacja%20na&section-id=\\\\\\\\{05DF1439-683C-45FE-8260-61E2EC66DC91}&page-id=\\\\\\\\{F85E69B9-BC0D-4FAA-BDC2-3E89CD2E4917}&end] ([Widok sieci Web|https://kotrak.sharepoint.com/sites/erpasysta/_layouts/OneNote.aspx?id=%2Fsites%2Ferpasysta%2FShared%20Documents%2FBaza%20wiedzy%2FBaza%20Wiedzy%20-%20ERPSD&wd=target%28Klienci%2FDEHEUS%2FDEHEUS%20APPLICATIONS%2FBrazil%2FBaza%20wiedzy.one%7C05DF1439-683C-45FE-8260-61E2EC66DC91%2F%5BDHP%203.0%5D%20Stocktaking%20-%20Reserved%20StockUnits%2C%20rezerwacja%20na%7CF85E69B9-BC0D-4FAA-BDC2-3E89CD2E4917%2F%29])\'"", \'Comment 19: ""Hi PiotrThank you for this correction!It\\\'d be nice to now why is happened\', ""Comment 20: however when this happened we had 7.9 version and now we have 8.3Since then we didn\'t experienced this again"", \'Comment 21: maybe it was some error of the version.If you think is a good task\', \'Comment 22: we can create a RCA.Thank you""\', ""Comment 23: \'If the analysis is to be for RCA the verification would be for new cases ( as you mentioned"", ""Comment 24: there were version changes for DHP).\'"", ""Comment 25: \'Po konsultacjach z [~maciej.dobrzanski@kotrak.com]:Wskazane raporty zostały kilkukrotnie potwierdzone (w tym samym czasie)"", \'Comment 26: co mogło spowodować powstanie rezerwacji już po potwierdzeniu PLR. Musimy spróbować zreprodukować możliwość kilkukrotnego\', \'Comment 27: równoległego potwierdzenia PLR\', \'Comment 28: żeby dobrać najkorzystniejsze rozwiązanie problemu. - [~maciej.buchacz@kotrak.com]\', \'Comment 29: [~aleksandra.masternak@kotrak.com]prośba o testy i zreprodukowanie błędu.Proponowane sposoby naprawy: - zablokowanie przycisku na UI po pierwszym kliknięciu\', \'Comment 30: - obsługa potwierdzania PLR w ramach transakcji SQL\', \'Comment 31: - obsługa konkurencyjności dla agregatu PLR\', \'Comment 32: - wprowadzenie statusu ""ConfirmationPending"" dla PLR\', \'Comment 33: - zmiana procesu potwierdzania PLR na zdarzeniowy.Poniżej dodaję zapytania SQL pomocne w analizie problemu.{code:java}SELECT *FROM DHPlantStockBusinessLogicMain.dbo.ProductionLots PJOIN DHPlantStockBusinessLogicMain.dbo.StockUnitReservations R ON P.Id = R.SourceDocumentIdWHERE P.ProductionLotStatus = 4ORDER BY P.StartDate DESC;{code}{code:java}SELECT AggregateId\', \'Comment 34: COUNT(CorrelationId) AS _Count\', ""Comment 35: MAX(Created) AS _DateFROM DHPlantProdBusinessLogicEvents.dbo.ProductionLotsWHERE EventType LIKE \\\\\'%ProductionLotConfirmedEvent\\\\\'GROUP BY AggregateIdHAVING COUNT(CorrelationId) > 1ORDER BY MAX(Created) DESC;{code}{code:java}DECLARE @LotNumber NVARCHAR(100) = \\\\\'0881031122029\\\\\'DECLARE @ProductionId UNIQUEIDENTIFIER = (SELECT Id FROM DHPlantProdBusinessLogicMain.dbo.ProductionLots WHERE LotNumber = @LotNumber)DECLARE @StartDate DATETIME = (SELECT CONVERT(DATE"", ""Comment 36: StartDate) FROM DHPlantProdBusinessLogicMain.dbo.ProductionLots WHERE Id = @ProductionId);WITH Events AS(    SELECT *    FROM DHPlantProdBusinessLogicEvents.dbo.ProductionLots    WHERE AggregateId = @ProductionId    UNION ALL    SELECT *    FROM DHPlantStockBusinessLogicEvents.dbo.StockUnits E    WHERE E.Created > @StartDate        AND Event LIKE (\\\\\'%\\\\\' + @LotNumber + \\\\\'%\\\\\'))SELECT    Created"", \'Comment 37:    CorrelationId\', \'Comment 38:    UserName\', \'Comment 39:    REPLACE(REPLACE(AggregateType\', ""Comment 40: \\\\\'Plant.Prod.BusinessLogic.Domain.ProductionLots.Model.\\\\\'"", ""Comment 41: \\\\\'\\\\\')"", ""Comment 42: \\\\\'Plant.Stock.BusinessLogic.Domain.StockUnits.\\\\\'"", ""Comment 43: \\\\\'\\\\\') AS AggregateType"", \'Comment 44:    AggregateId\', \'Comment 45:    REPLACE(REPLACE(EventType\', ""Comment 46: \\\\\'Plant.Prod.BusinessLogic.DomainAbstractions.ProductionLots.DomainEvents.\\\\\'"", ""Comment 47: \\\\\'\\\\\')"", ""Comment 48: \\\\\'Plant.Stock.BusinessLogic.DomainAbstractions.StockUnits.\\\\\'"", ""Comment 49: \\\\\'\\\\\') AS EventType"", ""Comment 50:    EventFROM Events EORDER BY E.Created;{code}\'"", ""Comment 51: \'Hello"", ""Comment 52: finally RCA was created for cause analysis DGS-8168.\'"", ""Comment 53: \'[~tomasz.nojek@kotrak.com] Nie udało mi się zreprodukować błędu. Gdy próbowałam równolegle potwierdzić ten sam PLR"", ""Comment 54: to jeden z nich się potwierdzał a na drugim pojawiał błąd o złym statusie PLRa. !confirmation! \'"", ""Comment 55: \'Hello,you can close this task"", ""Comment 56: thank you.\'"", ""Comment 57: \'Hi PiotrAs we have this RCA (DGS-8168).You can close this task.Thank you very much\']""]\nRelated Issues:\n[\'DGS-8168\', \'DGS-8102\', \'DGS-8184\', \'DGS-8185\', \'DAP-13157\']\n\n### End'}"
945,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8086\n\n### Instruction:\nDOcuments are not synchroniing into erp, all plrs from yesterday are not showing in erp as job orders\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Wszystkie z czwartku mają taki error:!image-2022-12-19-07-40-07-559.png!\'"", ""Comment 3: \'Timeout pojawiał się od 15 grudnia{code:java}Application: Evolution.ErpIntegrator.PlatformApplication Date: 12/18/2022 7:38:16 AM Id: 129686 Message: An error occurred while executing the command definition. See the inner exception for details. Source: EntityFramework StackTrace: System.Data.Entity.Core.EntityCommandExecutionException: An error occurred while executing the command definition. See the inner exception for details. ---> System.Data.SqlClient.SqlException: Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding. ---> System.ComponentModel.Win32Exception: The wait operation timed out --- End of inner exception stack trace --- at System.Data.SqlClient.SqlConnection.OnError(SqlException exception"", \'Comment 4: Boolean breakConnection\', \'Comment 5: Action`1 wrapCloseInAction) at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception\', \'Comment 6: Boolean breakConnection\', \'Comment 7: Action`1 wrapCloseInAction) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj\', \'Comment 8: Boolean callerHasConnectionLock\', \'Comment 9: Boolean asyncClose) at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior\', \'Comment 10: SqlCommand cmdHandler\', \'Comment 11: SqlDataReader dataStream\', \'Comment 12: BulkCopySimpleResultSet bulkCopyHandler\', \'Comment 13: TdsParserStateObject stateObj\', \'Comment 14: Boolean& dataReady) at System.Data.SqlClient.SqlDataReader.TryConsumeMetaData() at System.Data.SqlClient.SqlDataReader.get_MetaData() at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds\', \'Comment 15: RunBehavior runBehavior\', \'Comment 16: String resetOptionsString\', \'Comment 17: Boolean isInternal\', \'Comment 18: Boolean forDescribeParameterEncryption\', \'Comment 19: Boolean shouldCacheForAlwaysEncrypted) at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior\', \'Comment 20: RunBehavior runBehavior\', \'Comment 21: Boolean returnStream\', \'Comment 22: Boolean async\', \'Comment 23: Int32 timeout\', \'Comment 24: Task& task\', \'Comment 25: Boolean asyncWrite\', \'Comment 26: Boolean inRetry\', \'Comment 27: SqlDataReader ds\', \'Comment 28: Boolean describeParameterEncryptionRequest) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior\', \'Comment 29: RunBehavior runBehavior\', \'Comment 30: Boolean returnStream\', \'Comment 31: String method\', \'Comment 32: TaskCompletionSource`1 completion\', \'Comment 33: Int32 timeout\', \'Comment 34: Task& task\', \'Comment 35: Boolean& usedCache\', \'Comment 36: Boolean asyncWrite\', \'Comment 37: Boolean inRetry) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior\', \'Comment 38: RunBehavior runBehavior\', \'Comment 39: Boolean returnStream\', \'Comment 40: String method) at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior\', \'Comment 41: String method) at System.Data.SqlClient.SqlCommand.ExecuteDbDataReader(CommandBehavior behavior) at System.Data.Common.DbCommand.ExecuteReader(CommandBehavior behavior) at System.Data.Entity.Infrastructure.Interception.DbCommandDispatcher.<Reader>b__c(DbCommand t\', \'Comment 42: DbCommandInterceptionContext`1 c) at System.Data.Entity.Infrastructure.Interception.InternalDispatcher`1.Dispatch[TTarget,TInterceptionContext,TResult](TTarget target\', \'Comment 43: Func`3 operation\', \'Comment 44: TInterceptionContext interceptionContext\', \'Comment 45: Action`3 executing\', \'Comment 46: Action`3 executed) at System.Data.Entity.Infrastructure.Interception.DbCommandDispatcher.Reader(DbCommand command\', \'Comment 47: DbCommandInterceptionContext interceptionContext) at System.Data.Entity.Internal.InterceptableDbCommand.ExecuteDbDataReader(CommandBehavior behavior) at System.Data.Common.DbCommand.ExecuteReader(CommandBehavior behavior) at System.Data.Entity.Core.EntityClient.Internal.EntityCommandDefinition.ExecuteStoreCommands(EntityCommand entityCommand\', \'Comment 48: CommandBehavior behavior) --- End of inner exception stack trace --- at System.Data.Entity.Core.EntityClient.Internal.EntityCommandDefinition.ExecuteStoreCommands(EntityCommand entityCommand\', \'Comment 49: CommandBehavior behavior) at System.Data.Entity.Core.Objects.Internal.ObjectQueryExecutionPlan.Execute[TResultType](ObjectContext context\', \'Comment 50: ObjectParameterCollection parameterValues) at System.Data.Entity.Core.Objects.ObjectQuery`1.<>c__DisplayClass7.<GetResults>b__6() at System.Data.Entity.Core.Objects.ObjectContext.ExecuteInTransaction[T](Func`1 func\', \'Comment 51: IDbExecutionStrategy executionStrategy\', \'Comment 52: Boolean startLocalTransaction\', \'Comment 53: Boolean releaseConnectionOnSuccess) at System.Data.Entity.Core.Objects.ObjectQuery`1.<>c__DisplayClass7.<GetResults>b__5() at System.Data.Entity.SqlServer.DefaultSqlExecutionStrategy.Execute[TResult](Func`1 operation) at System.Data.Entity.Core.Objects.ObjectQuery`1.GetResults(Nullable`1 forMergeOption) at System.Data.Entity.Core.Objects.ObjectQuery`1.<System.Collections.Generic.IEnumerable<T>.GetEnumerator>b__0() at System.Data.Entity.Internal.LazyEnumerator`1.MoveNext() at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection) at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source) at Evolution.ErpIntegrator.DHC.DHC30.Documents.VehicleTickets.VehicleTicketRepository.GetVehicleTickets(Boolean forProcessing\', ""Comment 54: GuidObjectKey id) in C:\\\\\\\\TeamCity\\\\\\\\buildAgent\\\\\\\\work\\\\\\\\57a7e278b67a115c\\\\\\\\Evolution.ErpIntegrator\\\\\\\\Evolution.ErpIntegrator.DHC.DHC30\\\\\\\\Documents\\\\\\\\VehicleTickets\\\\\\\\VehicleTicketRepository.cs:line 275 at Evolution.ErpIntegrator.DHC.DHC30.Documents.VehicleTickets.VehicleTicketRepository.GetVehicleTicketsToSynchronization() in C:\\\\\\\\TeamCity\\\\\\\\buildAgent\\\\\\\\work\\\\\\\\57a7e278b67a115c\\\\\\\\Evolution.ErpIntegrator\\\\\\\\Evolution.ErpIntegrator.DHC.DHC30\\\\\\\\Documents\\\\\\\\VehicleTickets\\\\\\\\VehicleTicketRepository.cs:line 108 at Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor.OnExecute(Object data) at Evolution.ErpIntegrator.IntegrationLibrary.IntegrationTaskBase.Execute(Object data) at Evolution.ErpIntegrator.IntegrationLibrary.Integrator.Execute() at Evolution.ErpIntegrator.PlatformApplication.Application.TimerCallback(Object state){code}\'"", ""Comment 55: \'!image-2022-12-19-08-34-14-112.png!!image-2022-12-19-08-34-48-333.png!\'"", ""Comment 56: \'!image-2022-12-19-08-35-16-048.png!\'"", ""Comment 57: \'Hi,It should be fine now. If missing documents did not generate"", \'Comment 58: please generate them again from application: first VT\', ""Comment 59: then PLRs.!image-2022-12-19-09-08-50-112.png!Regards\'"", ""Comment 60: \'{color:#212121}Okay please close{color} ----\'"", ""Comment 61: \'Thank you\']""]\nRelated Issues:\n[]\n\n### End'}"
946,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8085\n\n### Instruction:\nError id 6111032 start transfer  3\n\n### Response:\n[""Comment 1: [\'Zgłoszenie w trakcie realizacji\'"", ""Comment 2: \'Please check"", ""Comment 3: for p46034 in database was a different item - id 19905.\'"", ""Comment 4: \' !screenshot-1! \'"", ""Comment 5: \'użyta procedura z[[DHP] Problem ze zbiornikiem"", \'Comment 6: ciągłe czyszczenie\', ""Comment 7: jeżdzą w kółko. Incorrect article.|onenote:https://kotrak.sharepoint.com/sites/erpasysta/Shared%20Documents/Baza%20wiedzy/Baza%20Wiedzy%20-%20ERPSD/Klienci/DEHEUS/DEHEUS%20APPLICATIONS/Polska/Baza%20wiedzy/DHP%20Produkcja.one#%5bDHP%5d%20Problem%20ze%20zbiornikiem,%20ci%C4%85g%C5%82e%20czyszczenie,%20je%C5%BCdz%C4%85%20w%20k%C3%B3%C5%82ko&section-id=\\\\\\\\{CC5FB5C6-8E0D-42E5-8319-3DC0E80D8642}&page-id=\\\\\\\\{5BCB8D63-41B2-417C-B3C8-73B535158C20}&end] ([Widok sieci Web|https://kotrak.sharepoint.com/sites/erpasysta/_layouts/OneNote.aspx?id=%2Fsites%2Ferpasysta%2FShared%20Documents%2FBaza%20wiedzy%2FBaza%20Wiedzy%20-%20ERPSD&wd=target%28Klienci%2FDEHEUS%2FDEHEUS%20APPLICATIONS%2FPolska%2FBaza%20wiedzy%2FDHP%20Produkcja.one%7CCC5FB5C6-8E0D-42E5-8319-3DC0E80D8642%2F%5BDHP%5D%20Problem%20ze%20zbiornikiem%2C%20ci%C4%85g%C5%82e%20czyszczenie%2C%20je%C5%BCdz%C4%85%20w%20k%C3%B3%C5%82ko%7C5BCB8D63-41B2-417C-B3C8-73B535158C20%2F%29])\'"", ""Comment 8: \'Confirmed by teams"", ""Comment 9: the taskis closed.\']""]\nRelated Issues:\n[]\n\n### End'}"
947,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8084\n\n### Instruction:\nWe want help in making our 2023 calender year on stock in ERP zero with no roll backs from 2022, so that we can have a true reflection of the stock count from december to be used in january. can you help?\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 2: ""HelloIn ERP it is possible to close period of trade operations\', ""Comment 3: it really means that you can\'t sell anything but also can not make any warehouse movement.So"", \'Comment 4: if you are sure that you want to close 2022 year\', \'Comment 5: you can   close December 2022 and make printout Stock on hand dated on ....- but to close December 2022 you must first close every earlier periods- month by month.Closing periods is possible in module Administrator -> Company -> Periods of trade operations !screenshot-1! ""\', ""Comment 6: \'which means if i close 2022 month by month in 2023 it will be  fresh start?\'"", \'Comment 7: \\\'This means that the system should not allow you to change documents in the old year or issue new ones. I don\\\\\\\'t know what you exactly mean by ""fresh start""?\\\'\', ""Comment 8: \'{color:#212121}Okay i understand. Please close{color} ----\']""]\nRelated Issues:\n[]\n\n### End'}"
948,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8083\n\n### Instruction:\nCodes 6051020 and 6051901 do not have BulkItemId in the database.\r\n\r\nFor this reason scanning in PCS system does not work properly.\r\n\r\nPlease update BulkItemId for those Items.\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'!image-2022-12-19-09-22-55-529.png!\'"", ""Comment 3: \'Pleasecheck the items have been resent.Regards.\'"", ""Comment 4: \'The issue has been completed and is closed.Regards.\']""]\nRelated Issues:\n[]\n\n### End'}"
949,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8082\n\n### Instruction:\nVT for intake was created (VT-379/12/22). VT is for ASN with 4 lines. ASN and VT show correct quantity for all lines in DHP. VT message has no quantity for last item. Because of this, message is not accepted in PCS.\r\nPlease check why the quantity is missing. This particular VT was processed manually by PCS supplier, plant informed us that the had similar cases. \r\n\r\nNote that this VT has multiple lines. \r\nPerhaps that is related to this issue.\r\n\r\nExpected: on loadLineNumber 4: estimatedQuantity: 6000Kg. Message contains: 0Kg\r\n\r\n{\r\n\t\t\t""vehicleTicketNumber"": ""VT-379/12/22"",\r\n\t\t\t""asnNumber"": ""CL000010522"",\r\n\t\t\t""status"": 1,\r\n\t\t\t""realisationDate"": ""2022-12-19T02:00:00.0000000+01:00"",\r\n\t\t\t""forwarderCode"": ""HEU"",\r\n\t\t\t""forwarderName"": ""HEU"",\r\n\t\t\t""plantId"": 4,\r\n\t\t\t""vehiclePlateNumber"": ""TRUCK"",\r\n\t\t\t""vehicleTicketLines"": [\r\n\t\t\t\t{\r\n\t\t\t\t\t""loadLineNumber"": 1,\r\n\t\t\t\t\t""articleCode"": ""0769"",\r\n\t\t\t\t\t""articleName"": ""PX LEG-ZC 0.25%"",\r\n\t\t\t\t\t""packingForm"": ""BLK"",\r\n\t\t\t\t\t""itemBaseWeight"": 0.0,\r\n\t\t\t\t\t""itemBaseWeightUnit"": ""kg"",\r\n\t\t\t\t\t""supplierCode"": ""L004239"",\r\n\t\t\t\t\t""supplierName"": ""De Heus Premix BV"",\r\n\t\t\t\t\t""estimatedQuantity"": 8000.0,\r\n\t\t\t\t\t""estimatedQuantityUnit"": ""kg"",\r\n\t\t\t\t\t""deliveryId"": 18429,\r\n\t\t\t\t\t""countryOfOrigin"": ""*""\r\n\t\t\t\t},\r\n\t\t\t\t{\r\n\t\t\t\t\t""loadLineNumber"": 2,\r\n\t\t\t\t\t""articleCode"": ""0777"",\r\n\t\t\t\t\t""articleName"": ""PX LAYERS 0.1%"",\r\n\t\t\t\t\t""packingForm"": ""BLK"",\r\n\t\t\t\t\t""itemBaseWeight"": 0.0,\r\n\t\t\t\t\t""itemBaseWeightUnit"": ""kg"",\r\n\t\t\t\t\t""supplierCode"": ""L004239"",\r\n\t\t\t\t\t""supplierName"": ""De Heus Premix BV"",\r\n\t\t\t\t\t""estimatedQuantity"": 10000.0,\r\n\t\t\t\t\t""estimatedQuantityUnit"": ""kg"",\r\n\t\t\t\t\t""deliveryId"": 18430,\r\n\t\t\t\t\t""countryOfOrigin"": ""*""\r\n\t\t\t\t},\r\n\t\t\t\t{\r\n\t\t\t\t\t""loadLineNumber"": 3,\r\n\t\t\t\t\t""articleCode"": ""0672"",\r\n\t\t\t\t\t""articleName"": ""PX VIT E 40.000"",\r\n\t\t\t\t\t""packingForm"": ""BLK"",\r\n\t\t\t\t\t""itemBaseWeight"": 0.0,\r\n\t\t\t\t\t""itemBaseWeightUnit"": ""kg"",\r\n\t\t\t\t\t""supplierCode"": ""L004239"",\r\n\t\t\t\t\t""supplierName"": ""De Heus Premix BV"",\r\n\t\t\t\t\t""estimatedQuantity"": 7000.0,\r\n\t\t\t\t\t""estimatedQuantityUnit"": ""kg"",\r\n\t\t\t\t\t""deliveryId"": 18431,\r\n\t\t\t\t\t""countryOfOrigin"": ""*""\r\n\t\t\t\t},\r\n\t\t\t\t{\r\n\t\t\t\t\t""loadLineNumber"": 4,\r\n\t\t\t\t\t""articleCode"": ""0695"",\r\n\t\t\t\t\t""articleName"": ""PX VITEXTRA-CO .5%"",\r\n\t\t\t\t\t""packingForm"": ""BLK"",\r\n\t\t\t\t\t""itemBaseWeight"": 0.0,\r\n\t\t\t\t\t""itemBaseWeightUnit"": ""kg"",\r\n\t\t\t\t\t""supplierCode"": ""L004239"",\r\n\t\t\t\t\t""supplierName"": ""De Heus Premix BV"",\r\n\t\t\t\t\t""estimatedQuantity"": 0.0,\r\n\t\t\t\t\t""estimatedQuantityUnit"": ""kg"",\r\n\t\t\t\t\t""deliveryId"": 18432,\r\n\t\t\t\t\t""countryOfOrigin"": ""*""\r\n\t\t\t\t}\r\n\t\t\t]\r\n\t\t}\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 2: "" !screenshot-1! {code:java}  select * FROM [DHPlantVCBusinessLogicMain].[dbo].[VehicleTicketBulkIntakeElements] -- where VehicleTickets=\\\'2E1DC5A6-1F17-4D19-84A8-18B47167203D\\\' where InternalSerialNumber like \\\'VT-379/12/22%\\\'{code} !screenshot-2! ""\', \'Comment 3: \\\'{code:java}SELECT TOP (1000) [Id]      ,[Created]           ,[Event]      ,[EventType]         ,[UserName]     FROM [DHPlantVCBusinessLogicEvents].[dbo].[VehicleTickets] FROM [DHPlantVCBusinessLogicEvents].[dbo].[VehicleTickets]  where AggregateId=\\\\\\\'2E1DC5A6-1F17-4D19-84A8-18B47167203D\\\\\\\'  and EventType=\\\\\\\'Plant.VC.BusinessLogic.DomainAbstractions.VehicleTickets.DomainEvents.VehicleTicketBulkIntakeFinalWeighingPerformedEvent\\\\\\\'  and event like \\\\\\\'%""No"":4%\\\\\\\'  order by created{code}\\\'\', ""Comment 4: \'Final weight information for element 4 came from pcs.What you can see below and in the VC module. !screenshot-4! !image-2022-12-20-14-12-59-154!\'"", ""Comment 5: \'PCS supplier manually updated the quantity so that intake could be completed. However"", \'Comment 6: that is not the solution.On 20-12 again we had a VT with quantity 0: VT-461/12/22Same case: multiple lines\', \'Comment 7: last line has qty 0.\\\\t\\\\t{\\\\t\\\\t\\\\t""vehicleTicketNumber"": ""VT-461/12/22"",\\\\t\\\\t\\\\t""asnNumber"": ""CL000010495"",\\\\t\\\\t\\\\t""status"": 1,\\\\t\\\\t\\\\t""realisationDate"": ""2022-12-21T02:00:00.0000000+01:00"",\\\\t\\\\t\\\\t""forwarderCode"": ""HEU"",\\\\t\\\\t\\\\t""forwarderName"": ""HEU"",\\\\t\\\\t\\\\t""plantId"": 4,\\\\t\\\\t\\\\t""vehiclePlateNumber"": ""TRUCK"",\\\\t\\\\t\\\\t""vehicleTicketLines"": [\\\\t\\\\t\\\\t\\\\t{\\\\t\\\\t\\\\t\\\\t\\\\t""loadLineNumber"": 1,\\\\t\\\\t\\\\t\\\\t\\\\t""articleCode"": ""0791"",\\\\t\\\\t\\\\t\\\\t\\\\t""articleName"": ""PX BREEDR1 0.1%"",\\\\t\\\\t\\\\t\\\\t\\\\t""packingForm"": ""BB"",\\\\t\\\\t\\\\t\\\\t\\\\t""itemBaseWeight"": 0.0,\\\\t\\\\t\\\\t\\\\t\\\\t""itemBaseWeightUnit"": ""kg"",\\\\t\\\\t\\\\t\\\\t\\\\t""supplierCode"": ""L004239"",\\\\t\\\\t\\\\t\\\\t\\\\t""supplierName"": ""De Heus Premix BV"",\\\\t\\\\t\\\\t\\\\t\\\\t""estimatedQuantity"": 8000.0,\\\\t\\\\t\\\\t\\\\t\\\\t""estimatedQuantityUnit"": ""kg"",\\\\t\\\\t\\\\t\\\\t\\\\t""deliveryId"": 18541,\\\\t\\\\t\\\\t\\\\t\\\\t""countryOfOrigin"": ""*""\\\\t\\\\t\\\\t\\\\t},\\\\t\\\\t\\\\t\\\\t{\\\\t\\\\t\\\\t\\\\t\\\\t""loadLineNumber"": 2,\\\\t\\\\t\\\\t\\\\t\\\\t""articleCode"": ""0774"",\\\\t\\\\t\\\\t\\\\t\\\\t""articleName"": ""PX SLF-ORG-MIN 0,25%"",\\\\t\\\\t\\\\t\\\\t\\\\t""packingForm"": ""25 KG"",\\\\t\\\\t\\\\t\\\\t\\\\t""itemBaseWeight"": 0.0,\\\\t\\\\t\\\\t\\\\t\\\\t""itemBaseWeightUnit"": ""kg"",\\\\t\\\\t\\\\t\\\\t\\\\t""supplierCode"": ""L004239"",\\\\t\\\\t\\\\t\\\\t\\\\t""supplierName"": ""De Heus Premix BV"",\\\\t\\\\t\\\\t\\\\t\\\\t""estimatedQuantity"": 2000.0,\\\\t\\\\t\\\\t\\\\t\\\\t""estimatedQuantityUnit"": ""kg"",\\\\t\\\\t\\\\t\\\\t\\\\t""deliveryId"": 18542,\\\\t\\\\t\\\\t\\\\t\\\\t""countryOfOrigin"": ""*""\\\\t\\\\t\\\\t\\\\t},\\\\t\\\\t\\\\t\\\\t{\\\\t\\\\t\\\\t\\\\t\\\\t""loadLineNumber"": 3,\\\\t\\\\t\\\\t\\\\t\\\\t""articleCode"": ""0778"",\\\\t\\\\t\\\\t\\\\t\\\\t""articleName"": ""PX BROSUPP EXP 0.1%"",\\\\t\\\\t\\\\t\\\\t\\\\t""packingForm"": ""BB"",\\\\t\\\\t\\\\t\\\\t\\\\t""itemBaseWeight"": 0.0,\\\\t\\\\t\\\\t\\\\t\\\\t""itemBaseWeightUnit"": ""kg"",\\\\t\\\\t\\\\t\\\\t\\\\t""supplierCode"": ""L004239"",\\\\t\\\\t\\\\t\\\\t\\\\t""supplierName"": ""De Heus Premix BV"",\\\\t\\\\t\\\\t\\\\t\\\\t""estimatedQuantity"": 8000.0,\\\\t\\\\t\\\\t\\\\t\\\\t""estimatedQuantityUnit"": ""kg"",\\\\t\\\\t\\\\t\\\\t\\\\t""deliveryId"": 18543,\\\\t\\\\t\\\\t\\\\t\\\\t""countryOfOrigin"": ""*""\\\\t\\\\t\\\\t\\\\t},\\\\t\\\\t\\\\t\\\\t{\\\\t\\\\t\\\\t\\\\t\\\\t""loadLineNumber"": 4,\\\\t\\\\t\\\\t\\\\t\\\\t""articleCode"": ""0674"",\\\\t\\\\t\\\\t\\\\t\\\\t""articleName"": ""PX VIT HYD-MIX 0,1%"",\\\\t\\\\t\\\\t\\\\t\\\\t""packingForm"": ""BB"",\\\\t\\\\t\\\\t\\\\t\\\\t""itemBaseWeight"": 0.0,\\\\t\\\\t\\\\t\\\\t\\\\t""itemBaseWeightUnit"": ""kg"",\\\\t\\\\t\\\\t\\\\t\\\\t""supplierCode"": ""L004239"",\\\\t\\\\t\\\\t\\\\t\\\\t""supplierName"": ""De Heus Premix BV"",\\\\t\\\\t\\\\t\\\\t\\\\t""estimatedQuantity"": 0.0,\\\\t\\\\t\\\\t\\\\t\\\\t""estimatedQuantityUnit"": ""kg"",\\\\t\\\\t\\\\t\\\\t\\\\t""deliveryId"": 18544,\\\\t\\\\t\\\\t\\\\t\\\\t""countryOfOrigin"": ""*""\\\\t\\\\t\\\\t\\\\t}\\\\t\\\\t\\\\t]\\\\t\\\\t}\\\'\', \'Comment 8: \\\'mam dla dwóch przypadków EventType=\\\\\\\'Plant.VC.BusinessLogic.DomainAbstractions.VehicleTickets.DomainEvents.VehicleTicketBulkIntakeFinalWeighingPerformedEvent\\\\\\\' dla pozycji po 0. jak niżej{code:java}  select event,eventtype,username FROM [DHPlantVCBusinessLogicEvents].[dbo].[VehicleTickets]  where AggregateId=\\\\\\\'2E1DC5A6-1F17-4D19-84A8-18B47167203D\\\\\\\'  and EventType=\\\\\\\'Plant.VC.BusinessLogic.DomainAbstractions.VehicleTickets.DomainEvents.VehicleTicketBulkIntakeFinalWeighingPerformedEvent\\\\\\\'--  and event like \\\\\\\'%""No"":4%\\\\\\\'  order by created   select event,eventtype,username FROM [DHPlantVCBusinessLogicEvents].[dbo].[VehicleTickets]  where AggregateId=\\\\\\\'B0728B49-D06D-4223-A511-5396660CF55A\\\\\\\'  and EventType=\\\\\\\'Plant.VC.BusinessLogic.DomainAbstractions.VehicleTickets.DomainEvents.VehicleTicketBulkIntakeFinalWeighingPerformedEvent\\\\\\\'--  and event like \\\\\\\'%""No"":4%\\\\\\\'  order by created{code} !screenshot-6! \\\'\', \'Comment 9: ""Isn\\\'t this the same issue as in the DHITS-611?""\', \'Comment 10: ""{color:#000000}In this case I do not see that VT was sent a second time. And situation only seems to occur for VT\\\'s with multiple lines.{color}   {color:#000000}{color}     {color:#000000}       {color}{color:black}{color} {color:#000000} {color}{color:black}Best regards | Met vriendelijke groeten,{color}{color:#000000}{color}{color:black}  Bob Kennedy{color} {color:#000000}{color}{color:black}Informatie analist{color}{color:#000000} {color}{color:black}{color}{color:#000000} {color}{color:#000000} {color} |{color:#000000}{color} {color:#000000}{color}De Heus Voeders{color:#000000} <[http://www.de-heus.nl/]>{color}{color:black}{color}{color:#000000} {color}{color:#000000} {color}|{color:#000000}{color}{color:#006FB7} * De Heus Voeders B.V.*{color}{color:#000000}{color}{color:#006FB7}{color} {color:#000000}{color}{color:#006FB7} Postbus 396 6710 BJ Ede{color}{color:#000000}{color}{color:#006FB7} Rubensstraat 1756717 VE Ede  *M* 06 - 53 224 931 KvK 14626985{color}{color:#000000}{color}{color:black} {color}{color:#000000}{color}{color:#006FB7} _ Op dit e-mailbericht en eventuele bijlage(n) is de disclaimer van toepassing_{color}{color:#000000}{color}{color:#006FB7}{color} {color:#000000}{color}{color:#006FB7} _ gepubliceerd op de website van_{color} [{color:#006FB7} _De Heus Voeders_{color}|http://www.de-heus.nl/maildisclaimer]{color:#006FB7} _._{color}{color:#000000}{color}{color:#006FB7}{color} {color:#000000} {color}{color:#000000} {color}| |{color:#000000}{color}{color:black}{color} image007.jpg@01D62AA3.AD14DDB0{color:black}{color}{color:#000000} {color}{color:#000000} {color}| |{color:#000000}{color}{color:black}{color} image004.jpg@01D62AA3.AD2CAB70{color:black}{color}{color:#000000} {color}{color:#000000} {color}| {color:#000000}{color} ---- {color:#000000} *From:* Piotr Gaczorek (Jira) <jira@kotrak.com>  *Sent:* Thursday\', \'Comment 11: December 22\', \'Comment 12: 2022 3:33 PM  *To:* Kennedy\', \'Comment 13: Bob <BKennedy@deheus.com>  *Subject:* DGS-8082 VT for intake does not contain quantity for one of the lines{color}  |{color:#ffffff} CAUTION: This message originated from outside the organisation. Please do not click on links or open attachments unless you trust the sender and know the content is safe.{color} |""\', ""Comment 14: \'Analogicznie do:https://helpdesk.kotrak.com/browse/DAP-13104?focusedCommentId=1068405&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-1068405\'"", ""Comment 15: \'Hello"", ""Comment 16: this issue has been fixed in version 8.5.Can we close this ticket?\'"", ""Comment 17: \'This ticket can be closed.\']""]\nRelated Issues:\n[\'DAP-13104\']\n\n### End'}"
950,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8081\n\n### Instruction:\nHello all,\r\n\r\nWe want to improve a process in NAS. When build it can be rolled out our other administrations when needed.\r\n\r\nImprovement NAS – deposits\r\n•\tWe do not want to use Kofax (now we are creating invoices ourselves and scan them with Kofax)\r\n•\tWe want the possibility to copy registration sales invoices that are booked on an specific NAS round now VERG. Creation of a new item code, specific for this type of posting: item code VNAS\r\n\r\nStart of this process must be something like this: \r\no\t1. From out the Round select the Registration Sale document and drill down to this document (double click). \r\no\t2. Copy this document by clicking the <Action> button and choose <copy this document>.\r\no\t3. Automatically I come into the created document where I can adjust the document on header level and also on line level.\r\no\t4. Create Purchase Regular invoice and adjust what is needed on header level and line level. = standard procedure.\r\no\t5. Send  the Purchase invoice into the workflow for approval (Archive) = standard procedure.\r\no\t6. Return to the created SI document and send this one into the approval flow (Archive) = standard procedure.\r\no\t7. Return to the source SI registered document and close.\r\no\t8. Return to the Round. Where the proces initially started.\r\no\tEND.\r\n\r\n•\tAdditional requirments below:\r\n•\tThe information on the invoice lines should be copied, but we need to be able to adjust the invoice lines.\r\n•\tThe invoice date of the document should be the day of today, the delivery date can be copied from the original document. The due date should be the invoice date +1.  Data like supplier, invoice type, reference and full number should be copied as well.\r\n•\tA regular purchase invoice should be created in the background at the same time the registration sales invoice is copied from the round. All data except the invoice and due date need to be copied as well. The SI and PI need to be linked the same way as whenever they were created manually.\r\n•\tPurchase invoices with the item code VNAS should always be considered as self-billing, although we will select a L-number as Supplier. The L-number that is used in the communication with Milas should be the L-number of the delivery customer (and not the invoice customer)\r\n•\tBert and Christine should be able to move the created invoices to another round (of the same customer)\r\n•\tYou could have a look at SI-RTN/2022/0132 (ID57946) and the linked PI document as a reference of how we do it right now.\r\n\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Do wewnętrznego podsumowania.\'"", ""Comment 3: \'linked toDHNLC-691Waititng for Mitch\'"", ""Comment 4: \'Hi @MitchHi [~CJong@deheus.com]I have some questions I want to clarify before we start working on that topic.As I understand from above"", \'Comment 5: the process for invoicing the VNAS item (in NAS) starts from SI registration\', \'Comment 6: from which PI regular is created. It means that we want to see in Round SI Registration\', ""Comment 7: but at the same time we need to have a PI Regular linked to this SI. PI is not to be presented in Round. None of these invoices will be listed in S2P. Could you confirm that is correct?!image-2023-01-09-16-11-07-299.png!\'"", ""Comment 8: \'We divide this task to 2 steps. 1st step is ready for UAT tests.After confirmation that it\\\\\'s correct"", \'Comment 9: we can start adjusting 2nd part of the task\', \'Comment 10: so points1-5 are ready for UAT tests:*1st part of task*{quote}1. Add a new tab in Round document <Vergoeding> (like Expenses) * SI REGULAR with VNAS item code (and corrections)- new relation is added to the Relation Table in NAS (AD column)2. Add new section (lists like Expenses) ""Vergoeding"" in Financial Statement document form (the same data is to be displayed as described on point 2): * General * Details3. Addnew section ""Vergoeding"" to the printout Financial Statement printout4. Add the invoicesSI REGULAR with VNAS item code (if not corrected by CSI) to S2P document and saldo calculation5. Add the invoicesSI REGULAR with VNAS item code (if not corrected by CSI) to S2P printout{quote}*2nd part of task:*NAS - new process:to do: # Add the possibility to copy the SI Regular (VNAS) and PI Regular (linked to SI) from a Round. It should be possible to double click in the VNAS item in Round (the system opens the SI) and create copies of the VNAS invoices by lightening action ""Create copies of VNAS SI and PI"". # The system should open both generated documents SI and below PI. The user can adjust data in these invoices!image-2023-01-16-11-45-12-739.png! Data in the copied invoices: - document date - generation date - delivery date - to be copied from the original invoice -the due date should be the invoice date +1. - it should be possible to change the round number (only for round related to the farmer from SI/PI) !image-2023-01-16-11-45-26-847.png!!image-2023-01-16-11-45-12-739! !image-2023-01-16-11-45-26-847!\\\'\', ""Comment 11: \'Part 1 is approved.\'"", ""Comment 12: \'What is the status of part 2?\'"", ""Comment 13: \'[~mbovene@deheus.com]we are in progress.\'"", \'Comment 14: \\\'[~mbovene@deheus.com],we have done part 2. You can feel free to test new funtionality.Creation copy for SI and PI is attached on SI document with VNAS element:!image-2023-01-27-11-08-29-220.png!I have one more question about view on Round expenses table:!image-2023-01-27-11-23-22-890.png!We need to exclude VNAS invoice positions from ""Expenses"" on Round?Best regards\', ""Comment 15: Grzegorz!image-2023-01-27-11-23-22-890!\'"", \'Comment 16: ""Hi [~mbovene@deheus.com],Hi[~CJong@deheus.com],Please review redesign of functionality and add some remarks if it\\\'s needed or confirm that this is correct.There is summary of adjustments needed after our today meeting. * Relation tableThere process should looks like that: Purchase Invoice -> Sales InvoiceFirst should be created Purchase Invoice\', ""Comment 17: then from PI should be created Sales Invoice.Only Sales invoices should be included on Round and Financial statement. !image-2023-02-01-14-23-29-141.png!We need to add new values \'Vergoeding\' to dictionaries:!image-2023-02-01-14-17-26-832.png! * Item Group * Round Category * Relation Table for Round - there should be added relations for: ** Customer"", \'Comment 18: Farmer,Vergoeding,Vergoeding ** Vendor\', ""Comment 19: Farmer,Vergoeding,Vergoeding!image-2023-02-01-14-17-13-579.png!Item VNAS should be properly parrametrized (otherwise on invoice line values for \'Default round category\' and \'Round category\' won\'t be set with correct values): * Item Group = \'Vergoeding\' * Possible Round Categories = \'Vergoeding\' !image-2023-02-01-14-10-26-552.png! * Purchase Invoice documents list:There will be new list of documents (defined list) which will contain elements of Purchase Invoices with items = \'VNAS\' - important column for this list is: Description from document elements. These invoices will have only one line with Item = \'VNAS\'!image-2023-02-01-14-29-13-026.png!From the list it will be possible to select multiple invoices on list"", ""Comment 20: then from the ligtning button execute action - \'Create copies of VNAS PI and SI\' for all selected PI\'s.For each PI will be created: * Copy of PI * Copy of SI (connected to source PI by Leading doc)Documents will be created in background in inbox of user who execute action and it will be possible to change data on documents (for example Description on invoice elements)For exapmle: If there will be 10 selected PI documents from this list"", \'Comment 21: action will generate 10 copies of PI and 10 copies of SI documents.Access to this list should have: Christine and Bert (for now)""\', ""Comment 22: \'{color:black}Good morning Damian,{color} {color:black}{color} {color:black}Please continue this development.{color} {color:black}It is a correct approach of our meeting yesterday!{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Christinede{color} |{color:#000001} {color} |{color:#000001} Jong{color} |  {color:#000001}MedewerkerContractadministratie{color} | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.de-heus.nl/]>{color} | |  *{color:#006FB7} *DEHEUSVOEDERSB.V.*{color}* | | | |{color:#000001} Postbus396 6710BJEde \\\\u200b{color} | |{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} | | |{color:#000001} T:0318675567{color} |  {color:#000001}KvK14626985{color}   _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | | !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | | !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} | | !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} |           *Van:* Damian Świstek (Jira) <[jira@kotrak.com|mailto:jira@kotrak.com]>   *Verzonden:* woensdag 1 februari 2023 14:42  *Aan:* Jong"", ""Comment 23: Christine de <[CJong@deheus.com|mailto:CJong@deheus.com]>  *Onderwerp:* DGS-8081 Ready for UAT tests (partly) - Process adjustments deposits (now VERG)   |  *{color:white} *CAUTION: This message originated from outside the organisation. Please do not click on links or open attachments unless you trust the sender and know the content is safe.*{color}* |   !image006!!image007!!image008!!image009!!image010!\'"", ""Comment 24: \'Dodano listę z PI w NAS:!image-2023-02-02-14-56-34-871.png!Pod prawym przyciskiem myszy na danej fakturze - możliwość generacji:!image-2023-02-02-14-57-07-372.png!Generacja kopiuje pierwsze PI i podnosi je do edycji (z możliwością wykonania przepływu)"", ""Comment 25: kolejno SI.Do przetestowania przez klienta z uwzględnieniem informacji o których rozmawialiśmy.\'"", \'Comment 26: ""Could we meet to review how we changed it right now and verify wheter it will be ok for your needs and discuss other details of this functionality?Please let me know if you have time tomorrow or any other day and I will show you our changes so far. I can also record some short video if you want to show how it could works.We\\\'ve made some changes\', \'Comment 27: but we had to modified functionality of copying PI and SI due to technical limitations of Intense. We cannot use multiply selecting documents and make copy all of documents (PI and SI) by one clik. It would be possible to do it with 2 steps (1st: multiple select on PI list and create PI copies\', \'Comment 28: 2nd:multiple select on PI list and create SI copies)\', \'Comment 29: but this solution when we discuss about it\', ""Comment 30: it\'s not so comfortable.We\'ve made some different solution right now which seems better to handle this process of creating invoices.In summary: * There is a list of PI documents with \'VNAS\' item * Action from lighnitng is executed for 1 document PI (we don\'t select multiple documents) ** copy of PI is generated and it\'s open on screen"", ""Comment 31: then you can change needed fields and also make a flow for the document ** copy of SI is generated and it\'s open on screen"", \'Comment 32: then you can change needed fields and also make a flow for the documentIn this case it will be done for 1 document\', \'Comment 33: but you can handle whole process: copy of invoices\', \'Comment 34: change values\', \'Comment 35: make a flowsThen it\\\'s not needed to go again to all documents and make some changes.""\', ""Comment 36: \'Do wysłania info jak obecnie jest to skonfigurowane na bazie testowej\'"", \'Comment 37: ""We\\\'ve discussed internally this solution and made partly changes of this functionality. How it can works right now: # From defined list you are able to select multiple Purchase Invoices # Then you can select action from Lightning button # Copy of all selected documents are created - (PI -> new PI\', \'Comment 38: SI (based on PI Leading doc) -> new SI)There is an attachment with video where you can see how works this part of functionality.[^VNAS.wmv]If it is good way to handle process we can start with further part of solution with extended the process of sending invoices to Archive (we discussed about it last time that it could be 2 processes for invoices which are modified and for this which are a copy 1 to 1 from old document and could be send to Archive without any Approval flow).We can plan a meeting again and discuss about solution which will be best suited to your needs.""\', ""Comment 39: \'{color:black}Good morning Damian,{color} {color:black}{color} {color:black}{color} {color:black}Thanks for your input and development to this process adjustment.{color} {color:black}Last Thursday we tested and discuss this modification. The tab/button shows the information we need for this action.{color} # {color:black} How does the system recognize that a posting which is not modified can be archived at once.{color}  {color:black}Maybe it is a good approach that when a modification/new document should be made we create one as usual{color} {color:black}à{color}{color:black} regular PI.{color} # {color:black} After action"", \'Comment 40: these documents should go to the inbox of the action taker à not administrator.{color} {color:black}At first Bert Geijtenbeek and Christine de Jong should be able to create these.{color} # {color:black} Are only the documents visible which were created last month or is this only with a filter?{color}# {color:black} These criteria were not clear in our test The red text we missed:{color} |{color:black} Purchase Invoice Number{color} | = To be generared automatically | |{color:black} Invoice date{color} | = TODAY | |{color:black} Delivery date{color} |{color:red} = TODAY{color} | |{color:black} Due date{color} |{color:red} = TODAY + 1{color} | |{color:black} External Document Number{color} |{color:red} = To be generared automatically\', \'Comment 41: dynamic (source document + 1){color} | |{color:black} {color} |{color:red} {color} |  {color:black}Awaiting your feedback\', \'Comment 42: so we can test again.{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Christinede{color} |{color:#000001} {color} |{color:#000001} Jong{color} |  {color:#000001}MedewerkerContractadministratie{color} | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.de-heus.nl/]>{color} | |  *{color:#006FB7} *DEHEUSVOEDERSB.V.*{color}* | | | |{color:#000001} Postbus396 6710BJEde \\\\u200b{color} | |{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} | | |{color:#000001} T:0318675567{color} |  {color:#000001}KvK14626985{color}   _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | | !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | | !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} | | !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} |      *Van:* Damian Świstek (Jira) <jira@kotrak.com>   *Verzonden:* maandag 13 februari 2023 16:03  *Aan:* Jong\', ""Comment 43: Christine de <CJong@deheus.com>  *Onderwerp:* DGS-8081 Ready for UAT tests (partly) - Process adjustments deposits (now VERG)   |  *{color:white} *CAUTION: This message originated from outside the organisation. Please do not click on links or open attachments unless you trust the sender and know the content is safe.*{color}* |   !image006.gif!\'"", \'Comment 44: ""Hello Christine,Below my remarks.{quote}{color:#000000}Last Thursday we tested and discuss this modification. The tab/button shows the information we need for this action.{color} # {color:#000000}How does the system recognize that a posting which is not modified can be archived at once.{color}{quote}{color:#000000}We don\\\'t have any good moment or field when we know that document should be modified or not. I think the best solution for now is to decide by user that this document should be modified or not and decide which invoices should go to \\\'Archive\\\' directly without \\\'Waiting for Approval\\\' flow.{color}{color:#000000}After creating many documents we\\\'re not able to know how these documents should be treated.{color}{quote}{color:#000000}Maybe it is a good approach that when a modification/new document should be made we create one as usual{color}{color:#000000}à{color}{color:#000000}regular PI.{color} # {color:#000000}After action\', ""Comment 45: these documents should go to the inbox of the action taker à not administrator.{color}{quote}All of Purchase invoices copied in this process should be created as a \'Regular\' type of purchase? Is it something which we should set by default for these invoices (even if the old PI was different than \'Regular\')?Ok"", ""Comment 46: we will verify these and invoices will be created in inbox of user who launched this action.{quote}{color:#000000}At first Bert Geijtenbeek and Christine de Jong should be able to create these.{color} # {color:#000000}Are only the documents visible which were created last month or is this only with a filter?{color}{quote}{color:#000000}We will add permission to this list also to Bert.{color}{color:#000000}Now on Purchase Invoice (VNAS) list there are all PI invoices with item = \'VNAS\'. You can filter it on tjhe list by document date or other fields from invoices. We can also add some conditions and show only specify invoices if it will be needed.{color}{quote} # {color:#000000}These criteria were not clear in our test The red text we missed:{color}|{color:#000000}Purchase Invoice Number{color}|= To be generared automatically||{color:#000000}Invoice date{color}|= TODAY||{color:#000000}Delivery date{color}|{color:#FF0000}= TODAY{color}||{color:#000000}Due date{color}|{color:#FF0000}= TODAY + 1{color}||{color:#000000}External Document Number{color}|{color:#FF0000}= To be generared automatically"", \'Comment 47: dynamic (source document + 1){color}||{color:#000000}{color}|{color:#FF0000}{color}|{color:#000000}Awaiting your feedback\', \'Comment 48: so we can test again.{color}{quote}{color:#000000}Ok\', ""Comment 49: we will change \'Delivery date\' and \'Due date\' calculations like above.{color}{color:#000000}For \'External Document Number\' - this field it\'s not only numeric as I saw in database"", ""Comment 50: so there are also values with text. It couldn\'t be possible to add + 1 number to all fields if there will be some letter? Maybe we should add some letter/sign at the end of old number? It should be unique for Milas"", \'Comment 51: right? Milas won\\\'t accept 2 invoices with the same \\\'External Document Number\\\'{color}""\', ""Comment 52: \'[~damian.swistek@kotrak.com],dodałem pole na SI i PI w NAS - Doc_IntColumn40 - gdzie wrzucamy 1 przy generowaniu.Daty uzupełnione.Pozdrawiam"", ""Comment 53: Grzegorz\'"", ""Comment 54: \'Hi Damian"", \'Comment 55:  # {color:black} Maybe it is a good approach to only use the copy button when a document should be copied.{color}# {color:black} In case of modification I will make a regular posting à Regular PI / SI. This is a manual action\', \'Comment 56: already in Intense. No copy button used here.{color} {color:black}I think that this we’ll have the least impact for you in developing this new functionality.{color} # {color:black} In our external documentnumber we need to have a month notification.{color} {color:black}That’s why we now use 2023/1-02.. 2023/1-03 etc.{color} {color:black}When we change this to letters it will not be clear for our customers which month is compensated. Also\', \'Comment 57: when we make the closure of the rounds things can be mixed up.{color} {color:black}Mitch came up with the brilliant idea that if we change the letter of the purchase to a number\', \'Comment 58: are you then able to{color} {color:red}= To be generared automatically\', \'Comment 59: dynamic (source document + 1){color}{color:black}{color} {color:black}{color} {color:black}Thanks for your feedback.{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Christinede{color} |{color:#000001} {color} |{color:#000001} Jong{color} |  {color:#000001}MedewerkerContractadministratie{color} | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.de-heus.nl/]>{color} | |  *{color:#006FB7} *DEHEUSVOEDERSB.V.*{color}* | | | |{color:#000001} Postbus396 6710BJEde \\\\u200b{color} | |{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} | | |{color:#000001} T:0318675567{color} |  {color:#000001}KvK14626985{color}   _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | | !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | | !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} | | !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} |        *Van:* Damian Świstek (Jira) <jira@kotrak.com>   *Verzonden:* maandag 20 februari 2023 12:39  *Aan:* Jong\', ""Comment 60: Christine de <CJong@deheus.com>  *Onderwerp:* DGS-8081 Ready for UAT tests (partly) - Process adjustments deposits (now VERG)   \'"", \'Comment 61: ""{quote}{color:#000000}1. Maybe it is a good approach to only use the copy button when a document should be copied.{color}{quote}{color:#4c9aff}Do you mean to use in this case action as it is on IBIP_DH_TEST right now?{color}{color:#000000}!image-2023-02-27-10-50-57-302.png!{color}{quote}{color:#000000}2. In case of modification I will make a regular posting à Regular PI / SI. This is a manual action\', \'Comment 62: already in Intense. No copy button used here.{color}{quote}{color:#4c9aff}Which action do you mean in this case? Manually creating PI and SI\', \'Comment 63: not copying documents by action from point above?{color}{quote}{color:#000000}1. In our external documentnumber we need to have a month notification.{color}{color:#000000}That’s why we now use 2023/1-02.. 2023/1-03 etc.{color}{color:#000000}When we change this to letters it will not be clear for our customers which month is compensated. Also\', \'Comment 64: when we make the closure of the rounds things can be mixed up.{color}{color:#000000}Mitch came up with the brilliant idea that if we change the letter of the purchase to a number\', \'Comment 65: are you then able to{color}{color:#FF0000}= To be generared automatically\', \'Comment 66: dynamic (source document + 1){color}{quote}{color:#4c9aff}I\\\'m not sure that i good understand it.{color}{color:#4c9aff}Do you mean that there will be always a number in field \\\'External Document Number\\\'? And then will be for example 20230102 and we should calculate it when there will be a copy of this PI and put number for new PI number 20230103 (20230102 + 1) ? Or do you refer to other number?{color}{color:#000000}!image-2023-02-27-11-30-15-576.png!{color}{color:#000000}Regards{color}""\', ""Comment 67: \'1. Yes you are right.2. Yes"", \'Comment 68: also correct. In that case we will only copy documents which 100% identical (in step 1\', \'Comment 69: except the dates and external document number)1. Yes\', \'Comment 70: we can agree with your proposal. For example 20230102 and we should calculate it when there will be a copy of this PI and put number for new PI number  20230103 (20230102 + 1).Next to this we would like to use the field ""Description on the header"" to indicate the month of compensation. This can be only a number like 1 for January\', ""Comment 71: 2 for February etc. Could we do a +1 to this field when we copy the previous document?\'"", ""Comment 72: \'{quote}2. Yes"", \'Comment 73: also correct. In that case we will only copy documents which 100% identical (in step 1\', \'Comment 74: except the dates and external document number){quote}In this case documents will be created manually by already existing functionality\', ""Comment 75: right?How \\\\\'External Document Number\\\\\' field should be calculated on new document (when it\\\\\'s copying by functionality \\\\\'Create copied VNAS SI and PI\\\\\' for identical documents)?There are examples from database"", \'Comment 76: there are sometimes values like these:01VF009316,101529/9-3-2022 2022/11-00004\', \'Comment 77: then we\\\\\\\'re not able to add +1 to this values when it\\\\\\\'s a text or other characters between numbers.{quote}Next to this we would like to use the field ""Description on the header"" to indicate the month of compensation. This can be only a number like 1 for January\', ""Comment 78: 2 for February etc. Could we do a +1 to this field when we copy the previous document?{quote}Maybe it\\\\\'s better to add new number field (to avoid letters or any other characters) which will be filled only by numbers. We can calculate this number when document will be copying"", \'Comment 79: but what should be range of this values (do we need a calculating like month - from 1 to 12\', ""Comment 80: or it could be continuous). It\\\\\'s also option to calculate this value from other field (from invoice date - we can take proper month from this date and fill in this field).Where this field should appears? it should be visible on Purchase Invoice list of VNAS document? It will be better when this field will be numeric only"", ""Comment 81: then we can be sure that we\\\\\'re able to calculate it properly (when it\\\\\'s a text field we don\\\\\'t know what will be in this field).\'"", \'Comment 82: ""Hi [~CJong@deheus.com],Could you confirm/add some remarks to this summary of meeting below: * External Document Number should be calculated and created from other data and should looks like that *803319/A/2023/02* ** 803319 - Code from Reference ** A - manually added symbol\', ""Comment 83: copying when coument is copying by action ** 2023 - year - taken from current date of invoicing (date from creation date of document) ** 02 - month- taken from current date of invoicing (date from creation date of document)Main rules for these calculation for External Document Number will be always unique ** document will be created in month of real creation of it ** document will be created once per month for this type of invoice!image-2023-03-06-12-12-04-129.png! * Should be created new flows for documents which are copying 1:1 - without changes in data on invoices (for PI and SI documents) ** should be possible to perform flow from \'Entry\' to \'Archive\' directly without approval flow ** this flow should only appear for documents which are copied by functionality\'Create copied VNAS SI and PI\'"", \'Comment 84: for other documents (not created by this action - \\\'Create copied VNAS SI and PI\\\' - flow from \\\'Entry\\\' to \\\'Archive\\\' shouln\\\'t be available""\', \'Comment 85: ""CONFIRMED - External Document Number should be calculated and created from other data and should looks like that 803319/A/2023/02803319 - Code from ReferenceA - manually added symbol\', ""Comment 86: copying when coument is copying by action2023 - year - taken from current date of invoicing (date from creation date of document)02 - month - taken from current date of invoicing (date from creation date of document)Main rules for these calculation for External Document Number will be always uniqueCONFIRMEDdocument will be created in month of real creation of itdocument will be created once per month for this type of invoiceCONFIRMEDShould be created new flows for documents which are copying 1:1 - without changes in data on invoices (for PI and SI documents)should be possible to perform flow from \'Entry\' to \'Archive\' directly without approval flowthis flow should only appear for documents which are copied by functionality \'Create copied VNAS SI and PI\'"", \'Comment 87: for other documents (not created by this action - \\\'Create copied VNAS SI and PI\\\' - flow from  \\\'Entry\\\' to \\\'Archive\\\' shouln\\\'t be available""\', ""Comment 88: \'{color:black}Good day,{color} {color:black}{color} {color:black}We have an adaptation in our process requirement.{color} {color:black}It should be regular PI to registered SI.{color} # {color:#172B4D} This is WRONG: Copy of all selected documents are created - (PI -> new PI"", \'Comment 89: SI (based on PI Leading doc) -> new SI){color}  {color:#172B4D}GOOD: PI -> new PI (regular)\', \'Comment 90: SI (based on PI Leading doc) -> new SI (registered){color}  {color:black}Please confirm if this is clear.{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Christinede{color} |{color:#000001} {color} |{color:#000001} Jong{color} |  {color:#000001}MedewerkerContractadministratie{color} | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.de-heus.nl/]>{color} | |  *{color:#006FB7} *DEHEUSVOEDERSB.V.*{color}* | | | |{color:#000001} Postbus396 6710BJEde \\\\u200b{color} | |{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} | | |{color:#000001} T:0318675567{color} |  {color:#000001}KvK14626985{color}   _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | | !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | | !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} | | !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} |        *Van:* Mitch van Bovene (Jira) <jira@kotrak.com>   *Verzonden:* dinsdag 7 maart 2023 13:11  *Aan:* Jong\', ""Comment 91: Christine de <CJong@deheus.com>  *Onderwerp:* DGS-8081 Ready for UAT tests (partly) - Process adjustments deposits (now VERG)   \'"", \'Comment 92: ""Ok\', \'Comment 93: so for each document which will be copied by action\\\'Create copied VNAS SI and PI\\\' (copy 1:1 - without changes in data on invoices) it should be created PI regular (copy of old PI regular with calculated fields) and then it should be created SI registered.""\', ""Comment 94: \'Indeed.\'"", ""Comment 95: \'{color:black}Dear Damian,{color} {color:black}{color} {color:black}What is the status of this project? We would like to make a full test before implementation.{color} {color:black}{color} {color:black}Furthermore"", \'Comment 96: our financial management has decided that process of booking should be regular{color} {color:black}à{color}{color:black} regular as per 01-04-2023.{color} {color:black}Relations for this booking change will be set by the project managers. We think that this should not have implications for Intense. As my posting will be from 01-04-2023 regular{color} {color:black}à{color}{color:black} regular. When I make a copy of this in the VNAS\', \'Comment 97: system will pick-up.{color} {color:black}Can you confirm this thought?{color} {color:black}{color} {color:black}Thanks for your feedback.{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Christinede{color} |{color:#000001} {color} |{color:#000001} Jong{color} |  {color:#000001}MedewerkerContractadministratie{color} | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.de-heus.nl/]>{color} | |  *{color:#006FB7} *DEHEUSVOEDERSB.V.*{color}* | | | |{color:#000001} Postbus396 6710BJEde \\\\u200b{color} | |{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} | | |{color:#000001} T:0318675567{color} |  {color:#000001}KvK14626985{color}   _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | | !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | | !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} | | !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} |        *Van:* Damian Świstek (Jira) <jira@kotrak.com>   *Verzonden:* vrijdag 10 maart 2023 13:26  *Aan:* Jong\', ""Comment 98: Christine de <CJong@deheus.com>  *Onderwerp:* DGS-8081 Ready for UAT tests (partly) - Process adjustments deposits (now VERG)   \'"", \'Comment 99: ""Hi Christine,Unfortunately due to other urgent topics we didn\\\'t make much progress in this topic.We\\\'ll try to do this as soon as possible and I\\\'ll let you know when it will be ready for another tests.{quote}{color:#000000}Furthermore\', \'Comment 100: our financial management has decided that process of booking should be regular{color}{color:#000000}à{color}{color:#000000}regular as per 01-04-2023.{color}{color:#000000}Relations for this booking change will be set by the project managers. We think that this should not have implications for Intense. As my posting will be from 01-04-2023 regular{color}{color:#000000}à{color}{color:#000000}regular. When I make a copy of this in the VNAS\', \'Comment 101: system will pick-up.{color}{color:#000000}Can you confirm this thought?{color}{quote}{color:#000000}What do you mean regularàregular? Can it happen that some assumptions from this taks can change?{color}{color:#000000}Should it works like it was described before?{color}{quote}{color:#000000}Ok\', \'Comment 102: so for each document which will be copied by action\\\'Create copied VNAS SI and PI\\\' (copy 1:1 - without changes in data on invoices) it should be created PI regular (copy of old PI regular with calculated fields) and then it should be created SI registered.{color}{quote}{color:#000000}Regards,{color}{color:#000000}Damian{color}""\', ""Comment 103: \'{color:black}Hi Damian,{color} {color:black}{color} {color:black}Thanks for your message.{color}  {color:black}Okay if it can be prioritized again it would be of much help to me. Process now is very inefficient.{color} {color:black}{color} {color:black}Indeed in process it is back to first set-up regular{color} {color:black}à{color}{color:black} regular.{color}  {color:black}Not regular{color} {color:black}à{color}{color:black} registration.{color} {color:black}{color} {color:black}{color} {color:black}{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Christinede{color} |{color:#000001} {color} |{color:#000001} Jong{color} |  {color:#000001}MedewerkerContractadministratie{color} | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.de-heus.nl/]>{color} | |  *{color:#006FB7} *DEHEUSVOEDERSB.V.*{color}* | | | |{color:#000001} Postbus396 6710BJEde \\\\u200b{color} | |{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} | | |{color:#000001} T:0318675567{color} |  {color:#000001}KvK14626985{color}   _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | | !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | | !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} | | !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} |        *Van:* Damian Świstek (Jira) <jira@kotrak.com>   *Verzonden:* donderdag 30 maart 2023 13:17  *Aan:* Jong"", ""Comment 104: Christine de <CJong@deheus.com>  *Onderwerp:* DGS-8081 Ready for UAT tests (partly) - Process adjustments deposits (now VERG)   \'"", \'Comment 105: \\\'Hi [~CJong@deheus.com],we\\\\\\\'ve made changes on VNAS process:1. Added new generation for external document number (for copied PI invoices).2. Added new flow for VNAS documents (entry -> archive).You can verify it from list ""Purchas Invoices (VNAS)"".Best regards,Grzegorz\\\'\', ""Comment 106: \'{color:black}Hi Grzegorz,{color} {color:black}{color} {color:black}It works! Thanks a lot.{color} {color:black}Please make it available for PROD.{color} {color:black}{color} {color:black}Can you prioritize that VNAS item is available next week. So that I can make the deposits for 04-2023 with VNAS item code.{color}  {color:black}Than we can use the copy function starting 05-2023.{color} {color:black}{color} {color:black}Thanks a lot"", \'Comment 107: to the whole team\', \'Comment 108: this is a great efficiency approvement.{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Christinede{color} |{color:#000001} {color} |{color:#000001} Jong{color} |  {color:#000001}MedewerkerContractadministratie{color} | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.de-heus.nl/]>{color} | |  *{color:#006FB7} *DEHEUSVOEDERSB.V.*{color}* | | | |{color:#000001} Postbus396 6710BJEde \\\\u200b{color} | |{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} | | |{color:#000001} T:0318675567{color} |  {color:#000001}KvK14626985{color}   _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | | !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | | !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} | | !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} |        *Van:* Grzegorz Materla (Jira) <jira@kotrak.com>   *Verzonden:* vrijdag 14 april 2023 09:55  *Aan:* Jong\', ""Comment 109: Christine de <CJong@deheus.com>  *Onderwerp:* DGS-8081 Ready for UAT tests (partly) - Process adjustments deposits (now VERG)   \'"", \'Comment 110: ""Hi [~CJong@deheus.com],we\\\'ve moved all functionality into PROD Intense environment. We have also prepared special role for VNAS document list and we have already pinned you and Mitch:!image-2023-04-21-09-27-04-212.png!If you want add more users please provide us with names.Best regards,Grzegorz""\', ""Comment 111: \'{color:black}Hi Grzegorz,{color} {color:black}{color} {color:black}Thanks for your action.{color}  {color:black}NAS functionality should be available for me and Bert Geijtenbeek.{color} {color:black}{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} | | | |{color:#000001} Christinede{color} |{color:#000001} {color} |{color:#000001} Jong{color} |  {color:#000001}MedewerkerContractadministratie{color} | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.de-heus.nl/]>{color} | |  *{color:#006FB7} *DEHEUSVOEDERSB.V.*{color}* | | | |{color:#000001} Postbus396 6710BJEde \\\\u200b{color} | |{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} | | |{color:#000001} T:0318675567{color} |  {color:#000001}KvK14626985{color}   _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | | !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | | !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} | | !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} |        *Van:* Grzegorz Materla (Jira) <jira@kotrak.com>   *Verzonden:* vrijdag 21 april 2023 09:33  *Aan:* Jong"", ""Comment 112: Christine de <CJong@deheus.com>  *Onderwerp:* DGS-8081 Ready for UAT tests (partly) - Process adjustments deposits (now VERG)   !image006-1!\'"", \'Comment 113: ""Ok,Bert has also access to this list.One more thing is to verify that item in Intense is configured properly\', ""Comment 114: we see 2 items in Intense. 1st one with name \'Vergoeding NAS\' we configured as on Test database. We\' re not sure why there are 2 items"", \'Comment 115: one looks like created manually and 2nd like sent from Milas.!image-2023-04-21-12-35-27-347.png!!image-2023-04-21-12-36-50-035.png!2nd with other name \\\'Vergoeding NAS_VNAS\\\' is congifured like that: !image-2023-04-21-12-37-05-224.png!Please verify it and maybe make some test on Test database aslo with archiving these documents with VNAS code and see that it will go to Milas properly.""]\']\nRelated Issues:\n[\'DGS-8324\']\n\n### End'}"
951,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8080\n\n### Instruction:\nHello,\r\n\r\nWe miss 3 catergories on the round of Reimert 101619/0023/0001.\r\nPlease add, Calves/Expenses-Feed/Slaughtery.\r\n\r\nWe need this information to be able to close the round. If it can be made priority it would be of much help.\r\n\r\nKR Christine\r\n\n\n### Response:\n[""Comment 1: [\'[^Purchase_migration_Reimert 101619-1.xlsx] _(20 kB)_[^Sales_migration_Reimert 101619-1.xlsx] _(19 kB)_\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'The files have been checked"", ""Comment 4: and they were sent to Grzegorz. To be planned based on the current backlog.\'"", ""Comment 5: \'Grzegorz has migrated the files. Christine"", ""Comment 6: please verify if everything is OK :)\'"", ""Comment 7: \'Dodane do listy z podsumowaniem wysłanej do klienta.\'"", ""Comment 8: \'Everything is okay. Thanks for migration. File is complete\']""]\nRelated Issues:\n[]\n\n### End'}"
952,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8079\n\n### Instruction:\nDear Service Desk \r\nWe have experienced a problem in DHPlant on Accepting and Confirming production lot reports on the listed Lot Numbers. \r\nWe never had this kind of problem before so ; if anyone who is able to assist us in solving the problem would be so helpful .\r\nThis are the lot reports denied to accept and confirm with the Error massage.  (Attached)\r\n\r\nLot number\r\n0415131222006/ 0415131222005/ 0415131222003/ 0415131222002/ 0415121222006\r\n0415121222005/ 0415121222001/ 0415101222010/ 0415101222008/ 0415101222007\r\n0415101222004/ 0415101222003/ 0415101222002/ 0415091222006\r\n\r\nThanks in Advance \r\n\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Thanks very Much  We wait for you. \'"", ""Comment 3: \'Good morning,Please attach the error Message indicates tolerance"", ""Comment 4: !image-2022-12-16-12-17-25-102.png|width=1495,height=783!Raw production Valid ? Is the user role set ? !image-2022-12-16-12-21-59-368.png!Regards\'"", \'Comment 5: \\\'{code:java}022-12-16 14:29:51 (e9ef4f10-b4ae-4048-8a60-41df7735adab/Plant.Prod.BusinessLogic/ETDB04/12476/111) [Error] Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware - Error during request{  ""scheme"": ""http""\', \'Comment 6:  ""host"": {    ""Value"": ""10.103.3.33:83""\', \'Comment 7:    ""HasValue"": true\', \'Comment 8:    ""Host"": ""10.103.3.33""\', \'Comment 9:    ""Port"": 83  }\', \'Comment 10:  ""path"": ""/api/productionLot/update""\', \'Comment 11:  ""queryString"": []\', \'Comment 12:  ""requestBody"": ""{\\\\\\\\""elements\\\\\\\\"":[{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":1,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""04167494-ebf7-46ad-ac04-11e526b26b86\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":8622.887},\\\\\\\\""description\\\\\\\\"":null},{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":2,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""77c37b5a-8668-425c-870f-00fedc43d6da\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":2402.233},\\\\\\\\""description\\\\\\\\"":null},{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":3,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""8f643e2c-f2af-4f84-9899-bc0d0ca93acc\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":5040.365},\\\\\\\\""description\\\\\\\\"":null},{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":4,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""c4461a25-a85d-4948-b9ae-83549ce2b6ff\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":120.964},\\\\\\\\""description\\\\\\\\"":null},{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":5,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""37b8e22a-4e7c-4c8c-a064-cca2179bebfa\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":1504.411},\\\\\\\\""description\\\\\\\\"":null},{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":6,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""c148f2cb-b821-4370-9ea3-ed9f44fc0c0e\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":1017.799},\\\\\\\\""description\\\\\\\\"":null},{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":7,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""0e1d846b-db85-42b4-87e9-99953a68f015\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":4259.599},\\\\\\\\""description\\\\\\\\"":null},{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":8,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""1ea1388f-851e-41b2-ae58-57e94e9253c0\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":613},\\\\\\\\""description\\\\\\\\"":null},{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":9,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""11edbf16-5303-42a3-854a-5b44db0b32a4\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":685.084},\\\\\\\\""description\\\\\\\\"":null},{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":10,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""b760843d-7131-4900-8275-35044f545d45\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":1561.572},\\\\\\\\""description\\\\\\\\"":null},{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":11,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""0d1662a5-43a4-4a31-89ad-42c401424983\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":30281.895},\\\\\\\\""description\\\\\\\\"":null},{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":12,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""7f225535-0db8-4ea2-9e5a-2ab2a18f60f2\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":120.344},\\\\\\\\""description\\\\\\\\"":null},{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":13,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""52abdb1b-bb1c-4d2e-8b49-c6d92c2de176\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":180},\\\\\\\\""description\\\\\\\\"":null},{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":14,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""e5cd69cf-ea6e-4821-ac7e-955bd4abb1a0\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":626.908},\\\\\\\\""description\\\\\\\\"":null},{\\\\\\\\""substitutes\\\\\\\\"":[],\\\\\\\\""recipeElementId\\\\\\\\"":15,\\\\\\\\""itemId\\\\\\\\"":\\\\\\\\""627dfb57-370f-4e2a-b83e-f38f60fc1b90\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":3005.108},\\\\\\\\""description\\\\\\\\"":null}],\\\\\\\\""executions\\\\\\\\"":[{\\\\\\\\""elements\\\\\\\\"":[],\\\\\\\\""readyProductId\\\\\\\\"":\\\\\\\\""1ef655dc-4d13-469e-a955-e58f7aee615b\\\\\\\\"",\\\\\\\\""packingRecipeId\\\\\\\\"":\\\\\\\\""c927c795-a570-42e6-b19e-e6fc52dba462\\\\\\\\"",\\\\\\\\""quantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":60042.169},\\\\\\\\""requestedQuantity\\\\\\\\"":{\\\\\\\\""unit\\\\\\\\"":\\\\\\\\""kg\\\\\\\\"",\\\\\\\\""value\\\\\\\\"":60000},\\\\\\\\""expiryDate\\\\\\\\"":\\\\\\\\""2023-06-09T15:51:34.476Z\\\\\\\\""}],\\\\\\\\""reservations\\\\\\\\"":[],\\\\\\\\""productionLotId\\\\\\\\"":\\\\\\\\""79fdfac7-7f09-48bc-bd8f-50aa29f7f97c\\\\\\\\"",\\\\\\\\""recipeId\\\\\\\\"":\\\\\\\\""c927c795-a570-42e6-b19e-e6fc52dba462\\\\\\\\"",\\\\\\\\""labelId\\\\\\\\"":null,\\\\\\\\""productionOrderId\\\\\\\\"":\\\\\\\\""3163ad39-d59a-4894-a5d8-2fb3698d692d\\\\\\\\"",\\\\\\\\""businessPartnerId\\\\\\\\"":null,\\\\\\\\""shiftNumberId\\\\\\\\"":null,\\\\\\\\""description\\\\\\\\"":null,\\\\\\\\""statusChange\\\\\\\\"":3}""}.System.AggregateException: One or more errors occurred. (Response status code does not indicate success: 400 (Bad Request).) ---> Refit.ApiException: Response status code does not indicate success: 400 (Bad Request).   at Refit.RequestBuilderImplementation.<>c__DisplayClass14_0`2.<<BuildCancellableTaskFuncForMethod>b__0>d.MoveNext() in d:\\\\\\\\a\\\\\\\\1\\\\\\\\s\\\\\\\\Refit\\\\\\\\RequestBuilderImplementation.cs:line 273   --- End of inner exception stack trace ---   at System.Threading.Tasks.Task`1.GetResultCore(Boolean waitCompletionNotification)   at Plant.Prod.BusinessLogic.Infrastructure.ContextIntegration.ApiServices.StockEngine.StockEngineApi.UpdateReservationsAndConfirmProductionLot(AggregateId productionLotId\', \'Comment 13: AggregateId businessUnitId\', \'Comment 14: Quantity productionQuantity\', \'Comment 15: IEnumerable`1 settlementData\', \'Comment 16: IEnumerable`1 dosingSiloItemData) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Infrastructure.ContextIntegration\\\\\\\\ApiServices\\\\\\\\StockEngine\\\\\\\\StockEngineApi.cs:line 132   at Plant.Prod.BusinessLogic.Domain.ProductionLots.ConfirmProductionLotDomainService.UpdateReservationsAndConfirmProductionLot(ProductionLot productionLot\', \'Comment 17: ConfirmProductionLotActionData data\', \'Comment 18: IEnumerable`1 reservations\', \'Comment 19: IEnumerable`1 dosingSiloItemData) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Domain\\\\\\\\ProductionLots\\\\\\\\ConfirmProductionLotDomainService.cs:line 82   at Plant.Prod.BusinessLogic.Application.ProductionLots.ProductionLotService.UpdateProductionLot(UpdateProductionLotActionData data) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Application\\\\\\\\ProductionLots\\\\\\\\ProductionLotService.cs:line 308   at Plant.Prod.BusinessLogic.Application.ProductionLots.CommandHandlers.UpdateProductionLotCommandHandler.Handle(UpdateProductionLotCommand command) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Application\\\\\\\\ProductionLots\\\\\\\\CommandHandlers\\\\\\\\UpdateProductionLotCommandHandler.cs:line 39   at Kotrak.Common.Infrastructure.Commands.CommandEnvironment.Run[TCommand](TCommand command)   at Kotrak.Common.Infrastructure.Commands.Decorators.IntercontextEventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command)   at Kotrak.Common.Infrastructure.Commands.Decorators.EventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command)   at Kotrak.Common.Infrastructure.Commands.Decorators.ValidationCommandEnvironmentDecorator.Run[TCommand](TCommand command)   at Castle.DynamicProxy.AbstractInvocation.Proceed()   at Kotrak.Common.Infrastructure.Interceptors.LoggingInterceptor`1.Intercept(IInvocation invocation)   at Castle.DynamicProxy.AbstractInvocation.Proceed()   at Kotrak.Common.Infrastructure.Commands.Decorators.HistoryGateDecorator.Dispatch[TCommand](TCommand command)   at Plant.Prod.BusinessLogic.Infrastructure.Api.Controllers.ProductionLotController.UpdateProductionLot(UpdateProductionLotViewModel viewModel) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\957197a90f25e5f0\\\\\\\\Plant.Production.BusinessLogic\\\\\\\\Infrastructure.Api\\\\\\\\Controllers\\\\\\\\ProductionLotController.cs:line 106   at lambda_method(Closure \', \'Comment 20: Object \', \'Comment 21: Object[] )   at Microsoft.Extensions.Internal.ObjectMethodExecutor.Execute(Object target\', \'Comment 22: Object[] parameters)   at Microsoft.AspNetCore.Mvc.Internal.ActionMethodExecutor.SyncObjectResultExecutor.Execute(IActionResultTypeMapper mapper\', \'Comment 23: ObjectMethodExecutor executor\', \'Comment 24: Object controller\', \'Comment 25: Object[] arguments)   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.InvokeActionMethodAsync()   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.InvokeNextActionFilterAsync()   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.Rethrow(ActionExecutedContext context)   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.Next(State& next\', \'Comment 26: Scope& scope\', \'Comment 27: Object& state\', \'Comment 28: Boolean& isCompleted)   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.InvokeInnerFilterAsync()   at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.InvokeNextResourceFilter()   at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.Rethrow(ResourceExecutedContext context)   at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.Next(State& next\', \'Comment 29: Scope& scope\', \'Comment 30: Object& state\', ""Comment 31: Boolean& isCompleted)   at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.InvokeFilterPipelineAsync()   at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.InvokeAsync()   at Microsoft.AspNetCore.Builder.RouterMiddleware.Invoke(HttpContext httpContext)   at Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware.Invoke(HttpContext httpContext)---> (Inner Exception #0) Refit.ApiException: Response status code does not indicate success: 400 (Bad Request).   at Refit.RequestBuilderImplementation.<>c__DisplayClass14_0`2.<<BuildCancellableTaskFuncForMethod>b__0>d.MoveNext() in d:\\\\\\\\a\\\\\\\\1\\\\\\\\s\\\\\\\\Refit\\\\\\\\RequestBuilderImplementation.cs:line 273<---{code}\'"", ""Comment 32: \'Hello Dear we tried now to edit salt and accept confirm then this error message still appers  raw production is valid and the user role is set fro production yes ;  see attached error message!image002!!image003!!buz 2.PNG|thumbnail!\'"", ""Comment 33: \'Hello"", ""Comment 34: Please Verify production lot reports “0415131222003”Regards\'"", ""Comment 35: \'Hi dear  yes this lot reports “0415131222003” is verified and accepted  this one worked great . Thanks\'"", ""Comment 36: \'Hello Gemechis"", \'Comment 37: I have resubmitted the batch reports.The reason\', ""Comment 38: out of stock items.Please check Lot number.0415131222006/ 0415131222005/ 0415131222003/ 0415131222002/ 04151212220060415121222005/ 0415121222001/ 0415101222010/ 0415101222008/ 04151012220070415101222004/ 0415101222003/ 0415101222002/ 0415091222006Regards\'"", ""Comment 39: \'Dear  sorry for the late replay ; but this lot number verified  0415101222007/ 0415101222004/ 0415101222003/ 0415101222002/ 0415091222006/0415131222003 0415121222001/ 0415101222008/0415121222005/  We are also trying verify the rest will tell you the result  thanks so much and respect\'"", \'Comment 40: ""I\\\'m waiting for feedbackYou can close your incident?The problem has been resolved? Regards""\', ""Comment 41: \'Dear  Ok I will close the ticket But this one is still rejecting not accepting  0415121222003\'"", ""Comment 42: \'Hello"", \'Comment 43: Please verify \', ""Comment 44: 0415121222003.You can close your incident?Regards\'"", ""Comment 45: \'Thanks very much  Now we have closed / Verified all the lot Report we had faced problem Accepting ;  Thanks very much Again @Adrian Kozak for your time and support .  Much appreciated  Regards\'"", ""Comment 46: \'Thanks a lot.\']""]\nRelated Issues:\n[]\n\n### End'}"
953,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8078\n\n### Instruction:\nKontenery dostają status 999 (czyszczenia), pomimo wyczyszczenia nadal dostają status 999 i tak od nowa. Produkcja zatrzymana.\r\nWcześniej pojawiały się liczne błędy:\r\nId 6109642 -finish transfer\r\n6109533 – register transfer error 5:1\r\nOstatni log z błędem 20:15\r\n\n\n### Response:\n[""Comment 1: [\'[^komunikat błędu.txt] _(3 kB)_!obraz!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Please check if problem still occurs\'"", ""Comment 4: \'Nadal jest komunikat 999"", ""Comment 5: powinien być do gotowy do zasypu. \'"", ""Comment 6: \'Please check now\'"", ""Comment 7: \'pokazał się błąd id 6110188\'"", ""Comment 8: \'!obraz-1!\'"", ""Comment 9: \'Please check if problem still occurs\'"", ""Comment 10: \'Problem dalej występuje.Kontenery jeżdżą w kółko do czyszczenia.Produkcja stoi"", ""Comment 11: temat ktyryczny !\'"", ""Comment 12: \'Błąd nie dotyczy silosu tylko transportu\'"", \'Comment 13: ""Problem still occurs. Production can\\\'t produce. When will problem resolved?""\', ""Comment 14: \'We are working on solution with our dev team. I will give you feedback as soon as possible.\'"", ""Comment 15: \'Hi,Can you please check?!image-2022-12-16-09-40-12-729.png!\'"", \'Comment 16: ""I\\\'ve verified VPN connection right now and it\\\'s working. Please restart FortiClient and try again.""\', ""Comment 17: \'Messages for this production has been cancelled yesterday. Please provide us why?!image-2022-12-16-10-14-01-704.png!\'"", ""Comment 18: \'Messages have been incorrectly removed as requested by the reporter.\'"", ""Comment 19: \'Please check conatiners now\'"", ""Comment 20: \'communication should be working right now. Please verify\'"", ""Comment 21: \'msg_id 6110637 - error:System.Web.Services.Protocols.SoapException: Serwer nie może przetworzyć żądania. ---> StartTransfer error: System.Data.SqlClient.SqlException (0x80131904): StartTransferError 2: Transfer from silo containing different article\'"", ""Comment 22: \'Please check current queue"", ""Comment 23: looks like since 12:39 all messages are with status 0 \'"", ""Comment 24: \'containers are cleaning all the time"", ""Comment 25: it can be caused by PCS-DHP error reported while ago. \'"", ""Comment 26: \'Please provide us wchih art_id is right:!image-2022-12-16-14-07-42-650.png!\'"", ""Comment 27: \'art_id 27579 poprawny915752-W25 był dla lotu 28 transferowany z p46033 do p46063\'"", ""Comment 28: \'Also there areResidues in destination codep46063. As I understand it should be empty am I right?!image-2022-12-16-14-38-59-823.png!\'"", ""Comment 29: \'all tanks are emptied and cleaned\'"", ""Comment 30: \'We cleaned entries in database . please verify\'"", ""Comment 31: \'is correct"", ""Comment 32: no error shows\']""]\nRelated Issues:\n[]\n\n### End'}"
954,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8077\n\n### Instruction:\nQuestion from my collegue Koen. These invoices are on round B004145/0035/0001, but should be on round B004145/0035/0002. Financially everything is right, so can you move these documents in Intense?\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'SteffenCould you and Koen try to do it by yourself?!image-2022-12-16-10-27-22-596.png|width=1108,height=293!!image-2022-12-16-10-28-39-443.png!\'"", ""Comment 4: \'I was able to change the round so we can now. Thank you!!image-1!\'"", ""Comment 5: \'Great! This action works only in case of Slaughtery Report invoices. After using this action the system changes Round Number in: SR"", \'Comment 6: SI and PI. This is very important to keep the same Round number in these three documents\', ""Comment 7: otherwise the Technical Results will no be calculated properly.\']""]\nRelated Issues:\n[]\n\n### End'}"
955,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8076\n\n### Instruction:\nThe recipe 3921.030 does not appear in DHC even though it is available in DHC and the technology has been generated properly.\n\n### Response:\n[""Comment 1: [\'!1.jpg|thumbnail!!2.jpg|thumbnail!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 3: ""System.Data.Entity.Infrastructure.DbUpdateException: An error occurred while updating the entries. See the inner exception for details. ---> System.Data.Entity.Core.UpdateException: An error occurred while updating the entries. See the inner exception for details. ---> System.Data.SqlClient.SqlException: Cannot insert duplicate key row in object \\\'dbo.Items\\\' with unique index \\\'IX_Code\\\'. The duplicate key value is (3204010).The statement has been terminated.""\', \'Comment 4: \\\'brak itemu w dhc service przy update z poziumu dhc linkowania2022-12-15 15:26:15,427 [35] INFO Evolution.DHCService.Dhc30.Handlers.ItemChangedMessageHandler [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\31916033\\\\\\\\DHAPPSV3-DHCSER497-JOB1\\\\\\\\Evolution.DHCService\\\\\\\\Evolution.DHCService.Dhc30\\\\\\\\Handlers\\\\\\\\BaseMessageHandler.cs:37] - Receiving message (Evolution.DHCountry.Interfaces.Items.ItemChangedMessage) [Id:bd7b72a3-7c5a-11ed-86ea-ccca08f7b613]2022-12-15 15:26:15,427 [35] ERROR Evolution.DHCService.Dhc30.Handlers.ItemChangedMessageHandler [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\31916033\\\\\\\\DHAPPSV3-DHCSER497-JOB1\\\\\\\\Evolution.DHCService\\\\\\\\Evolution.DHCService.Dhc30\\\\\\\\Handlers\\\\\\\\BaseMessageHandler.cs:55] - Cannot handle message (Evolution.DHCountry.Interfaces.Items.ItemChangedMessage). Exception occured:2022-12-15 15:26:15,427 [35] ERROR Evolution.DHCService.Dhc30.Handlers.ItemChangedMessageHandler [E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\31916033\\\\\\\\DHAPPSV3-DHCSER497-JOB1\\\\\\\\Evolution.DHCService\\\\\\\\Evolution.DHCService.Dhc30\\\\\\\\Handlers\\\\\\\\BaseMessageHandler.cs:56] - System.Data.Entity.Infrastructure.DbUpdateException: An error occurred while updating the entries. See the inner exception for details. ---> System.Data.Entity.Core.UpdateException: An error occurred while updating the entries. See the inner exception for details. ---> System.Data.SqlClient.SqlException: The INSERT statement conflicted with the FOREIGN KEY constraint ""FK_dbo.Items_dbo.DhhItems_DhhItemId"". The conflict occurred in database ""DHCService_UA_Test""\', \'Comment 5: table ""dbo.DhhItems""\', ""Comment 6: column \\\\\'Id\\\\\'.The statement has been terminated.\'"", ""Comment 7: \'Please verify should be ok now!image-2022-12-15-14-48-49-764.png!\'"", ""Comment 8: \'Yes"", \'Comment 9: we see\', ""Comment 10: thank you\'"", ""Comment 11: \'May we close the task?\'"", ""Comment 12: \'Yes\']""]\nRelated Issues:\n[]\n\n### End'}"
956,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8075\n\n### Instruction:\nFurthermore, we have a question regarding the types of hatchery invoices. In almost every case where we put in a hatchery invoice which should be settled in the saldo (regular or financed, not registration), we use financed. In that case, the customer gets the invoice from the hatchery but we have to finance it for the customer. In that case, we thus do not send the invoice created from Milas (because the customer already has the invoice from the hatchery). Right now, the printouts still use the invoice number from Milas (as it gets posted in Milas, which is also correct), but Koen and I were wondering if we could use the external document number on the invoice from the hatchery instead. So only in the following case: Financed PI and SI on hatchery round category. For regular invoices on hatchery round, the Milas SI number can be showed, as we do sent the invoice to the customer then.\r\nWe would like to hear from you if this is possible.\r\n\n\n### Response:\n[\'Comment 1: [\\\'Financial Statement Printout in MAS BE:In case of Financed SI/PI the system must show the ""External Number"" instead of the ""Document Number ERP"" field in the ""Document nr"" column.Regular/Registration invoices remains as they are (Regular- Document Number ERP\', \'Comment 2: Registartion- Intense PI/SI Document Number)Purchase Invoice- External Document NumberDoc_ShortStringColumn19Sales invoice- no External Document NumberSteffen\', \'Comment 3: there is no External Document Number field in Sales Invoice\', ""Comment 4: could you please tell us how we should manage this?\'"", ""Comment 5: \'We would like the external invoice number from the PI to come through on SI invoices on printouts as well. This invoice+number is sent from the hatchery directly to the customer"", \'Comment 6: so they both ""know"" this external document number. To finalize\', ""Comment 7: is this possible only for financed HATCHERY invoices?\'"", \'Comment 8: \\\'Yes. I forgot to write this is related to the Hatchery financed invoices.ADJUSTED STATEMENT: Financial Statement Printout in MAS BE:In case of Financed HATCHERY SI/PI the system must show the ""External Number"" from PI instead of the ""Document Number ERP"" field in the ""Document nr"" column.Nothing change for Regular/Registration invoicesPurchase Invoice/ External Document Number: Doc_ShortStringColumn19\\\'\', ""Comment 9: \'[~ewa.mucha@kotrak.com]"", ""Comment 10: done for FS. You can feel free to test it ;)\'"", ""Comment 11: \'Grzesiu"", ""Comment 12: UAT?\'"", ""Comment 13: \'Dodane do wewnętrznego podsumowania tasków.\'"", ""Comment 14: \'[~ewa.mucha@kotrak.com]UAT :)\'"", ""Comment 15: \'!image-2022-12-28-15-23-41-098.png|width=841,height=347!!image-2022-12-28-15-24-03-549.png|width=803,height=139!!image-2022-12-28-15-24-36-997.png|width=779,height=351!\'"", ""Comment 16: \'[~grzegorz.materla@kotrak.com]sprawdziłam na FS ID78688 i system wyświetla numer ERP zamiast External Number z PI\'"", ""Comment 17: \'[~ewa.mucha@kotrak.com]"", \'Comment 18: rzeczywiście kolumna która była wyświetlana to ERP nr.\', \'Comment 19: a nie Document nr. tak jak sugerował wydruk\', ""Comment 20: aktualnie zaktualizowałem i działa.Pozdrawiam,Grzegorz\'"", ""Comment 21: \'Przetestowane i działa na UAT.DHNLC-1209\'"", ""Comment 22: \'Steffen"", \'Comment 23: this was adjusted in the system. Could you please test this on IBIP_DH_TEST? After your confirmation everything is correct\', ""Comment 24: the changes will be deployed on PROD>!image-2022-12-28-16-01-52-834.png!\'"", ""Comment 25: \'{color:black}Hello Ewa,{color} {color:black}{color} {color:black}This seems to be correct for the FS"", \'Comment 26: but I don’t see a modification on the S2P in the test environment.{color} {color:black}{color} {color:black}First\', \'Comment 27: on the S2P\', \'Comment 28: the external document number is showed under document nr.{color} {color:black}{color} !image001!{color:black}{color} {color:black}{color} {color:black}Second\', \'Comment 29: on the S2P\', \'Comment 30: I still see the SIB numbers for hatchery invoices (first two lines on the printout){color} {color:black}{color} !image009!{color:black}{color} {color:black}{color} | |{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}SalutationsCordiales{color} | | | |{color:#000001} Steffen{color} |{color:#000001} {color} |{color:#000001} Driesen{color} | | | |{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image002!{color:black} <[https://www.de-heus.nl/]>{color} | |  *{color:#006FB7} *DEHEUSVOEDERSBELGIEN.V.*{color}* | | |{color:black} {color} | |{color:#000001} LouisPasteurstraat11/201 \\\\u200b3920Lommel{color} | | |{color:#000001} M:{color}{color:#000001}{color}{color:#000001}+32-11-546672{color}{color:#000001} <tel:+32%20-%2011%20-%2054%2066%2072>{color} |  {color:#000001}Ondernemingsnummer:0437.737.739{color} |  _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ | | | !image003! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} | | !image004! <[https://twitter.com/de_heus_voeders]>{color:black}{color} | | !image005! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} | | !image006! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} | |{color:black}{color} !image007.jpg|thumbnail!{color:black}{color} |      *Van:* Ewa Mucha (Jira) <jira@kotrak.com>   *Verzonden:* woensdag 28 december 2022 16:03  *Aan:* Driesens\', ""Comment 31: Steffen <SDriesen@deheus.com>  *Onderwerp:* DGS-8075 Financial Statement printout update for financed hatechery invoice   |  *{color:white} *CAUTION: This message originated from outside the organisation. Please do not click on links or open attachments unless you trust the sender and know the content is safe.*{color}* |   !image008!\'"", ""Comment 32: \'[~ewa.mucha@kotrak.com]"", ""Comment 33: z tego co widzę to klient chce takie zmiany jeszcze na S2P wydruku.\'"", ""Comment 34: \'Steffen"", ""Comment 35: could you please specify what has to be adjusted in the S2P printout? Only FS printout was modified.\'"", \'Comment 36: ""If possible\', \'Comment 37: we would like to see the same external document number on the S2P (under \\\'factuurnummer\\\' for this case (financed hatchery invoices). So the same number as the one used on the FS under document nr.!image!""\', ""Comment 38: \'[~grzegorz.materla@kotrak.com] jesteśmy w stanie rozróżnć hatchery invoices od pozostałych na wydruku S2P?\'"", ""Comment 39: \'[~grzegorz.materla@kotrak.com]sprawdzisz to ?\'"", ""Comment 40: \'[~ewa.mucha@kotrak.com],[~damian.swistek@kotrak.com]"", \'Comment 41: tak\', \'Comment 42: możemy sięgnąć do faktur\', ""Comment 43: które istnieją w systemie i są powiązane z S2P aby zweryfikować czy jest to Hatchery.\'"", ""Comment 44: \'Question"", \'Comment 45: could we enlarge this principle for all financed invoices? We do get a few financed invoices other than hatchery invoices (veterinary costs\', ""Comment 46: slaughtery reports as well,...)\'"", ""Comment 47: \'Hello"", ""Comment 48: do you have the current status for this?\'"", ""Comment 49: \'Hello Steffen,Could you confirm changes are needed on printouts?Should we change FS printout and also S2P printout"", \'Comment 50: right?Changes are related to the old printouts (printous which you use right now\', \'Comment 51: not new layout for Coppens)?Is it requirement correct? It should be applied to all Financed SI/PI invoices instead \\\\\\\'Financed HATCHERY SI/PI\\\\\\\'{quote}In case of Financed HATCHERY SI/PI the system must show the ""External Number"" from PI instead of the ""Document Number ERP"" field in the ""Document nr"" column.Nothing change for Regular/Registration invoicesPurchase Invoice/ External Document Number: Doc_ShortStringColumn19{quote}Now we\\\\\\\'re working on new Financial statement printout and S2P printout (regarding Coppens new layout) and it\\\\\\\'s priority and then we can adjust printouts for MAS BE which you use right now. I think it could be handleat the earliest on next week.\\\'\', \'Comment 52: ""Hello Damian\', \'Comment 53: this update is indeed for both the FS and also the S2P. Also this is related to the current printouts\', ""Comment 54: I don\'t know how the Coppens layout will look like"", \'Comment 55: however I suspect that in the end\', \'Comment 56: there we would like to see the same number. Additionally\', \'Comment 57: if possible we would like to see it for all types of financed invoices indeed\', \'Comment 58: we found out there are a few other cases than hatchery invoices only.""\', ""Comment 59: \'The document numbers on the new Coppens layouts should indeed be the same numbers as Steffen refers to.\'"", \'Comment 60: ""Do sprawdzenia wydruki FS i S2P dla MAS BE (zarówno nowe jak i stare) i do zmiany wyświetlanie numeru dokumentu - powinen być \\\'External Document Number\\\' zamiast \\\'Document ERP Number\\\' dla wszystkich faktur PI o typie \\\'Financed\\\'.""\', ""Comment 61: \'Sprawdzone"", ""Comment 62: zmienione dla PI o trypie Financed dla MAS BE na test.\'"", \'Comment 63: ""Now for all \\\'Financed\\\' invoices (SI and PI) on S2P and Financial statement printouts will be displayed \\\'External Document Number\\\'.It\\\'s ready on UAT environment (IBIP_DH_TEST).It has been implemented to all printouts of FS and S2P (new and old versions) in MAS BE sector.Please verify that it works properly on printouts of FS and S2P\', \'Comment 64: then we can move it to producion environment.""\', ""Comment 65: \'This looks good for the Hatchery section on the FS (it took the external nr. from the PI and showed this where there would be an SI nr. otherwise. For the S2P (and I guess for other sections such as expenses/slaughtery) there is no update yet.!image-1!!image-2!\'"", \'Comment 66: ""Do you mean this invoice on S2P? SI-FNB/2022/0053?In this case should we displays value from Purchase Invoice linked with this SI?On SI Financed invoices there are no field \\\'External Document Number\\\'.!image-2023-02-17-15-56-38-867.png!!image-2023-02-17-15-56-51-768.png!!image-2023-02-17-15-57-03-433.png!""\', \'Comment 67: ""Yes indeed. The SI is the one that will be shown on the S2P\', \'Comment 68: but it is indeed the PI that has de external document number. So if possible\', \'Comment 69: we would like to see the external document number from the PI as the document number on the printouts for both PI\\\'s or SI\\\'s (if financed of course).""\', \'Comment 70: ""[~SDriesen@deheus.com],we\\\'ve made changes on S2P printouts in MAS BE test environment. You can feel free to test it.Best regards,Grzegorz""\', ""Comment 71: \'Grzegorz"", ""Comment 72: I took a quick look. For financed hatchery/expenses invoices this looks fine to me on the S2P. For financed slaughtery invoices we don\\\\\'t really seem to have an external document number because we just use the slaughter report"", \'Comment 73: no invoice. So that would explain why this field is empty (line of 85.764,22 EUR). For the last line (202.563,77 EUR\', \'Comment 74: also financed document)\', \'Comment 75: I do however see ""TEST123"" (see screenshot 1). To what is that referring? Secondly\', \'Comment 76: these implementations could be moved to the FS as well. There I see that for hatchery this external doc. nr is already used\', ""Comment 77: but not for expenses etc. as it is for the S2P (see last 3 screenshots)!image-3!!image-4!!image-5!!image-6!\'"", \'Comment 78: ""Grzegorz\', \'Comment 79: I have an additional question. Is it possible\', \'Comment 80: that when we have a registration document on the FS printout\', \'Comment 81: the document nr. column for this line will be empty? The customer doesn\\\'t know this number neither.""\', ""Comment 82: \'What is the status of this?\'"", ""Comment 83: \'Hi [~SDriesen@deheus.com]could you please confirm all changes which should be done in this task to adjust all your requirements.I reviewed this task and try to summarize all remaining changes.{quote}For the last line (202.563,77 EUR"", \'Comment 84: also financed document)\', \'Comment 85: I do however see ""TEST123"" (see screenshot 1). To what is that referring?{quote}It\\\\\\\'s a External Document Number from this Financed PI!image-2023-04-18-12-26-36-727.png!{quote}Secondly\', \'Comment 86: these implementations could be moved to the FS as well. There I see that for hatchery this external doc. nr is already used\', ""Comment 87: but not for expenses etc. as it is for the S2P (see last 3 screenshots){quote}It means that if there is \\\\\'Financed\\\\\' Purchase Invoice it should be shown on Financial statement printouts (old and new) always \\\\\'External Document Number\\\\\' from Purchase Invoice instead of Intense document number or Erp Document number. It doesn\\\\\'t matter in which section it is (Expense"", \'Comment 88: Slaughtery\', ""Comment 89: Hatchery) it should be alway \\\\\'External Document Number\\\\\'?In cases when it\\\\\'s \\\\\'Financed\\\\\' Sales Invoice it should be visible alway \\\\\'External Document Number\\\\\' from linked PI (\\\\\'Leading doc\\\\\')?{quote}Grzegorz"", \'Comment 90: I have an additional question. Is it possible\', \'Comment 91: that when we have a registration document on the FS printout\', ""Comment 92: the document nr. column for this line will be empty? The customer doesn\\\\\'t know this number neither.{quote}Should it be applied to all \\\\\'Registered\\\\\' Purchase Invoices and all \\\\\'Registered\\\\\' Sales Invoices?Everytime when one of these cases (SI or PI registerd) will be shown on FS printouts and S2P printouts it shouldn\\\\\'t be visible any number in column \\\\\'Document nr\\\\\' on printout?!image-2023-04-18-13-01-43-574.png!\'"", ""Comment 93: \'Hello Damian,To sum up we would like:1. To have all financed invoices (hatchery"", \'Comment 94: expenses\', \'Comment 95: slaughtery,..) show their external document number on both the FS and the S2P. So for financed documents not the Intense document number\', ""Comment 96: nor the Milas document number.2. We reconsidered and the demand to make the document number for registrated invoices empty should NOT be put through. Our apologies.\'"", \'Comment 97: ""Hi Steffen,we\\\'ve made changes on FS old (FS new has no document number) and S2P old and new regarding your comments.You can feel free to test it in TEST Intense environment.Best regards,Grzegorz""\', \'Comment 98: ""Hello Grzegorz,I tested it for multiple cases\', \'Comment 99: but I still have some comments:1. For financed slaughtery invoices (PI to the customer)\', ""Comment 100: I couldn\'t continue because of this error (screenshot 1)2. I do see the external number for the hatchery invoice on the hatchery category (marked in yellow)"", \'Comment 101: but I do miss the numbers for the expenses category (stripes in black\', \'Comment 102: external document number was 002079 and 002080) and as I said in point 1\', ""Comment 103: I couldn\'t add the external document number"", \'Comment 104: so these numbers are also missing (stripes in red\', \'Comment 105: external document nr was 002081).!image-7!!image-9!""\', ""Comment 106: \'Hello Steffen,ad1. Every condition from error message did you check?ad2. Could you give me the document numer or id?Best regards,Grzegorz\'"", \'Comment 107: ""Hello Grzegorz,Ad 1. Yes. The difference with this financed slaughtery invoice and all the other financed invoices is that for this financed slaughtery invoice\', \'Comment 108: the PI is directed to the the customer (a customer number\', \'Comment 109: B006062). The other invoices\', \'Comment 110: there the financed PI is directed to a supplier (a hatchery\', \'Comment 111: veterinary,.. a supplier number\', ""Comment 112: LB000054). The error says I can\'t create a financed invoice with an external document number if there is no supplier number (LB-number) as supplier.Ad 2. The round is B006062/0201/0003 (ID 79961)"", \'Comment 113: financed hatchery invoice PI-FNB/2023/0002 (ID 79971)\', \'Comment 114: financed veterinary invoice PI-FNB/2023/0003 (ID 79973) and financed slaughtery invoice PI-FNB/2023/0004 (79976).""\', \'Comment 115: ""{quote}Ad 1. Yes. The difference with this financed slaughtery invoice and all the other financed invoices is that for this financed slaughtery invoice\', \'Comment 116: the PI is directed to the the customer (a customer number\', \'Comment 117: B006062). The other invoices\', \'Comment 118: there the financed PI is directed to a supplier (a hatchery\', \'Comment 119: veterinary,.. a supplier number\', ""Comment 120: LB000054). The error says I can\'t create a financed invoice with an external document number if there is no supplier number (LB-number) as supplier.{quote}Error messages appears during sending to Archive if one of conditions hasn\'t been met. There are some validation to prevent sending unacceptable data for Milas. Probably there were no VendorID on \'Customer Card\' for this supplier. If you will have this message again"", \'Comment 121: please send us screen and we\\\'ll see which validation it is.""\', \'Comment 122: \\\'Steffen,as I verified these invoices and this document doesn\\\\\\\'t have ""Document Number ERP\\\\\\\' for example:!image-2023-04-19-11-13-29-164.png!Do we need to display something else when the ""Document Number ERP"" is empty?\\\'\', ""Comment 123: \'Grzegorz"", \'Comment 124: Damian,Yes I deleted this number\', \'Comment 125: because of the error. You can fill in a number yourself\', \'Comment 126: then the error will come back. It has to do with the fact dat the supplier on this invoice is not a supplier card\', \'Comment 127: but a customer card. When it is a customer card\', ""Comment 128: external doc nr. should be empty according to the system.\'"", \'Comment 129: ""In this case condition for Milas validation has been met: Purchase Invoice has a Supplier with BP_Type = Customer and Type of purchase is different than \\\'Registration\\\'\', ""Comment 130: then External Document Number must be empty.Maybe it\'s only test case"", \'Comment 131: but it won\\\'t be real data?!image-2023-04-24-13-32-00-450.png!!image-2023-04-24-13-32-25-895.png!Is this solution with displaying numbers on printouts works properly or should we adjust it somehow?""\', \'Comment 132: ""If \\\'External Document Number\\\' is empty it should be displayed Intense number - for Financed PI.""\', ""Comment 133: \'do sprawdzania czy External Document Number jest uzupełniony"", \'Comment 134: jeśli nie\', \'Comment 135: to pokazujemy nr z Intense.we wszystkich sekcjach powinno to działać tak samo\', \'Comment 136: na żółto jedna faktura\', \'Comment 137: w sekcji Hatchery jest dobry numer\', ""Comment 138: w innych nie. Do sprawdzenia i poprawienia.!image-2023-04-24-14-55-54-714.png!\']""]\nRelated Issues:\n[\'DGS-8067\']\n\n### End'}"
957,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8074\n\n### Instruction:\nHi Ewa,\r\n\r\nI have 3 migration files to upload in Intense. This round was missing in the migration file.\r\n\r\nPlease see e-mail for details.\n\n### Response:\n[""Comment 1: [\'Planned on Tuesday next week.\'"", ""Comment 2: \'!image-2022-12-19-14-26-44-879!\'"", ""Comment 3: \'The files have been migrated.\']""]\nRelated Issues:\n[]\n\n### End'}"
958,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8073\n\n### Instruction:\nPlease have a look at feed sale FE-M/0100 in MAS NL. This document is assigned to customer 003774 but most probably it should be assigned to customer 004334 because the round is 004334/0100/0001 and all invoices belong to customer 004334 (maybe 43571 is an exception).\r\n\r\nAccording to this screen the other active round number is 003774/0060/0002 which is assigned to the first customer. Because of this issue it seems that a few feed sale invoice elements are (partly) moved from customer 004334 to customer 003774.\r\n\r\n\xa0\r\n\r\n\xa0\n\n### Response:\n[""Comment 1: [\'Theo has confirmed green comments:  !image-2022-12-15-09-20-29-566.png|width=1244,height=101! !image-2022-12-15-09-20-26-929! !image-2022-12-15-09-20-29-566!\'"", ""Comment 2: \'Feed elements (4 lines) fromFE-M/0403 (round003774/0060/0002) have been moved back to the FE-M/0100 (round004334/0100/0001) and Customer onFE-M/0100 has been changed from 003774 to 004334.Feed elements (1 line) from FE-M/0288 (round 005550/0125/0002) have been moved back to the FE-M/0131 (round 005724/0131/0001) and Customer on FE-M/0131 has been changed from 005550 to 005274.Please verify that everything is correct now.\'"", ""Comment 3: \'MitchTheoCould you please check and confirm we can close the task?Thank you in advance.\'"", ""Comment 4: \'Dodane do listy podsumowania dla klienta.\'"", ""Comment 5: \'Mitch"", ""Comment 6: could you check and confirm status?Can we close the task?\'"", ""Comment 7: \'Confirmed by Theo that can be closed.\']""]\nRelated Issues:\n[]\n\n### End'}"
959,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8072\n\n### Instruction:\nUmlaas WB\'s are not available for usage on DHP\r\n\r\nissue previously experienced with KD etc...\r\nhttps://helpdesk.kotrak.com/servicedesk/customer/portal/56/DGS-8019\r\nhttps://helpdesk.kotrak.com/servicedesk/customer/portal/56/DGS-7990\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'{code:java}2022-12-15 08:52:12 (/Plant.Weightbridge.Integration/SAURSRV04/7264/28) [Error] Plant.Integration.Weighbridge.Implementation.WcfWeightbridgeService - Cannot get weight data from wcf service.System.ServiceModel.CommunicationException: No connection could be made because the target machine actively refused it. (10.27.2.5:8041) ---> System.Net.Http.HttpRequestException: No connection could be made because the target machine actively refused it. (10.27.2.5:8041) ---> System.Net.Sockets.SocketException (10061): No connection could be made because the target machine actively refused it.   at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error"", \'Comment 4: CancellationToken cancellationToken)   at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource.GetResult(Int16 token)   at System.Net.Sockets.Socket.<ConnectAsync>g__WaitForConnectWithCancellation|277_0(AwaitableSocketAsyncEventArgs saea\', \'Comment 5: ValueTask connectTask\', \'Comment 6: CancellationToken cancellationToken)   at System.Net.Http.HttpConnectionPool.ConnectToTcpHostAsync(String host\', \'Comment 7: Int32 port\', \'Comment 8: HttpRequestMessage initialRequest\', \'Comment 9: Boolean async\', \'Comment 10: CancellationToken cancellationToken)   --- End of inner exception stack trace ---   at System.Net.Http.HttpConnectionPool.ConnectToTcpHostAsync(String host\', \'Comment 11: Int32 port\', \'Comment 12: HttpRequestMessage initialRequest\', \'Comment 13: Boolean async\', \'Comment 14: CancellationToken cancellationToken)   at System.Net.Http.HttpConnectionPool.ConnectAsync(HttpRequestMessage request\', \'Comment 15: Boolean async\', \'Comment 16: CancellationToken cancellationToken)   at System.Net.Http.HttpConnectionPool.CreateHttp11ConnectionAsync(HttpRequestMessage request\', \'Comment 17: Boolean async\', \'Comment 18: CancellationToken cancellationToken)   at System.Net.Http.HttpConnectionPool.AddHttp11ConnectionAsync(HttpRequestMessage request)   at System.Threading.Tasks.TaskCompletionSourceWithCancellation`1.WaitWithCancellationAsync(CancellationToken cancellationToken)   at System.Net.Http.HttpConnectionPool.GetHttp11ConnectionAsync(HttpRequestMessage request\', \'Comment 19: Boolean async\', \'Comment 20: CancellationToken cancellationToken)   at System.Net.Http.HttpConnectionPool.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage request\', \'Comment 21: Boolean async\', \'Comment 22: Boolean doRequestAuth\', \'Comment 23: CancellationToken cancellationToken)   at System.Net.Http.RedirectHandler.SendAsync(HttpRequestMessage request\', \'Comment 24: Boolean async\', \'Comment 25: CancellationToken cancellationToken)   at System.Net.Http.DecompressionHandler.SendAsync(HttpRequestMessage request\', \'Comment 26: Boolean async\', \'Comment 27: CancellationToken cancellationToken)   at System.Net.Http.HttpClient.<SendAsync>g__Core|83_0(HttpRequestMessage request\', \'Comment 28: HttpCompletionOption completionOption\', \'Comment 29: CancellationTokenSource cts\', \'Comment 30: Boolean disposeCts\', \'Comment 31: CancellationTokenSource pendingRequestsCts\', \'Comment 32: CancellationToken originalCancellationToken)   at System.ServiceModel.Channels.HttpChannelFactory`1.HttpClientRequestChannel.HttpClientChannelAsyncRequest.SendRequestAsync(Message message\', \'Comment 33: TimeoutHelper timeoutHelper)   --- End of inner exception stack trace ---   at System.ServiceModel.Channels.HttpChannelUtilities.ProcessGetResponseWebException(HttpRequestException requestException\', \'Comment 34: HttpRequestMessage request\', \'Comment 35: HttpAbortReason abortReason)   at System.ServiceModel.Channels.HttpChannelFactory`1.HttpClientRequestChannel.HttpClientChannelAsyncRequest.SendRequestAsync(Message message\', \'Comment 36: TimeoutHelper timeoutHelper)   at System.ServiceModel.Channels.RequestChannel.RequestAsync(Message message\', \'Comment 37: TimeSpan timeout)   at System.ServiceModel.Channels.RequestChannel.RequestAsyncInternal(Message message\', \'Comment 38: TimeSpan timeout)   at System.ServiceModel.Channels.RequestChannel.Request(Message message\', \'Comment 39: TimeSpan timeout)   at System.ServiceModel.Dispatcher.RequestChannelBinder.Request(Message message\', \'Comment 40: TimeSpan timeout)   at System.ServiceModel.Channels.ServiceChannel.Call(String action\', \'Comment 41: Boolean oneway\', \'Comment 42: ProxyOperationRuntime operation\', \'Comment 43: Object[] ins\', \'Comment 44: Object[] outs\', \'Comment 45: TimeSpan timeout)   at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(MethodCall methodCall\', \'Comment 46: ProxyOperationRuntime operation)   at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(MethodInfo targetMethod\', \'Comment 47: Object[] args)   at generatedProxy_1.GetWeightData()   at Plant.Integration.Weighbridge.Implementation.Integrations.Wcf.WeightbridgeServiceClient.GetWeight() in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\be19d0deb1043a27\\\\\\\\Plant.Integration.Weighbridge\\\\\\\\Plant.Integration.Weighbridge.Implementation\\\\\\\\Integrations\\\\\\\\Wcf\\\\\\\\WeightbridgeServiceClient.cs:line 48   at Plant.Integration.Weighbridge.Implementation.WcfWeightbridgeService._timer_Elapsed(Object sender\', ""Comment 48: ElapsedEventArgs e) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\be19d0deb1043a27\\\\\\\\Plant.Integration.Weighbridge\\\\\\\\Plant.Integration.Weighbridge.Implementation\\\\\\\\WcfWeightbridgeService.cs:line 80{code}\'"", ""Comment 49: \'{code:java}2022-12-15 09:03:34 (/Plant.Weightbridge.Integration/SAURSRV04/8116/21) [Error] Plant.Integration.Weighbridge.Implementation.WcfWeightbridgeService - Scale: ABWeighbridge is not responding. Auto reconnect.2022-12-15 09:03:34 (/Plant.Weightbridge.Integration/SAURSRV04/8116/35) [Error] Plant.Integration.Weighbridge.Implementation.WcfWeightbridgeService - Scale: Gate is not responding. Auto reconnect.{code}\'"", ""Comment 50: \'Hello Thabile,I restarted the services,I checked in the DHP application currently running!image-2022-12-15-08-24-22-489.png!You can close your incident?The problem has been resolved? Regards\'"", ""Comment 51: \'Hello"", ""Comment 52: thank you task can be closed\'"", ""Comment 53: \'[[DHP 3.0] Weighbridge|onenote:https://kotrak.sharepoint.com/sites/erpasysta/Shared%20Documents/Baza%20wiedzy/Baza%20Wiedzy%20-%20ERPSD/Klienci/DEHEUS/DEHEUS%20APPLICATIONS/RPA/Baza%20wiedzy.one#%5bDHP%203.0%5d%20Weighbridge&section-id=\\\\\\\\{A2F09CD6-A23A-42F3-92F5-ED66B521455B}&page-id=\\\\\\\\{44A9CA7C-AB75-48F4-A7D1-65EEAE848D9F}&end] ([Widok sieci Web|https://kotrak.sharepoint.com/sites/erpasysta/_layouts/OneNote.aspx?id=%2Fsites%2Ferpasysta%2FShared%20Documents%2FBaza%20wiedzy%2FBaza%20Wiedzy%20-%20ERPSD&wd=target%28Klienci%2FDEHEUS%2FDEHEUS%20APPLICATIONS%2FRPA%2FBaza%20wiedzy.one%7CA2F09CD6-A23A-42F3-92F5-ED66B521455B%2F%5BDHP%203.0%5D%20Weighbridge%7C44A9CA7C-AB75-48F4-A7D1-65EEAE848D9F%2F%29])\']""]\nRelated Issues:\n[\'DGS-7990\']\n\n### End'}"
960,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8071\n\n### Instruction:\nCan\'r select/find SO-2987/22//KBG to create a PrO in Kleinberg\r\n\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'!image!!image-1!!image-2!\'"", ""Comment 3: \'!image-3!\'"", ""Comment 4: \'!image-4!\'"", ""Comment 5: \' !screenshot-2! !image-2022-12-14-20-29-37-132!\'"", ""Comment 6: \'SO should be avilable to choose. Please verify.!image-2022-12-14-20-30-10-412.png!\'"", ""Comment 7: \'!image-2022-12-14-20-41-56-703.png!\'"", ""Comment 8: \'[[DHP 3.0] Brak SO na liście przy dodatnie PrO ProductionOrder|onenote:https://kotrak.sharepoint.com/sites/erpasysta/Shared%20Documents/Baza%20wiedzy/Baza%20Wiedzy%20-%20ERPSD/Klienci/DEHEUS/DEHEUS%20APPLICATIONS/RPA/Baza%20wiedzy.one#%5bDHP%203.0%5d%20Brak%20SO%20na%20li%C5%9Bcie%20przy%20dodatnie&section-id=\\\\\\\\{A2F09CD6-A23A-42F3-92F5-ED66B521455B}&page-id=\\\\\\\\{CB917569-631C-4815-87B9-09D10C0E1270}&end] ([Widok sieci Web|https://kotrak.sharepoint.com/sites/erpasysta/_layouts/OneNote.aspx?id=%2Fsites%2Ferpasysta%2FShared%20Documents%2FBaza%20wiedzy%2FBaza%20Wiedzy%20-%20ERPSD&wd=target%28Klienci%2FDEHEUS%2FDEHEUS%20APPLICATIONS%2FRPA%2FBaza%20wiedzy.one%7CA2F09CD6-A23A-42F3-92F5-ED66B521455B%2F%5BDHP%203.0%5D%20Brak%20SO%20na%20li%C5%9Bcie%20przy%20dodatnie%7CCB917569-631C-4815-87B9-09D10C0E1270%2F%29])\'"", ""Comment 9: \'Configuration of the item was not complete.\']""]\nRelated Issues:\n[]\n\n### End'}"
961,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8070\n\n### Instruction:\nPlease relink code 080587 in DHC for Premix Veghel. It should be linked to bulk code 080587, but it is linked to BB code 080587-B1000\r\nThere is an order for production and delivery this week.\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'It is already done !screenshot-1! \'"", \'Comment 3: ""thank\\\'s""]\']\nRelated Issues:\n[]\n\n### End'}"
962,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8069\n\n### Instruction:\nDear Kotrak Team,\r\n\r\nWe will be glad if our system could be set to two decimal places only for all parameters on ERP.\r\n\r\nThe difference is causing lot of descripancies for us as shown below. \r\n\r\nIt is happening at other area such as purchases, inventory etc.\r\n\r\ncan we fix it please? and how?\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Currently for document the value is correct.Can I get information on how this value has been generated - as it is in the attachment.Checking the control option should help but it should be tested. !screenshot-1! I understand that the problem is for different documents?Regards.\'"", ""Comment 4: \'we are looking for value of GHS 14,220.90 but the unit price doe not equate when multiplied.\'"", ""Comment 5: \'We have used the control option aswell"", \'Comment 6: but the best result was that it gave a discount \', ""Comment 7: which we dont want.\'"", ""Comment 8: \'In this case if the item has a quantity of 13500 this 14220.9/13500 gives a price of 1.0534.For two decimal places it is 1.05.I understand that the problem is when the item is copied and for the next item of the document is 1.05*13500=14175.Or is it about something else?\'"", ""Comment 9: \'Exactly\'"", ""Comment 10: \'How can we make it uniform,because if the customer recieves the invoice for 2 decimal his com putations would be different and might think we are cheating him or her\'"", ""Comment 11: \'And on what basis is the position value determined? Because the price then is with four decimal places.The price itself results from rounding in this case to two places.If changing the price to four places is not an option we can change the presentation of only printouts with four places.Only in this case will the price on the printout be different from the one in the system.\'"", ""Comment 12: \'Will consult with commercial team as well and get back please\'"", ""Comment 13: \'Hello"", ""Comment 14: do you have any update for our last comment?Thank you and regards.\'"", ""Comment 15: \'Hello,We are closing this task as we haven’treceivedany replyfromyouforalong time.Regards\']""]\nRelated Issues:\n[]\n\n### End'}"
963,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8068\n\n### Instruction:\nWe have an issue with creating sales orders when there are no stocks available.\r\nis it possible to block or stop the confirmation of a sales order when an item in the sales order does not have the requested sale quantity?\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'You meant sales order or Sales order release ?Could you rpovide a screenshot from error message?\'"", ""Comment 3: \'i mean sales order. It is not an errorBasically"", \'Comment 4: we want to put a control measure when there are no stocks available for an item so when a sales order is created on the item\', ""Comment 5: erp should not allow the order to be confirmed\'"", ""Comment 6: \'We may trigger on database the cost shouldnt exceed 3 hours.\'"", ""Comment 7: \'okay but is it possible to put that control in the ERP?\'"", ""Comment 8: \'Yes that trigger will be verifying when user will be confiming SO if there is enough resources\'"", ""Comment 9: \'okay please go ahead\'"", ""Comment 10: \'so we can test\'"", ""Comment 11: \'the control should indicate what product is missing the quantities\'"", ""Comment 12: \'you wish an error message for operator?\'"", ""Comment 13: \'{color:#212121}Yes please there should be an error message indicating what products are missing quantities depending on the requested sale quantity{color} ----\'"", ""Comment 14: \'I would ask for some more information before preparing the trigger:What about the situation when there are two orders for the same commodity and the total quantity is not sufficient for approval or"", \'Comment 15: when several orders are approved in bulk\', \'Comment 16: does the - should only one order be approved\', \'Comment 17: e.g. with a higher gidnumber?- None of them will be approved? How should the message read? Should it show which goods are missing?Changes from erp xl are to be verified?I would also like to point out that we are currently seeing ungenerated documents from you all the time\', \'Comment 18: VT from the dhc level. It would be a good idea for you to sort this out first and to reconcile your inventories.After deeper analisys\', ""Comment 19: adding this will be about 5 man -hours,\'"", ""Comment 20: \'Thank you and to the answer your questions;If there are two orders for the same product"", \'Comment 21: only the order that can be fulfilled by the current stock should be allowed to be confirmed.The error messages should be something like ""the order SO123/22 cannot be confirmed due 7700-b50 missing the requested quantity\', \'Comment 22: please check your stock levels and try again"" something like this.For the ungenerated VT from dhc i will be working on them.\\\'\', ""Comment 23: \'Error message : Order SO123/22 cannot be confirmed due to missing quantity for item 7700-b50. Please check your stock levelsandtryagain\'"", \'Comment 24: \\\'About""If there are two orders for the same product\', \'Comment 25: only the order that can be fulfilled by the current stock should be allowed to be confirmed.""If we got 2 orders for item code item1 with stock 50 kgOlder order ( with lower gidnumber) is for 50 kgandNewer older ( with higher gidnumber) is for 50 kgwhich of them should be confirmed ?\\\'\', ""Comment 26: \'the older one"", ""Comment 27: first come first served\'"", ""Comment 28: \'Please any update?\'"", ""Comment 29: \'We are very sorry for the time of implementation of the work is in progress.\'"", ""Comment 30: \'We prepared solution on internal envirovment. Did you wish to insert in to production or do you have any test database?\'"", ""Comment 31: \' will it cause any issue when inserted into production environment?\'"", ""Comment 32: \'Well it is opertion that are blocking confirming SO "", ""Comment 33: so if there is possibility please prepare backup to be used as database for tests.\'"", ""Comment 34: \'okay\'"", ""Comment 35: \'okay we will push it to production environment next week so i will use this week to prepare the grounds\'"", ""Comment 36: \'please implement it\'"", ""Comment 37: \'Hellooo\'"", ""Comment 38: \'Hello,Please let me know if the change is to be added immediately to the production base?If not whether you have issued bakcup ( if so"", ""Comment 39: in what location) I do not see at this time any test base plugged into erp xl.\'"", ""Comment 40: \'{color:#212121}We have a test environment where we can test that. If it is okay by you. I am sure you are aware of the test environment for ERP{color} ----\'"", ""Comment 41: \'Unfortunately"", \'Comment 42: I do not have the given directions for the erp xl test environment\', ""Comment 43: can you provide,\'"", ""Comment 44: \'{color:#212121}I will furnish you with the information soon{color} ----\'"", ""Comment 45: \'the ip to the test server is 10.233.3.34would you need any other info?\'"", ""Comment 46: \'Whta is the correct databse to log on"", \'Comment 47: the one with extenstion prod is for good version but it wnat work \', \'Comment 48: cause the key menager is not set correctly.Please verify it and let me know\', ""Comment 49: where is the wroking test for erpxl\'"", ""Comment 50: \'okay\'"", ""Comment 51: \'the database is 10.233.3.30 \'"", ""Comment 52: \'!image!\'"", ""Comment 53: \'there are 2 ERPXL databases ton this server"", ""Comment 54: do you meant this with extension _prod?\'"", ""Comment 55: \'no the one with test at the end\'"", ""Comment 56: \'[^kr_zatwierdzanie_zamowienie.sql]trigger we wspolpracy z Bartkiem\'"", ""Comment 57: \'Please indicate unequivocally where you have a test environment and on which base will ruuchominy erpxl to verify the base.Cause ERPXL_GHA_Test database is for version 2019.1.0 but you are using different versions of ERPXL so noe one will be uble to test it.In both test and prod you are using 2020.1.0 version of ERPXL.We may add this to ERPXL_GHA_Test but do you want us to upgrade this DB if yes we need to increase the pricing for setting up you test envirovemnt.But if you are working on db from this server with extension prod ( but it seems not to be you prod db"", \'Comment 58: different server and no sales documents from 2023) just confirm that.We have prepared solution\', ""Comment 59: we need only add this to correct test database on correct server.!image-2023-01-20-12-33-04-721.png!\'"", ""Comment 60: \'if that be the case add it to the production environment for use\'"", ""Comment 61: \'lets add the solution to the production environment\'"", ""Comment 62: \'Hi,The trigger has been implemented on Prod db:!image-2023-01-20-14-06-02-081.png!If it causes any issues"", ""Comment 63: please disable it and let us know. Right click on Trigger and then disable.Trigger name:KR_zatwierdzanieZamowienia!image-2023-01-20-14-05-08-737.png!Regards\'"", ""Comment 64: \'Thanks please close\'"", ""Comment 65: \'please close\'"", ""Comment 66: \'Thank you\']""]\nRelated Issues:\n[]\n\n### End'}"
964,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8067\n\n### Instruction:\nToday, we received the first vendor invoices from Milas, translated to French. I see now that everything is translated (correct), exept the item codes and names. They are still in Dutch. According to Adifo, the company behind Milas, this is data that should be translated in Intense and only then will be translated on the vendor invoice in Milas. Could you tell me if indeed this is the case? We do have the translations of these item codes. In the annexe an example of such an invoice, with the French header and the Dutch item codes and names.\n\n### Response:\n[""Comment 1: [\'[^VendInvoiceDocument-sdriesens-0_14122022_095522_31_30309_P.pdf] _(62 kB)_\'"", ""Comment 2: \'This has to be discussed with Mitch.\'"", ""Comment 3: \'[~damian.swistek@kotrak.com] do omówienia z klientem: # Czy chcą tłumaczyć item code oraz item name # Czy chcą do MILASA wysyłać przełtumaczony item code i item name? Co dla mnie jest wątpliwe"", \'Comment 4: bo item code musi się zgadzać pomiedzy MILAS i Intense\', \'Comment 5: więc jeśli zmienimy w Intensie Item Code\', \'Comment 6: to Milas go chyba nie rozpozna.Do wewnętrznej analizy # Jesli wydruki faktur sa generowane w MILASIE\', \'Comment 7: to chyba najlepiej tłumaczyć faktury w MILASIE. Co do wydruku FS\', \'Comment 8: to trzeba by się zastanowić jak to obsłużyć w Intensie. Myślałam\', \'Comment 9: że można dodać pola z dodatkowym item name np. po francusku\', \'Comment 10: po niemiecku i jeśli pole jest wypełnione na kartotece Itemu oraz jezyk wybrany na kartotece klienta\', ""Comment 11: to system automatycznie wybiera dobre tlumaczenie dla nzwy itemu na wydruk FS.\'"", ""Comment 12: \'The translations provided by Steffen are enclosed.[^RE_ French translations printouts.msg]\'"", ""Comment 13: \'What is the status of this?\'"", ""Comment 14: \'Na tą chwilę mamy plik z tłumaczeniami dla Itemów na język francuski.[^Copy of Copy of Artikelen vertalingen.xlsx]Przyszłościowo powinny być także tłumaczenia na język niemiecki oraz holenderski.\'"", ""Comment 15: \'W pierwszej kolejności robimy obsługę wielojęzyczności na Itemie i zaciągnięcie francuskich tłumaczeń"", ""Comment 16: które zostały dostarczone.W drugim etapie będziemy robić obsługę tłumaczeń na wydrukach.\'"", ""Comment 17: \'zaimportowano dane i stworzono walidacje na odpowiednie tłumaczenia\'"", ""Comment 18: \'Na IBIP_DH_TEST wyłączona została akcja po zapisie Itemu z procedurą [dbo].[KR_TranslationCount]"", \'Comment 19: która powoduje problemy w zakładaniu itemów z Milasa.Do sprawdzenia i zmiany\', ""Comment 20: aby nie blokować zapisywania itemów.\'"", ""Comment 21: \'[~grzegorz.materla@kotrak.com]do zrobienia druga część zmian z taska"", ""Comment 22: czyli - obsługa tłumaczeń itemów na wydrukach Financial Statement i S2P.\'"", ""Comment 23: \'Dotyczy wszystkich wydruków FS i S2P"", \'Comment 24: zarówno starych\', \'Comment 25: jak i nowych dla sektora MAS BE.Przyszłościowo też będzie to w sektorze MAS NL i być może innych\', ""Comment 26: ale na tą chwilę implementujemy w MAS BE.\'"", ""Comment 27: \'Wydruki"", \'Comment 28: na których są już obsłużone tłumaczenia dla itemów na IBIP_DH_TEST: * Financial Statement (MAS BE) Horizontal * Financial Statement (MAS BE) VerticalDo przetłumaczenia nagłówki dla nowego wydruku FS * Financial Statement 2 (new printout) (MAS BE)Do ustalenia czy na wydruku S2P mają też być tłumaczone jakieś inne elementy wydruku czy tylko nagłówek\', ""Comment 29: tam nie wyświetlamy nazw itemów. * Saldo 2 pay_2 (new printout) (MAS BE)\'"", ""Comment 30: \'[^FS_new_printout_translations.xls]\'"", \'Comment 31: ""On IBIP_DH_TEST there are provided French translations for Items. On Item card there is new tab with table where are translations.!image-2023-02-22-10-59-42-408.png!It\\\'s ready to tests for FS printouts on IBIP_DH_TEST: * Financial Statement (MAS BE) Horizontal * Financial Statement (MAS BE) Vertical-------------Could you provide to us translations for: * Financial Statement 2 (new printout) (MAS BE) - in Excel there are all labels which i found on printout (if we already had a translation I filled it in column \\\'French\\\'). You can add/modify values for translation in this excel.[^FS_new_printout_translations.xls] * Saldo 2 pay_2 (new printout) (MAS BE) - I think only these 2 labels\', \'Comment 32: others we already had for old S2P printouts. Should be other elements of S2P printouts translated on French? On S2P printouts there are no item names\', \'Comment 33: we have only invoices without invoice elements. ** Diversen ** Subtotal!image-2023-02-22-11-39-47-908.png!""\', ""Comment 34: \'[~mbovene@deheus.com],the translations have been added on S2P (MAS BE) in test environment.You can feel free to test it.Best regards,Grzegorz\'"", \'Comment 35: ""Hello,I can\\\'t find the translations in the item card in the test environment.Can you tell me where I should look?!image!""\', ""Comment 36: \'Sorry"", ""Comment 37: wrong screenshot (previously). !image-1!\'"", ""Comment 38: \'[~SDriesen@deheus.com],the translations have been added in the test environment IBIP_DH_TEST:!image-2023-02-27-10-39-17-906.png!Best regards,Grzegorz\'"", ""Comment 39: \'Regarding this topic:Could you provide to us translations for:Financial Statement 2 (new printout) (MAS BE) - in Excel there are all labels which i found on printout (if we already had a translation I filled it in column \\\\\'French\\\\\'). You can add/modify values for translation in this excel. FS_new_printout_translations.xls --> This topic is in progress. I asked a colleague to help me with this.Saldo 2 pay_2 (new printout) (MAS BE) - I think only these 2 labels"", \'Comment 40: others we already had for old S2P printouts. Should be other elements of S2P printouts translated on French? On S2P printouts there are no item names\', \'Comment 41: we have only invoices without invoice elements.Diversen --> Translation FR: DiversSubtotal --> can the Dutch version be modified to ""Subtotaal"" (2 A\\\\\\\'s)? Translation FR:  Sous-total--> The translations can indeed be copied from the old printouts if available. The two other codes\', ""Comment 42: \\\\\'diversen\\\\\' and \\\\\'subtotal\\\\\' may be translated. You can find it above.\'"", \'Comment 43: \\\'[~SDriesen@deheus.com],the name ""Subtotaal"" has been changed on S2P printout in test environment.Best regards,Grzegorz\\\'\', ""Comment 44: \'Grzegorz,Regarding the translations"", ""Comment 45: that was my fault. I was indeed accidently looking in PROD and not in TEST. There I can see the translations and I can modify them.\'"", ""Comment 46: \'Grzegorz,Do you have any idea when this translation field will be moved from TEST to PROD environment?!image-2!!image-3!\'"", \'Comment 47: ""Hello Steffen,We should be able to move it to PROD environment to the end of this week - 10.03.2023.We\\\'ll let you know when it will be moved.For now ready to move on PROD are printouts: * Financial Statement (MAS BE) Horizontal * Financial Statement (MAS BE) Vertical * Saldo 2 pay (MAS BE) Horizontal * Saldo 2 pay (MAS BE) Vertical * Saldo 2 pay_2 (new printout) (MAS BE)We\\\'re waiting only for translations for printout: * Financial Statement 2 (new printout) (MAS BE)Regards,Damian""\', ""Comment 48: \'Could you tell me if the translation field can be moved to PROD by now?The translation of FS 2 (new) I hope to be able to deliver you this week. Do you need any more translations for S2P_2 (new)? If not"", ""Comment 49: when do you think the translation will be available?\'"", ""Comment 50: \'Hi [~SDriesen@deheus.com],we are working with [~mbovene@deheus.com]on FS 2 (new) calculations right now. Could you tell me when is your deadline for the translation of FS 2 (new)?Best regards,Grzegorz\'"", \'Comment 51: ""Hello Grzegorz,I hope this week\', ""Comment 52: but that\'s up to the person helping me (he is a native French speaker and a representative). I will do my best to deliver the translations as soon as possible. My question was regarding the translation field on item cards"", \'Comment 53: I don\\\'t know if you were talking about this as well?!image-4!""\', ""Comment 54: \'[~SDriesen@deheus.com],yes"", \'Comment 55: my mistake. I thought about the printouts. If we are talking about the fields on item cards\', ""Comment 56: we can plan import translation data for tommorow. Could you provide me the file with translations?Best regards,Grzegorz\'"", ""Comment 57: \'Grzegorz,Normally the translations were already provided a while ago and should be on the item cards in TEST. If not"", \'Comment 58: let me know\', ""Comment 59: I think we have the list somewhere here.\'"", ""Comment 60: \'[~SDriesen@deheus.com],yes"", ""Comment 61: we have the translations items in test environment. We can transfer it to prod Intense environment or when you have new file with new translations you can provide it to us.Best regards,Grzegorz\'"", ""Comment 62: \'Normally these translations are valid. If we notice that there are some things we would like to see translated differently"", ""Comment 63: we will let you know afterwards.\'"", ""Comment 64: \'Hello Grzegorz,I translated the whole Financial Statement 2 (new). You can find the translations in blue in the excel provided. When do you expect the translated FS 2 (new) and S2P 2 (new) to be available in French?[^Translations Financial Statement 2 (new).xls] _(57 kB)_\'"", ""Comment 65: \'Made 1 more small adjustment"", ""Comment 66: this is the final version:[^Translations Financial Statement 2 (new) 2.0.xls] _(57 kB)_\'"", \'Comment 67: ""Hi [~SDriesen@deheus.com],we\\\'ve made changes on printout FS 2(new) for translations in test Intense environment. Now we are focusing on migrate translations for items.You can verify it.Best regards,Grzegorz""\', ""Comment 68: \'Hello Damian,I looked into both documents. They look good"", \'Comment 69: but we have a few more adaptions we would like to have on both documents\', \'Comment 70: everything written in red specifically. If you modified that\', ""Comment 71: you may move both to PROD. Thank you!Regards,Steffen Driesen[^Translations Financial Statement 2 (new) MODIFIED.xls] _(57 kB)_[^Translations Saldo 2 Pay 2 (new) MODIFIED.xls] _(50 kB)_\'"", ""Comment 72: \'One more small modification on FS 2"", ""Comment 73: please use this version.[^Translations Financial Statement 2 (new) MODIFIED-1.xls] _(57 kB)_\'"", \'Comment 74: ""[~SDriesen@deheus.com],We\\\'ve made changes with your new version. You can feel free to test it.Best regards,Grzegorz""\', \'Comment 75: ""Grzegorz,The changes for FS 2 new are fine. You may move this to PROD. Do you know when this will be? And the translations on the item card\', \'Comment 76: when will those be added in PROD? I see the field is already available.The changes for S2P 2 new however I don\\\'t see yet in TEST? [^Translations Saldo 2 Pay 2 (new) MODIFIED-1.xls] _(50 kB)_""\', ""Comment 77: \'[~SDriesen@deheus.com],FS2 (new) and Items translations are avaliable on PROD Intense environment. Other prinouts will be migrate after the weekend.S2P 2 (new) with translations is in TEST Intense environment.Best regards"", ""Comment 78: Grzegorz\'"", \'Comment 79: ""Hello Grzegorz\', \'Comment 80: Thank you for the update!Here a few reactions:1. FS 2 (new): Translations seem good\', ""Comment 81: only the stock isn\'t translated"", ""Comment 82: which was in TEST (see screenshot 1)2. I don\'t see the translated item names on the old FS while I do see them on item cards (see screenshot 2)3. Translations ands changes for S2P 2 (new) seem good in TEST"", \'Comment 83: so they may be moved to PROD. Can the info be placed a bit more under the titles? (see screenshot 3)!image-5!!image-6!!image-7!""\', \'Comment 84: ""Hi[~SDriesen@deheus.com],we\\\'ve moved all printout with translation into Prod Intense environment. We\\\'ve included your reactions\', \'Comment 85: but we don\\\'t understand point 3. Could you explain it with more details?Best regards,Grzegorz""\', \'Comment 86: ""Ok\', \'Comment 87: I\\\'ve got the feedback from Damian. We\\\'ve changed alignment at titles on Saldo 2 pay prinouts.Best regards,Grzegorz""\', ""Comment 88: \'Hi Grzegorz,I will look into them"", \'Comment 89: thank you.My remark on point 3 was regarding the alignment\', ""Comment 90: but now in Prod it looks much better already. Below you see the difference.!image-8!!image-9!\'"", ""Comment 91: \'Hello,1. S2P new seems good in PROD"", \'Comment 92: alignment as well2. On FS new\', \'Comment 93: the entry stock and final stock are still in Dutch on French printouts (see screenshots 1&2) and the remark of Mitch regarding the guarantee that needs to be included in the feed profit (positive or negative) is not modified yet.3. The translations of the item codes are visible on the printouts.So if you could get the stock fields translated it seems fine to me.One more question\', \'Comment 94: for feed lines we have ""voer\\\\\\\' as description on the S2P and for one sided SI\\\\\\\'s where the customer is both the supplier and the reference\', \'Comment 95: we have ""Salmonellafonds"" as description on the S2P. Could these fields be translated as well\', ""Comment 96: looking to the customer card for the correct translation?!image-10!!image-11!\'"", \'Comment 97: \\\'When can point 2 ""On FS new\', \'Comment 98: the entry stock and final stock are still in Dutch on French printouts"" be moved to PROD? These translations seemed to be allright in TEST.\\\'\', ""Comment 99: \'Hi [~SDriesen@deheus.com],point 2 have been moved into Prod Intense environment. You can feel free to test it.Regarding your question about Salmonellafonds"", ""Comment 100: it is possible to translate it for french customers. Could you send us the particular translation for this word?Best regards,Grzegorz\'"", ""Comment 101: \'Hello Grzegorz,Translations of stock in French on FS new are fine (and by that the whole document is"", \'Comment 102: thank you).On S2P\', \'Comment 103: we would like to see feed and salmonellafonds translated\', ""Comment 104: so:* Voer (Dutch version) --> Aliments (French version) (is feed) * Salmonellafonds (Dutch version) --> Fonds de salmonelle (French version)\'"", \'Comment 105: ""Hi[~SDriesen@deheus.com],we\\\'ve modified the printout S2P in the TEST environment. You can feel free to test it.Best regards,Grzegorz""\', ""Comment 106: \'Zmodyfikowana funkcja[dbo].[KR_Printouts_Translation].\'"", \'Comment 107: ""Hello Grzegorz,I don\\\'t see both changes in test. On a French S2P ( horizontal)\', ""Comment 108: I still see \'voer\' for feed and \'salmonellafonds\' for the salmonelle fund"", ""Comment 109: but not the translations below. For the new S2P \'salmonellafonds\' is correctly translated"", ""Comment 110: \'voer\' we don\'t see on these printouts so that is good. But if you can move this also to the other available S2P printouts it would be great.Mitch also asked me this morning if I saw the abbreviated slaughtery and hatchery names"", \'Comment 111: but as you can see they aren\\\'t yet (all?) on the new S2P.!image-13!!image-14!""\', \'Comment 112: ""Update: the abbreviations are probably not visible because they aren\\\'t in test I just realised. Mitch showed me that if he adds the abbreviation manually\', \'Comment 113: it is shown and right now I did the same. This works for the new FS\', \'Comment 114: but not yet for the new S2P as you can see in the screenshots. !image-15!!image-16!!image-17!""\', ""Comment 115: \'[~SDriesen@deheus.com],we adjusted only the S2P (new) printout in test environment.In that case"", ""Comment 116: are you want to add the translation also on the other S2P prinouts?Best regards,Grzegorz\'"", ""Comment 117: \'Grzegorz"", \'Comment 118: Yes\', \'Comment 119: if possible. If that is too much work\', ""Comment 120: it will be fine I guess.Best regards,Steffen\'"", ""Comment 121: \'[~SDriesen@deheus.com],so"", ""Comment 122: we added it on theremaining S2P prints.You can verify it.Best regards,Grzegorz\'"", ""Comment 123: \'Grzegorz,This is perfect"", \'Comment 124: thank you. You may move this to PROD\', ""Comment 125: the only thing open for the new S2P is the abbreviations of the slaughtery/hatchery I guess.\'"", \'Comment 126: ""The new S2P is good now\', \'Comment 127: only the abbreviations for hatchery and slaughtery are still missing and on the old S2P\', \'Comment 128: the French translations of \\\'voer\\\' and \\\'salmonellafonds should be added in the French version (see down below).""\', \'Comment 129: ""Oh\', \'Comment 130: and 1 extra comment now\', \'Comment 131: on the french new S2P\', \'Comment 132: the title \\\'Divers\\\' is missing (on the dutch version it is called \\\'Diversen\\\')!image-12!""\', \'Comment 133: ""[~SDriesen@deheus.com],could you test the prints one more time? We\\\'ve made changes.If everithing will be ok\', \'Comment 134: we will move the modifications to PROD.Best regards,Grzegorz""\', ""Comment 135: \'Grzegorz,I see all the last asked changes on the different S2P versions"", \'Comment 136: so these modifications may be moved to PROD. The abbreviations for slaughtery/hatchery names are in PROD\', \'Comment 137: so if that stands as it is on the new S2P in PROD now\', ""Comment 138: everything regarding S2P should be good.Regards,Steffen\'"", \'Comment 139: ""[~SDriesen@deheus.com],we\\\'ve moved translations for S2P (MAS BE) printouts from TEST to PROD Intense environment.You can feel free to test it.Best regards,Grzegorz""\', ""Comment 140: \'Grzegorz,Everthing regarding S2P printouts looks fine to me in PROD now. Thank you.Regards,Steffen\'"", \'Comment 141: ""I notice now that there are 2 small modifications that we would like to see on the new S2P. 1. Could you make \\\'leverdatum\\\' (delivery date) the leading column for the chronlogy of the printout? 2. Could you switch column 1 \\\'factuurdatum\\\' (invoice date) and column 5 \\\'leverdatum\\\' (delivery date) around? So that \\\'leverdatum\\\' (delivery date) is the first column and the leading column for the chronology?!image-18!""\', \'Comment 142: ""[~SDriesen@deheus.com]These 2 changes should be applied only to S2P printout in MAS BE?{quote}I notice now that there are 2 small modifications that we would like to see on the new S2P. 1. Could you make \\\'leverdatum\\\' (delivery date) the leading column for the chronlogy of the printout? 2. Could you switch column 1 \\\'factuurdatum\\\' (invoice date) and column 5 \\\'leverdatum\\\' (delivery date) around? So that \\\'leverdatum\\\' (delivery date) is the first column and the leading column for the chronology?!image-18!{quote}""\', ""Comment 143: \'Hello Damian,If possible also for MAS NL please.\'"", \'Comment 144: ""[~SDriesen@deheus.com],we\\\'ve made changes on S2P new printouts (MAS NL\', \'Comment 145: MAS BE) in the TEST environment.You can verify it.Best regards,Grzegorz""\', ""Comment 146: \'Hello Grzegorz,This seems good both in MAS BE and MAS NL test. You may move this to PROD. Thank you!Regards,Steffen\'"", \'Comment 147: ""Hello Steffen,we\\\'ve made changes also in PROD environment.You can feel free to test it.Best regards,Grzegorz""\', \'Comment 148: ""Hello,I think there is still one small error.The columns are switched perfectly\', ""Comment 149: but the first column \'leverdatum\' (delivery date) should still be leading for the chronology. I think it is still ordered on \'factuurdatum\' (invoice date). On the example I tested yesterday in TEST"", \'Comment 150: I think there was no case like this.!image-20!""\', ""Comment 151: \'Hello,yes"", ""Comment 152: we have order by Facturdatum in SQL procedure. We made changes. Can you look at it one more time in PROD environment?Best regards,Grzegorz\'"", \'Comment 153: ""Hello,It still seems to be sorted by \\\'factuurdatum\\\'. Do I need to re-login?!image-21!""\', \'Comment 154: ""I did by now\', \'Comment 155: but it\\\'s still the same order. (I am talking about the PROD environment)""\', ""Comment 156: \'Hi Steffen,could you give me the document number?Best regards,Grzegorz\'"", ""Comment 157: \'Hello Grzegorz,The screenshot down below for example is SP-B/0652 (ID 106931).\'"", ""Comment 158: \'Hi,yes"", \'Comment 159: you are right with the order\', ""Comment 160: because we had the wrong date type. The prints are working fine now.You can verify it.Best regards,Grzegorz\'"", ""Comment 161: \'Hello,It seems good now indeed"", ""Comment 162: thank you.\']""]\nRelated Issues:\n[\'DGS-8215\', \'DGS-8326\', \'DGS-8075\']\n\n### End'}"
965,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8066\n\n### Instruction:\nIn Andel a printout must be generated when an order for packed arrives in DHP. Manual selection of printout on sales order in DHP does generate a print; the template and printer seem to be fine. \r\n\r\nPlease check/fix config so that the printout is created automatically when sales order for packed arrives.\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Hej"", ""Comment 3: sposób generowania wydruku można skonfigurować z poziomy pliku konfiguracyjnego pluginu as400 (\\\\\\\\kotrak\\\\\\\\dhp30_IIS\\\\\\\\PlantPrintoutPrintServer\\\\\\\\Plugins):!image-2022-12-20-08-43-44-854.png!\'"", ""Comment 4: \'aktualny konfig :!image-2022-12-20-09-08-05-212.png!\'"", ""Comment 5: \'According to the service agreement this task should be categorized as a service request.Kindly approve change of the type of this task?AlsoThe current configuration is such that for shipping notice on creation and update is enabled I understand that it should be enabled?The automatic printout generation for orders (enabled at the moment) should not be changed?\'"", ""Comment 6: \'{color:#000000}Goodmorning.{color} {color:#000000}{color}  {color:#000000}Ok to change the type of this task and please check/change the setup so that orders are printed.{color}   {color:#000000}Plant needs the printout for packed orders.{color}   {color:#000000}{color}     {color:#000000}       {color}{color:black}{color} {color:#000000} {color}{color:black}Best regards | Met vriendelijke groeten,{color}{color:#000000}{color}{color:black}  Bob Kennedy{color} {color:#000000}{color}{color:black}Informatie analist{color}{color:#000000} {color}{color:black}{color}{color:#000000} {color}{color:#000000} {color} |{color:#000000}{color} {color:#000000}{color}De Heus Voeders{color:#000000} <[http://www.de-heus.nl/]>{color}{color:black}{color}{color:#000000} {color}{color:#000000} {color}|{color:#000000}{color}{color:#006FB7} * De Heus Voeders B.V.*{color}{color:#000000}{color}{color:#006FB7}{color} {color:#000000}{color}{color:#006FB7} Postbus 396 6710 BJ Ede{color}{color:#000000}{color}{color:#006FB7} Rubensstraat 1756717 VE Ede  *M* 06 - 53 224 931 KvK 14626985{color}{color:#000000}{color}{color:black} {color}{color:#000000}{color}{color:#006FB7} _ Op dit e-mailbericht en eventuele bijlage(n) is de disclaimer van toepassing_{color}{color:#000000}{color}{color:#006FB7}{color} {color:#000000}{color}{color:#006FB7} _ gepubliceerd op de website van_{color} [{color:#006FB7} _De Heus Voeders_{color}|http://www.de-heus.nl/maildisclaimer]{color:#006FB7} _._{color}{color:#000000}{color}{color:#006FB7}{color} {color:#000000} {color}{color:#000000} {color}| |{color:#000000}{color}{color:black}{color} image007.jpg@01D62AA3.AD14DDB0{color:black}{color}{color:#000000} {color}{color:#000000} {color}| |{color:#000000}{color}{color:black}{color} image004.jpg@01D62AA3.AD2CAB70{color:black}{color}{color:#000000} {color}{color:#000000} {color}| {color:#000000}{color} ---- {color:#000000} *From:* Agnieszka Januszewska (Jira) <jira@kotrak.com>  *Sent:* Tuesday"", \'Comment 7: December 20\', \'Comment 8: 2022 11:32 AM  *To:* Kennedy\', ""Comment 9: Bob <BKennedy@deheus.com>  *Subject:* DGS-8066 Printout packed Andel not generared on receiving sales order{color}  |{color:#ffffff} CAUTION: This message originated from outside the organisation. Please do not click on links or open attachments unless you trust the sender and know the content is safe.{color} |\'"", \'Comment 10: \\\'konfig zmieniany 13.12. 2022 "" !image-2022-12-22-08-14-28-445.png!drukowanie dla orderow jest ustawione!image-2022-12-22-08-17-24-405.png!\\\'\', ""Comment 11: \'Please verify"", ""Comment 12: after you log on again.Configuration for order is set.\'"", ""Comment 13: \'May we close the task? Did you verify it?\'"", ""Comment 14: \'Andel responded that still no printouts are received for packed orders. \'"", ""Comment 15: \'Hi Bob,Could you please confirm when do Andel want to print printout for packed orders? When Order arrives or when Trip arrives?Regards\'"", ""Comment 16: \'{color:#000000}Andel wishes to get printout on arrival of order{color}   {color:#000000}{color}     {color:#000000}       {color}{color:black}{color} {color:#000000} {color}{color:black}Best regards | Met vriendelijke groeten,{color}{color:#000000}{color}{color:black}  Bob Kennedy{color} {color:#000000}{color}{color:black}Informatie analist{color}{color:#000000} {color}{color:black}{color}{color:#000000} {color}{color:#000000} {color} |{color:#000000}{color} {color:#000000}{color}De Heus Voeders{color:#000000} <[http://www.de-heus.nl/]>{color}{color:black}{color}{color:#000000} {color}{color:#000000} {color}|{color:#000000}{color}{color:#006FB7} * De Heus Voeders B.V.*{color}{color:#000000}{color}{color:#006FB7}{color} {color:#000000}{color}{color:#006FB7} Postbus 396 6710 BJ Ede{color}{color:#000000}{color}{color:#006FB7} Rubensstraat 1756717 VE Ede  *M* 06 - 53 224 931 KvK 14626985{color}{color:#000000}{color}{color:black} {color}{color:#000000}{color}{color:#006FB7} _ Op dit e-mailbericht en eventuele bijlage(n) is de disclaimer van toepassing_{color}{color:#000000}{color}{color:#006FB7}{color} {color:#000000}{color}{color:#006FB7} _ gepubliceerd op de website van_{color} [{color:#006FB7} _De Heus Voeders_{color}|http://www.de-heus.nl/maildisclaimer]{color:#006FB7} _._{color}{color:#000000}{color}{color:#006FB7}{color} {color:#000000} {color}{color:#000000} {color}| |{color:#000000}{color}{color:black}{color} image007.jpg@01D62AA3.AD14DDB0{color:black}{color}{color:#000000} {color}{color:#000000} {color}| |{color:#000000}{color}{color:black}{color} image004.jpg@01D62AA3.AD2CAB70{color:black}{color}{color:#000000} {color}{color:#000000} {color}| {color:#000000}{color} ---- {color:#000000} *From:* Aleksandra Przybyłek (Jira) <jira@kotrak.com>  *Sent:* Monday"", \'Comment 17: January 23\', \'Comment 18: 2023 3:28 PM  *To:* Kennedy\', ""Comment 19: Bob <BKennedy@deheus.com>  *Subject:* DGS-8066 Printout packed Andel not generared on receiving sales order{color}  |{color:#ffffff} CAUTION: This message originated from outside the organisation. Please do not click on links or open attachments unless you trust the sender and know the content is safe.{color} |\'"", ""Comment 20: \'Dear Bob,Could you please ask Andel to verify again?Regards\'"", ""Comment 21: \'Dear Bob,Could you please ask Andel to verify again?Regards\'"", ""Comment 22: \'I have asked Andel to verify.\'"", ""Comment 23: \'Sure"", ""Comment 24: waiting for your feedback then.Regards\'"", ""Comment 25: \'Andel checked and they are not receiving printout for packed sales orders. Is there a way to check where in the process we have an issue? Is a print file generated? Is the printer / paper tray available?\'"", ""Comment 26: \'[~maciej.dobrzanski@kotrak.com]server aplikacyjny:172.23.1.91server bazodanowy:DHVD01AG01\\\\\\\\ANDEL\'"", ""Comment 27: \'Order: SOBE000014055 f3ceec11-90bf-4a0b-9115-77e6e166b77dWydruk jest widoczny w preview. Idiki wydruku są poprawne w konfiguracji pluginu. !prevoew! \'"", \'Comment 28: \\\'Hi,Could you please set up ""Keep Printed Documents"" configuration for us?Regards!image-2023-02-16-07-17-37-560.png!\\\'\', ""Comment 29: \'I have asked Martijn Meier for this configuration\'"", ""Comment 30: \'Thank you. Please"", ""Comment 31: let us know when it is configured.Regards\'"", ""Comment 32: \'Can you give us the Ip address for this printer? We are not sure which printer it is  {quote}Op 17 feb. 2023 om 07:22 heeft Aleksandra Przybyłek (Jira) <jira@kotrak.com> het volgende geschreven:  {quote}  {quote} \\\\ufeff{color:#999999}{color}{color:#999999}{color}{color:#7a869a}{color}{color:#7a869a}{color} {quote}\'"", ""Comment 33: \'This is the name of the printer:!image-2023-02-17-10-46-10-103.png!\'"", ""Comment 34: \'Hi"", \'Comment 35: requested checkbox ""Keep printed documents"" has been set.\\\'\', ""Comment 36: \'Thank you\'"", ""Comment 37: \'Ordery są zapisane na liście wydrukowanych dokumentówPrzykłady:SOBE000014869 - created  2023-02-22 12:40:50 -> Printed 12:40SO000072839 - created 2023-02-22 12:12:48 -> Printed 12:12 !Created_SO!  !printed! \'"", ""Comment 38: \'Dear,Orders are saved on printd documents list"", ""Comment 39: please see our examplesSOBE000014869 - created 2023-02-22 12:40:50 -> Printed 12:40SO000072839 - created 2023-02-22 12:12:48 -> Printed 12:12!image-2023-02-22-14-12-32-533.png|width=1279,height=755!We advise to check devices if they are connected properly or maybe there was some Windows update that crashed communication with printer.Regards\'"", ""Comment 40: \'Hi Aleksandra"", \'Comment 41: Martijn sent a test page to the printer and it was printed correctly. However\', ""Comment 42: the documents generated from DHP are sent to the queue but these are not printed. We will try to find out why. Or do you have an idea what may be the issue here?\'"", ""Comment 43: \'Dear Bob,All we could verify was done. I will put on hold this task untill we get some feedback from Martijn.Regards\'"", ""Comment 44: \'Hi,Any feedback? Can we close this task?Regards\'"", ""Comment 45: \'Plant confirmed that printout is now working fine. This ticket can be closed.\'"", ""Comment 46: \'Thank you\']""]\nRelated Issues:\n[]\n\n### End'}"
966,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8065\n\n### Instruction:\nhttps://helpdesk.kotrak.com/servicedesk/customer/portal/56/DGS-6795\r\nwhen the daily report is run(execute report then bulk approval) if a different tab is opened then a user goes back to the report the system retains the previous settings but does not allow the user to continue with bulk approval, only the download button shows. It does not allow a refresh, the only solution being to reload the entire site then are we able to use the report again. dhp refresh does not work.\n\n### Response:\n[""Comment 1: [\'[^2022-11-28_15-09-58.mp4] _(1,63 MB)_\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Dear Thabile,Does the issue occurs for all users in plant? Do users experience issue ony in MM server? If there are fewer tabs open"", \'Comment 4: does the system behave the same way?{color:#0747a6}_It does not allow a refresh\', \'Comment 5: the only solution being to reload the entire site then are we able to use the report again. dhp refresh does not work._{color}{color:#172b4d}Should I understand that you need the same report again like presented\', \'Comment 6: ie. from 28th of October to 28th of November when returning to Daily control reports?{color}{color:#172b4d}Just to confirm\', ""Comment 7: on the movie you reload report with Refresh button ... Could you please confirm how report should be refreshed? !image-2022-12-14-11-50-43-941.png!{color}{color:#172b4d}Regards{color}\'"", ""Comment 8: \'Odtworzyłam sytuację na moim userze"", \'Comment 9: przeklikując się przez moduły planta (identycznie jak widac na filmiku) powrót do Daily Control Reports u mnie powoduje zzmianę filtra na datach\', ""Comment 10: natomiast knefelki Bulk Approval i Execute Report sa aktywne!image-2022-12-14-15-00-43-271.png!\'"", ""Comment 11: \'Hello"", ""Comment 12: the issue was resolved in 8.3.0... (see video from test environment on how it should behave) and yes all plants have this issue.!image![^2022-12-15_8-30-51.mp4] _(1,07 MB)_\'"", ""Comment 13: \'Dear Thabile,Could you please ask some users to clear Cache and cookies and let me know if it helped?Regards\'"", ""Comment 14: \'Hello"", ""Comment 15: I have been using the admin profile to check. I had and have again cleared cache as well as cookies. the issue still exists. \'"", ""Comment 16: \'Próbowałam przeklikać z widokiem dla dev"", \'Comment 17: to za pierwszym razem poszła 400\', ""Comment 18: ale po przeklikaniu wszystkiego brak błędów!image-2022-12-16-08-31-36-026.png!Tylko filtr wraca do dzisiejszej daty!image-2022-12-16-08-32-05-447.png!\'"", ""Comment 19: \'Dear Thabile,We still cannot reproduce this issue.Could you please confirm if browser was restarted after clearing cache?Could you please let me know or confirm if user is logged"", \'Comment 20: for example\', ""Comment 21: in Umlaas Road server and the issue occurs in DHP Umlaas?Could you please ask one user to recreate situation but first open dev view in browser (please click F12 button to open the console) and record it?!image-2022-12-21-13-07-33-645.png!Regards\'"", ""Comment 22: \'Hello"", ""Comment 23: please see attached[^from server.mp4] _(1,63 MB)_[^dev view.mp4] _(1,22 MB)_\'"", ""Comment 24: \'Hi,Thank you for recordings. But"", \'Comment 25: the dev view\', \'Comment 26: as I metioned before\', \'Comment 27: we need console not elements. If it would be possible to make the recordin again\', ""Comment 28: I would be very thankful.Regards!image-2022-12-22-10-19-56-144.png!\'"", ""Comment 29: \'Hello"", ""Comment 30: as per our discussion!image-1![^2022-12-22_15-20-01.mp4] _(1,53 MB)_\'"", ""Comment 31: \'Thank you\'"", ""Comment 32: \'Chodzi o to że po powrocie do Daily control report i wybraniu Bulk aproval nie ma opcji na dole: !screenshot-1! - zostaje Download jak przy execute report - pomaga F5.To co w DAP-12061.\'"", ""Comment 33: \'[~maciej.dobrzanski@kotrak.com]to by trzeba chyba Oli podesłać czy oddelegować czy coś. Tak"", \'Comment 34: jak Piotrek pisał\', \'Comment 35: brakuje tych trzech knefli na dole\', ""Comment 36: co ze zgłoszenia niekoniecznie wynikało...\'"", ""Comment 37: \'Na Firefox też nie działa!image-2023-01-10-13-35-14-485.png!\'"", ""Comment 38: \'To jest dalej to samohttps://helpdesk.kotrak.com/browse/DAP-12061\'"", ""Comment 39: \'Udało mi się znaleźć babola :)\'"", ""Comment 40: \'[~gedeon.kucharski@kotrak.com]!image-2023-01-11-07-43-48-797.png|width=281,height=202!\'"", ""Comment 41: \'Okay"", \'Comment 42: w wersji 8.3.1 najnowszej ten case został poprawiony.[~maciej.dobrzanski@kotrak.com]\', ""Comment 43: [~aleksandra.przybylek@kotrak.com]trzeba by dopytać ich kiedy ewentualnie można by im podegrać.\'"", ""Comment 44: \'This problem has been fixed in the new version of the application.\'"", ""Comment 45: \'Dear Thabile,As Piotr mentioned"", \'Comment 46: problem has been fixed in the newest version. Please\', ""Comment 47: contact your Project Manager to set relevant date for upgrade.Regards\'"", ""Comment 48: \'Hello,you can close this ticket\']""]\nRelated Issues:\n[\'DAP-13180\', \'DGS-6795\', \'DAP-12061\']\n\n### End'}"
967,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8064\n\n### Instruction:\nIO....610 was created in Milas with call off for Meppel and sent to DHC/DHP/PCS. ASN is not available in DHP. In Masterdata I see that the ASN is missing is Vehicle Control.\r\n\r\nPlease check why this ASN (and possible others?) are not in Vehicle Control / in DHP.\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 3: \\\'An error occurred while saving the entity changes. See the inner exception for details. -> The INSERT statement conflicted with the FOREIGN KEY constraint ""FK_Orders_ContactDatas_MainBusinessPartnerId_MainBusinessPartnerContactDataId"". The conflict occurred in database ""DHPlantVCBusinessLogicMain""\', \'Comment 4: table ""dbo.ContactDatas"".The statement has been terminated.!image-2022-12-14-10-38-38-592.png!\\\'\', \'Comment 5: \\\'Could you please provide here information for Bussines Partner with code 96 ?for that order in dhp after resending I got this error messageAn error occurred while saving the entity changes. See the inner exception for details. -> The INSERT statement conflicted with the FOREIGN KEY constraint ""FK_Orders_ContactDatas_MainBusinessPartnerId_MainBusinessPartnerContactDataId"". The conflict occurred in database ""DHPlantVCBusinessLogicMain""\', \'Comment 6: table ""dbo.ContactDatas"".The statement has been terminated.after you did that you may send as information or tried to use resend on marked row:!image-2022-12-14-10-51-39-599.png!The esend should be done on every module\\\'\', ""Comment 7: \'{color:#000000}Hi,{color} {color:#000000}Code 96 is a business partner created for one of our own warehouses (site 96){color} {color:#000000}In this transfer order"", \'Comment 8: it is the location from which items are delivered{color}  {color:#000000}{color}  {color:#000000}What I see from logging\', \'Comment 9: the busines paerner data was nog correct in DHP? Or was data missing?{color} {color:#000000}{color}  {color:#000000}We resend order with other BP linked and now the order is visble in DHP and intake can be registered.{color} {color:#000000}{color}  {color:#000000}This ticket can be closed.{color}  {color:#000000}{color}   {color:#000000}{color}     {color:#000000}       {color}{color:black}{color} {color:#000000} {color}{color:black}Best regards | Met vriendelijke groeten,{color}{color:#000000}{color}{color:black}  Bob Kennedy{color} {color:#000000}{color}{color:black}Informatie analist{color}{color:#000000} {color}{color:black}{color}{color:#000000} {color}{color:#000000} {color} |{color:#000000}{color} {color:#000000}{color}De Heus Voeders{color:#000000} <[http://www.de-heus.nl/]>{color}{color:black}{color}{color:#000000} {color}{color:#000000} {color}|{color:#000000}{color}{color:#006FB7} * De Heus Voeders B.V.*{color}{color:#000000}{color}{color:#006FB7}{color} {color:#000000}{color}{color:#006FB7} Postbus 396 6710 BJ Ede{color}{color:#000000}{color}{color:#006FB7} Rubensstraat 1756717 VE Ede  *M* 06 - 53 224 931 KvK 14626985{color}{color:#000000}{color}{color:black} {color}{color:#000000}{color}{color:#006FB7} _ Op dit e-mailbericht en eventuele bijlage(n) is de disclaimer van toepassing_{color}{color:#000000}{color}{color:#006FB7}{color} {color:#000000}{color}{color:#006FB7} _ gepubliceerd op de website van_{color} [{color:#006FB7} _De Heus Voeders_{color}|http://www.de-heus.nl/maildisclaimer]{color:#006FB7} _._{color}{color:#000000}{color}{color:#006FB7}{color} {color:#000000} {color}{color:#000000} {color}| |{color:#000000}{color}{color:black}{color} image007.jpg@01D62AA3.AD14DDB0{color:black}{color}{color:#000000} {color}{color:#000000} {color}| |{color:#000000}{color}{color:black}{color} image004.jpg@01D62AA3.AD2CAB70{color:black}{color}{color:#000000} {color}{color:#000000} {color}| {color:#000000}{color} ---- {color:#000000} *From:* Agnieszka Januszewska (Jira) <jira@kotrak.com>  *Sent:* Wednesday\', \'Comment 10: December 14\', \'Comment 11: 2022 10:53 AM  *To:* Kennedy\', ""Comment 12: Bob <BKennedy@deheus.com>  *Subject:* DGS-8064 Internal order is sent to PCS but not available in DHP{color}  |{color:#ffffff} CAUTION: This message originated from outside the organisation. Please do not click on links or open attachments unless you trust the sender and know the content is safe.{color} |\']""]\nRelated Issues:\n[]\n\n### End'}"
968,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8063\n\n### Instruction:\nHi, from Wiola\r\nRaport needs to be correct.\r\n\r\nRafał Boniecki\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!!image-1!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Any news?\'"", ""Comment 4: \'According to call with Wioletta Winkler report will be corrected. Predicted date is first week of January 2023\'"", \'Comment 5: ""report has been corrected. Wioletta informed by e-mail. I\\\'m waiting for feedback from Wioletta""\', ""Comment 6: \'*From:* Winkler"", \'Comment 7: Wioletta <wwinkler@deheus.com>  *Sent:* Saturday\', \'Comment 8: January 7\', \'Comment 9: 2023 2:25 PM *To:* Monika Biśta <monika.bista@kotrak.com> *Subject:* ODP: uzupełnie raportu nadgodzinDzień dobryBider- jest widoczny poprawnie w grudniu.U Pana Kostrzewy w grudniu już nie są widoczne na raporcie godz. średniotygodniowe (100). Wypłacona odstawa (powyżej normy jest i nie jest zaznaczone w raporcie.|PozdrawiamWiola***Wioletta Winkler**kierownik sekcji administracji płac*||+48600291 312[wwinkler@deheus.com|mailto:wwinkler@deheus.com][*www.deheus.pl*|https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.deheus.pl%2F&data=04%7C01%7Cwwinkler%40deheus.com%7Cd75ad8044e434b7cdc6a08d9150c5b5b%7C1004261bdfb74f37830f7438cb8a1b69%7C1%7C0%7C637563965071751417%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=X6qcIpvA%2Bw63vtWwf7ooaJK7gtrJAQHCZ70Yo4vPQs8%3D&reserved=0]**W tytułach wiadomości stosuję regułę *ARDI*:  *A* – proszę o akcję\', \'Comment 10: działanie; *R* – proszę o recenzję\', \'Comment 11: reakcję; *D* – proszę o decyzję; *I* – informuję|||| |DeHeusSp.zo.o. ul.Lotnicza21B 99–100Łęczyca tel.:247210400 fax:247210404 REGON:011917655 NIP:526-13-06-893 wysokośćkapitałuzakładowego:22141000.00zł  nrKRS:0000060991 SądRejonowydlaŁodzi-ŚródmieściawŁodzi XXWydziałKRS||Treść tej informacji może być poufna\', \'Comment 12: w związku z czym powinna trafić bezpośrednio do rąk adresata. Jakiekolwiek jej ujawnianie\', \'Comment 13: rozpowszechnianie\', ""Comment 14: bądź kopiowanie jest zabronione.||\'"", ""Comment 15: \'!image-2!\'"", ""Comment 16: \'*From:* Monika Biśta  *Sent:* Tuesday"", \'Comment 17: January 17\', \'Comment 18: 2023 7:58 AM *To:* Winkler Wioletta <wwinkler@deheus.com> *Subject:* FW: uzupełnie raportu nadgodzinDzień dobry,Proszę o poniższą informację możemy się zdzwonić w tym tygodniu jestem 7-15.*Pozdrawiam / Best regards,**Monika Biśta* mobile: +48538212 162tel.: +48 3235 12721e-mail: +[monika.bista@kotrak.com|mailto:monika.bista@kotrak.com]+*Kotrak S.A.*Parczewskiego 2540-582 KatowicePoland*tel./phone:* (+48 32)35 12700[www.kotrak.com|https://kotrak.com/]*Certified ISO 9001:2015*++*Sąd Rejonowy / District Court* *Katowice-Wschód w Katowicach* *Wydział VIII Gospodarczy KRS\', \'Comment 19: nr KRS*: 0000704357*NIP*: 954-24-96-628 *Regon:* 277683949*Kapitał zakładowy / Share capital:* 1.052.700,00 zł\', \'Comment 20: opłacony w całości / paid in full*Lokalizacje / Locations:* Kraków\', \'Comment 21: Łódź\', \'Comment 22: Warszawa\', \'Comment 23: Opole\', \'Comment 24: Bielsko-Biała\', \'Comment 25: Gdańsk\', \'Comment 26: London*From:* Monika Biśta  *Sent:* Monday\', \'Comment 27: January 9\', \'Comment 28: 2023 8:06 AM *To:* Winkler\', \'Comment 29: Wioletta <[wwinkler@deheus.com|mailto:wwinkler@deheus.com]> *Subject:* RE: uzupełnie raportu nadgodzinDzień dobry,U Pana Kostrzewy dodałam godziny średniodobowe 100 \', \'Comment 30: W którym miejscu w raporcie powinna być wykazana informacja powyżej normy?*Pozdrawiam / Best regards,**Monika Biśta* mobile: +48538212 162tel.: +48 3235 12721e-mail: +[monika.bista@kotrak.com|mailto:monika.bista@kotrak.com]+*Kotrak S.A.*Parczewskiego 2540-582 KatowicePoland*tel./phone:* (+48 32)35 12700[www.kotrak.com|https://kotrak.com/]*Certified ISO 9001:2015*++*Sąd Rejonowy / District Court* *Katowice-Wschód w Katowicach* *Wydział VIII Gospodarczy KRS\', \'Comment 31: nr KRS*: 0000704357*NIP*: 954-24-96-628 *Regon:* 277683949*Kapitał zakładowy / Share capital:* 1.052.700,00 zł\', \'Comment 32: opłacony w całości / paid in full*Lokalizacje / Locations:* Kraków\', \'Comment 33: Łódź\', \'Comment 34: Warszawa\', \'Comment 35: Opole\', \'Comment 36: Bielsko-Biała\', \'Comment 37: Gdańsk\', \'Comment 38: London\', ""Comment 39: Santa Clara\'"", ""Comment 40: \'Cześć"", \'Comment 41: przesłałem to do Wioli\', \'Comment 42: ale ma cały ten tydzień urlop\', ""Comment 43: więc nie wiem czy się odezwie...\'"", ""Comment 44: \'ok przyszły tydzień pracuję 7-15 wtedy myślę skontaktujemy się\'"", ""Comment 45: \'przypomnieć w tym temacie. Ten tydzień jestem 12-20"", ""Comment 46: przyszły 7-15\'"", ""Comment 47: \'!image-3!\'"", ""Comment 48: \'any feedback?\'"", ""Comment 49: \'!image-4!\'"", ""Comment 50: \'6.10 u tego pracownika oznaczony jako OBM to 4h a nie 1h . Stąd pochodzi 3h różnicy między raportem a wyliczeniami z maila. Pozostałe dni są ok. Proszę o weryfikację po stronie Deheus. !screenshot-1! \'"", ""Comment 51: \'!image-5!\']""]\nRelated Issues:\n[]\n\n### End'}"
969,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8062\n\n### Instruction:\nFrom approx 08.30 DHP does not seem to process dispatch messages for DHP Maasbracht. Messages do arrive from PCS and are accepted in DHP, but VT is not created and no packing slip XML is generated.\r\nThere was another ticket about this issue (did you install a logger on DHP Maasbracht to monitor for delays?). Here you have more examples (see timestamp messages from PCS and overview of VTs\r\nE.g. dispatch message for trip 00946181 (received at 08:52) from PCS is for an active trip (not cancelled), but VT is missing.\r\n\n\n### Response:\n[""Comment 1: [\'!image!!image-1!!image-2!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Hi Bob,We can see a lot of messages were to process so we will analise this log. But it looks now message queues are clean right now. Please"", ""Comment 4: let me know if you can see documents processing.Regards\'"", \'Comment 5: ""I still do not see any new VT\\\'s created (so no SPS will be generated) in DHP.""\', ""Comment 6: \'How many VTs are missing? Do we have this information?\'"", ""Comment 7: \'But how many VTs should be cerated approximately? 10? 20?\'"", ""Comment 8: \'As far as I can check"", ""Comment 9: already 10 dispatches are not processed. Please check services / why dispatches messages from PCS are not picked up in DHP. Plant needs the packing slips.First missing dispatch in DHP: see marked line in attached screenprint!image-3!\'"", \'Comment 10: \\\'{code:java}2022-12-14 10:04:29 (/Plant.Integration.PCS.NL/DHVD01AP178/31760/162) [Error] Microsoft.AspNetCore.Server.IIS.Core.IISHttpServer - Connection ID """"18230571293206390851""""\', \'Comment 11: Request ID """"80002844-0000-fd00-b63f-84710c7967bb"""": An unhandled exception was thrown by the application.System.Data.SqlClient.SqlException (0x80131904): Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding. ---> System.ComponentModel.Win32Exception (258): The wait operation timed out.   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception\', \'Comment 12: Boolean breakConnection\', \'Comment 13: Action`1 wrapCloseInAction)   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj\', \'Comment 14: Boolean callerHasConnectionLock\', \'Comment 15: Boolean asyncClose)   at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior\', \'Comment 16: SqlCommand cmdHandler\', \'Comment 17: SqlDataReader dataStream\', \'Comment 18: BulkCopySimpleResultSet bulkCopyHandler\', \'Comment 19: TdsParserStateObject stateObj\', \'Comment 20: Boolean& dataReady)   at System.Data.SqlClient.SqlDataReader.TryConsumeMetaData()   at System.Data.SqlClient.SqlDataReader.get_MetaData()   at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds\', \'Comment 21: RunBehavior runBehavior\', \'Comment 22: String resetOptionsString)   at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior\', \'Comment 23: RunBehavior runBehavior\', \'Comment 24: Boolean returnStream\', \'Comment 25: Boolean async\', \'Comment 26: Int32 timeout\', \'Comment 27: Task& task\', \'Comment 28: Boolean asyncWrite\', \'Comment 29: SqlDataReader ds)   at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior)   at Dapper.SqlMapper.ExecuteReaderWithFlagsFallback(IDbCommand cmd\', \'Comment 30: Boolean wasClosed\', \'Comment 31: CommandBehavior behavior) in /_/Dapper/SqlMapper.cs:line 1075   at Dapper.SqlMapper.QueryRowImpl[T](IDbConnection cnn\', \'Comment 32: Row row\', \'Comment 33: CommandDefinition& command\', ""Comment 34: Type effectiveType) in /_/Dapper/SqlMapper.cs:line 1187   at Plant.Integration.PCS.NL.Infrastructure.Persistence.Repositories.LogRepository.LogWebApiRequest(WebApiRequestDto request) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\1b53a96170a797c0\\\\\\\\Plant.Integration.PCS.NL\\\\\\\\Plant.Integration.PCS.NL.Infrastructure.Persistence\\\\\\\\Repositories\\\\\\\\LogRepository.cs:line 33   at Plant.Integration.PCS.NL.Middleware.ApiRequestLoggingMiddleware.InvokeAsync(HttpContext context) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\1b53a96170a797c0\\\\\\\\Plant.Integration.PCS.NL\\\\\\\\Plant.Integration.PCS.NL\\\\\\\\Middleware\\\\\\\\ApiRequestLoggingMiddleware.cs:line 58   at Microsoft.AspNetCore.Server.IIS.Core.IISHttpContextOfT`1.ProcessRequestAsync()ClientConnectionId:6e465ec9-bbf3-4675-b756-2a9566512378Error Number:-2,State:0,Class:11{code}\'"", \'Comment 35: ""{code:java}2022-12-14 08:32:19 (null/Plant.PCS.BusinessLogic/DHVD01AP178/31780/8) [Warning] Microsoft.EntityFrameworkCore.Query - Compiling a query which loads related collections for more than one collection navigation\', ""Comment 36: either via \'Include\' or through projection"", ""Comment 37: but no \'QuerySplittingBehavior\' has been configured. By default"", ""Comment 38: Entity Framework will use \'QuerySplittingBehavior.SingleQuery\'"", \'Comment 39: which can potentially result in slow query performance. See https://go.microsoft.com/fwlink/?linkid=2134277 for more information. To identify the query that\\\'s triggering this warning call \\\'ConfigureWarnings(w => w.Throw(RelationalEventId.MultipleCollectionIncludeWarning))\\\'.{code}""\', ""Comment 40: \'VT for trip is in plant now.In my opinion"", \'Comment 41: we need to wait for processing documents. As tehy will appear in some time. In the mean time\', ""Comment 42: can we lower priority to P2?Regards\'"", ""Comment 43: \'!image-2022-12-14-10-24-36-518.png!\'"", \'Comment 44: ""I see that VT\\\'s are now created in DHP and I was informed that VT\\\'s from one hour ago are picked up and SPS are printed.Prio 2: for this ticket it is okBut: I ask you to analyze this further and find a solution to solve these delays. The trucks from last hour left without SPS because they cannot wait for one hour until document is generated. This is an issue because it is not allowed and customers do not accept it anymore.Last weeks we had several moments where we had these delays\', \'Comment 45: also for other plants. I hope you found information in the log why it takes such a long time / what type of data is taking that long to process. If we can avoid sending this data (e.g. recipes)\', \'Comment 46: please let us know. ""\', ""Comment 47: \'Tripped marked in yellow have VTs now in plant:!image-2022-12-14-10-46-31-337.png!\'"", ""Comment 48: \'Sure"", ""Comment 49: thank you. We are now analysing the data. Will let you know as soon as possible.Regards\'"", ""Comment 50: \'I have checked"", ""Comment 51: al VTs from above list are in plant now.\'"", ""Comment 52: \'Dear Bob,We are analysing data within RCA task for this issue underDGS-7949. I know you have access to RCA task"", \'Comment 53: so I think we can close this incident as missing VTs are now in Plant.Please\', ""Comment 54: let me know if I can close this incident.Regards\'"", ""Comment 55: \'{color:#000000}Ok"", \'Comment 56: you can close this ticket.{color} {color:#000000}Can you add me to DGS-7949 I cannot access it.{color}     {color:#000000}       {color}{color:black}{color} {color:#000000} {color}{color:black}Best regards | Met vriendelijke groeten,{color}{color:#000000}{color}{color:black}  Bob Kennedy{color} {color:#000000}{color}{color:black}Informatie analist{color}{color:#000000} {color}{color:black}{color}{color:#000000} {color}{color:#000000} {color} |{color:#000000}{color} {color:#000000}{color}De Heus Voeders{color:#000000} <[http://www.de-heus.nl/]>{color}{color:black}{color}{color:#000000} {color}{color:#000000} {color}|{color:#000000}{color}{color:#006FB7} * De Heus Voeders B.V.*{color}{color:#000000}{color}{color:#006FB7}{color} {color:#000000}{color}{color:#006FB7} Postbus 396 6710 BJ Ede{color}{color:#000000}{color}{color:#006FB7} Rubensstraat 1756717 VE Ede  *M* 06 - 53 224 931 KvK 14626985{color}{color:#000000}{color}{color:black} {color}{color:#000000}{color}{color:#006FB7} _ Op dit e-mailbericht en eventuele bijlage(n) is de disclaimer van toepassing_{color}{color:#000000}{color}{color:#006FB7}{color} {color:#000000}{color}{color:#006FB7} _ gepubliceerd op de website van_{color} [{color:#006FB7} _De Heus Voeders_{color}|http://www.de-heus.nl/maildisclaimer]{color:#006FB7} _._{color}{color:#000000}{color}{color:#006FB7}{color} {color:#000000} {color}{color:#000000} {color}| |{color:#000000}{color}{color:black}{color} image007.jpg@01D62AA3.AD14DDB0{color:black}{color}{color:#000000} {color}{color:#000000} {color}| |{color:#000000}{color}{color:black}{color} image004.jpg@01D62AA3.AD2CAB70{color:black}{color}{color:#000000} {color}{color:#000000} {color}| {color:#000000}{color} ---- {color:#000000} *From:* Aleksandra Przybyłek (Jira) <jira@kotrak.com>  *Sent:* Wednesday\', \'Comment 57: December 14\', \'Comment 58: 2022 1:17 PM  *To:* Kennedy\', ""Comment 59: Bob <BKennedy@deheus.com>  *Subject:* DGS-8062 Dispatches not processed in DHP{color}  |{color:#ffffff} CAUTION: This message originated from outside the organisation. Please do not click on links or open attachments unless you trust the sender and know the content is safe.{color} |\'"", ""Comment 60: \'Please"", \'Comment 61: verify\', ""Comment 62: you are added as a request participant since the very beginning :)!image-2022-12-14-14-40-04-436.png!\'"", ""Comment 63: \'{color:#000000}Ok"", \'Comment 64: indeed I have access\', \'Comment 65: perhaps the URL I used was not correct.{color}   {color:#000000}{color}     {color:#000000}       {color}{color:black}{color} {color:#000000} {color}{color:black}Best regards | Met vriendelijke groeten,{color}{color:#000000}{color}{color:black}  Bob Kennedy{color} {color:#000000}{color}{color:black}Informatie analist{color}{color:#000000} {color}{color:black}{color}{color:#000000} {color}{color:#000000} {color} |{color:#000000}{color} {color:#000000}{color}De Heus Voeders{color:#000000} <[http://www.de-heus.nl/]>{color}{color:black}{color}{color:#000000} {color}{color:#000000} {color}|{color:#000000}{color}{color:#006FB7} * De Heus Voeders B.V.*{color}{color:#000000}{color}{color:#006FB7}{color} {color:#000000}{color}{color:#006FB7} Postbus 396 6710 BJ Ede{color}{color:#000000}{color}{color:#006FB7} Rubensstraat 1756717 VE Ede  *M* 06 - 53 224 931 KvK 14626985{color}{color:#000000}{color}{color:black} {color}{color:#000000}{color}{color:#006FB7} _ Op dit e-mailbericht en eventuele bijlage(n) is de disclaimer van toepassing_{color}{color:#000000}{color}{color:#006FB7}{color} {color:#000000}{color}{color:#006FB7} _ gepubliceerd op de website van_{color} [{color:#006FB7} _De Heus Voeders_{color}|http://www.de-heus.nl/maildisclaimer]{color:#006FB7} _._{color}{color:#000000}{color}{color:#006FB7}{color} {color:#000000} {color}{color:#000000} {color}| |{color:#000000}{color}{color:black}{color} image007.jpg@01D62AA3.AD14DDB0{color:black}{color}{color:#000000} {color}{color:#000000} {color}| |{color:#000000}{color}{color:black}{color} image004.jpg@01D62AA3.AD2CAB70{color:black}{color}{color:#000000} {color}{color:#000000} {color}| {color:#000000}{color} ---- {color:#000000} *From:* Aleksandra Przybyłek (Jira) <jira@kotrak.com>  *Sent:* Wednesday\', \'Comment 66: December 14\', \'Comment 67: 2022 2:42 PM  *To:* Kennedy\', ""Comment 68: Bob <BKennedy@deheus.com>  *Subject:* DGS-8062 Dispatches not processed in DHP{color}  |{color:#ffffff} CAUTION: This message originated from outside the organisation. Please do not click on links or open attachments unless you trust the sender and know the content is safe.{color} |\'"", ""Comment 69: \'Good. Thank you.Regards\']""]\nRelated Issues:\n[\'DGS-7949\']\n\n### End'}"
970,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8061\n\n### Instruction:\nThere is sample result in DHC MM BU. However, we got informed from Formulation Department that they cannot see result started from 25-Nov-2022.\r\nPlease check. I do attached screenshot of DHC for your reference\n\n### Response:\n[""Comment 1: [\'!image!!image-1!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'We are unable to log on to your VPN"", ""Comment 4: !image-2022-12-14-08-12-51-716.png!\'"", ""Comment 5: \'Hi"", \'Comment 6: We are looking into it now. We will update you back about access.Best Regards\', ""Comment 7: Clara\'"", \'Comment 8: \\\'Please set up the Forticlient VPN as per attached and try for connection with your current VPN user. Configuration of Preshare key is ""Deheus@IPsec"" !IPsec-2.jpg|thumbnail!!IPsec-3.jpg|thumbnail!!IPsec-1.jpg|thumbnail!\\\'\', ""Comment 9: \'!image-2022-12-14-13-45-15-586.png!\'"", ""Comment 10: \'!image-2022-12-14-13-46-09-343.png!\'"", ""Comment 11: \'!image-2022-12-14-13-53-13-478.png!\'"", ""Comment 12: \'!image-2022-12-14-14-21-02-902.png! nie dla dla tego sample analisysFROM [DHP_YAN].[dbo].[SampleAnalysis]-- where SAn_SRgId= 230087\'"", ""Comment 13: \'You mentioned in task title about DHH"", \'Comment 14: but in other task you mentioned DHC\', \'Comment 15: also DHc is visible in screenshoot\', ""Comment 16: you missed results in DHC and we should focus on sample registers without results ?\'"", \'Comment 17: ""There is 2 issues. This Ticket is for DHC to DHH for all sample result. The other ticket is from DHP to DHC for Aqua Factory (57) result only.As I mention\', ""Comment 18: Formulation Department say they cannot see the result on DHH. That\'s why I raise it. Last night"", \'Comment 19: Formulation Department informed us that they can see it on DHH. So\', \'Comment 20: you can close this ticket. Please investigate for other ticket. Thanks""]\']\nRelated Issues:\n[]\n\n### End'}"
971,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8060\n\n### Instruction:\nThere is all sample result from 57- Aqua Plant result not in DHC. Starting from late November. There is result on DHP been executed. \r\nFor Example: \r\nSample Code - 57221201001.\r\n\r\nI do attached screen shot for more details.\r\n\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!!image-1!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'We are unable to log on to your vpn!image-2022-12-14-08-08-21-125.png!\'"", ""Comment 4: \'Hi"", \'Comment 5: We are looking into it and will update you back Best Regards\', ""Comment 6: Clara\'"", \'Comment 7: \\\'Please set up the Forticlient VPN as per attached and try for connection with your current VPN user. Configuration of Preshare key is ""Deheus@IPsec"" !IPsec-2.jpg|thumbnail!!IPsec-3.jpg|thumbnail!!IPsec-1.jpg|thumbnail!\\\'\', ""Comment 8: \'https://helpdesk.kotrak.com/browse/DGS-6936\'"", ""Comment 9: \'SELECT TOP (1000) [SAR_Id] ,[SAR_SAnId] ,[SAR_Identity] ,[SAR_Date] ,[SAR_Type] ,[SAR_ForeignId] ,[Sar_plantid] FROM [DHP_YAN].[dbo].[SampleAnalysisResult] where sar_sanid=117766SELECT TOP (1000) [SAR_Id] ,[SAR_SAnId] ,[SAR_Identity] ,[SAR_Date] ,[SAR_Type] ,[SAR_ForeignId] ,[Sar_plantid] FROM [DHP_YAN].[dbo].[SampleAnalysisResult] where sar_sanid=117766\'"", \'Comment 10: ""W odróznieniu do zalinkowanego taska tutaj nie zgasdza się plat it na analisys resultselect a.SAn_Id,r.SRg_PlantId,a.SAn_PlantId,AR.sar_plantid,r.SRg_Codefrom SampleRegister R join SampleAnalysis A on A.SAn_SRgId = srg_id left join SampleAnalysisResult AR on AR.SAR_SAnId = A.SAn_Idwhere (Sar_plantid <>SAn_PlantId)and SAn_CreateDate>\\\'2022-12-01 00:00\\\'!image-2022-12-15-10-34-05-515.png!""\', ""Comment 11: \'Co do ostatniego komentarza ten sar_Plantid jest dobrze mają 55 wszystkie - są dwa planty w jednym.!image-2022-12-15-19-03-48-839.png!Zostały przesłane analizy i wyniki około 15 dziś ich czasu  !screenshot-1! I błędy się skończyły dla dhcservice o tej godzinie - Required entity was not found !screenshot-2!  Teraz dane są w DHC: !screenshot-3! \'"", ""Comment 12: \'Please verify and send a feedback - thank you. !screenshot-4! \'"", ""Comment 13: \'All are ok now. May I know the root cause of this issue?\'"", ""Comment 14: \'We were unable to find a clear reason why the samples did not originally pass"", ""Comment 15: after restarting the services the results did pass. It is likely that there may have been some problems with the infrsatructure.Can the request be closed?\'"", ""Comment 16: \'Sure. Please close the request. \']""]\nRelated Issues:\n[]\n\n### End'}"
972,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8059\n\n### Instruction:\nWe have problem to remove one barcode from VT using mobile, system is showing error message when I try to remove.\r\nThese barcode was loaded by mobile picking without use of a bag label but they loadade wrong barcode and was trying to remove.\r\nCould you check why we have this error and fix it?\r\n\r\nThank you\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 3: "" !screenshot-1! {code:java}SELECT *  FROM [DHPlantWmsBusinessLogicMain].[dbo].[WarehouseOrderElements]  where id=\\\'B982C7F2-63BF-4822-AD3B-AC21E4BEE993\\\'SELECT *  FROM [DHPlantWmsBusinessLogicMain].[dbo].[VehicleTicketElements]  where id=\\\'39E87E76-2B71-4C0E-82D3-B1B5BD969D8C\\\'{code}""\', \'Comment 4: \\\'{code:java}2022-12-13 13:51:40 (f3d4b686-79d6-47a2-9388-6a9286b60cdc/Plant.WMS.BusinessLogic/BR-1-SV-VM0604/968/218) [Error] Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware - Error during request{  ""scheme"": ""http""\', \'Comment 5:  ""host"": {    ""Value"": ""br-1-sv-vm0604.mubbrasil.local:85""\', \'Comment 6:    ""HasValue"": true\', \'Comment 7:    ""Host"": ""br-1-sv-vm0604.mubbrasil.local""\', \'Comment 8:    ""Port"": 85  }\', \'Comment 9:  ""path"": ""/api/WarehouseDispatch/withdrawUnitLoadFromWarehouseDispatchOrder""\', \'Comment 10:  ""queryString"": []\', \'Comment 11:  ""requestBody"": ""{\\\\\\\\""warehouseOrderId\\\\\\\\"":\\\\\\\\""b982c7f2-63bf-4822-ad3b-ac21e4bee993\\\\\\\\"",\\\\\\\\""unitLoadBarcode\\\\\\\\"":{\\\\\\\\""code\\\\\\\\"":\\\\\\\\""85-W00XQ8\\\\\\\\""}}""}.System.InvalidOperationException: Sequence contains more than one element   at System.Linq.ThrowHelper.ThrowMoreThanOneElementException()   at System.Linq.Enumerable.TryGetSingle[TSource](IEnumerable`1 source\', \'Comment 12: Boolean& found)   at System.Linq.Enumerable.SingleOrDefault[TSource](IEnumerable`1 source)   at Kotrak.Common.Infrastructure.Repositories.AggregateRootRepository`2.GetByExpression(Expression`1 expression)   at Plant.WMS.BusinessLogic.Infrastructure.Persistance.WarehouseDispatches.WarehouseDispatchRepository.GetWarehouseDispatchForWarehouseOrderAndUnitLoadBarcode(AggregateId warehouseOrderId\', \'Comment 13: AggregateId unitLoadId) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Infrastructure.Persistance\\\\\\\\WarehouseDispatches\\\\\\\\WarehouseDispatchRepository.cs:line 87   at Plant.WMS.BusinessLogic.Application.WarehouseDispatches.WarehouseDispatchService.GetWarehouseDispatchOrThrow(AggregateId warehouseOrderId\', \'Comment 14: AggregateId unitLoadId) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Application\\\\\\\\WarehouseDispatches\\\\\\\\WarehouseDispatchService.cs:line 1054   at Plant.WMS.BusinessLogic.Application.WarehouseDispatches.WarehouseDispatchService.WithdrawUnitLoadFromWarehouseDispatchOrder(AggregateId warehouseOrderId\', \'Comment 15: Barcode unitLoadBarcode) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Application\\\\\\\\WarehouseDispatches\\\\\\\\WarehouseDispatchService.cs:line 445   at Plant.WMS.BusinessLogic.Application.WarehouseDispatches.Handlers.WithdrawUnitLoadFromWarehouseDispatchOrderCommandHandler.<>c__DisplayClass5_0.<Handle>b__0() in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Application\\\\\\\\WarehouseDispatches\\\\\\\\Handlers\\\\\\\\WithdrawUnitLoadFromWarehouseDispatchOrderCommandHandler.cs:line 39   at Plant.WMS.BusinessLogic.Application.Workflows.WorkflowRunner.Run(Workflow workflow) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Application\\\\\\\\Workflows\\\\\\\\WorkflowRunner.cs:line 17   at Plant.WMS.BusinessLogic.Application.WarehouseDispatches.Handlers.WithdrawUnitLoadFromWarehouseDispatchOrderCommandHandler.Handle(WithdrawUnitLoadFromWarehouseDispatchOrderCommand command) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Application\\\\\\\\WarehouseDispatches\\\\\\\\Handlers\\\\\\\\WithdrawUnitLoadFromWarehouseDispatchOrderCommandHandler.cs:line 44   at Kotrak.Common.Infrastructure.Commands.CommandEnvironment.Run[TCommand](TCommand command)   at Kotrak.Common.Infrastructure.Commands.Decorators.IntercontextEventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command)   at Kotrak.Common.Infrastructure.Commands.Decorators.EventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command)   at Kotrak.Common.Infrastructure.Commands.Decorators.ValidationCommandEnvironmentDecorator.Run[TCommand](TCommand command)   at Castle.DynamicProxy.AbstractInvocation.Proceed()   at Kotrak.Common.Infrastructure.Interceptors.LoggingInterceptor`1.Intercept(IInvocation invocation)   at Castle.DynamicProxy.AbstractInvocation.Proceed()   at Kotrak.Common.Infrastructure.Commands.Decorators.HistoryGateDecorator.Dispatch[TCommand](TCommand command)   at Plant.WMS.BusinessLogic.Infrastructure.Api.Controllers.WarehouseDispatchController.WithdrawUnitLoadFromWarehouseDispatchOrder(WithdrawUnitLoadFromWarehouseDispatchOrderViewModel viewModel) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\f579cce2236e7995\\\\\\\\Plant.WMS.BusinessLogic\\\\\\\\Plant.WMS.BusinessLogic.Infrastructure.Api\\\\\\\\Controllers\\\\\\\\WarehouseDispatchController.cs:line 203   at lambda_method358589(Closure \', \'Comment 16: Object \', \'Comment 17: Object[] )   at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor.SyncActionResultExecutor.Execute(IActionResultTypeMapper mapper\', \'Comment 18: ObjectMethodExecutor executor\', \'Comment 19: Object controller\', \'Comment 20: Object[] arguments)   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeActionMethodAsync()   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next\', \'Comment 21: Scope& scope\', \'Comment 22: Object& state\', \'Comment 23: Boolean& isCompleted)   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeNextActionFilterAsync()--- End of stack trace from previous location ---   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Rethrow(ActionExecutedContextSealed context)   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next\', \'Comment 24: Scope& scope\', \'Comment 25: Object& state\', \'Comment 26: Boolean& isCompleted)   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeInnerFilterAsync()--- End of stack trace from previous location ---   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeFilterPipelineAsync>g__Awaited|20_0(ResourceInvoker invoker\', \'Comment 27: Task lastTask\', \'Comment 28: State next\', \'Comment 29: Scope scope\', \'Comment 30: Object state\', \'Comment 31: Boolean isCompleted)   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker\', \'Comment 32: Task task\', \'Comment 33: IDisposable scope)   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker\', \'Comment 34: Task task\', \'Comment 35: IDisposable scope)   at Microsoft.AspNetCore.Routing.EndpointMiddleware.<Invoke>g__AwaitRequestTask|6_0(Endpoint endpoint\', \'Comment 36: Task requestTask\', \'Comment 37: ILogger logger)   at Swashbuckle.AspNetCore.SwaggerUI.SwaggerUIMiddleware.Invoke(HttpContext httpContext)   at Swashbuckle.AspNetCore.Swagger.SwaggerMiddleware.Invoke(HttpContext httpContext\', ""Comment 38: ISwaggerProvider swaggerProvider)   at Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware.Invoke(HttpContext httpContext){code}\'"", ""Comment 39: \'[~piotr.gaczorek@kotrak.com],Problem istnieje wtedy gdy zeskanowana paleta została więcej niż raz (czyli dwa razy częściowo zeskanowali paletę). Nie wiem dlaczego tak robią. Zawsze mogą częściowo sprzedać raz.Funkcjonalność którą używają została dostarczona w https://helpdesk.kotrak.com/browse/GDC-224. Z racji tego że nie w scope nie było żadnej mowy o wycofaniu a funkcjonalność została dostarczona tylko pod NL jeżeli klient chce to w takiej formie to używać to musi zgłosić GDC.\'"", ""Comment 40: \'Hello. This problem exists when the scanned pallet has been scanned more than once (i.e. partially scanned the pallet twice).It is always possible to partially sell once.GDC is required for this to work as it is (as reported in this task).This functionality has been provided but for NL - GDC-224.Regards\'"", ""Comment 41: \'All information was provided in the last comment.The issue is closed.\']""]\nRelated Issues:\n[\'DAP-13096\']\n\n### End'}"
973,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8058\n\n### Instruction:\nCommunication not working (trips not arriving in DHP), dispatches not processed in DHP, code 500 errors in DHP UI (same type of issues occurred in Utrecht today)\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 2: ""I restarted application but i didn\\\'t get error 500.Please check if there are any missing documents (please provide examples).Thank you.""\', ""Comment 3: \'This ticket can be closed\']""]\nRelated Issues:\n[]\n\n### End'}"
974,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8057\n\n### Instruction:\nWhen we move feed to the next round this should be maximised by the weight of the original delivery. \r\n\r\nNot we can move 5.000kg for instance while the original delivery was only 2.000kg.\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'[~mbovene@deheus.com]this is handled in the newest version of Feed Sale that will be deployed on PROD on Monday. I will close the task when deployment is completed.\'"", ""Comment 3: \'[~ewa.mucha@kotrak.com]you can close this task. Update is working on PROD right now ;).\'"", ""Comment 4: \'Great! I close the task.\']""]\nRelated Issues:\n[]\n\n### End'}"
975,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8056\n\n### Instruction:\nHi\r\n\r\nWe had two DHC x ERP integration erros last week about PLRs:\r\n\r\nPLR LotNumber 0856051222001\r\nPLR LotNumber 0856051222003\r\n\r\nThen we found the reason: There were these two PLRs from Guararapes that had substitutes in PLR, however, DHC and ERP received the original item instead the substitue.\r\n\r\nCould you please fix that?\r\n\r\nThank you very much\n\n### Response:\n[""Comment 1: [\'!image!!image-1!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'!image-2022-12-14-08-58-33-063.png!A po itemid dla substitute:!image-2022-12-14-09-13-13-620.png! !image-2022-12-14-08-58-33-063!!image-2022-12-14-09-13-13-620!\'"", ""Comment 4: \'!image-2022-12-14-09-02-28-353.png!\'"", ""Comment 5: \'Hi Maicon,I have analised your case. To solve this issue in ERP system"", \'Comment 6: you need to replace item. Integration with ERP does not integrate substitutes. For this issue\', \'Comment 7: a GDC task needs to be raised.Please\', ""Comment 8: let us know if this solution is fine for you.Regards\'"", \'Comment 9: ""Hi AleksandraI don\\\'t see this as an issue on DHC x ERP integration\', \'Comment 10: but an issue on DHP x DHC integration.Take a look at the screenshot from DHC application\', \'Comment 11: the item in DHC is also wrong.!image-2!""\', ""Comment 12: \'!image-2022-12-14-14-35-22-300.png!!image-2022-12-14-14-35-22-300!\'"", ""Comment 13: \'Having analised for example PLR:!image-2022-12-14-14-22-47-544.png!Substitutes are defined here:!image-2022-12-14-14-23-58-221.png!What I can do is to chnage Item id under db for the PLR preview (which in fact means there will be other item on PLR element) and this will be resent to ERP.As I mentioned before"", \'Comment 14: with the view above,Integration with ERP does not integrate substitutes. For this issue\', \'Comment 15: a GDC task needs to be raised.Please\', ""Comment 16: let me know what should be done on our side.\'"", \'Comment 17: ""Hi AleksandraNow I understood. Thank you.However the origin of the issue in DHC x ERP integration is not a case of GDC but a fixing on the functionality.As you can see in the attached screenshot the documentation about DHCxERP integration and it was already covered.We didn\\\'t notice this error before because no one raised their hand to ask for help untill now.But seems that DHC are not sending this information for a long time.Could you please help us?Thank you!image-3!!image-4!""\', \'Comment 18: \\\'{code:java}2022-12-05 17:29:54,686 [142] DEBUG Evolution.DHCERPService.LocalLimsIntegration.Lims.Lims [C:\\\\\\\\Repository\\\\\\\\erpS\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.LocalLimsIntegration.Lims\\\\\\\\Lims.cs:366] - Lims DTO: {""BatchNo"":""0856051222003"",""PlantID"":""f7cf4447-16a6-4972-8757-09db240a58a6"",""ItemID"":""3471b5d7-d763-4e9f-a638-2220a235f5b7"",""ItemVersion"":0,""Quantity"":""2100.000000"",""QuantityUnits"":""kg"",""ManufacturingDate"":""2022-12-05T17:18:42"",""CustomerRequirements"":[],""XmlType"":null}2022-12-05 17:29:55,249 [16] DEBUG Evolution.DHCERPService.LocalLimsIntegration.Lims.Lims [C:\\\\\\\\Repository\\\\\\\\erpS\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.LocalLimsIntegration.Lims\\\\\\\\Lims.cs:374] - Lims result: {""Success"":true,""ErrorMessage"":"""",""XmlType"":""_WS_In_Common_DTO.serviceCallResponseDTO""}2022-12-05 17:29:55,280 [142] DEBUG Evolution.DHCERPService.LocalLimsIntegration.Commands.ProductionLotReportSavedCommand [C:\\\\\\\\Repository\\\\\\\\erpS\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.LocalLimsIntegration\\\\\\\\Commands\\\\\\\\ProductionLotReportSavedCommand.cs:58] - Import OK!2022-12-05 17:29:55,280 [142] INFO Evolution.DHCERPService.MessageSender.Actors.ClientServiceCallActor [C:\\\\\\\\Repository\\\\\\\\erpS\\\\\\\\Evolution.DHCERPService\\\\\\\\Evolution.DHCERPService.MessageSender\\\\\\\\Actors\\\\\\\\ClientServiceCallActor.cs:64] - Message with command ProductionLotReportSave and object id e4724e3c-2173-4a37-8435-9174b423fae8 was sucessfully processed.{code}ItemID powinno pokrywać się z ID planta lub dhc?!image-2022-12-15-11-53-54-910.png!!image-2022-12-15-11-54-11-865.png!\\\'\', ""Comment 19: \'Dear Maicon,Could you please provide me with correct example of substitute that integrated do ERP correctly?Regards\'"", \'Comment 20: ""Hi AleksandraI don\\\'t have such example because I was never informed about bugs on it.I\\\'m looking to the documentation from KOTRAK.Thank you""\', ""Comment 21: \'Hi Maicon,So should I understood you have never used substitute before?Regards\'"", \'Comment 22: ""Hi AleksandraIf you query the ProductionLotReportElementSubstitutes table\', \'Comment 23: you\\\'ll find a lot of cases.Thank you very much""\', ""Comment 24: \'W opisie powołał się na dwa przykłady"", \'Comment 25: zatem miałam prawo założyć\', \'Comment 26: że nie zadziałało dwa razy. Przegadałam z Przemkiem\', \'Comment 27: w Brazylii nie mają takiej integracji substitues to ERP obsłużonej\', \'Comment 28: a dokument\', \'Comment 29: którym macha Maicon opisuje możliwości nie założenia deploymentu. !image-2022-12-16-14-59-16-085.png!Tak w tabeli DHC jest wiele substitutes\', \'Comment 30: ale nie ma powiązania do dokumenty ERP\', \'Comment 31: o którego poprawny przykład pytałam wcześniej.!image-2022-12-16-15-08-41-851.png!Obejrzałam dokument mappingu i nie wiem\', ""Comment 32: co Maicon sobie ubzdurał\'"", ""Comment 33: \'Hej [~marcin.kleszcz@kotrak.com]Jak opisałam wyżej"", \'Comment 34: wyjaśnisz proszę Maiconowi\', \'Comment 35: że to\', \'Comment 36: czym macha to możliwości a nie deployment? I że to nigdy nie działało\', ""Comment 37: bo tego zwyczajnie nie mają? :)\'"", ""Comment 38: \'Hej,[~aleksandra.przybylek@kotrak.com] jeśli tak faktycznie jest"", \'Comment 39: że jest to opisane w dokumencie technicznym\', \'Comment 40: ale nie ma jeszcze takiej integracji do ERP\', \'Comment 41: to tak też napisz\', ""Comment 42: że taka integracja nie była do tej pory realizowana.\'"", \'Comment 43: ""Hi Maicon,Regarding to:{color:#0747a6}_If you query the ProductionLotReportElementSubstitutes table\', ""Comment 44: you\'ll find a lot of cases.{color:#172b4d}-{color}_ {color:#172b4d}yes but I have asked about cases / substitutes that integrated to ERP.{color}{color}{color:#0747a6}{color:#172b4d}I have consulted this case and"", \'Comment 45: as I mentioned before\', \'Comment 46: the document you are showing only describes the possibility of such integration. Integration of substitutes has not been released so far.{color}{color}{color:#0747a6}{color:#172b4d}Regards{color}{color}""\', \'Comment 47: ""HiThank you for the information. I\\\'ll raise a GDC for KOTRAK to deliver what is in the documentation created by KOTRAK itself.Thank you very much.You can close this task.""\', ""Comment 48: \'Hi,Thank you.Regards\']""]\nRelated Issues:\n[]\n\n### End'}"
976,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8055\n\n### Instruction:\nSee also : DGS-8046 and DGS-8048\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.In DGS-8048 I asked you could you anserw!image-2022-12-13-15-16-34-151.png!Regards\'"", ""Comment 2: \'Ok I can see this is the same situation as dgs-8046\'"", ""Comment 3: \'Please check both items "", \'Comment 4: should be ok\', ""Comment 5: also if there were recipes ( for 080587 were ) please asked dhh holding to send them again.,\'"", ""Comment 6: \'May we close the task?\'"", ""Comment 7: \'Link 080587-B1000 and 080583-B1000 are still present in Premix!image!!image-1!\'"", ""Comment 8: \'Please bring details what do you need. We changed base item.you want to deleted items from DHC? Or unlinked them - if we do that that means that no order "", \'Comment 9: no recipe etc would not be send to DHP.You may do it by yourself from the application.Please go to details by click ""link ite""m in dhc and then use buttons to unlink the itemUsually when you have item with code 080587.nl it has baseitem 080587 and linked other items start with 080587.!image-2022-12-15-12-11-09-627.png!\\\'\', ""Comment 10: \'According the list somebody has delete the base items 080597-B1000 and 080587-B1000 so it shlould be correct.!image-2!!image-3!\'"", ""Comment 11: \'Hi,To conclude"", ""Comment 12: can we close this task?Regards\'"", ""Comment 13: \'I am waiting off the conformation off the requester\'"", ""Comment 14: \'Ticket can be closed!image-4!\']""]\nRelated Issues:\n[\'DGS-8048\', \'DGS-8046\']\n\n### End'}"
977,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8054\n\n### Instruction:\nIn DHP Utrecht user server error 500 in DHP and sales orders do not seem to arrive. Can you check if DHP is working ok?\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Hello"", ""Comment 3: We kindly inform you that wecurrentlyare processing another Priority1 task.DGS-8051We will revert to processing your task as soon as possible.Regards\'"", ""Comment 4: \'!image-2022-12-13-15-12-56-684.png!\'"", ""Comment 5: \'Good morning,Services have been restarted in the DPH application.The message is currently not showing.Are you expecting additional action on this request ?Can we close this incident ?Regards\'"", ""Comment 6: \'[[DHP 3.0] aplikacji i rabbit kolejność uruchomienia.|onenote:https://kotrak.sharepoint.com/sites/erpasysta/Shared%20Documents/Baza%20wiedzy/Baza%20Wiedzy%20-%20ERPSD/Klienci/DEHEUS/DEHEUS%20APPLICATIONS/Holandia%20Premix%20i%20AS400/Baz%20wiedzy%20z%20AS400.one#%5bDHP%203.0%5d%20%20aplikacji%20i%20rabbit%20kolejno%C5%9B%C4%87%20uruchomienia.&section-id=\\\\\\\\{9BB564BA-0B58-4580-B9E0-F3CF9D6D80A7}&page-id=\\\\\\\\{0589CBBE-2349-4B7D-9707-381B3E7C7F9C}&end] ([Widok sieci Web|https://kotrak.sharepoint.com/sites/erpasysta/_layouts/OneNote.aspx?id=%2Fsites%2Ferpasysta%2FShared%20Documents%2FBaza%20wiedzy%2FBaza%20Wiedzy%20-%20ERPSD&wd=target%28Klienci%2FDEHEUS%2FDEHEUS%20APPLICATIONS%2FHolandia%20Premix%20i%20AS400%2FBaz%20wiedzy%20z%20AS400.one%7C9BB564BA-0B58-4580-B9E0-F3CF9D6D80A7%2F%5BDHP%203.0%5D%20%20aplikacji%20i%20rabbit%20kolejno%C5%9B%C4%87%20uruchomienia.%7C0589CBBE-2349-4B7D-9707-381B3E7C7F9C%2F%29])\'"", ""Comment 7: \'We will check if all processes are working ok again\'"", ""Comment 8: \'We see same kind of issues in Maasbracht. Do you need a separate ticket for this? Or can you check it in this ticket?\'"", ""Comment 9: \'Please create new one.Thank you.\'"", ""Comment 10: \'This ticket can be closed\']""]\nRelated Issues:\n[]\n\n### End'}"
978,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8053\n\n### Instruction:\nThe formula needs to be changed:\r\n\r\nFeed profit = Total net value of SLAC – (Total net value of Item group DOC’s) – (Total net value of all items codes in green) – Total net value of Feed \n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 2: \\\'MitchWhat items codes do you mean ""(Total net value of all items codes in green) ""?Could you please confirm this is related only to MAS NL?\\\'\', ""Comment 3: \'This is for the MAS and MAS BE.Thank you for asking.I have added the attachment"", ""Comment 4: I forgot to add it.!image![^RE_ Item codes MAS_xlsx.msg] _(236 kB)_\'"", \'Comment 5: ""[~mbovene@deheus.com]should we mark somehow Item Cards which are green on list?It\\\'s better to keep somewhere this information that we should collect data from that kind of items to some calculations.Maybe we can add checkbox on Item Card \\\'Include in Feed profit\\\' (or something like this) or add new dictionary to allow in the future adding or removing items which should be possible to include in calculations.I\\\'m not sure this values will be changed often or not\', \'Comment 6: but it will be more flexible if we will not hard code these item in procedures to calculations and allow to add/remove items when we need.What do you think?""\', \'Comment 7: ""I totally agree. I don\\\'t think it will change very often but it is good to have some flexibility.""\', \'Comment 8: ""Ok\', \'Comment 9: great\', \'Comment 10: so we\\\'ll add to Item Card checkbox\\\'Include in Feed profit\\\'.""\', \'Comment 11: ""Zostało dodane pole Itm_IntColumn9 na Item Card o nazwie\\\'Include in Feed profit\\\' i dla wskazanych itemów zostało ono uzupełnione.Na potrzeby wyliczania danych z ww. Itemów zostały dodane funkcje:[dbo].[KR_TechResults_TotalIncludeFeedProfitItems][dbo].[KR_TechResults_TotalIncludeFeedProfitItems_MASBE]Zostały zmodyfikowane procedury:[dbo].[KR_calculatetechresults][dbo].[KR_calculatetechresults_MASBE]Procedury korzystają ze wspomnianych wcześniej funkcji.""\', \'Comment 12: ""On Item Card has been added field\\\'Include in Feed profit\\\' and was marked for Items indicated on green on the list for sectors MAS NL and MAS BE (35 items in each sector). This field is visible only for user = Administrator.Changes with new formula have been implemented on production database IBIP_DH.Please verify on one or more documents that calculations for Feed profit is correct in sectors MAS NL and MAS BE.""\', ""Comment 13: \'Damian"", ""Comment 14: to be verified!image-2022-12-19-14-06-18-633.png|width=1590,height=364!!image-2022-12-19-14-07-02-258.png!\'"", ""Comment 15: \'Maybe a plus and a minus are mixed up by accident. On the other hand I think the total value from the formula is divided by the number of broilers. While in the formula as provided by me (based on input from Oscar) this isn’t. The provided formula was:Feed profit = Total net value of SLAC – (Total net value of Item group DOC’s) – (Total net value of all items codes in green) – Total net value of FeedOur interpretation of the numbers (maybe that is were it went wrong): Feed profit (can be positive or negative base on the outcome) = Total net value of SLAC (positive value) – Total net value of Item group DOC’s (positive value) – Total net value of all items codes in green (positive value) – Total net value of Feed (positive value).The logic of this formula is that a farmer needs to know what his profit it when his costs (docs"", \'Comment 16: feed\', ""Comment 17: most of the expenses) are subtracted from his revenues (SLAC).Regards,Mitch\'"", ""Comment 18: \'In addition"", ""Comment 19: they would like to see this profit per broiler.\'"", \'Comment 20: \\\'The outcome of the formula should be diveded by ""Number of first loaders (quantity)+Number of alle loaders (quantity)"".\\\'\', \'Comment 21: ""Ok\', \'Comment 22: so it means that we should take always absolute value of: * Total net value of SLAC * Total net value of Item group DOC’s * Total net value of all items codes in green * Total net value of FeedIs it correct that in formula expression (Total net value of all items codes in green) contains item = \\\'SLAC\\\' (on list item \\\'SLAC\\\' is marked on green)?It means that we at firs sum all \\\'SLAC\\\' in*Total net value of SLAC*and then in *(Total net value of all items codes in green)* substract sum of \\\'SLAC\\\' and other items marked on green.Feed profit = *Total net value of SLAC* – (Total net value of Item group DOC’s) – *(Total net value of all items codes in green)* – Total net value of FeedFor case of document ID = 78127 there is: * Total net value of SLAC =276893,20 * Total net value of Item group DOC’s =26122,50 * Total net value of all items codes in green =275054,26 * Total net value of Feed =156502,62 * Number of first loaders (quantity) = 0 * Number of alle loaders (quantity) = 63773so result of Feed profit formula will be after rounding for conditions above =-2.83""\', ""Comment 23: \'* We should indeed take absolute values of the four SUMS you mention. Note"", \'Comment 24: it could be that some of the parts are with a minus when you look at the green item codes.* No\', \'Comment 25: that is a mistake. The SLAC should not be included in the green item codes.* Almost all your SUMS are correct\', ""Comment 26: however the Total net value of the items in green will be 1838,94 (you need to exclude SLAC)\'"", \'Comment 27: ""Calculation have been modified and \\\'SLAC\\\' is now excluded from the \\\'Total net value of all items codes in green\\\'Now value of Feedprofit = 1,45Please verify that is correct righ now.""\', ""Comment 28: \'Yes indeed\'"", ""Comment 29: \'Ok"", ""Comment 30: so I close the task.\']""]\nRelated Issues:\n[\'DGS-8215\', \'DGS-8428\']\n\n### End'}"
979,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8052\n\n### Instruction:\nProduct created by mistake as bulk. And so it was produced and confirmed. Subsequently, a colleague noticed the mistake, corrected it instead of buulk in bagged.\r\n\r\nNow we have the produced quantity on stock, which instead of a 20 kg bag is on stock as bulk.\r\n\r\nHow can we fix it, can you put the entire amount of product 30440140-B20 to be bagged?\n\n### Response:\n[""Comment 1: [\'!Screenshot_1!!Screenshot_3!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 3: ""Performing changes by inventory.For bullk stock units change to zero.For bagged stocks adding what\\\'s taken out of the bulk stock units?""\', ""Comment 4: \'Hello"", ""Comment 5: can we get feedback for our last comment?\'"", ""Comment 6: \'Hello,We are closing this task as we haven’treceivedany replyfromyouforalong time.Regards\']""]\nRelated Issues:\n[]\n\n### End'}"
980,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8051\n\n### Instruction:\nLot report do not come into DHP\r\nPossible error included\r\n\r\nSee also : DGS-8050\r\n\r\n\n\n### Response:\n[""Comment 1: [\'[^Batchperformance_202212090068_BL01_1_d1c2b00d-cc79-4203-b99a-6c57a101a152_35168067.xml] _(13 kB)_[^Batchperformance_202212090068_BL01_2_d1c2b00d-cc79-4203-b99a-6c57a101a152_35170346.xml] _(13 kB)_[^Batchperformance_202212090068_BL01_3_d1c2b00d-cc79-4203-b99a-6c57a101a152_35252533.xml] _(13 kB)_[^Batchperformance_202212090068_BL01_4_d1c2b00d-cc79-4203-b99a-6c57a101a152_35256933.xml] _(13 kB)_[^Batchperformance_202212090068_BL01_5_d1c2b00d-cc79-4203-b99a-6c57a101a152_35264995.xml] _(13 kB)_[^Batchperformance_202212090068_BL01_6_d1c2b00d-cc79-4203-b99a-6c57a101a152_35268376.xml] _(13 kB)_[^Batchperformance_202212090068_BL01_7_d1c2b00d-cc79-4203-b99a-6c57a101a152_35272898.xml] _(13 kB)_[^Batchperformance_202212090068_SL06_1_10_4b3785c2-9349-4c80-92e0-8757133e5ade_34250438.xml] _(2 kB)_[^Batchperformance_202212090068_SL06_1_11_4b3785c2-9349-4c80-92e0-8757133e5ade_34251532.xml] _(2 kB)_[^Batchperformance_202212090068_SL06_1_2_4b3785c2-9349-4c80-92e0-8757133e5ade_34221064.xml] _(2 kB)_[^Batchperformance_202212090068_SL06_1_3_4b3785c2-9349-4c80-92e0-8757133e5ade_34223244.xml] _(2 kB)_[^Batchperformance_202212090068_SL06_1_4_4b3785c2-9349-4c80-92e0-8757133e5ade_34227212.xml] _(2 kB)_[^Batchperformance_202212090068_SL06_1_5_4b3785c2-9349-4c80-92e0-8757133e5ade_34230483.xml] _(2 kB)_[^Batchperformance_202212090068_SL06_1_6_4b3785c2-9349-4c80-92e0-8757133e5ade_34232298.xml] _(2 kB)_[^Batchperformance_202212090068_SL06_1_7_4b3785c2-9349-4c80-92e0-8757133e5ade_34237321.xml] _(2 kB)_[^Batchperformance_202212090068_SL06_1_8_4b3785c2-9349-4c80-92e0-8757133e5ade_34237471.xml] _(2 kB)_[^Batchperformance_202212090068_SL06_1_9_4b3785c2-9349-4c80-92e0-8757133e5ade_34243429.xml] _(2 kB)_!image!\'"", ""Comment 2: \'Hi,Could you please provide us with Production Lot Report Number?Where does this message come from? Which database? !image-2022-12-13-12-12-23-640.png!Regards !image-2022-12-13-12-12-23-640!\'"", ""Comment 3: \'These lot reports are coming from PCS  (KSE)\'"", ""Comment 4: \'Okay"", ""Comment 5: but what are Production Lot Reports numbers?\'"", ""Comment 6: \'In the XML files are the numbers of the lot reports present.!image-1!\'"", ""Comment 7: \'This number is a part off the lot report name in DHP\'"", ""Comment 8: \'We are investigating\'"", ""Comment 9: \'!image-2022-12-13-14-53-19-686.png!\'"", ""Comment 10: \'{code:java}System.Net.WebException: The remote server returned an error: (400) Bad Request.     at System.Net.HttpWebRequest.GetResponse()     at PCS.Repository.Netherlands.Repositories.BaseSaveRepository`6.Save(Package`1 package"", ""Comment 11: ActionCode action) in E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\152764417\\\\\\\\DHAPPS25-PCSEV139-JOB1\\\\\\\\PCS.Repository.Netherlands\\\\\\\\Repositories\\\\\\\\BaseSaveRepository.cs:line 70{code}\'"", \'Comment 12: "" !screenshot-4! {code:java}  FROM [DH_Exchange_NL_PROD].[dbo].[ProductionLotReportHeader]  where PLH_Id in(\\\'87014110122222217\\\',\\\'87014110122222183\\\')  select *   FROM [DHP_NL_PROD].[dbo].[ProductionLotReportHeader]  where PlH_LotNumber in(\\\'87014110122222217\\\',\\\'87014110122222183\\\'){code} !screenshot-5! nie ma w dhp. exchange jest.""\', ""Comment 13: \'PLRy z 10.12 \\\\r87014110122222183\\\\r87014110122222217\\\\rsą w exchange"", \'Comment 14: nie ma dhp\', ""Comment 15: prośba o pomoc w ustaleniu przyczyny. \\\\rW logach są błędy ale nie jestem stanie ustalić czy pod te.\\\\rDzięki.\'"", ""Comment 16: \'I have one question,can it wait until tomorrow morning?We need analysis results from our developers.\'"", ""Comment 17: \'brak receptury w plancie: !screenshot-6! usunięta z bazy dhp: !screenshot-7! \'"", \'Comment 18: ""Please resend lot reports to DHP and check.Please send a feedback.Recipe for item was missing in DHP and it\\\'s seems to have been removed from the database.""\', ""Comment 19: \'Total weight off lot report is visible but used raw material is not present. Zero KG.Track and tracing is not posible without consumption off raw material,!image-2!\'"", ""Comment 20: \'Please correct the used consumption off raw material.\'"", ""Comment 21: \'We are working on it\'"", \'Comment 22: ""Only on PLR \\\'87014110122222183\\\' or on PLR\\\'87014110122222217\\\' as well?""\', \'Comment 23: ""Please\', \'Comment 24: verify\\\'87014110122222183\\\' and let me know""\', ""Comment 25: \'The real quantity is stil zero\'"", ""Comment 26: \'We are checking\'"", ""Comment 27: \'Real quantity is fild in but the dosed quantity is now twice as mutch.!image-3!\'"", \'Comment 28: ""Please\', \'Comment 29: check\\\'87014110122222183\\\' now""\', \'Comment 30: ""Please\', \'Comment 31: check\\\'87014110122222217\\\'""\', ""Comment 32: \'{code:java} select * FROM [DHP_NL_PROD].[dbo].[PcsDosing] where DSN_PlEId in(SELECT        PlE_Id                               FROM            ProductionLotReportElement                               WHERE        (PlE_PlHId = 254279  ))\\\\t\\\\tselect *\\\\t\\\\t FROM [DHP_NL_PROD].[dbo].[ProductionLotReportRelease]  where PlR_PlEId in(SELECT PlE_Id  FROM [DHP_NL_PROD].[dbo].[ProductionLotReportElement]  where PlE_PlHId=254278) SELECT PlE_Id,* --delete  FROM [DHP_NL_PROD].[dbo].[ProductionLotReportElement] where PlE_PlHId=254279  and PlE_RcEId is  null\\\\t\\\\t{code}\'"", ""Comment 33: \' !screenshot-8! \'"", ""Comment 34: \'Lot report in DHC and not going to CDN.!image-4!\'"", \'Comment 35: ""PLR or VT? If VT\', ""Comment 36: which of them:\'87014110122222183\' ,\'87014110122222217\' ?If none of them"", \'Comment 37: please\', \'Comment 38: arise another task.Regards""\', \'Comment 39: ""I have checked\', ""Comment 40: and For PLR:87014110122222183\'"", \'Comment 41: item 970125-B25!image-2022-12-19-10-50-21-745.png!There are documents in CDN:!image-2022-12-19-10-50-47-007.png!!image-2022-12-19-10-51-55-160.png!!image-2022-12-19-10-52-16-744.png!Please\', \'Comment 42: let me know what is the exact case.Regards !image-2022-12-19-10-51-55-160! !image-2022-12-19-10-52-16-744!""\', ""Comment 43: \'It is about  87014110122222183.87014110122222217 is an wrong one and kan be deleted.\'"", ""Comment 44: \'Ok"", \'Comment 45: but documents: JO\', \'Comment 46: IR+ and IR - related to PLR:87014110122222183 are generated in ERP XL as you can see on above screenshots.Please\', ""Comment 47: let us know what is missing?Regards\'"", \'Comment 48: ""The problem is VT is not accepted.See ticket : DGS-8099 VT \\\'s are not going from DHC to CDN Please solve ticket DGS-8099 and close thics ticket ""\', ""Comment 49: \'Ticket DGS-8099 is under investigation.Regards\'"", ""Comment 50: \'[[DHP/Exchange] Bad Request 400 dla PLR - są w exchange nie wpadają do DHP|onenote:https://kotrak.sharepoint.com/sites/erpasysta/Shared%20Documents/Baza%20wiedzy/Baza%20Wiedzy%20-%20ERPSD/Klienci/DEHEUS/DEHEUS%20APPLICATIONS/Holandia%20Premix%20i%20AS400/Baza%20wiedzy.one#%5bDHP/Exchange%5d%20Bad%20Request%20400%20dla%20PLR%20-%20s%C4%85&section-id=\\\\\\\\{B6BA0A4E-07B0-413E-A582-89B093FD9A36}&page-id=\\\\\\\\{7504D29D-9B42-4A26-81C2-0BE1CF27FE2C}&end] ([Widok sieci Web|https://kotrak.sharepoint.com/sites/erpasysta/_layouts/OneNote.aspx?id=%2Fsites%2Ferpasysta%2FShared%20Documents%2FBaza%20wiedzy%2FBaza%20Wiedzy%20-%20ERPSD&wd=target%28Klienci%2FDEHEUS%2FDEHEUS%20APPLICATIONS%2FHolandia%20Premix%20i%20AS400%2FBaza%20wiedzy.one%7CB6BA0A4E-07B0-413E-A582-89B093FD9A36%2F%5BDHP%5C%2FExchange%5D%20Bad%20Request%20400%20dla%20PLR%20-%20s%C4%85%7C7504D29D-9B42-4A26-81C2-0BE1CF27FE2C%2F%29])\']""]\nRelated Issues:\n[]\n\n### End'}"
981,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8050\n\n### Instruction:\nLot report do not come into DHP \r\nPossible error included\r\n\r\n\r\n\n\n### Response:\n[""Comment 1: [\'[^Batchperformance_202212090068_BL01_1_d1c2b00d-cc79-4203-b99a-6c57a101a152_35168067.xml] _(13 kB)_[^Batchperformance_202212090068_BL01_2_d1c2b00d-cc79-4203-b99a-6c57a101a152_35170346.xml] _(13 kB)_[^Batchperformance_202212090068_BL01_3_d1c2b00d-cc79-4203-b99a-6c57a101a152_35252533.xml] _(13 kB)_[^Batchperformance_202212090068_BL01_4_d1c2b00d-cc79-4203-b99a-6c57a101a152_35256933.xml] _(13 kB)_[^Batchperformance_202212090068_BL01_5_d1c2b00d-cc79-4203-b99a-6c57a101a152_35264995.xml] _(13 kB)_[^Batchperformance_202212090068_BL01_6_d1c2b00d-cc79-4203-b99a-6c57a101a152_35268376.xml] _(13 kB)_[^Batchperformance_202212090068_BL01_7_d1c2b00d-cc79-4203-b99a-6c57a101a152_35272898.xml] _(13 kB)_[^Batchperformance_202212090068_SL06_1_10_4b3785c2-9349-4c80-92e0-8757133e5ade_34250438.xml] _(2 kB)_[^Batchperformance_202212090068_SL06_1_11_4b3785c2-9349-4c80-92e0-8757133e5ade_34251532.xml] _(2 kB)_[^Batchperformance_202212090068_SL06_1_2_4b3785c2-9349-4c80-92e0-8757133e5ade_34221064.xml] _(2 kB)_[^Batchperformance_202212090068_SL06_1_3_4b3785c2-9349-4c80-92e0-8757133e5ade_34223244.xml] _(2 kB)_[^Batchperformance_202212090068_SL06_1_4_4b3785c2-9349-4c80-92e0-8757133e5ade_34227212.xml] _(2 kB)_[^Batchperformance_202212090068_SL06_1_5_4b3785c2-9349-4c80-92e0-8757133e5ade_34230483.xml] _(2 kB)_[^Batchperformance_202212090068_SL06_1_6_4b3785c2-9349-4c80-92e0-8757133e5ade_34232298.xml] _(2 kB)_[^Batchperformance_202212090068_SL06_1_7_4b3785c2-9349-4c80-92e0-8757133e5ade_34237321.xml] _(2 kB)_[^Batchperformance_202212090068_SL06_1_8_4b3785c2-9349-4c80-92e0-8757133e5ade_34237471.xml] _(2 kB)_[^Batchperformance_202212090068_SL06_1_9_4b3785c2-9349-4c80-92e0-8757133e5ade_34243429.xml] _(2 kB)_!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Hi,If this issue has the highiest priority"", ""Comment 4: you should raise an incident with priority P1 or P2.Could you please provide us with Production Lot Report Number?Where does this message come from? Which database?!image-2022-12-13-12-02-57-399.png!Regards\'"", ""Comment 5: \'I am closing this task as it is processing underDGS-8051.Regards\']""]\nRelated Issues:\n[]\n\n### End'}"
982,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8049\n\n### Instruction:\nDHC does not work. \r\nRestart of Business platform does not work: \r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 3: ""2022-12-13 10:05:37,299 [5] FATAL Evolution.BusinessPlatform.BusinessPlatform [(null)] - Some errors occured during platform startupSystem.Data.SqlClient.SqlException (0x80131904): Login failed for user \\\'dhbp\\\'. Reason: The password of the account has expired. at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject\', \'Comment 4: UInt32 waitForMultipleObjectsTimeout\', \'Comment 5: Boolean allowCreate\', \'Comment 6: Boolean onlyOneCheckConnection\', \'Comment 7: DbConnectionOptions userOptions\', \'Comment 8: DbConnectionInternal& connection) at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject\', \'Comment 9: TaskCompletionSource`1 retry\', \'Comment 10: DbConnectionOptions userOptions\', \'Comment 11: DbConnectionInternal& connection) at System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection\', \'Comment 12: TaskCompletionSource`1 retry\', \'Comment 13: DbConnectionOptions userOptions\', \'Comment 14: DbConnectionInternal oldConnection\', \'Comment 15: DbConnectionInternal& connection) at System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection\', \'Comment 16: DbConnectionFactory connectionFactory\', \'Comment 17: TaskCompletionSource`1 retry\', \'Comment 18: DbConnectionOptions userOptions) at System.Data.ProviderBase.DbConnectionClosed.TryOpenConnection(DbConnection outerConnection\', \'Comment 19: DbConnectionFactory connectionFactory\', \'Comment 20: TaskCompletionSource`1 retry\', \'Comment 21: DbConnectionOptions userOptions) at System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource`1 retry) at System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry) at System.Data.SqlClient.SqlConnection.Open()""\', ""Comment 22: \'!image-2022-12-13-11-39-03-985.png!\'"", ""Comment 23: \'[~marta.litkie@kotrak.com]sprawdź z nimi"", \'Comment 24: czy dane do bazy nie pozmieniali\', \'Comment 25: albo użytkowników\', ""Comment 26: niech przyróca najlepiej stare haslo dla dhbp\'"", \'Comment 27: ""Hello we check that there are erorrs like :2022-12-13 10:05:37,299[5]FATAL Evolution.BusinessPlatform.BusinessPlatform[(null)]- Some errors occured during platform startupSystem.Data.SqlClient.SqlException (0x80131904): Login failed for user \\\'dhbp\\\'. Reason: The password of the account has expired.at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject\', \'Comment 28: UInt32 waitForMultipleObjectsTimeout\', \'Comment 29: Boolean allowCreate\', \'Comment 30: Boolean onlyOneCheckConnection\', \'Comment 31: DbConnectionOptions userOptions\', \'Comment 32: DbConnectionInternal& connection)could you bring bag the old password for database for userdhbp?""\', ""Comment 33: \'Hello"", \'Comment 34: what was the old password? Write please a login  |{color:#0070C0} З найкращими побажаннями,{color}{color:#0070C0} Петро Світлик{color}{color:#0070C0} IT відділ{color}{color:#0070C0}{color}{color:#0070C0} {color}{color:#0070C0} Best regards,{color}{color:#0070C0} Petro Svitlyk{color}{color:#0070C0}{color}{color:#0070C0} IT department{color}{color:#0070C0} {color}{color:#0070C0}{color} [{color:#0070C0}{color}{color:#0563C1}servicedesk@koudijs.ua{color}{color:#0070C0}{color}|mailto:servicedesk@koudijs.ua]{color:#0070C0}{color}  {color:blue} +{color}[{color:blue}{color}{color:#0563C1} + Teams+{color}{color:blue} {color}|https://teams.microsoft.com/l/chat/0/0?users=servicedesk@koudijs.ua]{color:blue} {color}+ : [{color:#0563C1}Viber{color}|viber://chat/?number=+380952855727] :{color:#0070C0}{color} [{color:#0070C0}{color}{color:#0070C0}WhatsApp{color}{color:#0070C0}{color}|https://wa.me/380952855727]{color:#0070C0}{color} :  {color:#0070C0} +{color}[{color:#0070C0}{color}{color:#0563C1} + Telegram+{color}{color:#0070C0} {color}|https://t.me/psvitlyk]{color:#0070C0} {color}+  *{color:#006FB7} **{color}* | |{color:black}{color} !image003!{color:black}{color} |  *{color:#006FB7} **{color}*  *{color:#006FB7} *Коудайс Україна*{color}*{color:#006FB7} c{color}{color:#006FB7}.{color}{color:#006FB7}Хильчиці\', \'Comment 35: Золочівський р-н\', \'Comment 36: Львівська область{color}  *{color:#006FB7} **{color}*  *{color:#006FB7} *KoudijsUkraine*{color}*{color:#006FB7}{color}{color:#006FB7} Khylchytsi village\', \'Comment 37: Zolochiv district\', \'Comment 38: Lviv region{color}{color:#006FB7}{color} [{color:#006FB7}{color}{color:#0563C1}www.koudijs.ua{color}{color:#006FB7}{color}|http://www.koudijs.ua/]{color:#006FB7}{color}{color:black}{color}{color:#006FB7}{color} | |{color:black}{color} !image002!{color:black}{color} |       *From:* Agnieszka Januszewska (Jira) <jira@kotrak.com>   *Sent:* Tuesday\', \'Comment 39: December 13\', ""Comment 40: 2022 12:45 PM  *To:* Servicedesk <servicedesk@koudijs.ua>  *Subject:* DGS-8049 DHC does not work   \'"", ""Comment 41: \'For DHc db we had this password and login|dhbp|ZAQ!2wsx|login is dhbp\'"", ""Comment 42: \'IP: {color:#242424}10.106.25.32{color}{color:#242424} 10.106.25.33{color} ?\'"", ""Comment 43: \'!image-2022-12-13-13-02-06-869.png!\'"", ""Comment 44: \'Przy probie logowanai do bazy danych powpowiedziało mi zmiane hasla !image-2022-12-13-14-11-20-436.png!\'"", ""Comment 45: \'Did you set password again: I am not able to change it during login!image-2022-12-13-14-11-20-436.png!\'"", ""Comment 46: \'Please check again"", ""Comment 47: we have updated the password to the same one!image001!\'"", ""Comment 48: \'Please check services have been started.\'"", ""Comment 49: \'Yes"", \'Comment 50: running\', ""Comment 51: thanks\']""]\nRelated Issues:\n[]\n\n### End'}"
983,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8048\n\n### Instruction:\nRemove linked item 080587-B1000 in Premix\r\n\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'\'"", ""Comment 4: \'If I understand correctly"", ""Comment 5: you want baseitem to be 080587 instead of 080587-b1000?Do you give the shuffle a higher priority p2? p1?!image-2022-12-13-11-52-01-301.png!\'"", \'Comment 6: ""select *from dhhitems where code like \\\'080587\\\'select * from items where code like \\\'080587\\\'--update DhhItems--set BaseItemId=--\\\'BDCFBF6C-1B0C-423D-8351-AEE2B33608A6\\\'--where code like \\\'080587\\\'""\', ""Comment 7: \'Linked DHC items 080587-B1000 and 080583-B1000 must be deleted.This can not be done using a screen.!image-1!!image-2!\'"", ""Comment 8: \'We are processing this task indgs-8055"", ""Comment 9: so this task will be closed.\']""]\nRelated Issues:\n[\'DGS-8055\']\n\n### End'}"
984,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8047\n\n### Instruction:\nWe need to add a relation to the table on the NAS. \r\n\r\nWe already created an invoice SI-RTN/2022/0503. Can this be linked to the round whenever this relation is added?\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Mitch"", \'Comment 4: after the changes this will be visible in the Round etc. but still need to gain some more details before we start with the system update.I see the yellow relation\', \'Comment 5: did you add it to our Excel ""Relation tables""? I cannot find it.Second question: in the yellow relation\', \'Comment 6: you wrote that Item Group = Slaughtery\', ""Comment 7: while I see AFLE is Expenses. What should be the item code for the items handled in the new relation?Sales invoiceInvoice type: RegisteredCustomer: FarmerReference: NULLItem Group: ExpensesRound Category: Slaughtery\'"", ""Comment 8: \'I have added it our relationshop table on BOX again and saved it.I have changed the item group of AFLE to SlaughteryExpenses. It is mostly about AFLE. \'"", \'Comment 9: ""Dodana obsługa relacji w sektorze NAS - dodane na Rundzie\', \'Comment 10: na FS\', \'Comment 11: na zapytaniach do wydruku FS. Na S2P bez zmian\', \'Comment 12: bo to faktura \\\'Registered\\\'.""\', ""Comment 13: \'New relation in NAS has been added and adjusted on documents Round"", ""Comment 14: Financial Statement.\\\\r\\\\rNow that type of Sales Inovices will be visible on Round and Financial Statement.\'"", ""Comment 15: \'Great! Thank you"", ""Comment 16: Damian!\']""]\nRelated Issues:\n[]\n\n### End'}"
985,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8046\n\n### Instruction:\n Item 080583 is linked in DHC to BB item. Please relmove link.\r\n\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Hi,Linking has been removed. You can link items correctly now.Please"", ""Comment 4: let us know if we can close this task.Regards\'"", ""Comment 5: \'This change was done in dgs-8055\']""]\nRelated Issues:\n[\'DGS-8055\']\n\n### End'}"
986,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8045\n\n### Instruction:\nFor plant Andel multiple XML files are generated for SPS. A fix was done to prevent this (and installed for all plants). However, for Andel we still get these duplicates\r\nIssue does not seem to be related to multiple order lines:\r\n\r\nDe SO-37131 1 orderline\r\nDe SO-37028 2 orderlines\r\nDe SO-36457 1 orderline\r\n\r\nPlease / adjust check config\r\n\r\nSee examples of XML files below (from 12/12/2022)\n\n### Response:\n[""Comment 1: [\'!image!!image-1!!image-2!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Please be informed that we have forwarded the issue to the development team in order to internal analysis.We are waiting for more details and will be back with further information as soon as possible.\'"", \'Comment 4: \\\'[~aleksandra.przybylek@kotrak.com]- zmieniłem konfiguracje na AS400PluginConfiguration""GenerateOnVehicleTicketDispatchClosedEvent"": false\', \'Comment 5: wygląda mi to że tutaj leżał problem.Niech sprawdzą czy mają jeszcze takie przypadki jeszcze\', ""Comment 6: jakieś nowe od momentu zmiany.\'"", ""Comment 7: \'[~gedeon.kucharski@kotrak.com]Dzięki :)\'"", ""Comment 8: \'Hi,About 12:30 configuration has been changed. Please"", ""Comment 9: verify and let us know if new cases occured after 12:30.Regards\'"", ""Comment 10: \'Issue not found anymore. This ticket can be closed.\'"", ""Comment 11: \'Thank you.\']""]\nRelated Issues:\n[]\n\n### End'}"
987,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8044\n\n### Instruction:\nRonnie Thuis does have more options on the contract list witch I do not see on my screen. Do I have to reset layout?\r\n\r\n\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!!image-1!!image-2!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Please uncheck minimize the ribbon in the context menu. !screenshot-1! \'"", ""Comment 4: \'Minimize the system was not selected. Selecting and deselecting the minimize did not make any difference.The only thing wich was working was : Reset layout.Afther this the fields had to be added munualy .\'"", ""Comment 5: \'Ticket can be closed\']""]\nRelated Issues:\n[]\n\n### End'}"
988,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8043\n\n### Instruction:\nFor item 302010, recipe version 86 and 87 are sent for location 15 GFM. \r\nAccording to recipe overview, item is not linked. In Bestmix I see that item is linked. \r\n\r\nCan you check/fix linking of this item?\r\n\n\n### Response:\n[""Comment 1: [\'!image!!image-1!!image-2!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Please link this item - 9111 !screenshot-1! \'"", ""Comment 4: \'{color:#000000}Thanks"", \'Comment 5: I was not aware of the missing RM. This ticket can be closed.{color}   {color:#000000}{color}     {color:#000000}       {color}{color:black}{color} {color:#000000} {color}{color:black}Best regards | Met vriendelijke groeten,{color}{color:#000000}{color}{color:black}  Bob Kennedy{color} {color:#000000}{color}{color:black}Informatie analist{color}{color:#000000} {color}{color:black}{color}{color:#000000} {color}{color:#000000} {color} |{color:#000000}{color} {color:#000000}{color}De Heus Voeders{color:#000000} <[http://www.de-heus.nl/]>{color}{color:black}{color}{color:#000000} {color}{color:#000000} {color}|{color:#000000}{color}{color:#006FB7} * De Heus Voeders B.V.*{color}{color:#000000}{color}{color:#006FB7}{color} {color:#000000}{color}{color:#006FB7} Postbus 396 6710 BJ Ede{color}{color:#000000}{color}{color:#006FB7} Rubensstraat 1756717 VE Ede  *M* 06 - 53 224 931 KvK 14626985{color}{color:#000000}{color}{color:black} {color}{color:#000000}{color}{color:#006FB7} _ Op dit e-mailbericht en eventuele bijlage(n) is de disclaimer van toepassing_{color}{color:#000000}{color}{color:#006FB7}{color} {color:#000000}{color}{color:#006FB7} _ gepubliceerd op de website van_{color} [{color:#006FB7} _De Heus Voeders_{color}|http://www.de-heus.nl/maildisclaimer]{color:#006FB7} _._{color}{color:#000000}{color}{color:#006FB7}{color} {color:#000000} {color}{color:#000000} {color}| |{color:#000000}{color}{color:black}{color} image007.jpg@01D62AA3.AD14DDB0{color:black}{color}{color:#000000} {color}{color:#000000} {color}| |{color:#000000}{color}{color:black}{color} image004.jpg@01D62AA3.AD2CAB70{color:black}{color}{color:#000000} {color}{color:#000000} {color}| {color:#000000}{color} ---- {color:#000000} *From:* Piotr Gaczorek (Jira) <jira@kotrak.com>  *Sent:* Monday\', \'Comment 6: December 12\', \'Comment 7: 2022 4:21 PM  *To:* Kennedy\', ""Comment 8: Bob <BKennedy@deheus.com>  *Subject:* DGS-8043 Recipe for item 302010 not accepted because it not linked. Item is linked{color}  |{color:#ffffff} CAUTION: This message originated from outside the organisation. Please do not click on links or open attachments unless you trust the sender and know the content is safe.{color} |\']""]\nRelated Issues:\n[]\n\n### End'}"
989,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8042\n\n### Instruction:\nHow to select a total overvieuw of Service Request - NL (Compound Feed)\r\nNot possible to select \r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Sudenly service request is added!image-1!\'"", ""Comment 4: \'Only my own ticket are visible.!image-2!\'"", ""Comment 5: \'Hello Bert,We added you to the request participants section and now you are able to select all open tickets. Starting today you will be added automatically to all new tickets from NL.Regards\']""]\nRelated Issues:\n[]\n\n### End'}"
990,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8041\n\n### Instruction:\nHi,\r\nWe can not receive Recipes from DHH to DHC.\r\nPlease kindly help check: Cần Thơ Factory(ID:437) with Versions:\r\n91C5006-04 V8\r\n91C5006-05 V10\r\n91C5007A-05 V11\r\n90C8004-2C V1\r\n90C8005-2C V4\r\n Note: Put P1 because need for production\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'{code:java}2022-12-12 17:18:27,974 [52] DEBUG Evolution.DHCountry.Logging.EventPublisherWithLog4NetTracing [(null)] - Published event [Evolution.DHCountry.Dictionaries.Recipes.Events.RecipeSaveEvent RecipeId: 228555d8-6206-4399-8e70-c2f6f229fc26"", \'Comment 3: HasError: True\', \'Comment 4: Reason:System.InvalidOperationException: The operation failed: The relationship could not be changed because one or more of the foreign-key properties is non-nullable. When a change is made to a relationship\', \'Comment 5: the related foreign-key property is set to a null value. If the foreign-key does not support null values\', \'Comment 6: a new relationship must be defined\', \'Comment 7: the foreign-key property must be assigned another non-null value\', \'Comment 8: or the unrelated object must be deleted.   at System.Data.Entity.Core.Objects.ObjectContext.PrepareToSaveChanges(SaveOptions options)   at System.Data.Entity.Core.Objects.ObjectContext.SaveChangesInternal(SaveOptions options\', ""Comment 9: Boolean executeInExistingTransaction)   at System.Data.Entity.Core.Objects.ObjectContext.SaveChanges(SaveOptions options)   at System.Data.Entity.Internal.InternalContext.SaveChanges()   at System.Data.Entity.Internal.LazyInternalContext.SaveChanges()   at System.Data.Entity.DbContext.SaveChanges()   at Evolution.DHCountry.Infrastructure.Recipes.RecipeChangedHandler.OnHandle(RecipeChangedMessage recipeMessage) in E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\152764417\\\\\\\\DHAPPSV3-DHC-JOB1\\\\\\\\Evolution.DHCountry\\\\\\\\Evolution.DHCountry.Infrastructure\\\\\\\\Recipes\\\\\\\\RecipeChangedHandler.cs:line 80] to publisher [Evolution.Events.EventPublisher] under domain context [6ea48361ad5648e99f5397492bf619ba]{code}\'"", \'Comment 10: ""Hello Hardy,We don\\\'t have access below servers IP 113.161.145.252:3370IP 10.84.1.22!image-2022-12-12-11-27-50-715.png!Regards""\', ""Comment 11: \'which user you want to login?\'"", ""Comment 12: \'Apac\\\\\\\\Piotr.Gaczorek Apac\\\\\\\\aprzybyłekApac\\\\\\\\akozak kotrak11@apac.corp.deheus.com kotrak12@apac.corp.deheus.com kotrak13@apac.corp.deheus.com kotrak14@apac.corp.deheus.com\'"", ""Comment 13: \'Please try\'"", ""Comment 14: \'Sorry"", ""Comment 15: this account no accessPlease refresh this acount Apac\\\\\\\\Piotr.GaczorekApac\\\\\\\\aprzybyłekIP 113.161.145.252:3370IP 10.84.1.22!image-2022-12-12-11-42-58-460.png!\'"", ""Comment 16: \'!image!\'"", ""Comment 17: \'Please try\'"", ""Comment 18: \'I need connect to server 113.161.145.252:3370!image-2022-12-12-11-59-55-214.png!IP 10.84.1.22 OK\'"", ""Comment 19: \'from Puclic remote you can try with IP: 10.84.1.16\'"", ""Comment 20: \'!image-1!\'"", ""Comment 21: \'Thank you for your accesses I sent again from DHH recipesCurrently"", ""Comment 22: the recipes appear in the DHC applicationRegards\'"", ""Comment 23: \'what is root cause? issue from DHH? \'"", ""Comment 24: \'and you can lower it to P2. i will check and feedback later on\'"", ""Comment 25: \'data have been arrived to DHC\'"", ""Comment 26: \'Hello,In this task we have focused on clearingandunblocking the process.If there is a need from your sideto investigate the reasonof the issue"", \'Comment 27: we may raise RootCause Analysis (RCA)task for you.Please\', ""Comment 28: let us knowhow you wish us to proceed.Regards.\'"", ""Comment 29: \'so"", ""Comment 30: what is clearing and unblocking? clear from DHH or DHC?\'"", ""Comment 31: \'Resend from DHH holding Recipe to DHC No errors in synchronization.Create RootCause Analysis ?Will we do a more extensive request analysis next time we report ?Close this Incident ?Regards\'"", ""Comment 32: \'thank"", ""Comment 33: you can close the ticket\']""]\nRelated Issues:\n[]\n\n### End'}"
991,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8040\n\n### Instruction:\nInvoices PI-RLB/2022/1050 (ID 75798) and SI-RLB/2022/1135 (ID 75799) were sent with wrong prices. Could you please put them back to entry? They aren\'t posted in Milas yet.\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Same counts for SI-RLB/1136 (ID 75801)\'"", \'Comment 3: ""There are in Entry (in Koen\\\'s Inbox)PI-RLB/2022/1050,SI-RLB/2022/1135,SI-RLB/2022/1136""\', ""Comment 4: \'Send to Entry\'"", \'Comment 5: ""The round wasn\\\'t modified on the original PI (PI-RLB/2022/1051\', \'Comment 6: ID 75800). Could you put this one back to entry as well? Sorry for the work.!image-1!""]\']\nRelated Issues:\n[]\n\n### End'}"
992,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8039\n\n### Instruction:\nHello,\r\n\r\nAttached LOTs are not showing dosed quantity in DHP.\r\n\r\nPlease assist.\r\n\n\n### Response:\n[""Comment 1: [\'!image!!image-1!\'"", \'Comment 2: \\\'{code:java}2022-12-09 14:23:07 (/Plant.PCS.BusinessLogic/SAURSRV04/6936/7) [Error] Microsoft.EntityFrameworkCore.Query - An exception occurred while iterating over the results of a query for context type \\\\\\\'""Plant.PCS.BusinessLogic.Infrastructure.EF.IntercontextCommunicationDbContext""\\\\\\\'.""""""Microsoft.Data.SqlClient.SqlException (0x80131904): A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider\', \'Comment 3: error: 40 - Could not open a connection to SQL Server) ---> System.ComponentModel.Win32Exception (53): The network path was not found.   at Microsoft.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject\', \'Comment 4: UInt32 waitForMultipleObjectsTimeout\', \'Comment 5: Boolean allowCreate\', \'Comment 6: Boolean onlyOneCheckConnection\', \'Comment 7: DbConnectionOptions userOptions\', \'Comment 8: DbConnectionInternal& connection)   at Microsoft.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject\', \'Comment 9: TaskCompletionSource`1 retry\', \'Comment 10: DbConnectionOptions userOptions\', \'Comment 11: DbConnectionInternal& connection)   at Microsoft.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection\', \'Comment 12: TaskCompletionSource`1 retry\', \'Comment 13: DbConnectionOptions userOptions\', \'Comment 14: DbConnectionInternal oldConnection\', \'Comment 15: DbConnectionInternal& connection)   at Microsoft.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection\', \'Comment 16: DbConnectionFactory connectionFactory\', \'Comment 17: TaskCompletionSource`1 retry\', \'Comment 18: DbConnectionOptions userOptions)   at Microsoft.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry\', \'Comment 19: SqlConnectionOverrides overrides)   at Microsoft.Data.SqlClient.SqlConnection.Open(SqlConnectionOverrides overrides)   at Microsoft.EntityFrameworkCore.Storage.RelationalConnection.OpenInternal(Boolean errorsExpected)   at Microsoft.EntityFrameworkCore.Storage.RelationalConnection.Open(Boolean errorsExpected)   at Microsoft.EntityFrameworkCore.Storage.RelationalCommand.ExecuteReader(RelationalCommandParameterObject parameterObject)   at Microsoft.EntityFrameworkCore.Query.Internal.SingleQueryingEnumerable`1.Enumerator.InitializeReader(Enumerator enumerator)   at Microsoft.EntityFrameworkCore.SqlServer.Storage.Internal.SqlServerExecutionStrategy.Execute[TState,TResult](TState state\', \'Comment 20: Func`3 operation\', \'Comment 21: Func`3 verifySucceeded)   at Microsoft.EntityFrameworkCore.Query.Internal.SingleQueryingEnumerable`1.Enumerator.MoveNext()ClientConnectionId:00000000-0000-0000-0000-000000000000Error Number:53,State:0,Class:20""Microsoft.Data.SqlClient.SqlException (0x80131904): A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider\', \'Comment 22: error: 40 - Could not open a connection to SQL Server) ---> System.ComponentModel.Win32Exception (53): The network path was not found.   at Microsoft.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject\', \'Comment 23: UInt32 waitForMultipleObjectsTimeout\', \'Comment 24: Boolean allowCreate\', \'Comment 25: Boolean onlyOneCheckConnection\', \'Comment 26: DbConnectionOptions userOptions\', \'Comment 27: DbConnectionInternal& connection)   at Microsoft.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject\', \'Comment 28: TaskCompletionSource`1 retry\', \'Comment 29: DbConnectionOptions userOptions\', \'Comment 30: DbConnectionInternal& connection)   at Microsoft.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection\', \'Comment 31: TaskCompletionSource`1 retry\', \'Comment 32: DbConnectionOptions userOptions\', \'Comment 33: DbConnectionInternal oldConnection\', \'Comment 34: DbConnectionInternal& connection)   at Microsoft.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection\', \'Comment 35: DbConnectionFactory connectionFactory\', \'Comment 36: TaskCompletionSource`1 retry\', \'Comment 37: DbConnectionOptions userOptions)   at Microsoft.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry\', \'Comment 38: SqlConnectionOverrides overrides)   at Microsoft.Data.SqlClient.SqlConnection.Open(SqlConnectionOverrides overrides)   at Microsoft.EntityFrameworkCore.Storage.RelationalConnection.OpenInternal(Boolean errorsExpected)   at Microsoft.EntityFrameworkCore.Storage.RelationalConnection.Open(Boolean errorsExpected)   at Microsoft.EntityFrameworkCore.Storage.RelationalCommand.ExecuteReader(RelationalCommandParameterObject parameterObject)   at Microsoft.EntityFrameworkCore.Query.Internal.SingleQueryingEnumerable`1.Enumerator.InitializeReader(Enumerator enumerator)   at Microsoft.EntityFrameworkCore.SqlServer.Storage.Internal.SqlServerExecutionStrategy.Execute[TState,TResult](TState state\', \'Comment 39: Func`3 operation\', ""Comment 40: Func`3 verifySucceeded)   at Microsoft.EntityFrameworkCore.Query.Internal.SingleQueryingEnumerable`1.Enumerator.MoveNext()ClientConnectionId:00000000-0000-0000-0000-000000000000Error Number:53,State:0,Class:20{code}\'"", \'Comment 41: ""{code:java}SELECT *  FROM [DHPlantPCSBusinessLogicEvents].[dbo].[ProductionLots] where AggregateId=\\\'6445a774-0ad1-4d86-b00d-42722bc8ab19\\\'  SELECT *  FROM [DHPlantPCSBusinessLogicEvents].[dbo].[ProductionLots] where AggregateId=\\\'716a9be0-d457-4f65-96e7-0e0406164d70\\\' {code}{code:java}SELECT *  FROM [10.0.1.40\\\\\\\\PCS].[DHExchange66].[dbo].[SqlApiRequestLog]  where parameters like \\\'%66221208002%\\\'GOSELECT *  FROM [10.0.1.40\\\\\\\\PCS].[DHExchange66].[dbo].[SqlApiRequestLog]  where parameters like \\\'%66221205009%\\\'GO{code} !screenshot-1! !image-2022-12-09-15-08-53-441!""\', ""Comment 42: \'There are entries in PCS module(Plant.PCS.BusinessLogic)  about missing sql connections,module has been restarted.Missing amounts of doses should be add in the application manually.That PLR from yesterday also has dosed information missing from PCS?"", ""Comment 43: I have only as below: !screenshot-2! \'"", ""Comment 44: \'What table is that?\'"", ""Comment 45: \'[10.0.1.40\\\\\\\\PCS].[DHExchange66].[dbo].[SqlApiRequestLog]\'"", ""Comment 46: \'Sorry..Same table.Thought you were looking at 009\'"", ""Comment 47: \'Please drop it to a P2\'"", \'Comment 48: ""We\\\'ve asked them to create it manually in the mean time. Can you tell us what went wrong with 009?We\\\'ll report 002 to the PCS supplier.Doesn\\\'t the new version of DHP (8.3) accept zero (0) value production lots?""\', ""Comment 49: \'PLR 66221208002 has been finished by user not PCS. !screenshot-5! As for PLR 66221205009 there was a DHP upgrade at the time"", ""Comment 50: and only those from before seven in the morning registered in the plant. !screenshot-4!So I suspect the cause here.\'"", ""Comment 51: \'Thanks"", ""Comment 52: you may close this ticket\']""]\nRelated Issues:\n[]\n\n### End'}"
993,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8038\n\n### Instruction:\nShipping Notice isn\'t arriving in DHP it is in DHC though. \r\nConcerns 7_L000076575 with ext_nr 00944774\r\n\r\n\n\n### Response:\n[""Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 2: \'Hello"", ""Comment 3: We kindly inform you that wecurrentlyare processing another Priority1 task DGS-8030.We will revert to processing your task as soon as possible.Regards\'"", ""Comment 4: \'Please verify !image-2022-12-09-14-09-52-731.png!\'"", ""Comment 5: \'Yes"", ""Comment 6: it is there now. Thank you Adrian!\']""]\nRelated Issues:\n[]\n\n### End'}"
994,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8037\n\n### Instruction:\nDzień dobry,\r\n\r\nproszę o dodanie nowego składnika wynagrodzeń jakim jest: odprawa pośmiertna. \r\n\r\nZgłoszenie proszę przekazać dla Monika Biśta.\r\nZgłoszenie już zostało zrealizowane - do zamknięcia. \n\n### Response:\n[""Comment 1: [\'Dzień dobry,Zgłoszenie zostało przyjęte do weryfikacji.\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Realized\']""]\nRelated Issues:\n[]\n\n### End'}"
995,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8036\n\n### Instruction:\nOn creation of VT for call off for Andel-Mest (location 98, managed in DHP Andel, location 5), an error message is given. See e.g. CL000008902\r\n\r\nPlease check why we get an error message / how it can be solved. We must be able to register intakes for Andel-Mest.\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 3: \\\'022-12-09 14:40:13 (bf5569e0-a6ee-478b-938f-804b730efead/Plant.VC.BusinessLogic/DHVD01AP184/18856/10) [Error] Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware - Error during request{ ""scheme"": ""http""\', \'Comment 4: ""host"": { ""Value"": ""dhvd01ap184:82""\', \'Comment 5: ""HasValue"": true\', \'Comment 6: ""Host"": ""dhvd01ap184""\', \'Comment 7: ""Port"": 82 }\', \'Comment 8: ""path"": ""/api/VehicleTicket/createVehicleTicketFromShippingNotice""\', \'Comment 9: ""queryString"": []\', \'Comment 10: ""requestBody"": ""\\\\\\\\""7d2730b1-a089-42f9-85a3-14e62543d118\\\\\\\\""""}.System.ArgumentException: DefaultDestinationSiteIsNotConfigured at Plant.VC.BusinessLogic.Domain.Configuration.ConfigurationExtensions.GetDestinationSiteIdOrThrow(Dictionary`2 defaultDestinationSitesStructure\', \'Comment 11: AggregateId businessUnitId) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\67ba263564c33499\\\\\\\\Plant.VC.BusinessLogic\\\\\\\\Plant.VC.BusinessLogic.Domain\\\\\\\\Configuration\\\\\\\\ConfigurationExtensions.cs:line 15 at Plant.VC.BusinessLogic.Domain.VehicleTickets.Policies.BaseVehicleTicketFromShippingNoticeGenerationPolicy.AddBulkIntakeElementToVehicleTicket(VehicleTicket vehicleTicket\', \'Comment 12: ShippingNoticeElement shippingNoticeElement\', \'Comment 13: AggregateId businessUnitId\', \'Comment 14: ShippingNotice shippingNotice\', \'Comment 15: Item item\', \'Comment 16: BusinessPartner businessPartner\', \'Comment 17: Nullable`1 producerId) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\67ba263564c33499\\\\\\\\Plant.VC.BusinessLogic\\\\\\\\Plant.VC.BusinessLogic.Domain\\\\\\\\VehicleTickets\\\\\\\\Policies\\\\\\\\BaseVehicleTicketFromShippingNoticeGenerationPolicy.cs:line 180 at Plant.VC.BusinessLogic.Domain.VehicleTickets.Policies.ItemSettlementTypeVehicleTicketFromShippingNoticeGenerationPolicy.OnIntakeElementGeneration(AddShippingNoticeToVehicleTicketDomainDataStructure dataStructure\', \'Comment 18: ShippingNoticeElementRelationsDataStructure shippingNoticeRelations\', \'Comment 19: ShippingNoticeElement shippingNoticeElement) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\67ba263564c33499\\\\\\\\Plant.VC.BusinessLogic\\\\\\\\Plant.VC.BusinessLogic.Domain\\\\\\\\VehicleTickets\\\\\\\\Policies\\\\\\\\ItemSettlementTypeVehicleTicketFromShippingNoticeGenerationPolicy.cs:line 26 at Plant.VC.BusinessLogic.Domain.VehicleTickets.Policies.BaseVehicleTicketFromShippingNoticeGenerationPolicy.AddVehicleTicketElements(AddShippingNoticeToVehicleTicketDomainDataStructure dataStructure) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\67ba263564c33499\\\\\\\\Plant.VC.BusinessLogic\\\\\\\\Plant.VC.BusinessLogic.Domain\\\\\\\\VehicleTickets\\\\\\\\Policies\\\\\\\\BaseVehicleTicketFromShippingNoticeGenerationPolicy.cs:line 108 at Plant.VC.BusinessLogic.Domain.VehicleTickets.Policies.BaseVehicleTicketFromShippingNoticeGenerationPolicy.GenerateVehicleTicket(CreateVehicleTicketFromShippingNoticeDomainDataStructure dataStructure\', \'Comment 20: ContainerCompartment compartments) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\67ba263564c33499\\\\\\\\Plant.VC.BusinessLogic\\\\\\\\Plant.VC.BusinessLogic.Domain\\\\\\\\VehicleTickets\\\\\\\\Policies\\\\\\\\BaseVehicleTicketFromShippingNoticeGenerationPolicy.cs:line 49 at Plant.VC.BusinessLogic.Application.VehicleTickets.Services.VehicleTicketService.CreateVehicleTicketFromShippingNotice(AggregateId vehicleTicketId\', \'Comment 21: AggregateId shippingNoticeId\', \'Comment 22: Boolean isPlanned) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\67ba263564c33499\\\\\\\\Plant.VC.BusinessLogic\\\\\\\\Plant.VC.BusinessLogic.Application\\\\\\\\VehicleTickets\\\\\\\\Services\\\\\\\\VehicleTicketService.cs:line 485 at Plant.VC.BusinessLogic.Application.VehicleTickets.CommandHandlers.CreateVehicleTicketFromShippingNoticeCommandHandler.Handle(CreateVehicleTicketFromShippingNoticeCommand command) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\67ba263564c33499\\\\\\\\Plant.VC.BusinessLogic\\\\\\\\Plant.VC.BusinessLogic.Application\\\\\\\\VehicleTickets\\\\\\\\CommandHandlers\\\\\\\\CreateVehicleTicketFromShippingNoticeCommandHandler.cs:line 21 at Kotrak.Common.Infrastructure.Commands.CommandEnvironment.Run[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.IntercontextEventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.EventCommandRunEnvironmentDecorator.Run[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Commands.Decorators.ValidationCommandEnvironmentDecorator.Run[TCommand](TCommand command) at Castle.DynamicProxy.AbstractInvocation.Proceed() at Kotrak.Common.Infrastructure.Interceptors.LoggingInterceptor`1.Intercept(IInvocation invocation) at Castle.DynamicProxy.AbstractInvocation.Proceed() at Kotrak.Common.Infrastructure.Commands.Decorators.HistoryGateDecorator.Dispatch[TCommand](TCommand command) at Plant.VC.BusinessLogic.Infrastructure.Api.Controllers.VehicleTicketController.CreateVehicleTicketFromShippingNotice(Guid shippingNoticeId) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\67ba263564c33499\\\\\\\\Plant.VC.BusinessLogic\\\\\\\\Plant.VC.BusinessLogic.Infrastructure.Api\\\\\\\\Controllers\\\\\\\\VehicleTicketController.cs:line 762 at lambda_method33788(Closure \', \'Comment 23: Object \', \'Comment 24: Object[] ) at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor.SyncActionResultExecutor.Execute(IActionResultTypeMapper mapper\', \'Comment 25: ObjectMethodExecutor executor\', \'Comment 26: Object controller\', \'Comment 27: Object[] arguments) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeActionMethodAsync() at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next\', \'Comment 28: Scope& scope\', \'Comment 29: Object& state\', \'Comment 30: Boolean& isCompleted) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeNextActionFilterAsync()--- End of stack trace from previous location --- at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Rethrow(ActionExecutedContextSealed context) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next\', \'Comment 31: Scope& scope\', \'Comment 32: Object& state\', \'Comment 33: Boolean& isCompleted) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeInnerFilterAsync()--- End of stack trace from previous location --- at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeFilterPipelineAsync>g__Awaited|20_0(ResourceInvoker invoker\', \'Comment 34: Task lastTask\', \'Comment 35: State next\', \'Comment 36: Scope scope\', \'Comment 37: Object state\', \'Comment 38: Boolean isCompleted) at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker\', \'Comment 39: Task task\', \'Comment 40: IDisposable scope) at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker\', \'Comment 41: Task task\', \'Comment 42: IDisposable scope) at Microsoft.AspNetCore.Routing.EndpointMiddleware.<Invoke>g__AwaitRequestTask|6_0(Endpoint endpoint\', \'Comment 43: Task requestTask\', \'Comment 44: ILogger logger) at Swashbuckle.AspNetCore.SwaggerUI.SwaggerUIMiddleware.Invoke(HttpContext httpContext) at Swashbuckle.AspNetCore.Swagger.SwaggerMiddleware.Invoke(HttpContext httpContext\', ""Comment 45: ISwaggerProvider swaggerProvider) at Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware.Invoke(HttpContext httpContext)\'"", ""Comment 46: \'!image-2022-12-09-14-58-36-384.png!\'"", ""Comment 47: \'HelloThere is no unit in configuration for feed 098 :Please add it in WMS->configuration-> storage locations!image-2022-12-09-15-07-22-352.png!Then in VT configuration check if here you have value"", ""Comment 48: if it will be empty add new line!image-2022-12-09-14-58-36-384.png!Please let me know if that informations are helpfull and we may clos ethe task\'"", ""Comment 49: \'May we close the task?\'"", ""Comment 50: \'Vt intake arrived. This task can be closed.  {quote}Op 20 dec. 2022 om 08:31 heeft Agnieszka Januszewska (Jira) <jira@kotrak.com> het volgende geschreven:  {quote}  {quote} \\\\ufeff |{color:#ffffff} CAUTION: This message originated from outside the organisation. Please do not click on links or open attachments unless you trust the sender and know the content is safe.{color} |{color:#999999}{color}{color:#999999}{color}{color:#7a869a}{color}{color:#7a869a}{color}  {quote}\']""]\nRelated Issues:\n[\'DGS-8115\']\n\n### End'}"
996,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8035\n\n### Instruction:\nMove feed from 00651A/0006/0001 to 806514/0004/0001.\r\n\r\nIn Milas this is already done.\n\n### Response:\n[""Comment 1: [\'Hi Mitch"", \'Comment 2: can I ask what happened that Feed Sale invoices were booked on customer 0651A\', \'Comment 3: so they were sent to Round 0651A/0006/0001\', \'Comment 4: but then the customer was changed\', ""Comment 5: so now they should be in Round 806514/0004/0001?\'"", ""Comment 6: \'A wrong customer number was use in Intense unfortunately. The specific customer has different account and a wrong one was used.\'"", ""Comment 7: \'[~damian.swistek@kotrak.com]dasz radę to ogarnąć albo pokazać Grzesiowi lub Tomkowi jak to zrobić? Należy przenieść pozycje Feed Sale z00651A/0006/0001 do 806514/0004/0001.\'"", ""Comment 8: \'22 elements from Feed Sale FE-L/0006 releted to Round00651A/0006/0001 have been moved to the Feed SaleFE-L/0002 related to Round806514/0004/0001. There are 63 elements in total. From No. 42 there are moved elements.!image-2022-12-13-15-21-11-234.png!\'"", ""Comment 9: \'Elements have been moved to other Feed Sale\']""]\nRelated Issues:\n[]\n\n### End'}"
997,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8034\n\n### Instruction:\nRecipe 505582 for Global feed mill (plant 15) was sent from DHH. Import of recipe in DHC failed.\r\nRecipes were sent yesterday and today\r\n\r\nError message: Object reference not set to an instance of an object.\r\n\r\nCan you check why the import failed / how it can be fixed. Plant needs the recipe.\r\n\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Dear Bob,Item is not linked.Regards!image-2022-12-09-10-47-20-176.png!\'"", \'Comment 4: ""{code:java}2022-12-09 11:22:10,600 [176] ERROR Evolution.DHCountry.Logging.EventPublisherWithLog4NetTracing [(null)] - Error occurred for event [Evolution.DHCountry.Dictionaries.Recipes.Events.RecipeChangedEvent[RecipeId=\\\'b17da454-8b02-43df-91b2-d82ec5b5fc11\\\']] in publisher [Evolution.Events.EventPublisher] under domain context [a5cea9f65ec04d4d85861d54e4850951]Evolution.Events.EventPublishException: Exception occurred while handling event. ---> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.NullReferenceException: Object reference not set to an instance of an object.   at Evolution.DHCountry.Production.AS400.ContaminationGroups.Queries.GetMatchedContaminationGroupAS400Query.OnExecute() in E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\156434433\\\\\\\\DHAPPSV3-DHC1239-JOB1\\\\\\\\Evolution.DHCountry\\\\\\\\Evolution.DHCountry\\\\\\\\Production\\\\\\\\AS400\\\\\\\\ContaminationGroups\\\\\\\\Queries\\\\\\\\GetMatchedContaminationGroupAS400Query.cs:line 115   at Evolution.DHCountry.Domain.DomainCommand.Execute() in E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\156434433\\\\\\\\DHAPPSV3-DHC1239-JOB1\\\\\\\\Evolution.DHCountry\\\\\\\\Evolution.DHCountry\\\\\\\\Domain\\\\\\\\DomainCommand.cs:line 94   at Evolution.DHCountry.Dictionaries.Recipes.Subscribers.GenerateProductionRecipeSubcriber.GetMatchedContaminationGroupId(Recipe recipe\', \'Comment 5: Model context) in E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\156434433\\\\\\\\DHAPPSV3-DHC1239-JOB1\\\\\\\\Evolution.DHCountry\\\\\\\\Evolution.DHCountry\\\\\\\\Dictionaries\\\\\\\\Recipes\\\\\\\\Subscribers\\\\\\\\GenerateProductionRecipeSubcriber.cs:line 300   at Evolution.DHCountry.Dictionaries.Recipes.Subscribers.GenerateProductionRecipeSubcriber.ValidateMatchedContaminationGroupsForAS400(Recipe recipe\', \'Comment 6: Model context\', \'Comment 7: ValidationResult& result) in E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\156434433\\\\\\\\DHAPPSV3-DHC1239-JOB1\\\\\\\\Evolution.DHCountry\\\\\\\\Evolution.DHCountry\\\\\\\\Dictionaries\\\\\\\\Recipes\\\\\\\\Subscribers\\\\\\\\GenerateProductionRecipeSubcriber.cs:line 221   at Evolution.DHCountry.Dictionaries.Recipes.Subscribers.GenerateProductionRecipeSubcriber.Validate(Recipe recipe\', \'Comment 8: Model context) in E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\156434433\\\\\\\\DHAPPSV3-DHC1239-JOB1\\\\\\\\Evolution.DHCountry\\\\\\\\Evolution.DHCountry\\\\\\\\Dictionaries\\\\\\\\Recipes\\\\\\\\Subscribers\\\\\\\\GenerateProductionRecipeSubcriber.cs:line 206   at Evolution.DHCountry.Dictionaries.Recipes.Subscribers.GenerateProductionRecipeSubcriber.GenerateProductionRecipeFromRecipe(Guid recipeId\', \'Comment 9: Boolean generatedAutomatically) in E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\156434433\\\\\\\\DHAPPSV3-DHC1239-JOB1\\\\\\\\Evolution.DHCountry\\\\\\\\Evolution.DHCountry\\\\\\\\Dictionaries\\\\\\\\Recipes\\\\\\\\Subscribers\\\\\\\\GenerateProductionRecipeSubcriber.cs:line 150   at Evolution.DHCountry.Dictionaries.Recipes.Subscribers.GenerateProductionRecipeSubcriber.OnEventHandle(RecipeChangedEvent event) in E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\156434433\\\\\\\\DHAPPSV3-DHC1239-JOB1\\\\\\\\Evolution.DHCountry\\\\\\\\Evolution.DHCountry\\\\\\\\Dictionaries\\\\\\\\Recipes\\\\\\\\Subscribers\\\\\\\\GenerateProductionRecipeSubcriber.cs:line 47   --- End of inner exception stack trace ---   at System.RuntimeMethodHandle.InvokeMethod(Object target\', \'Comment 10: Object[] arguments\', \'Comment 11: Signature sig\', \'Comment 12: Boolean constructor)   at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj\', \'Comment 13: Object[] parameters\', \'Comment 14: Object[] arguments)   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj\', \'Comment 15: BindingFlags invokeAttr\', \'Comment 16: Binder binder\', \'Comment 17: Object[] parameters\', \'Comment 18: CultureInfo culture)   at Evolution.Events.EventPublisher.HandleEvent(Object subscriber\', \'Comment 19: Object event)   at Evolution.Events.EventPublisher.PublishToSubscriberTypes(Object event\', \'Comment 20: IEnumerable`1 subscriberTypes)   --- End of inner exception stack trace ---   at Evolution.Events.EventPublisher.PublishToSubscriberTypes(Object event\', \'Comment 21: IEnumerable`1 subscriberTypes)   at Evolution.Events.EventPublisher.Publish(Object event)   at Evolution.DHCountry.Logging.EventPublisherWithLog4NetTracing.Publish(Object event) in E:\\\\\\\\BambooHome\\\\\\\\xml-data\\\\\\\\build-dir\\\\\\\\156434433\\\\\\\\DHAPPSV3-DHC1239-JOB1\\\\\\\\Evolution.DHCountry\\\\\\\\Evolution.DHCountry\\\\\\\\Logging\\\\\\\\EventPublisherWithLog4NetTracing.cs:line 31{code}""\', ""Comment 22: \'In error logs we have information that contamination group is not matched to this recipe when we trying to import recipe.Please"", ""Comment 23: verify\'"", ""Comment 24: \'Indeed"", \'Comment 25: item is not linked\', \'Comment 26: but that should not give issue on import of recipe.Assigning of contamination group normally happens when recipe is accepted\', \'Comment 27: not on import. And even if recipe cannot be accepted\', ""Comment 28: it is successfully imported and visible in DHC. In this case I cannot find the recipe in DHC!image-1!\'"", \'Comment 29: ""Well,As base item is not linked with DHH item\', ""Comment 30: the recipe cannot linked to contamination group. So it won\'t appear to accept according to error about containation group matching. The best and the quickest way is t link base item with dhh item.I have consulted your case"", \'Comment 31: in version 3.0.61 this issue should not occur. If possible\', \'Comment 32: please\', \'Comment 33: link items.Best regards""\', ""Comment 34: \'ERP item was not exported. I exported it. DHC linked the item automatically. Can you reprocess the recipe?!image-2!\'"", ""Comment 35: \'We have already sent recipe fro Holding"", ""Comment 36: please verify. On our side we can see version 2.Regards\'"", ""Comment 37: \'Yes"", \'Comment 38: now both versions are in DHC and accepted.So\', \'Comment 39: currently import of recipes fails if item is not linked? This is new for me; I do know that it cannot be accepted before it is linked\', ""Comment 40: but then at least the recipe is visible in DHC\'"", ""Comment 41: \'Yes"", \'Comment 42: because contaminaton group requires linked items.If everything is fine now\', ""Comment 43: can we close task? :)Regards\'"", ""Comment 44: \'Yes"", ""Comment 45: you can close this task.\'"", ""Comment 46: \'Thank you\'"", ""Comment 47: \'Ok"", ""Comment 48: thank you. I will check this with formulation.\'"", \'Comment 49: ""Hi Bob,Shouldn\\\'t this comment be underDGS-8849? ;)""\', ""Comment 50: \'Indeed. My mistake.\'"", ""Comment 51: \'No issue :)\']""]\nRelated Issues:\n[]\n\n### End'}"
998,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8033\n\n### Instruction:\nHello,\r\n\r\nVT-153/12/MM and VT-158/12/MM are stuck in DHC (please see attached error message).\r\nSORs are not showing in ERP, we are not sure whether they were re-opened and deleted.\r\n\r\nhttps://helpdesk.kotrak.com/servicedesk/customer/portal/56/DGS-6448\r\n\r\nPlease assist.\r\n\n\n### Response:\n[""Comment 1: [\'!image!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", ""Comment 3: \'Morning,Can we please have feedback \'"", ""Comment 4: \'{code:java}2022-12-12 20:24:33,956 [63] INFO  Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor [(null)] - VehicleTicket - VT-158/12/2022/MM [Id: ac544643-16f6-49f0-a183-366af7e8e4d3]2022-12-12 20:24:33,956 [63] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor [(null)] - VehicleTicket Validator started - Evolution.ErpIntegrator.Extensions.VTOrderValidator.VehicleTicketOrderValidator2022-12-12 20:24:33,956 [63] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor [(null)] - VehicleTicket Validator finished - Evolution.ErpIntegrator.Extensions.VTOrderValidator.VehicleTicketOrderValidator2022-12-12 20:24:34,050 [89] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateSalesOrderRelease [(null)] - GenerateSalesOrderRelease execution started2022-12-12 20:24:34,112 [89] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateSalesOrderRelease [(null)] - Forcing document number - 2783/0/2022/MPMM for vt element id - Id: 9118867a-22e7-4773-8fa0-58576aef75bf2022-12-12 20:24:34,191 [89] ERROR Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateSalesOrderRelease [(null)] - System.InvalidOperationException: Sequence contains no elements   at System.Linq.Enumerable.Single[TSource](IEnumerable`1 source)   at System.Data.Entity.Core.Objects.ELinq.ObjectQueryProvider.<>c__14`1.<GetElementFunction>b__14_3(IEnumerable`1 sequence)   at System.Data.Entity.Core.Objects.ELinq.ObjectQueryProvider.ExecuteSingle[TResult](IEnumerable`1 query"", \'Comment 5: Expression queryRoot)   at System.Data.Entity.Core.Objects.ELinq.ObjectQueryProvider.System.Linq.IQueryProvider.Execute[TResult](Expression expression)   at System.Data.Entity.Internal.Linq.DbQueryProvider.Execute[TResult](Expression expression)   at System.Linq.Queryable.Single[TSource](IQueryable`1 source)   at Evolution.ErpIntegrator.CdnXL.CdnXL2019.Dictionaries.Items.CdnXL2019ItemRepository.GetItem(XLObjectKey xlId\', \'Comment 6: String code) in C:\\\\\\\\TeamCity\\\\\\\\buildAgent\\\\\\\\work\\\\\\\\57a7e278b67a115c\\\\\\\\Evolution.ErpIntegrator\\\\\\\\CdnXL\\\\\\\\Evolution.ErpIntegrator.CdnXL.CdnXL2019\\\\\\\\Dictionaries\\\\\\\\Items\\\\\\\\CdnXL2019ItemRepository.cs:line 241   at Evolution.ErpIntegrator.CdnXL.CdnXL2019.Dictionaries.Items.CdnXL2019ItemRepository.GetItem(ObjectKey id) in C:\\\\\\\\TeamCity\\\\\\\\buildAgent\\\\\\\\work\\\\\\\\57a7e278b67a115c\\\\\\\\Evolution.ErpIntegrator\\\\\\\\CdnXL\\\\\\\\Evolution.ErpIntegrator.CdnXL.CdnXL2019\\\\\\\\Dictionaries\\\\\\\\Items\\\\\\\\CdnXL2019ItemRepository.cs:line 30   at Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateSalesOrderRelease.GenerateSalesOrderReleaseData(VehicleTicket vehicleTicket\', \'Comment 7: IMatchRule`1 vehicleTicketElementSelector)   at Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateSalesOrderRelease.OnExecute(VehicleTicket vehicleTicket)   at Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketIntegrationTaskBase.OnExecute(Object data)   at Evolution.ErpIntegrator.IntegrationLibrary.IntegrationTaskBase.Execute(Object data)2022-12-12 20:24:34,191 [89] ERROR Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor [(null)] - Sequence contains no elementsSystem.InvalidOperationException: Sequence contains no elements   at System.Linq.Enumerable.Single[TSource](IEnumerable`1 source)   at System.Data.Entity.Core.Objects.ELinq.ObjectQueryProvider.<>c__14`1.<GetElementFunction>b__14_3(IEnumerable`1 sequence)   at System.Data.Entity.Core.Objects.ELinq.ObjectQueryProvider.ExecuteSingle[TResult](IEnumerable`1 query\', \'Comment 8: Expression queryRoot)   at System.Data.Entity.Core.Objects.ELinq.ObjectQueryProvider.System.Linq.IQueryProvider.Execute[TResult](Expression expression)   at System.Data.Entity.Internal.Linq.DbQueryProvider.Execute[TResult](Expression expression)   at System.Linq.Queryable.Single[TSource](IQueryable`1 source)   at Evolution.ErpIntegrator.CdnXL.CdnXL2019.Dictionaries.Items.CdnXL2019ItemRepository.GetItem(XLObjectKey xlId\', \'Comment 9: String code) in C:\\\\\\\\TeamCity\\\\\\\\buildAgent\\\\\\\\work\\\\\\\\57a7e278b67a115c\\\\\\\\Evolution.ErpIntegrator\\\\\\\\CdnXL\\\\\\\\Evolution.ErpIntegrator.CdnXL.CdnXL2019\\\\\\\\Dictionaries\\\\\\\\Items\\\\\\\\CdnXL2019ItemRepository.cs:line 241   at Evolution.ErpIntegrator.CdnXL.CdnXL2019.Dictionaries.Items.CdnXL2019ItemRepository.GetItem(ObjectKey id) in C:\\\\\\\\TeamCity\\\\\\\\buildAgent\\\\\\\\work\\\\\\\\57a7e278b67a115c\\\\\\\\Evolution.ErpIntegrator\\\\\\\\CdnXL\\\\\\\\Evolution.ErpIntegrator.CdnXL.CdnXL2019\\\\\\\\Dictionaries\\\\\\\\Items\\\\\\\\CdnXL2019ItemRepository.cs:line 30   at Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateSalesOrderRelease.GenerateSalesOrderReleaseData(VehicleTicket vehicleTicket\', \'Comment 10: IMatchRule`1 vehicleTicketElementSelector)   at Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateSalesOrderRelease.OnExecute(VehicleTicket vehicleTicket)   at Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketIntegrationTaskBase.OnExecute(Object data)   at Evolution.ErpIntegrator.IntegrationLibrary.IntegrationTaskBase.Execute(Object data)   at Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor.<>c__DisplayClass6_2.<ProcessSingleVT>b__1()2022-12-12 20:24:34,191 [63] ERROR Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor [(null)] - Sequence contains no elementsSystem.InvalidOperationException: Sequence contains no elements   at Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor.ProcessSingleVT(VehicleTicket vehicleTicket)2022-12-12 20:24:34,191 [63] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.VehicleTicketProcessor [(null)] - VehicleTicketProcessor execution finished2022-12-12 20:24:34,191 [63] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.ProductionLotReports.ProductionLotReportProcessor [(null)] - ProductionLotReportProcessor execution started2022-12-12 20:24:34,206 [63] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.ProductionLotReports.ProductionLotReportProcessor [(null)] - ProductionLotReportProcessor execution finished2022-12-12 20:24:37,524 [SoapERPService_18] DEBUG Evolution.ErpIntegrator.Services.ERP.CdnXL.SoapERPService [(null)] - Recived Order message from trigger - ID - 7868762022-12-12 20:24:37,540 [SoapERPService_18] DEBUG Evolution.ErpIntegrator.Services.ERP.CdnXL.SoapERPService [(null)] - Order data downloaded - SO-526/22/MMW2022-12-12 20:24:37,540 [SoapERPService_18] DEBUG Evolution.ErpIntegrator.Services.ERP.CdnXL.SoapERPService [(null)] - Sending Order message - SO-526/22/MMW2022-12-12 20:24:37,540 [SoapERPService_18] DEBUG Evolution.ErpIntegrator.Services.ServiceManager [(null)] - Order message mapping.... (Firma:556290 - TYP:960/NUMER:786876/LP:0\', \'Comment 11: SO-526/22/MMW)2022-12-12 20:24:37,555 [SoapERPService_18] DEBUG Evolution.ErpIntegrator.Services.ServiceManager [(null)] - Order message mapped (Firma:556290 - TYP:960/NUMER:786876/LP:0\', \'Comment 12: SO-526/22/MMW)2022-12-12 20:24:37,555 [SoapERPService_18] DEBUG Evolution.ErpIntegrator.Services.ServiceManager [(null)] - Order message send (Firma:556290 - TYP:960/NUMER:786876/LP:0\', ""Comment 13: SO-526/22/MMW){code}\'"", \'Comment 14: ""Sprawdziłem linkowane itemy i order elementy\', \'Comment 15: klientai powiązanie elementów VT do elementów SO.{code:java}SELECT ve.*  FROM [DHCountry_RSA_PROD].[dbo].[VehicleTicketElements] ve  left join [DHCountry_RSA_PROD].[dbo].[OrderElements] oe on ve.[OrderElementId]=oe.id  where ve.VehicleTicketId=\\\'AC544643-16F6-49F0-A183-366AF7E8E4D3\\\'SELECT TOP (1000) [Id]      ,[DhcId]      ,[XlId]      ,[XlTyp]      ,[XlFirma]  FROM [DHCErpPlugin_RSA_PROD].[dbo].[ItemSyncs]  where dhcid=\\\'1095AE07-44C7-4438-A3C8-58407D7928ED\\\'  or DhcId=\\\'5F577FD4-7D25-4F7A-9B11-979388197B3D\\\'  /****** Script for SelectTopNRows command from SSMS  ******/SELECT TOP (1000) [Id]      ,[DhcId]      ,[XlId]      ,[XlTyp]      ,[XlFirma]  FROM [DHCErpPlugin_RSA_PROD].[dbo].[OrderElementSyncs]  where DhcId in(\\\'44335F42-6A97-452A-ACB3-145D777A8122\\\',\\\'50E2E0E8-03C2-47AD-9CAE-536325F07FF0\\\')SELECT TOP (1000) [Id]      ,[DhcId]      ,[XlId]      ,[XlTyp]      ,[XlFirma]  FROM [DHCErpPlugin_RSA_PROD].[dbo].[OrderSyncs]  where xlid in(787981,786876)  or DhcId=\\\'A20D0E7A-7E78-49A7-B5F7-8F6DF0200CF1\\\'{code}""\', ""Comment 16: \' !screenshot-1! \'"", ""Comment 17: \'problem się zaczal 5 grudnia!image-2022-12-13-13-04-48-160.png!\'"", ""Comment 18: \'{code:java}  update z  set z.zae_twrtyp=16 FROM [CDNXL_DHFU].[CDN].[ZamElem] z  left join cdn.twrkarty t on t.twr_gidnumer=z.zae_twrnumer  where zae_twrtyp=2  select cdn.tstodate(zan_datawystawienia,0),* from cdn.zamnag where zan_gidnumer in(select  ZaE_GIDNumer FROM [CDNXL_DHFU].[CDN].[ZamElem] z    where zae_twrtyp=2){code}\'"", ""Comment 19: \'Corrected for now"", ""Comment 20: please check.As to the cause - under investigation.\'"", ""Comment 21: \'VTs generated.\'"", \'Comment 22: ""Hello,SO-989/22/KDWSO-990/22/KDWSO-991/22/KDWSO-992/22/KDWSO-993/22/KDWSO-597/22/MMWSO-994/22/KDWThe problem still occurs due to incorrect data on the order elements/items. Were they created differently from the others?(it\\\'s not about creating from a copy or from a plus)Above is a list from the last days.""\', ""Comment 23: \'Hi PiotrYes"", ""Comment 24: they were created differently. I inserted the line items via SQL.Can you tell me what field was/is wrong?Regards\'"", ""Comment 25: \'Hello,zae_twrtyp column should be equal to 16 it is a reference to a group of items.\'"", ""Comment 26: \'Hello"", ""Comment 27: VT 323/12/2022/MM has the same issue. !image-1!\'"", ""Comment 28: \'Generated.\'"", \'Comment 29: ""Thank you. I\\\'ll fix that now. Please keep the ticket open till I can confirm.""\', \'Comment 30: ""Ok\', ""Comment 31: I\'véupdate the query"", \'Comment 32: and the orders already create with the incorrect type.Thank you for the assistance.""\', ""Comment 33: \'Thank you for confirmation.\']""]\nRelated Issues:\n[]\n\n### End'}"
999,"{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8032\n\n### Instruction:\nHi, we\'ve a lots of awd in Active status in gui, but it should be Realized (PZ generated to awd).\r\nThe same status in dhc. Any idea why? It must be corrected....\r\n\r\nRafał Boniecki\r\n\n\n### Response:\n[""Comment 1: [\'!image!!image-1!!image-2!\'"", ""Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'"", \'Comment 3: ""Puściłem dwa przykładowe i się statusy zaaktualizowały{code:java}AWD-60201/08/22 EXECUTE [Kotrak].[ExecuteShipmentNotificationDHC3] \\\'XL Integrator 1.0\\\',12119444,1489,2573532AWD-79773/10/22 EXECUTE [Kotrak].[ExecuteShipmentNotificationDHC3] \\\'XL Integrator 1.0\\\',12496634,1490,2593274{code}{code:java}SELECT dhcs.status,dhcs.foreignnumber,sh.DocumentStatus,t.TrN_GIDNumer,t.TrN_GIDTyp,sh.idFROM [CDNXL_DEHEUS].[Kotrak].[ShipmentNotificationsHeaders] shINNER join [CDNXL_DEHEUS].[Kotrak].[ShipmentNotificationsElements] seon sh.id=se.HeaderIdINNER join cdn.TraNag t on t.TrN_GIDNumer=se.DocumentElementGIDNumberINNER join [sql03-20\\\\\\\\dhapp].[Evolution_DHCountry].[dbo].[ShippingNotices] DHCSon dhcs.foreignid=sh.id--where dhcs.foreignnumber=\\\'AWD-76509/10/22\\\'--where dhcs.status=6 and sh.DocumentStatus=9 OR WHERE dhcs.documentyear=2022 and dhcs.status<>6 and dhcs.foreignnumber like \\\'AWD%\\\'and sh.DocumentStatus=5--where--(dhcs.foreignnumber IN(\\\'AWD-79773/10/22\\\'))--)){code}jest takich ponad 50  !screenshot-1! !image-2022-12-13-19-19-25-475!""\', \'Comment 4: ""Ostatni przykład: !screenshot-2!  !screenshot-3! {code:java}2022-12-12 10:59:21,107 [126] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Interfaces.ExtensionsHelper [(null)] - Shipment Notification processing started for PZ-76/12/22/Y2022-12-12 10:59:21,107 [126] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Interfaces.ExtensionsHelper [(null)] - EXECUTE [Kotrak].[ExecuteShipmentNotificationDHC3] \\\'XL Integrator 1.0\\\',12567434,1489,26046182022-12-12 10:59:21,154 [126] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Interfaces.ExtensionsHelper [(null)] - Shipment Notification processing finished for PZ-76/12/22/Y2022-12-12 10:59:21,154 [126] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GeneratePurchaseOrderReceipt [(null)] - Extension for document completed - PZ-76/12/22/Y [Firma:246785 - TYP:1489/NUMER:12567434/LP:0] Evolution.ErpIntegrator.Extensions.MYShipmentNoticeUpdate.MYShipmentNoticeUpdate2022-12-12 10:59:21,154 [126] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GeneratePurchaseOrderReceipt [(null)] - Extension for document started - PZ-76/12/22/Y [Firma:246785 - TYP:1489/NUMER:12567434/LP:0] Evolution.ErpIntegrator.Extensions.PLAdvanceLogger.PLAdvanceLogerExtension2022-12-12 10:59:21,154 [126] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GeneratePurchaseOrderReceipt [(null)] - Extension for document completed - PZ-76/12/22/Y [Firma:246785 - TYP:1489/NUMER:12567434/LP:0] Evolution.ErpIntegrator.Extensions.PLAdvanceLogger.PLAdvanceLogerExtension2022-12-12 10:59:21,185 [126] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2021.Transactions.XLTransaction [(null)] - XL transaction commited\', \'Comment 5: token ID - U_Y/2XMWl1O@`LG?SI-RM=5---0>D---2022-12-12 10:59:21,185 [126] DEBUG Evolution.ErpIntegrator.DHC.DHC30.Database.DhcTransaction [(null)] - DHC transaction commit started2022-12-12 10:59:21,185 [126] DEBUG Evolution.ErpIntegrator.DHC.DHC30.Database.DhcTransaction [(null)] - DHC transaction commit finished{code}puszczam procedurę i executed !screenshot-4!  !screenshot-5! ""\', ""Comment 6: \'list of corrected awd below"", ""Comment 7: [^awd.txt] statuses are updated for the current ones.We will check in the next few days if there are any new cases.\'"", \'Comment 8: ""There are again SN with status Active. What\\\'s the problem?!image-3!""\', \'Comment 9: ""Są nowe w logu:{code:java}2022-12-21 12:35:15,845 [73] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GeneratePurchaseOrderReceipt [(null)] - Extension for document started - PZ-457/12/22/D [Firma:246785 - TYP:1489/NUMER:12600421/LP:0] Evolution.ErpIntegrator.Extensions.MYShipmentNoticeUpdate.MYShipmentNoticeUpdate2022-12-21 12:35:15,880 [73] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Interfaces.ExtensionsHelper [(null)] - Shipment Notification processing started for PZ-457/12/22/D2022-12-21 12:35:15,880 [73] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Interfaces.ExtensionsHelper [(null)] - EXECUTE [Kotrak].[ExecuteShipmentNotificationDHC3] \\\'XL Integrator 1.0\\\',12600421,1489,26087342022-12-21 12:35:15,927 [73] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Interfaces.ExtensionsHelper [(null)] - Shipment Notification processing finished for PZ-457/12/22/D2022-12-21 12:35:15,927 [73] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GeneratePurchaseOrderReceipt [(null)] - Extension for document completed - PZ-457/12/22/D [Firma:246785 - TYP:1489/NUMER:12600421/LP:0] Evolution.ErpIntegrator.Extensions.MYShipmentNoticeUpdate.MYShipmentNoticeUpdate2022-12-21 12:35:15,927 [73] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GeneratePurchaseOrderReceipt [(null)] - Extension for document started - PZ-457/12/22/D [Firma:246785 - TYP:1489/NUMER:12600421/LP:0] Evolution.ErpIntegrator.Extensions.PLAdvanceLogger.PLAdvanceLogerExtension2022-12-21 12:35:15,927 [73] DEBUG Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GeneratePurchaseOrderReceipt [(null)] - Extension for document completed - PZ-457/12/22/D [Firma:246785 - TYP:1489/NUMER:12600421/LP:0] Evolution.ErpIntegrator.Extensions.PLAdvanceLogger.PLAdvanceLogerExtension2022-12-21 12:35:16,005 [73] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2021.Transactions.XLTransaction [(null)] - XL transaction commited\', \'Comment 10: token ID - d:eJj^@U]1GGL<Q.T2klg=5---0EJ]--2022-12-21 12:35:16,005 [73] DEBUG Evolution.ErpIntegrator.DHC.DHC30.Database.DhcTransaction [(null)] - DHC transaction commit started2022-12-21 12:35:16,005 [73] DEBUG Evolution.ErpIntegrator.DHC.DHC30.Database.DhcTransaction [(null)] - DHC transaction commit finished{code}Jak puściłem ten sam ponownie przeszło:EXECUTE [Kotrak].[ExecuteShipmentNotificationDHC3] \\\'XL Integrator 1.0\\\',12600421,1489,2608734""\', ""Comment 11: \'Hello"", ""Comment 12: I confirm new cases for no status change to executed.RCA will be required for analysis - please confirm to create.\'"", ""Comment 13: \'i confirm"", ""Comment 14: you can create RCA task.\'"", ""Comment 15: \'We confirm create RCA.\'"", ""Comment 16: \'RCA has been created DGS-8153. \'"", ""Comment 17: \'Thanks"", ""Comment 18: this task you can close.\']""]\nRelated Issues:\n[\'DGS-8153\']\n\n### End'}"