when importing inventory movements from the i_movement table having a time component in the movementdate field leads to a separate movement document for every movementline (instead of one document with multiple movementlines)
The reason is the movementdate is truncated when inserting into the m_movement table and then comparison i_movement.movementdate = m_movement.movementdate fails.
The attached patch solves the issue for us.
importing records to i_movement directly with time component in movementdate field
I can not run UPDATE query in test server. But i can change reference from Date to Date +Time for filed MovementDate.
Step to reproduce:
Login as Client GardenWorld
Open window Import Inventory Move
Create first record with values:
Organization: HQ
DocumentNo: 1000123
Movement Date: 09 May 2020 12:00:00 AM
Document Type: Material Movement
Business Partner: C&W Construction
Shipper: Fertilizer Internal Shipper
Product: Oak
Locator: Fertilizer
Locator To: Fertilizer Transit
Movement Quantity: 4
Run process Import Inventory Movement
Login as Client System
Open window Table and Column
Open record “I_Movement“
Open record “MovementDate” in tab Column
Change value to “Date + Time“ in field Reference and Save
Login as Client GardenWorld
Open window Import Inventory Move
Create second record with values:
Organization: HQ
DocumentNo: 1000123
Movement Date: 09 May 2020 04:02:00 PM
Document Type: Material Movement
Business Partner: C&W Construction
Shipper: Fertilizer Internal Shipper
Product: Elm
Locator: Fertilizer
Locator To: Fertilizer Transit
Movement Quantity: 2
Login as Client System
Open record “I_Movement” in window “Table and Column”
Set value “Date” in field “Reference” for record “MovementDate” and save
Login as Client GardenWorld
Open window Import Inventory Move
Run process Import Inventory Movement
Open window Inventory Move and see two documents with DocumentNo = 1000123 and equals MovementDate (9 May 2020)
reproduced by