Uploading A Bin Setup
Tip: This process should only be done with the acknowledgement and assistance of a Senior Technical Analyst.
Once data has been received from a customer, it must be checked to make sure it conforms to the requirements of the Bin Setup Tool. If any of the data is invalid or unsuitable when uploaded, it will have serious consequences and compromise the customer's data integrity.

-
Start with a blank Bin Setup Tool Microsoft Excel template.
It is not recommended to reuse the same spreadsheet from customer to customer as they may be lingering formulas or changes made to the macro record that will conflict with the upload.
If you are not sure, check with a Senior Technical Analyst to confirm that you are using the most recent template.
-
The Bin Setup Tool spreadsheet includes column headings indicating the data that is needed.
Make sure the data meets the requirements as specified.
-
Once all final verification checks are complete, the upload can be done.

There are several essential checks that must be done to make sure the data is suitable:
-
Check all entries for any special characters in columns where they should not be or are not allowed.
For example, a positive integer cannot include symbols such as !@#$%^
-
Copy and paste values over the data to confirm that there are no formulas present.
For example, VLOOKUPS are used for verification.
Do not worry about columns from 'O' onwards as these formulas are required.
-
Delete the blank data rows at the bottom.
Use Ctrl+Shift+End to confirm the true end of the spreadsheet.
-
Make sure the formulas from columns 'O' to 'Q' are present on each row of data.
Copy to the bottom if necessary.
-
If the upload is appending data to existing records, first log in to the customer's system to verify that what data is there is correct.
For example, if you are appending Pick Sequence values to a list of bin locations that are already there, you will need to check that the rest of the data matches. If it does not match, you will potentially overwrite the customer's data instead of appending to it. Use a VLOOKUP formula to check that each field matches between what you have and what you are adding to.
-
Check the number of records in the sheet.
The macro record (press the Alt+F11 keys) indicates the cell range that will be uploaded.
If your data extends beyond row 3590, you will need to adjust this range.
-
Also in the macro record, check the URL of the SET statement.
In the above example, the upload is for a customer in the B-cluster. Change this character to a C or D if the customer is in one of those clusters. Customers in A cluster will need the URL to point to
http://a-prod.dotwms.com.au/.........

Once the above checks have been completed, the spreadsheet needs to be updated to the demo warehouse.
-
Set the Instance Code to DEMO
-
Find the relevant API key:
-
Log into the .wms DEMO system.
-
Go to Settings > System Parameters.
-
In the Search field, enter API.
If you are unsure which API to use, ask a Senior Technical Analyst.
-
-
Click Run Upload to test.
If any errors are returned, go through the verification checks again.
If you cannot pinpoint the issue, ask a Senior Technical Analyst.

Once the test upload has been successfully completed, the spreadsheet can be changed to include the Instance Code and API key for the customer.
-
The Instance Code is required and will need to be retrieved from the database.
-
Locate the customer page in Confluence and find the .wms InstanceID from the Core Data section.
-
In the database run a query to find the InstanceCode by using the InstanceID.
Use INS Table > Search > InstanceID = xxx
-
Copy the result to the spreadsheet.
-
-
Retrieve the API key for the customer.
-
Click Run Upload.
If any errors are returned, go through the verification checks again.
If you cannot pinpoint the issue, ask a Senior Technical Analyst.

-
Log in to the customer's .wms.
-
Go to Settings > Bin Locations.
-
Confirm that the data has uploaded accurately.