| Table of Contents |
|---|
...
The Pull option will search for invoiced PO items, inclusive of the starting invoice date, that have beenmarked for inventory. At this point, the item is at a 'pending' status for Inventory. For a invoiced PO item to be marked for inventory, it must meet the pending threshold criteria in USAS-R. The EIS Classic Integration module must be installed and the EIS Classic Integration Configuration* set up for the pending threshold (these processes are part of the USAS -R Post Import steps).
| Note |
|---|
Third Party Software* The EIS Classic Integration Configuration setup is specific to flagging items when invoiced via USAS-R. Districts invoicing through a third party application should check with their third party to see if there is additional setup needed to flag invoice items for inventory. |
Test Connection
Prior to pulling items from USAS, the Test Connection button may be selected to notify the user whether or not they are connected to USAS. A date does not need to be entered in order to use this feature. If the connection was successful, the user will see "Successfully connected to USAS" message. If the connection failed, the user will see "Unable to connect to USAS". There will be a button available to "Show Stack Trace". This information will be needed by SSDT if a support ticket is created for assistance.
...
Click on
Enter the starting AP invoice date. It will pull any Purchase Order items marked for inventory from USAS -R into the pending file in Inventory inclusive of the starting date.
NOTE: If items are deleted from the pending items grid, a message is sent back to USAS -R stating the item was rejected. Pull from USAS will not include marked for inventory items with a status of 'rejected' by default. However, if the item needs to be pulled into Inventory again, check the "includes rejected' box to include rejected items inclusive of the starting date.
Click Confirm and the items will appear on the grid.
...
This means there were no USAS items to pull into the Inventory application. The USAS and Inventory applications are communicating. You may want to verify invoiced items that have met the pending threshold have been 'marked for inventory' in USAS with a 'pending' status.
Solution: In USAS, you may perform one of the following to check the inventory status of the invoices items marked for inventory.
Inventory Pending Items Report Definition
SSDT Inventory Pending Items report definition may be downloaded and then imported into the USAS -R Report Manager. You have the option of entering a starting invoice date. It will generate an Excel formatted spreadsheet containing invoiced items inclusive of the starting date that have been marked for inventory, along with their current inventory status. Please refer to the 'Communication between USAS and Inventory' note above for more details on the various inventory statuses.
...
AP Invoice Advanced Query
Please refer to the screenshot below on how to perform an advanced query to determine if there are invoiced items currently marked for inventory in USAS-R. If it doesn't return any results, please ensure the EIS Classic Integration module has been installed and the EIS Classic Integration Configuration has been set up for the pending threshold (these processes are part of the USAS -R Post Import steps). Any invoiced items that did not get marked for inventory will need to be added manually as an item via Transactions>Items or mass-added via System>Import.
...
The above error means you have a configuration problem.
Solution: ITC should review your ssdt-inventory-app.properties file to ensure you have the correct values for usasHost and usasPort (443).
The above error means you have an api key problem:
Solution: ITC should review the usas docker-compose.override.yml api key definitions. The override file cannot contain quotes around the api value like you see in the inventory properties files. If you do in fact have quotes around the api key you'll need to remove those. Once this configuration change is made the docker-compose up -d command will need to be executed for this change to take effect.
The above error means you may have a possible nginx problem.
Solution: ITC will need to assist. If you are using nginx please review your ssdt-inventory-app.properties file to ensure you have nginx configured properly. Verify the values for virtualHost and virtualPort.
...