search

meridianww / M4PLBase

0 stars 1 forks source link

NAV SO/PO Creation Not Including Dimensions: Division and DC Location #404

Open nmfujimoto opened 3 years ago

nmfujimoto commented 3 years ago

Electrolux orders in production and AWC orders in development are not populating the NAV environments for the Division and DC Location dimensions.

Please confirm the mapping is correct.

prashantaggarwal1999 commented 3 years ago

@nmfujimoto if the location is TSPANDSC then Dimension code should be DISTCTR as per below json correct?

{ "@odata.etag": "W/\"JzY0O1hRRUFBQUo3LzBRQVNRQlRBRlFBUXdCVUFGSUFBQUFDZS85VUFGTUFVQUJCQUU0QVJBQlRBRU1BQUFBQUFBPT03OzM0MDQyMzIwOyc=\"", "Dimension_Code": "DISTCTR", "Code": "TSPANDSC", "Name": "TSP DELIVERY ANDREWS,SC", "Dimension_Value_Type": "Standard", "Totaling": "", "Blocked": false, "Map_to_IC_Dimension_Value_Code": "", "Consolidation_Code": "", "ERP_ID": "V-80000" }

prashantaggarwal1999 commented 3 years ago

@nmfujimoto There is an issue on development NAV for Divison code where ERPId of the customer is not properly coming under the response. Please check the below files, it's fine on production but on dev we have an issue: Dev_DimensionValues.txt Prod_DimensionValues.txt

prashantaggarwal1999 commented 3 years ago

@nmfujimoto Dimension code was having a code issue where logic was wrong to get this value, corrected the logic and committed. We can discuss this in our meeting.

nmfujimoto commented 3 years ago

@prashantaggarwal1999 In the example that you provided, the DC Location Code dimension is "TSPANDSC" and the Division dimension is determined by the customer (Electrolux is "50" and AWC is "44".

{ "@odata.etag": "W/"JzY0O1hRRUFBQUo3LzBRQVNRQlRBRlFBUXdCVUFGSUFBQUFDZS85VUFGTUFVQUJCQUU0QVJBQlRBRU1BQUFBQUFBPT03OzM0MDQyMzIwOyc="", "Dimension_Code": "DISTCTR", "Code": "TSPANDSC", "Name": "TSP DELIVERY ANDREWS,SC", "Dimension_Value_Type": "Standard", "Totaling": "", "Blocked": false, "Map_to_IC_Dimension_Value_Code": "", "Consolidation_Code": "", "ERP_ID": "V-80000" }