AMS Setup - Revision history

Freddy at 16:40, 25 July 2025

2025-07-25T16:40:15Z

Jared at 18:08, 28 August 2023

2023-08-28T18:08:08Z

Tcampbell: /* Item Attributes */

2023-01-20T14:22:54Z

‎Item Attributes

Ryan: /* Item Attributes */

2021-12-08T20:32:51Z

‎Item Attributes

Curtis: /* Initial Set Up */

2020-09-04T12:33:04Z

‎Initial Set Up

Freddy at 19:13, 2 September 2020

2020-09-02T19:13:21Z

Freddy at 19:07, 2 September 2020

2020-09-02T19:07:06Z

Freddy at 19:05, 2 September 2020

2020-09-02T19:05:57Z

Freddy at 18:57, 2 September 2020

2020-09-02T18:57:47Z

Freddy at 18:56, 2 September 2020

2020-09-02T18:56:42Z

@@ Line 177: / Line 177: @@
-[[Category: Help]]
+[[Category:Production]]
-[[Category: Internal]]
+[[Category:Integrations]]
 [[Category: Setup Guides]]

@@ Line 118: / Line 118: @@
 * AMSPRODSQL (REQ) - enables SQL transfer for production information.
 * AMSORDERSQL (REQ) - enables SQL transfer for sending orders.
-* AMSSQLLEN (REQ) -
+* AMSSQLLEN (REQ) - sends items to the machine based on bundle# and length (longest to shortest)
 * AMSCTAG - will print bundle tags for bundles created when they are sent to AMS. This will use the AMSPRINTER rule set up previously to determine which printer is used.
 * AMSLABEL -

@@ Line 41: / Line 41: @@
 For Adjutant to recognize and push an item out to Eclipse, it needs to have the proper item attribute (Attribute name "AMS" with form "AMSPROD" in the Item Attribute Rule).
-[[File:AMS Wiki AMS Item Attribute Set Up.png]]
+[[image:amsrule.png]]
 The AMS Product Attribute jump screen has three fields. These fields will need to line up with the Eclipse data exactly. The preferred scenario is that the customer sets up their Eclipse items with the same names as their item codes in Adjutant. That makes for an easy data import. This information can be filled out using an Excel import (download here) and shows data from the AMSXREF table.

← Older revision		Revision as of 20:32, 8 December 2021
Line 55:		Line 55:

	[[File:AMS Wiki AMS Attribute Jump Screen.png]]		[[File:AMS Wiki AMS Attribute Jump Screen.png]]
−

	===Rule Setup===		===Rule Setup===

@@ Line 15: / Line 15: @@
 ==Initial Set Up==
-There are a number of things that can and should be set up before you are ready to "flip the switch". The Database Set Up section, the Item Attributes section, and the Rule Setup sections should all be completed before working with Eclipse for the integration. Once you are ready to "flip the switch", you will complete the Eclipse Setup section, then the Setup Options section, then the Coil Table Population section, then the Ready to Test section.
+There are a number of things that can and should be set up before you are ready to "flip the switch". The Database Set Up section, the Item Attributes section, and the Rule Setup sections should all be completed before working with Eclipse for the integration.
@@ Line 80: / Line 82: @@
 [[File:AMS_Wiki_Rule_Scrap.png]]
 ==Eclipse Setup==

@@ Line 126: / Line 126: @@
 * AMSSKIPBUNDLE - will skip the bundle process during the S2P. Orders will be manually bundles using the scanner.
 * AMSSCRAP - will enable the AMS Scrapping process. This will need the AMSSCRAP rule set up previously.
 ==Coil Table Population==
-Before you begin testing, you will need to run the Purge and Reload Controller Coils process in order to populate the AMS stock table with the current inventory. This will take all the open coils for the selected warehouse, remove and re-add them so they can be processed into the AMS_Stock_WhseName table. For most customers, this should not take more than 10 minutes or less, but it should be run outside of business hours because it does lock the itemtrack table.
+Before you begin testing, you will need to run the Purge and Reload Controller Coils process in order to populate the AMS stock table with the current inventory. This will take all the open coils for the selected warehouse, remove and re-add them so they can be processed into the AMS_Stock_WhseName table. For most customers, this should take 10 minutes or less, but it should be run outside of business hours because it does lock the itemtrack table.
 Once completed, run "Select * From ams_stock_WhseName" to verify that the coils are in.
 [[File:AMS Wiki Purge Coil.png]]
 ==Ready to Test==
-Once Eclipse is ready and connected, flipping on the setup options and running the AdjAmsProcess will make the integration Live.
+Once Eclipse is ready and connected, flipping on the setup options and running the AdjAmsProcess will make the integration live.
 AdjAMSProcess.exe is the process used to push data back and forth. Make sure you have the latest version from the FTP folder. Run it in a local session to test for errors.
-The best way to test is to take an order with an item having the Adj AMS attribute and send it to production. The line should appear in theamsorder table (select top 100 * from amsorder). The amsorder.datesent field should get filled out as the AMS process pushes it to the Eclipse database table, ams_orderin. Once it processes from there, have your customer verify they can see it in Eclipse.
+The best way to test is to take an order with an item having the Adj AMS attribute and send it to production. The line should appear in the amsorder table (select top 100 * from amsorder). The amsorder.datesent field should get filled out as the AMS process pushes it to the Eclipse database table, ams_orderin. Once it processes from there, have your customer verify they can see it in Eclipse.
 When coil is scanned from the Eclipse/AMS machine, it should verify from the Adjutant coil tag.
-Tracking return usage is more difficult since this can only be done as the machine actually does the production. With your customer, settle on an order being run and track it through in the amsproduct table. If it shows in there, verify the PWO has usage assigned and is completed. The amsproduct table should have the coil that was scanned in the amsproduct.coilmat field. If you find "NO COIL MATCH", it was not able to find the coil.
+Tracking return usage is more difficult since this can only be done as the machine actually does the production. With your customer, settle on an order being run and track it through in the amsproduct table. If it shows in that table, verify the PWO has usage assigned and is completed. The amsproduct table should have the coil that was scanned in the amsproduct.coilmat field. If you find "NO COIL MATCH", it was not able to find the coil.
 If nothing is coming back, turn off the services, and go back to the start to make sure the right set up options and tables are matched correctly.
 Once you are confident that everything is set up correctly, send an email to support to set up AdjAMSProcess as a service if they are hosted. Otherwise, set up AdjAMSProcess in the customers' Service + in their system.
 ==Troubleshooting==
 Q: What if the customer says they completed the job in AMS but a carton tag didn’t print?
-A:  Look at the amsproduct table where orderno= the SO#.  When the bundle # changes a tag should have been printer.  Look at procdate and compare that to labelmast for that same time.
+A:  Look at the amsproduct table where orderno= the SO#.  When the bundle # changes a tag should have been printed.  Look at procdate and compare that to labelmast for that same time.
 Q: What if the SQL tables are connected but Eclipse is not able to find the coil, even though it's in the table?
@@ Line 166: / Line 169: @@
 If they are "F", change them to a "T" and save.
 ==Helpful Contacts==

← Older revision		Revision as of 19:07, 2 September 2020
Line 87:		Line 87:

	Step 1: Find the Eclipse folder installed on the C Drive. This is a centralized folder that has all the root files for Eclipse, similar to the Adjutant folder for our customers. Open the SQL Setup File. It is always helpful to Run as Admin if possible. Important note - this program cannot be opened while Eclipse is running. You need to shut it down before this will open.		Step 1: Find the Eclipse folder installed on the C Drive. This is a centralized folder that has all the root files for Eclipse, similar to the Adjutant folder for our customers. Open the SQL Setup File. It is always helpful to Run as Admin if possible. Important note - this program cannot be opened while Eclipse is running. You need to shut it down before this will open.
−

	Step 2: Establish an ODBC connection. On the Import(1) tab there is a button that says "ODBC" which will launch the standard ODBC screen we use to connect for scanners. The connection will be mostly the same as if setting up the scanners, except SQL Native Client 9 will not work. You can just use the SQL Server connection on the System DSN "Add"button. From there, the set up is exactly the same as if installing scanners. See steps 13-20 [http://www.abiscorp.com/faq/index.php?title=Install_Desktop HERE] if you need a refresher.		Step 2: Establish an ODBC connection. On the Import(1) tab there is a button that says "ODBC" which will launch the standard ODBC screen we use to connect for scanners. The connection will be mostly the same as if setting up the scanners, except SQL Native Client 9 will not work. You can just use the SQL Server connection on the System DSN "Add"button. From there, the set up is exactly the same as if installing scanners. See steps 13-20 [http://www.abiscorp.com/faq/index.php?title=Install_Desktop HERE] if you need a refresher.

@@ Line 69: / Line 69: @@
 '''AMS Printer Rule (AMSPRINTER) - Optional - '''
-This rule will allows you to set the printers per machine per location to print bundle and carton tags. There are certain set up options (see below) that are needed to print labels from the machine based on bundling done during the S2P process.
+This rule will allow you to set the printers per machine per location to print bundle and carton tags. There are certain set up options (see below) that are needed to print labels from the machine based on bundling done during the S2P process.
-The machine name (Text 1) should match the profile machine rule exactly for it to work. The UNC Name for the printer (Text 2) should match the UNC name for the printer in Printer Control exactly. This will be paired with the Loctid (num 1) to allow you to print to machines in multiple warehouses.
+The machine name (Text 1) must match the profile machine rule exactly for it to work. The UNC Name for the printer (Text 2) must match the UNC name for the printer in Printer Control exactly. This will be paired with the Loctid (num 1) to allow you to print to machines in multiple warehouses.
 [[File:AMS Wiki Rule AMS Printer.png]]
@@ Line 77: / Line 77: @@
 '''AMS Scrap Rule (AMSSCRAPXREF) - Optional - '''
-This rule will allows you to match scrap codes sent back from AMS to different item codes. This is useful if you wanted to direct various kinds of scrap into different expense accounts. Text 1 will be the numeric Scrap Code received from AMS. Text 2 is the Item Code that it will go against. It is possible that these AMS codes are dynamic and can change. You will need to work with AMS and with your customer to make sure they are correct and are being used.
+This rule will allow you to match scrap codes sent back from AMS to different item codes. This is useful if you wanted to direct various kinds of scrap into different expense accounts. Text 1 will be the numeric Scrap Code received from AMS. Text 2 is the Item Code that it will go against. It is possible that these AMS codes are dynamic and can change. You will need to work with AMS and with your customer to make sure they are correct and are being used.
 [[File:AMS_Wiki_Rule_Scrap.png]]
@@ Line 84: / Line 84: @@
 ==Eclipse Setup==
-This section will describe everything that needs to take place on the Eclipse side. Your customer will need to grant you some screen share access to the computer on which Eclipse is installed.
+This section will describe everything that needs to take place on the Eclipse side. Your customer will need to grant you some form of screen share access to the computer on which Eclipse is installed.
 Step 1: Find the Eclipse folder installed on the C Drive. This is a centralized folder that has all the root files for Eclipse, similar to the Adjutant folder for our customers. Open the SQL Setup File. It is always helpful to Run as Admin if possible. Important note - this program cannot be opened while Eclipse is running. You need to shut it down before this will open.
-Step 2: Establish an ODBC connection. On the Import(1) tab there is a button that says "ODBC" which will launch the standard ODBC screen we use to connect for scanners. The connection will be mostly the same as if setting up the scanners, except SQL Native Client 9 will not work. You can just use the SQL Server connection on the System DSN "Add"button. From there the set up is exactly the same as if installing scanners. See steps 13-20 [http://www.abiscorp.com/faq/index.php?title=Install_Desktop HERE] if you need a refresher.
+Step 2: Establish an ODBC connection. On the Import(1) tab there is a button that says "ODBC" which will launch the standard ODBC screen we use to connect for scanners. The connection will be mostly the same as if setting up the scanners, except SQL Native Client 9 will not work. You can just use the SQL Server connection on the System DSN "Add"button. From there, the set up is exactly the same as if installing scanners. See steps 13-20 [http://www.abiscorp.com/faq/index.php?title=Install_Desktop HERE] if you need a refresher.
 Step 3: Each tab, except for tab (3) has sources that need to be matched up to our new tables. Important note - the "Tables" drop down is NOT in alphabetical order. You have to find the tables exactly as they are shown in the screenshot (ex. "ams_orderin"). There are other tables that look similar to this but are not correct. To begin the match up, follow these steps:
@@ Line 100: / Line 100: @@
 [[File:AMS Wiki Eclipse t1.png|500px]]
-Step 4: Rinse and repeat the steps above for tab Export Local (2) and Verify Coil (4). On the Verify Coil tab, you will select the AMS_Stock_WhseName table to use, and make sure that "Verify Coil data from SQL Server Tables" is checked.
+Step 4: Repeat the steps above for tab Export Local (2) and Verify Coil (4). On the Verify Coil tab, you will select the AMS_Stock_WhseName table to use, and make sure that "Verify Coil data from SQL Server Tables" is checked.
 [[File:AMS Wiki Eclipse t2.png|500px]]

@@ Line 62: / Line 62: @@
 This rule will determine the various processes that are used. These entries are warehouse specific, so if setting up for multiple warehouses, should include each entry shown below ''per each warehouse''. Important note: The Loctid (num 1) is the Warehouse Key number.
-Everything else should be set up as seen in the image, paying special attention to which is an import or export process (Log 1 and Log 2 respectively).
+Everything else should be set up as shown in the image, paying special attention to which is an import or export process (Log 1 and Log 2 respectively).
 [[File:AMS Wiki Rule AMS Process.png]]