Not a Valid Location.

  • Not a Valid Location.

    Posted by DSC Communities on July 25, 2018 at 4:50 pm
    • Anna Mortimer

      Member

      July 25, 2018 at 4:50 PM

      ?We are using AX 2012 R3 CU9. I am trying to move inventory from one location to another and I get the following message.

      This location does not require license plates. We were able to move from that location the day before and now we can not. It is only for that location. On other locationsĀ I can make the move just fine.Ā  I can notĀ adjust inventory into or out of this bin. I can put away and pick inventory from this binĀ without any problems. Ā Does any one know what would cause this or how to fix it?

      Thank you

      ——————————
      Anna Mortimer
      Tactical & Survival Specialities Inc
      Harrisonburg VA
      ——————————

    • Guy Terry

      Member

      July 25, 2018 at 5:46 PM

      I will put £1 on someone having created a License plate with the same name as the Location.

      Check in the License plates form (Warehouse management -> Setup -> Warehouse setup) if that ‘location’ exists there.

      ——————————
      Guy Terry
      Application Consultant
      Annata
      Portsmouth
      ——————————
      ——————————————-

    • Mike Medendorp

      Member

      July 26, 2018 at 8:24 AM

      I’d agree with Guy… This has happened enough times for us, so we added some extra validation.

      On the Insert method of the WHSLicensePlate table, we added the following, so that we prevent that from happening: (for Locations, and for ProdId’s.)

      select firstOnly RecId from wmsLocation
      where wmsLocation.wMSLocationId == this.LicensePlateId;

      if (wmsLocation)
      {
      throw error(strFmt(“License plate %1 is already a Location”, this.LicensePlateId));
      }
      // End Mod

      // Begin Mod – MPM – 5/1/17 – HD# 7571 – Stop Production Order #’s as License Plates
      select firstOnly RecId from prodTable
      where prodTable.prodId == this.LicensePlateId;

      if (prodTable)
      {
      throw error(strFmt(“License plate %1 is already a Production order”, this.LicensePlateId));
      }
      // End Mod

      ——————————
      Mike Medendorp
      AX Systems Specialist
      Bell’s Brewery Inc.
      Galesburg MI
      ——————————
      ——————————————-

    • Anna Mortimer

      Member

      July 26, 2018 at 9:04 AM

      ?Thank you. You are correct. I did find a license plate that matched the location. It was entered from a production order.Ā  I will check with my IT department to see about putting in the extra validation.Ā  Is there any way to fix this location?Ā  I have tried to delete the license plate and says there are open transactions.

      ——————————
      Anna Mortimer
      Tactical & Survival Specialities Inc
      Harrisonburg VA
      ——————————
      ——————————————-

    • Guy Terry

      Member

      July 26, 2018 at 9:26 AM

      It is possible to delete an LP, but it might not be completely straight forward!

      Obviously you have to make sure there is no Physical Inventory on the LP. But probably that is not enough. I encountered this message, which sounds like what you are seeing:

      The record cannot be deleted. Open transactions exist in table On-hand inventory

      This validation comes from a method called hasOpenInventSum in Table WHSLicensePlate, which says that we cannot delete a License plate if there are any records in InventSum (that have an InventDimId which is related to the License plate) which have InventSum.Closed set to ‘No’.

      When I investigated that, I found there were records in InventSum which had no quantity, but did have a financial cost amount. In my scenario, the items were Standard Costed, and there was no way to use the Inventory close procedure to Close those records. So if your items are actual costed, you might find Inventory close will allow you to delete the LP.

      As I was able to reproduce the scenario in a Contoso environment, I logged it with Microsoft. At first, they suggested running this clean-up job, but that didn’t solve it:

      Improve performance by running the Warehouse management on-hand entries cleanup job – for New AX and for AX2012 R3 CU10

      Then they suggested the clean-up job called On-hand entries aggregation by financial dimensions. You can read about that one here:

      Key Clean up Features for InventSum and InventDim Tables

      This one did solve the problem for me. After questioning whether this clean-up job was the recommended solution to delete used LPs, I got this response:

      Yes, this is officially supported solution, since we released this as a hotfix, and it is available from the main menu in AX.

      Ā 

      It is acceptable to have these financial cost amounts on InventSum records while quantity is 0. This is just how AX is designed and is the consequence of not having all Active inventory dimensions part of financial inventory. When you look at inventory on financial inventory level (for site for example), costs should be fine. On ‘lower inventory dimensions’ like License plates, costs are however distributed over multiple transactions with different non-financial dimensions, and this may cause having these financial cost amounts on inventsum records without actual quantities.

      Ā 

      This logic may however cause performance degradation if there are huge number of InventSum records with no quantity, but with financial cost amount. And in customer’s scenario, may cause License plates to not being able to get removed. Running the Aggregation tool cleans up InventSum, which is primarily meant to improve performance, but may also allow in this case remove license plates.

      Ā 

      The tool does delete InventSum records only. This tool is created to be run periodically (recurring batch) to make sure it keeps the InventSum table cleaned up properly, as new inventory movements will create new occurences of InventSum records without quantity but with financial amount. The tool will keep things tidy.

      ——————————
      Guy Terry
      Application Consultant
      Annata
      Portsmouth
      ——————————
      ——————————————-

    • Sarah Gabriel

      Member

      July 26, 2018 at 11:51 AM

      Hi Anna,
      We have run into the same issue as well, but I was not able to find the cause. In meantime, you can post inventory movements on the full screen until the issue is resolved. I’m definitely going to review our License plate table.

      ——————————
      Sarah Gabriel
      Operations Business Analyst
      Kai USA Ltd
      Tualatin OR
      ——————————
      ——————————————-

    • Kevin McLean

      Member

      July 26, 2018 at 1:55 PM

      ?You might try using the record renaming function to rename the license plate.Ā  You would then want to reprint the license plate, find the container, and put the new license plate on it.Ā 

      As with anything this extreme, you should test in a non-production environment first.

      ——————————
      Kevin McLean
      Strategic Solutions NW, LLC
      Beaverton OR
      ——————————
      ——————————————-

    DSC Communities replied 7 years, 1 month ago 1 Member · 0 Replies
  • 0 Replies

Sorry, there were no replies found.

The discussion ‘Not a Valid Location.’ is closed to new replies.

Start of Discussion
0 of 0 replies June 2018
Now

Welcome to our new site!

Here you will find a wealth of information created for peopleĀ  that are on a mission to redefine business models with cloud techinologies, AI, automation, low code / no code applications, data, security & more to compete in the Acceleration Economy!