How to use the Bedrock Inventory Location Change Database

Note: the database can be found here.

Usage

This database is to be used as a change request system: users submit requests (database records) for locations to be created, or for changes to be made to pre-existing locations, in Dynamics AX.

Each record is simply a request for changes to be made, and should not be modified after they are entered.

Step 1. Initial Request

Typically performed by the warehouse user who created the location in AX, this informs the BAs and Planning team that a location was added, and provides unverified details about that location.

  1. First, navigate to the change request form here.
  2. Fill in each field accordingly:
    • Requestor — Your name.
    • Change type — To the best of your knowledge, whether this is a New location, or a Revision to an existing location.
    • Location Name — The name of the location as it should exist (or already exists) in AX.
    • Reason for Change — Why the requested change is being made.
    • Company — Which entity this location applies to.
    • Notes — Any other notes you feel important to pass on to the Business Analysts or Planning team.
    • [Shinola Only] Include for Magento/ATS — If this location should be marked as Included or Excluded in AX.
    • [Filson Only] Inventory Status — Whether this location should be marked as Available or Not Available in AX.
  3. Click the Save & Done button.

Step 2. Planning Verification

At this point, Planning is made aware of the location, and can log in to submit another request to verify the details of the new location.

  1. Navigate to the change request form here.
  2. Fill in each field accordingly:
    • Requestor — Your name.
    • Change type — To the best of your knowledge, whether this is a New location, or a Revision to an existing location.
    • Location Name — The name of the location as it was specified in the initial request, or as shown in Dynamics AX.
    • Reason for Change — Why the requested change is being made.
    • Company — Which entity this location applies to.
    • Notes — Any other notes you feel important to pass on to the Business Analysts or Planning team.
    • [Shinola Only] Include for Magento/ATS — If this location should be marked as Included or Excluded in AX.
    • [Filson Only] Inventory Status — Whether this location should be marked as Available or Not Available in AX.
  3. Click the Save & Done button.

Step 3. Business Analyst Action

At this point, the BAs should have the information needed to make the necessary updates to locations, and can proceed doing so.

Once the updates have been completed, that’s it—no further action needs to be taken.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

Please sign in to leave a comment.