AR74 - Running report by sales agent, product group and item. Only agent prints.
Agility
- Data Warehouse
AR83 - What is the difference between new average and average cost in viewer?
Agility
- Viewers
AR96 - New winXP machine can't run Cqcs reports vcq host cannot be run directly
Agility
- Cyberquery
AR101 - Sales Order Status and Sales Order Viewer showing different values
Agility
- Sales Orders
AR114 - How can the user mass update laser control records?
Agility
- Customer
How can the user mass update laser control records
Question: How is a user able to mass update various laser control records in Agility?
Option 1)
If you are on v535 or higher, you are now able to Create, Delete, and Update Laser Controls through the Customer Import. We have added this to Default Definition Layout for Sold To, Ship To, and Bill To records through Data Files > Customer Information > Customer Import.
Default Definition Layout > what to select for Laser Control export:
What to fill out in import:
Option 2)
If you are on v534 or lower, the user will need to go into System Administration > Mass Update > Laser Controls Update. Once the program has been selected, the Update for Laser Control Records program window will appear. The user has the option of overwriting laser control records for Customer Sold-To/Bill-To/Ship-To/Branch Ship-To, Supplier Ship-From and Carrier records.
NOTE: RUNNING THIS PROGRAM WILL OVERWRITE LASER CONTROL RECORDS, NOT APPEND TO EXISTING RECORDS!
The user will select the specific form type to overwrite and then specify the valid range for the form type selected. The user can choose a specific range or select All records within the range.
The user will then specify each laser printer, number of quantities, and any form footer for the specified laser printer. The user can also determine which Primary Contact (Sold-To, Bill-To, Ship-To) to designate. If the user chooses FAX from the available list of laser printers, the Use Default Fax # to Populate Laser Controls box is automatically checked. If you uncheck the box or if no default fax number exists on the master record, no fax number will be populated in the laser control record.
Once all settings have been selected, the user will click Update and the program will update the specified laser control records.
Laser Controls Update window you would need to fill out:
AR140 - CONTROL-FRAME errors when trying to print forms or access print scr - ocx
Agility
- Forms
AR151 - How to Subtotal an SO Viewer
Agility
- Viewers
AR275 - Find Items where Standard Pricing is Not Setup
Agility
- Pricing
Items that Don’t Have Standard Pricing Setup
Would like to find all the items where standard pricing is not setup.
Use the Pricing Report. Go to Sales Orders/Quotes > Queries/Reports > Pricing Report
(1) Select Standard Pricing
(2) Run for All Sales Types
(3) Input Item Range for All Items
̵ Use blank spaces followed by a number for the Start item and ZZZZZZZZZ for the End item
(4) Uncheck the option to Only Include Items with Prices or Discounts
Run the Viewer and select the Price column to sort by prices. Items with zero pricing would not have Standard Price records setup.
AR307 - How does the Loftware automated process work for labels?
Agility
- Data Files
New AP client is available with v440 Agility. This is version 6.0.0.0 of the AP client and includes the necessary pieces for the transferring the Loftware label files from one place to another. With this change, there are essentially 2 services that can be installed. They can be installed together or individually. Because of the combined installation option, there are some installation process changes to gather further information. See below. AP File Transfer client configuration file contains a set of tags that is pretty much identical to the AP Queue client. In fact, most of the entries are duplicated from the original install. However, the ?dequeue? tag for the File Transfer service indicates how often the client should go out to move files from the location the appserver placed them (connect.xml tag) and where the user told the client to transfer them to (input during installation of the client and saved to ?FileSavePath? tag in configuration.xml). The value entered in the ?FileSavePath? should be the final location where Loftware is looking for it to pull in for processing. In the installation, there are 2 sets of inputs for user/password for the File Transfer service. This first is for the user that will be running the File Transfer service via the API and it will be logging into Agility. It is assumed/expected that the user id will be the same as that used to run the normal AP processing for queues. The second user name and password is to be filled in if you will be accessing a remote share directory when accessing/moving files. This user should have all the necessary permissions to the directors where the files are being placed or transferred to. These fields are NOT saved in the Configuration.xml file. Instead they are saved inside the properties of the client as the LogOn information. The user name must be in the format ?domain\user?. New tags are available for connect.xml in v440. They are: Loftware and Loftware_Appserver. These are NOT automatically added into connect.xml. When the customer wants this, tech will need to add the appropriate tag to the connect.xml file based on whether the customer is using Windows (Loftware) or Unix servers (Loftware_Appserver). This tag will indicate to the appserver where to store the PAS files generated for labels generated and is used when the File Transfer service needs to know where to pick up the label files from during the transfer. This location is ONLY used when generating pick files from Automated Processing because we needed files to be placed in a spot that the appserver could find them. The current label processing inside Agility does NOT run on the appserver. We did not want to force the change to the appserver from inside Agility. If the tag is missing from the connect.xml file or is there, but is blank, labels will be placed in/pulled from the ?startin? directory + \labels. If the \labels subdirectory does not exist, it will be created. (Either process ? generating labels or picking up labels for transfer ? can create that directory.) This will ensure that labels continue to be generated and printed even with the connect.xml does not have the appropriate information. Under these condition, an appserver error log entry will be created to alert users to the fact that the connect.xml is missing information for this process. **If the connect.xml is updated after labels are generated, but before they are picked up, there could be a mismatch of locations which would cause labels to not print. This should be a very rare situation, but could occur. There is no new setup inside Agility for this process. Labels run through this process when they are setup to be run through Automated Processing (ie, run on the appserver). **It is important to note the label process when not running through automated processing, like expediting a pick, it still being run through the old method, which automatically places the .PAS file in the correct loftware directory immediately. Labels files are generated 1 per pick file; this is existing functionality. If the label file is larger than the BLOB file allows, the process will break the files up into multiple files, transfer the files and then combine them again into 1 large file for Loftware to process.
AR323 - How to View Purchasing or cost data for expense PO's
Agility
- Purchasing
AR361 - Unable to Complete Work Orders Due to Default Location Error
Agility
- Work Orders
AR431 - Receiving error of "Sales Order in process by another user."
Agility
- Sales Orders
Receiving error of “Sales Order is in process by another user” This occurs when an order is in process and cannot be accessed. To be able to access the order, the status must be changed so that it can be cancelled or shipped.
Follow the steps below to remove the sales order:
1. In Agility, verify you are logged into the same branch in which the sales order exists
2. Access System Administration > Performance Tuning > In Process/Locked Orders
3. Select a Record Type of In Process Orders and select the Search button
4. Highlight the order in question and select the Delete button
5. The order should now be removed from Agility as if it were never entered
Note: If you wish to keep the order, the user listed in the error message can display the order and save it. If that user isn't available (no longer works at company, etc.), reset the user's password in User Profiles and then log into Agility as that user to access & save the order.
AR436 - Aged trial balance run for a prior date still including current invoices
Agility
- A/R
AR441 - Incorrect A/R Write Off - How to add the balance back or reverse write off?
Agility
- A/R
AR460 - Pricing Records from Template Master Quote Error message says the items were created from a
Agility
- Quotes
AR464 - Can You copy the quick access toolbar to multiple users.
Agility
- System Administration
Can you copy the Quick Access Toolbar to multiple users You can copy Custom Ribbon tab, Dashboard, Favorites, Quick Access Toolbar, Saved Viewers, Shortcut Keys and User Preferences via the same mass update program.
1. Go to System Administration > Mass Updates > Copy User Customizations
2. Select the user profile that you would like to copy in the “Copy From” field
3. Select “Quick Access Toolbar” from the “Copy type” drop down list
4. Select the “Object to copy” – Main Menu or SO Entry
5. Use the “Add >>” button to move user to the “Copy to user” side for those users that you want to have the Quick Access Toolbar.
6. Click Copy button and then close.
Be sure that the “copy to” users are logged out of Agility during the copying process.
AR491 - Item showing On Order but there are no Open Purchase Orders for the Item
Agility
- System Administration
ITEM SHOWING ON ORDER WHEN THERE ARE NO OPEN PURCHASE ORDERS FOR THE ITEM We have an item that is showing material on order, but we don’t have anything on order.
You will need to run a support program called rebldonord.
Go to System Administration > Restricted Processing > Support Programs
Using the drop down to ‘Select Program’ select support program rebldonord. The drop down will support jumping to selection using your keyboard input. To quickly jump to the correct section for this program, click the r key on your keyboard.
Move the program under Selected Programs using the right arrow. Then select Run.
Select Yes on the prompt “Are you sure you want to perform the selected support programs?”
Input the Branch and Item or Item range. Then select Update.
Select Yes to run the report, No to produce an Audit Report, or Cancel to abort.
You will get a prompt to check the logfile and a location of the logfile generated, which can be found in the U:/prod folder.
After running this support program, you may still notice that stock status is not reflecting correctly. If that is the case, please also try to run support program updqtyttls for the item. Also, check out our help documentation (under the Item Quantity sub-heading) if you have any questions about either of these support programs.
AR495 - Unable to release detail group from quote to a SO due to inactive item warning mesage
Agility
- Quotes
AR521 - Cyberquery reports not running after upgrade
Agility
- Cyberquery
You are trying to run saved CQ reports, but get an error stating the reports are compiled using an old version. Anytime you install a new version of Agility, you will need to recompile the reports.
The images associated with this article are contained in a separate Word document attached to this article.
1. Go to Report Writer > VCQ Report Compiler (Image 1).
2. Here (Image 2), you can compile a single report or all reports at once.
If you know the report name, but not where it is stored, click “Include sub-directories in compile.”
Click Run.
*** DMSi recommends that you DO NOT select “All.” This will compile every CQ report, including each pass on multipass reports. ***
3. The compile process launches a CQ window, detailing the results of the compile process.
If the pop-up report contains the line, “Enquiry [report name] is compiled – no errors,” then everything is fine, and your report is ready for use (Image 3).
If the pop-up report does not include the report name and specify that it’s compiled (Image 4), make sure you’ve spelled the report name correctly, and check “Include sub-directories…,” if you haven’t already. Run the compiler again.
4. If you are still not able to compile the report, please contact DMSi Support.
AR532 - Error Message when trying to export to excel
Agility
- System Administration
AR540 - How to include customers in export to PreLien2Lien
Agility
- A/R
AR571 - Fatal Error - E111:001 Application not Found
Agility
- System Administration
AR666 - What does it mean when an item showing as being on a pending PO? (LP status)
Agility
- Purchasing
AR677 - Agility Mobile Sales app - Why will customers not show in the Agility Mobile Sales app?
Agility
- Agility Mobile Sales
Agility Mobile Sales app - Why will customers not show in the Agility Mobile Sales app? Issue: I am not able to locate any customers in the Agility Mobile Sales App
Solution: In order for a customer to show in the Agility Mobile Sales app, the customer ship to record must have keywords built, the customer locator in the Agility Mobile Sales app is solely dependent on all information you would use to locate the customer ship-to record being contained in the ship to's customer keyword field.
If your customer records do not have any customer keywords built for them, you will need to configure what information you want to build into customer keywords in the System Configuration Settings found in System Administration > System Configuration > System Config on the Misc Settings Tab.
To build the keywords for existing customer ship to records once you configure what information you want to include in keywords, you will need to run the custkeyword support program to build the customer keyword field on all existing ship to records.
System Administration > Restricted Processing > Support Programs
Update which fields the system uses to assign values to Keywords field on the customer ship-to record based on the pre-defined fields selected in System Configuration Settings.
Running this program does not affect the values in the User-defined keywords field on the customer ship-to record.
AR683 - Error Message: CQ compiler license not available.
Agility
- Cyberquery
AR685 - Error Message: Invalid query name in keypath.
Agility
- Cyberquery
AR696 - Branch Transfer Error "Shipment criteria update is complete. No shipments were created.
Agility
- Branch Transfers
AR736 - User cannot open SO from dashboard or menu - task appears to be in focus in window but canno
Agility
- Sales Orders
AR739 - Item Activity Viewer not showing orders when run by supplier
Agility
- Viewers
AR741 - Error message that order must have pick printed before printing the delivery ticket
Agility
- Sales Orders
AR744 - Question on Market Cost vs. Current Market Cost Column
Agility
- Viewers
AR795 - How to resolve a printer not valid for branch error (local host)
Agility
- Printing
AR797 - How to update customer credit check for all customers
Agility
- Data Files
AR826 - Invalid Commit Record Message On An Invoiced Order
Agility
- Sales Orders
Invalid Commit Record Message On An Invoiced Order
*** This method is not available within current Agility versions v600+ ***
To delete orphaned BOs or Commits, you will need to use the Automated Support Program "Delete Orphan BO and Commits":
System Administration > Restricted Processing > Automated Support Programs
Run this program within the relevant branch to delete any orphaned backorders or committed item records attached to orders.
A Sales Order is displaying the following error message: "Invalid commit record exists for SO # 1212121212 seq 1 Line item has been completely invoiced".
To Resolve This Issue:
Navigate to System Administration > Restricted Processing > Support Programs and run the support program "delorphbocm" for the affected branch. You can run an audit report only to show you any orphaned commit records and not change anything, or run the program as "audit report & Update" to clean up any orphaned commit records. Once you have run the "delorphbocm" support program, go back into the order and confirm you no longer receive the error message.
AR832 - How to better manage trim and interior door packages to allow complete order fufillment?
Agility
- Work Orders
For backordered pre-hungs or material on a job-site delivery I think it is a millwork industry issue when product goes to job sites and the trim carpenter does not get all of the pre-hungs he needs to start trimming and has to call us? Sometimes we do not even know until he calls. The trim carpenters get mad because they aren’t making money and don’t have time to waste. Marking the order ship complete is not always the solution. Possibly we could have substituted, upgraded, or arranged a later date with the contractor, etc. had we known the items were not going to print on a work order or pick ticket. What is a better way to manage these orders to allow for reliable and quality service for our customers? Using the ship complete flag until you are knowingly ready to deliver (and/or build if desired) part of the quantities is likely the best option to prevent partial quantities from shipping unknowingly on these orders. You should monitor the upcoming work orders via viewers to see if there are substitutions to be made, reallocation of quantities to fill the back orders or fulfillment of the backorders via a special fill in purchase or the like or if the customer needs to be contacted to move the date out. Because it is components of work orders that are the key here the parent component list is a nice solution. You can save and launch a sales order viewer and include just the items (parents, other trim items you are interested in, likely by product group) for orders out a number of days. Other filters can apply (sales agent, even misc field values if using misc fields creatively for status type tracking) Once the viewer is launched, from there you can use the “Update Dept/Resource/Schedule Date” process selection on the lines you select (the parent lines) and that takes you into the parent component list.
With the parent component list you can
Define a view that by default looks at backorders only (the things you have problems with. You can have another view that shows all components. There is a lot of info about dates, quantities and the like you can have in the customizable grid. Show the parent items completion quantity, quantity that could be completed (parents with all components available) and the quantity that is uncompleted and have backordered components Call the parent component list from the viewer for multiple work orders View stock status, reallocate quantities and the like · From within a sales order this is the closest thing we have to the order inquiry in DMS+ and is part of the reason we built the parent component list screen was to allow customers to see into their work orders for component statuses/quantities more easily.
With some creative use of relabeled misc fields attached to the header of the order - you can monitor what conversations you are having with customers for user defined status of the order. Although the scheduling manager does not have this same view into the work orders themselves, the use of scheduling resources, departments and schedule dates does help to ensure the original date when placing the order is close to the real date This would allow you to manage dates a little better on ship complete orders on the front side.
AR840 - Year End Procedures Checklist
Agility
- General Ledger
Year End Procedures Checklist Initial Preparation Steps 1. Complete all period-end procedures except closing and changing the periods which are included on this checklist. Refer to the Period End Procedures Checklist for instructions.
2. Review the Year End Procedures within Agility Help for general guidelines on closing year end activity.
3. Perform a year end backup of the complete system. Label the tape "Year End xxxx"(replacing xxxx with the year) and store the tape in a safe place.
Hosted (SaaS) Solution customers ONLY: The normal automatic nightly backup creates this backup for you. NO action is required.
4. Open a new general ledger year and update period start dates as needed: Select General Ledger > End of Period > Begin New G/L Year.
You can complete this step a few days prior to the new year. The new general ledger year must be open before you close the year in accounts receivable and accounts payable and before you open a new year in accounts receivable and accounts payable.
Manually opening a new year is not necessary when changing the current period using Automated Period End.
Accounts Payable Functions 5. Open the new year: Select Accounts Payable > End of Period > Begin New A/P Year.
This step is not necessary when changing the current period using Automated Period End.
6. Change the current year to the new year: Select Accounts Payable > End of Period > Change Current A/P Year.
This step is not necessary when changing the current period using Automated Period End.
7. All periods for the new year default to open when manually opening a new year. The default period is automatically set to the first period of the year.
If you do not want all periods open for the year, select Accounts Payable > End of Period > Close Open A/P Periods. Close periods other than the first period of the new year.
When changing the current period to period 1 using Automated Period End, the Close future periods created with the new year setting controls whether the periods are open or closed.
8. Select Accounts Payable > End of Period > Close Open A/P Periods. Close open periods for the previous year.
This step may not be necessary if you have been using Close current period through the Automated Period End.
9. Run the end of year process for the previous year: Select Accounts Payable > End of Period > End of A/P Year.
This step is not necessary when closing your final period using Automated Period End.
In A/P you should run the end of year process one time.
If you reopen a prior A/P year, the system requires you to run the End of A/P Year before you can run the End GL Year.
Accounts Receivable Functions 10. Open the new year: Select Accounts Receivable > End of Period > Begin New A/R Year.
This step is not necessary when changing the current period using Automated Period End.
11. Change the current year to the new year: Select Accounts Receivable > End of Period > Change Current A/R Year.
This step is not necessary when changing the current period using Automated Period End.
12. All periods for the new year default to open. The default period is automatically set to the first period of the year.
If you do not want all periods open for the year, select Accounts Receivable > End of Period > Close Open A/R Periods. Close periods other than the first period of the new year.
When changing the current period to period 1 using Automated Period End, the Close future periods created with the new year setting controls whether the periods are open or closed.
13. Close open periods for the previous year: Select Accounts Receivable > End of Period > Close Open A/R Periods.
This step may not be necessary if you have been using Close current period through the Automated Period End.
14. Run the end of year process for the previous year: Select Accounts Receivable > End of Period > End of A/R Year.
This step is not necessary when closing your final period using Automated Period End.
In A/R you cannot repeat the end of year process.
General Ledger Functions 15. To refresh the balance values on customer sold-to records, select System Administration > System Setup > Recalculate Current Balance. This program is optional.
16. Copy the customer sold-to high balance information from the current year to the previous year and move the 1099 value from the current year to the prior year on remit-to records: Select General Ledger > End of Period > Maintenance File Updates.
If you share A/R information, do not run customer update process more than once. If you do not share A/R information, run this process only once for each unique A/R branch.
Perform this step at the end of the calendar year regardless of whether your company has a calendar or fiscal year end.
17. If you share A/P information, do not run the 1099 update process more than once. If you do not share A/P information, run this process only once for each unique A/P branch.
Perform this step at the end of the calendar year regardless of whether your company has a calendar or fiscal year end.
18. Change the current year to the new year: Select General Ledger > End of Period > Change Current G/L Year.
This step is not necessary when changing the current period to period 1 using Automated Period End.
19. All periods for the new year default to open. The default period is automatically set to the first period of the year.
If you do not want all periods open for the year, select General Ledger > End of Period > Close Open G/L Periods. Close periods other than the first period of the new year.
When changing the current period to period 1 using Automated Period End, the Close future periods created with the new year setting controls whether the periods are opened or closed.
20. Close open periods for the previous year: Select General Ledger > End of Period > Close Open G/L Periods.
This step may not be necessary if you have been using Close current period through the Automated Period End.
21. Run the Retained Earnings Validation report: Select General Ledger > End of Period > End of G/L Year.
Verify that all accounts are assigned to a retained earnings account. If there are any accounts not assigned or assigned incorrectly, select General Ledger > Chart of Accounts > Retained Earning Accounts. Assign the accounts to the correct retained earnings account.
22. Run the end of year process for the previous year: Select General Ledger > End of Period > End of G/L Year.
You can run the G/L End of Year process as many times as necessary if adjusting entries are required in the previous year.
23. If start dates are not automatically updated when opening the new year, define a new start date for each period: Select General Ledger > Chart of Accounts > G/L Structure > Period Definition.
Complete this step prior to entering any receiving or receiving adjustments for the new year or running any Data Warehouse Update programs for the new year.
24. Create financial statements for the new periods in the new year: Select General Ledger > Financial Report Writer > Print/Export Financial Rpt.
All periods in financial statements are tied to a G/L year, so when you create a new year you must also create or update a financial statement layout with the periods for the new year.
Click here to view an article that helps walk through this step.
25. If you use the LIFO method to value inventory, update LIFO records and then run the LIFO report to review LIFO values assigned to items.
· General Ledger > End of Period > LIFO Update
· Data Files > Item Information > Queries/Reports > LIFO Report
This step is a fiscal year-end process as your LIFO update needs to correspond to when you close your books and file your tax returns.
26. If you use the F9 Professional® reporting tool, change your year as well as your period in order to get financial statements for the new year.
Posting to a Closed Year If you need to make journal entries for a closed year, complete the following steps. You may repeat these steps as often as necessary.
Post Year-end Activities 1. Ensure the user has access to the 'Access Prior Year Data' security action : Select System Administration > Security Administration > Action Allocation.
2. Open the desired period: Select General Ledger > End of Period > Open Closed G/L Periods.
3. Enter the journal entries: Select General Ledger > Journal Entries > Journal Entry.
Change the Posting Period and Posting Year to the appropriate values.
4. If you use the manual post option, post the new journal entries: Select General Ledger > Posting Functions > Post Journal Entries. *
Change the Posting Period and Posting Year to the appropriate values.
5. Close the period: Select General Ledger > End of Period > Close Open G/L Periods.
6. Run the Retained Earnings Validation report: Select General Ledger > End of Period > End of G/L Year.
Verify that all accounts are assigned to a retained earnings account. If there are any accounts not assigned or assigned incorrectly, assign the accounts to the correct retained earnings account on the Retained Earnings Acct Maintenance screen within the General Ledger module.
7. Run the end of year process for the previous year: Select General Ledger > End of Period > End of G/L Year.
You can run the G/L End of Year process as many times as necessary if adjusting entries are required in the previous year.
* Recommendation: Set all default posting options to Direct Post to keep the General Ledger up to date with real time data and allow for timely balancing with subsidiary ledgers.
AR863 - How to set up Automated Processing Jobs in Agility
Agility
- System Administration
How to setup Automated Processing Jobs in Agility
The Automated Processing tool, also known as Auto Processing, allows you to run routine Agility processes automatically without user intervention. The example we will use will be to setup your reorder calculations to be run each month.
Setting Up Jobs Go to System Administration > Restricted Processing > Automated Processing > Queue Maintenance.
Click the New Job icon. In Job name, type in Reorder Calculations Forward. Type in the Job description.
Click the Add Task button.
Under Task Category, choose Update Process. The Process Type will be Reorder Calculations. Under the Process Name, click the magnifying glass to open the saved Reorder Calculations you just set up. Choose the first Forward Calculation that was set up and click OK. Verify the processing branch is correct and click OK.
When finished, click the Save Job button.
Setting up a Queue Click on the Queue tab. Click on the Create Queue tab. In the Queue Name, type in Reorder Calculations Forward. For Frequency, choose Monthly. IN the Interval, choose Last day of calendar month. your Daily interval will be Once daily. Set the Start time sometime after the end of business. Start time is in military time, so 6 pm would actually be 18:00. Click Add Job and choose your Job of Reorder Calculations Forward. When finished, click the Save Queue button.
Agility will run the jobs automatically at the times specified.
Listed below are tasks that can be run via automated processing:
AR876 - Pick adjustments that are set to default to print are not printing
Agility
- Sales Orders
AR897 - Is there a way to see what sales order was created from a quote?
Agility
- Quotes
AR911 - How do I merge or renumber 2 customer accounts into 1?
Agility
- System Administration
Instructions to merge two customer sold-to accounts or ship-to accounts into one. This typically is needed for thee common scenarios:
· one customer acquires or buys out another customer
· duplicate customer accounts created in error
· customer ID is incorrect and needs to be fixed
Once you merge the customers this will be reflected on all past and current sales transactions and A/R invoice history in the system. DMSi highly recommends that you performs this merge in your TEST environment first you are unsure how yo want to merge them (create new vs combine), as once the accounts are merged, we cannot un-merge them.
You can perform this process through System Administration > Renumber Processing > Renumber Customers.
Merge entire customer account
Enter in the customer code you would like to merge into another account in the “from” customer id field. Then enter in the correct customer you want to combine with in the “to” customer id field.
If you are moving the entire customer account then check the ALL box for all ship-to’s.
There are drop down options for both the ship-to and bill-to:
· Create new sequences
· Combine with sequences
Create new is typically used if you want to ADD the ship-to/bill to sequences to the new customer ID. This is common when one customer acquires or buys out another customer.
Combine with is typically used if the accounts are duplicated created in error and you just want to merge into one account.
Merge / move customer ship-to
The ship-to is only needed if you want to move one ship-to to another account or you need to merge two ship-tos on the same customer account together (shown below). Rather then selecting the “all” checkbox for all ship-to’s, specify the desired ship-to you are moving. This is common if the ship-to is created under the wrong account or a customer that was previously as cash ship-to account decides to open a true account with credit terms, etc and you want to move history.
The ship-to and bill-to drop down have the same options and previously: Create new or combine.
AR917 - Marvin - Receiving error connecting to Marvin Web Service
Agility
- Interfaces
AR972 - Cannot perform cost allocation error message when trying to complete a reman
Agility
- Reman
AR974 - Improve performance of CQ reports starting in version 450
Agility
- Cyberquery
AR1001 - Daily Balancing FAQ V521 and Prior Versions
Agility
- General Ledger
V521 and Prior Versions Setup Required General Ledger Settings Before you set up the processes for daily balancing, there is a little set up you need to do in the General Ledger and G/L Integration Points so the Daily Balancing process recognizes the subsidiary G/L accounts to balance.
Go to: General Ledger > Reports > G/L Subsidiary Balancing Report
Setup the Subsidiary Balancing Report Save for All Users Go to: General Ledger > Chart of Accounts > Categories Definition
Setup new GL categories in Agility "Sales" & "COGS" Go to: General Ledger > Chart of Accounts > Account Maintenance
Change the Category on the Sales account and COGS account. Go to: System Administration > System Controls > Default System G/L Accounts
Assign default GL accounts to the new categories These settings are needed for the custom Cyberquery that you will run daily to indicate what the balance is in your General Ledger for the G/L Subsidiary Accounts.
Custom Cyberquery Create a new folder named “GL_Balance_Rpt ” under the cq_reports folder. There are 3 Cyberquery files that need to be placed into your Agility Cyberquery folders
Copy and paste these 3 lines (highlighted in red) into a new Cyberquery Macro (in CQ: File > New Macro ) report named: GL_balancing_report.mf run ../GL_Balance_Rpt/gl_balance_rpt1.eq run ../GL_Balance_Rpt/gl_balance_rpt2.eq rreplace gl_balance
The file “GL_balancing_report.mf ” created in step "a" above needs to be saved (File > Save Macro As ) in the folder "cq_reports " Attached to this Article are two Cyberquery report files named “gl_balance_rpt1.eq ” and “gl_balance_rpt2.eq ”. These 2 files need to be brought into CQ (save the file locally on your desktop, then in CQ use File > Import from “your computer”). Then save them in the new sub-folder “GL_Balance_Rpt ” created in step “4” above (File > Save Enquiry As ) Daily Processes At the end of each day you will want to do the following for Daily Balancing:
Ensure the Data Warehouse Update is run. This is typically an Automated Process that is run each day after hours. Set up the G/L Subsidiary Balancing Report to run as an Automated Process daily, after hours, following the Data Warehouse Update automated process. This report can be emailed in the appropriate format. Typically this is .xlsx or .pdf. Set up the “GL_balancing_report.mf ” to run daily through Automated process, after hours. It can be included in the same scheduling that is used for running the GL Subsidiary Balancing Report in order to eliminate any timing issues between the two reports. This report can be emailed in the appropriate format. Typically this is .xlsx or .pdf. Compare the G/L Subsidiary Report Balances to the 'GL_balancing_report' cyberquery. Often the output from these two reports is entered into a daily balancing spreadsheet where you can track any variances that occur. Researching accounts that are out of balance The following help links will assist you with the steps needed for you to research accounts that are out of balance For Balancing Reports:http://documentation.dmsi.com/agility/prod/General_Ledger/g.lbalancingreports.htm For balancing inventory:http://documentation.dmsi.com/agility/prod/General_Ledger/balancinginventory.htm For balancing AP:http://documentation.dmsi.com/agility/prod/General_Ledger/balancingaccountspayabletrade.htm For balancing AP Recon:http://documentation.dmsi.com/agility/prod/General_Ledger/balancinga.preconaccount.htm For balancing AR:http://documentation.dmsi.com/agility/prod/General_Ledger/balancingaccountsreceivable.htm For balancing COGS:http://documentation.dmsi.com/agility/prod/General_Ledger/balancingcostofgoodssold.htm For balancing sales:http://documentation.dmsi.com/agility/prod/General_Ledger/balancingsales.htm The following are some of the most common errors that cause out-of-balance entries: 1. AP and/or AR parameters set to manual post, but transactions have not been posted to the GL 2. Reports were not printed at the correct time 3. Backdating transaction such as invoices and receivers 4. Posting both debit and credit side of payables and/or receivables to the same account 5. Dropping A/P Recon records and using the A/P Clearing account as the offset 6. Inventory adjustment reason codes set to post to the Inventory account which will leave a net impact on the GL of zero, while increasing/decreasing the on hand value report. 7. Sales account parameters set incorrectly
AR1008 - Zip Tax - Creation and Import of Tax Code Updates in Agility
Agility
- Interfaces
AR1065 - Can I use Avalara if my users don't have internet access?
Agility
- Avalara
AR1078 - SPO Cannot Be Created, already have a saved SPO...
Agility
- Purchasing
AR1087 - Cause of excessive WMS logging
Agility
- WMS
When working in a test environment, excessive, unexpected WMS Log activity could cause a database to crash if ignored. Review the following solution if you are experiencing WMS activity in a test environment which has not been properly configured for testing WMS activity. 1. Is WMS running in a branch and environment where you don't expect WMS activity? If so, access System Administration > Module Controls > WMS Parameters and uncheck "Use WMS" to turn off WMS for that branch.
2. Access Inventory Control > Warehouse Management > WMS Log Maintenance. Confirm that the Logging Level is set to Error and review the messages.
3. If the WMS Log contains errors with a Process Type of Processing, confirm that the Agility WMS Processor service is installed and configured to run in this branch and environment. (Agility always attempts to process incoming records. If it can't process them as soon as it receives them, it changes the records' status back to Ready and attempts to process them again. If Agility can't process the records, it can get stuck in a loop.)
4. If you need to prevent Agility from attempting to process records again, access Inventory Control > Warehouse Management > WMS Transaction Maintenance. Set the Activity Type to Incoming or Outgoing (same Activity Type listed in the WMS Log), and set the Status to Ready. If you know the record's created date, select it in Created Date; if you don't know the created date, check All. When all options have been set, click Search.
Select the record(s) you wish to process, and click the Update Status button (rightmost button on toolbar). When Transaction Status appears, select Processed, and OK. WMS Transaction Maintenance will now show an In Status of P (Processed).
AR1127 - Is there a report to see how much we charged in restock fees for a specific period of time?
Agility
- Sales Orders
AR1153 - Create Custom viewers
Agility
- Viewers
Viewers Define and save queries to quickly search and select data for review records such as transactions, inventory, or commissions.
The three main features of Viewers:
Viewer Builder: to define and save viewer queries for multiple users Viewer Criteria: the criteria selection options to control the records returned Viewer Results: display data based on the selections made on the Viewer Criteria screen. The results includes additional options for viewing further information about a record returned by the query or take action on the data such as creating a new transaction and adding items to a transaction Available viewer types: Attribute, Commission, Dimension, Dispatch, Inventory, Item Activity, Picking, PO, Reman, Shipping and SO
User the Viewer Builder to create Viewers from Scratch or to save for specific users, security groups, or All users. (Data Files > Misc Information > Viewer Builder)
Viewers can be accessed from a number of places. An easy spot to start would be Sales Orders/Quotes > Viewers > SO Viewer. To search for a Viewer, select the Locator icon. Change the type if necessary.
To run a Viewer select the “Run” button on the bottom right corner.
If you change the criteria and wish to go back to the original viewer criteria, use the “Reset to Default” button in the top left corner.
To save a new Viewer, select the Save button and chose Create New Record. Type in the name of the new viewer and click OK.
Recommended/Commonly Used Viewers: The viewer options are grouped by department that most commonly use each viewer, but the same viewer may be useful in multiple departments.
Sales Department MTD Sales by Customer: month-to-date invoiced SO information by customer; totaled by customer
Open Orders by Sales Agent: open SOs and CMs; totaled by expect date. This view should be created for each sales agent.
Orders Created Today: SOs entered for the current date by sales agent; totaled by expect date. This view should be created for each sales agent.
Orders Delivering in the next “x” days: SOs delivered for the current date range; totaled by route. This query is typically run prior to billing for the day and sometimes used for specific routes to provide a route sheet for the driver.
Inventory Stock Status Viewer: stock status information for a selected item/product group. You can set up multiple specific viewers for your “A” items or setup a viewer so that the item/product group range must be selected each time the viewer is run.
Purchasing/Receiving Department Open PO Listing by Supplier: open POs by supplier; totaled by supplier. You can also set this query to run for a specific supplier.
Inventory Stock Status by Supplier: stock status information for a specific supplier’s products
Open Purchase Orders by Expected Date: open POs; total by PO
Production Department Reman Production Schedule: all open reman orders
Millwork Department Work Order by Department: Bill-of-materials work orders by expect date and department used to gauge resource allocation within a millwork shop.
Sales/Dispatch Department Open Orders Sorted by Expected Date: Open sales orders; totaled by expect date. This query includes both orders that have been printed and orders that have not been printed.
Orders Shipping Next Day: Open sales orders expected to ship the following day used by the warehouse manager to properly allocate shipping resources; totaled by expect date
Backorder Report: Items that cannot ship due to insufficient available quantity; totaled by route
Management Gross Margin View of Orders : Orders entered for the specified date or date range showing profitability information
MTD Booked Sales by Sales Agent: Month-to-date invoiced sales orders; totaled by sales agent
Commission Viewer- what’s been paid or not (including write-offs)
Open Purchase Orders: Open purchase orders
For additional information in Help, check out the Recommended/Commonly Used Viewers page.
AR1375 - Agility Security for WMS Implementation
Agility
- WMS
AR1434 - How to Modify the Default Item Activity Viewer used in Stock Status
Agility
- Viewers
How to Modify the Default Item Activity Viewer used in Stock Status
Question: Is there a way to set the default settings for an item activity viewer that is accessed through stock status?
Solution: The default activity viewer in stock status (or any viewer for that matter) is the last activity viewer that you ran.
Meaning if you run the activity viewer from stock status (ie. viewer named ABC). then change the viewer to a different activity viewer that you already have saved (ie. viewer named XYZ) & run that. Or you can change the date setting on that viewer, save it and then run it again with the new defaults.
When you go back into the activity viewer the next time the last viewer you ran is what will default. Which in this case is the XYZ viewer.
To change the setting on the default activity viewer go to Data Files > Misc Information > Viewer Builder. Locate the activity viewer that is setup & adjust the activity date range option and save the viewer.
AR1521 - Custom Item Fields
Agility
- Data Files
Custom Item FieldsEasily define custom fields for item and dimension records (Training video available here ) The new Custom Item Fields Definition screen allows you to specify user-defined field labels, determine whether the field is required, and select a data type for each custom field (e.g. text, decimal). These custom fields are then shared across all branches so there is no need to create or maintain the fields for more than one branch. 1. To create a new Definition click on the Custom Item Field (marked below). 2. Select Custom Field Definitions. 3.Identify the field label, Select the data type, and Save. Types of Custom Fields (Data Types) for Items and Quotes: • Date • Decimal • List • Text • Whole Number • Yes/No
The new 'Update Custom Item Fields' security action determines whether you can add, delete, or update custom item fields. If access to this action is denied, the custom item fields are display only. Once you define custom fields, you can maintain the actual data in the fields at the item or dimension level. A new icon on the Item and Dimension Maintenance screens gives you access to the Custom Item Fields window where you can enter values. This data is unique per branch and item/dimension, including the main item record (00x00x00). The system stores these records based on how you share item content definition branch records. In addition, with proper security, you can access the Custom Item Fields Definition screen from the Custom Item Fields window.
Additionally, custom item fields are included as available columns on the Inventory and Dimension Viewers and the values for these fields can be updated from Item Mass Update, Item Cross Branch Update, and Item Import. For more information, see the comprehensive help files here .
AR1530 - Why is my order point not correct
Agility
- SPO
An item does not have the correct order point after running reorder point calcuations
Question: GAF Shinglemate (GAFSM) in ABC branch has purchased 100 plus rolls in April. I recalculated all ABC branch reorder points this a.m. to try to capture the increased GAF buying at that branch over last 30-60 days. I was surprised that on this product (as an example) that the needle (i.e. reorder point) didn't move much and that projected monthly usage was under 5 rolls. The item had April sales of 105.
We ran Reorder Calculations looking forward three months but trending the last 90 days.
When we did the calculation, Agility switched to B03A (backward three months), instead of F03 as selected? Also the Average 12 month usage is 19.17 (current) and 7.42 (last). Why is the Projected average only 4.33?
We imported the 24 month usage so the item would have the correct usage.
Answer: The issue has to do with the History Start Date used in Reorder Calculations
When reorder calculations are set to use forward history (e.g. selected on the Reorder Calculations screen or set as the fixed ROP Calc Method on the item record ), the system verifies the history start date on the item record before calculating the reorder point.
?
History start date is blank ? The system uses the minimum reorder point as the reorder point, if a minimum reorder point is specified. If there is no minimum reorder point, the system does not calculate a reorder point for the item.
?
History start date is less than one year ago ? If the ROP Calc Method is not fixed, the system calculates the reorder point using a backward history of 3 months, since available history is insufficient to calculate a valid forward history. The system assigns B03A as the ROP Calc Method , indicating a backward history of 3 months was used as an alternative to the selected method.
If the ROP Calc Method is fixed, the system does not calculate a reorder point for the item.
?
History start date is greater than one year ago ? The system calculates the reorder point using the calculation parameters specified on the Reorder Calculations screen. If the ROP calculation method for an item is set to B03A (i.e. the history start date was previously less than one year old), the system uses the selected forward history calculation and assigns the new method to the item content definition branch record.
AR1541 - Troubleshooting custom CyberQuery reports added to the Dashboard
Agility
- Cyberquery
AR1556 - What are the recommended Credit Memo Reason Codes
Agility
- Best Practice
AR1563 - Assigning users to Cash Receipts Batch for POS
Agility
- Sales Orders
Assigning users to Cash Receipts Batch for POS The most important thing about a cash batch is that the assignment of the user and the payments that are part of the cash batch MATCH what you take to the bank. By using a process of opening a new cash batch when you pull the cash drawer(s) associated with the batch and grouping the payments that were made as part of the cash batch together and depositing them in the bank together you simplify the process of bank reconciliation throughout the month (if reconciling items as they appear online) or at the end of the month when you receive your bank statement. For most Agility customers, typically cash batches have a unique batch ID for a branch. All users in the branch are assigned to the cash batch. The cash drawer is pulled at the end of the business day and the cash batch is changed at the end of the day. This process can be automated daily through Automated Processing. DMSi recommends that if this process matches closely to your handling of your cash drawers that you automate the process by assigning a cash batch of the date of the batch plus a sequence that is unique for the branch and that you include all users that have the branch assigned as a default branch in the cash batch.
To assign users to the cash batch, go to System Admin > Restricted Processing > Automated Processing > Batch Criteria
Select the type of 'Cash Receipts'
Select the branch for the cash batch criteria.
Check the option to Only Display users with default branch of (selected Branch)
Select all available users for Selected Users. This will set the Selected Users to <all>
By selecting all users for the branch, if any users are added later with a default of that branch - they will automatically be included in the next cash batch created for the branch. This reduces the maintenance you would need to do to maintain the cash batch criteria record when new users are added.
Select relative date for the date for batch ID. Typically, this is set to the run date +1 if the automated processing is set to run daily Before midnight. If running after Midnight the days would be zero
Select an additional sequence for batch ID which will make this a unique cash batch for this branch. This is a numeric field and can be up to 8 digits.
The new batch ID for the current day will show (yyyymmddxx) where xx is the additional sequence number.
Automate the criteria to run once a day at the end of the day if before Midnight, beginning of the day if after midnight. By doing this, all cash receipts received in the branch are assigned to one cash receipt batch for the day.
See the following related article for information related to adding jobs to automated processing:
How do I setup Automated Processing Jobs in Agility
AR1571 - EOQ Worksheet
Agility
- Best Practice
Information about the Economic Order Quantity and the worksheet to calculate it's values
EOQ Parameters
Recommendation: Update the purchasing cost and carrying cost factors annually for each branch using the EOQ Parameters Maintenance screen. The factors may be different for each branch.
Economic Order Quantity (EOQ)
Once the buyer has determined when to buy (based on reorder point) they then need to determine how much inventory to buy. Buyers use the economic order quantity (EOQ) to determine the appropriate inventory quantity to purchase. The economic order quantity is the order quantity that results in the lowest outgoing costs of an item based on the unit cost of the item, item usage, costs for purchasing, and storage cost.
Recommendation: Update the purchasing cost and carrying cost factors annually for each branch using the EOQ Parameters Maintenance screen. The factors may be different for each branch.
The system calculates the economic order quantity, rounded to two decimals, to determine the recommended buy amount for an item on a suggested purchase order. Use the economic order quantity to determine whether you should buy smaller quantities more frequently or buy larger quantities less frequently to have the lowest outgoing cost.
EOQ = square root of [(24 * TAU * Purchasing Cost) / (Carrying Cost Factor * Cost)]
Value
Definition
24
Fixed constant value representing 2 times the number of months in a year, as the formula needs to include twice the monthly demand
TAU (Trend Adjusted Usage)
Same monthly usage used in Reorder Point (ROP) calculations
The exact formula for the usage is based on the method used to calculate the ROP.
Purchasing Cost
Annual cost incurred by the purchasing department for writing each line of a purchase order
To determine the cost per purchase order line, divide the purchasing department costs by the number of purchase orders issued annually, multiplied by the average number of line items on each purchase order.
Purchasing Cost = Annual Cost for Purchasing / (Total Number of POs Per Year * Average Number of Lines Per PO)
For example, a purchasing department issues 2160 purchase orders annually with an average of 14 line items per purchase order and an annual cost of $151,200. The cost per purchase order line would be $5.
$151,200 / (2160 * 14) = $5
The annual purchasing cost can consist of the following costs. Specific cost types can vary by company. See the calculation worksheet below to determine your Purchasing Cost.
•
Inventory control – salaries and costs related to keeping accurate inventory quantity information
•
Computer – portion of data processing costs related to inventory control/accuracy and purchase order entry and receiving
•
Purchasing – salaries, rent, phones, expediting, etc.; expenses related to stock purchasing
•
Receiving – costs associated with accurately receiving material into the computer system; this cost does not include unloading and put-up costs
Carrying Cost Factor
Cost of keeping the item on hand
This factor represents the cost of carrying $1 of inventory for one year. You should review the carrying cost factor annually. Cost can vary widely based on the nature or your business and the type of products you carry. See the calculation worksheet below to determine your Carrying Cost factor.
Cost
Replacement cost of the material
For non-lumber type items, this value represents average cost. The following hierarchy determines the cost used in EOQ calculations for lumber type items. The first step applies only if the item is costed by dimension. If the value for a step is zero, the system moves to the next step.
•
Average cost for dimension
•
Average cost for main item record
•
Last received landed cost for dimension
•
Last received landed cost for main item record
Calculating the Inventory Carrying Cost Factor
Use the following worksheet to determine the economic order quantity carrying cost factor, e.g. amount to carry $1 of inventory for 1 year.
Warehouse Space
$__________
The annual expense of warehouse space. If all space is company owned, use the cost of leasing equivalent space in the area. Include taxes and insurance paid on buildings in this amount.
Taxes
$__________
Actual taxes paid in the last year on inventory. Taxes on buildings should be part of the warehouse space cost figure.
Insurance
$__________
Insurance premiums paid in the last year on inventory. Insurance on buildings should be part of the warehouse cost figure.
Shrinkage/Obsolete Items
$__________
The value of inventory which was adjusted off during the last year, either because of physical count differences or material that was deemed non-saleable.
Material Handling
$__________
The total annual expense in labor and material handling equipment needed to receive and stock all incoming merchandise. This should also include the cost to move and count inventory during the year. Customer order-filling expense is not included.
Cost of Money
$__________
The interest that could have been earned in a safe investment if the money had not been used to purchase inventory.
======================================================================================
Total Costs
$__________
Totals Costs = Carrying Cost Factor
Total Costs
/
Avg Inventory for Past Year
=
Carrying Cost Factor
$_________
/
$__________
=
$__________
You can find the average inventory for the last year by running the Inventory Turns/GMROI report for last year. The total prints at the bottom of the report.
Cost typically is between .25 and .4
Calculating the Purchasing Cost
Use the following worksheet to determine the Purchasing Cost, e.g. amount of money it costs to buy one line item on a purchase order.
Cost of Purchasing Staff
$__________
The total annual expense for staff that handles purchasing and negotiating costs for all incoming merchandise.
Cost of Accounts Payable Staff
$__________
The percentage of cost as a dollar amount for the accounts payable staff creating invoices, paying the invoices to your suppliers and researching inventory discrepancies.
Cost of Overhead
$__________
The percentage of cost as a dollar amount for the overhead on things such as computers and phones.
Cost of Receiving
$__________
The percentage of cost as a dollar amount spent receiving the incoming merchandise and entering the receipt into Agility.
======================================================================================
Total Costs
$__________
Totals Costs
Total Costs
/
Number of PO Line Items
=
Purchasing Cost Factor
$_________
/
$__________
=
$__________
To get the total number of PO line items, run a PO viewer in detail view for all POs created in the last year. In the bottom right of the screen it will tell you record 1 of X. The number X is the total number of PO line items for the year.
Cost typically is between $4 and $8
How to Update EOQ Parameters
Access EOQ Parameters Maintenance: Purchasing Þ EOQ Parameters
Notes:
•
Update these values once a year.
AR1596 - How to set up Purchase Order Labels
Agility
- Purchasing
AR1600 - How to set up sales agents
Agility
- Data Files
1. In Agility, access Data Files > Sales Order Settings > Sales Agents.
2. Populate the Sales agent ID and Printed ID fields at a minimum.
a. The key field is the Sales agent ID, a 12-position alphanumeric field. The Sales agent ID is what is seen in Sales Order Entry, Viewers, and Reports.
i. Use a consistent format to ensure sales agent records display in a logical order throughout the system, such as range selections and reports. If you include alpha characters DMSi recommends you utilize an upper-case format to ensure a consistent sort order.
b. The Printed ID value prints on forms. DMSi recommends you enter a meaningful value in this field to assist customers in recognizing the sales agent associated with the sales order.
c. Assign the notification user ID
ii. The system uses the user ID to pull the email address from the user’s profile for sending notifications via email.
3. The remaining fields are information only and not required
4. To Save, click the Save icon on the top left corner
Additional information: Agility Online Help link:
http://documentation.dmsi.com/agility/prod/Data_Files/salesagents.htm
AR1603 - How to Set up Delivery Routes
Agility
- Customer
How to Set up Delivery Routes When you define delivery routes, you can assign the routes to customer ship-tos or customer branch ship-tos, which allows you to batch create pick files and shipments, batch print picking/delivery forms, and invoice sales orders based on delivery route/date. In addition, you can run viewers and reports for selected routes.
Data Files > Customer Information > Delivery Routes Populate Route ID, Frequency, Lead days, Cut-off time, and any other necessary information. To Save, click the Save icon on the top left corner, circled below. For field descriptions in the Delivery Route Maintenance screen, open the Delivery Route Maintenance screen in Agility and then press F1 on your keyboard to launch the Agility online documentation page.
Additional Information: · If you do not use true delivery routes, DMSi recommends you set up at least one generic route. If you don't deliver to every customer every day of the week, define a generic route for each day of the week. Assign the generic routes to all of the branch ship-to records in each branch that delivers to the customer. You can then batch print pick forms or delivery tickets using the generic routes, a process which is much faster than printing the forms on an order-by-order basis.
· Typical methods for structuring routes:
o Generic: define routes based on delivery schedule (days of week).
§ Examples: 1MonAM, 1MonPM, 2TuesAM, 2TuesPM
o Generic and Truck: define one set of routes based on delivery schedule and another set representing actual trucks or drivers.
§ Before printing delivery tickets, reassign routes to the orders based on the actual truck. This method allows you to track trucks throughout the delivery process.
§ Examples: Trk1, Trk2, Trk3
o Geographical: define routes based on a combination of delivery schedule and geographical location.
§ Used if you routinely deliver to the same locations (rather than job sites) on set days of the week.
§ Example: The Orlando branch delivers to Tampa, Miami and Jacksonville. 1Tmp, 2Tmp, 3Mia, 4Mia, 5Jax
o External delivery services (UPS, FedEx).
o Hold: assign to sales orders to place on hold until you resolve delivery date so pick/deliver forms are not printed for the order.
o Expedite: flag high priority orders to ship same day or ASAP.
AR1705 - Does the GetPriceInfo API include representative item logic or future price logic?
Agility
- API
Scenario:
Under Sales Orders/Quotes > Queries and Reports > Pricing Report there is an option to build a pricing viewer to display pricing information using representative item logic and future pricing logic.
The question is can the GetPriceInfo API call be used to pull this information? Can it be run for future pricing?
Can it be run to use the Representative item code functionality?
Answer:
Current functionality in our SOAP GetPriceInfo API does not include representative item logic nor future price page logic. It is currently built to essentially mimic the functionality of the price info window in stock status.
AR1725 - How to write off duplicate finance charges created in error
Agility
- A/R
How to write off duplicate finance charges created in error Issue When creating finance charges, the finance charges can be created multiple times in one day. How do you remove the duplicate finance charges?
Solution You will need to write off the duplicate finance charges. The simplest way to do this is to pull up the finance charges that exist for the branches or groups of branches and then write them off in the AR Open and Paid Inquiry (Accounts Receivable > Inquiries > AR Open and Paid Inquiry). The screen shot below indicates what you would want to use as criteria:
1. Run for branch or group of branches you included in the finance charge application process
2. Search by All invoices
3. Choose a Level to view of Customer
4. Include All Invoices
5. Select the Invoice Type of FC
You will see all the Finance Charge invoices that are open for this set of branches (including old open FC invoices). When selecting the invoices, you can select the first invoice and then use CTRL-click to select the last invoice in the list you want to write off. That will highlight all the invoices in between.
6. Once the invoices are selected, select the button for AR Write Off.
This will remove the duplicates from the customers’ account and correct the duplicate entry in the GL.
This will not prevent the invoices from being printed if you print invoices. They will still show in the print invoice queue. They will also be transmitted to BillTrust if you print invoices there.
It will however, remove them from the customer’s open AR.
AR1771 - How to Add custom paint colors during order entry
Agility
- Sales Orders
AR1778 - How to import item attributes into PartnerView
Agility
- PartnerView
How to import item attributes into PartnerView The Item Attribute Import allows you to update the attributes within the PartnerView Search Product option. In the example used below, the Product Search contains a Power Tools section with a Drill section. Within the Drills section, items are listed according to Manufacturer, Price, and Clearance. Using this example, the steps below outline how to update this information using the Item Attribute Import.
Category: Power Tools Group: Drills Attributes: Manufacturer of the item, Price, Clearance items Value: Milwaukee, Stanley, Dewalt, $20 - $30, $30 - $40, $40 - $60, Clearance 2012, Clearance 2011, Clearance 2013
1. Create a spreadsheet containing the Category, Group, Attribute, and Value you wish wish to update In this example, item DR1040 is being added to the filter for Dewalt items and items within the price range of $20 - $40
2. Save the spreadsheet to a location where you can access it during the import
3. In Agility, access Data Files > Item Information > Attributes Information > Import Item Attributes a. Select the Add new record icon to create a new import definition -or- select an existing Definition ID from the grid If creating a new definition, see the Creating a new Definition ID section below b. Select the correct branch, if applicable c. Select the correct Processing Branch d. Select the Select a file icon and choose the spreadsheet you created and saved in step 1 -or- enter the file location in the Transaction fiel field e. After all information has been entered, select Process to begin the import
4. When prompted, select Yes to import the file
5. Review any errors/messages after the import completes
6. Access the Product Search in PartnerView to verify the information displays correctly
Creating a new Definition ID 1. From the Item Attribute Import window, select the Add new record icon a. Enter a name for the Definition ID b. Select <all> for the branch c. Select the Build a Directory Path icon to locate and choose the spreadsheet you created -or enter the file location in the Transaction File field d. Select the corresponding column from the spreadsheet e. Select the radio button for one of the following options: - Replace Existing Attributes : This option removes all existing attributes and saves only the attributes included in the import file Do not select the Replace Existing Attributes option unless you are absolutely sure you wish to wipe out all existing attributes! - Append to Existing Attributes : This option adds the attributes from the import file to the existing attributes - Override Attribute Value if Duplicate Attribute Encountered : Setting this option replaces duplicate attributes with the information from the import file
2. After all information has been entered, select Save and Exit
AR1796 - How to use the Image Bin prior to v522
Agility
- Image Gallery
Go to http://images.dmsi.com as a hosted user. If you are locally hosted, you can access http://imageslh.dmsi.com and follow the same instructions below. Contact Support to get your API URL and service name. Log in with your Agility username and password. Select an existing directory or create a new directory with the “Create Folder” button. Note: DMSi recommends removing spaces to avoid any errors in the image URL, since this URL will contain the folder names. Select Upload Files Select the image(s) from your local directory and upload. Note: When naming images, it is easiest to use the item code here to easily find them again if future edits are needed. To select multiple images for upload, use Internet Explorer and add dmsi.com to your Compatibility View Settings (Alt+X brings up tools menu). It does require SilverLight to be installed to
upload multiple images at a time. Once you have uploaded your images, select 'Export Image list' on the folder to which you uploaded images. Save as an Excel spreadsheet. Note that you will need to add 2 columns to the spreadsheet:Type – valid values are Image or Document. This is a required field. Because your image repository only houses Images, your type will always need to be populated with 'Image' when you’re exporting from the Image Bin Primary – valid values are Yes or No. This is not a required field, but if you leave this field blank or if this column is excluded, the uploaded image will not be a primary image, even if it’s the only image associated with the item Save this updated spreadsheet on a shared folder that you can access from Agility. In Agility, go to Data Files > Misc. Info > Images and Documents. Select the 'Import Images and Documents' icon. Create a Layout Definition by clicking the 'Add new record' icon, select your transaction file, and map over the fields to the appropriate column. Click Save to start the Import. You can view the imported image in Stock Status. You can access Stock Status by going to Data Files > Item Information > Items and click on the 'Display Stock Status' icon. You can also access Stock Status by going to Sales Orders/Quotes > Stock Status. In Stock Status, click on the 'View Image' icon. Note: This only shows the primary image associated with this item.
You can view all images and documents associated with the item in Item Maintenance, by clicking on the 'Assign Images and Docs' icon.
NOTE: Documents can be imported in the same way; however, the Image Bin cannot house documents. Like your images, your docs must be exposed to the internet. You can do this by housing these docs on a webserver you may have or by using a publicly accessible document storage URL. The only difference in your content on the import (step 8 above) will be to change the value of your 'Type' to 'Document'.
AR1797 - How do I print a document to multiple trays?
Agility
- Printing
To get a document to print to multiple trays, you will need to change the Forms Assignment settings for the specific document (i.e. Delivery Ticket).
Data Files > Misc. Information > Forms Assignment In the Forms Assignment Screen:
1) Choose the “Number of Copies” to print
2) Under “Print to Printer Default Tray”, change to “No”.
a) Note if this is set to “Yes” the “Tray/Copy Setting” button will be inactive
3) In the bottom left, click the “Tray/Copy Setting” button.
4) In the Printer/Tray Copy Selection window, choose the same default printer as specified in the “Form Settings” grid.
5) Next you will choose up to 5 trays for the document to print to
a) This will take some trial and error due to the print driver that is associated with the printer.
b) For example, you may need to print to 3 trays and you have an HP printer. HP Tray 1 may match up with tray 2, HP Tray 3 may match to tray 2, etc.
c) Save the Printer “Tray/Copy Selection” and Exit.
6) Save the Forms Assignment settings.
7) Test print a delivery ticket and monitor which trays they come out of. If they are correct, you are finished. If they are incorrect, you will need to go back to step 6 and repeat until they are correct.
AR1798 - F9 was working, but it now gets errors.
Agility
- F9
F9 has been installed and working correctly for a while, but now it displays errors. The errors occur in the F9 financial reports in Excel and also when running the F9 “FMU GL Translate” data update program.
F9 works with a Pervasive database. Normally the Pervasive Server and F9 data files are on a server and the Pervasive Client and F9/Excel financial reports are on a client computer. Errors will occur when the Pervasive Client cannot communicate with the Pervasive Server. There are several reasons why this might happen.
If possible, restart the client (user) PC. In some instances restarting the client will restore the connection between the Pervasive client and the server as well as the connection between F9 and Pervasive. Look to see if the Pervasive services are started (Windows Control Panel, Administrative Tools, Services). There are two Pervasive services on the server. If they are not started, start them both, or if they are already showing that they are started, stop them both and start them again. First start “Pervasive PSQL Relational Engine” and then start “Pervasive PSQL Transactional Engine”. Also on the server, check to see that the Pervasive licensing Product Key is active and permanent (Programs, Pervasive PSQL, Utilities, Pervasive License Administrator). If the Product Key is not showing as active, click on the Repair button. If that does not correct the problem, or if there is no Repair button, call Support at DMSi. If the errors still occur the following will need to be checked.
On the server, changes might have been made to the data paths for F9 folders and files. If this is the case, then the Fmu32 GL Translate and the F9/Excel financial reports need to be edited to point to the new data paths. Permissions might have been changed on the server. The F9 user needs read/write permissions for the folder where the F9 data files are located. The admin password on the server might have been changed. The Pervasive Server installation will need to be edited to use the new password. The password can be edited as follows: Pervasive PSQL Server installations automatically run as a service on the server machine. There are two services and you will need to run them both under a user account other than the default Local System account. This can be modified in the Log On Properties for the Services using the Windows Control Panel. (Administrative Tools, Services, find both PSQL services (when sorted by name, they will start with “Pervasive PSQL”, right click and select properties of each PSQL service, go to the “Log On” tab, click on “This Account” and enter the network username and password. It may need to be entered as machinename@domain.com (i.e. machinename@dmsi.com ) or as networkdomain\networkusername (i.e. dmsinet\networkusername) or perhaps just as the network username. The password will be the network password. If the services are already running, they will need to be stopped and started for the changes to take effect.
AR1800 - Why can't I cancel a direct SO
Agility
- Sales Orders
AR1815 - How to export and import a quote
Agility
- Quotes
How to export and import a quote Accidentally delete a quote for a customer or project? If the quote is in your test system, you can easily export it from there and then import it into your production environment. Follow the steps below to recover a quote from test and restore it in production.
DMSi recommends keeping your test system up to date and regularly completing backups in this environment.
Exporting a quote from your test system Log in to Agility in your test system Access Sales Orders/Quotes > Quote Entry Display the quote to export Select the Detail tab Select the Export icon to export the quote After the spreadsheet displays, save the file in a place where you can access it during the import
Importing a quote into your production system Log in to Agility in your production system Access Sales orders/Quotes > Import SO/Quote Select the Add new record icon to create a new import definition –or– select an existing Definition ID from the grid Note: If creating a new definition, it is suggested that you set all possible fields under the Ship-to Info and Quote Header tabs to Prompt for Value since the export does not contain that information. Doing this allows you to enter that information manually. See the Creating a new Definition ID section below for additional information. Select the correct Branch, if applicable Select the correct Processing Branch Select the Select a file icon and choose the file you saved from the export –or– enter the file location in the Transaction file field After all information has been entered, select Process to begin the import When prompted, select Yes to import the file Review any errors/messages after the import completes Access the quote in Quote Entry for verification
Creating a new Definition ID The steps below outline how to create a new Definition ID and are specific to importing a quote from your test system.
From the Sales Order/Quote Import window, select the Add new record icon Access the Action tab Enter a name for the Definition ID Select Quote from the Type dropdown Select <all> for the branch Select the Build a Directory Path icon to locate and choose the file you saved from the export –or– enter the file location in the Transaction File field Enter the number of header rows on the spreadsheet you saved during the export Select the radio button for Create New Quote(s) Select the desired radio button in the Break Orders by section Note: A PO or Reference number is required and will need to be added if not already in the import file. Access the Ship-to Info tab Select Prompt for Value for the following fields: Customer ID, Ship-to, Ordered by/Quoted for, Authorized to Charge, and Reference # Note: Selecting Prompt for Value allows you to enter these fields manually during the import since the exported file does not contain this information Select the appropriate column from the exported spreadsheet for the PO#, if applicable Access the Quote Header tab Select Prompt for Value for the following fields: Job, Message, Print on Forms, Send to WMS, Order Date, Sale Type, Sales Agent, Sales Agent 2, Sales Agent 3, Taxable, Tax Code, Payment Terms Code Note: Like the Ship-to Info fields mentioned above, these fields are not contained in the exported file. If any of the fields listed here do not apply, you can mark them N/A instead and they will be blank in Quote Entry once the import is complete Access the Quote Detail tab If you are importing pricing, unset Default from Cust Ship-to in order for the specified information to import Suggested: Select Value from the UOM dropdown Fill in all remaining applicable fields, selecting the appropriate corresponding column from the exported file when possible (fields labeled red are required) Access the Non-Stock Info tab - If Create Non-Stock Item was set to Fail when Not Found on the Quote Detail tab, you can skip this tab - If you need to create non-stocks, fill in all applicable fields, selecting the appropriate corresponding column from the exported file when possible Access the Tally tab Fill in all applicable fields, selecting the appropriate corresponding column from the exported file when possible After all information has been entered, select Save and Exit
AR1821 - Getting Started Using Suggested Purchasing (SPOs)
Agility
- SPO
Getting Started Using Suggested Purchasing (SPOs)
Below are the steps for setting up and running Suggested Purchasing (SPOs) in Agility.
*Please watch the " Understanding Suggested Purchasing in Agility webinar " available on the Wedge. Review our list of Common Purchasing Values and What They Mean (AR2079). You can also review Common SPO Troubleshooting Issues (AR2211) if you are currently using SPOs.
Set your EOQ Parameters (Purchasing > EOQ Parameters). Set the EOQ cost per purchase order line. Costs typically range between $4 and $8 (DMSI recommends using 6). Set the EOQ inventory carrying cost factor. Costs typically range between .25 and .4 (DMSI recommends using .3). For additional help doing these calculations, refer to the “ How to Calculate your Cost Factors ” article (AR1945). Verify you have a Purchase Type flagged as Use as Default for Stock Suggested Purchase Orders. (Data Files > Supplier Information > Purchase Order Types) Verify you have a Sale Type set to Yes for the Use in Reorder Calc’s field. (Data Files / Sales Order Settings / Sale Types) Verify Purchasing Parameters are correct (System Admin > Module Controls > Purchasing Parameters) Display 24 month usage Limit trend percentage % of EOQ in Surplus calculation Assign a Location for usage adjustments in the Locations Maintenance screen by having the “Use for usage adjustments” box checked (Data Files > Item Information > Locations). This prevents any errors from popping up when updating 24 month usage. Refer to the “ Basic System Setup for Running SPOs ” article (AR1946) for steps 2-5. Assign ABCs (Data Files > Item Information > Misc Settings > ABC Classification). For help, review the How to set up and run ABC Classifications. Set up Parameters first, then Calculate/Update ABCs. DMSI recommends A=70, B=20, C=7 and D=3 Can be set for All items (do this at minimum), Product Group Major/Minor, Supplier and Buyer. For additional help, refer to the “ How to set up and run ABC Classifications ” article (AR939). Verify Item info is correct. (Data Files > Item Information > Items) Branch Settings tab: Stock History Start Date ABC Reorder Info tab: Do Order Calculations/Include in SPO’s Minimum Reorder Point (optional) Minimum Delivery Delay factor (optional) Verify Item Supplier information is correct. (Data Files > Item Information > Items > Item Supplier icon). *These can be updated using our List of Reorder Info (AR2283) Cyberquery report available on the Wedge. Use the articles on the Wedge on how to download, run (AR2039), then make changes and import changes (AR2038) into Agility. Set your Primary Supplier as the supplier you will be using for SPOs. Verify lead times are accurate. If not you can manually update or mass update by primary supplier. (System Administration > Mass Update > Item Mass Update) Change the mass Update Action to Update Item Supplier Records. Select the Supplier that you would like to update the lead days for. Choose All Records or a range of items, product groups or buyers. Select the Field Name of Lead Time – Most Recent. Choose the Numeric value that corresponds to the average lead time from the supplier. Click Process. Change the Field Name to Lead Time – 2nd Recent. Repeat through 5th Recent. Verify the minimum package quantities are accurate (optional). Verify the minimum order quantities are accurate (optional). Refer to the “ Basic Item Setup for Running SPOs ” article (AR1939) for steps 8 and 9. Watch the SPOs Part 1: Basic System and Item Setup training video for steps 1-5 and 8-9. Watch the SPOs Part 2: ABCs and Usage training video for steps 7 and 11. Verify 24 month usage is correct (Stock Status > View/Update Usage icon) Can be manually updated. Can be updated with a Usage Import. Run Reorder Calculations (Purchasing > Reorder Calculations) Forward calculation for seasonal items. Should be run last day of the month. Backward calculation for non-season items. Should be run first day of the month. Forward calculation with Trending. Should be run last day of the month. Criteria can be saved and run via automated processing. For additional help, refer to the “ Setting up Reorder Calculations for Running SPOs ” article (AR1950). Run Suggested POs (Purchasing > Suggested POs) Choose the branch or branches. Choose your Supplier(s), Buyer(s) or Product Group(s). Choose All Items or only Items below the Buy Point. Choose if you want to calculate Surplus and corresponding branches. Create SPOs. Work your SPO View Details for the supplier. Review and make changes to items and quantities to be ordered. When finished, exit and Create PO. Write down examples of items that don’t look right, including items that aren’t showing up when they should be, items that are showing up and shouldn’t be and recommended buy quantities that look too low or too high. Use the Excel Reorder Calculations Worksheet on the Wedge to work through questionable values. Refer to the “ Running SPOs ” article (AR1951) for steps 13 and 14. Watch the SPOs Part 3: Running SPOs and SPOs Part 4: Advanced SPOs training videos for steps 13 and 14. If you use Surplus and Transfers, refer to AR1825-What is Surplus and How do I Review Surplus and Create Transfers . Contact Agility Support with questions about any exceptions.
AR1828 - Daily Balancing in Agility pre v545
Agility
- General Ledger
Daily Balancing in Agility Recommended only for versions pre 545; for versions after 545 DMSi recommends using AR19378 - How to set up GL Recon in Agility
Dmsi recommends a daily balancing process to ensure the Default accounts in Agility are staying in balance with sub-ledgers. This would include, AR Trade, AP Trade, AP Clearing/Recon, Inventory, Sales, and COGS. The four steps included in this article are 1) manual daily balancing 2) automated daily balancing 3) filling out the daily balancing worksheet and 4) common out of balance issues.
Manual daily balancing These are the manual steps for running the daily balancing. You can save the balances with the Daily Balancing Worksheet .
Here is the link to the Day End Procedures Checklist .
At the end of each day you will want to do the following for Daily Balancing:
Run the Data Warehouse (Data Warehouse > Update DW) The Data Warehouse will take 1-2 minutes to run and will let you know when it is complete. You must run the DW before running your reports. Run the Subsidiary Balancing Report (General Ledger > Reports > GL Subsidiary Balancing Reports ). Make sure your Report type is "Subsidiary". You will just need to hit “print” and the report will print to your screen. From there you can email the report to yourself, save it or print a hard copy. Run the GL Comparison Report (General Ledger > Reports > GL Subsidiary Balancing Reports ). Make sure your Report type is "G/L Comparison". You will just need to hit “print” and the report will print to your screen. From there you can email the report to yourself, save it or print a hard copy. Please Note: These 3 step paths can be saved in your Favorites.
Automate daily balancing Automating daily balancing will allow you to have the reports run automatically and be emailed nightly.
Data Warehouse Update Open the Data Warehouse Update (Data Warehouse > Update DW) Select All branches, then set your DW Update to Process Item Activity, Collect Inventory Value and Collect A/R Balances Click the Save Criteria For All button, then Save the name (commonly Called Data Warehouse Update)
Subsidiary Balancing Report Open the Subsidiary Balancing Report (General Ledger > Reports > GL Subsidiary Balancing Reports ). Make sure the Report type is Subsidiary. Click the Save Criteria for All button, then Save the name (commonly called G/L Subsidiary Balancing Report)
G/L Comparison Report Open the GL Comparison Report (General Ledger > Reports > GL Subsidiary Balancing Reports ). Make sure the Report type is G/L Comparison. Click the Save Criteria for All button, then Save the name (commonly called G/L Comparison Balancing Report)
Automated Processing Go into Automated Processing (System Administration > Restricted Processing > Automated Processing > Queue Maintenance)
Click the Create Job button Type in the Job Name (commonly Daily Balancing Reports) Type in the Job description Click the Add Task Icon Choose the Task Category of Update Process Choose the Process Type of Data Warehouse Update Choose the Process Name that you saved in the Data Warehouse Update section Click OK Data Warehouse Update has now been added as a task. Click the Add task button again Choose the Task category of Standard Report Choose the Report type of G/L Subsidiary Balancing Report Choose the Report name you saved in the Subsidiary Balancing Report section In the Report data type, choose either PDF or Excel spreadsheet In the ‘Sent to’ addresses section, type each email address the report should get sent to with a comma separating multiple emails Click OK The Subsidiary Balancing Report has been added to the Job Click the Add task button Choose the Task category of Standard Report Choose the Report type of G/L Subsidiary Balancing Report In the Report name field, type in the name you saved in the GL Comparison Report section In the Report data type, choose either PDF or Excel spreadsheet In the Email subject type in “GL Comparison Report” In the ‘Sent to’ addresses section, type each email address the report should get sent to with a comma separating multiple emails Click OK On the Jobs screen, click Save Click the Create Queue icon In the Queue name, type in a name (commonly Daily Balancing Reports) In the Frequency field, choose Daily In the Daily interval field, choose Once Daily In the Start time field, choose the time. This is a military value so 8:00 pm is 20:00 Click the Add Job icon In the Job locator, search for the Job you just created. Once you find it, click OK. Click the Save Queue icon Your reports will now run nightly assuming the Automated Processing Client is running
Enter values into the Daily Balancing Worksheet Enter your balances from each report into your Daily Balancing Excel file. There is a “section” for each of the AR, AP, AP Recon, Inventory, Sales, COGS and Invalid Postings. Enter the date (step 1). For each “section” you will put the balances from the Daily Balancing report (step 2) in the first column of the “section” Put in the balances from the Subsidiary report (step 3) in the second column of the “section.” Step 4 shows the file is formatted to calculate the differences between the Daily Balancing report and the Subsidiary report. Step 5 shows the change in variance from the prior day.
Common Out of Balance Issues For out of balances, please see the following Help links to get you started and assist in investigating. You can also search for “balancing” in the Agility Online Help .
For Balancing Reports (step 9):
For Period End Balancing (step 2):
And other Balancing help docs.
The following are common errors that cause out-of-balance entries:
AP and/or AR parameters set to manual post, but transactions have not been posted to the GL Reports were not printed at the same time Backdating transaction such as invoices and receivers Posting both debit and credit side of payables and/or receivables to the same account Dropping A/P Recon records and using the A/P Clearing account as the offset Inventory adjustment reason codes set to post to the Inventory account which will leave a net impact on the GL of zero, while increasing/decreasing the on hand value report. Sales account parameters set incorrectly
AR1839 - How to manually process Marvin Orders
Agility
- Interfaces
1. Log into the OMS back office system. You can find this URL by going to E-Commerce > Interface Maintenance > select the Web Service Options tab for the Form/Interface Type of MARVIN.
2. Copy and paste the URL from the “URL” field into an IE session. Please make sure IE is used, otherwise the XML file you attempt to generate will have errors.
3. Once you have accessed the Marvin site by entering in the URL in IE, enter in the login credentials that are specified in Interface Maintenance.
4. Click on “GetOrdersByTimestamp”.
5. Specify your search criteria. To get your startDate, just copy and paste what is in your Last Order Retrieval field in Interface Maintenance to retain the correct formatting.
6. Adjust the startDate and endDate criteria as you see fit. Populate includeFeatures with “FALSE” and includeTextDetails with “TRUE”.
7. Click Invoke to bring up a single xml file with orders created within the date and time range you specified.
8. Save the XML file by clicking on the IE Tools icon > File > Save As and note the location to which you save the file.
9. To import the file, go to E-Commerce > Send/Receive > Select an Interface type of Marvin Windows. Change the Source of data to process value to “Load file from disk”.
10.10. Select your file by clicking on the icon to the right of the “File(s) to load” field, and click Run.
11.11. Your files will then be received, and you will get your normal confirmation in the Processing Activity Log that pops up once the send/receive process is complete.
AR1841 - How to automatically send shipping confirmations to customers
Agility
- Sales Orders
Question: I have a customer that would like email reminders of orders the day before the delivery. Is there an "Auto Process" that will do that?
Answer:A sales order viewer can be set up and automatically emailed to customers for an order confirmation of orders to be shipped the next business day.
First, set up a sales order viewer to look for customer orders.
Go to Sales Orders Quotes/Viewers/SO Viewer.
Click on Branch and choose the appropriate branch or All branches.
Click on the Customer button and choose the correct customer.
Click on Date Criteria and set the Expect Date to be through the next business day. Use Relative Date and choose the Run Date. The To field should have a +1 which will show shipments for the next day. Make sure no other dates are set (like Order Date or Invoiced Date).
Click on Order Phase. Choose Orders and Staging Records, then make sure Staged is the only Selected Options. This will select any shipments that are in a Staged status.
Click on Display type. If you only want transactional information, choose Summary. If you want item information as well, choose Detail.
Click on Column Display. Choose the appropriate fields you want displayed (like branch, tran ID, ship via, pay terms, customer PO, item, quantity and any other fields). Choose the appropriate sort order.
When the viewer information is correct, click Save. Create a New Record and save the viewer with a name like “Expected Shipments for Customer ABC”.
When finished, run the Viewer to make sure the data is correct.
Next you will want to set this viewer up to run through Automated Processing.
Open System Administration/Restricted Processing/Automated Processing/Queue Maintenance.
Determine if you have an existing job that you can add this viewer in or if you need to create a new job.
If you have an existing Job to add this viewer to (like a daily sales report job, or daily data warehouse job), find the job and double click on it. If you need to start a new job, click on the Create job button. Type in your Job name and Description.
Click Add Task.
Under Task category, choose Viewer.
Under Viewer type, choose SO Viewer.
Click the magnifying glass next to Viewer Name. Find the Viewer you just set up, click on it and click OK.
Put in a ‘Sent from’ address and an Email subject.
Under the ‘Sent to” addresses, type in your customer’s email address. If there are multiple email addresses, separate them with a semi-colon.
Click OK to finish adding the Task to the Job. Verify the Task appears in the grid below the Job.
If you added to an existing Job, no further steps are necessary. If you created a new Job, click on the Queues tab.
If you would like to attach the Job to an existing Queue, find the Queue and double click on it. If you need to create a new Queue, click the Create Queue button. Type in the Queue name. Set the Frequency to Daily and the Daily interval to Once Daily. Choose your Start time.
Click the Add Job button. Find your Job, click it and then click OK.
Click the Save Queue button. Your viewer will now run automatically and email the customer a list of their expected shipments.
You may need to set up a separate SO viewer for shipments that will go out on Monday (since the expected ship date would be +3 not + 1 when running this on a Friday). You can also set up additional viewers for different customers that request a list of orders that are shipping. You will want to set up one viewer for each customer.
Follow these steps to set up your viewers and add them to the Automated Processing so they can be automatically sent to customers.
AR1849 - Why are the expect date for the Sales Order detail line and the header different dates?
Agility
- Sales Orders
Why are the expected date for the Sales Order detail line and the header different dates?
Question: When looking at an order in the SO Viewer, the expected date for the detail lines is different in some cases from the expected date in the header of the order. How can this be?
Answer:
The expect date field in the viewer is the expected date from the header of the order. The Expect Date (detail) field is the expected date that is assigned to the detail line on the order. These two dates can vary.
If the order is a ship complete and the system is calculating the date (it is not overridden) , they are typically the same and the expect date in the header of the order is the latest date from all the detail lines.
If the order is NOT a ship complete and the system is calculating the date (provided it is not overridden), the header expect date is the earliest date from the detail lines left to ship.
If the expected date is overridden in the header or the details, these rules do not apply. If the header date is overridden, generally provided the system calculated date for the detail lines is not later than the overridden date, the expect date on the detail lines is set to the header overridden date.
On sales orders that affect inventory, the detail expected delivery date determines when the system includes the item in a pick file or shipment.
The following is the Agility help documentation on calculation of header and detail expect dates:http://documentation.dmsi.com/agility/Prod/Sales_Transactions/expecteddeliverydateandrouteassignmentonsalesorders.quotes.htm
AR1887 - Expected Delivery Date Change Notification Options
Agility
- System Administration
One of the most useful notifications that exist in Agility is the ability for the system to notify you when the expected date changes on the detail lines of an order. Many events can trigger this notification and the idea behind the notification is to provide you information on a timely basis when the date you have acknowledged to a customer is different than the current expected delivery date.
This notification, unlike most other notifications, is not sent for each event that occurs. Rather, it is triggered to be sent to the appropriate user as part of an automated process. This automated process groups all notifications for a user and sends the user one email instead of many. Typically, this notification is set to run every five minutes.
The notification improves the visibility of expected delivery date changes, allowing you to notify sales agents and customers of these changes so they can plan accordingly.
When printing an order acknowledgment and the 'Acknowledgment sent to customer' field is set on the Select Laser Printer window, the system tracks and displays the sales order header and detail expected delivery dates. If the header or any detail expected delivery date is changed, and the order acknowledgment is printed again, the modified dates are tracked and a notification is sent. The 'OA exp delv date' and the 'Orig OA exp delv date' fields can be added to Sales Order Entry layouts (via the myUI Designer), custom views and sales order viewers.
Additionally, the 'Exp Delv Date Change' notification gives you control over what notifications are sent and who they are sent to when detail level expected delivery changes are made. These settings include:
Notifications can be set up to include or exclude date changes made from different areas of the system so you can customize the recipients based on the source of the date change: Notifications can be limited to work order parent items Sales order details being updated to an earlier date can be excluded from notifications Sales order details outside of a # of days threshold can be excluded from notifications Sales Order Entry Transaction Analysis Areas outside of SO Entry and Transaction Analysis, such as viewers, changes to linked transactions, etc. The notification itself is triggered by a system-defined Automated Processing queue called 'Notifications - Exp Delv Date Change'. Changes to detail expected delivery dates are stored in a Notification Transaction Queue. When the 'Notification - Exp Delv Date Change' automated process is run, the date changes are evaluated and the appropriate notifications are sent based on the notification maintenance record(s). This queue was created automatically and set to run every 5 minutes. When you have created a ‘Exp Delv Date Change’ notification, verify the 'On Hold' field on this queue has been unset.
Related Documentation: See the following for events that trigger notifications (search for Exp Delv Date Change):
http://documentation.dmsi.com/agility/prod/wwhelp/wwhimpl/js/html/wwhelp.htm#href=System_Administration/eventsthattriggernotifications.htm
Also see field descriptions for notifications for more information on the options available within the notification details:
http://documentation.dmsi.com/agility/prod/wwhelp/wwhimpl/js/html/wwhelp.htm#href=System_Administration/fielddescriptionsfornotificationdetails.htm
AR1945 - How to Calculate your Cost Factors
Agility
- SPO
How to Calculate your Cost Factors Purchasing Cost Use the following to determine the Purchasing Cost (Amount of money it costs to buy 1 line item on a purchase order):
Cost of Purchasing Staff $_________ The total annual expense for staff that handles purchasing and negotiating costs for all incoming merchandise. Cost of Accounts Payable Staff $_________ The percentage of cost as a dollar amount for the accounts payable staff creating invoices, paying the invoices to your suppliers and researching inventory discrepancies. Cost of Overhead $_________ The percentage of cost as a dollar amount for the overhead on things such as computers and phones. Cost of Receiving $_________ The percentage of cost as a dollar amount spent receiving the incoming merchandise and entering the receipt into Agility. =================================================== Total Costs $_________ Totals Costs Total Annual Cost / Number of PO Line Items = Purchasing Cost Factor $_________ / $_________ = __________
To get the total number of PO line items, run a PO viewer in detail view for all POs created in the last year. In the bottom right of the screen it will tell you record 1 of X. The number X is the total number of PO line items for the year.
(Cost typically is between $4 and $8, use a default of 6 if you need to get started without doing the calculations)
Carrying Cost Use the following to determine the economic order quantity carrying cost factor (amount to carry $1 of inventory for 1 year):
Warehouse Space $_________ The annual expense of warehouse space. If all space is company owned, use the cost of leasing equivalent space in the area. Include taxes and insurance paid on buildings in this amount. Taxes $_________ Actual taxes paid in the last year on inventory. Taxes on buildings should be part of the warehouse space cost figure. Insurance $_________ Insurance premiums paid in the last year on inventory. Insurance on buildings should be part of the warehouse cost figure. Shrinkage/Obsolete Items $_________ The value of inventory which was adjusted off during the last year, either because of physical count differences or because the material was deemed non-saleable. Material Handling $_________ The total annual expense in labor and material handling equipment needed to stock all incoming merchandise. This should also include the cost to move and count inventory during the year. Customer order-filling expense is not included. Cost of Money $_________ The interest that could have been earned in a safe investment if the money had not been used to purchase inventory. =================================================== Total Costs $_________ Totals Costs Total Costs / Avg Inv. for Past Year = Carrying Cost Factor $_________ / $_________ = __________
Can find the average inventory for the last year by running the Inventory Turns/GMROI report for last year. Total is at the bottom of the report.
(Cost typically is between .25 and .4, use a default of .3 if you need to get started without doing the calculations)
AR1950 - Setting up Reorder Calculations for Running SPOs
Agility
- SPO
Setting up Reorder Calculations for Running SPOs Setting up Reorder Calculations for running SPOs is an important step to ensuring your buyers are able to handle the inventory needs of your company at all times. Saving your buyers time, increasing efficiency in purchasing and reducing inventory costs are all goals for using SPOs. In order to use SPOs in Agility effectively, you must ensure reorder calculations are being run regularly for all your stock items.
When Reorder Calculations are run, Agility calculates a Reorder Point, safety stock, EOQ and projected monthly usage for each item Reorder Calculations are run for.
Determine how you want Agility to do Reorder Calculations for your different products or product lines. A general rule of thumb is if the product/product group is seasonal in nature, do a Forward calculation. For products that are not seasonal, a Backward Calculation is best.
Setting up Reorder Calculations Go to Purchasing > Reorder Calculations.
Specify the Calculate criteria for your first set of items. You can calculate base on a range of Buyer, Item, Product Group or Supplier.
Choose the From and To range.
Next, choose the Calculate timeframe, either Forward or Backward. Agility will default the Number of Months to 3. Change this for a longer or shorter timeframe.
For a Forward timeframe, you can choose No Trend, Trend last 90 days or 180 days. Agility will calculate a trend based on the last 90 days of this year compared to the same timeframe last year and adjust the projected monthly usage based on this trend. Refer to the Agility help doc for Reorder Calculations to see the exact calculation.
For a Backward timeframe, you can choose to increase or decrease the buy point by a %.
When you have finished setting up your first set of products the way you want to run the Reorder Calculations, use the Save Criteria to save the calculation. This will allow you to Open the saved criteria at a later time to run Reorder Calculations manually or use Automated Processing to automatically run Reorder Calculations.
Once you have set your criteria and saved it, repeat the steps for each of the products you will be using with Suggested Purchasing. Click on the Open Folder to see the list of saved criteria.
Running Reorder Calculations DMSI recommends using Automated Processing to automatically run your Reorder Calculations monthly.
Running via Automated Processing Go to System Administration > Restricted Processing > Automated Processing > Queue Maintenance.
Click the New Job icon. In Job name, type in Reorder Calculations Forward. Type in the Job description.
Click the Add Task button.
Under Task Category, choose Update Process. The Process Type will be Reorder Calculations. Under the Process Name, click the magnifying glass to open the saved Reorder Calculations you just set up. Choose the first Forward Calculation that was set up and click OK. Verify the processing branch is correct and click OK.
Repeat the process of Add Task for each of your Forward Calculations. When finished, click the Save Job button.
Click on the New Job button and repeat the steps for your Backward Calculations. When you are finished, you should have all of your Forward Calculations in one job and all your Backward Calculations in a second job.
Click on the Queue tab. Click on the Create Queue tab. In the Queue Name, type in Reorder Calculations Forward. For Frequency, choose Monthly. In the Interval, choose Last day of calendar month. Your Daily interval will be Once daily. Set the Start time sometime after the end of business. Start time is in military hours, so 6 pm would actually be 18:00. Click Add Job and choose your Job of Reorder Calculations Forward. When finished, click the Save Queue button.
Repeat the steps to create the Reorder Calculations Backward queue. Your Interval will need to be First day of calendar month. You will want the time to be sometime before the start of business. When finished, click the Save Queue button.
Agility will run the jobs automatically at the times specified. This will keep you from having to remember to manually run each of the Reorder Calculations.
Running Reorder Calculations manually Go to Purchasing > Reorder Calculations.
On the last day of the month after the close of business, you will want to run your Forward Calculations. In the Reorder Calculations screen, click the Open criteria button and select your first Forward Calculation. Click Calculate. When it is finished, open your second Forward Calculation. Repeat until you have run all your Forward Calculations.
On the first day of the month in the morning, you will want to run your Backward Calculations. In the Reorder Calculations screen, click the Open criteria button and select your first Backward Calculation. Click Calculate. When it is finished, open your second Backward Calculation. Repeat until you have run all your Backward Calculations.
You will need to manually do each of these steps on the first and last day of each month if you are not using Automated Processing.
AR1951 - Running SPOs
Agility
- SPO
Running SPOs Suggested Purchasing in Agility is an efficient tool for buyers who are looking for ways to make buying decisions on what to buy and how much to buy. Agility will do the heavy lifting of calculating when to buy items, how much to buy, and give the buyers a centralized place to review the recommendations, making changes if necessary. Suggested Purchasing allows buyers to streamline their buying, giving them time to focus on the items that are most important to the success of your business.
Purchasing > Suggested POs
Create Suggested PO Specify the criteria to use for generating the Suggested PO’s.
-Create SPO’s for items for replenishing stock, items tagged to fill from a PO, or both. -Choose from a list of product lines, suppliers or buyers. -Include only certain ABC items or all items. -Include items with a recommended buy or all items regardless if there is a need to purchase.
Once you have your criteria set, use the save buttons at the top to save your criteria. Set up multiple views to match the different ways you run your SPOs.
Click Create SPOs.
Review Suggested PO Click on the row you would like to look at and click View Details.
On the details screen, the items will appear in the middle of the screen. The details section will show the items along with a recommended buy, unit cost and UOM. All three of those fields can be changed to what you need it to be.
Lower on the details section is data used to calculate the recommended buy for the selected detail.
Your 24 month usage for the item is also displayed in the bottom portion of the SPO screen.
For additional options for the SPO details, you can click on the Options button (or right click anywhere in the grid). From here you can adjust costs, view stock status, print a usage report or add messages.
For items that may have multiple suppliers, you can also change the item to purchase from a different supplier. Highlight the item or items and change to the new supplier.
When you have finished updating your items and quantities, just click Exit. Your work has been automatically saved.
Create PO To create a PO, click on the Create PO button in the bottom right of the Suggested POs screen. Fill out the required information in the Info for PO screen. Click OK when finished. Your PO will then be ready to send to the supplier.
If you would like to have a supplier or multiple suppliers give you quotes, you can click the Options button from the Suggested POs screen and choose Print PO Quote Request. This will allow you to print a copy of the SPO without costs that can be sent to a supplier or multiple suppliers.
AR1959 - How to use SO Viewers to quickly find orders
Agility
- Viewers
AR1974 - WMS FAQ – “WMS and Agility are not Communicating”
Agility
- WMS
WMS FAQ – “WMS and Agility are not Communicating”
Symptom: Orders/Transactions in Agility are not showing up on the gun (not showing up in WMS).
Action 1 In Agility, go to Inventory Control > Warehouse Management > WMS Transaction Maint. Change the Activity Type to Outgoing, hit Search. Look at the Status Column, if you see “P” and “S”, move on to the next action. If you see all “R”, restart the Agility WMS client (also known as “Agility WMS Controller”, “Agility WMS Processor”).
Action 2: Go to Inventory Control > Warehouse Management > WMS Log Maintenance. Change the Logging Leve to Communication and hit Search. If you see a cluster of repeating messages reading “WMS Send Data executed…” and “No data to process, exiting”, this means the Agility WMS Client is running and checking for data to process… in other words, no need to restart the client yet.
If the log is blank, or if you see an error stating “Cannot Connect to Webservice…” move on to action 3.
Action 3: Go to System Administration > Module Controls > WMS Parameters. Click the Test Connection button. If you quickly get a pop up with a status id of “OK”, Agility is able to connect to the Majure Data (WMS) webservice.
If you get a pop up that reads “Error connecting to Webservice…”, Agility cannot connect to the Majure Data webservice. Have you recently changed the username or password of the Agility user profile that is used to by the WMS? Majure needs to know this information, make sure they aware of the changes.
If you are still experiencing issues, contact both Majure Data and Agility support.
Spport360@dmsi.com
support@majure.com
AR1976 - Saved viewers in Sales Order Entry
Agility
- Viewers
SAVED VIEWERS IN SALES ORDER ENTRY
Agility viewers are powerful query tools that allow users to quickly find the information they need when they need it. Agility has been designed to streamline these results when running a saved viewer from Sales Order entry by defaulting the customer ship-to as criteria into the viewer so the results are specific to the customer that the order is being placed for. This feature saves time during order entry by skipping the viewer criteria window and limiting the results to review.
Saved viewers can be accessed from the Information tab within the Saved Viewers menu option on the Sales Order Entry ribbon. Saved Viewers can also be added to a custom ribbon tab as well as the Quick Access Toolbar for easy access.
The same set of saved viewers are also available in the OrderPad to allow for quick access to customer order information when using the OrderPad.
Once Saved Viewers have been saved for one user, they can be copied from that user to other user's in similiar roles by going to System Administration > Mass Updates > Copy User Customizations.
AR1994 - How to display Login Info for PartnerView
Agility
- PartnerView
Method 1: Log Viewer
1. In Agility, access System Administration > Security Administration > User Profiles to verify the Use debug feature flag is set. Users in Agility must have Use debug feature set on their user profile to display in Log Viewer. 2. Log into PartnerView. 3. After logging in, click the user’s name to activate the drop-down and select Settings . 4. After clicking Settings , Select Log Viewer on the left-hand side. 5. You can click Search to display when users last logged into PartnerView. This will only display users that have Use debug feature set on their user profile.
Method 2: Run Cyberquery Report
1. In Agility, access Report Writer > VCQ Report Writer. Close the report wizard and click on the language editor icon (keyboard icon). 2. Copy and paste the following into your enquiry:
viewpoint native;
define file zasc = access asc_product_user, set asc_product_user:user_obj = gsm_user:user_obj; file xasc = access asc_product, set asc_product:asc_product_obj = zasc:asc_product_obj; file xproduct = access gsc_product, set gsc_product:product_obj = xasc:product_obj; where xproduct:product_description <> "Agility" and xproduct:product_description = "PartnerView" and time (gsm_user:last_login_time) not one of 00:00 list /duplicates/domain="gsm_user" xproduct:product_description/noheading sorted by gsm_user:user_login_name xproduct:product_description top of gsm_user:user_login_name/noheading gsm_user:user_login_name user_ctl:email_address gsm_user:last_login_date time (gsm_user:last_login_time) 3. Click on the run icon or hit ‘F6’ on your keyboard to process the report.
AR2009 - How to use customer quicklists in PartnerView
Agility
- PartnerView
How to use customer quicklists in PartnerView
In order to use customer Quicklists in PartnerView, the steps outlined below must be completed in Agility.
Create and Grant Access to Quicklist Criteria
In Agility, access System Administration > System Configuration > System Config > Web Services/PartnerView tab In the PartnerView section, set ‘Display customer item quicklists in product search’ field. System Administration > Restricted Processing > Automated Processing > Customer Quicklist Criteria The Customer Item Quicklist Criteria window displays. Select New to create a new record. Select the appropriate branch or all branches. Select the appropriate option for ‘Summarize items by’. Valid options are: Sold-to, Ship-to, or Sold-to and Ship-to. Select the appropriate option for ‘Customer selection’. Valid options are: All customers, Customer, or Customer Group. If you selected customer or customer group in the previous step, enter the appropriate customer ID or customer group. Note that your criteria selections are now reflected in the criteria name at the top of the screen. You will need this information when you create your automated process. Select what you would like to build your quicklist by:Hits – List of top ranked items based on the number of times the item has been sold to the selected customerTotal Sales Amt – List of top ranked items based on the total extended sales amountGM% - List of top ranked items based on the gross margin percentage
Select the period of history to include:In the first box, enter a numeric value such as 12 In the second box, select either months or days Enter a value for the number of top ranked items to include. For example, entering a value of 25 limits the quicklist to a maximum of 25 items. Select Save. Create Automated Process for running Customer Quicklist Criteria on a regular basis
System Administration > Restricted Processing > Automated Processing > Queue Maintenance Select Create job to create a new job for your quicklist criteria and fill in the following fields: a. Enter a Job name for this process. b. Enter a Job description for the job name. Save the record. Select the Add button. In Task Settings, complete the following fields:Task category : Select Update Process.Process Type : Select Customer Item Quicklist.Process name : Select the locator for Process name and in the task name column and select the criteria name created above.Processing branch : This defaults to the branch you are currently logged into. Change if necessary. Select OK. Select the Save icon to save your job. Select Queues tab. In Queue Maintenance, complete the following required fields:Queue name : Enter a queue name for this queue.Frequency : Select the frequency for running your queue.Interval : If you select a frequency other than daily, select the appropriate interval.Daily interval : Select a daily interval.Start time : Enter a start time for your automated process using a 24-hour clock. Consider running your automated process during non-business hours for maximum efficiency. Select the Save icon. Select the Add button. Select the job name created above. Select OK. Select the Save icon. Select Run Now or wait for your automated process to run. Access your quicklist in PartnerView
Log in to PartnerView. Select the Products tab. Select Advanced Search. Select the appropriate quicklist from the Quicklist drop-down. After selecting the Quicklist from the dropdown, select View Quicklist to display the Quicklist that was selected.
AR2028 - How to Move Material to a New Location Outside of Inventory Adjustments
Agility
- Inventory Control
How to Move Material to a New Location Outside of Inventory Adjustments Material can be moved to a different location outside of Inventory Adjustments using the On Hand Summary Viewer, Specify Commit/Uncommit, and Specify Tags to Commit windows when accessed from Stock Status, Reman Entry, and Sales Order Entry.
From the On Hand Summary Viewer or Specify Commit/Uncommit screens 1. Use the Assign New Location button after selecting a record in the On Hand Summary Viewer or Specify Commit/Uncommit screens to display a pop-up to Assign New Location
2. Enter or select a new location and select OK to generate a location adjustment for the selected record
From Tags to Commit 1. Use the New location field in Specify Commit to open Tags to Commit and generate location adjustments for tags you are committing
2. Select New Location in Tags to Commit to move the tag(s) to the new location and commit the tag(s) to the order
Setup Considerations Action allocation security 'Allow new location inventory adjustments', controls whether you can generate location inventory adjustments. The action defaults to granted. Deny the security action to prevent location inventory adjustments from any Agility screens.
The System Parameters screen 'New location reason' field is used to specify a default reason to apply when generating location inventory adjustments. The value from this field automatically applies to location adjustments generated outside of the Inventory Adjustments screen. Additionally, the value defaults into the 'Reason' field in the Inventory Adjustments screen but can be overridden if desired.
AR2038 - Running the List of Reorder Info, correcting data and importing into Agility
Agility
- SPO
RUNNING THE LIST OF REORDER INFO, CORRECTING DATA AND IMPORTING INTO AGILITY Run the List of Reorder Info and make changes 1. Run the List of Reorder Info query from VCQ Reports or your dashboard.
2. Follow the prompts (branch, buyer, supplier, product group and stock items). The report will print to your screen.
3. Export the report to Excel by clicking on the View in Spreadsheet button. 4. Review the data in the spreadsheet. Make changes as needed (ex: lead days, min pack, min ROP, min DDF, etc). 5. If you are using dimensional items, all item supplier information MUST be updated on the 00x00x00 record. All reorder information MUST be set on the dimensional record. 6. Save the updated spreadsheet on your desktop. Close the spreadsheet.
Build the Item Import
7. In Agility, click on Data Files > Item Information > Item Import.
8. Click on the Default Layout button.
9. Click on the Select a File button. 10. In the Select File screen, find the file you saved for the reorder info and then Click Open in the bottom right corner. 11. In the Build Path screen, click OK. 12. You will be back in the Item Import screen. The screen will have the Default Layout Definition highlighted. Click the Update Record button or double click on the Default Layout Definition. 13. In the Item Import Definition Maintenance screen, change the Definition to be the name you would like to use for all future updates (something like Item ROP Info Update, etc.). A couple of additional changes will need to be made. In the Action tab, type 2 in the value for the Number of header rows field. In the Updates to items should flow to all existing dimensions, change the value to Yes. Agility has auto-mapped all the fields in the spreadsheet so there is no additional changes that will need to be made. 14. When you are finished, click the Save button in the top left corner. 15. The Add/Update Confirmation window will pop up. Click on the Create New Record button. This will overwrite the Default Layout Definition so that it can be used at a different time. 16. Click the X in the top right corner of the Definition Maintenance screen. This will take you back to the Item Import screen.
Run the Item Import to update Reorder Info data
17. You can now run this import by clicking the Process button in the bottom right of the screen. The Question window will open asking if you want to Import the file. Answer Yes. 18. Agility will now run the item import. 19. Wait for the Item Import Audit screen to load. The Item Import Audit will show you how many records were updated, if there were any warnings and if you had failures. You can review the audit file for any discrepancies and make corrections as necessary. Re-import if needed. 20. To make additional changes, run through steps 1-6 to get a new file, make corrections and load into Agility. 21. To choose the new file to load in the Item Import screen, scroll down in the Item Import and find the definition you created. Click on the line. 22. Next, click on the Browse button for the Transaction file. 23. When you have the correct file, click the Process button in the bottom right of the screen. The new file will then be imported into Agility with any new corrections made to the spreadsheet. 24. Verify the corrections were made to your items in Agility using the List of Reorder Info query. Repeat as necessary to correct data for your items. Contact Agility Support if you have additional questions.
List of Reorder Info using Inventory Viewer The inventory viewer has been updated to include most of the fields the List of Reorder Info query contains. It is not an exact match but will get almost all the same exact fields.
To use an inventory viewer to get this info, you will need to open Purchasing > Viewers > Inventory Viewer
In Column Display, choose these fields (in this order): Branch, Item, Buyer ID, Size, Description, Primary Supplier ID, Primary Ship-from Sequence, Last Lead Time, Lead Time 2, Lead Time 3, Lead Time 4, Lead Time 5, Min Order Qty, Min Pack, UOM, Do Order Calculations, Stock Flag, Min Reorder Point, Order Point, Reorder Point, Cost UOM, EOQ, EOQ Fixed, Safety Stock, Safety Stock Fixed, Min Delivery Delay Factor, Last ROP Calc Date, ROP Cal Method, ROP Calc Method Fixed, History Start Date, ABC Code, Last Receipt Date, Last PO Cost.
To use this instead of the query, you will need to build the Item Import layout (you will need to manually map all the fields, or use the List of Reorder Info spreadsheet as a starting point to auto-map then make changes accordingly).
AR2039 - How to download the List of Reorder Info query and run it.
Agility
- SPO
How to download the List of Reorder Info query and run it. Log into the Wedge. Go to dmsi.com/wedge . Put your username and password in and click Login to Account. Click on the Articles tab. Choose a category equals of Cyberquery Samples, then type Reorder info the Articles contains field. Click Search. Click on the link for the List of Reorder Information article. A new window will open with the text of the query. Highlight the text that contains the query (starting at /* This query will...). Then type Control C (this is Copy). Go into Agility and click on the Report Writer button. Then click on VCQ Report Writer. The Cyberquery report wizard may pop open: if it does, click Cancel. Click on the Select Language Editor button to switch the view. Click your cursor into the Enquiry section and paste the query (Control V). To save the query, click on the Save button. The Save enquiry as box will come open. Click on the Up One Level button to move to the cq_reports folder. In the cq_reports folder, put list_of_reorder_info in as the File Name and click Save. You can now run the report by clicking the Run button (or hitting the F6 button). When you run, you will need to specify some answers to prompts about branch, buyer, supplier, product group and stock items. If you would like to run the report from your dashboard or from the VCQ Reports, you will need to compile the report. To compile, go to Report Writer/VCQ Report Compiler. In the Report name field, type in list_of_reorder_info.eq. Click Run. A report will print to your screen. If the compile went through, it will say Enquiry “list_of_reorder_info” compiled-no errors. To run the report from the VCQ Reports, go to the Report Writer/VCQ Reports. Click the + next to the cq_reports folder. Find the list_of_reorder_info report, click on it then click Run. To add the report to your dashboard, go to the Saved Reports section of the Dashboard. Click the Add Custom Report link. In the Report name field, type in list_of_reorder_info.eq. In the Text to display, you can change this field to be whatever you want to call your report. Click OK. To run it, click on the Run link next to the name of the report.
AR2055 - How to Setup / Install Automated Processing
Agility
- System Administration
HOW TO SETUP/INSTALL AUTOMATED PROCESSING Set up Auto Process User in Agility 1. Go to System Administration/Security Administration/User Profiles. 2. Type "autoprocess" in User ID. 3. Type "Auto Process" in the User name field. 4. Click the "Password never Expires" and "User for 3rd party batch processing". 5. On the Products tab, choose "Agility" and move to the Selected Products side. Click Save. 6. In the Change Password screen, type "autoprocess" in the New password field and the Confirm password field. 7. Unset the Force password change at next login flag and click OK. Set up Automated Processing 1. To setup or install Automated Processing, install the Client on a PC that has an internet connection and is always on. Note that you will need the '.NET Framework 3.5' installed to run the client. This program does not come installed by default on Windows 10 machines. To install, please follow the instructions below: First you will need to navigate to software.dmsi.com, your login is your RDP username (without dmsi\) and RDP password. Once logged in you will click on the following path to get to the client to download: Releases > Agility > (Page 4) > Agility AP > Agility_AP_v7-1.exe
2. You will need the following values to complete the Install: • Your Unique Soap URL • Your Agility Automated Processor Username • Your Agility Automated Processor Password **Contact support to obtain your FULL Unique Soap URL if needed**
3. Run the Wizard and Accept terms of the license agreement.
4. Next you will be asked to enter the Website URL. a) Enter your Full unique customer Soap URL b) Click Test Connection a. If connection failed, verify accuracy of entered data, continue to re-test connection until successful. c) Click Next
5. Make sure the Agility the Automated Processing service box is Selected, Click Next. 6. Enter the WebService Username. (Refer to step 2 of "Set up Auto Process User in Agility” section above). 7. Enter the WebService Password. (Refer to step 6 of "Set up Auto Process User in Agility” section above).Troubleshooting If the Automated processor is not running: Go to the start menu. Right Click on My Computer (or Computer). Select the Manage option. Click on Services and Applications (or Services). Click on Services (again). You will now see a list of services on that PC. Look for a service that starts with Agility; typically, “Agility Automated Processor”. Right click on the service and select Start.
AR2071 - How do I resolve my errors in my A/R ACH Exceptions Report?
Agility
- A/R
Run Cyberquery Sample for Exceptions Report from AR18604
Exception Reason: Invalid/missing customer bank
This exception is a result of an ACH payment being made when the related customer bank record has been deleted prior to being sent in the NACHA file. - If the customer bank record is missing, it will need to be added back, with the ‘Use for ACH processing’ and ‘Approved for ACH processing’ fields set. You can then generate and send the NACHA file by going to Accounts Receivable > Payments > ACH Processing > Payments and Pre-notifications > Click the Send button. - If the payment should not have been made, simply reverse the payment by going to Accounts Receivable > Payments > Payment Backout.
Exception Reason: Customer bank not approved for ACH
This exception is a result of an ACH payment being made and the related customer bank record has had the ‘Approved for ACH processing’ field and/or ‘Use for ACH processing’ field unchecked prior to being sent in the NACHA file. - If either of these fields should not have been checked, go back into the Customer Bank record and check ‘Approved for ACH processing’ and ‘Use for ACH processing.’ You can then generate and send the NACHA file by going to Accounts Receivable > Payments > ACH Processing > Payments and Pre-notifications > Click the Send button. - If this payment should not have originally been made, simply reverse the payment by going to Accounts Receivable > Payments > Payment Backout.
Exception reason: G/L account not valid for ACH
This exception is a result of the ‘Use for ACH processing in A/R’ field being unset in the G/L Acount-Bank Information screen. - If this field should not have been unchecked, then check the field by going to General Ledger > Chart of Accounts > Accounts Maintenance > Bank Info. - If payments should not have been made on this G/L account, simply reverse the payment by going to Accounts Receivable > Payments > Payment Backout.
Exception reason: Invalid target address, Login ID or Password
This exception is a result of the target address, Login ID or password containing invalid information. - Work with your bank to determine the correct values for these fields, then update them by going to System Administration > Restricted Processing > File Transfer Maintenance and select the bank and account number in question. Use the ‘Test Connection’ button to verify that this information is correct.
Exception reason: Missing File Transfer Maintenance record
This exception is a result of a File Transfer Maintenance record not existing to transmit the ACH file. File Transfer Maintenance Records must be created for each unique bank name, routing number, and account number combination. - Create the File Transfer Maintenance record by going to System Administration > Restricted Processing > File Transfer Maintenance. Work with your bank to determine the valid values that belong in these fields.
- If this is a result of multiple G/L banks pointing to the same account number have different bank names. Find the difference in the bank names by reviewing the ACH Bank Accounts in the G/L Files Listing by going to General Ledger > Reports > G/L Files Listings > ACH Bank Accounts. Correct the bank names in General Ledger > Chart of Accounts > Accounts Maintenance > Bank Info > Bank name.
Exception reason: Maximum number of 36 files per bank/day has been exceeded
This exception occurs when more than 36 files per bank per day are attempted to be sent.
- Review the frequency of the automated processing queue run to ensure that this is sent no more than 36 times a day by going to System Administration > Restricted Processing > Automated Processing > Queue Maintenance and pull up the queue and job in question. - Because the payments do not get sent, the payments will need to be sent the following day when the number of files per bank per day will reset to zero.
AR2096 - Agility Mobile Warehouse Tools - Verify Tags
Agility
- Agility Mobile WH Tools
Agility Mobile Warehouse Tools - Verify Tags Verify Tags is used to perform tag verification for cycle counts. In order to perform the tag verification, physical inventory workfiles must be created and frozen.
Steps to Verify Tags Select Verify Tags. A list of frozen PI Workfiles is displayed for the branch you are logged into. For each workfile , the following information displays:A – Workfile ID, Sequence, and Description
B – Selection Criteria used to create the workfile
C - Location
Select a workfile and scan or enter tags to verifyEach Tag entered is listed below “Tags Verified” A tag can be moved from the list by pressing the ‘× ‘ icon When online, the app will display a warning indicator when an invalid tag is entered
Once all the tags to be verified have been scanned or entered, select the Send button. Selecting the Send button sends the workfile and tags to Agility to be processed as counts for the physical inventory workfile based on the freeze qty for that tag.A message is displayed at the top of the screen confirming the tags were sent to Agility to be verified. A notification is sent if any errors are found in processing (i.e. tags scanned and not in file/found). To set up the Agility Mobile Warehouse Tools Event Log notification in Agility go to System Administration > Restricted Processing > Notification Maintenance Run the PI Tag comparison report to see tags in the workfile that were not scanned
AR2101 - How to Set up Reman Scheduling
Agility
- Inventory Control
Using Schedule Manager for Reman Work Orders Schedule Manager has been available to schedule sales order work orders. With Agility v512, Schedule Manager provides the ability to schedule reman work orders. For remans, the operation is what is scheduled. Therefore, each operation must have a department assigned in order for a schedule date and completion date to calculate, allowing the reman operation to display in Schedule Manager.
Setting up an operation for scheduling In order for an operation to calculate the schedule and completion dates, you must assign a Schedule type and Department to the operation. If desired, you may also assign a Schedule resource. In this example, only the Schedule type and Department are assigned.
In Agility, access Data Files > Inv Control Settings > Operation Maintenance Enter the operation you wish to maintain and select Search or use the locator to find and select the operation. Once the operation is displayed in the Operation Maintenance window, select the schedule rule icon to add the Schedule type and Department. Complete the following steps in the Schedule Rule Maintenance window. a. From the Schedule type dropdown, select the Schedule type you wish to assign. b. From the Department dropdown, select the Department you wish to assign. If applicable, select a Schedule assignment, Schedule resource, Department capacity, and/or Resource capacity. Once all selections are made, select OK to exit Schedule Rule Maintenance and save your changes. Creating a reman with a scheduled operation Now that the operation has been set up with a schedule rule, the schedule and completion dates are calculated for the operation based on how the Schedule type and Department are set up in Schedule Maintenance. The steps below provide an example of applying an operation set up for scheduling to a reman.
Create a reman with an operation that is set up for scheduling. Once the reman is saved, the system calculates the expected schedule date and expected completion date for the operation. The dates are also carried to the reman header. If multiple operations with different dates exist on the reman, the header displays the earliest schedule date and the latest completion date for all of the operations Displaying remans in Schedule Manager Now that the reman with a scheduled operation has been saved and the dates have been calculated, the reman operation can be viewed and maintained in Schedule Manager
Access Inventory Control > Schedule Manager and select your search criteria a. Criteria name —If applicable, select a saved viewer from the Criteria name dropdown or use the default viewer for remans, Resource Schedule for Reman . b. Schedule date —If you do not wish to select a date range, check All next to Schedule date.Note : Selecting ‘All’ instead of entering a date range may take several minutes to return results. c. From —To enter a date range, select whether you wish the From date to be a Run date or an Actual date.Run date —calculate a date based on run date, number of days added or subtracted, and the day basis Example: Current day (5/13/16) minus 2 weekdays = 5/11/16Actual date —enter a date in the format of mm/dd/yy d. To —If entering a date range, select the same date type (Run or Actual) you selected for the From date for the To date and enter the date/date variables. e. Tran type/Tran ID —To view all transactions, select <all> for the tran type. To view a single reman, select Reman for the Tran type and enter the Reman ID in the Tran ID field. f. Schedule type —To search for specific Schedule types, select the desired Schedule types from the dropdown or select <all> to search for all Schedule types. g. Department —To search for specific Departments, select the desired Departments from the dropdown or select <all> to search for all Departments. h. Schedule resource —To search for specific Schedule resources, select the desired Schedule resources from the dropdown or select <all> to search for all Schedule resources. i. Print status —To search for specific Print statuses, select the desired Print statuses from the dropdown or select <all> to search for all Print statuses. j. WO/Reman status —To search for specific Reman statuses, select the desired Reman statuses from the dropdown or select <all> to search for all Reman statuses. k. Include only work orders/reman work orders with backorders —If you wish to include only reman work orders with backordered items, check the selection box. After all selections have been made, select Search Records The work orders and remans that fall within the specified search criteria display in Schedule Manager.Note: If you have operations without a Department with manually entered schedule and completion dates, those reman operations will display in Schedule Manager as well. The results sort according to the groups specified in the viewer. In the example above, the results are sorted according to Department and then by Schedule date. The user can specify how the results are grouped and sorted. In addition, the columns that display in the grid are customizable. See the Help doc for more information on setting up custom views in Schedule Manager. Updating remans in Schedule Manager After completing a search in Schedule Manager, the department, resource, schedule date, and/or print status can be updated using the Update Records option described in the steps below. Note: Updating an operation will fully recalculate the schedule dates for the entire reman.
In Schedule Manager, highlight the reman operation(s) you wish to update. Select Update Records Complete the following steps in the Schedule Manager Update window. a. Schedule date —If you wish to change the Schedule date, select the Schedule date check box and choose a new date from the New schedule date calendar in the dropdown. b. Department —If you wish to change the Department, select the Department check box, the Method to change the Department, and, if applicable, the department you wish to assign from the New department dropdown.Method: Assign New Department —Select this option if you wish to select a different, existing department from the New department dropdown. Update Department Based on Current Settings —Select this option if you wish to update the operation on the reman order to match the current department setup c. Resource —If you wish to change the Resource, select the Resource check box, the Method to change the Resource, and, if applicable, the resource you wish to assign from the New resource dropdown.Method: Assign New Resource —Select this option if you wish to select a different, existing resource from the New resource dropdown. Update Resource Based on Current Settings —Select this option if you wish to update the operation on the reman order to match the current resource setup. d. Print status —If you wish to change the Print status, select the Print status check box and choose the new print status from the New status dropdown.Note: Updating the Print status updates the Print status for the entire reman, not just the operation. After all selections are complete, select OK to exit the Schedule Manager Update window and save your changes. After exiting Schedule Manager Update, all changes are reflected immediately in the Schedule Manager window. Printing selected remans in Schedule Manager After completing a search in Schedule Manager, multiple selected remans or a single selected reman can be printed using the steps described below.
In Schedule Manager highlight the reman(s) you wish to print. Select Print Reman Work Order The Print Reman Work Orders, Print Options for Reman Work Order, and Select Laser Printer for Reman Work Order windows will display. The Print Options for Reman Work Order window will display according to your default print options. Make any necessary changes and select OK Complete the following steps in the Select Laser Printer for Reman Work Orders window. a. Printer 1 & 2 —Select the printer(s) if you wish to print a copy of the reman form(s). b. Fax —If you wish to fax the reman form(s), select the Fax checkbox and enter the fax number. c. Email —If you wish to email the reman form(s), select the Email checkbox and enter the email address(es). After all selections are complete, select OK to exit the Select Laser Printer for Reman Work Orders window and generate the reman form(s). Once printing is complete, the Print Reman Work Orders window closes automatically.
AR2107 - How to run Support Programs in Agility
Agility
- System Administration
How to Run Support Programs in Agility Support Programs can be used for periodic maintenance in Agility. Use the Support Programs screen to run support programs as needed. Some of the programs, such as resetting batch numbers, can be run at any time. Other programs should be run with caution or only under special conditions. Contact DMSi Support prior to running any support program as the results from these processes may require follow-up research.
Run Support Programs System Administration > Restricted Processing > Support Programs
Choose the support program(s) you wish to run from the Available Program and move to the Selected Programs. After finishing your selections, click Run.
Answer Yes to run the support program.
Each support program will have a slightly different window and prompts. DMSI recommends running in Audit mode first, then reviewing the audit file to see what records will be impacted.
To update, click the Process button. Agility may display an additional message about the audit report and name of the file it will create.
When finished, exit the specific support program you are running.
In the main Support Programs screen, Agility will give another reminder to check the logfile. The file name and location will display in the Status/Errors section. Click Exit when finished.
Most of the programs run in conjunction with the loading of a release or release update. For detailed instructions to run support programs included with a release update, refer to the Release Update Instructions document, available within Agility by selecting Resources > About Agility > Support tab > View Update Notes > Release Update Instructions.
AR2137 - How to set up ACH payments in PartnerView and run via Automated Processing
Agility
- A/R
How to set up and implement A/R ACH payment processing in PartnerView Before starting the setup process, consult your ACH partner or bank to gather any prerequisites and provide our IP address to them to be white listed: 63.246.25.161
Prior to applying ACH payments in PartnerView, the following must be set up in Agility
1. In Agility, access General Ledger > Chart of Accounts > Accounts Maintenance a. Enter your cash account in the G/L account field and select Bank Info b. Select the check box for Use for ACH processing in A/R and select OK c. When prompted, select OK that Bank Information was updated d. Select the red X at the top right of the window to exit G/L Bank Information. e. Select Exit to exit the G/L Accounts Maintenance window
2. In Agility, access Data Files > Misc Information > Payment Method a. Display the single Payment method you wish to use for ACH payments in PartnerView b. In the Payment Method Maintenance window, verify the following: Payment type = Check Use as payment method for ACH processing = selected Use as payment method for ACH processing in PartnerView = selected c. Make any necessary changes and select the Save icon to retain your changes d. Select the red X at the top right of the window to exit Payment Method Maintenance
3. In Agility, access System Administration > Restricted processing > File Transfer Maintenance a. Verify that an SFTP method exists for the bank(s) to which you will transfer your ACH file b. If an SFTP method does not exist, select New to add the method c. Input the following information for each unique routing number and Company ID: Record type = A/R ACH Processing Name = the bank you are using for ACH processing Method = SFTP Target address = the server hosting the ACH file; enter this information as a URL or server name Login ID = login name to connect to the host server specified above Password = password to connect to the host server specified above Target path = subdirectory of the default directory associated with the login, if applicable
d. Once all information has been entered, select Save to retain your changes and exit to File Transfer Maintenance or select Save & New to add an additional record e. Once all records have been added, select the red X at the top right to exit File Transfer Maintenance
Setting up customer accounts for ACH payment processing Customer accounts for ACH payment processing can be set at the sold-to, bill-to, and/or ship-to level. In the example below, the bank account to use for ACH payments is being set on the sold-to level.
DMSi recommends selecting one level and not deviating from the chosen level.
In Agility, access Data Files > Customer Information > Customers In Customer Maintenance, display the customer for whom you wish to add a bank account to be used for ACH payment processing Select the credit payment info icon In Credit and Payments, select the Customer Bank Maintenance icon In Customer Banks, fill in the following information:Bank name = the name of the customer’s bank (destination bank)Account number = the customer’s account numberRouting number = the nine-digit routing number of the customer’s bankAccount type = the type of account the customer wishes to use for ACH payments (Checking or Savings)Default branch = the branch to use for cash on account (CA) recordsUse for ACH processing = selected After all information has been entered, select the Save icon and the select the red X at the top right to exit Customer Banks and retain your changes Select Exit in Credit and Payments Select the red X to exit Customer Maintenance
Approving customer accounts for use with ACH processing After the steps in the section above are complete for all of your customers, a pre-notification is sent to the destination bank(s) in order to verify that the bank information is valid. Once approved by the destination bank, the account must be manually marked as approved in Customer Maintenance.
In Agility, access Data Files > Customer Information > Customers In Customer Maintenance, display the customer you wish to approve Select the credit payment info icon In Credit and Payments, select the Customer Bank Maintenance icon In Customer Banks, select the check box for Approved for ACH processing Select the Save icon and the select the red X at the top right to exit Customer Banks and retain your changes Select Exit in Credit and Payments Select the red X to exit Customer Maintenance
Maintaining Action Allocations for PartnerView users Now that the general ledger, bank information, and customer accounts have been entered and validated, it’s time to set up your PartnerView users. PartnerView users must be granted permission to apply payments in PartnerView. Complete the steps below to grant access to payments for your PartnerView users.
1. In Agility, access System Administration > Security Administration > Action Allocation 2. Complete the following steps in the Security Action Allocation window 3. Select how you wish to assign the Security Action Allocation (this example uses User ID for the search and for assigning the Security Action Allocation) User ID – locate security action records based on the user profile User Name – locate security action records based on the user name Group ID – locate security action records based on a security group 4. Select how you wish to search Beginning with Containing 5. Select PartnerView for the product 6. Select the appropriate User category Guest Internal 7. Select <all> for the Module ID 8. If known, enter the User ID you wish to modify or use the locator 9. Select Search to display the current Security Action Allocations for the user 10. Verify the following Security Action Allocations are set properly for the user: Apply Payments – Permission must be granted in order for the user to apply ACH payments in PartnerView Note: If you allow credit card payments in PartnerView, this setting grants access to applying credit card payments as well as ACH payments View Billing Information for All Ship-to’s – Optional setting Granting permission to this optional setting allows the user to see the billing information in PartnerView for all ship-to records for the customer, regardless of the ship-to records granted to the user through Security Data Allocation Denying permission to this optional setting allows the user to only view the billing information for the customer ship-to records to which the user has access in Security Data Allocation
Create Cash on Account – Optional setting Granting permission to this optional setting allows the user add cash on account by selecting the 'Payment on Account' button. Denying permission to this optional setting allows the user to only apply payments to invoices and removes the 'Payment on Account' button.
Apply Open Credits to Invoices – Optional setting Granting permission to this optional setting allows the apply credits to invoices using the 'Apply Credits' button. Denying permission to this optional setting allows the user to only apply payments to invoices, and it also prevents credits from being selected and removes the 'Apply Credits' button.
11. If permission needs to be granted for any of the above Security Action Allocations, highlight the allocation and select the right arrow to move the action to the Permission granted grid 12. Select the Save icon to exit the Security Action Allocation window and retain your changes 13. Log out and log back in to Agility and PartnerView for the Security Action Allocation changes to take effect
Applying an ACH payment in PartnerView Now that the user has access to Apply payments in PartnerView, the Bank Account button displays as an option in PartnerView. In the example below, both credit card payments and ACH payments are allowed in PartnerView.
In PartnerView, access the Billing page Select the invoice(s) for payment Once items are selected for payment, the total of all selections is displayed and the Pay via buttons become enabled. In the Bank Account window, select the Bank Account button to pay by ACH Select the bank account to use for payment from the dropdown and select Pay to create the payment After the payment is created, you are returned to the Billing page and the invoices selected for payment are no longer available. To create cash on account, select Payment on Account to enter the amount then select Bank Account to specify the account and select Pay. Additional Information See the following articles for more information regarding ACH payment processing:
AR2076 – How to send A/R ACH files via Automated Processing
AR2071 – How do I resolve my errors in my A/R ACH Exceptions Report?
AR26018 - ACH FAQ & Troubleshooting
AR2144 - Setup requirements for capturing customer signatures
Agility
- Forms
Capturing customer signatures when printing forms from Sales Order Entry or a function called from Sales Order Entry requires the following setup.
You must be using Element as your credit card payment processor and using a triPOS® Full Function POS MX 915 device to capture customer signatures.
Element's triPOS® needs to be installed on each PC that will be collecting customer signatures.
System Setup
Contact DMSi Techinical Support to assist in entering the required settings in connext.xml for your configuration.The connext.xml file must contain the following settings.
A Windows share must be configured to allow both Agility clients and the Agility AppServers to write the signature image into the Optio "images" folder. Once the share is setup and configured properly, you must enter the path into the connect.xml for the Agility Client and the Agility AppServers to use. Depending on your configuration, make the entries in the Master section of the connect.xml or in the appropriate Environment's section.
In a standard installation, Optio is installed in C:\Agility\Optio. An example of a Windows share for a standard installation would be \\agilserver\Optio.
The connect.xml tags for the signature feature are <OPTIO_SHARE_CLIENT> and <OPTIO_SHARE_SERVER>.
<OPTIO_SHARE_CLIENT> contains the full share path accessible by Agility Clients to the Optio installation directory. Using the above example, the path would be \\agilserver\optio. <OPTIO_SHARE_SERVER> contains the full share path accessible by AgilityAppServers to the Optio installation directory. If the Agility AppServers are running on a Unix server, the Windows share must be mounted on the Unix server and you must enter the path to the mount point.
If the Agility AppServers are running on a Windows server, use the Windows share.
Using the above example, if the AppServers are on a Windows server, you would enter \\agilserver\Optio. If the AppServers are on Unix, an example mount point would be /remote/agilserver/Optio.
Agility Setup
For sale types used on sales orders where the customer is present such as counter sales and customer pickup, set the form specific flag on each form you want to capture signatures. The flags are available under the heading 'Prompt for customer signature in SO Entry when printing'.
Access Sale Types Maintenance: Data Files > Sales Order Settings > Sale Types
Set the User Preference 'Do not require customer signature when printing forms' on users that print forms for orders with customer facing sale types, that will never have customers present. (Optional)
Access User Preferences: File > User Preferences
Update the 'Timout seconds for signature device' field if the default value of 60 seconds does not meet your needs.
Access System Configuration: System Adminstration > System Configuration > System Config
Define signature print options in Forms Assignment for the order acknowledgement, delivery ticket and invoice
Set 'Print customer signature' to Yes if signatures should print. Use the 'Customer signature label' field to define a custom label to print on the form. There is a default value of 'Customer Signature'.
The invoice has additional settings for printing credit card customer signatures. They do not affect printing the other customer signatures.
To print credit card customer signatures set 'Print payment receipt information' and 'Print credit card signature' to Yes. If you want to print credit card signatures on the Reprint of the invoice, set 'Print credit card signature on reprint' to Yes
Access Forms Assignment: Data Files > Misc Information > Forms Assignment
The following Sales Order Parameters settings are related to the order signature.
If you will be using the order signature for a single purpose, unset the SO parameter 'Prompt for customer signature in SO Entry' to suppress the display of the Signature Capture window and define a label in the 'Default order signature label' field.
If you will be using the order signature for multiple purposes define a label in the 'Default order signature label' field that will default into the Signature Capture window. Note: Leaving the default label field empty requires entering a label each time a signature is captured.
Access Sales Order Parameters: System Adminstration > Module Controls > Sales Order Parameters
AR2147 - How to Delete a Dimension Length from an Item
Agility
- Inventory
How to Delete a Dimension Length from an Item
Considerations 1. Item dimension must have no activity. If there is on-hand, on-order, quoted, etc… the record cannot be deleted.
2. Item dimensions that only appear on Quotes with no other Item Activity may be deleted once the Item dimension is removed from the quote.
Steps 1. In Agility, go to Data Files > Item Information > Items
2. Search for the item
3. From the Item Record click the Dimensional Records
4. Highlight dimension in question and click Delete
5. If Item Dimension has no on-hand, on order, or other activity it will delete successfully.
If encountering error: "This record cannot be deleted" 1. However, if the following message pops up there is some order containing this dimension as a line item. "Current inventory (on hand, on order, suggested tally, etc.) records are on file for dimension(s) 1X12X1234 in the following branches <BRANCH>. This record cannot be deleted."
2. Check Item Activity for any PO or SO containing this Item dimension.
3. Check to see if the item dimension is on a Quote by running a query to find the trans# that’s keeping this dimensional length on file. The following Query was run to find any trans# with a tally length = 1234. Trans ID 287272 was returned which turned out to be a Quote. This query can be edited to search for different attributes of an item as needed
4. The next steps would be to remove the Item dimension in question from all orders.
5. Retry steps to delete Item dimensional length.
AR2161 - Available Conversions in Agility
Agility
- System Administration
General Notes: Template files can be found in the Document Library of 360. Within the Document Categories there is a category of Conversion Templates where the files reside. They are also made visible through the Portal for customers.
All conversion files need to be a .csv file
All conversion files should be run in Audit Only mode first
For large files, progress can be tracked using the In Process audit through CQ
Make sure to launch CQ before running the conversion (sample at the bottom of this document)
The purge option will purge ALL records created by CONV on the date entered
There are some conversions that have specific rules for DMS+ customers. Make sure to use the DMS+ Conversion option when processing the files.
If there are fields with leading zeros, do not directly open the csv file with Excel.
Instead, open a blank Excel sheet first and go to the Data tab and Get External Data From Text. Use the Wizard to separate the delimited file and format all columns as Text.
Maintenance – Customer Conversions Alternate Payment Terms Creates records for the Payment Terms Assignment maintenance window. Allows customers to setup payment terms that are customer ship-to and sale type specific (ie. Customer gets different terms for Direct vs. Stock orders). Authorization to Charge The Authorized Charge List is accessed off the sold-to in customer maintenance. Maintains the name and photo of individuals who have the authority to charge to a customer’s account. Auto Messages Creates auto message records. If the message text has not already been created, then a message record will also be created along with the auto message record. Contacts Used to create the contact records for either customer or supplier records. Customer Bank Assigns the customer’s banking information that will be used for either EDI R823 Lockbox Payments or A/R ACH payments. Customer Charges Creates the records for the Customer Charge Maintenance window. Customer/Price Group Codes Creates the records for the Customer/Pricing Group Definition window. Data Allocations Creates the list of customer records that a PartnerView user can access. The purge process is different than the other conversion programs. There is no date associated with these records so you must provide a file of what is going to be purged. See the NOTES section on the Layout tab of the template file for more business rules. Delivery Routes Creates the delivery routes EC Ref Creates the EDI Customer Reference Maintenance records. An EC Ref record is required for each customer record that trades electronic documents. Laser Controls Used to create laser control records for either customer or supplier records. Notes Used to create Customer, Credit, Supplier, and Item notes. Payment Terms Creates the Payment Terms codes Route Assignments Used to assign delivery routes to customer ship-to records Sales Account Parameters Creates the Sales Account Parameters Maintenance records to define the general ledger accounts to be used at time of invoicing. Sales Agents Creates the Sales Agents Sales Type Creates the Sale Type records Shipto Tax Certificates Used to maintain Tax Resale Certificates for the customer ship-to records. This program has the ability to either add new records or update existing records since the certificate numbers and expiration dates can change yearly. Tax Authority Creates the Tax Authorities Tax Codes Creates the Tax Codes and assigns the Tax Authorities to the Tax Code Tax Exceptions Creates Tax Exception records to exclude sales tax from being charged on items for specific customers or customer groups by either item or product group. Zip Tax Assigns a list of ZIP codes to specific Tax Codes.
Maintenance – Inventory Conversions Allocation Sets Creates the Allocation Set Maintenance records by assigning up to 5 allocators to each Allocation Set. Allocators Creates records for the Allocator Maintenance window. Alternate Items Creates a list of alternate items to a main item code. Auto Messages Creates auto message records. If the message text has not already been created, then a message record will also be created along with the auto message record. Cut Category Creates the categories that are used for grouping items with similar cut-from dimensions. Cut Records Creates the hierarchy of cuts to determine which cut-from dimensions are valid for each cut-to dimension. Item Supplier Creates secondary item supplier records after the primary item supplier is created through the Item Import. Location Creates the location records Notes Used to create Customer, Credit, Supplier, and Item notes. Permanent Locations Assigns a list of permanent locations to items. Instead of a purge option, a file must be provided to remove a permanent location from an item. Price Codes Creates the price code major and minor records. Price Codes – Copy from Product Groups Runs the support program that copies the current product groups to create the price codes Product Groups Creates the product group major and minor records.
Maintenance – Supplier Conversions Auto Messages Creates auto message records. If the message text has not already been created, then a message record will also be created along with the auto message record. Buyers Creates the Buyer records Contacts Used to create the contact records for either customer or supplier records. Item Supplier Creates secondary item supplier records after the primary item supplier is created through the Item Import. Laser Controls Used to create laser control records for either customer or supplier records. Notes Used to create Customer, Credit, Supplier, and Item notes. Payment Terms Creates the Payment Terms codes
Maintenance – General Ledger Conversions Budget Data Creates up to 13 periods of budget amounts for each GL Account. G/L Balances Creates beginning balance and the net change for each GL Account for each period in the year. Has an option to create just beginning balances when using the G/L Detail conversion or Journal Entry Import to create detail information for the periods. G/L Detail Works like the Journal Entry Import but allows multiple periods/years in the same file. Sales Account Parameters Creates the Sales Account Parameters Maintenance records to define the general ledger accounts to be used at time of invoicing.
Maintenance – Other Conversions Branch Transfer Parameters Defines requesting-branch/shipping-branch customer and supplier relationships for branch transfers Data Allocations Creates the list of customer records that a PartnerView user can access. The purge process is different than the other conversion programs. There is no date associated with these records so you must provide a file of what is going to be purged. See the NOTES section on the Layout tab of the template file for more business rules. Messages Create p ermanent message information, including message ID and message text PartnerView Quick Lists Create a list of items for a specific PartnerView user by branch for quick order entry in PartnerView. Sales Account Parameters Creates the Sales Account Parameters Maintenance records to define the general ledger accounts to be used at time of invoicing. Split large text files Takes a csv, txt, or DAT file and splits it into smaller, workable files. Helpful for large DMS+ flies to make them more manageable for importing. Places new files in the same file path as the source file, keeping the original file name and adding an incrementing value at the end. User Profile – Initial Create Uses a template user already created to create new users. The template user is used to assign default branch and copy security settings and user customizations. This conversion is unavailable after Agility version 607. User Profile – Settings Tab Since a user id can be assigned to a sales agent or buyer, this program can be run to update the Settings tab on existing user profiles to add the corresponding sales agent and buyer to a user. This conversion is unavailable after Agility version 607.
Go Live conversionsA/P Recon Detail Open A/P Creates the open accounts payable records for a branch. The branch passed in the file should be the transactional branch if they want to be able to run an AP Aged Open Payables by branch. Open A/R Creates the open accounts receivable records for a branch. The branch passed in the file should be the transactional branch of the original order if they want to be able to run an AR Aging by branch. Quantity On Hand Creates Quantity On Hand records for inventory items. Will not combine quantity into the same location. The Inventory Valuation report is auto launched after this program is complete to aid in balancing. Back Order Manager Runs the back order manager support program. This is used if there have already been sales orders entered into the system before the quantity on hand conversion is run to commit the on hand quantity to the open orders. Make sure the quantity on hand is correct before running this program.
Historical conversions GMROI Creates the inventory_value_fact records that are used when running the GMROI report from the Data Warehouse menu. Item Activity Previously used to build usage information before Usage Import was available. Creates item activity records. These are just view only records and there is no drill down options when viewing these in the Activity Viewer. Sales Analysis Creates the historical sales records read when running the Sales Analysis reports. Invalid data is written to a catch all record so the overall sales figures can be reported on even if a customer or item existed in the prior system but not in Agility. Run in audit only mode first to determine which records are invalid and the total amount that will be written to the catch all record for that record.
In Process Audit On the window that you select the conversion file, a report key will be displayed in the text box. Use this report key to query out the report_output table. The output of the report will give a processing log for every 500 records along with any failures that will be written to the audit report.
where report_output:rpt_key = "04026557.RPT" list seq report_line
AR2169 - How to Use Save Criteria in Agility
Agility
- Best Practice
How to Use Save Criteria in Agility Saving criteria for processes run on a regular basis saves time and increases efficiency by allowing you to easily regenerate reports or run processes without having to select the criteria fields each time.
S ave Criteria for Reports, Viewers, Forms, and Automated PurgesAlthough the screens display differently, the general concept when saving criteria for reports, viewers, forms, and automated purges is generally the same. The steps listed below use the Sales Order Profitability Report as an example.
1. Access the report, viewer, form, or automated purge in Agility
2. Fill in the criteria for how you wish the report, viewer, form, or automated purge to run.
3. Select the applicable save option to save the selection criteria.
Save for user
This option allows you to save the criteria for your specific user. When selected, you are prompted to create a new record or, if you are on an existing record, you can update the record you modified.
When creating a new record you are prompted to enter the name under which you wish to save your criteria, unless the selection criteria screen contains a place for you to enter that information prior to saving.
Save for a security group
This option allows you to save the criteria for a security group. When selected, you are prompted to create a new record or, if you are on an existing record, you can update the record you modified. After selecting the security group for which you wish to save the criteria, you are prompted to enter the name under which you wish to save your criteria, unless the selection criteria screen contains a place for you to enter that information prior to saving.
Save for all users
This option allows you to save the criteria for all users. When selected, you are prompted to create a new record or, if you are on an existing record, you can update the record you modified. You are then prompted to enter the name under which you wish to save your criteria, unless the selection criteria screen contains a place for you to enter that information prior to saving. Note: Even though the criteria is saved for all users, only users with menu access granted to the specific report, form, etc. are able to access the saved criteria.
Save Criteria for Reports You can save report criteria for all users, a specific user, or a security group for the following Agility reports:
· Accounts Payable > A/P Recon > A/P Recon Register
· Accounts Payable > Reports > A/P Aged Open Payables
· Accounts Receivable > Reports > A/R Aged Trial Balance
· Accounts Receivable > Reports > A/R Lien Reminder
· Accounts Receivable > Reports > A/R Tax Summary/Detail
· Data Warehouse > Sales Analysis Report
· General Ledger > Reports > G/L Subsidiary Balancing Rpt
· Inventory Control > Queries/Reports > Inventory Valuation Report
· Inventory Control > Queries/Reports > Usage/Purchase Comparison
· Inventory Control > Reman > Output Only Completion Report
· Sales Orders/Quotes > Queries/Reports > Cash Drawer Balancing
· Sales Orders/Quotes > Queries/Reports > Profitability Report
Save Criteria for Viewers You can save viewer criteria for all users, a specific user, or a security group for the Agility viewers listed below in Data Files > Misc. information > Viewer Builder. In addition, you can access the viewers listed below within their specified module. Saving criteria within the specific viewer instead of the Viewer Builder only provides the ability to save the view for your specific user.
· Accounts Receivable > Commission Viewer
· Dispatch > Viewers > Dispatch Viewer
· Inventory Control > Queries/Reports > Item Activity Viewer
· Inventory Control > Reman > Viewers > Reman Viewer
· Inventory Viewer
§ Dispatch > Viewers > Inventory Viewer
§ Inventory Control > Queries/Reports > Inventory Viewer
§ Inventory Control > Reman > Viewers > Inventory Viewer
§ Purchasing > Viewers > Inventory Viewer
§ Sales Orders/Quotes > Queries/Reports > Inventory Viewer
· Purchasing > Viewers > PO Viewer
· Sales Orders/Quotes > Viewers > SO Viewer
Save Criteria for Forms
You can save form criteria for Agility acknowledgments in Sales Orders/Quotes > Forms > Print Acknowledgements. Acknowledgements can be printed for credit memos, RMAs, and sales orders. Acknowledgement criteria can be saved either for all users or a user group. You can also save form criteria for Agility invoices.
Save Criteria for Automated Purges You can save purge criteria for the Agility automated purges listed below in System Administration > Performance Tuning > Automated Purges. Automated Purges can only be saved for all users.
· Audits
· Data Warehouse – daily activity
· Data Warehouse – summary activity
· OrderPad
· Packing Summary
Save Criteria for Automated Processes You can save criteria for Agility batch criteria and automated update processes.
· System Administration > Restricted Processing > Automated Processing > Batch Criteria
· System Administration > Restricted Processing > Automated Processing > Queue Maintenance
A/R Finance Charge Application ABC Classification Automated Purges Batch Criteria Cost Mass Update Create Pick File Customer Item Quicklist Data Warehouse Update KPI Update Reorder Calculations Shipment Update Tax interface Invoice Error Processing Transaction Analysis WMS Monitor Note: When saving criteria for an update process in Automated Processing > Queue Maintenance, the criteria is actually saved as a specific task and the task is then added to a job set up in Queue Maintenance. For example, the saved criteria for Customer Item Quicklist is saved in System Administration > Restricted Processing > Automated Processing > Customer Quicklist Criteria.
AR2177 - How to Enter a Sales Order Using the WS Test Harness
Agility
- API
AR2180 - Faxing FAQs
Agility
- Faxing
Faxing FAQ
Can special characters be used on a Coversheet? No. Concord will reject it because it will not be in the correct format for a fax number.
Can you stop a fax from “sending” after it has left Agility? Once the fax has left Agility there is not a way to stop as it is an automated process at Concord.
How many times does a fax try to resend before it stops sending? On a voice answer it will attempt a second try to make sure someone didn’t accidentally pick-up the fax. If a busy or no answer attempt 6 retries before sending out an error notification of failure. For both the retry attempts will be in 5 minute intervals.
Can broadcast faxing or mass faxing be done? Yes. DMSi will need to contact Concord to set this up.
Can you fax outside of Agility? Yes. For Desktop Faxing, enter “1” followed by the fax number, followed by @concordsend.com in the Subject line of the email message. 1XXXXXXXXXX@concordsend.com
For Setup within Agility, go to System Administration>Module Controls>Branch Parameters
Select and change 3rd Party Fax Provider to Concord. This is a branch specific setting and will need to be made in each branch.
AR2181 - Concord Faxing Common Error Messages
Agility
- Faxing
Busy "Busy" Indicates that the called number (phone line) is already in use or engaged.
"No Answer" indicates that the line was not picked up (answered) by a fax No Answer machine or person before timing out. The timeout is sufficient to ensure at a minimum of 5‐8 standard rings.
"Not a fax machine" indicates that a fax device has failed to answer the call. Specifically, fax tones or the fax signal from a remote machine has not been Not a Fax Machine detected. This may for a number of reason including but not limited to, a wrong number, a machine not configured to automatically answer, or a device that has stopped answering because it is out of paper or has a paper jam.
"Voice Answer" indicates that either a person or voicemail message answered the Voice Answer call.
“Fast Busy" indicates that there was no available path to the attempted fax number. This normally indicates that the destination is currently overloaded, or that there is an outage with the specific number or in the area attempted such as Fast Busy that due to a fibre cut. This can also be caused by severe weather conditions in the area of the destination. In most cases Fast Busy conditions are temporary, please verify the fax number you’re trying to reach is valid and if so please try again later.
"Sit‐Tone / Operator Msg" indicates that the call was intercepted by the special situation information tones followed by an operator message, examples include "The number you have dialed is disconnected or is no longer in service. Please Sit‐Tone / Operator Msg check the listing and try your call again.", "The number you have dialed has been changed…the new number is…XXX‐XXX‐XXXX", "All circuits are currently busy, please try your call again later". "Operator Msg" indicates the same issue however the special situation information tones were not detected.
“Negotiation Failed” indicates the call was answered by a fax device but during the initial training phase of the call, communication between the fax transmitter and the receiving fax device failed or the two devices could not agree on the Negotiation Failed parameters to be used for the call. This often indicates a phone line quality issue and may occur at the beginning of the fax transmission, or, during the fax transmission between pages on a multi‐page fax.
"Transmission Failed“ indicates the receiving fax machine has answered and connected but the fax was not able to be fully and successfully transmitted. This can be caused by line quality issues, fax device issues, the sharing of phone line Transmission Failed with other devices such as credit card processing terminals. Temporary conditions such as severe weather conditions in the destination area can also cause transmissions failures.
“Exceeded ECM Retransmit” indicates the call was answered by a fax device and connected using ECM or Error Correction Mode. Due to poor line quality or a poor connection for that specific call attempt the transmission of the fax required Exceeded ECM Retransmit an excessive amount of data to be retransmitted to the receiving device to get acknowledgment of successful reception of the fax, the call was aborted to allow a retry or new attempt to get a better connection and to ensure the call duration did not ensure excessive overtime charges.
"Job Cancelled" indicates that the job or recipient number was cancelled or the Job Cancelled set time for delivery expired.
"General Error" indicates that another uncommon error not listed above has occurred resulting in the failure to transmit your fax. Please retry the fax job or General Error recipient again. If you get the same error again please contact Concord customer service for further assistance and investigation.
AR2223 - Exporting to Excel is opening on the hosted site and not locally
Agility
- System Administration
AR2231 - Fax Error: There was a problem with your fax request, Unauthorized sending email address
Agility
- Faxing
Issue: When a user sends a fax out of Agility, an email notification is generated from Concord with the subject line, “There was a problem with your fax request, Unauthorized sending email address.”
The body of the e-mail states:
“Your request could not be processed for the following reasons
Unauthorized sending email address.”
Steps to Resolve:
Verify whether the client has recently added or changed their email domain.If a new domain has recently been added, contact DMSi Support to contact Concord and have the new domain added. Concord, the faxing company, uses the domain information to process faxes, so they know who to charge. If a new domain has not recently been added, verify the user is using a valid email address. Generic email addresses like ‘@gmail.com’ may not be considered valid to Concord. If a new domain was recently added, please remind the client that they may need to update the e-mail addresses on the Branch Parameters screen. Go to System Administration > Module Controls > Branch Parameters. This screen is branch specific and needs to be updated for each branch.
AR2287 - Cyberquery (CQ) sample: Line items sold by sales type
Agility
- Cyberquery Samples
--Customer Profitability: Know Where I'm Making Money THIS QUERY WILL DISPLAY THE NUMBER OF LINE ITEMS SOLD FOR A SPECIFIED TIME PERIOD BY SALE TYPE.
--Suggested Naming Convention: Line_Items_Sold_by_Sales_Type
--THIS IS USEFUL WHEN DETERMINING THE COST TO SERVE EACH ORDER TYPE FOR RUNNING THE CUSTOMER NET PROFITABILITY REPORT.
/* THIS QUERY WILL DISPLAY THE NUMBER OF LINE ITEMS SOLD FOR A SPECIFIED TIME PERIOD BY SALE TYPE. THIS IS USEFUL WHEN DETERMINING THE COST TO SERVE EACH ORDER TYPE FOR RUNNING THE CUSTOMER NET PROFITABILITY REPORT. */ define string xbranch = parameter prompt "Enter Branch ID or All" default "All"; file xaropen = access aropen, set aropen:system_id = so_header:cust_key_sysid, aropen:prof_name = shipments_header:prof_name, aropen:ref_num_sysid = shipments_header:prof_name, aropen:tran_id = shipments_header:so_id, aropen:shipment_num = shipments_header:shipment_num; number xso_lines = if shipments_detail:qty <> 0 and xaropen:ref_type one of "IN", "DM" then 1; number xcm_lines = if shipments_detail:qty <> 0 and xaropen:ref_type one of "CM", "CI" then 1; number xcm_affect_inv = if xaropen:ref_type one of "CM", "CI" and so_header:so_status <> "C" --and so_header:so_status_type not one of "RMA", "RMA Received" and shipments_detail:qty <> 0 and so_detail:return_to_stock = 1 then 1; number xcm_not_affect_inv = if xaropen:ref_type one of "CM", "CI" and so_header:so_status <> "C" --and so_header:so_status_type not one of "RMA","RMA Received" and shipments_detail:qty <> 0 and so_detail:return_to_stock = 0 then 1; number xcm_rma = if so_header:so_status="B" and --if shipments_header:type = "CM" and so_header:so_status_type one of "RMA", "RMA Received" THEN 1; --and shipments_detail:qty <> 0 then 1; date xstart_date = parameter/prompt="Please Enter Start Date" default date(str("01/01/") +str(year(todaysdate), "9999")); date xend_date = parameter/prompt="Please Enter End Date" default date(str("12/31/")+str (year(todaysdate), "9999")); string xvalid = if shipments_header:invoice_date >= xstart_date and shipments_header:invoice_date <= xend_date then "Y"; where (shipments_header:system_id = xbranch or xbranch="All") and xvalid = "Y" sum/noreporttotals/nobanner/domain="shipments_detail" xso_lines/total/heading="Sales-Order-Lines" xcm_lines/total/heading="Total-CM-Lines" xcm_affect_inv/total/heading="Total-CM-Affect-Inv" xcm_not_affect_inv/total/heading="Total-CM Not-Affect-Inv" xcm_rma/total/heading="Total-RMAs" across shipments_header:sale_type/total by shipments_header:system_id
AR2499 - Physical Inventory in Agility
Agility
- Physical Inventory
1. Establish the cutoff date for when shipping, receiving, billing, and work orders are to be completed in the warehouse. In addition, determine when the workfile will be created.
2. Create workfile : Inventory Control > Physical Inventory > Physical Inventory Desktop. The system prevents you from creating a new workfile if the current status of a full physical workfile is Active.
3. Generate workfile detail: Inventory Control > Physical Inventory > Physical Inventory Desktop.
Perform this step close to the transactional cutoff in the warehouse. The system updates the item tally record with the workfile identification code to prevent the item tally record from being included in another workfile .
NOTE : If you carry inventory at multiple locations and/or the lot, tag and/or content levels and you generate the workfile detail prior to completing the transaction activity (i.e. step 4), you must append new inventory received which is not included in the workfile , or add the new inventory to the workfile via Blank tags to include them in the physical count.
4. If using Tags, print tags to mark the locations in the warehouse for counting items: Inventory Control > Physical Inventory > Print Tags. The physical inventory tags are perforated between the first count and second count sections to allow for multiple counts.
If you use the Mobile Physical Inventory function or are using count sheets only, this step is not necessary.
5. Complete billing, receiving, and outstanding work orders in the system based on the cutoff date.
6. Freeze the on-hand quantity and current average cost of items in the workfile : Inventory Control > Physical Inventory > Freeze Workfile.
7. Print count sheets for each team, if applicable: Inventory Control > Physical Inventory > Count Sheets.
Only one copy of count sheets should be printed. Assign count sheets to count teams and begin physical count.
8. Enter the physical inventory counts for an active workfile from the physical inventory tags or count sheets: Inventory Control > Physical Inventory > Enter Counts. OR Use the Mobile Physical Inventory feature to gather physical inventory data and save that data to an active workfile . Refer to the "How to Use Mobile Physical Inventory Screens" subheading in the Mobile Physical Inventory topic for more information.
The system allows you to skip uncounted items and add counts for the items later.
9. Print the Physical Inventory Comparison report to view counts, extended costs, and differences: Inventory Control > Physical Inventory > Comparison Report
10. If necessary, recount items that were identified with discrepancies on the Comparison Report and enter subsequent counts.
11. Print the Audit report to review errors in the workfile that may cause inaccurate counts for items: Inventory Control > Physical Inventory > Audit Report.
12. Make corrections to the workfile based on items from the Audit Report.
13. Print the final Audit report to verify all information is accurate: Inventory Control > Physical Inventory > Audit Report.
14. Update quantity on hand inventory and cost records based on the counts entered for the items in the workfile : Inventory Control > Physical Inventory > Update Quantity on Hand.
15. Run the Overcommitted Inventory Report to review items with negative available quantity at the item tally level: Inventory Control > Queries/Reports > Overcommitted Inventory.
AR2508 - Item Branch Record Not Found Error in Sales Analysis Conversion
Agility
- System Administration
Item Branch Record Not Found Error in Sales Analysis Conversion
The user is running a Sales Analysis Conversion. They have codes set up if an invalid Customer, Product Group, Item, Sales Agent, or Location is found. When they run the conversion there are several items that are not processing with an error message of Item Branch Record Not Found. The items are all invalid items but for some reason the system is not using the conversion template set up when the conversion was run.
The issue is that the invalid items were valid items at one time and had Item Dimension Records built before the items were deleted from the system. The Sales Analysis Conversion program checks for the Item Dimension Record first, finds a valid record, then looks for an actual item record. The system will not use the template conversion item because a valid Item Dimension Record was found.
To process these records, contact DMSi to remove the invalid Item Dimension Records (item_dim table) prior to processing the Sales Analysis file.
AR2525 - What setup is needed to start using the payments tab of SO entry
Agility
- Sales Orders
AR2534 - Automate Running Daily Balancing
Agility
- General Ledger
Implementation Requirements
Install the Automated Processing client on a computer that has Internet access and is running constantly.
Update Data Warehouse daily, after hours, via Automated Processing. This process must finish before starting the daily balancing automated processes.
Implementation First Steps
Go to: General Ledger > Reports > G/L Subsidiary Balancing Report
Select Report Type: Subsidiary Select criteria for reportIf you don't check any of the boxes, it will total Sales and COGS including customer charges and cost that affect gross margin. If you just check the top box, Display customer charges and order costs separately, it will total customer charges and order costs that affect gross margin separately. If you just check the middle box, Include customer charges and order costs not affecting GM, it will total all charges and costs included in Sales and COGS. If you check both boxes, all charges and costs are total and listed separately. Save for All Users and note Report name for final step Repeat steps for second report type
Select Report Type: G/L Comparison Select criteria for report Save for All Users and note Report name for final step
Implementation Next Steps
Go to: General Ledger > Chart of Accounts > Categories Definition
Setup new GL categories in Agility 'Sales' & 'COGS' Go to: General Ledger > Chart of Accounts > Account Maintenance
Change the Category on the Sales account and COGS accounts
Implementation Final Steps
Go to: System Administration > Restricted Processing > Automated Processing > Queue Maintenance * Setup the Job to run daily after the Data Warehouse Update is complete *
Create a Job that includes the 'G/L Subsidiary Balancing Report' for both types: Subsidiary and G/L Comparison Specify the reports to email in in Excel format (recommended)
AR2560 - How to implement Notifications for Critical Sales Order Changes
Agility
- System Administration
Implementation Requirements
Install the Automated Processing client on a computer that has Internet access and is running constantly.
The 'Expected Delv Date Change' notification is based on a change to the expected delivery date on a sales order detail and the 'Backorder Qty Available...' notifications are based on availability of previously backordered material. Each of these notifications are generated through Automated Processing which requires the above setup.
Implementation First Steps
Go to: System Administration > Restricted Processing > Notification Maintenance - Monitor quantities previously backordered that are now available - Create a new record for the event 'Backorder Qty Available Items Ready to Ship' to monitor for individual items that are now available to ship. - Create a new record for the event 'Backorder Qty Available SO Ready to Ship' to monitor for sales orders that previously had at least one item on backorder that is now available to ship. - Create a new record for the event 'Backorder Qty Available Parent Ready to Build' to receive an alert when a parent item that previously had at least one component on backorder is now ready to be built. - Specify the recipient(s) - Send for All records or only those meeting certain criteria - Create the email message subject and body with System Inputs
Implementation Next Steps
Go to: System Administration > Restricted Processing > Notification Maintenance - Monitor expected delivery date changes - Create a new record for the event 'Exp Delv Date Change' - Specify the recipient(s) - Create the email message subject and body with System Inputs - Send for All records or only those meeting certain criteria - Criteria available for this notification is within the 'More Details' link
Implementation Final Steps
Go to: System Administration > Restricted Processing > Automated Processing > Queue Maintenance
-Review the 'Notifications - BO Qty Available' queue - Verify the queue's On Hold flag is unset - Modify the recommended interval if desired (defaults to every 5 minutes)
- Review the 'Notifications - Exp Delv Date Change' queue - Verify the queue's On Hold flag is unset - Modify the recommended interval if desired (defaults to every 5 minutes)
AR2565 - How to implement Suggested Purchasing (SPOs)
Agility
- SPO
Implementation Requirements Review the following articles to ensure all system and item information is set up correctly.
Basic System Setup for Running SPOs (AR1946)
Basic Item Setup for Running SPOs (AR1939)
Setting up Reorder Calculations for Running SPOs (AR1950)
ABC Classification for Items (AR939) - The steps in this article are not required but are highly recommended to efficiently use SPOs.
Additional SPO setup and general information can be found in the Getting Started Using Suggested Purchasing (SPOs) article (AR1821).
Implementation First Steps Go to: Purchasing > Suggested POs Choose criteria based on how you want to run Suggested POs - 'Include SPOs' for stock items, items tagged for POs or both - Choose from a list of Product Groups, Suppliers or Buyers - Use 'ABC Criteria' to look at only your high priority items - Include only items with recommended buys or all items - Select 'Calculate surplus' to specify the branches searched to determine whether surplus quantity is available - Click 'Create SPOs'
Implementation Next Steps Review SPO Details - Double-click on the SPO header for the supplier you wish to review - Review each item, recommended buy, net quantities, prior usage, and projected usage - Make any necessary changes such as, adjusting the recommended buy or adding/removing items until all of the items and quantities you wish to purchase are specified - The system automatically saves your work so when you are finished, simply click 'Exit'
Implementation Final Steps Click 'Create PO' (choose 'w/Append' if you are adding your order to an existing PO)
- Fill in the necessary PO Info and click 'OK' - Open the PO to review, then Print, and send it to your supplier
Repeat these steps for each additional SPO until you are finished.
AR2581 - How to implement the Dead Stock Report
Agility
- Inventory Control
How to implement the Dead Stock Report The dead stock report allows you to see what’s not moving in your inventory by generating a list of items without activity quickly. Use this report to reduce your holding costs and maximize your warehouse and shelf space. You can use this report in conjunction with the Inventory Hits report to identify infrequently used items.
Initial setup In Agility, access Inventory Control > Queries/Reports > Dead Stock ReportIf attempting to run the report in Agility v541 or earlier, access this report from Inventory Control > Queries/Reports > Usage/Purchase Comparison and restrict ‘Items to include’ found under Additional Criteria to ‘With no activity (Dead Stock)’.
Once the report is displayed, review the following tabs:Selection CriteriaRestrict the analysis to a specific branch, product group, etc. Additional CriteriaDefine the level of usage activity you want to include on the report Define the period of usage you want to review - Use relative dates so the report criteria can be saved and run again Define desired exclusions involving recently created or received items Report OptionsPull in non-stock, discontinued, or consignment items for review Pull in the ‘Last Sold’ date Define print criteria such as repeating headers on each page, prepping for physical printing, or exporting to a spreadsheet Once your tab criteria is set up as desired, save the criteria so you can skip this process the next time. - You can save the report for a single user, a security group, and/or all users Additional information DMSi suggests reviewing this report every 6-12 months. Waiting too long to review this report may result in paying excess holding costs and could clog your shelf space. Running this report too frequently may falsely identify slow-moving items as dead. Once you’ve identified your dead stock, you’ll need to decide how to handle it:Ask your supplier if they’ll let you return the stock Reclassify the items as alternate or substitute items Transfer the item(s) to branches where they are selling Discount, donate or discard Compare holding costs on the item versus how much of a loss you’d take discounting it to encourage sales, or outright throwing it away
AR2590 - Troubleshooting API Errors in Agility Configurator
Agility
- PartnerView
AR2591 - File Transfer Icon Disappeared
Agility
- System Administration
AR5866 - What EDI documents are currently available to use within Agility?
Agility
- EDI
EDI Forms
Customer Related S810 (Invoice) – The 810 is an Invoice. We will designate with the ‘S’ to indicate that we are Sending the form. The S810 is the most commonly used EDI form for our customers. This form is created when a sales order is invoiced and the ‘Invoice Via’ field is set to EDI on the sales order. R850 (PO) – The 850 is a Purchase Order. We will designate with an ‘R’ to indicate that we will Receive the form. When the R850 (PO) is received and processed, we will create a sales order for the customer. S856 (ASN) – The 856 is an Advance Shipping Notice. This is sent to a customer. This is based from a dispatch record within Agility. In order for the ASN to be released, the delivery ticket for the corresponding sales order must be printed. This is done because many trading partners will access fines if there are quantity errors on what is shipped to them vs. what is on the ASN. S855 (Purchase Order Acknowledgement) – The 855 is actually a dual purpose form, depending on the final customer’s need. It can be used as a Reverse PO. The idea for this would be that the customer would call in the order. The order would be placed in Agility and the S855 would be sent to the customer. The 855 that is sent to the customer would then be used to create a PO on that customer’s system. The other use for the S855 would be as a PO Acknowledgement. This would be used to update the cost, qty or dates of an existing PO on the customer’s system rather than create a PO. R820 (Remittance Advice) – The 820 is a Remittance Advice. Within the R820, the customer will specify a transaction that is being paid with the remittance. When processed, we will apply payment to that AR transaction. R823 (Lockbox) – The 823 is for Lockbox payments. This is similar to the 820 in that AR transactions could have payments applied to them. The primary difference is in the detail that is sent. The 823 is information that is sent from the bank rather than from the customer. The bank could send transaction information on the 823. Is so, then we could apply payment based on that detail. The bank may send just the check amount. If that is the case, we could run auto-cash procedures to apply payment to the open AR transactions. S870 (Order Status) – The 870 is used to send an order status update to the customer. This is primarily used for special orders, but could be used for non-special orders as well. Some common uses for this document might be to inform the customer if a scheduling date has changed on a special order or something like that. This will allow them to in turn keep their customer informed on the status of their order. R870 (Order Status) – Similar to the outbound 870 except the status request is sent from the customer. We produce a report to indicate the status update that is requested from the customer. R852 (Item Activity) – The item activity file is used for consignment inventory. The customer will send item activity for the consigned inventory indicating qty on hand, qty sold, and other values related to the consigned inventory. We can then invoice the customer for the material that has been sold. R846 (Consignment Activity Data) – This is similar to the 852 in that it is used to process item activity data. The primary difference is that this is designed specifically for consignment inventory. When processed, we will write consignment data that will allow us to produce simple consignment sales reports from that processed data. Supplier Related R810 (Invoice) – When the R810 is processed within Agility, we will create a standard AP record. S850 (PO) – This is a Purchase Order sent to a supplier. In order to send the PO to the Send PO Via field must be set to EDI and the PO must be printed. R856 (ASN) – When the R856 is processed, we will create pre-receipt records for the PO’s/packing slips contained in the ASN. Normal PO receiving is then done for those pre-receipt records. R855 (PO Acknowledgement) – The 855 can serve a dual purpose for suppliers. We can either update an existing PO, or we can create a new PO based on the set up of the Supplier EDI Ref record.
Undefined R864 (Message) – The Message file is not tied to either supplier or customer records. It technically can be used for both types of record types. The R864 simply produces a report based on the text message sent in the 864 document.
AR5889 - How to implement OrderPad
Agility
- OrderPad
Implementation Requirements Install the Automated Processing client on a computer that has Internet access and is running constantly. If you are already using supplier returns, there are no additional requirements for use with OrderPad.
Implementation First Steps
Use the Customer Item Quicklist Criteria screen to define criteria records for building quicklists to display based on the customer within the OrderPad screen.
Go to: System Administration > Restricted Processing > Automated Processing > Quicklist Criteria
You can build a quicklist of the top items in the following categories for branch and customer sold-to and/or ship-to or customer reporting group. Top items are based on invoiced orders only.
- Hits – include items sold most often to the customer - Total sales amt – include items with the largest total sales amount sold to the customer - GM % – include top items based on the highest gross margin percentage on the items
** Regardless of criteria, the system creates a unique Quicklist record for each branch, customer, customer level (e.g. sold-to and ship-to record).**
Implementation Next Steps
Go to: System Administration > Restricted Processing > Automated Processing > Queue Maintenance
- Create a Job for each saved criteria - Add job to queue to run on proper interval
If you wish to see supplier rebate information in OrderPad, go to: Sales Orders/Quotes > OrderPad > Right click in the grid > Select Edit Custom View > Add the 'Rebate' field to the 'Show these columns' list
Implementation Final Steps
Start using OrderPad. Agility automatically applies rebates to items in the OrderPad and to new orders when they are released.
If you have access to the 'View Other Cost' security action and the Show Cost option is set, you can review and update supplier rebates for a detail line.
See it in Action
Fastest Way to Check Pricing and Availability for a List of Items
Fastest Way to Check Availability and Price of Tally Items
AR5928 - How to access open orders for a customer within order entry?
Agility
- Sales Orders
To quickly access a list of open orders for a customer you can quickly run a Open Sales Order Viewer from the toolbar. The system automatically loads the customer from the sales order as the customer for the viewer. With the viewer results you then open a related tran by simply double clicking a transaction record, or keep the pending order list displayed in the background while continuing to work on the new order.
Initial Setup Instructions
To define the viewers you want to access within sales order entry complete the following:
Set up a Sales Order Viewer record. On the Information tab of the sales order entry ribbon, click the Saved Viewers toolbar icon. Select 'Add Viewer' Locate the viewer you want to display on your list within sales order entry and click OK. The system adds the selected viewer to your list. How to run the viewer from within sales order entry
Either start a new order and enter the customer shipto, or display an existing order to populate the customer and shipto sequence fields. Click Saved Viewers toolbar icon, locate the desired viewer, then click Run. The system automatically populates the customer into the viewer criteria prior to running the viewer. Note
The Saved Viewers list is custom to each user so each sales agent can customize their viewer list.
AR5929 - Why aren’t my RMAs showing in Order Processing (Print Delv Tickets/RMA tab)
Agility
- Order Processing
AR8907 - How to implement notifications when backordered material becomes available
Agility
- System Administration
AR18591 - AD Payments / Invoice Transaction Upload with Agility
Agility
- A/P
The AD Group has a payment process which involves uploading transactions into a payment center on the ADHQ website. DMSi has created a report to help users with this process by eliminating a manual entry step which can be time consuming and prone to entry error.
This process is also known as the Invoice Transaction Upload
AD Payments with Agility (Invoice Transaction Upload)
This document will walk through the process and setup required to submit payment to AD via the Invoice Transaction Upload and how Agility can help.
There are two areas that you will need to access for this process to work. Each section will be highlighted to help indicate where each step takes place.
AD Payments Portal Agility Accounts Payable Setup Supplier Cross References AD has a list of Suppliers in the AD system. Those Suppliers are associated with AD Supplier Codes. For this process to work, a one-time setup is required to tie the AD Supplier Code to the Agility Supplier Code in your system.
Download the Supplier ID Mapping File Log into ADHQ.com and access the Invoice Transaction Upload under the “Reporting” tab.
Select your Division
Download the Supplier ID Mapping File
Populate the Supplier ID Mapping File The downloaded file will provide a list of supplier codes which will contain the AD Supplier Code and an empty column for the Supplier Account ID which needs to be populated with that Supplier’s Agility Supplier Code. If your company does not buy from a Supplier in this list, simply skip that row.
Upload the Supplier ID Mapping File Once the file is complete. Upload the file to the ADHQ website.
Click “Choose File” Select your saved Supplier ID Mapping file. Click Open
Making Your Payments - Start
Preparing Payments ***This process requires the “ad_payments” report be saved to your system prior to attempting the process below.. If you do not have the report, instructions on how to load the report can be found at the end of this document. For assistance, contact Agility Customer Support ***
Agility Process This section outlines the processes required prior to submitting the Invoice Transaction Upload File. These steps occur in the Agility system and any issues with these processes can be directed to Agility Customer Support.
The general process flow in Agility is as follows:
The AD Member process flow in Agility is as follows:
The new process adds a step which will take place of manually entering the AD Payment information into the Transaction Upload File. Follow your defined processes in Agility and simply insert this step after you have selected your AD Invoices for payment and before you complete your payment in Agility.
Running the Report The Report looks at the invoices that have been selected for payment in the “A/P Select Items to Pay” window in Agility.
Once you have selected items for payment, run the CQ report titled “ad_payments”.
Go To > Report Writer > VCQ Reports
If you do not have access to this menu option, contact your system administrator.
Select and run the report
Select “ALL” Batches
This will generate an excel file in the appropriate Transaction Upload format.
Saving the AD Payments Report The report needs to be saved to your computer. You will need to save this file as a .csv file. There are two possible ways this report will open. B is the most likely of the two possibilities
If the Excel file opens within the hosted site,Save this file to a folder you are familiar with as a .csv file. Then Copy this file and save it to you PC Desktop. If the Excel file opens on your PC Desktop.Save the .csv file in a folder you are familiar with. To save as a .csv file, in Excel go to the File menu and select “Save As”. In the “Save As” window, select “Save as type:” and choose “CSV (Comma delimited).
*** Remember where you save this file. ***
AD Payment Upload AD Provides a secure payment upload template. The information that has been gathered from Agility needs to be copied into this template prior to uploading the payment file.
Download the Template Go to the AD Invoice Transaction Upload site. In the AD Payment Center, click the “Download Payment Template” button.
Open the downloaded file and open the saved “ad_payments.csv” file that was saved from Agility. Then, copy and paste the invoices (not including row 1) from the “ad_payments.csv” file to the AD Payment Template file. Once finished, save the AD Payment File.
Submitting the Payments Click “Enter Payment” on the AD Payment Center/Invoice Transaction Upload site.
Enter payment details:
Enter the Payment Details Select the Payment File Click “Continue to Review” If there are issues with the file, the Review process will identify them and questions can be directed to the ADHQ Accounting Team.
Completing Payment Don’t forget to complete your payment in Agility. Whether you use the check method or the non-check payment, the payment needs to be fully processed. Follow your company’s defined procedure for completing the payment.
Making Your Payments - Finish
Loading the CQ Report Step 1 is to load the CQ Report into Agility. This is a Customer Report and the exact code is listed below.
Open the VCQ Report WriterIf the Report Wizard opens, “Cancel” and select the Language Editor Paste the following code into the “Enquiry” window.
AD CQ Code START COPY ON NEXT LINE
viewpoint native;define number xremitamount = apinvhdr:amount - apinvhdr:discount_amount; --as specified by AD file requirements number xremitdisplay = if apinvhdr:voucher_type = "CM" --Displays credits as a negative number then xremitamount*-1 else xremitamount; string xblankcolumn = "" ; --necessary for formatting to AD file requirements string xbatch = parameter prompt "Enter Batch ID or ALL" default "ALL" ; number xinvamount = if apinvhdr:voucher_type = "CM" --Displays credits as a negative number then apinvhdr:amount*-1 else apinvhdr:amount; number xmonthnum = month (apinvhdr:invoice_date)/leadingzeros/width= 2 ; -- converts the month to a number for future processing string xmonthform = if xmonthnum<10 --if the month is less than 10, this will create a 0 prefix which ensures formatting of MM then "0" + str (xmonthnum) else str (xmonthnum); number xdaynum = day (apinvhdr:invoice_date)/leadingzeros/width= 2 ; -- converts the day to a number for future processing. string xdayform = if xdaynum<10 --if the day is less than 10, this will create a 0 prefix which ensures formatting of DD then "0" + str (xdaynum) else str (xdaynum); string xyearstr = str ( year (apinvhdr:invoice_date)); --converts the year portion of the date to a string. string xdatedisplay = xmonthform+"/" +xdayform+ "/" +xyearstr; --This brings all peices together with formatting so excel does not apply date formats. where apinvpay:posted_to_gl = 0 and apinvpay:cancelled = 0 and (apinvpay:batch_id = xbatch or xbatch = "ALL" )list /duplicates/noendofreport/noreporttotals/nopageheadings/xls/domain= "apinvpay" suppname:supplier_name/heading="Supplier Name" suppname:supplier_code/heading= "Supplier Account ID" apinvhdr:reference_number/heading= "Invoice Number" xdatedisplay/heading="Invoice Date (MM/DD/YYYY)" xinvamount/heading= "Original Invoice Amount" xremitdisplay/heading= "Remittence Amount" apinvhdr:discount_amount/heading= "Affiliate Discount Taken" apinvhdr:tax_amt/heading= "Tax Amount" /decimalplaces= 0 xblankcolumn/heading="Reason Code" sorted by suppname:supplier_name
END COPY ON PREVIOUS LINE
Go to “File” and click “Save enquiry as… Save the Enquiry”.Click the “Up Folder” option to ensure that you are in the “cq_reports” folder. Save the Enquiry as “AD_PAYMENTS”.Be sure to include the “_”. Spaces do not work well with the compiler.
Click Save The report is now ready to run from CQ.
*Optional – Adding the Report to your Dashboard
If you need assistance compiling the CQ Report and adding it to your Dashboard, contact DMSi Agility Support
AR18597 - How to run the On Hand Summary Viewer
Agility
- Inventory Control
How to run the On Hand Summary Viewer The On Hand Summary Viewer can be used to view on hand tally records for one or more items, move inventory to new locations and create sales orders or remans on the fly.
Steps to run the On Hand Summary Viewer 1. I n Agility, access Inventory Control > Queries/Reports > On Hand Summary Viewer.
2. Enter an item or items in the search criteria on the 'Criteria' tab.
a. You can search for a single item by entering an item code in the Item field
b. You can search for an item list by clicking on the Item List button and selecting Item list in the Selection method dropdown . Enter item codes in the Item field and click on the 'Add' button to add items to the list.
c. You can search for an item range by selecting Item range in the Selection method dropdown and entering an item code in the 'From' and 'To' fields.
3. Select additional criteria to narrow your search. Depending on the items included in the search criteria, more options may become available on the Criteria tab to narrow your search further.
Additional search criteria fields include: Lot, Tag, On Hand, Available, Tally UOM, PO ID, Supplier ID, Last receipt date, Lengths, and Widths.
4. After all selections have been made, select the Run button to generate the On Hand Summary Viewer. A new window displays with the results of the search.
Moving material to a new location You can move material to a new location using the On Hand Summary Viewer.
Highlight the line or lines (using Control + click) that you need to move location. Click the Assign New Location icon. Select the new location, then click 'OK'. * In order to do this, you must have a ‘New location reason’ specified in Branch Parameters (System Administration > Module Controls > Branch Parameters, Inventory Settings tab)
Viewing tag details in the On Hand Summary viewer Set Level to view inventory to Tag in order to view tag details for a hardwood-PC item or for a hardwood-BF item with actual dimensions. There are multiple ways to view tag details:
1. Highlight a line on the viewer and click the enabled View Tag Details icon. The View Inventory window displays.
2. Highlight a line on the viewer and double click on the line. The View Inventory window displays.
3. Expand a line by clicking on the plus to the left of the line. This will display a child record with widths and pieces for the tag in addition to a total footage.
a. Click on the plus next to the child record to display another child record that shows the widths, lengths, pieces, and footage in the tag.
Note: Hardwood-BF items with actual dimensions display with the full quantities received for the tag in the tag details/child record. If a partial tag exists the tag details/child record still displays with the quantities as the material was received.
4. Right click on the viewer and choose Expand All Details. This expands any child records that exist for each line on the viewer.
Creating a new reman in the On Hand Summary Viewer When Level to view inventory is set to Tag, the Create Reman button is enabled for items carried at the tag level. Create reman commits the full tag or tags selected to the reman work order input items.
To create a reman from the On Hand Summary Viewer:
Set Level to view inventory to Tag Highlight each line you wish to create a reman for Click on a line to highlight the line. Use Shift+click to select a range of lines. Use Ctl+click to select multiple lines that are not next to each other. Click on the 'Create Reman' button. The Info for Reman window displays. Complete any additional fields and click 'OK' to create the reman. Creating a new sales order in the On Hand Summary Viewer When Level to view inventory is set to Tag, the Create Sales Order button is enabled for items carried at the tag level. Create Sales Order commits the full tag or tags selected to the sales order detail
To create a sales order from the On Hand Summary Viewer:
Set Level to view inventory to Tag. Highlight each line you wish to create a sales order for Click on a line to highlight the line. Use Shift+click to select a range of lines. Use Ctl+click to select multiple lines that are not next to each other. Click on the Create Sales Order button. The Create New SO window displays. Click OK to create the sales order. Additional Grid Options for the On Hand Summary Viewer The functions below are available when right-clicking within the On Hand Summary Viewer grid.
Filter – Display records that meet selected criteria. Once filtering is enabled you can click on the filter in a column to view and select your filter options. Right-click and unselect Filter to disable filtering. Group by Field – Show the option to drag a column header to group data by that column. Clear Groups – Remove the current group(s) selected but retain the Group by Field function. Collapse All Groups – Hide the details of the groups. Expand All Groups – Display the details of the groups. Collapse All Details – Hide the details of all grid sections. Expand All Details – Display the details of all grid sections. Export Grid – Export the data in the grid based on the option selected on the Export To window. The export function applies to all columns/data selected to display, regardless of whether the values are currently visible on the screen. Export Grid To – Select option to use when exporting data from a grid. If you select Choose Default Option, the Export To window displays for selecting the export option. Set Always export using this setting, to specify a default export option the system automatically uses when you select the Export option for grids. If you clear the value for Always export using this setting, the system clears the default export option and displays the Export To window the next time you select to export data from the grid.
AR18603 - How to Implement and Automate the Customer Net Profitability Report
Agility
- Sales Orders
Implementation Requirements
Install the Automated Processing client on a computer that has
Internet access and is running constantly.
Implementation First Steps
Determine what the cost per line or transaction for different sale types is. To determine this use cost to serve measurements or simply take operating expenses (not contributing to Gross Margin) divided by number of sales orders or lines for a branch for a time period. These cost to serve figures are used to 'Apply additional costs per Transaction or Line Item' on the Report Options tab of the Customer Net Profitability Report.
Implementation Next Steps
Go to: Sales Orders > Queries/Reports > Customer Net Profitability On the Selection Criteria Tab - Select the branch used for cost to serve figures in the first step. - Select the Customer range, Sale Type range, Sales Agent range and Entered by for the report. Typically 'All' is selected for each of these criteria. - Select the transaction type, typically 'Invoices'. - Select the relative date for the report, typically a range like the past 3, 6 or 12 months. On the Report Options Tab - Typically the Cost Type is 'Default'. - Set the 'Apply additional costs per' based on how you calculated cost to serve amounts for operating expenses. - Set the additional costs for Direct orders, Warehouse orders, Will call order and Credit memos. - Set the sale types for will call transactions - Set the desired sort and subtotals as well as rank option desired. If exporting to Excel, unselect print report headings otherwise set report headings options as desired. Save the criteria for the Customer Net Profitability Report for All Users, a User Group or a User with a name that indicates what the criteria includes.
Implementation Final Steps
Go to System Administration > Restricted Processing > Automated Processing > Queue Maintenance - Create a Job with the Customer Net Profitability Report that was saved in the previous step - Create a Queue and include the Job from the previous step - Schedule the Queue to run as frequently as you would like
AR18605 - Branch Transfer Best Practice
Agility
- Branch Transfers
Branch Transfer Process (Manual) This is an overview of the Branch Transfer process in Agility. The Process is very similar to processing a regular Purchase Order and Sales Order. The difference is that the Purchase Order is placed with another branch and the Sales order is automatically created in the other branch. How the Sales Order is priced and how the G/L transactions are posted is based on your unique set-up. This is a review of how to create the Orders.
1. Enter Requesting Branch PO
2. Route shipping sales order
3. Invoice Shipping sales order
4. Manually Receive requesting PO
a. Pre-receipt records from invoiced sales order will default
b. If you allow qty to be changed in receiving you will catch any changes in next step
5. Run Branch Transfer Audit report to catch variances between what was received and what was invoiced
Entering the Requesting PO 1. Make sure you are in the branch that is requesting the material
2. Enter the branch that will be shipping the material
3. Enter the items as you would a regular PO
4. Click save and you will see the transfer SO on the PO header tab
Shipping the Transfer Order During this process you should be routing transfer orders with your other orders. They should display in the same viewers that you are looking at to ship customer orders so it goes in your queue for picking/shipping.
Invoicing the Shipping Sales Order Our best practice is to invoice the shipping sales order as soon as it leaves the shipping branch.
There is even a security setting that doesn’t allow users to receive a PO before it has been invoiced by the shipping branch.
We do this because, if you are confident in what was supposed to be shipped and loaded on the truck, that is what should arrive that the requesting branch. If it isn’t, it will show up in the Branch Transfer Audit Report and alert you that there may be an issue.
Receiving the requesting PO This process should be the same as receiving a regular stock PO.
Branch Transfer Audit Report On a daily basis, you should be running the Branch Transfer audit report to catch any variances. This report will only work correctly if the Shipping Sales order has been invoiced and the receiving PO has been received because the report compares the invoice with the receiver.
There are various options on the report and the one most used is ‘only include if variance is >=’ a value. The variance theoretically should be zero, so you can set this at .01 to catch any issues.
AR18607 - How to keep certain orders from showing in SPOs
Agility
- Purchasing
AR18608 - What does the define branch columns button do in a SO viewer?
Agility
- Viewers
AR18640 - How to Update the Agility Automated Processor Client URL
Agility
- Automated Processing
How to Update the Agility Automated Processor Client URL Section 1 If Automated Processing jobs/queues are not running, it may be due to the Automated Processor Client not being on the same server that Agility is installed on. You can update the configuration file by updating the URL on the Automated Processor Client (rather than reinstalling the client).
The Automated Processor Client should be installed on a server or PC that is powered on 24/7 and is connected to the internet. It is typically located on the Local Drive of the PC in the DMSi folder. If you need help locating the client, you can verify the path to the executable by following the directions in Section 2.
Once you have located the Agility Automated Processor, right-click on the “configuration.xml” file and select Open with > Notepad
The configuration file should look similar to the screenshot below.
Update the SessionConnectionURL in the text file to the new server name. Accounts changing to the St. Louis TierPoint server will use the website domain, http://stlapc1.dmsi.com followed by the customer unique webservice name.
For example, http://stlapc1.dmsi.com/dmsidevelprod/dmsidevelprod
If you have questions on your Account’s webservice name, please contact Agility Support.
After you have updated the SessionConnectionURL, Save the .txt file.
Automated Processing jobs/queues should run successfully.
Section 2 Locating the Agility Automated Processing client
If you are having trouble locating the Agility Automated Processing client, try searching for Computer Management from your Windows Start Menu.
In the Computer Management window, locate the Agility Automated Processor using the path:
Computer Management > Services and Applications > Services > Agility Automated Processor
Right-click and select Properties
The Path to executable will show you which drive the Agility Automated Processor is located on.
If you don’t see the Automated Processor Client, it is not installed on the PC and you will need to locate the PC with the client on it.
AR18698 - Cyberquery (CQ) sample: POD Signature Verification
Agility
- Cyberquery Samples
This report prints an audit for POD signatures that were captured for orders with a ship date equal to the run date or the day before. The report lists all orders by route and if the signature was captured, handwritten, or not captured.
-- The report does not contain any prompts to allow running in the automated processing on a daily basis. This report may need to be modified to exclude branches that are not using POD and also to exclude routes that are not delivery routes.
--This report will need to be copied into a macro. To copy the report into a macro open the report writer and then in the upper left of the screen click on “File” and “New” and select Macro.
--You can also automatically open a macro by using the key sequence of CTRL-M. Since the entire report is in a macro there is no need to compile the query.
--Suggested Naming Convention: pod_signature_verification.mf
/* pod_signature_verification This report prints the orders with a ship date of today or the previous day along with how the signature was captured */
define string ximage = if related_image:image_info = null then "Not Captured" else "Captured"; define string xno_sig = if related_image:no_signature = 1 then "Customer not available" else "Customer present"; define string xresults = if ximage = "Captured" and xno_sig = "Customer not available" then "Customer not available" else ximage;
where related_image:image_type = "POD Signature" and related_image:related_table = "shipments_header"
list/domain="related_image" /nodetail /hold="hf_related_image" related_image:related_table related_image:related_table_guid related_image:image_info /heading="Text of Signature" ximage /heading="Image Avail" xno_sig /heading="Customer Avail" xresults /heading="Results"
sorted by related_image:related_table_guid
end of related_image:related_table_guid /noheading related_image:related_table related_image:related_table_guid/keyelement=1 related_image:image_info ximage /name="image_avail" xno_sig /name="cust_avail" xresults /name="results" ;run define date xdate1 = todaysdate-1;
define file ximage = access hf_related_image, set hf_related_image:related_table_guid = shipments_header:shipments_header_guid, outer join;
define string xstatus = switch(shipments_header:status_flag) case "S" : "Staged" case "L" : "Loaded" case "E" : "En Route" case "D" : "Delivered" case "I" : "Invoiced" default : shipments_header:status_flag;
define xcustomer = cust_shipto:cust_code + " - " + str(cust_shipto:seq_num);
define string xroute = if shipments_header:route_id_char > "" then uppercase(shipments_header:route_id_char) else if so_header:route_id_char > "" then uppercase(so_header:route_id_char) else " ";
define number xall = 1; define number xsig = if ximage:results <> null then 1 else 0;
define string xtype_name = if ximage:results = "Captured" and ximage:image_info <> "" then "Typed:"+ximage:image_info else if ximage:results = "Captured" then "Handwritten Only" else if ximage:results = null then "Not Captured" else ximage:results
define xvalid = if sales_type:transfer = 0 and sales_type:will_call = 0 -------Need to remove this if Will call routes should be included and xroute not one of " " --------May want to add common carrier routes here and sales_type:inv_affect = 1 --------This excludes directs and other nondelivered sales types then "Y" else "N" where shipments_header:type = "SO" and shipments_header:ship_date => xdate1 and shipments_header:ship_date =< todaysdate and shipments_header:shipment_num = so_header:shipment_num --and shipments_header:system_id one of " " --add branches to process otherwise all branches will process and xvalid = "Y"
list/domain="shipments_header" /nobanner/duplicates/noheadings/nopageheadings /title="Daily ePOD Signature Verification" /pagelength=66 xcustomer /width=16 cust_shipto:shipto_name shipments_header:so_id /width=8/nocommas shipments_header:shipment_num /width=8 /center shipments_header:ship_date /mask="mm/dd/yyyy" xroute /width=10 xstatus /width=12 xtype_name xall/hidden xsig/hidden
sorted by shipments_header:system_id shipments_header:ship_date xroute cust_shipto:cust_code cust_shipto:seq_num shipments_header:so_id
top of xroute /noheading
"Route: "+xroute +" "+delv_route:description+" Ship Date: " + str(shipments_header:ship_date,8)/newline "Invoicing"/align=xstatus/newline "Customer"/align=xcustomer "Name"/align=cust_shipto:shipto_name "SO ID"/align=shipments_header:so_id "Ship #"/align=shipments_header:shipment_num "Ship Date"/align=shipments_header:ship_date "Route"/align=xroute "Status"/align=xstatus "POD Status"/align=xtype_name
end of xroute " "/newline "Total Orders: " + str(total[xall])/align=cust_shipto:shipto_name "Responses: " + str(total[xsig]) "Captured: " + str((total[xsig] divide total[xall]) * 100) + "%"/newline
top of page/noheading "Report run for starting date of: " + str(xdate1,8) "Page number: " + str(pagenumber)/align=xstatus/right/newline=2
if pagenumber <> 1 then { "Route: "+xroute + " "+delv_route:description+" Ship Date: " + str(shipments_header:ship_date,8)/newline "Invoicing"/align=xstatus/newline "Customer"/align=xcustomer "Name"/align=cust_shipto:shipto_name "SO ID"/align=shipments_header:so_id "Ship #"/align=shipments_header:shipment_num "Ship Date"/align=shipments_header:ship_date "Route"/align=xroute "Status"/align=xstatus "POD Status"/align=xtype_name }
;run rreplace pod_signatures view
AR18809 - Agility Mobile Sales app - Login Troubleshooting
Agility
- Agility Mobile Sales
Agility Mobile Sales app – Login Troubleshooting The information contained in this article pertains to the version of the Agility Mobile Sales app that requires Agility v531 or higher. If the older version of the app is installed, DMSi suggests deleting the old version and installing the new version of the app. You can find the new version of the app in the App/Play Store by searching for Agility Mobile Sales .
There are several messages that may appear when login is unsuccessful. Typically, Invalid User ID or Password displays to indicate there is an issue and this can be associated with a variety of different causes. Unless the message is specifically noted in the steps below, you may assume the step pertains to the Invalid User ID or Password message displayed upon login.
1. If the message received is Unable to find connection information , retry the login. If not successful, contact DMSi Support. 2. If the message received is Server returned an error , retry the login 1 or 2 more times. If failures continue, use the below steps. 3. If the Agility environment is locally hosted and you do not have an SSL certificate installed on your server to run https, please contact DMSi Support. 4. Verify the user has entered their user ID as <AgilityUserID>@<orgid> or <AgilityUserID>.<orgid> 5. Verify the user entered their Agility password correctly. 6. Verify the user has been granted access to the Agility Mobile Sales product in Agility > System Administration > Security Administration > User Profiles. 7. If Agility Mobile Sales does not exist as an available product, verify the license for Agility Mobile Sales has been granted. If the license is not granted, contact DMSi Support. Prior to v534, the license record for the Agility Mobile Sales product will not be visible. Contact DMSi Support for verification. 8. If the message received is V531 is required , verify the environment is on v531 or higher. a. If the environment is on v531 or higher, contact DMSi Support to verify the necessary components are set up and working as expected.
AR18982 - Loyalty Program-Sales Order Entry
Agility
- Sales Orders
SALES ORDER ENTRY – DISPLAY NEW FIELDS
With the addition of the Loyalty Program in v533, Sales Order Entry now has new fields available to add to the Order Information section and a new payment icon available for reward redemption. The Reward Credit icon is enabled when there are available reward credits and a reward payment method is set up (#1). The following fields can be added by going to Information > Edit Layout > Order Information section: • ‘Reward available’ - shows the total of the reward credits that are available to be used(#2) • ‘Reward expiration’ - shows the earliest expiration date of the available rewards(#3) • ‘Loyalty points earned’ - shows the points accumulated that haven’t been converted to a reward when the accumulate by is points(#4) • ‘Loyalty dollars earned’ - shows the dollars accumulated that haven’t been converted to a reward when the accumulate by is percent of sell (not pictured). Use the ‘Reward available’ field dropdown to see the individual reward credits that make up the total. View the expiration date and created date also in this dropdown to inform customers as to when rewards are expiring. ‘Loyalty points earned’ and ‘Loyalty dollars earned’ allows your users to see how close a customer is to getting the next reward so that they can provide a status update to the customer when the order is being placed. If a customer belongs to multiple enrollment plans that accumulate by the same unit, this field shows the sum of those accumulations. For example, my customer belongs to Loyalty Plan A and has 125 points accumulated. They also belong to Loyalty Plan B and has 50 points accumulated. The ‘Loyalty points earned’ field shows 175 points.
SALES ORDER ENTRY – REWARD REDEMPTION
The Reward Credit icon opens a payment window where users can select which reward credits they want to apply to the order. • If the order total is less than the reward credit, only the amount of the order is used from the open reward credit. • If the order total is more than the reward credits, all available reward credits apply to the order. • A user can choose which reward credits apply to the order by clicking on the dropdown in the reward credit applied amount field. This dropdown shows the applied selector, amount of the open reward, and the expiration of the reward credit. The reward credits are very similar to deposits and will appear as deposits do in AR inquiry windows until the order is invoiced.
SALES ORDER ENTRY – CANCEL LOYALTY REDEMPTION
If a Reward Credit payment is applied in error, the payment can be deleted from the order before it has been invoiced from the Previous Payments window. Once a payment is deleted, it will show an amount in the “Cancelled” column.
AR19024 - Loyalty Plan Manager Overview
Agility
- Sales Orders
Loyalty Plan Manager Overview The Loyalty Plan Manager window is where you are able to research rewards and accumulations created, converted, redeemed, and/or expired. The Search by option determines if you are looking at rewards or accumulations.
Grouping The grid allows for grouping so that you can quickly filter/summarize the data being presented at a header level. You can expand the group to see details under this header record. To turn on grouping, right click in the grid and select Group by Field . Once selected, you can drag the column heading up to the group section to have the grid group by that column.
The below screenshot shows grouping by Customer name.
Columns The customizable grid allows you to change the order in which the information is presented. To edit the grid, right click in the grid and select Edit Custom View .
The Customize View window allows you to add columns to the grid by double clicking or selecting them and using the arrows to move them over to the Show these columns in this order section. To change the order of the columns, select the column and use the Move Up/Move Down buttons. The Move Up button moves columns to the left and the Move Down button moves columns to the right in the grid.
Select Summaries The Select Summaries option allows you to summarize data at the group level so you don’t have to expand the details to see the data. In the below screenshot, the Sum feature is turned on for the Open amount and shows the sum of all the open amounts for customer Patrick Cropsey.
Setting up search criteria The Search Criteria section allows you to set up different criteria to meet different needs. Criteria can be saved, allowing you to quickly access information. There are two default criteria selection already in place: Open Rewards and Open Accumulations. Once the criteria has been modified to your liking, select Save Criteria and save your selections with the name of your choice and who is allowed to access it. You must have the action allocation to save criteria set for your user in order to complete this function. Criteria is saved with the Search by selection as there are different columns available for rewards and accumulations.
Below, the Open Rewards criteria has been modified and with the name Reward Created this week and is set to search for rewards created in the past 7 days that have an Open status.
Running the Plan Manager Once you have search criteria set up, select the Search Records button to pull in records. If changes are made to the criteria, select Refresh Records to refresh the grid.
Update Rewards The Update Rewards button is available viewing rewards in the grid results. After selecting reward records in the grid and selecting this button, you have the ability to update the expiration date. Moving the expiration date into the past updates the status of the reward to Expired and g/l postings will be made. If an expired reward is reinstated (expiration date moved to the future and an expired open amount exists), then the reward credit is updated to a status of Open and the expired amount becomes the open amount to be used in SO Entry.
Accumulations Parent/Child Grid Accumulations show a little differently than rewards because there is a header record created for each invoiced shipment and enrollment plan. Detail records underneath that header are broken down by the line items that make up the accumulations. The customizations covered above apply here, but there will be two grids that can be customized based on where you click: header grid or line items.
In the below screenshot, item PHIS2068 accumulated 2,004 points and NAILS accumulated 3 to make up the 2,007 on this accumulation record created for tran 3282.
AR19063 - How to customize item keywords (Agility v535 and later)
Agility
- Inventory
How to customize item keywords (Agility v535 and later) You can use keywords to search for items. Item keywords are based on a combination of item-related field values and additional user-defined keywords. The following steps walk you through how to customize item keywords to best suit your needs.
Review Item keyword values in System Configuration Settings The selections in the Item keyword values field in System Configuration Settings control which pieces of item-related information to use as keywords. These keywords are automatically generated when you create an item, or you update information in the selected fields. By default, Item, Size, Item description, and Item extended description are selected.
In Agility, access System Administration > System Configuration > System Config > Misc Settings tab. Select the Item keyword values dropdown and review the current selections. To make changes, set the field information you would like to include automatically as item keywords. Select the drop-down to close the selections. If you changed settings, click Save. Rebuild the item keywords After changing the Item keyword values, run the support program to rebuild the keywords based on the new settings. Run the rebuild outside normal business hours to avoid performance degradation.
In Agility, access System Administration > Restricted Processing > Support Programs. From the Select Program dropdown , choose rblditmkywd . Select Move to populate the program in the Selected Programs list and select Run. Select Yes to the prompt asking if you are sure you want to perform the rebuild. In the Item Keyword Rebuild window, set the parameters for the items you want to include. To rebuild all of the items in your system, change the Branch to <all> and set all Update Criteria options to All. Select Update and then select OK to the message informing you to check the log for errors. If you experience problems with keywords after running the rebuild, check the log referenced in the message. Add user-defined keywords You can add additional keywords to an item to be included along with the keywords generated based on the System Configuration Settings.
In Agility, access Data Files > Item Information > Items. Search for the item using the Search by locator at the top of the screen then select the Misc tab and add the keywords to the User-defined keywords field with a space between each word. Select Save. When you save the item, the Keywords field is updated to include the user-defined keywords.
AR19104 - What info does Agility use for trending in Reorder Calculations
Agility
- SPO
AR19201 - Why won't my interface create a non-stock item?
Agility
- Interfaces
Why won't my interface create a non-stock item? What is the problem being encountered? Sometimes when creating items via an interface the processing activity log will give an error stating that it could not create the non-stock item. The sales order is not created after processing the file via E-Commerce > Process Incoming Files.
What does this mean? Agility was not able to create the non-stock item for one of two reasons:
The template item set up to be used with the interface is invalid Other item codes starting with the same letters as the non-stock prefix used by the interface exist either in the branch the file is being processed in, or in a branch which shares items with that branch How to troubleshoot and resolve the issue? The first stop to figuring out why the interface could not create a non-stock item is to check that the non-stock template item on the interface is a valid template item.
In Agility, access E-Commerce > Interface Maintenance Locate the interface you are having the issue with and make note of the non-stock template item code in the field. In Agility, access Data Files > Item Information > Items in the same branch as where the interface is being processed and search for that template item. Did the item display when you searched for it?If no, the item is not a valid item, and a new non-stock template item will need to be saved for the interface within the Interface Maintenance window. If yes, double-check the Branch Settings tab within Item Maintenance to verify that the item is set up to be active and used as a template item. As long as the non-stock template item is both active and set up as a template item, the next troubleshooting step is to see if there are other items set up with the same starting letters as the non-stock prefix used by the interface. Some interfaces will allow you to define a non-stock prefix to use when creating items, while others can only use the default value.
Default values for non-stock prefixes on each interface are:
Interface NS Prefix AMSCO Window Navigator AM Cascade Frontier Power Bids CW Eagle Windows and Doors EV FeneVision FV Gerkin Windows and Doors GW HomeCrest Cabinetry HC Anderson Intelligent Quote (iQ) IQ Kolbe-Kolbe Millwork KK Kasson and Keller KN Loewen QuoteMaster LW Milgard Windows and Doors MG Marvin Windows MV Ply Gem Windows PG Reeb Windows via Saberis Interface RB Silver Line Windows SL Sierra Pacific SP Lincoln Wood/Timeline Windows TL Viwinco Windows via Saberis Interface VW Wincore Windows and Doors WC Windsor Windows and Doors Win-Quote WS Ellison Window Wizard WW 20/20 Technologies TT
If your items are created with a different prefix, you need to verify which prefixes are set up in your branch for that interface.
In Agility, access System Administration > Restricted Processing > Interface/Form Setup Locate the interface having the issue. Use the arrows at the top to scroll the tabs to the right until you see the Options tab and click on it. Set the Options drop-down to Select NS Prefix to see the list of prefixes that were manually defined for the interface. Once you have verified which non-stock prefix your items should be created with, you will need to run a Cyberquery report to list out other items that begin with that same sequence of letters. This query needs to look at the branch where the item maintenance records are coming from. In some cases, this may be a different branch if your branches share the item maintenance table.
To verify whether your branch shares the item maintenance table with other branches:
In Agility, access System Administration > System Controls > System Profile Definition. Scroll the Category Assignment grid down to the Item Maintenance entry. If the System ID and Branch ID match the branch you’re currently in, the branch does not share item maintenance records with other branches. If another branch’s ID shows in these columns, such as 00CORP, the item maintenance records are shared and the branch to be used in the query will be the Branch ID shown in Category Assignment.
Once you know which branch to use in the query:
In Agility, access Report Writer > VCQ Report Writer.If the wizard displays, cancel out of it and click on the keyboard icon to open a new language editor window. With the language editor open, copy and paste the query below into the Enquiry section.viewpoint native;where item:system_id = "BRANCH" and item:item begins with "NS PREFIX" list /domain="item" item:item item:created_date item:created_bysorted by item
Replace the BRANCH and NS PREFIX text with the appropriate branch code and non-stock prefixes you need to search for. Press F6 on your keyboard or click the icon of the running person to run the query. Once the results display, scroll the list down to find items that do not follow the numeric sequence the interface is using to create non-stock items.This will typically look like the screenshot below, where the auto-generated items are above the red line, and the items using the same letters as the non-stock prefix are below the red line. The items using the same non-stock prefix (MV in this example) prevent Agility from knowing where the end of the numeric sequence is when it’s processing the interface files. This stops it from creating the non-stock items.
In order to correct the issue, the items after the numeric sequence (items below the red line in the screenshot) will need to be renumbered to an item code which does not start with the same letters as the non-stock prefix. Once there are no more item codes starting with the non-stock prefix outside of those created by the interface, Agility will be able to process the interface files and create non-stock items again.
For assistance with item renumbering, please see article AR825 .
AR19261 - Period End Procedures Checklist
Agility
- General Ledger
Period End Procedures Checklist 1. Prior to End of Period1. Complete all day-end procedures. Refer to the Day End Procedures Checklist for instructions.
2. Establish a date and time for the period-end shipping/receiving cutoff.
3. Complete all receiving, invoicing, cash application, write-offs and credit memos for period.
4. Open new G/L accounting period: Select General Ledger > End of Period > Open Closed G/L Periods.This step is not necessary when changing the current period using Automated Period End.
2. Accounts Payable5. Enter any accounts payable service charges: Select Accounts Payable > Payments > Service Charge Entry.
6. If A/P is not set up to direct post, manually post monthly A/P transactions : Select General Ledger > Posting Functions > A/P Posting to G/L. *
7. Print A/P Aged Open Payables Report and balance to A/P Trade G/L account: Select Accounts Payable > Reports > A/P Aged Open Payables.
8. Print A/P Aged Open Payables Report in detail mode to aid in reconciling A/P: Select Accounts Payable > Reports > A/P Aged Open Payables. Run this report before entering new activity for the next period.
9. Optional: print A/P Trial Balance Report to aid in reconciling A/P: Select Accounts Payable > Reports > A/P Trial Balance Report. Run this report before entering new activity for the next period.
10. Print A/P Recon Register for all out-of-balance AP Recon records: Select Accounts Payable > A/P Recon > A/P Recon Register. Run this report after entering payables, receivings, and receiving adjustments for the current period and before entering new activity for the next period.
11. Print G/L Detail Report for A/P accounts: Select General Ledger > Reports > G/L Detail Report.
12. If not already open, open new A/P accounting period: Select Accounts Payable > End of Period > Open Closed A/P Periods.
13. Change default A/P accounting period to the new A/P period: Select Accounts Payable > End of Period > Change Default A/P Period.This step can be done using Automated Period End.
14. Close prior A/P accounting period: Select Accounts Payable > End of Period > Close Open A/P Periods.This step can be done using Automated Period End.
15. Reconcile A/P checks and service charge entries against bank statement: Select Accounts Payable > Check Administration > Bank Reconciliation . This step is completed once your month end bank statement arrives.
3. Accounts Receivable 16. Review Unbilled Orders Report to ensure all billing has taken place for the period: Select Sales Orders/Quotes > Unbilled Orders.
17. If A/R is not set up to direct post, manually post monthly A/R transactions : Select General Ledger > Posting Functions > A/R Posting to G/L. *
18. Print Finance Charge Report to verify charges; then select option to print report and apply charges: Select Accounts Receivable > Open Items > Finance Charge Application.
19. Print A/R Aged Trial Balance to balance accounts receivable aging to A/R Trade account: Select Accounts Receivable > Reports > A/R Aged Trial Balance.Run this report before entering invoices, credit memos, A/R write-offs, A/R adjustments, or applying cash for the next period .
20. Print G/L Detail Report for A/R accounts: Select General Ledger > Reports > G/L Detail Report.
21. Print customer account statements: Select Accounts Receivable > Open Items > Print Acct Statements.
22. Print A/R Tax Summary/Detail Report: Select Accounts Receivable > Reports > A/R Tax Summary/Detail.
23. Print A/R Cash Reconciliation Report: Select Accounts Receivable > Reports > A/R Cash Reconciliation Rpt.
24. Optional: Run additional period end reports as required by your company.
25. If not already open, open new A/R accounting period: Select Accounts Receivable > End of Period > Open Closed A/R Periods.
26. Change default A/R accounting period to the new A/R period: Select Accounts Receivable > End of Period > Change Default A/R Period.This step can be done using Automated Period End.
27. Close prior A/R accounting period: Select Accounts Receivable > End of Period > Close Open A/R Periods.This step can be done using Automated Period End.
28. Reconcile deposits to the bank statement: Select Accounts Receivable > Payments > Bank Reconciliation. This step is completed once your month end bank statement arrives.
4. General Ledger 29. Change default G/L accounting period: Select General Ledger > End of Period > Change Default G/L Period.This step can be done using Automated Period End.
30. Make journal entries and reversing entries.
General Ledger > Journal Entries > Journal Entry General Ledger > Journal Entries > Make Manual Reversing Entry 31. If the default posting option is manual post, manually post open entries : Select General Ledger > Posting Functions > Post Journal Entries. *
32. Review and post any entries set to hold for review.
33. Print G/L Trial Balance Report and verify ending balance is in balance: Select General Ledger > Reports > G/L Trial Balance Report.
34. Reconcile accounts. If you want to reconcile Sales and Cost of Goods Sold to the G/L, print the A/R Detailed Sales Report and the G/L Detail Report for all Sales and Cost of Goods Sold general ledger accounts. If you include branch transfer sale types in the A/R Detail Sales Report, include transfer clearing accounts in the G/L Detail Report.
Select Accounts Receivable > Reports > A/R Detailed Sales Report. Select General Ledger > Reports > G/L Detail Report 35. Verify the Inventory – WIP, Operations in Process, and Invalid Posting account balances are zero. If the balances are greater than zero, research the entries and enter adjustments to reduce the balance to zero.
36. If you process branch transfer transactions and any branch transfer parameter records do not specify transfer clearing accounts, print the Branch Transfer Audit Report: Select Inventory Control > Queries/Reports > Branch Transfer Audit Report. Write off branch transfer A/P Recon records to the appropriate transfer clearing accounts to remove A/P Recon records for transfers and to balance your transfer clearing accounts.
37. Close prior G/L accounting period: Select General Ledger > End of Period > Close Open G/L Periods.This step can be done using Automated Period End.
38. Optional: Export the G/L data if you use F9 Professional® to create financial reports: Select System Administration > External Interfaces Processing > Export G/L Data. **
39. Print financial statements: Select General Ledger > Financial Report Writer > Print/Export Financial Rpt. **
5. Inventory and Data Warehouse 40. To reconcile inventory, print the Inventory Valuation Report on a period-end basis and retain as a permanent record: Select Inventory Control > Queries/Reports > Inventory Valuation.Run this report before entering work orders, receiving, physical inventory, inventory adjustments, or invoices for the new period.
41. Run daily item activity program in data warehouse (if not done as part of day end procedures): Select Data Warehouse > Update Data Whse.
42. Run monthly summary data programs in data warehouse: Select Data Warehouse > Update Data Whse > Criteria 2.
43. Purge audit records older than 3 months: System Administration > Performance Tuning > Automated Purges.
Use a setting of <all> in the Table Name field. These audit records are generated by application of user-defined and system-defined audit rules and are intended only for short-term tracking, for example to monitor changes to critical fields.
44. Purge processed reports on a monthly basis: System Administration > Performance Tuning > Purge Programs > Set Program to Processed Reports.
6. Recommended File Cleanup (Optional) 45. Rebuild items on order records using the "rebldonord" support program for all branches: Select System Administration > Restricted Processing > Support Programs.
46. Remove orphaned backorder and commit records using the "dlorphbocm" support program for all branches. When running this program, select the option for Audit Report and Update: Select System Administration > Restricted Processing > Support Programs.
47. Update item quantity total records using the "updqtyttls" support program for all branches: Select System Administration > Restricted Processing > Support Programs.
48. If you use the Automated Processing feature, remove Queue History records using the Purge Programs window. DMSi recommends retaining 2 weeks of Queue History records System Administration > Performance Tuning > Purge Programs > Select Queue History in the Purge Selection field.
7. Periodic Maintenance DMSi recommends running the following tasks periodically. You can run these tasks any time during the month. When running the tasks, ensure all users are off the system.
49. Rebuild cost maps: Select System Administration > Performance Tuning > Rebuild Maps. Rebuild cost maps if you use supplier, supplier group, or default cost. If you use purchase order costs instead of cost records, rebuilding the cost map is unnecessary.
50. Recalibrate scroll bars: Select System Administration > Performance Tuning > Recalibrate Scroll Bars.
* Recommendation: Set all default posting options to Direct Post to keep the General Ledger up to date with real time data and allow for timely balancing with subsidiary ledgers.
** Complete this step after entering month end adjusting entries.
AR19343 - How to Update Product Groups and Historical Records
Agility
- Inventory
How to Update Product Groups & Historical Records The following procedures should be processed during non-business hours.
Method 1: Item Maintenance Best when updating product groups for fewer than 10-15 items.
In Agility, access Data Files > Item Information > Items Using the search box or the Item Locator, find an item that you wish to update On the Item tab, you can either use the Product Group Locator or type in the product group major and minorIf the product group major and/or minor has not been created yet, you can create these from the Product Group Maintenance screen by accessing Data Files > Item Information > Product Groups Save the item recordUpon saving, Agility will give the following question: Click Yes to update the item’s product group and rebuild the costing structure for the item Click No if you do not want to update the item’s product group Repeat steps 1 through 4 for each item If you use the product group for item keywords, these will be updated automatically. Any forms including reprinted forms that list the item’s product group will be updated immediately upon saving. To update the historical information for viewers and reports, refer to the last section of this document.
Best when updating ALL items assigned to a single product group major/minor to another product group major/minor . May also delete the old product group.
Access System Administration > Mass Updates > Renumber Processing > Reassign Prod Grp/Price Cd Leave the Reassign By field as Product Group Use the Product Group Locator or type in the old major and old minor Use the Product Group Locator or type in the new major and new minorYou may create a new product group major/minor by typing it into these fieldsIf you do, it will not have a description, but can be edited later in product group maintenance If you want to delete the old product group major/minor, then check the Remove Old Product Group flagThis will remove the product group major/minor. If the major has other existing minors, then only the minor will be deleted. If the major has no other minors, then the major will also be deleted. Click Process Upon processing, Agility will give the following question: Rebuilding cost maps is necessary if you use costing records based on product groups. If processing multiple product group reassignments during the same session, only rebuild cost maps after the last process. Click Yes to rebuild the cost maps for ALL items Click No if you do not want to rebuild cost mapsYou can rebuild cost maps afterward by accessing System Administration > Performance Tuning > Rebuild Maps If you use the product group for item keywords, these will NOT be updated automatically. You can manually update the item keywords by running the support program rblditmkywd by accessing System Administration > Restricted Processing > Support Programs.
It is recommended that you close all Agility windows except the main window before you Run support programs. Verify that you have selected the correct support program before running as many programs should be run only under special conditions.
Search and select the support program rblditmkywd Click Run Click Yes when prompted to perform the selected support program Enter in the new Major Product Group and Minor Product Group Click Update Any forms including reprinted forms that list the item’s product group will be updated immediately upon processing. To update the historical information for viewers and reports, refer to the last section of this document.
Method 3: Item Mass Update Best when updating product groups for more than 10-15 items that have a common criterion to a single product group major/minor. This criterion includes an item range, product group range, buyer range, primary item supplier, or ABC range.
In Agility, access System Administration > Mass Updates > Item Mass Update Leave the Mass Update Action drop-down as Update Item Record Fields Select your Item Criteria Select Product Group from the Field Name drop-down Click the Alpha Value locator and select the new product group major/minor Click Process to update the product group major/minor After processing, the system will advise you to rebuild cost maps. Rebuilding cost maps is necessary if you use costing records based on product groups. Access System Administration > Performance Tuning > Rebuild Maps. Click Process to rebuild all costing records in all branches. Make sure to run this during non-business hours as this will rebuild ALL costing records on the system.
If you use the product group for item keywords, these will be updated automatically. Any forms including reprinted forms that list the item’s product group will be updated immediately upon processing. To update the historical information for viewers and reports, refer to the last section of this document.
Method 4: Item Import Best when updating product groups for more than 10-15 items from one or more product group major/minors to two or more product group major/minors.
In Agility, access Data Files > Item Information > Item Import Click on one of the icons at the top to create a new import definition record, select an existing record to update, or create a new default layout if using the exported default layout Update the import definition so all fields on the Action tab are set correctly and fields are mapped correctly on the Item tabThe minimum required fields for this process are the item code, product group major, and product group minor The new product groups must already exist in the system Save the record Close the Item Import Definition Maintenance window If you do not share item records between branches, make sure the processing branch is correct Click Process and check the audit report for errors It is recommended that you Process in your Test database first to validate your data and Process in your Production during non-business hours.
After processing, it is recommended that you rebuild your cost maps if you use costing records based on product groups. Access System Administration > Performance Tuning > Rebuild Maps. Click Process to rebuild all costing records in all branches. Make sure to run this during non-business hours.
If you use the product group for item keywords, these will be updated automatically. Any forms including reprinted forms that list the item’s product group will be updated immediately upon processing. To update the historical information for viewers and reports, refer to the next section of this document.
Update History for Viewers and Reports After updating an item’s product group, the data displayed on most reports and viewers will be updated immediately with the new (current) item’s product group. The exception includes ALL data warehouse reports (sales analysis, inventory valuation by date, inventory turns/GMROI) which will display the items’ product groups at the time of the activity/transaction. These reports can be updated by running support program dwsync (System Administration > Restricted Processing > Support Programs).
It is recommended that you close all Agility windows except the main window before you Run support programs. Verify that you have selected the correct support program before running as many programs should be run only under special conditions.
Search and select the support program dwsync Click Run Click Yes when prompted to perform the selected support program Select your processing branch Select your Date range or check ALL to update all historical records Select your Item Range by item code, product group major, and/or product group minorWhen using product group, enter the NEW product groups Recommend NOT processing this for ALL items and ALL product groups Click Process to update This process updates the product groups in the SALES_FACT table (used for data warehouse reports) with the product groups on the ITEM table. After you run the dwsync support program AND after your data warehouse update, these reports will reflect the new items' product groups for historical records based on the date range specified.
To update BInformed reports, create a case on The Wedge to request for a Prior Reload with a Master Reload to update the historical records with the NEW product groups over the last 3 years. Make sure you request this after you run the dwsync support program AND after your data warehouse update as BI reports use Data Warehouse information.
If your saved viewers and reports in Agility use specific product groups as a criterion, these may need to be manually reviewed and updated. The only criterion that DOES update is the product group for ALL viewers if you used Method 2 (Reassign Prod Grp/Price Cd). All other processes DO NOT update the criteria on saved viewers and reports.
AR19378 - How to set up GL Recon in Agility
Agility
- General Ledger
How to set up GL Recon in Agility Agility includes a recommended way to reconcile the general ledger to the various subledgers (or subsidiary balances) in Agility called G/L Recon. The G/L Recon process provides a way to map G/L accounts to their corresponding subledgers so that the balancing can be easily reviewed in a single report and even automated.
Chart of accounts/account maintenance setup To begin using the new G/L Reconciliation process, some setup within Accounts Maintenance is necessary. Fields have been added to Accounts Maintenance that will be used to map the G/L account to its corresponding subledger so that the G/L Recon Report can accurately compare account balances to the appropriate subledgers .
In Agility, navigate to General Ledger > Chart of Accounts > Accounts Maintenance. Alternatively, you can also use the G/L Import (by clicking in the Accounts Maintenance window) to assign the following G/L Recon fields. Assign a Recon category to G/L accounts that will be used to compare to subledger balances for that category. For example, an accounts receivable account should be assigned a Recon category of A/R Trade . The recon category of Zero balance clearing account should be assigned to accounts that should always carry a $0 balance, like an invalid posting account. These will be considered out of balance if they carry a balance other than $0. Click on the Recon info button. Assign the branch (or branches) that the G/L account will be used in as the Recon branch . This should be any branch that posts activity to this G/L account. If a certain variance level is acceptable, you can assign an amount as the Tolerable variance so that any variance under that amount will not be considered out of balance. For example, if Inventory being off by $0.10 or less is not a concern (since rounding may cause penny variances here and there), then set the Tolerable variance to 0.10 for the inventory G/L account. If this is the first year using Agility and known variances for certain accounts are being carried forward from the legacy system to Agility, you can enter that amount as the Initial Variance and assign the fiscal year that variance Applies to . For example, if going live on Agility in the middle of 2019 and a known variance in sales of $800,000 is being carried over, enter 800,000 for the Initial variance and enter 2019 for Applies to. Running the G/L Recon Update In order to collect the G/L account balances and subledger balances to be compared and saved for historical purposes, the G/L Recon Update should be run daily after all work in Agility is done for the day. Therefore, it should be setup in Automated Processing to run overnight so that the final balances for the day can be captured.
In Agility, navigate to General Ledger > G/L Recon > G/L Recon Update. Set the Branch (or branches) for which G/L and subledger data should be collected. If planning to capture balances for all branches, set the Branch to <All> . Agility will store subledger balances for each branch, separately. The Post date is the date to be date-stamped on the collected records. Data should be captured after business has closed for the day. Therefore, if this process runs after midnight to capture the previous day’s balances, set a relative date of -1 . For the Update options , select which categories you want to collect the G/L and subledger balances for. The G/L category will collect the balances of all G/L accounts with a Recon category assigned. All other categories, when run, will collect the subledger balances of their respective category. For example, contract billing is not commonly used. Therefore, if not using, unset the Contract billing category in order to improve processing performance. Save each set of criteria using Save Criteria. Add the G/L Reconciliation Update process in Automated Processing. Schedule it to process on a nightly basis. If not all branches share G/L data, separate automated processes should be set up (using the appropriate processing branch) to accurately capture the balances since the update respects G/L sharing. Running the G/L Recon Report The G/L Recon Report will be used to review the comparison of the G/L account balances to their appropriate subledger balances and any variances. Ideally, the Report should be run on a daily basis. Therefore, it should be setup in Automated Processing to run overnight (in addition to the G/L Recon Update).
In Agility, navigate to General Ledger > G/L Recon > G/L Recon Report. Select which Branch (or branches) and the Activity date the report should be run for. When scheduling this report to run in Automated Processing on a nightly basis, you should set the relative date to +0 . As long as the G/L Recon Update is processed on a daily basis, this report can be run for dates in the past if needing to review historical daily balances. Select which categories to display in the report output under Recon categories to include . All categories are selected by default, but if certain categories are not reviewed by your business, they can be unchecked. The report option of Only include categories that are out of balance , if checked, will display only the categories that show a variance (above the tolerable variance threshold, if one is specified). If using automated processing to run this report daily, check this setting if you only want to be emailed the report if there is a category out of balance. Otherwise, if all categories are in balance, the report will be blank and no report will be emailed via automated processing. The report offers options to Print G/L account description , initial variance , and tolerable variance columns, as well as other formatting options. Save each set of criteria using Save Criteria. Run the report and review.a. The report will be sorted by category. The G/L account balances will display on the left and the corresponding subledger balances will display on the right.b. If run for multiple branches, the report will subtotal by branch (or branch groupings, depending on account setup) within each category.c. If Only include categories that are out of balance is unchecked, any variance that is not $0 (and exceeds the tolerable variance for an account) will be highlighted yellow.d. The variance is calculated as follows, using the subtotal balance from each column: G/L balance + Initial variance – Subledger balance – Charges/Costs GM – Charges/Costs no GM = Variancee . If multiple accounts are used for a category and all pointed to the same Recon branch, the subtotal of these accounts will be compared to the corresponding branch’s subledger balance. For example, multiple sales accounts may be used in one branch. Therefore, the subtotal of the G/L account balances will be compared to the sales subledger of that branch. See the Sales category in the report example below.f. Conversely, if one G/L account is used by multiple branches, the balance of that G/L account will be compared to the subtotal of the branches’ subledger balances. See the A/R trade category in the report example below. Add the G/L Reconciliation Report in Automated Processing. This should be done on a nightly basis and scheduled to run after the G/L Recon Update. Again, if not all branches share G/L data, you will need to set up separate automated processes (using the appropriate processing branch) to accurately report the data since the report respects G/L sharing.
AR19533 - Cyberquery (CQ) sample: PV Guest User Listing Report
Agility
- Cyberquery Samples
This report can be run to see the customers that have PV guest user logins and the last day the user logged in. The prompts built into the report will allow those running the report to narrow it down to a particular customer, customer ship-to, sales agent 1, or any combination of the three. The report can be modified to exclude some or all of these prompts.
viewpoint native; define string xcust_id = parameter prompt "ENTER CUSTOMER ID" default "ALL";
number xcust_seq = parameter prompt "ENTER SEQUENCE #" default 0;
string xsa = parameter prompt "ENTER SALES AGENT ID" default "ALL"; file xcust_shipto = access cust_shipto, set cust_shipto:system_id = user_ctl:default_cust_key_sysid, cust_shipto:cust_key = user_ctl:default_cust_key, cust_shipto:cust_key_sysid = user_ctl:default_cust_key_sysid, cust_shipto:seq_num = user_ctl:default_shipto_seq_num; file xgsm_user = access gsm_user, set gsm_user:user_obj = user_ctl:user_obj; where user_ctl:default_cust_key <> "" and ( xcust_seq = xcust_shipto:seq_num or xcust_seq = 0 ) and ( xcust_id = xcust_shipto:cust_code or xcust_id = "ALL" ) and ( xsa begins with xcust_shipto:sales_agent_1 or xsa begins with "ALL" ) list/domain="user_ctl"/duplicates xcust_shipto:sales_agent_1/heading="OUTSIDE SALES REP" xcust_shipto:shipto_name/heading="CUSTOMER NAME" xcust_shipto:seq_num/heading="SHIP TO SEQ" user_ctl:user_or_group_id/heading="USER ID" user_ctl:user_name/heading="USERNAME" xgsm_user:last_login_date/heading = "LOGIN DATE" user_ctl:default_branch/heading="DEFAULT BRANCH" user_ctl:email_address/heading="EMAIL ADDRESS" user_ctl:created_date/heading="CREATED" user_ctl:update_date/heading="UPDATED" sorted by xcust_shipto:sales_agent_1 user_ctl:default_cust_key
AR19542 - PartnerView Public user for Catalog Configuration
Agility
- PartnerView
PartnerView Public user for Catalog Configuration Specific setup is required for the catalog user to work correctly in the PV Web Config file.
If the output is from Agility, IE viewer or report, it processes through the Email Server. You will go to System Administration > Module Controls > Branch Parameters and Test the Mail Server. If you get those emails fine, you can work with Tech to see if the output email specifically hit the email server. PartnerView v4.5.4 introduces Catalog Search. The new functionality requires the creation and security administration of a public Guest user in Agility for the PrtnrView product to be used as the public user.
When utilizing the new Catalog Search functionality, PartnerView starts a session using the credentials of the Agility public Guest user you configure to retrieve inventory item information and pricing. This retrieval happens before the PartnerView user logs in with their personal login credential which then sets their Agility branch, customer and ship-to defaults accordingly.
Because the public user credentials are stored in the web configuration for PartnerView, once the user has been created AND you are ready to use the new functionality, a request to DMSi’s tech support team will need to be made that includes the user name and password of the public user as well as a confirmation that you wish to begin to use the new functionality. Please be sure to include whether you would like this turned on in your test environment, production environment or both. If you wish to see the functionality in your test environment, a separate request can be sent in to update production when you are ready.
Following are suggested guidelines for the creation and security setup of the public Guest user.
The following is an example setup for the guest user. Permissions granted may vary based on desired settings for prices, available qty and on order qty. Permissions denied should be entered this way for the generic user.
AR19683 - Accounting Best Practices - Balancing
Agility
- General Ledger
Accounting Best Practices - Balancing Agility Help Doc - Checklists Agility Help has checklists available when researching an out of balance occurrence. In Help, search for “Balancing”. Balancing checklists will take you step-by-step through researching possible causes of an out of balance occurrence.
Articles - Out of Balance Troubleshooting The Wedge has Out of Balance Troubleshooting Articles available when researching an out of balance occurrence. In The Wedge, under Articles, search for “OOB”.
The Out of Balance Troubleshooting Articles will take you step-by-step through researching possible causes of an out of balance occurrence.
Links to Balancing Checklists & Troubleshooting Articles Accounts Receivable
HELP DOC - CHECKLIST
ARTICLE - TROUBLESHOOTING
Accounts Payable
HELP DOC - CHECKLIST
ARTICLE - TROUBLESHOOTING
A/P Reconciliation
HELP DOC - CHECKLIST
ARTICLE - TROUBLESHOOTING
Inventory
HELP DOC - CHECKLIST
ARTICLE - TROUBLESHOOTING
Sales
HELP DOC - CHECKLIST
ARTICLE - TROUBLESHOOTING
COGS
HELP DOC - CHECKLIST
ARTICLE - TROUBLESHOOTING
Common Causes of Out of Balance situations - Timing
- Journal Entries
- Backdating/Posting
- Unposted Entries
Tips to help find differences G/L Detail Inquiry Use origin, source, dates, and wildcards to define specific data and then compare to subsidiary reports. Specific accounts should only have postings from specific sources. This list provides the source and the report/viewer they should balance to.A/R TradeA/R Fin --> A/R Open items inquiry – run by type A/R GL --> A/R GL detail report A/R Inv --> A/R Detailed Sales – by created date A/R Recp --> Cash Reconciliation report A/R Void --> Cash Reconciliation report A/R WO --> Cash Reconciliation report A/P TradeA/P Edit --- A/P Inv --- A/P Pmnt --- A/P Audit A/P Void --- Inventory – Item Activity Viewer (set for activity that affects Inventory) A/P Recon – AP Recon Register by Activity Date (All Activity)P/O Recv --- RM --------- Recv/RM Amt Column SO --------- CM --- CM/SR Column SR --- A/P Inv ------- A/P Void ------ AP Amt Column A/P Edit ------ Drop A/P Recon ----- Adj Column Adjust A/P Recon --- G/L Transaction Inquiry Detail on transactional posting, including item information G/L Balancing Reports IA G/L Balancing report Inventory balance comparison Inventory level comparison Non-standard postings
AR19923 - Cyberquery (CQ) sample: Item Export
Agility
- Cyberquery Samples
-- This report will list all Items in the system. It is formatted to match the Item Import for v546 define string zbranch = parameter/uppercase prompt "Enter Branch for Branch specific Info" string zStockToPc = if item:stock_to_pc_calc = "((Qty/2.35849)*1000)/((TxWxL)/12)" then "((Qty/2.35849)*1000)/((TxWxL)/12) (i.e. M3)" else if item:stock_to_pc_calc = "(Qty*1000)/(((Thickness-1/16)x(Width+1/8)xLength)/12)" then "(Qty*1000)/(((Thickness-1/16)x(Width+1/8)xLength)/12) (i.e. MBFW)" else if item:stock_to_pc_calc = "(Qty*1000)/(TxWxL/12)" then "(Qty*1000)/(TxWxL/12) (i.e. MBF)" else if item:stock_to_pc_calc = "(Qty/2.35849)*1000/((Thickness-1/16)x(Width+1/8)xLength)/12)" then "(Qty/2.35849)*1000/((Thickness-1/16)x(Width+1/8)xLength)/12) (i.e. M3W)" else if item:stock_to_pc_calc = "Qty" then "Qty (i.e. PC)" else if item:stock_to_pc_calc = "Qty/((WxL)/12)" then "Qty/((WxL)/12) (i.e. SM)" else if item:stock_to_pc_calc = "Qty/(LxW)" then "Qty/(LxW) (i.e SF)" else if item:stock_to_pc_calc = "Qty/(TxWxL/12)" then "Qty/(TxWxL/12) (i.e. BF)" else if item:stock_to_pc_calc = "Qty/Length" then "Qty/Length (i.e. LF)" string zCostCarried = if item_branch:cost_code = 1 then "Branch" else if item_branch:cost_code = 2 then "Location" else if item_branch:cost_code = 3 then "Lot" else if item_branch:cost_code = 4 then "Tag" else if item_branch:cost_code = 5 then "Content" else if item_branch:cost_code = 6 then "Dimension" string zPringGroupType = if item:print_group_type = 1 then "Qty" else if item:print_group_type = 2 then "Weight" else if item:print_group_type = 3 then "Load" file xBOM_RTS_Item = access item, set system_id = item:system_id, set item_ptr = item:bom_rts_item_ptr file xTaxCategory = access tax_category, set tax_category_guid = item:tax_category_guid file xItemSupplier = access item_supplier, set item_ptr = item:item_ptr, set item_ptr_sysid = item:system_id, set primary = 1 , set thickness = item_content_def_branch:thickness, set width = item_content_def_branch:width, set item_supplier:length = item_content_def_branch:length, set system_id = item_content_def_branch:system_id file xItemXref = access item_xref, set system_id = item:system_id, set type = "Supplier" , set supplier_key_sysid = xItemSupplier:system_id, set supplier_key = xItemSupplier:supplier_key, set ship_from_seq_num = xItemsupplier:ship_from_seq_num, set item_ptr_sysid = item:system_id, set item_ptr = item:item_ptr, set thickness = item_content_def_branch:thickness, set width = item_content_def_branch:width, set item_xref:length = item_content_def_branch:length where item_content_def_branch:system_id = zbranch and item:item one of "item1" , "item2" , "item3" --paste list of items here list /nobanner/duplicates/domain="item_content_def_branch" /* Item */ item_content_def_branch:item/heading = "ItemVal - Item - ITEM - - A(16)" item:size/heading = "SizeVal - Size - SIZE - - A(16)" item:description/heading = "ItemDescVal - Description - DESCRIPTION - - A(40)" item:pg_major/heading = "PrdGrpMajorVal - Product Group Major - PRODUCT_GROUP_MAJOR - - A(4)" item:pg_minor/heading = "PrdGrpMinorVal - Product Group Minor - PRODUCT_GROUP_MINOR - - A(6)" item:price_code_major/heading = "PriceGrpMajorVal - Price Code Major - PRICE_CODE_MAJOR - - A(4)" item:price_code_minor/heading = "PriceGrpMinorVal - Price Code Minor - PRICE_CODE_MINOR - - A(6)" item:stocking_uom/heading = "StockUOMVal - Stocking UOM - STOCKING_UOM - - A(4)" item:costing_uom/heading = "CostUOMVal - Costing UOM - COSTING_UOM - Stocking UOM - A(4)" item:default_uom_conv_factor/nocommas/decimalplaces=10 /heading = "StkCostFctrVal - UOM Conversion: 'X' Stocking = 1 Costing - STOCK_TO_COSTING_CONV_FCTR - 1 - N(5.10)" item:ext_description/heading = "ExtDescVal - Ext Desc - EXT_DESCRIPTION - - A(500)" --item:ecommerce_description/heading = "EcommerceDescVal - Ecommerce Description - ECOMMERCE_DESCRIPTION - - A(30000)" if item:use_short_desc_wo_phrase = 1 then "YES" else "NO" /heading = "UseShortDescWOPhraseVal - Use Short Desc in WO Phrase - USE_SHORT_DESC_WO_PHRASE - YES - YES/NO" item:short_des/heading = "ShortDescVal - Short Desc - SHORT_DES - - A(25)" item:wo_long_short/heading = "BOMPrtFlgWOVal - BOM Print Flags/Settings:Work Order - WO_LONG_SHORT - Blank - A(1)" item:long_short/heading = "BOMPrtFlgOtherVal - BOM Print Flags/Settings:Other Forms - LONG_SHORT - Blank - A(1)" if item:bom_filter_item = 1 then "YES" else "NO" /heading = "PBOMFilterVal - BOM Print Flags/Settings: BOM Filter Item - BOM_FILTER_ITEM - NO - YES/NO" if item:bom_use_price_cost = 1 then "YES" else "NO" /heading = "PriceCostBomCompVal - BOM Print Flags Settings:Price/Cost BOM Component - BOM_USE_PRICE_COST - YES - YES/NO" if item:bom_neg_price_cost = 1 then "YES" else "NO" /heading = "NegPriceCostBomCompVal - BOM Print Flags/Settings:Deduct from Rolled Up Price/Cost - BOM_NEG_PRICE_COST - NO - YES/NO" item:website/heading = "WebsiteVal - Website - WEBSITE - - A(200)" if item:price_prompt = 1 then "YES" else "NO" /heading = "PBOMFlgPromptVal - Parent BOM Flags:Prompt when Price Overridden - PRICE_PROMPT - YES - YES/NO" if item:price_prompt_default = 1 then "YES" else "NO" /heading = "PBOMFlgOptionsVal - Parent BOM Flags:Options Included in Price Default - PRICE_PROMPT_DEFAULT - NO - YES/NO" if item:auto_complete_wo = 1 then "YES" else "NO" /heading = "AutoCompleteWOVal - Parent BOM Flags:Auto Complete WO - AUTO_COMPLETE_WO - NO - YES/NO" if item:wo_type = "SO" then "Sales Order" else if item:wo_type="RM" then "Reman" /heading = "WOTypeVal - Work Order Type - WO_TYPE - Sales Order - A(2)" if item:wo_create_reman = 0 then "NO" else if item:wo_create_reman = 1 then "YES" /heading = "WOCreateRemanVal - Work Order Type: Create Reman - WO_CREATE_REMAN - NO - YES/NO" item:reman_type/heading = "RemanTypeVal - Work Order Type:Reman Type - REMAN_TYPE - - A(8)" if item:cafe = 1 then "YES" else "NO" /heading = "CafeVal - Work Order Type:CAFE - CAFE - NO - YES/NO" if item_branch:prompt_for_bom_xref = 1 then "YES" else "NO" /heading = "PromptForBomXrefVal - Work Order Type:Prompt for Cross Reference - PROMPT_FOR_BOM_XREF - NO -YES/NO" item:type/heading = "ItemTypeVal - Item Type:Type - TYPE - - A(30)" item:piece_ref/heading = "PCRefVal - Item Type:Piece Reference - PIECE_REF - - A(2)" zStockToPc/heading = "StcktoPCCalcVal - Item Type:Stock to PC Calc - STOCK_TO_PC_CALC - Qty/(TxWxL/12) - A(75)" item_content_def_branch:thickness/heading = "ThicknessVal - Item Type:Thickness - THICKNESS - 0 - N(4.4)" item:thickness_uom/heading = "ThicknessUOMVal - Item Type:Thickness UOM - THICKNESS_UOM - Inches - A(16)" item_content_def_branch:width/heading = "WidthVal - Item Type:Width - WIDTH - 0 - N(4.4)" item:width_uom/heading = "WidthUOMVal - Item Type:Width UOM - WIDTH_UOM - Inches - A(16)" item_content_def_branch:length/heading = "LengthVal - Item Type:Length - LENGTH - 0 - N(4.4)" item:length_uom/heading = "LengthUOMVal - Item Type:Length UOM - LENGTH_UOM - Feet - A(16)" item:tally_uom/heading = "TallyUOMVal - Item Type:Tally Calculator UOM - TALLY_UOM - - A(4)" if item:print_sundry = 1 then "YES" else "NO" /heading = "SundryPrintSell0Val - Item Type:Print on Forms if Sell = 0 - PRINT_SUNDRY - YES - YES/NO" /* Misc Branch */ item_branch:display_uom/heading = "DisplayUOMVal - Display UOM - DISPLAY_UOM - - A(4)" item_branch:default_uom_so_qu/heading = "SOQTUOMVal - SO/Quote UOM - DEFAULT_UOM_SO_QU - Stocking UOM - A(4)" item_branch:default_uom_cm/heading = "CMUOMVal - CM UOM - DEFAULT_UOM_CM - Stocking UOM - A(4)" item_branch:picking_uom/heading = "PickingUOMVal - Picking UOM - PICKING_UOM - Stocking UOM - A(4)" item_branch:picking_tally_uom/heading = "PickingTallyUOMVal - Picking Tally UOM - PICKING_TALLY_UOM - From Order - A(13)" if item_branch:use_tally_uom_pick = 1 then "YES" else "NO" /heading = "UseTallyforPickVal - Use Tally UOM for Pick Ticket - USE_TALLY_UOM_PICK - YES - YES/NO" item_branch:default_uom_delv/heading = "DelvUOMVal - Delivery UOM - DEFAULT_UOM_DELV - Stocking UOM - A(4)" if item_branch:use_tally_uom_delv = 1 then "YES" else "NO" /heading = "UseTallyforDelvVal - Use Tally UOM for Delivery Ticket - USE_TALLY_UOM_DELV - YES - YES/NO" item_branch:default_uom_invoice/heading = "InvoiceUOMVal - Invoice UOM - DEFAULT_UOM_INVOICE - Stocking UOM - A(4)" if item_branch:use_tally_uom_invoice = 1 then "YES" else "NO" /heading = "UseTallyforInvoiceVal - Use Tally UOM for Invoice - USE_TALLY_UON_INVOICE - YES -YES/NO" item_branch:dw_report_uom/heading = "DWRptUOMVal - DW Reports UOM - DW_REPORT_UOM - Stocking UOM - A(4)" item_branch:dflt_qty_quick_entry/heading = "DefaultQtyVal - Default Qty for Quick Entry - DFLT_QTY_QUICK_ENTRY - 0 - N(9.4)" item_content_def_branch:so_min_pack/heading = "SellMinPakVal - Selling Min Pack - SO_MIN_PACK - 0 - N(5.2)" item_content_def_branch:so_min_pak_disp_uom/heading = "SellMinPakUOMVal - Selling Min Pack UOM - SO_MIN_PAK_DISP_UOM - - A(4)" item_content_def_branch:min_pak_violation/heading = "MinPakViolVal - Min Pack Violation - MIN_PAK_VIOLATION - Allow Question - A(24)" item_branch:handling_code_broken_min_pak/heading = "HandCodeBrokenMinPakVal - Broken Min Pack Handling Code - HANDLING_CODE_BROKEN_MIN_PAK - - A(12)" item_branch:handling_code/heading = "HandCodeVal - Handling Code - HANDLING_CODE - - A(12)" item_branch:weight/heading = "ItemWeightVal - Weight - WEIGHT - - N(6.4)" item_branch:weight_uom/heading = "ItemWeightUOMVal - Weight UOM - WEIGHT_UOM - - A(4)" item_branch:load_factor/heading = "ItemLoadVal - Load - LOAD_FACTOR - - N(6.4)" item_branch:load_uom/heading = "ItemLoadUOMVal - Load UOM - LOAD_UOM - - A(4)" item_branch:default_uom_pi_full/heading = "PICountUOMVal - PI Count UOM - DEFAULT_UOM_PI_FULL - Stocking UOM - A(4)" if item_branch:pi_create_by_dim = 1 then "YES" else "NO" /heading = "PIByDimensionVal - Always Create WorkFile Details by Dimension - PI_CREATE_BY_DIM - NO - YES/NO" if item_branch:use_pi_broken_uom = 1 then "YES" else "NO" /heading = "AllowBrknVal - Allow Broken UOM in Count Entry - USE_PI_BROKEN_UOM - NO - YES/NO" item_branch:default_uom_pi_broken/heading = "PIBrknUOMVal - PI Broken UOM - DEFAULT_UOM_PI_BROKEN - Stocking UOM - A(4)" /* Branch Settings */ item_content_def_branch:location/heading = "LocVal - Default Location - LOCATION - - A(6)" item_content_def_branch:subloc/heading = "SubLocVal - Default Subloc - SUB_LOCATION - - A(6)" item_branch:buyer_id/heading = "BuyerVal - Buyer - BUYER_ID - - A(8)" item_content_def_branch:rl_code/heading = "RandLengthCdVal - Random Length Code - RL_CODE - - A(12)" item_content_def_branch:overall_rank/heading = "OverallABCVal - Overall ABC - OVERALL_ABC - - A(1)" item_branch:hist_start_date/mask="MM/DD/YYYY" /heading = "HistStartDtVal - History Start Date - HISTORY_START_DATE - - D(MM/DD/YYYY)" if item_branch:stock = 1 then "YES" else "NO" /heading = "StockVal - Stock - STOCK - YES - YES/NO" if item_branch:active_flag = 1 then "YES" else "NO" /heading = "ActiveVal - Active - ACTIVE_FLAG - YES - YES/NO" if item_branch:template = 1 then "YES" else "NO" /heading = "TemplateVal - Template - TEMPLATE - NO - YES/NO" if item_branch:prompt_rise_run = 1 then "YES" else "NO" /heading = "PromptRiseRunVal - Prompt for Rise & Run - PROMPT_RISE_RUN - NO - YES/NO" if item_branch:nonsaleable = 1 then "YES" else "NO" /heading = "NonSaleableVal - Non Saleable - NONSALEABLE - NO - YES/NO" if item_branch:allow_in_pv = 1 then "YES" else "NO" /heading = "AllowPartnerVwVal - Allow in PartnerView - ALLOW_IN_PV - NO - YES/NO" if item_branch:allow_in_pv_visual_cafe = 1 then "YES" else "NO" /heading = "AllowPartnerVwVCVal - Allow in Visual CAFE - ALLOW_IN_PV_VISUAL_CAFE - YES - YES/NO" if item_branch:allow_in_mobile_apps = 1 then "YES" else "NO" /heading = "AllowMobAppVal - Allow in Mobile Apps - ALLOW_IN_MOBILE_APPS - NO - YES/NO" if item_branch:allow_in_api = 1 then "YES" else "NO" /heading = "AllowAPIVal - Allow in E Commerce Gateway/API - ALLOW_IN_API - NO - YES/NO" item_branch:auto_tag/heading = "AutoTagSOVal - Auto Tag for SO's - AUTO_TAG - Blank - A(3)" item_branch:parent_po_rule/heading = "ParentPORuleVal - Parent PO Rule - PARENT_PO_RULE - - A(16)" item_branch:auto_tag_rm/heading = "AutoTagRemanVal - Auto Tag for Reman's - AUTO_TAG_RM - Blank - A(3)" item_branch:transfer_shipping_branch/heading = "DfltTransBrnchVal - Default Transfer Branch - TRANSFER_SHIPPING_BRANCH - - A(8)" item_branch:transfer_shipping_branch_comp/heading = "CompTransBrnchVal - - TRANSFER_SHIPPING_BRANCH_COMP - - A(8)" item_branch:cut_category/heading = "CutCatVal - Cut Category - CUT_CATEGORY - - A(16)" item_branch:def_dtl_grp_pricing/heading = "DfltPriceSetVal - Default Price Setting - DEF_DTL_GRP_PRICING - - A(30)" item_branch:dflt_group_id/heading = "DfltGrpIDVal - Default Group ID - DFLT_GROUP_ID - - A(30)" if item_branch:invoice_all_for_group = 1 then "YES" else "NO" /heading = "ReqGrpforInvoiceVal - Require All Items in Group for Invoicing - INVOICE_ALL_FOR_GROUP - NO - YES/NO" /* Reorder Info */ if item_content_def_branch:compute_flag = 1 then "YES" else "NO" /heading = "DoOrderCalcVal - Do Order Calculations/Include in SPO's - COMPUTE_FLAG - YES - YES/NO" item_branch:reorder_info_disp_uom/heading = "ReorderInfoUOMVal - Reorder Info Qty UOM - REORDER_INFO_DISP_UOM - - A(4)" item_branch:reorder_info_dim_disp_uom/heading = "ReorderInfoDimUOMVal - Reorder Info Dimension Qty UOM - REORDER_INFO_DIM_DISP_UOM - - A(4)" item_content_def_branch:order_pt/decimalplaces=2 /heading = "OrderPtVal - Order Point - ORDER_PT - 0 - N(7.2)" item_content_def_branch:eoq/decimalplaces=2 /heading = "EOQVal - EOQ - EOQ - 0 - N(7.2)" if item_content_def_branch:eoq_fix = 1 then "YES" else "NO" /heading = "EOQFixVal - EOQ Fix (box) - EOQ_FIX - NO - YES/NO" item_content_def_branch:saf_stk/decimalplaces=2 /heading = "SafetyStkVal - Safety Stock - SAF_STK - 0 - N(7.2)" if item_content_def_branch:saf_stk_fix = 1 then "YES" else "NO" /heading = "SafetyStkFixVal - Safety Stock Fix (box) - SAF_STK_FIX - NO - YES/NO" item_content_def_branch:ropcalc_method/heading = "ROPCalcMethVal - ROP Calc Method - ROPCALC_METHOD - - A(4)" if item_content_def_branch:ropcalc_fix = 1 then "YES" else "NO" /heading = "ROPCalcMethFixVal - ROP Calc Method Fix (box) - ROPCALC_FIX - NO - YES/NO" item_content_def_branch:min_reord_pt/decimalplaces=2 /heading = "MinReorderPtVal - Minimum Reorder Point - MIN_REORD_PT - 0 - N(5.2)" item_content_def_branch:deliv_delay_factor/decimalplaces=2 /heading = "DelDelayFactVal - Delivery Delay Factor - DELIV_DELAY_FACTOR - 0 - N(5.2)" /* Inv Param */ if item_branch:lotcode = 1 then "YES" else "NO" /heading = "QtyCarLotVal - Quantity Carried:Lot - LOTCODE - NO - YES/NO" if item_branch:tagcode = 1 then "YES" else "NO" /heading = "QtyCarTagVal - Quantity Carried:Tag - TAGCODE - NO - YES/NO" if item_branch:contentcode = 1 then "YES" else "NO" /heading = "QtyCarContentVal - Quantity Carried:Content - CONTENTCODE - NO - YES/NO" item_branch:track_whqty_lot_tag/heading = "LotandTagTrackingVal - Lot and Tag Tracking - TRACK_WHQTY_LOT_TAG - Track Qty in Warehouse - A(32)" zCostCarried/heading = "CostCarriedVal - Cost Carried - COST_CODE - Branch - *****" item_branch:consign_contract/heading = "ConsignmentInvVal - Consignment Inventory - CONSIGN_CONTRACT - Blank - A(1)" item_branch:cost_desig/heading = "CostSettingVal - Cost Setting - COST_DESIG - A - A(1)" if item_branch:standard_cost = 1 then "YES" else "NO" /heading = "InvStdCostVal - Standard Cost:Standard Cost Item - STANDARD_COST - NO - YES/NO" if item_branch:upd_inv_std_cost_chg = 1 then "YES" else "NO" /heading = "UpdInvStdCostVal - Standard Cost:Update Inv w/Std Cost Chg - UPD_INV_STD_COST_CHG - YES - YES/NO" if item_branch:dw_detail_level_loc = 1 then "YES" else "NO" /heading = "DWSaleLocVal - DW Sales Level:Location - DW_DETAIL_LEVEL_LOC - NO - YES/NO" if item_branch:dw_detail_level_lot = 1 then "YES" else "NO" /heading = "DWSaleLotVal - DW Sales Level:Lot - DW_DETAIL_LEVEL_LOT - NO - YES/NO" if item_branch:dw_detail_level_twl = 1 then "YES" else "NO" /heading = "DWSaleDimVal - DW Sales Level:Dimension (T/W/L) - DW_DETAIL_LEVEL_TWL - NO - YES/NO" if item_branch:dw_detail_level_piece_cnt = 1 then "YES" else "NO" /heading = "DWSalePCVal - DW Sales Level:Piece Cnt - DW_DETAIL_LEVEL_PIECE_CNT - NO - YES/NO" if item_branch:dw_inv_level_loc = 1 then "YES" else "NO" /heading = "DWInvLocVal - DW Inventory Level:Location - DW_INV_LEVEL_LOC - NO - YES/NO" if item_branch:dw_inv_level_lot = 1 then "YES" else "NO" /heading = "DWInvLotVal - DW Inventory Level:Lot - DW_INV_LEVEL_LOT - NO - YES/NO" if item_branch:dw_inv_level_twl = 1 then "YES" else "NO" /heading = "DWInvDimVal - DW Inventory Level:Dimension (T/W/L) - DW_INV_LEVEL_TWL - NO -YES/NO" if item_branch:dw_inv_level_piece_count = 1 then "YES" else "NO" /heading = "DWInvPCVal - DW Inventory Level:Piece Cnt - DW_INV_LEVEL_PIECE_COUNT - NO -YES/NO" item_branch:copy_itmsup_option/heading = "ItemSupCopyOptVal - Item Supplier Copy Defaults:Copy Option - COPY_ITEMSUP_OPTION - Prompt with Defaults - A(30)" if item_branch:copy_itmsup_itm_ref = 1 then "YES" else "NO" /heading = "ItemSupItemRefVal - Item Supplier Copy Defaults:Item Reference - COPY_ITMSUP_ITM_REF - NO - YES/NO" if item_branch:copy_itmsup_weight = 1 then "YES" else "NO" /heading = "ItemSupWghtVal - Item Supplier Copy Defaults:Weight - COPY_ITMSUP_WEIGHT - YES - YES/NO" if item_branch:copy_itmsup_load = 1 then "YES" else "NO" /heading = "ItemSupLoadVal - Item Supplier Copy Defaults:Load - COPY_ITMSUP_LOAD - YES - YES/NO" if item_branch:copy_itmsup_uom = 1 then "YES" else "NO" /heading = "ItemSupUOMVal - Item Supplier Copy Defaults:Supplier UOM - COPY_ITMSUP_UOM - NO - YES/NO" if item_branch:copy_itmsup_min = 1 then "YES" else "NO" /heading = "ItemSupPOMinVal - Item Supplier Copy Defaults:PO Minimums - COPY_ITMSUP_MIN - YES - YES/NO" if item_branch:copy_itmsup_leads = 1 then "YES" else "NO" /heading = "ItemSupLdTimeVal - Item Supplier Copy Defaults:Lead Times - COPY_ITMSUP_LEADS - NO - YES/NO" if item_branch:copy_itmsup_lot = 1 then "YES" else "NO" /heading = "ItemSupRcvDefLotVal - Item Supplier Copy Defaults:Recv Default Lot - COPY_ITMSUP_LOT - NO - YES/NO" if item_branch:copy_itmsup_content = 1 then "YES" else "NO" /heading = "ItemSupRcvDefContVal - Item Supplier Copy Defaults:Recv Default Content - COPY_ITMSUP_CONTENT - NO - YES/NO" /* Misc Param */ if item_branch:auto_delete_tally = 1 then "YES" else "NO" /heading = "AutoDelZeroInvRcdVal - Misc:Auto Delete Zero Balance Inventory Records - AUTO_DELETE_TALLY - NO - YES/NO" if item_branch:adj_req_so_from_ship_so = 1 then "YES" else "NO" /heading = "AdjCustOrderFromShipSOVal - Misc:Adj Cust Order from Shipping SO for SHip to Branch Transfers - ADJ_REQ_SO_FROM_SHIP_SO - NO - YES/NO" if item_branch:transfer_affect_usage = 1 then "YES" else "NO" /heading = "AffectUsageTrnsfSOVal - Misc:Always Affect Usage History for Transfer SO'S - TRANSFER_AFFECT_USAGE - NO - YES/NO" if item_branch:reman_affect_usage = 1 then "YES" else "NO" /heading = "AffectUsageRemanVal - Misc:Affect Usage History for Reman - REMAN_AFFECT_USAGE - YES - YES/NO" if item_branch:convert_price_and_uom = 1 then "YES" else "NO" /heading = "ConvertPriceVal - Misc:Convert Price/Price UOM to Match Order - CONVERT_PRICE_AND_UOM - NO - YES/NO" if item_branch:warn_zero_po_cost = 1 then "YES" else "NO" /heading = "WarnZeroCostVal - Misc:Warn if Zero Cost in PO/SR Entry - WARN_ZERO_PO_COST - YES - YES/NO" if item_branch:use_fractional_dim = 1 then "YES" else "NO" /heading = "UseFractionalDim - Misc:Maintain Dimensions in Fractions - USE_FRACTIONAL_DIM - NO - YES/NO" if item_branch:store_actual_dim = 1 then "YES" else "NO" /heading = "StoreActDimVal - Misc:Store Actual Dimensions - STORE_ACTUAL_DIM - NO - YES/NO" item_branch:new_tally_percent_incr/decimalplaces=2 /heading = "NewTallyPercIncrVal - Misc:New Tally Percent Increase - NEW_TALLY_PERCENT_INCR - 0 - N(2.2)" item_branch:print_locations/heading = "PrintLocAvailQtyVal - Print Locations w/ Avail Qty - PRINT_LOCATIONS - Do Not Print - A(32)" item_branch:inv_tag_type/heading = "InvTagTypeVal - Misc:Inv Tag Type - INV_TAG_TYPE - Single Unit, PC Count and Length - A(46)" if item_branch:pass_thru_flag = "Allow Pass-thru" then "Allow item to be used as a pass-thru" else if item_branch:pass_thru_flag = "Don't allow Pass-thru" then "Do not allow item to be used as a pass-thru" else if item_branch:pass_thru_flag = "Pass-thru Alternate" then "Pass-thru alternate" /heading = "PassThruRuleVal - Misc:Pass thru Rule - PASS_THRU_FLAG - Allow Item to be Used as a Pass thru - A(25)" item_branch:remain_qty_after_cmt/heading = "RemainQtyAfterCmtVal - Misc:Remaining Qty AFter Tag Commits - REMAIN_QTY_AFTER_CMT - YES - A(5)" item_branch:remaining_percent/decimalplaces=2 /heading = "RemainingPercentVal - Misc:Remaining Qty After Tag Commits Remaining Percent - REMAINING_PERCENT - 0 - N(3.2)" item:lifo_level/heading = "LifoLevelVal - Misc:LIFO Level - LIFO_LEVEL - Item - A(9)" item_branch:dflt_so_dim/heading = "DfltSODim - Default for New Dimensions:SO Dimension - DFLT_SO_DIM - Stock - A(15)" item_branch:dflt_po_dim/heading = "DfltPODim - Defalut for New Dimensions:PO Dimension - DFLT_PO_DIM - Stock - A(15)" item_branch:dflt_vw_dim/heading = "DfltVWDim - Default for New Dimensions:Viewer Dimension - DFLT_VW_DIM - Always Display - A(15)" item_content_def_branch:so_dimension/heading = "SODimVal - Dimension Record:SO Dimension - SO_DIMENSION - Stock - A(15)" item_content_def_branch:po_dimension/heading = "PODimVal - Dimension Record:PO Dimension - PO_DIMENSION - Stock - A(20)" item_content_def_branch:viewer_dimension/heading = "DimViewerVal - Dimension Record:Viewer Dimension - VIEWER_DIMENSION - Always Display - A(15)" item_branch:track_ship_ser_num_ai/heading = "SerNumShipAIVal - Misc:Track Serial #'s for Shipments that Affect Inv - TRACK_SHIP_SER_NUM_AI - Do Not Use - A(24)" item_branch:track_ship_ser_num_dnai/heading = "SerNumShipDNAIVal - Misc:Track Serial #'s for Shipments that Do Not Affect Inv - TRACK_SHIP_SER_NUM_DNAI - Do Not Use - A(24)" item_branch:track_ser_num_qty_uom_ai/heading = "SerNumQtyUOMAIVal - Misc:Track Serial #'s for Shipments that Affect Inv Qty UOM - TRACK_SER_NUM_QTY_UOM_AI - Display - A(16)" item_branch:track_ser_num_qty_uom_dnai/heading = "SerNumQtyUOMDNAIVal - Misc:Track Serial #'s for Shipments that Do Not Affect Inv Qty UOM - TRACK_SER_NUM_QTY_UOM_DNAI - Display - A(16)" if item_branch:price_rep_item = 1 then "YES" else "NO" /heading = "RepItemVal - Misc:Representative Item - PRICE_REP_ITEM - NO - YES/NO" if item_branch:price_optimized = 1 then "YES" else "NO" /heading = "PriceOptimizedVal - Price Optimized - PRICE_OPTIMIZED - NO - YES/NO" /* Tran Defaults */ if item_branch:fill_entire_qty_src = 1 then "YES" else "NO" /heading = "FillQtySOVal - Fill Entire Qty from Source:From Sales Orders - FILL_ENTIRE_QTY_SRC - NO - YES/NO" if item_branch:rm_fill_entire_qty_src = 1 then "YES" else "NO" /heading = "FillQtyRemanVal - Fill Entire Qty from Source:From Reman Inputs - RM_FILL_ENTIRE_QTY_SRC - NO - YES/NO" item_branch:dflt_rm_key/heading = "RMKeyVal - Reman Defaults:Default Prefinish Key - DFLT_RM_KEY - - A(2)" item_branch:dflt_operation_type/heading = "RMOperationTypeVal - Reman Defaults:Default Operation Type - DFLT_OPERATION_TYPE - - A(1)" item_branch:dflt_operation/heading = "RMOperationVal - Reman Defaults:Default Operation - DFLT_OPERATION - - A(16)" item_branch:bulk_gm_pct_default/decimalplaces=2 /heading = "BulkItemGMDefPercentVal - Bulk Item GM Default % - BULK_GM_PCT_DEFAULT - 0 - N(3.2)" if item_branch:auto_commit = 1 then "YES" else "NO" /heading = "CommitAutoAsgnVal - Commit Records:Auto Assign - AUTO_COMMIT - NO - YES/NO" if item_branch:exact_commit = 1 then "YES" else "NO" /heading = "CommitReqExQtyVal - Commit Records:Require Exact Quantity - EXACT_COMMIT - NO - YES/NO" if item_branch:commit_all = 1 then "YES" else "NO" /heading = "CommitAllnoBOVal - Commit Records:Commit All Do Not Backorder - COMMIT_ALL - NO - YES/NO" if item_branch:commit_def_loc = 1 then "YES" else "NO" /heading = "CommitDefLocOnlyVal - Commit Records:Commit From Default Location Only - COMMIT_DEF_LOC - NO - YES/NO" if item_branch:commit_at_branch = 1 then "YES" else "NO" /heading = "CommitBrnchOrdCreateVal - Commit Records:Commit at Branch at Order Creation - COMMIT_AT_BRANCH - NO - YES/NO" if item_branch:commit_lowest_level = 1 then "YES" else "NO" /heading = "CommitOldtoLowestVal - Commit Records:Commit Oldest Material to Lowest Level - COMMIT_LOWEST_LEVEL - NO - YES/NO" if item_branch:commit_oldest_first = 1 then "YES" else "NO" /heading = "CommitFIFOVal - Commit Records:Regardless of Available (FIFO) - COMMIT_LODEST_FIRST - NO - YES/NO" if item_branch:cmt_on_hand = 1 then "YES" else "NO" /heading = "CommitSpecFinalVal - Commit Records:Specify Final Commit from On Hand - CMT_ON_HAND - NO - YES/NO" if item_branch:auto_uncommit = 1 then "YES" else "NO" /heading = "AutoUncommitVal - Commit Records: Auto Uncommit Higher Level Commits - AUTO_UNCOMMIT - NO - YES/NO" item_branch:full_tag_commit/heading = "FullTagCommitVal - Commit Records:Full Tag Commit - FULL_TAG_COMMIT - NO - A(8)" item_branch:long_lead_days/decimalplaces=0 /heading = "LLPLdDaysVal - Long Lead Processing:Lead Days - LONG_LEAD_DAYS - 0 - N(4.0)" item_branch:long_lead_purch_days/decimalplaces=0 /heading = "LLPPurchLdDaysVal - Long Lead Processing:Purchase Lead Days - LONG_LEAD_PURCH_DAYS - 0 - N(4.0)" if item:display_comp_items = 1 then "YES" else "NO" /heading = "DispCompItemVal - Item Specific:Display Complementary Items - DISLPLAY_COMP_ITEMS - NO - YES/NO" /* Tally Defaults */ if item_branch:display_dimensions_so = 1 then "YES" else "NO" /heading = "DispDimTSSOVal - Display Dimensions in Tally Selection:From Sales Orders - DISPLAY_DIMENSIONS_SO - YES - YES/NO" if item_branch:display_ns_dim_so = 1 then "YES" else "NO" /heading = "DispNSDimSOVal - Display Dimensions in Tally Selection:Display non stock dimensions - DISPLAY_NS_DIMENSIONS_SO - YES - YES/NO" if item_branch:display_ns_zero_qty_dim_so = 1 then "YES" else "NO" /heading = "DispNSZeroQtyDimSOVal - Display Dimensions in Tally Selection:Display non stock dimensions with zero qty on hand - DISPLAY_NS_ZERO_QTY_DIM_SO - NO - YES/NO" if item_branch:display_dimensions_rm = 1 then "YES" else "NO" /heading = "DispDimTSRemanINVal - Display Dimensions in Tally Selection:From Reman Inputs - DISPLAY_DIMENSIONS_RM - YES - YES/NO" if item_branch:display_dimensions_sr = 1 then "YES" else "NO" /heading = "DispDimTSSRVal - Display Dimensions in Tally Selection:From Supplier Returns - DISPLAY_DIMENSIONS_SR - NO - YES/NO" if item_branch:display_dimensions_po = 1 then "YES" else "NO" /heading = "DispDimOTPOVal - Display Dimensions in Order Tally:From Purchase Order - DISPLAY_DIMENSIONS_PO - YES - YES/NO" if item_branch:display_dimensions_rmoutput = 1 then "YES" else "NO" /heading = "DispDimOTRemanOUTVal - Display Dimensions in Order Tally:From Reman Outputs - DISPLAY_DIMENSIONS_RMOUTPUT - YES - YES/NO" item_branch:copy_so_tally/heading = "DefCopySOTallyVal - Default for Copy SO Tally - COPY_SO_TALLY - Don't Copy - A(20)" if item_branch:auto_tally_pick = 1 then "YES" else "NO" /heading = "TallyDefAutoTallyPickVal - Tally Defaults:Auto Tally with Pick File Creation - AUTO_TALLY_PICK - NO - YES/NO" if item_branch:auto_tally_wo_print = 1 then "YES" else "NO" /heading = "TallyDefAutoTallyWOPrintVal - Tally Defaults:Auto Tally with Work Order Print - AUTO_TALLY_WO_PRINT - NO - YES/NO" if item_branch:limit_short_lengths = 1 then "YES" else "NO" /heading = "TallyDefLimitShrtVal - Tally Defaults:Limit Shorts - LIMIT_SHORT_LENGTHS - NO - YES/NO" item_branch:short_percent/decimalplaces=2 /heading = "TallyDefPctVal - Tally Defaults:Percentage - SHORT_PERCENT - - N(3.2)" item_branch:short_length/decimalplaces=4 /heading = "TallyDefShrtLgthVal - Tally Defaults:Short Length - SHORT_LENGTH - - N(4.4)" if item_branch:dflt_commit_tally = 1 then "YES" else "NO" /heading = "SaveTallyAsVal - Tally Defaults:Save Tally as - DFLT_COMMIT_TALLY - YES - YES/NO" if item_branch:allow_new_dimension = 1 then "YES" else "NO" /heading = "AllowNewDimVal - Tally Selection:Allow Entry of New Dimensions - ALLOW_NEW_DIMENSION - YES - YES/NO" /* Form Settings */ if item:label_flag = "none" then "None" else if item:label_flag = "dim_pccount_pak_remain" then "Dimension/PC cnt-one per min pak/one per each remaining" else if item:label_flag = "dim_pccount_pak_total" then "Dimension/PC cnt- one per min pak/one for total remaining" else if item:label_flag = "mul_of_qty" then "Multiple of qty" else if item:label_flag = "pak_remain" then "One per min pak/one per each remaining" else if item:label_flag = "pak_total" then "One per min pak/one for total remaining" else if item:label_flag = "per_qty" then "One per qty" else if item:label_flag = "per_line" then "One per line" else if item:label_flag = "one_per_tag" then "One per tag" else if item:label_flag = "per_BOM_sundry" then "Qty based on sundry component" /heading = "LabelQtyVal - Labels:Label Qty - LABEL_FLAG - None - A(20)" item:ship_label/decimalplaces=0 /heading = "MultiplierVal - Labels:Multiplier - SHIP_LABEL - 0 - N(6.0)" item:label_component_details/heading = "CompDetailsVal - Labels:Component Details - LABEL_COMPONENT_DETAILS - Do Not Send - A(30)" item:label_sundry_item/heading = "SundryCompVal - LAbels:Sundry Component - LABEL_SUNDRY_ITEM - - A(16)" item:ship_label_misc/heading = "ShipLabMiscVal - Labels:Ship Label Misc - SHIP_LABEL_MISC - - A(25)" item:label_format/heading = "LabelFormatVal - Labels:Label Format - LABEL_FORMAT - - A(12)" if item:use_inv_label_first = 1 then "YES" else "NO" /heading = "UseInvLabFirstVal - Labels:Use Inventory Label First - USE_INV_LABEL_FIRST - NO - YES/NO" item:label_format_inventory/heading = "InvLabelFormatVal - Labels:Inv Label Format - LABEL_FORMAT_INVENTORY - - A(12)" if item:print_item_totals = 1 then "YES" else "NO" /heading = "PickPrtItemTotVal - SO/Quote Forms:Print Item Totals - PRINT_ITEM_TOTALS - NO - YES/NO" if item:override_pg_totals = 1 then "YES" else "NO" /heading = "PickUseItemSetVal - SO/Quote Forms:Use Item Settings for Product Group Totals - OVERRIDE_PG_TOTALS - NO - YES/NO" zPringGroupType/heading = "PickPrtFactorVal - SO/Quote Forms:Print By - PRING_GROUP_TYPE - Qty - *****" if item:print_uom = 1 then "YES" else "NO" /heading = "PickPrtUOMBoxVal - SO/Quote Forms:Print UOM - PRING_UOM - YES - YES/NO" item:print_group_uom/heading = "PrntGrpUOMVal - SO/Quote Forms:Total UOM - PRING_GROUP_UOM - - A(4)" item:print_group_description/heading = "PickDescrVal - SO/Quote Forms:Total Description - PRINT_GROUP_DESCRIPTION - - A(40)" if item:print_tag_desc = 1 then "YES" else "NO" /heading = "PrintTagDescVal - SO/Quote Forms:Print Tag Description - PRINT_TAG_DESC - NO - YES/NO" if print_item_ext_desc = 1 then "YES" else "NO" /heading = "PrtExtDescrVal - Forms:Print Item Ext Description on Forms - PRINT_ITEM_EXT_DESC - NO - YES/NO" /* Misc */ item:round_method/heading = "RoundMethVal - Misc:Round Methoud - ROUND_METHOD - - A(8)" item:length/decimalplaces=4 /heading = "RoundLengthVal - Misc:Length - LENGTH - - N(4.4)" if item:direct_only = 1 then "YES" else "NO" /heading = "DirectOnlyVal - Misc:Direct Only - DIRECT_ONLY - NO - YES/NO" if item:temporary = 1 then "YES" else "NO" /heading = "TemporaryVal - Misc:Temporary - TEMPORARY - NO - YES/NO" if item:assort_pricing = 1 then "YES" else "NO" /heading = "AsstPricingVal - Misc:Assortment Pricing - ASSORT_PRICING - NO - YES/NO" if item:commission_eligible = 1 then "YES" else "NO" /heading = "EligCommissionVal - Misc:Eligible for Commission - COMMISSION_ELIGIBLE - YES - YES/NO" if item:discountable = 1 then "YES" else "NO" /heading = "TermsDiscountVal - Misc:Terms Discountable - DISCOUNTABLE - YES - YES/NO" if item:allow_desc_override = 1 then "YES" else "NO" /heading = "AllowSizeDescOverVal - Misc:Allow Size and Description Override - ALLOW_DESC_OVERRIDE - YES - YES/NO" item:bom_qty_type/heading = "PBOMQtyTypeVal - Misc:BOM Qty Type - BOM_QTY_TYPE - BOM Qty - A(10)" xBOM_RTS_Item:item/heading = "WOReturnToStockItemVal - Misc:WO Return to STock Item - BOM_RTS_ITEM_PTR - - A(16)" item:routing_capacity_factor/decimalplaces=4 /heading = "RoutingCapacityFactorVal - Misc:Routing Capacity Factor - ROUTING_CAPACITY_FACTOR - 0 - N(6.4)" xTaxCategory:tax_category/heading = "TaxCategoryVal - Misc:Tax Category - TAX_CATEGORY_GUID - - A(25)" if item:taxable = 1 then "YES" else "NO" /heading = "TaxSalesTaxVal - Misc:Taxable for Sales Tax - TAXABLE - YES - YES/NO" if item:cost_taxable = 1 then "YES" else "NO" /heading = "TaxTaxCostVal - Misc:Taxable for Tax Cost - COST_TAXABLE - NO - YES/NO" if item:duplicate_item_warning = 1 then "YES" else "NO" /heading = "WarnIfDupItemVal - Misc:Warn if Duplicate Item (Transaction Entry) - DUPLICATE_ITEM_WARNING - YES - YES/NO" if item:display_market = 1 then "YES" else "NO" /heading = "DispMktCostGMVal - Misc:Display Market Cost and GM - DISPLAY_MARKET - YES - YES/NO" if item:dw_sales_component = 1 then "YES" else "NO" /heading = "DWSaCompVal - Misc:DW SAles Analysis Component - DW_SALES_COMPONENT - NO - YES/NO" if item:bom_comp_discount_item = 1 then "YES" else "NO" /heading = "BOMCompDiscItemVal - Misc:BOM Component Discount Item - BOM_COMP_DISCOUNT_ITEM - NO - YES/NO" item:bol_code/heading = "BOLCodeVal - Shipping Documentation:BOL Code - BOL_CODE - - A(30)" item:msds/heading = "HazMSDSVal - Shipping Documentation:MSDS - MSDS - - A(5)" item:cat_page/heading = "CatalogPageVal - Catalog:Page - CAT_PAGE - - A(6)" item:cat_section/decimalplaces=0 /heading = "CatalogSectVal - CatalogSectVal - CAT_SECTION - - N(6.0)" item:cat_seq/decimalplaces=0 /heading = "CatalogSeqVal - Catalog:Sequence - CAT_SEQ - - N(6.0)" item:labor_units/decimalplaces=4 /heading = "ProdSchedUnitsVal - Production Scheduling:Labor Units - LABOR_UNITS - - N(7.4)" item:machine_units/decimalplaces=4 /heading = "ProdSchedMachineUnitsVal - Production Scheduling:Machine Units - MACHINE_UNITS - - N(7.4)" item:keyword_string/heading = "KeywordsVal - Multiple Keyword Search:Keywords - KEYWORD_STRING - - A(750)" /* Cost/Price */ item_content_def_branch:market_cost/decimalplaces=4 /heading = "MktCostVal - Inventory Costs:Market Cost - MARKET_COST - 0 - N(7.4)" if item_content_def_branch:fixed_market_cost = 1 then "YES" else "NO" /heading = "MktCostFixVal - Inventory Costs:Market Cost Fixed - FIXED_MARKET_COST - NO - YES/NO" item_branch:market_formula_name/heading = "MktFormulaNameVal - Inventory Costs:Market Formula Name - MARKET_FORMULA_NAME - - A(30)" item_content_def_branch:standard_cost/decimalplaces=4 /heading = "StdCostVal - Inventory Costs:Standard Cost - STANDARD_COST - 0 - N(7.4)" item_content_def_branch:last_po_cost/decimalplaces=4 /heading = "LastPOCostVal - Inventory Costs:Last PO Cost - LAST_PO_COST - 0 - N(7.4)" if item_content_def_branch:fixed_last_po_cost = 1 then "YES" else "NO" /heading = "LastPOCostFixedVal - Inventory Costs:Last PO Cost Fixed - FIXED_LAST_PO_COST - NO - YES/NO" if item_branch:upd_primary_po_cost = 1 then "YES" else "NO" /heading = "UpdLastPOPrimSupVal - Inventory Costs:Update Last PO Cost for Primary Supplier Only - UPD_PRIMARY_PO_COST - YES - YES/NO" if item_branch:upd_last_po_cost_dnai = 1 then "YES" else "NO" /heading = "UpdLastPOIfDNAIVal - Inventory Costs:Update Last PO/Recv Cost when Order Does Not Affect Inv - UPD_LAST_PO_COST_DNAI - YES - YES/NO" item_branch:po_cost_dflt/heading = "POCostDefVal - Inventory Costs:PO Cost Default - PO_COST_DFLT - - A(23)" item_content_def_branch:misc_cost_price_1/decimalplaces=4 /heading = "MiscCost1Val - Misc Cost/Price and Description:Misc Cost 1 - MISC_COST_PRICE_1 - 0 - N(7.4)" item_content_def_branch:misc_cost_price_1_desc/heading = "MiscCost1DescVal - Misc Cost/Price and Description:Misc Cost 1 DEsc - MISC_COST_PRICE_1_DESC - - A(40)" item_content_def_branch:misc_cost_price_2/decimalplaces=4 /heading = "MiscCost2Val - Misc Cost/Price and Description:Misc Cost 2 - MISC_COST_PRICE_2 - 0 - N(7.4)" item_content_def_branch:misc_cost_price_2_desc/heading = "MiscCost2DescVal - Misc Cost/Price and Description:Misc Cost 2 DEsc - MISC_COST_PRICE_2_DESC - - A(40)" item_content_def_branch:misc_cost_price_3/decimalplaces=4 /heading = "MiscCost3Val - Misc Cost/Price and Description:Misc Cost 3 - MISC_COST_PRICE_3 - 0 - N(7.4)" item_content_def_branch:misc_cost_price_3_desc/heading = "MiscCost3DescVal - Misc Cost/Price and Description:Misc Cost 3 DEsc - MISC_COST_PRICE_3_DESC - - A(40)" item_content_def_branch:misc_cost_price_4/decimalplaces=4 /heading = "MiscCost4Val - Misc Cost/Price and Description:Misc Cost 4 - MISC_COST_PRICE_4 - 0 - N(7.4)" item_content_def_branch:misc_cost_price_4_desc/heading = "MiscCost4DescVal - Misc Cost/Price and Description:Misc Cost 4 DEsc - MISC_COST_PRICE_4_DESC - - A(40)" item_content_def_branch:misc_cost_price_5/decimalplaces=4 /heading = "MiscCost5Val - Misc Cost/Price and Description:Misc Cost 5 - MISC_COST_PRICE_5 - 0 - N(7.4)" item_content_def_branch:misc_cost_price_5_desc/heading = "MiscCost5DescVal - Misc Cost/Price and Description:Misc Cost 5 DEsc - MISC_COST_PRICE_5_DESC - - A(40)" /* WMS/Mobile */ if item_branch:auto_resolve_pick = 1 then "YES" else "NO" /heading = "AutoResolvePickVal - WMS/Mobile:Auto Resolve Pick - AUTO_RESOLVE_PICK - NO - YES/NO" if item_branch:wms_send_item = 1 then "YES" else "NO" /heading = "SendItemtoWMSVal - WMS Settings:Send to WMS - WMS_SEND_ITEM - YES - YES/NO" if item_branch:sent_to_wms = 1 then "YES" else "NO" /heading = "SenttoWMSVal - WMS Settings:Sent to WMS - SENT_TO_WMS - NO - YES/NO" item_branch:wms_allow_reservations /heading = "WMSAllowReservationVal - WMS Settings:Allow Lot Reservations - WMS_ALLOW_RESERVATION - NO - YES/NO" if item_branch:wms_lot_required = 1 then "YES" else "NO" /heading = "LotRequiredVal - WMS Settings:Serial # Required - WMS_LOT_REQUIRED - NO - YES/NO" if item_branch:wms_label = 1 then "YES" else "NO" /heading = "WMSLabelsVal - WMS Settings:Label - WMS_LABEL - NO - YES/NO" item_branch:wms_label_qty/decimalplaces=2 /heading = "WMSLabelQtyVal - WMS Settings:Label Quantity - WMS_LABEL_QTY - - N(5.2)" item_branch:wms_item_type/heading = "WMSItemTypeVal - WMS Settings:Item Type - WMS_ITEM_TYPE - - A(15)" item_branch:wms_shop_location/heading = "ShopLocVal - WMS SEttings:Ship Location - WMS_SHOP_LOCATION - - A(8)" item_branch:percent_over_pick/decimalplaces=2 /heading = "OverPickVal - WMS Settings:Over Pick Threshold Percent - PERCENT_OVER_PICK - - N(3.2)" item_branch:percent_under_pick/decimalplaces=2 /heading = "UnderPickVal - WMS Settings:Under Pick Threshold Percent - PERCETN_UNDER_PICK - - N(3.2)" item_branch:wms_pick_from/heading = "WMSPickFromVal - WMS Settings:Pick from - WMS_PICK_FROM - Warehouse - A(9)" item_branch:wms_uom_1/heading = "WMSUOM1Val - WMS Settings:UOM 1 - WMS_UOM_1 - - A(4)" item_branch:wms_uom_2/heading = "WMSUOM2Val - WMS Settings:UOM 2 - WMS_UOM_2 - - A(4)" item_branch:wms_uom_3/heading = "WMSUOM3Val - WMS Settings:UOM 3 - WMS_UOM_3 - - A(4)" if item_branch:wms_use_partial_pieces = 1 then "YES" else "NO" /heading = "WMSUsePartialPiecesVal - WMS Settings:Send Partial PC Ref UOMs - WMS_USE_PARTIAL_PIECES - NO - YES/NO" item_branch:percent_over_pick_mobile/decimalplaces=2 /heading = "MobOverPickVal - Mobile Settings:Over Pick Threshold Percent - PERCENT_OVER_PICK_MOBILE - - N(3.2)" item_branch:percent_under_pick_mobile/decimalplaces=2 /heading = "MobUnderPickVal - Mobile Settings:Under Pick thereshold Percent - PERCENT_UNDER_PICK_MOBILE - - N(3.2)" item_branch:percent_over_receive/decimalplaces=2 /heading = "MobOverRecvVal - Mobile Settings:Over Receive Threshold Percent - PERCENT_OVER_RECEIVE - - N(3.2)" item_branch:percent_under_receive/decimalplaces=2 /heading = "MobUnderRecvVal - Mobile Settings:Under Receive Threshold Percent - PERCENT_UNDER_RECEIVE - - N(3.2)" item_branch:num_tags_to_print/decimalplaces=0 /heading = "MobNumofTagsVal - Mobile Settings:Number of Tags to Print - NUM_TAGS_TO_PRINT - 0 - N(3.0)" item_branch:dflt_tag_remain_qty/heading = "DfltTagRemainQtyVal - Mobile Settings:Tag Split Defalut Remaining Qty to - DFLT_TAG_REMAIN_QTY - Original Tag - A(12)" /* Primary Supplier */ xItemSupplier:supplier_code/heading = "PrimSupVal - Primary Supplier:Supplier Code - SUPPLIER_CODE - - A(15)" xItemSupplier:ship_from_seq_num/decimalplaces=0 /heading = "ShipFromSeqVal - Primary Supplier:Ship from Seq - SHIP_FROM_SEQ_NUM - - N(4.0)" xItemXref:xref_num/heading = "SuppPartUPCVal - Primary Supplier:Part #/UPC - XREF_NUM - - A(50)" xItemXref:upc_flag/heading = "SuppPurposeVal - Primary Supplier:Purpose - UPC_FLAG - X - A(1)" if xItemXref:print_code = 1 then "YES" else "NO" /heading = "SuppPrtOnFormsVal - Primary Supplier:Print on Forms - PRINT_CODE - YES - YES/NO" if xItemXref:print_supp_part_num = 1 then "YES" else "NO" /heading = "SuppPrtXrefOnFormsVal - Primary Supplier:Print Supplier Cross Ref on Customer Forms - PRINT_SUPP_PART_NUM - YES - YES/NO" xItemSupplier:weight/decimalplaces=4 /heading = "SuppWeightVal - Primary Supplier:Weight - WEIGHT - 1 - N(6.4)" xItemSupplier:weight_uom/heading = "SuppWeightUOMVal - Primary Supplier:Weight UOM - WEIGHT_UOM - Stocking UOM - A(4)" xItemSupplier:load_factor/decimalplaces=4 /heading = "SuppLoadVal - Primary Supplier:Load - LOAD_FACTOR - 1 - N(6.4)" xItemSupplier:load_uom/heading = "SuppLoadUOMVal - Primary Supplier:Load UOM - LOAD_UOM - Stocking UOM - A(4)" xItemSupplier:dflt_alt_cost_uom/heading = "SuppCostUOMVal - Primary Supplier:Cost UOM - DFLT_ALT_COST_UOM - - A(4)" xItemSupplier:supp_uom/heading = "SuppQtyUOMVal - Primary Supplier:Qty UOM - SUPP_UOM - - A(4)" if xItemSupplier:use_uom_for_po_entry = 1 then "YES" else "NO" /heading = "SuppUOMForPOVal - Primary Supplier:Use for Order Qty in PO Entry - USE_UOM_FOR_PO_ENTRY - NO -YES/NO" if xItemSupplier:use_uom_for_po_from_spo = 1 then "YES" else "NO" /heading = "SuppUOMForPOFromSPOVal - Primary Supplier:Use for Order Qty on PO from SPO - USE_UOM_FOR_PO_FROM_SPO - NO - YES/NO" if xItemSupplier:use_uom_for_printed_po = 1 then "YES" else "NO" /heading = "SuppUOMForPOPrtVal - Primary Supplier:Use for Order Qty on Printed PO - USE_UOM_FOR_PRINTED_PO - NO - YES/NO" if xItemSupplier:use_uom_for_po_check_in = 1 then "YES" else "NO" /heading = "SuppUOMForPOChkInVal - Primary SUpplier:Use for Qty Remain on PO Check in List - USE_UOM_FOR_PO_CHECK_IN - NO - YES/NO" if xItemSupplier:use_uom_for_receiving = 1 then "YES" else "NO" /heading = "SuppUOMForRecvVal - Primary Supplier:Use for Receiving Qty - USE_UOM_FOR_RECEIVING - NO - YES/NO" if xItemSupplier:lead_time_flag = 1 then "YES" else "NO" /heading = "SuppUpdateLeadVal - Primary Supplier:Update Lead - LEAD_TIME_FLAG - YES - YES/NO" xItemSupplier:lead_time[1 ]/heading = "SuppLeadTime1Val - Primary Supplier:Most Recent - LEAD_TIME1 - 0 - N(6.0)" xItemSupplier:lead_time[2 ]/heading = "SuppLeadTime2Val - Primary Supplier:2nd Recent - LEAD_TIME2 - 0 - N(6.0)" xItemSupplier:lead_time[3 ]/heading = "SuppLeadTime3Val - Primary Supplier:3nd Recent - LEAD_TIME3 - 0 - N(6.0)" xItemSupplier:lead_time[4 ]/heading = "SuppLeadTime4Val - Primary Supplier:4nd Recent - LEAD_TIME4 - 0 - N(6.0)" xItemSupplier:lead_time[5 ]/heading = "SuppLeadTime5Val - Primary Supplier:5nd Recent - LEAD_TIME5 - 0 - N(6.0)" xItemSupplier:min_ord_qty/decimalplaces=4 /heading = "SuppMinOrdQtyVal - Primary Supplier:Minimum Order Quantity - MIN_ORD_QTY - 0 - N(9.4)" xItemSupplier:min_ord_qty_disp_uom/heading = "SuppMinOrdQtyUOMVal - Primary Supplier:Minimum Order UOM - MIN_ORD_QTY_DISP_UOM - Stocking UOM - A(4)" xItemSupplier:min_ord_violation/heading = "SuppMinOrdVioVal - Primary Supplier:Minimum Order Violation - MIN_ORD_VIOLATION - Allow Question - A(24)" xItemSupplier:min_pak/decimalplaces=4 /heading = "SuppMinPakVal - Primary Supplier:Minimum Pack - MIN_PAK - 0 - N(5.4)" xItemSupplier:min_pak_disp_uom/heading = "SuppMinPakUOMVal - Primary Supplier:Minimum Pack UOM - MIN_PAK_DISP_UOM - Stocking UOM - A(4)" xItemSupplier:min_pak_violation/heading = "SuppMinPakVioVal - Primary Supplier:Minimum Pack Violation - MIN_PAK_VIOLATION - Allow Question - A(24)" xItemSupplier:dflt_lot_option/heading = "SuppDefLotVal - Primary Supplier:Default Lot - DFLT_LOT_OPTION - Lot - A(16)" xItemSupplier:dflt_lot_value/heading = "SuppDefLotValueVal - Primary Supplier:Lot Value - DFLT_LOT_VALUE - - A(16)" xItemSupplier:dflt_content_option/heading = "SuppDefContentVal - Primary Supplier:Default Content - DFLT_CONTENT_OPTION - Content - A(16)" xItemSupplier:dflt_content_value/heading = "SuppDefContentValueVal - Primary Supplier:Content Value - DFLT_CONTENT_VALUE - - A(22)" xItemSupplier:supp_rebate_report_uom/heading = "SuppRebateRptUOMVal - Primary Supplier:Rebate Report UOM - SUPP_REBATE_REPROT_UOM - - A(4)" xItemSupplier:piece_count/decimalplaces=0 /heading = "SuppDefPCVal - Primary Supplier:Defalut Piece Count - PIECE_COUNT - 0 - N(5.0)" /* LIFO */ item_content_def_branch:lifo_pool_id/heading = "LifoPoolIDVal - LIFO:Pool ID - LIFO_POOL_ID - - A(16)" item_content_def_branch:index_factor/decimalplaces=4 /heading = "LifoIndexFactorVal - LIFO:Index Factor - INDEX_FACTOR - 1 - N(8.4)" item_content_def_branch:lifo_curr_year_qty/decimalplaces=4 /heading = "LifoCurrYearQtyVal - LIFO:Current Year Quantity - LIFO_CURR_YEAR_QTY - 0 - N(7.4)" item_content_def_branch:lifo_curr_year_cost/displaywidth=4 /heading = "LifoCurrYearCostVal - LIFO:Current Year Cost - LIFO_CURR_YEAR_COST - 0 - N(7.4)" item_content_def_branch:lifo_curr_year_date/mask="MM/DD/YYYY" /heading = "LifoCurrYearDateVal - LIFO:Current Year Date - LIFO_CURR_YEAR_DATE - - D(MM/DD/YYYY)" item_content_def_branch:lifo_curr_year_recv_cost/decimalplaces=4 /heading = "LifoCurrYearFirstReceivedCostVal - LIFO:Current Year First REceived Cost - LIFO_CURR_YEAR_RECV_COST - 0 - N(7.4)" item_content_def_branch:lifo_curr_year_recv_date/mask="MM/DD/YYYY" /heading = "LifoCurrYearFirstReceivedDateVal - LIFO:Current Year First Received Date - LIFO_CURR_YEAR_RECV_DATE - - D(MM/DD/YYYY)" item_content_def_branch:lifo_base_year_qty/decimalplaces=4 /heading = "LifoBaseYearQtyVal - LIFO:Base/Prior Year Quantity - LIFO_BASE_YEAR_QTY - 0 - N(7.4)" item_content_def_branch:lifo_base_year_cost/decimalplaces=4 /heading = "LifoBaseYearCostVal - LIFO:Base/Prior Year Cost - LIFO_BASE_YEAR_COST - 0 - N(7.4)" item_content_def_branch:lifo_base_year_date/mask="MM/DD/YYYY" /heading = "LifoBaseYearDateVal - LIFO:Base/Prior Year Date - LIFO_BASE_YEAR_DATE - - D(MM/DD/YYYY)" item_content_def_branch:lifo_prev_year_recv_cost/decimalplaces=4 /heading = "LifoBaseYearFirstReceivedCostVal - LIFO:Base/Prior Year First Received Cost - LIFO_PREV_YEAR_RECV_COST - 0 - N(7.4)" item_content_def_branch:lifo_prev_year_recv_date/mask="MM/DD/YYYY" /heading = "LifoBaseYearFirstReceivedDateVal - LIFO:Base/Prior Year First Received Date - LIFO_PREV_YEAR_RECV_DATE - - D(MM/DD/YYYY)" sorted by item_content_def_branch:item item_content_def_branch:width item_content_def_branch:length
AR20059 - Minimum Order Hold Processing
Agility
- Customer
Minimum Order Hold Processing
Use the minimum order hold feature to control shipping costs by requiring a customer ship-to location to order a minimum amount before you make a delivery to them.
To set up minimum order hold for a customer ship-to:
Go To > Data Files > Customer Information > Customers > Define Ship-To
Under the Default Flags tab, enter the desired amount in the minimum order hold amount field.
To set up minimum order holds that are branch specific :
From the Ship-to record, select the Maintain Branch Settings icon.
You will have to enable default flags, and then you can set a minimum order hold for the branch selected.
To update the minimum order hold processing amount for multiple customers via mass update:
Go To > System Administration > Mass Updates > Customer Mass Update
Field Name: Minimum Order Hold Amount; Enter the desired new value and click add.
Validate the procedure and then run the process. Click Yes When prompted.
The apply minimum order hold rules flag must be set on sale types and ship via methods that will be used with minimum order requirements.
Go To > Data Files > Sales Order Settings > Sale Types
Go To > Data Files > Ship Via Methods
After saving a sales order that does not meet the minimum order hold requirements, the status will change to Minimum Order Hold . Once the order is put on hold, it cannot be processed further until it is released or until the customer ship-to meets the minimum order requirements. (The order will not be accessible in Order Processing.)
Create a sales order viewer to use as a minimum order hold queue .
Go To > Sales Orders/Quotes >Viewers > SO Viewer
Within the Order Criteria tab, set Included minimum order hold/on hold orders to “Only minimum order hold/ on hold orders”.
Review security to limit which users can release orders from minimum order hold. “Release SO from Minimum Order Hold/On Hold” security action controls whether you can release an order from minimum order hold or unset the “On Hold” flag in Sales Order Entry. The action also controls whether you can release orders via the “Release from on hold/min order hold” process selection from the sales order viewer results screen.”
Go To > System Administration > Security Administration > Action Allocation
AR20082 - Cyberquery (CQ) Sample: Dead Stock Criteria to be removed in 5.4.2
Agility
- Cyberquery Samples
This query will allow you to see a list all saved criteria records for the Usage/Purchase Comparison Report that reference the Dead Stock Report directly. In addition, this report identifies any impacted the user/group for which the criteria was created, and whether the criteria is attached to an Automated Processing Task or Dashboard. Use this information to ensure criteria can be recreated after the release.
DMSi strongly suggests running this Cyberquery report prior to loading the 5.4.2 release.
*TO RUN THIS QUERY, PLEASE COPY ALL TEXT BELOW THIS POINT INTO A MACRO.
To do this, open Report Writer > VCQ Report Writer. Click Cancel in the Cyberquery report wizard. Click the Select Language Editor icon (looks like a keyboard) in the top middle of the screen. In the top left corner, click File > New > New macro (or just type Control + M).*
list/domain="Dummy"/nodefaults/pagelength=0 'where dashboard_report_links_user:report_id = "UsagePurchCompRpt" '/newline ' '/newline 'list/domain="dashboard_report_links_user"/hold="hf_dashboard_report_links_user" '/newline ' report_name /keyelement=1.1 '/newline ' report_access_type /keyelement=1.2 '/newline ' report_accessed_by /keyelement=1.3 '/newline ' user_id '/newline ' section_name '/newline ' section_id '/newline ' display_sequence '/newline ' dashboard_name '/newline ' applies_to_branch '/newline ' access_type '/newline ' accessed_by '/newline ' report_subfolder '/newline ' report_type '/newline ; run rreplace hf_dashboard_report_links_user cli mv hf_dashboard_report_links_user.cq hf_dashboard_report_links_user.eq cli rename hf_dashboard_report_links_user.cq hf_dashboard_report_links_user.eq run hf_dashboard_report_links_user.eq list/domain="Dummy"/nodefaults/pagelength=0 'define access queue_job_detail, set '/newline ' criteria_type = "Usage/Purchase Comparison Report", '/newline ' criteria_name = report_criteria_detail:report_name, '/newline ' access_type = report_criteria_detail:access_type, '/newline ' accessed_by = report_criteria_detail:accessed_by, one to many '/newline ' '/newline 'define access hf_dashboard_report_links_user, set '/newline ' report_name = report_criteria_detail:report_name, '/newline ' report_access_type = report_criteria_detail:access_type, '/newline ' report_accessed_by = report_criteria_detail:accessed_by, one to many '/newline ' '/newline ' '/newline 'define access company_prof, '/newline ' set prof_name = queue_job_detail:processing_branch '/newline ' '/newline 'where '/newline ' report_criteria_detail:report_id = "UsagePurchCompRpt" and '/newline ' report_criteria_detail:widget_name = "cb-include" and '/newline ' report_criteria_detail:widget_value = "3" '/newline ' '/newline 'list/domain="report_criteria_detail" '/newline ' '/newline ' report_criteria_detail:report_name/noduplicates '/newline ' report_criteria_detail:accessed_by/noduplicates '/newline ' report_criteria_detail:access_type/noduplicates '/newline ' '/newline ' hf_dashboard_report_links_user:dashboard_name '/newline ' hf_dashboard_report_links_user:section_name '/newline ' hf_dashboard_report_links_user:user_id '/newline ' '/newline ' queue_job_detail:queue_job_name /heading="Job Name" '/newline ' queue_job_detail:queue_task_seq /heading="Task Sequence" '/newline ' company_prof:branch_id /heading="Processing Branch" '/newline ' queue_job_detail:report_data_type '/newline ' queue_job_detail:sender /heading="' + "'Sent from'" + ' Email" '/newline ' queue_job_detail:subject_line /heading="Email Subject" '/newline ' queue_job_detail:email_completion /heading="Report Completed" '/newline ' queue_job_detail:email_errorr_msg /heading="Error Messages" '/newline ' queue_job_detail:email /heading="' + "'Sent to'" + ' Email" '/newline ' '/newline 'sorted by '/newline ' report_criteria_detail:report_name '/newline ' report_criteria_detail:accessed_by '/newline ' report_criteria_detail:access_type '/newline ' queue_job_detail:queue_job_name '/newline ' queue_job_detail:queue_task_seq '/newline ; run rreplace dead_stock cli mv dead_stock.cq dead_stock.eq cli rename dead_stock.cq dead_stock.eq run dead_stock.eq view
AR20109 - SYS-202 Tips & Tricks for System Managers
Agility
- Partners Conference
AR20133 - SAL-102 Inside Sales Ninja
Agility
- Partners Conference
AR20150 - OPS 200 Backorders Happen, So Improve!
Agility
- Partners Conference
AR20220 - Connecting to Agility
Technical Services
- User Administration
Hosted Agility Environments CONNECTING TO AGILITY Updated Q2 2024
Our latest iteration of hosted Agility offers a more robust and client-friendly delivery model with Remote App exclusively via the Hosted Agility Launcher. RemoteApp supports flexible access with a more native look and feel as Agility appears to be running on your local Windows computer.
WHAT YOU NEED TO DO Step 1 : Set up/update your AVC (Agility Virtual Channel). This is required for all customers!
*Note- Mass Deployment is also available. Please request these instructions from Systems Engineering.
Step 2: Determine the best connection option:
A. Portal Based RemoteApp via HAL Users access the current Agility login via the Hosted Agility Launcher (HAL) icon from hosting.dmsi.com.
B. RemoteApp and Desktop Connections (RADC Webfeeds) is highly recommended! Users access the current Agility login via Hosted Agility Launcher (HAL) from their Windows start menu. This connection is always current and always points to the correct location. (This is also supported by Active Directory/GPO deployment.)
C. HTML5 Web Client allows access to RemoteApp from any available HTML5 compatible browser. (This option does present some limitations on areas such as printing and file browsing.)
D. iOS/Android/MacOS allows access to the most current Agility portal applications from iOS/Android mobile devices and Apple computers without a web browser.
NOTE: Only Windows 10 and higher are supported client operating systems.
STEP 1: SET UP AGILITY VIRTUAL CHANNEL
The first step in Connecting to Agility requires a user to install the Agility Virtual Channel (AVC) client on their machine.
AVC can be downloaded from Helpful links on the DMSi portal at https://hosting.dmsi.com and in HAL (Hosted Agility Launcher) under the Helpful links tab.
The Agility Virtual Channel Quick Guide article will provide steps on How to Install the AVC client on a single machine, How to Update AVC, How to Uninstall and troubleshooting tips.
Click Here for access to the Article 'Agility Virtual Channel Quick Guide’ .
The Agility Virtual Channel Plugin Manager User Manual article will provide you with in-depth information as it relates to the application and its functions.
Click Here for access to the Article ‘Agility Virtual Channel Plugin Manager’ .
Note: Users with AVC version prior to 5.0 will need to uninstall and reinstall the latest AVC. Failure to update to the latest version can result in service disruption!
You must have permissions to install software on your computer before proceeding with this step .
STEP 2: SET UP ONE OF THE FOLLOWING OPTIONS
Option A. Portal Based RemoteApp Connection
Please be advised. An end user should not pin or save an icon on their desktop, as this can put access to Agility at risk!
The RDWeb Portal is the traditional method for connecting to Agility.
Connect to https://hosting.dmsi.com/ and sign in with your hosting credentials.
Select the Hosted Agility Launcher (HAL) ICON
NOTE: Single Sign On (SSO) only works within browsers that support ActiveX (Internet Explorer). Other browsers will allow you to access the RDS Desktop, but they may require you to log in twice.
Option B. RADC Web feeds (Remote App Desktop Connection Web feeds)
Please be advised. Copying Agility Icons from the start menu to the Desktop or pinning them to the taskbar will break the dynamic update process and put access to Agility at risk!
This option is highly recommended! If you need assistance with setup, please contact Support and we will be happy to help.
Customers leveraging Windows 10 or later are encouraged to take advantage of the native capabilities of RemoteApp and Desktop Connections RADC. When using RADC, the end user always has direct access to the server to sign on to Agility from their start menu.
The RADC (RemoteApp & Desktop Connections) article will provide steps on How to establish a RADC webfeed connection.
Click Here for access to the Article ‘ RADC Webfeeds (RemoteApp and Desktop Connections’) .
Option C. HTML5 Web Client
RemoteApp may also be accessed from any available HTML5 compatible browser. This experience will present some limitations based on your use case such as printing and file browsing.
From a compatible HTML5 Browser go to: https://hosting.dmsi.com/RDWeb/webclient/index.html and enter your login credentials.
You will be presented with the Hosted Agility Launcher Icon.
Option D. IOS/Android/MacOS Customers leveraging IOS or Android are encouraged to take advantage of the Microsoft Remote Desktop 10 app which can be installed from the App or Play stores depending on your OS. When using RADC with the Microsoft Remote Desktop 10 App the end user has the benefit of having the most current portal applications available to them without the need of accessing the portal via their web browser nicely packaged in their Microsoft Remote Desktop 10 App making the experience seamless and convenient.
Download the “Microsoft Remote Desktop 10” App from the Apple App Store or Google Play Store depending on your OS.
Once downloaded and installed, launch Microsoft Remote Desktop 10, and click “Add workspace"
Enter: https://hosting.dmsi.com/rdweb/feed/webfeed.aspx
Enter your login credentials and click “Continue”.
You will then be presented with the Hosted Agility Launcher Icon.
AR20252 - Message: "This sales order is in the process of being canceled..."
Agility
- Sales Orders
AR20385 - How to download a Cyberquery Samples query and run it
Agility
- Cyberquery Samples
How to download a Cyberquery Samples query and run it Find CQ report and download it
Log into the Wedge. Go to dmsi.com/wedge . Put your username and password in and click Login to Account. Click on the Articles tab. Choose a category equals of Cyberquery Samples, then type what you are looking for in the 'Article contains' field. Click Search. When you find the right query, click the link for the article. A new window will open with the text of the query. Highlight the text that contains the query (starting at /* This query will...). Then type Control C (this is Copy).Run report in CQ Report Writer Go into Agility and click on the Report Writer button. Then click on CQ Report Writer. The Cyberquery report wizard may pop open: if it does, click Cancel. Click on the Select Language Editor button to switch the view. Click your cursor into the Enquiry section and paste the query (Control V). To save the query, click on the Save button. The Save enquiry as box will come open. Click on the Up One Level button to move to the cq_reports folder. In the cq_reports folder, type what you want the name of the query to be (using the _ character instead of spaces and all lowercase letters), then click Save.Compile Report so you can run the report You can now run the report by clicking the Run button (or hitting the F6 button). If you would like to run the report from your dashboard or from the CQ Reports, you will need to compile the report. To compile, go to Report Writer/CQ Report Compiler. In the Report name field, type in the name of your report (like list_of_reorder_info.eq). Click Run. A report will print to your screen. If the compile went through, it will say something like Enquiry “list_of_reorder_info” compiled-no errors. To run the report from the CQ Reports, go to the Report Writer/CQ Reports. Click the + next to the cq_reports folder. Find the list_of_reorder_info report, click on it then click Run.Add Report to your Dashboard To add the report to your dashboard, go to the Saved Reports section of the Dashboard. Click the Add Custom Report link. In the Report name field, type the name of the report. In the Text to display, you can change this field to be whatever you want to call your report. Click OK. To run it, click on the Run link next to the name of the report.
AR20546 - Commonly asked questions for Purchasing and Receiving (FAQ)
Agility
- Purchasing
Attached is an FAQ document for Purchasing and Receiving questions that are frequently asked.
Within the attached document is a hyperlink to each Wedge article, which contains step by step instructions and examples from Agility.
Purchasing and Receiving FAQ’s
How do I correct a PO I received with the wrong supplier? AR496
How can I do a receiving quantity or cost adjustment? AR18648
How can I return material to a supplier and where does it post? AR20556 AR261
Why am I getting a “specify storage” error when trying to receive? AR20549
How can I add a delivery charge to a PO or receiving OR adjust the charge AR19556
How can I add freight to a PO or receiving OR adjust the freight cost OR get rid of the question about adding freight AR984 AR362
How to correct the cost of material received at a wrong cost AR2444
AR20595 - AR Open and Paid Inquiry - v553 and up
Agility
- A/R
A/R Open and Paid Inquiry Overview The A/R Open and Paid Inquiry window is where you can research open and paid accounts receivable items. The Search by dropdown determines if you are looking at payments or invoices/transactions.
Note : This article is specific to Agility version v553 and up. If you are using a version prior to v553, please reference AR24399 .
Setting up search criteria The Search Criteria section allows you to set up different criteria to meet different needs. Criteria can be saved, allowing you to quickly access information. Once the criteria and your grid view has been modified to your liking, select Save Criteria and save your selections with the name of your choice and who is allowed to access it. You must have the action allocation to Save Criteria for All Users/Groups or Save Criteria for User set in order to complete this function.
Criteria is saved with the value of the Search by dropdown as there are different columns available based on the value of the Search by dropdown.
Running Inquiry Once you have search criteria set up, select either of the Search buttons to pull in records. If changes are made to the criteria, select Search again to refresh the grid.
Payments Parent/Child Grid The A/R Open and Paid Inquiry is different than other inquiry windows within the A/R, A/P, and G/L modules as it utilizes a parent/child grid for each invoice/payment displayed.
When your Search by value is All payments or Single payment , the parent record represents a specific payment. Detail records underneath that parent represent all invoices to which the payment was applied.
In the below screenshot, since the Search by value is set to Single payment the parent shows that payment 1620-1 was entered on 01/06/20 for $85.09 while the details show that this payment was applied to invoice WEST00318223-001. The details also show that the invoice is considered closed since it has an Open amt of $0.00.
Invoice/Transaction Parent/Child Grid When the Search by dropdown is set to All invoices , Single invoice , or Single transaction the parent record displays information specific to the invoice or transaction while the detail records are all payments applied to the invoice or transaction.
In the below screenshot, since the Search by dropdown is set to Single transaction the parent shows that invoice WEST00318223-001 was invoiced on 01/06/20 for $85.89 while the details show the invoice was paid in full by check 1620-1 on 01/06/20.
Columns The customizable grid allows you to change the order in which the information is presented. For both invoices and payments. To edit the grid, right click in the grid and select Edit Custom View .
The Customize View window allows you to add columns to the grid by double clicking or selecting them and using the arrows to move them over to the Show these columns in this order section. Use the Applies to field to determine if you are customizing the invoices grid or the payments grid. To change the order of the columns, select the column and use the Move Up/Move Down buttons. The Move Up button moves columns to the left and the Move Down button moves columns to the right in the grid.
Grouping The grid allows for grouping so that you can quickly filter/summarize the data being presented. You can expand the group to see details. To turn on grouping, right click in the grid and select Group by Field . Once selected, you can drag the column heading up to the group section to have the grid group by that column. *Grouping MUST be done prior to being able to subtotal.
Select Summaries The Select Summaries option (i.e. Subtotals) allows you to summarize data at the group level, so you don’t have to expand the details to see the data. In the below screenshot, the Custom View is set to Show totals ‘Top fixed’ and the summary option is turned on for the Open amount and shows the sum of all the invoices.
Exporting from the grid To export out the details, either click the Export icon above the grid or right-click then choose Export Grid to and select the output. You can choose Excel files (.xlsx, .xls and .csv), PDF or email the files.
AR20832 - Query Name: Item Verification_Thick and Width
Agility
- Cyberquery Samples
Query Name: Item Verification_Thick and Width
Related Project: 114584 in v544 – Sheet good item type (standard thickness, width, size format)
When setting Standard Thickness or Standard Width on a sheet good item type record assigned to existing item records, the item records need to be updated with the new settings. While support program 'updstdwidth' exists allowing you to assign the standard width to all dimensions on selected items, there may be records which did not meet the right conditions to automatically complete the update.
The attached query allows you to identify those item records which need manual review and update. The query identifies two types of records:
1. item dimension records where the thickness or width value does not match the standard thickness or standard width that is set up on the item
2. item records where multiple widths or thicknesses exist which the support program could not update automatically
After running the report, review the records and update the Standard Thickness and Standard Width fields accordingly.
NOTE: This report should be run after hours as it could take extra time to process.
Query Details:
/* Note this query must be copied into a macro. You can open a macro by either using the control M or select ""File","New", "New Macro". */
-----Extract valid Branches
where system_id not one of "00CORP"
list /domain="system_file"/nodefaults/pagelength=0
',"'+system_file:system_id+"-"+company_name+'"'
top of report
'"ALL"'
;run
rreplace branch_list.cq
cli mv branch_list.cq branch_list.inc
------Extract Valid Types -------------
where item_type:type = "Sheet Good"
list /domain="item_type"/nodefaults/pagelength=0
',"'+item_type:item_type_name+'"'
top of report
'"ALL"'
;run
rreplace type_list.cq
cli mv type_list.cq type_list.inc
----------------- Enter Prompts ------------------
define string xpara_branch = parameter/prompt="Enter Branch or ALL" default "ALL"
valid
include "branch_list.inc"
define string para_type = parameter/prompt = "Enter Item Type or ALL" default "ALL"
valid
include "type_list.inc"
define string para_check = parameter/prompt="Verify Thickness or Width" default "Thickness"
valid "Thickness","Width"
define string para_validate =parameter/prompt="Verify to item or check inconsistant dimensions" default "Item"
valid "Item", "Inconsistant Dimensions"
define xbranch = subfield(xpara_branch,"-",1)
list /domain="dummy"/nodefaults/pagelength=0
xbranch/newline
para_type/newline
para_check/newline
para_validate/newline
;run
rreplace report_par.cq
cli mv report_par.cq report.par
---------------Print Verification Report -------------------------------
define string para_branch = parameter/prompt="Enter Branch or ALL" default "ALL"
define string para_type = parameter/prompt = "Enter Item Type or ALL" default "ALL"
define string para_check = parameter/prompt="Verify Thickness or Width" default "Thickness"
valid "Thickness","Width"
define string para_validate =parameter/prompt="Verify to item or check inconsistant dimensions" default "Item"
valid "Item", "Inconsistant Dimensions"
define file system_file = access system_file,
set system_id = item_content_def_branch:system_id
define file item_type = access item_type,
set system_id = "00CORP",
set item_type_name = item:item_type_name
define number xcheck = if para_check ="Thickness" then item_content_def_branch:thickness
else if para_check ="Width" then item_content_def_branch:Width
define number xitem_size_check = if para_check ="Thickness" then item:standard_thickness
else if para_check ="Width" then item:standard_width
define number xinvalid_size = if para_validate = "Item" and xitem_size_check = xcheck then 0
else if para_validate = "Item" and xitem_size_check <> xcheck then 1
else 0
define xcount = 1
define xnum_sizes = if total[xcount,xcheck] = 1 then 1 else 0
define xsize1 = if total[xnum_sizes,item_content_def_branch:system_id] = 1 and total[xcount,xcheck] = 1 then xcheck else 0
define xsize2 = if total[xnum_sizes,item_content_def_branch:system_id] = 2 and total[xcount,xcheck] = 1 then xcheck else 0
define xsize3 = if total[xnum_sizes,item_content_def_branch:system_id] = 3 and total[xcount,xcheck] = 1 then xcheck else 0
define xsize4 = if total[xnum_sizes,item_content_def_branch:system_id] = 4 and total[xcount,xcheck] = 1 then xcheck else 0
define xsize5 = if total[xnum_sizes,item_content_def_branch:system_id] = 5 and total[xcount,xcheck] = 1 then xcheck else 0
define xsize6 = if total[xnum_sizes,item_content_def_branch:system_id] = 6 and total[xcount,xcheck] = 1 then xcheck else 0
define xsize7 = if total[xnum_sizes,item_content_def_branch:system_id] = 7 and total[xcount,xcheck] = 1 then xcheck else 0
define xsize8 = if total[xnum_sizes,item_content_def_branch:system_id] = 8 and total[xcount,xcheck] = 1 then xcheck else 0
define xsize9 = if total[xnum_sizes,item_content_def_branch:system_id] = 9 and total[xcount,xcheck] = 1 then xcheck else 0
define xsize10 = if total[xnum_sizes,item_content_def_branch:system_id] = 10 and total[xcount,xcheck] = 1 then xcheck else 0
define xzero_record = if item_content_def_branch:thickness = 0 and width = 0 and length = 0 then "Y" else "N"
define xvalid = if (item:item_type_name = para_type or
(para_type = "ALL" and item_type:type = "Sheet Good"))
and ((xitem_size_check > 0.0000000000 and para_validate = "Item") or para_validate <> "Item" )
and xzero_record = "N"
then "Y"
where item:stock_to_pc_calc > " "
and (item_content_def_branch:system_id = para_branch or para_branch = "ALL")
and xvalid = "Y"
list /domain="item_content_def_branch"/nobanner/duplicates/nodefaults --/nodetail --/hold="hf_variances"
--#item_content_def_branch:item/name="prt_item"
--#thickness width length
--#item:description/name="prt_desc"
--#xnum_sizes
--#item:standard_thickness/heading="STD Width"
--#item:standard_width/heading="STD Length"
--#xsize1/heading=para_check+"1"
--#xsize2/heading=para_check+"2"
--#xsize3/heading=para_check+"3"
--#xsize4/heading=para_check+"4"
--#xsize5/heading=para_check+"5"
--#xsize6/heading=para_check+"6"
--#xsize7/heading=para_check+"7"
--#xsize8/heading=para_check+"8"
--#xsize9/heading=para_check+"9"
--#xsize10/heading=para_check+"10"
--#xinvalid_size
--#xcheck
--#xitem_size_check
sorted by item_content_def_branch:item system_id xcheck
end of item_content_def_branch:system_id/noheading
if
(( para_validate <> "Item" and total[xnum_sizes] > 1 )
or (para_validate = "Item" and total[xinvalid_size] <> 0 )
)
then {
item_content_def_branch:item
item:description
item_content_def_branch:system_id
system_file:company_name
item:standard_thickness
item:standard_width
item:item_type_name
total[xnum_sizes]/name="num_size"
total[xsize1]/name="size1"
total[xsize2]/name="size2"
total[xsize3]/name="size3"
total[xsize4]/name="size4"
total[xsize5]/name="size5"
total[xsize6]/name="size6"
total[xsize7]/name="size7"
total[xsize8]/name="size8"
total[xsize9]/name="size9"
total[xsize10]/name="size10"
}
top of page
"Item #"/align=item_content_def_branch:item
"Item Description"/align=item:description
"Branch ID"/align=item_content_def_branch:system_id
"Branch Name"/align=system_file:company_name
"# of sizes"/align=num_size
"STD Thickness"/align=item:standard_thickness
"STD Width"/align=item:standard_width
"Item Type"/align=item:item_type_name
para_check+"1"/align=size1
para_check+"2"/align=size2
para_check+"3"/align=size3
para_check+"4"/align=size4
para_check+"5"/align=size5
para_check+"6"/align=size6
para_check+"7"/align=size7
para_check+"8"/align=size8
para_check+"9"/align=size9
para_check+"10"/align=size10
;run/parameter=report.par
rreplace item_verification.cq
view
AR20839 - Auto-Select Invoices Using the Cash Application Import
Agility
- A/R
Auto-Select Invoices Using The Cash Application Import The A/R Cash Application window includes an import to save you time by automatically selecting invoices to pay based on payment/remittance information received in a file.
Accounts Receivable > Payments > Cash Application
Select a customer then go to Results.
The Cash Application Import reads the import file and compares it to information in the window to determine which records to select.
Import actions determine whether the file must balance with the window, and the information required in the import file. Based on these actions, records are automatically moved to the Selected items grid with payment and discount amounts applied. Records in the import file can include the invoice ID, payment amount, discount amount, and branch; however, the invoice ID is the only required information. The import includes the ability to validate the file for audit warnings and failures prior to running the import. In determining the records to select, the import considers all credits first and then compares that total to invoices to pay in the import file. The payment amount in the window, records selected at the time of import, and credits in the import file determine the total credit amount used for import comparison.
The ‘Require zero balance’ action setting determines whether the total credits and total payments in the file must net to zero for the import to select any records. When set to No, records are selected until the total payments reach the total credit amount.
The 'Auto apply payment amount' and 'Auto apply eligible discounts' actions allow you to leave the payment amount and/or discount amount blank in the import file and have the import automatically apply these amounts. The ‘Allow invoice overpayment’ option allows a record in the file to have a payment applied in excess of the open amount. This option is set to No when ‘Auto apply payment amount’ is set to Yes.
AR20843 - Cyberquery Troubleshooting Tips
Agility
- Cyberquery
Cyberquery Troubleshooting Tips Determine if the report is a standard Agility report or a custom report.
Standard Agility Report 1. Has Agility recently been upgraded to a new version of Agility? Was Cyberquery upgraded as part of the upgrade?
2. Get the parameters that were used when running the report. A screen shot of all parameter tabs is helpful.
3. Errors such as "Access Denied" or being asked to login to run the report should be sent to DMSI tech (for SaaS customers) or the customer's tech department if locally hosted.
a. Check to see if there were any server changes
b. Log the exact error that the customer is receiving
4. Field overflow errors or FETCH errors similar to "(FETCH) Column size at rowid nnnnn in table <table_name> has a value exceeding its max length or precision".
a. Have tech run the progress utility to expand the field
b. Determine if this field should be logged as a defect and be adjusted permanently in Agility
c. May need to have the field adjusted through a data fix procedure editor
5. Shadow the user to see exactly how the report is being run and what and when the error occurs.
6. Confirm the problem can be recreated on the customer's system.
7. Try to recreate the problem in the internal development systems and create a defect if the problem can be recreated.
a. If this can be recreated on the customer's system and not in development check to see if the problem was previously reported and has since been fixed in development
b. Determine the type of data that may be causing the problem and set that data up internally to try and recreate
Custom CQ Reports 1. Get the exact name of the report and the sub-directory if one exists.
2. Get an example of what the problem is. This could be a screen print of the error or an example of the printed report. Include the item number, transaction number, customer number that is causing the problem.
3. Determine if the query was previously working and has now stopped working or is this a new query that is being created.
4. Check to see if there were any recent changes to the report for existing reports that have stopped working.
a. To check the last time a query has changed go to the Report Writer language editor and select the "File”, “Open". Then click the "View Detail" icon next to the "New Folder" icon to show the last time the query was updated or saved
b. Keep in mind if the query is a macro(.mf) you will need to check all queries that the macro is running
5. If the query sends report via email and the emails are not being sent.
a. Have the user check to see if the report is in the spam folder
b. Check to see if an email can be sent from a standard Agility Report
c. Get permission to test the macro using the language editor. The language editor will show the steps and errors as the query is being run
6. If the query sends data using sftp
a. Check to see if there have been network address changes for the destination server
b. Check to see if the login credentials changed
AR20883 - How to find common inventory out of balances
Agility
- Inventory
How to find common Inventory Out of Balances (OOB)
Attached document has several steps to take to identify inventory out of balances between the inventory GL and subledger (inventory valuation report).
In order to begin the process you need to know the DATE the OOB occurred and the amount. Each step below is a separate step to research so if you don’t find the answer in step 1, move to step 2, and so on.
A. Look for JE’s in the GL 1. Find out the default GL for inventory GL. Login to the branch and to go System Administration > System Controls > Default System GL accounts. Pull where category = “Inventory – F.G”.
2. Review the GL for any journal entries as users should not be making JE’s into inventory GL account unless we tell them to make a JE to fix an OOB. General Ledger > Inquiries > GL Detail Inquiry
a. Update the “from” posting period/year to span back at least 1 year in the past
b. Posting date from/to should be date span in which the inventory OOB occurred.
c. Click Search to Display results and then double click the Source column to sort by that and journal entries will appear on the top.
B. Run programs for unposted entries 1. Go to General Ledger > Posting Functions > A/R posting to G/L
2. Select the correct branch and posting period for the date the OOB occurred and click OK. An audit report will generate with any pending entries that posting. Looks to see if that amount matched your OOB.
3. If AR posting did not fix, run for General Ledger – Posting Functions – Post Unposted Activity.
4. Select branch, select the posting period for the date, set Original = ALL & Run. An audit report will generate with any pending entries that posting. Looks to see if that amount matched your OOB.
C. Run Inventory Balance Comparison 1. General Ledger > Reports > GL Balancing Reports. Report: Inventory Balance Comparison. This report compares item activity for dates against inventory level changed in the data warehouse. Most OOB’s are found here . Please note that you just check Automated Processing queue to see when the DW update is being run.
2. IF DW is run in the evening (before midnight ), there are the settings you use for the query.
a. Select the branch and posting period/year. The from/to dates are the top are for item activity and must the date range for the OOB. The Date Warehouse Collection Dates must have the “first” date = one day BEFORE the “from” date from above and the “last” date = the “to” date from above
3. IF DW is run in the early morning (after midnight ), there are the settings you use for the query.
a. Select the branch and posting period/year. The from/to dates are the top are for item activity and must the date range for the OOB. The Date Warehouse Collection Dates must have the “first” date = “from” date from above and the “last” date = the “to” date PLUS 1 day.
4. When you get the results of the report, you need to look at item activity so see if you have figure out what happened.
5. COMMON ISSUES:
a. Sundry item with no sales account parameters assigned and item has cost and it’s posting to inventory. Sundry items costs cannot post to inventory as they are not inventory items.
b. Receiving adjustments to PO
c. Direct PO/ SO with no sales account parameters where sale type – direct. Need the inventory account to be “inventory – direct” GL rather than “inventory – F.G” GL.
6. If you see an item with no item code but “difference” listed, this is usually a reman. So look for reman orders completed in that branch on that day. Operations posting to inventory GL or sometimes balancing report output items & qty does not match item activity.
D. Run Inventory Level Comparison 1. General Ledger > Reports > GL Balancing Reports. Report: Inventory Level Comparison
2. Select the branch and run.
3. This report tells you if there are problems with the LEVEL at which quantity is stored.
Item 27500 : the “stocked at” fields indicate that it should not be stocked at tag yet there is inventory at the TAG level.
Item 404XXG2 : the “stocked at” fields indicate that it’s stock at all levels but the qty at Item and Loc level do not equal the quantity as lot, tag and content level. You will need to count item.
Please contact DMSI helpdesk for assistance if you have any data on this report as it required DMSI to do a data fix .
E. Run Inventory Adjustment report 1. Run inventory adjustment report for the branch, date range in questions. Look for any entry that is NOT a location change where there are no GL’s listed under the item code as this indicates that no dollars hit the GL. This may be because the Reason Code that was used has inventory GL as an offset and this will cause inventory OOB.
2. Ex: incorrect inventory adjustment – reason code defined and no journal # listed.
3. EX: correct inventory adjustment – reason code defined and JE# with GL’s listed.
F. Compare Inventory GL postings against Item Activity Viewer 1. You will be working in both the GL detail inquiry screen and item activity viewer.
GL Origin = A/P NONE
GL Origin = A/R IA Type = SO, CM
GL Origin = G/L IA Type = RM-Input, RM-inp-uncomplt, RM-output, RM-outpt-uncomplt
GL Origin = I/A IA Type = IA-Cost Adj, IA-Cost Replace, IA-Qty Adj
GL Origin = P/O IA Type = RV, RV-Cost adj, RV- Qty adj
NONE IA Type = CA (search separate)
2. Go to General Ledger > Inquiries > GL detail inquiry. Type in the inventory GL at the top, and the date range for OOB & select Origin = I/A. Note the amount for “Total Posted”
3. Go to Inventory Control > Queries/Reports > Item Activity Viewer. Select Branch, Select activity date, Options – exclude activity not affecting inventory. Type = select the IA type indicated above (IA-Cost Adj, etc) and look for total under “ext Activity cost”. The GL detail inquiry Total Posted should match Item Activity Ext Activity cost Total
4. Repeat for all GL Origin/IA viewer type combinations.
5. If there is a discrepancy for the type, you will sort and subtotal the item activity viewer for Journal number and then manually reconcile the IA viewer journal with GL inquiry journal amount. If they do not match, this is the activity into which you need to dig further.
AR21033 - Buyer Limits VCQ Report Setup
Agility
- Purchasing
Buyer Limits VCQ Report Setup This report looks at PO’s created on current date and have not yet been printed. Then it compares the total cost on the PO to the buyer limit. If the cost is greater, it will print the PO info on the report .
This report works in conjunction with an action allocation and setting up Buyer limits.
1. Set up Buyer Limits and deny action to print PO’s over Buyer purchasing limits
a. Go to Data Files > Supplier Information > Buyers. Set your buyer limit.
The system restricts the purchase order from being printed if the order total exceeds the limit for the buyer(s) assigned to the non-transfer purchase order. To print the order, the order total must be reduced or a user with permission granted to the 'Print purchase order over buyer purchase limit' security action can print the order.
b. Go to System Administration > Security Administration > Action Allocation
Deny permission to “Print Purchase Order Over Buyer Purchase Limit”
2. Create the VCQ Report
a. Open VCQ Report Writer and switch to language editor
b. Click on File > New Enquiry
c. On the enquiry screen paste in the report below.
d. Save your enquiry. Naming recommendation: buyer_limits
where ( po_header:created_date = todaysdate ) and po_header:printed = 0 list /nodetail/noreporttotals/nobanner/domain="po_header" po_header:system_id po_header:buyer suppname:supplier_code po_detail:ext_cost buyer:per_po_limit po_header:po_idsorted by po_header:system_id po_header:buyer po_header:po_idend of po_header:po_id if total[po_detail:ext_cost] > buyer:per_po_limit then { po_header:system_id/noheading/align=po_header:system_id po_header:buyer/noheading/align=po_header:buyer po_header:po_id/noheading/nocommas/align=po_header:po_id suppname:supplier_code/noheading/align=suppname:supplier_code total[po_detail:ext_cost]/align=po_detail:ext_cost buyer:per_po_limit/noheading/align=buyer:per_po_limit }
Automated Processing Setup 1. Create a new job/queue called Buyer Limits
a) Go to System Administration > Restricted Processing > Automated Processing > Queue Maintenance
b) Click the plus sign on the new job tab and fill out as follows.
c) The Report subfolder name is only needed if you saved the file into a subfolder in the cq reports directory.
d) Set the email address of any users that should receive the Buyer Limits report.
e) Set the report data type to PDF or excel
f) Save the job and create a queue that will run this job once a day or multiple times a day, however you desire. In the example below the job is set up to begin running at 6am CST, then run every two hours and stopping at 9pm CST.
g) Note you can also run this report on demand by placing this report on your dashboard or accessing and running through VCQ Reports to get a listing of PO’s that are over their buyer limits throughout the day without waiting for the normal runtimes to generate the report.
AR21114 - Dispatch Basics / Dispatch Terminology / Dispatch Questions / FAQ
Agility
- Dispatch Processing
Per Agility Help:
The freight dispatch function allows you to manage and coordinate the movement of outside or internal trucks by tying specific items and quantities on a purchase order, supplier return, sales order, sales order shipment, credit memo, or reman work order to a particular dispatch record, which you can print, update as needed, and track through A/P Recon and invoice entry.
By managing material using the dispatch module, you have greater control over the entire dispatch process since you know where the material is always located. In addition, the dispatch function tracks routes, stops, weight and load, allowing you to create the most efficient routes and consolidate freight orders when feasible.
Terminology:
Dispatch (e.g. freight dispatch)
Optional function allowing you to manage the delivery and pick up of orders, the related dispatch documents and freight payables for incoming and outgoing materials by tying specific items and quantities from a transaction to a dispatch record.
The following transaction types can be associated with a dispatch.
•(PO) Purchase order
•(SR) Supplier return
•(SR) Sales order
•(CM) Credit memo
•(RI/RO) Reman input/output
Dispatched transaction
A purchase order, supplier return, sales order, sales order shipment, credit memo or reman work order associated with a dispatch record.
Shipment info record
A means to track shipping information such as carrier ID, transport type and transport number on transactions regardless if you are using the Dispatch module.
Advance Shipping Notice (ASN)
Form used to provide dispatch information about material being shipped to a customer or from a supplier
For Agility sales orders, ASN forms (WMS/EDI) provide dispatch information to trading partners with whom you also trade invoices.
For Agility purchase orders, the ASN number used in mobile receiving corresponds to the dispatch ID assigned in the following situations.
· You dispatch the purchase order for freight purposes
· System auto dispatches purchase order upon processing an e-commerce interface file flagged to create dispatch
· You create a dispatch upon receiving notification from the supplier about the material being
· shipped
For each of these situations, you can then print the PO Check in List and perform mobile receiving by ASN, which displays and accumulates quantities of like items for all purchase orders on the ASN.
Third-party routing
· Appian Logistics Direct Route
· DQ Technologies Order Delivery Tracking System
The optional third-party routing interface allows you to utilize a third-party routing application to automatically calculate and optimize delivery routes for Agility purchase orders, supplier returns, sales orders, sales order shipments and credit memos.
This interface uses the dispatch function to control the data transmitted to the routing application and process data returned from the routing application. This interface utilizes screens within the Sales Orders/Quotes module.
Common Questions/Answers
How can I see which dispatches are not printed?
Answer
Assisted with going through the dispatch viewer, adding the printed search criteria, and sorting the viewer by the printed status. Also assisted in setting up the viewer to be used again in the future by going through the viewer saving options in the upper left portion of the viewer.
Any way to reprint the dispatch once the order is invoiced?
Answer
Once invoiced the only form you can reprint is the invoice
How to create a Dispatch from a Reman?
Answer
-You cannot create a Dispatch from RM entry. You need to open dispatch first, click Add button at the bottom and then add the Reman to it (RI for reman input or RO for reman output and you then need to select the operation so it will pull the items associated with the operation
AR21211 - New User Checklist for System Admins
Agility
- Best Practice
New User setup Checklist article for System Admins This article is intended to help System Admins onboard new employees using Agility. There are helpful articles and videos your employees can review to help learn Agility specific to their job function.
Different videos/article for different business tracks (sales, purchasing, accounting, warehouse, system admin) Sales 1. Articles
a. AR18651 – How to Create a Sales Order
b. AR18634 – Quote Process
c. AR18636 – OrderPad Procedure
d. AR18632 – Stock Status Procedure
e. AR18791 – Sales Order Entry FAQ
f. AR18794 – OrderPad FAQ
g. AR18795 – Stock Status FAQ
h. AR18793 – Cash Receipts FAQ
2. Videos
a. V887 – Welcome to Agility webinar (sales and purchasing)
b. V1832 – SO Entry Overview
c. V1793 – Basic SO Entry
d. V1794 – Intermediate SO Entry
e. V1795 – Advanced SO Entry
f. V1810 – Basic Quote Entry
g. V1820 – OrderPad Overview
h. V1803 – Credit Memo Overview
i. V980 – All About Credit Memos webinar
j. V982 – All About Quotes webinar
Purchasing 1. Articles
a. AR18646 – How to enter a PO
b. AR18647 – How to receive a PO
c. AR18648 – How to Adjust a received PO
d. AR2085 – Price/Discount Import
e. AR20546 – Purchasing and Receiving FAQ
f. AR1821 – Getting Started with Suggested Purchasing (SPOs)
2. Videos
a. V887 – Welcome to Agility webinar (sales and purchasing )
b. V1850 – Purchase Order Process Overview
c. V1851 – Basic PO Entry
d. V1852 – Advanced PO Entry
e. V1854 – Basic PO Receiving
f. V1855 – Advanced PO Receiving
g. V1856 – Basic PO Receiving Adjustments
h. V1857 – Supplier Returns
i. V727 – Inventory Management and Control webinar
j. V869 – SPOs in Action
k. V870 – SPOs Behind the Scenes
l. V871 – Help! Common Troubleshooting in SPOs
m. V850 – ABCs and Usage
Accounting 1. A/R Articles
a. AR679 - Setting up Financial Statements (links to other articles/videos)
b. AR18781 – Cash Application Procedure
c. AR18638 – Credit Memo Entry
d. AR18783 – Release Credit Hold
e. AR335 – AR Print Invoices
f. AR18787 – AR Print Account Statements
g. AR20488 – AR FAQ
h. AR18797 – AR Cash Application FAQ
i. AR18800 – AR Finance Charges FAQ
j. AR18799 – AR Invoice Printing FAQ
2. A/P Articles
a. AR18626 – AP Invoice Entry PO
b. AR18624 – AP Invoice Entry Expense
c. AR18622 – AP Print Checks
d. AR535 – AP Edit Invoice
e. AR655 – AP Recon Write-off, Drop or Adjust
f. AR18600 – AP FAQ
3. G/L Articles
a. AR18643 – GL Manual Journal Entry
b. AR1627 – GL Journal Entry Import
c. AR18776 – GL Bank Recon
d. AR1828 – GL Daily Balancing
e. AR1625 – GL Create GL Accounts
f. AR18788 – GL Manual Journal Entry FAQ
g. AR18789 – GL Bank Recon FAQ
h. AR1001 – GL Daily Balancing FAQ
i. AR1954 – GL Year End FAQ
4. A/R Videos
a. V1128 – Welcome to Agility webinar (Accounting)
b. V1163 – AR Overview
c. V701 – AR and AP Common Issues and Best Practices
d. V1147 – Time for a Good Accounting – AR Basics
e. V1161 – AR Express Cash Application
f. V1158 – AR Cash Application
g. V1159 – AR Printing Invoices
h. V1157 – AR Invoicing – Sales Profitability Report
i. V1155 – AR Invoicing from SO Entry
j. V1164 – AR Invoicing from Staging Status
k. V1153 – AR Cash Batches
l. V1151 – AR Open and Paid Inquiry
m. V1762 – AR Open and Paid Inquiry webinar
5. A/P Videos
a. V1128 – Welcome to Agility webinar (Accounting)
b. V701 – AR and AP Common Issues and Best Practices
c. V899 – AP Overview
d. V900 – Basic AP Invoice Entry
e. V902 – AP Payment Process
f. V903 – AP Check Voiding, Reprinting and Renumbering
g. V904 – AP Recon Overview
h. V905 – AP Recon Window
i. V906 – AP Recon Register
j. V907 – Drop/Adjust AP Recon
k. V1145 – Time for a Good Accounting – AP Basics
l. V1061 – A/P Invoice Entry – Credit Memo and Debit Memo
m. V1062 – A/P Invoice Entry – Entering Multiple Transactions
n. V1001 – A/P Invoice Edit
o. V1002 – A/P One Step Payment
6. G/L Videos
a. V1128 – Welcome to Agility webinar (Accounting)
b. V1058 – General Ledger Overview
c. V966 – GL Integration Points General Setup
d. V967 – GL Integration Points Purchasing
e. V968 – GL Integration Points Sales
f. V969 – GL Integration Points Specialty Specific
g. V672 – SMT 2 General Ledger Setup
h. V976 – General Ledger Structure Definition
i. V979 – General Ledger Accounts
j. V985 – General Ledger Account Groups
k. V997 – GL Categories Definition and Default System GL Accounts
l. V1008 – General Ledger Transaction Flow
m. V1011 – General Ledger Component Processing
n. V1014 – General Ledger Journal Entry Basic
o. V1044 – General Ledger Journal Entry Advanced
p. V1053 – General Ledger Journal Entry Edit
q. V1057 – General Ledger Journal Entry Import
r. V861 – Financial Reporting – Building Custom Financial Reports
s. V1115 – Review of Year End Procedures webinar
Warehouse 1. Articles
a. AR18654 – Basic Two Step Picking
b. AR18784 – Physical Inventory Procedure
c. AR18780 – Inventory Adjustments
d. AR1207 – Item Import
e. AR1699 – Dead Stock Report FAQ
f. AR18782 – Inventory Adjustments FAQ
g. AR20555 – Inventory Control and Physical Inventory FAQ
2. Videos
a. V1132 – Welcome to Agility webinar (Inventory Control)
b. V1814 – Shipping Process Overview
c. V1815 – Order Processing Overview
d. V1816 – Staging Status Overview
e. V1817 – Basic One Step Shipping Process
f. V1818 – Basic Two Step Shipping Process
g. V910 – Building it with Remans webinar
h. V783 – Understanding Physical Inventory in Agility webinar
i. V727 – Inventory Management and Control webinar
System Admins 1. Articles
a. AR20108 - Getting Started as a New System Manager
b. AR1998 How to create a new user on the Wedge
c. AR1366 How to create a new user in Agility
d. AR21955 – How to lock out a former employee
e. AR1617 – How to set up Security Groups
f. AR1614 – How to assign users to Security Groups
g. AR2097 – How to set up User Preferences
h. AR1156 – Common User Preferences
i. AR421 – How to edit Sales Order layouts
j. AR2007 -How to Change or Update User Passwords in the Portal
k. AR20654 -Access local files more easily using upgraded Agility Virtual Channel
l. AR1207 – Item Import
m. AR1594 – Supplier Import
n. AR1606 – Customer Import
o. AR2085 – Price/Discount Import
2. Videos
a. V887 – Welcome to Agility webinar (sales and purchasing)
b. V717 – How Security Works in Agility
c. V893 – Effective use of Audits and Purges webinar
d. V569 – Brief Overview of the Wedge
e. V720 – Searching on the Wedge
f. V699 – The Wedge webinar
g. V757 – Simplify your Life with Automated Processing
h. V744 – Maximize your Day with Viewers and Reports
i. V696 – Utilizing the Power of the Imports webinar
AR22210 - Viewers are like a box of chocolates
Agility
- Viewers
Viewers are like a box of chocolates
"My momma told me, life is like a box of chocolates, you never know what you are going to get."
In Agility Viewers are like a box of chocolates - and we hope this list helps you and your team understand some of the many treats they hold.
Some people want it to happen, other people wish it would happen and others make it happen. Wow - it sure is difficult to see all the open orders for a customer and have a conversation with them about it. Or is it? Or what about the orders that they had invoiced in the past few months? Or finding an order that was sent to a specific job site address so you can see the color of roofing or siding used at the job site? Without a sales order viewer this would all be tough to do. But with the Saved Viewer feature in Sales Orders and Quotes - these are all easy tasks for your sales agents.
V1031-Saved Viewers in Sales Order and OrderPad
Can't Stop This Feeling Can you view a sales order detail message without having to pull up the SO detail line and drill into the item message? Yes you can with the addition of an available column in the SO Viewer and the SO Detail Grid!
V1034-SO Viewer and SO Detail Grid - Item Message Column
I got this Good news, you can get right to the powerful Customer Information window from the sales order viewer - and this segment helps you understand how
V1032-SO Viewer - View Customer Information
One stop shopping Switch between summary and detail view in a viewer for more information at your fingertips without having to drill into the items or transactions
V1033-Viewers - switch between views
Create a new Sales Order from a Viewer - Get out! Ever wondered how you might help your sales agents focus on selling your opportunity stock or promotional items? Creating an inventory viewer that shows the opportunity stock or promotional items you have in a branch fits that bill. From there, in a simple step, the sales agent can create a sales order for the items the customer wants to buy.
V1025-Inventory Viewer - Process Selection - Create New Sales Order
Help me help you As a sales agent, how do I help update the open quotes I have to current pricing or to be more competitive? You can use a sales order viewer that includes quotes (or sales orders) and choose the reprice option. This segment shows you how!
V1030-SO Viewer - Repricing a Quote (or Sales Order)
I just want to buy 8 hot dogs and the 8 hot dog buns to go with them. I am removing the superfluous buns. Unsure of the easiest way to create a fill in purchase order? Find out how to use this inventory viewer to see your position on a list of items and then select the items you need to buy and easily create a new purchase order for the selected material.
V1023-Inventory Viewer - Process Selection - Create New PO
Hey Joe - When do we expect that material in? As a buyer, what do you do when you need to override the expected ship or receipt date for a number of open purchase orders? Pull them up one by one? Or did you know you can use a handy open Purchase Order Viewer to change the date for a number of PO detail lines?
V1028-PO Viewer - How to Override Expected Receipt Date
Bazinga! Viewers are awesome for finding out information about items or transactions! But did you know you can go well beyond just the information about the transaction or the item by exploring other columns that can be included in the viewer? Watch this segment for some examples of doing just that...
V1027-Viewers - Not just for transactional information anymore
Refresh isn't just for eyedrops anymore Ugh, I hate having to close my Viewer results to see the new or changed results. This segment shows you an easier way to see refreshed results in your viewer.
V1029-Refresh in Viewers
How do I find find? Isn't Ctrl-F or Find in Microsoft products like Excel and Word awesome? Did you know that Agility has a very similar Find feature in the Viewers? Watch this segment to learn how to use 'the binoculars'.
V1026-Viewers - How to "Find" something inside your viewer results
But I would like the pie heated with the ice cream on the side... Getting what you want the way you want it - is not just for Sally anymore... But do I really have to close the viewer results if I need to change the criteria or the columns that are showing in the viewer results? Did you know the answer is no? This segment will show you how to change criteria from the viewer results window.
V1024-Viewers - Change Criteria from Viewer Results
AR22516 - How to create customer Quicklists
Agility
- System Administration
AR22521 - Using Installed Sales
Agility
- Installed Sales
This article details how to use and navigate within Agility Installed Sales. Please DOWNLOAD the attachment for screen shots and a complete review of the module.
As of version 544, Installed Sales can be accessed via core Agility or via a standalone web browser. Note you MUST contact Support@dmsi.com to have the module activated before you will have access.
From within core Agility, you can find it at Sales Orders/Quotes > Installed Sales. Otherwise, from any computer or tablet (iOS, Android), go to agility.dmsi.com and login with your Agility credentials with the proper Org ID appended to your login. This is something you should have been notified of during implementation/setup, so please contact Agility Support if you do not know it.
If your normal Agility login is:
Login: jsmith PW: 123
You would use this to log in to Installed Sales for your company at agility.dmsi.com
Login: jsmith.orgid PW: 123
AR22589 - Cyberquery Shortcut keys
Agility
- Cyberquery
Cyberquery Shortcut Keys
CQW shortcut keys Action Details Key Clone Clone this Cyberquery window. Launches a new instance of CQW with the query or macro from the current window loaded as an Untitled document. CTRL-SHIFT-C Find Find text CTRL-F Find next Find next occurrence of text F3 or down arrow keyFind previous Find previous occurrence of text Shift-F3 or up arrow key Find and replace (Windows)Find and replace text CTRL-H Find and replace (HTML)Find and replace text CTRL-ALT-H Help Displays help about the currently selected pane F1 New query Create a new query CTRL-N Open query Open an existing query CTRL-O Open next file Opens the next file from the latest Open dialog, including any filtering CTRL-SHIFT-n Open previous file Open the previous file from the latest Open dialog, including any filtering CTRL-SHIFT-p Paste as new macro Pastes a macro from the Windows clipboard into CQW CTRL-SHIFT-V Point-and-click help Displays help on the next item that you click SHIFT-F1 Print report Print the report CTRL-P Quick run Refresh the report display with cached data F5 Run Refresh the report display with data from the server F6 Run In version 8.21-1A and later: When the Record Selection dialog box is open pressing F6 refreshes the report display with data from the server and closes the dialog box. F6 Run In version 8.21-1A and later: When the Record Selection dialog box is open pressing Shift-F6 refreshes the report display with data from the server and leaves the dialog box open. Shift-F6 Save query Save the query CTRL-S Switch Switch from the Language Editor to the Report Editor SHIFT-ALT-R Switch Switch from the Report Editor to the Language Editor SHIFT-ALT-L
Report Editor and Visual Editor Shortcut Key
The following shortcut key can be used with the report editor or the visual editor.
Report editor and visual editor shortcut key Action Details Key Switch Switch focus between panes TAB
Report Wizard Shortcut Keys
The following shortcut keys can be used with the Report Wizard (on its first page).
Report Wizard shortcut keys Action Details Key Display the Open dialog box Open a query CTRL-O Paste query Paste query from Windows clipboard into CQW CTRL-V Paste macro Paste macro from Windows clipboard into CQW CTRL-SHIFT-V
Report Pane Shortcut Keys
The following shortcut keys can be used with the report editor , visual editor and language editor but only when the report pane is selected.
Report pane shortcut keys Action Details Key Clear Clears the current selection ESC Find Find text CTRL-F Find and replace (Windows)Find and replace text CTRL-H Find and replace (HTML)Find and replace text CTRL-ALT-H Maximize report viewer Pressing this once closes the other panes, and makes the report pane as large as possible. Pressing again returns the report pane to its original size.
F8 or SPACEBAR
Options Pane Shortcut Keys
The following shortcut keys can be used in the Options pane.
Options pane shortcut keys Action Details Key Expand Expands the tree for the currently selected table + (numeric keypad)Expand everything Expands everything under the current selection * (numeric keypad)Collapse Collapses the tree for the currently selected table - (numeric keypad)Collapse/Go to Parent Collapses the current selection if expanded otherwise goes to the parent LEFT ARROW Expand/Go to first child Expands the current selection if it is not expanded, otherwise goes to the first child
Editing Shortcut Keys
The following table shows the Windows shortcut keys that can be used when editing text in dialog boxes and the language editor.
Editing shortcut keys Action Details Key Copy Copies selected text to clipboard CTRL-C Cut Removes selected text and places on clipboard CTRL-X Delete Delete the character to the right of the cursor or the selected text DELETE Delete line Deletes the current line CTRL-U Delete to end of line Deletes from the cursor to end of line CTRL-K Delete word right Deletes from the cursor to the end of the current word CTRL-DELETE Delete word left Deletes from the cursor to the start of the current word CTRL-BACKSPACE Insert/Over-write Toggles between over-write and insert mode INSERT Move down Moves the cursor down one line DOWN ARROW Move left (character) Moves cursor to the left one character at a time LEFT ARROW Move left word Moves the cursor to the left one word at a time CTRL-LEFT ARROW Move right (character) Moves cursor to the right one character at a time RIGHT ARROW Move right (word) Moves the cursor to the right one word at a time CTRL-RIGHT ARROW Move to end (line) Moves the cursor to the end of the line END Move to end (text) Moves the cursor to the end of the text CTRL-END Move to start (line) Moves the cursor to the beginning of the line HOME Move to start (text) Moves the cursor to the beginning of the text CTRL-HOME Move up Moves the cursor up one line UP ARROW Paste Pastes current clipboard contents CTRL-V Redo Last undone action is redone CTRL-Y Select Selects all text in current pane or dialog box CTRL-A Select left (character) Selects text to the left one character at a time SHIFT -LEFT ARROW Select left (word) Selects text from the cursor to the left one word at a time SHIFT-CTRL-LEFT ARROW Select right (character) Selects text to the right one character at a time SHIFT-RIGHT ARROW Select right (word) Selects text from the cursor to the right one word at a time SHIFT-CTRL-RIGHT ARROW Select to start (line) Selects text from the cursor to the beginning of the line SHIFT-HOME Select to start (text) Selects text from the cursor to the beginning of the text SHIFT-CTRL-HOME Select to end (line) Selects text from the cursor to the end of the line SHIFT-END Select to end (text) Selects text from the cursor to the end of the text SHIFT-CTRL-END Select down Selects text from the cursor, down one line at a time CTRL-DOWN ARROW Select up Selects text from the cursor up, one line at a time CTRL-UP ARROW Undo Last action is undone CTRL-Z
AR22597 - Order Entry Branch Option - Agility Call Center Functionality
Agility
- Sales Orders
Scenario : A company is planning to build/have a centralized location that fulfils orders for other branch locations of the same company for its customers. This “Call Center” environment needs to ensure that they are inputting sales orders for the correct branch location so that there is little-to-no error in processing for its customers. Does Agility have functionality to ensure that the centralized branch location will create transactions inside of the proper branch?
Answer : Agility has a flag/parameter we can set that would be beneficial.
This is a feature we can implement that will prompt the Sales Order creator to "select a branch" at order entry. This allows for efficiency in creating the order in the proper branch and mitigates any mistakes along the way. This is the “Order Entry Branch Option” on the Customer Ship-to record > Default Flags tab.
There are two things we need to set inside of Agility to turn this feature "on": 1) Inside of each customer ship to record (data files > customer information > customers) there is a field that we can set that will say "Order entry branch option" in the "Default Flags" tab.
The options there are either Current Branch, Default Branch, or Prompt for Branch
-
You will need to update any customer's ship-to
record that is needed for this field.
-
A setting of "Prompt for Branch" will
be the setting to prompt the sales order creator to select the branch at Order
entry every time.
-
This can be updated via a customer import
("Order entry Branch option" column in Ship-to default flags
section)
-
If you need assistance with this, please let us
know at support@dmsi.com and
we can assist!
2) Once
all ship-to records are updated, go to System Admin > Module controls >
Sales order parameters.
Here, go
to the second tab (SO/Quote/CM 2) and check the box of "Use order entry
branch option on ship-to " so that we can utilize the customer’s ship-to
settings properly.
After these settings are both enacted for the call center’s
branch, then moving forward will look like this:
-
Whenever a user at the “Centralized location
Call Center” branch creates a sales order in Agility and inputs a customer
ship-to from the system, there will be a prompt that forces the user to Select
the Branch for the sales order to go into.
·
If there are ever questions, please let us know at
support@dmsi.com
AR22783 - How to create an RMA in PartnerView
Agility
- PartnerView
How to create an RMA in PartnerView This article details the setup and general flow of creating a return request in PartnerView, Approve/Deny that request, and what the PartnerView user will see. This functionality will be complete in V549.
Set up Agility Allow RMA Creation 1. In Agility, access System Administration > Module Controls > PartnerView Parameters > Settings tab 2. Enable the Allow RMA Creation field and fill in the Number of allowed days to create RMA field (default is 30 days). 3. Select Save.
Allow RMA in PartnerView 1. Go to, Data Files> Item Information>Items>Branch Settings tab 2. Enable the “Allow RMA in PartnerView” to allows return creation from PartnerView. This holds true regardless if the order was created in PartnerView or Agility. One exception to this, items that normally create non-stock items or codes (i.e. BOM Parents) are not allowed to be returned with this method. 3. Click Save to update. 4. When updating in bulk Item mass update, Item Import, and Item cross branch update can be used
Reason Code 1. Data Files>Lookup Codes>Reason codes 2. For Type of “Credit memo item” PartnerView reason is visible 3. Select “Allow in PartnerView” for this reason code to show up as available for use within PartnerView. 4. Enter a “PartnerView Reason” if desired. This is the Reason seen by customers on PartnerView when submitting a return request. If blank, the Reason will display within PartnerView. 5. Go to System Administration>Module Controls>Sales Order Parameters>SO/Quote/CM 2 tab if you would like to require a reason code to be entered on all returns.
Security 1. System administration>Security Administration>Action Allocation 2. Product = Agility 3. Grant Agility user the ability to “Approve/Deny PartnerView Credit Memos” will allow that user to update a credit memo from hold to approved or denied. 4. Product = PartnerView 5. Grant user “Submit Returns” allows the ability to create a return request within PartnerView.
Notification 1. System Administration>Restricted Processing>Notification Maintenance 2. Event>PartnerView Order Created 3. Select either “send for all records” or Tran Criteria tab select “Credit memo created’. This can be added to existing notifications or made exclusively for this singular action. A system generated notice to the PartnerView customer is created any time a credit memo with the source of PartnerView is changed to Approved or Denied. This message is not customizable. More details provided later.
Subject line: ‘Credit Memo <ID> - <Status>’ body: Your Return request has been Approved/Denied. Please see PartnerView for more details under Credit Memo ID _______. Branch _______ Customer ID ________PartnerView Return Request Invoices Tab 1. Customer login to your PartnerView website 2. Click Invoices tab 3. Select date range and/or enter the Invoice ID 4. Press “Search”
Up to 2 years of invoices can be displayed regardless of source. A new Actions column has been added with an icon to start a Return request. If no items are allowed to be returned, the return date has past, the user does not have Security allowed, or the Invoice is from a Credit Memo: this icon is hidden.
Create a Return Request 1. Click Return Icon 2. Enter a Quantity you wish to return (limited by line order quantity)
All items on that invoice are organized in the sequence number on the original Sales Order. So, if you have multiple lines of identical items it will display multiple times. The items that are not able to be returned are marked with a yellow exclamation point and hover text. Parent/child items display a little different, with Reason and Message fields on the parent line. Dimensional wood items will show as a parent item with ordered dimensions under it. However, sheet good items have separate lines on the Sales Order and display within PartnerView as separate lines by dimension. 3. Add Reason and/or Message now if desired (optional on this screen) 4. After you have entered at least some Qty to be returned, you can click Review.Review Screen All items with 0 qty will be removed, but further edits can still be made. To remove a line, you must go back to the create screen and zero out the Qty. Estimated totals are calculated based on the original price, and do not consider quantity breaks or change in prices. Here we also enforce the Reason if one is required. This will display a drop-down of the PartnerView reason or Agility reason based on your settings. Selecting “Back to Create RMA” will hold your existing Return Qty, Reason, and Message but will not save after log-out. 1. If Reason is required and not yet filled in, click on the carrot for each line and select a reason for the return. 2. Click Release.Release Upon release, a pop-up will appear letting you know you will receive an email when the return has been approved. You will need to go to the Credit Memo tab to review the new request. 1. Click ok, and the customer can proceed to a new order, log out, or check on that new request for return.PartnerView Credit Memo 1. Click on the “Credit Memo” 2. Select “Search” to bring up all credit memos for the past 30 days. When a credit memo is pending or denied, the RMA Acknowledgement form is not available. When approved, the Acknowledgement is seen, and then becomes the RMA once invoiced.Agility Approval/Deny Process Now that the return request has been made by the PartnerView user, it is up to the Agility personnel to view that request and either deny the request, accept as credit memo without a return, or accept as a return of materials.
Credit Memo Entry 1. Sales Orders/Quotes>Credit Memo Entry 2. Type in the CM id and press Enter/tab on your keyboard. 3. Update to the shipping information now would be advised.
The Status of RMA and Approval status of Hold can be seen at the top. 4a. At this time, you can also un-select the RMA flag and press save to change this to a Credit Memo and give the customer credit without taking the material back. 4b. Click on the icon next to Approval Status to approve/deny the returnApproval Screen If your security has been restricted you may still click the icon, but your options will be greyed out to prevent any change. 1. To Approve, update the approval status. 2. To Deny, update the approval status to Denied. When Denied the denial notes are available for use. 3. Click Apply and the status will update and save. 4. An email will get sent to the PartnerView user that created the request.SO Viewer If you need to update multiple requests at once you can perform this from the Sales Order Viewer. 1. Sales Orders/Quotes>Viewers> SO Viewer 2. Select other criteria you wish to sort by like Branch or Customer 3. Select order criteria Order Criteria include Credit memos with approval status. If you select “Hold” only requests on hold will be seen. EDI also uses these approval status’Source tab If desired, the Source tab lets you filter by PartnerView to filter out EDI orders. You will not be able to mass update both types at one time. This does default to all source types.Process selection Once the results are populated for your viewer. 1. Select individual or multi-select records to update. 2. Use the Process selection at the bottom: PartnerView credit memo approval/denial 3. Run Process. Approval Screen Similar to the single Credit Memo update, the Credit Memo Approval/Denial window opens for updates to all selected credit memos. 1. Select a status, and if denial notes are needed. 2. Click Apply. 3. An email will get sent to each PartnerView user that created the return request.Back on PartnerView the credit memo RMA status is no longer pending, and the RMA Acknowledgement is available for the customer to download and print.
AR22800 - How to find COGS Out of Balance (OOB)
Agility
- General Ledger
How to find COGS Out of Balance (OOB) In order to begin the process you need to know the DATE the OOB occurred and the amount. Each step below is a separate step to research so if you don’t find the answer in step 1, move to step 2, and so on. A. Confirm that GL recon is pulling the necessary COGS GL accounts1. Confirm that COGS GL’s are setup with a GL Recon category of COGS assigned. Go to General Ledger > Reports > G/L Accounts Listing Report. Set the “Include Account Types” field = EX – Expense
2. Review the list and confirm that all COGS accounts are marked with GL Recon Category = COGS. Also confirm that any GL account with the category are in fact COGS accounts.
Keep this report available as you work through some of the other steps.
B. Look for JE’s in the COGS G/L Account1. Review the GL for any journal entries as users should not be making JE’s into COGS GL account unless we tell them to make a JE to fix an OOB. General Ledger > Inquiries > GL Detail Inquiry
a. Update the “from” posting period/year to span back at least 2 years or more in the past
b. Posting date from/to should be date span in which the inventory OOB occurred.
c. Click Search to display results and then double click the Source column to sort by that and journal entries will appear on the top.
C. Confirm that COGS GL only has posting with source of A/R Inv 1. Review the GL for any posting to the COGS GL and confirm that all entries have a source equal to “A/R Inv”. Go to General Ledger > Inquiries > GL Detail Inquiry
a. Select the posting period in which the out of balance occurred
b. Posting date from/to should be date span in which the inventory OOB occurred.
D. Run programs for unposted entries1. Go to General Ledger > Posting Functions > A/R posting to G/L
2. Select the correct branch and posting period for the date the OOB occurred and click OK. An audit report will generate with any pending entries that posting. Looks to see if that amount matched your OOB.
3. If AR posting did not fix, run for General Ledger > Posting Functions > Post Unposted Activity.
4. Select branch, select the posting period for the date, set Original = ALL & Run. An audit report will generate with any pending entries that posted. Look to see if that amount matched your OOB.
E. Run AR Commission Viewer to find Order Costs and confirm setup 1. Go to Accounts Receivable > Commission Viewer
2. Select the branch in which the out of balance occurred
3. Select sales agent position 1 for all sales agents and all other positions to none as this will prevent you from seeing the same data twice if you have more than one sales agent typically assigned to your Sales Orders.
4. Enter the invoice date range for when the out of balance occurred
5. Select the column display indicated in the screenshot and sort by “Cost Type”
6. If the value of your COGS out of balance is the value of a header cost, you will need to look at the Order Cost setup. Go to Data Files > Charges and Costs > Order Costs.
a. The G/L debit should be pointing to your COGS account
b. The G/L credit account should not be going to COGS account
c. The credit and debit accounts should not be the same.
F. Review Sales Account Parameters for Transfer sale types 1. Go to Data Files > Sales Order Settings > Sales Account Parameters
2. Pull up the parameters for your transfer sale type.
a. If you transfer material at cost, then your “cost-of goods” section should point to a branch transfer clearing account
b. If you invoice your branches and create A/R and A/P records, you should have a special transfer COGS account that is isolated to transfer sales as transfer sale types are excluded from COGS reporting in Sales Analysis and other sales reports.
AR22801 - How to find SALES Out of Balances (OOB)
Agility
- General Ledger
How to find Sales Out of Balance (OOB) In order to begin the process, you need to know the DATE the OOB occurred and the amount. Each step below is a separate step to research so if you don’t find the answer in step 1, move to step 2, and so on. A. Confirm that GL recon is pulling the necessary SALES GL accounts1. Confirm that SALES GL’s are setup with a GL Recon category of SALES assigned. Go to General Ledger > Reports > G/L Accounts Listing Report. Set the “Include Account Types” field = IC – Income
2. Review the list and confirm that all SALES accounts are marked with GL Recon Category = SALES. Also confirm that any GL account with the category are in fact SALES accounts.
Keep this report available as you work through some of the other steps.
B. Look for JE’s in the SALES G/L Account1. Review the GL for any journal entries as users should not be making JE’s into SALES GL account unless we tell them to make a JE to fix an OOB. General Ledger > Inquiries > GL Detail Inquiry
a. Update the “from” posting period/year to span back at least 2 years or more in the past
b. Posting date from/to should be date span in which the SALES OOB occurred.
c. Click Search to display results and then update the Sort by Source and journal entries will appear on the top.
C. Confirm that SALES GL only has posting with source of A/R Inv 1. Review the GL for any posting to the SALES GL and confirm that all entries have a source equal to “A/R Inv”. Go to General Ledger > Inquiries > GL Detail Inquiry
a. Select the posting period in which the out of balance occurred
b. Posting date from/to should be date span in which the Sales OOB occurred.
D. Run programs for unposted entries1. Go to General Ledger > Posting Functions > A/R posting to G/L
2. Select the correct branch and posting period for the date the OOB occurred and click OK. An audit report will generate with any pending entries that posting. Looks to see if that amount matched your OOB.
3. If AR posting did not fix, run for General Ledger > Posting Functions > Post Unposted Activity.
4. Select branch, select the posting period for the date, set Original = ALL & Run. An audit report will generate with any pending entries that posted. Look to see if that amount matched your OOB.
E. Run AR Commission Viewer to find Customer Charges and confirm setupOn you GL Recon report, charges set to effect GM and setup to post SALES GL, the value will be contained within SALES GL value and SALES will stay in balance on GL Recon. If charges are affecting GM are NOT set to affect a SALES GL, the value of the charge will display in a separate column than normal sales. It may appear as if SALES is out of balance but the difference should match the amount displaying in the Charges/Cost GM column.
1. Go to Accounts Receivable > Commission Viewer
2. Select the branch in which the out of balance occurred
3. Select sales agent position 1 for all sales agents and all other positions to none as this will prevent you from seeing the same data twice if you have more than one sales agent typically assigned to your Sales Orders.
4. Enter the invoice date range for when the out of balance occurred
5. Select the column display indicated in the screenshot and sort by “Charge Type”
6. If the value of your Sales is out of balance by the value of a charge, you will need to look at the Customer Charges setup. Go to Data Files > Charges and Costs > Customer Charges. Customer charges affecting inventory should be set to post to SALES
F. Review Sales Account Parameters for Transfer sale types Please note that this step only applies if you invoice your own branches for material transfers, creating A/R Invoice and A/P accruals.
1. Go to Data Files > Sales Order Settings > Sales Account Parameters
2. Pull up the parameters for your transfer sale type.
a. If you invoice your branches and create A/R and A/P records, you should have a special transfer SALES account that is isolated to transfer sales as transfer sale types are excluded from SALES reporting in Sales Analysis and other sales reports.
AR22855 - Cyberquery (CQ) Sample: Table Sharing for All Branches
Agility
- Cyberquery Samples
AR22947 - How to implement receiving via ASNs with WMS
Agility
- WMS
If you use WMS, you can use Dispatch Entry to send an Advance Shipping Notice (ASN) to WMS. You can then receive material in WMS against the ASN ID, and WMS will load the receiving details into Agility.
This document covers the following topics:
1. The setup which needs to be done in Agility to use ASNs with WMS.
2. Creating a dispatch in Agility and sending it to WMS.
3. Updating a dispatch and sending the update in WMS.
4. Receiving an ASN in the WMS.
Most information in this article is derived from the Agility Help entry for ASN Download .
Data Files > Supplier Information > Carrier Information: Define a carrier as an ASN Carrier . System Administration > Module Controls > WMS Parameters: On the Purchase Order tab, save the ASN carrier ID and default ship-from.
When you receive notice of a purchase order shipment from a supplier, create a dispatch for the purchase order items which are shipping.
You can create the dispatch from the purchase order, from a Purchasing > Viewers > PO Viewer, or from Dispatch > Dispatch Entry.
From Purchasing > Purchase Order Entry , open a PO and click Maintain dispatch records . At Purchasing > Viewers > PO Viewer , after running a PO viewer: 1. Select an open PO in the viewer
2. Under Process selection , choose “View/Create Dispatch”
3. Click Run Process .
At Dispatch Entry, click Create new dispatch . If you’ve saved an ASN carrier ID and ship-from in WMS Parameters and are creating a dispatch from Purchase Order Entry or the PO Viewer , Agility creates the dispatch with the ASN carrier ID and ship-from in WMS Parameters , and the PO for which you created the dispatch. If you create the dispatch from Dispatch Entry , you will need to add the ASN carrier ID and ship-from.
Once you’ve created and saved the dispatch, use Send to WMS to send the entire dispatch to WMS as an AS transaction.
If you use EDI, when you receive an 856 from the supplier, Agility automatically creates the dispatch, but you will still need to manually send it to the WMS.
Additional Notes
Purchase order transactions and details are the only transactions Agility can send to WMS as ASNs. If the purchase order header or details don’t have an expect date, Agility uses today’s date as the expect date. Send to WMS sends the entire dispatch to WMS.If you update a purchase order, Agility sends updated PO records to WMS, but does not send an updated ASN to WMS (see next topic).
If you’ve updated a purchase order, you will need to update the dispatch and send it to the WMS again. To send an updated ASN to WMS:
1. Open the dispatch.
2. In the dispatch details, select the PO which has been updated, and click the Synchronize to SR/PO/Receiving button.
3. When Synchronize to PO/Receiving opens, select PO Details and click OK .
4. Repeat steps 2 and 3 for each PO on the dispatch which has been updated.
5. Click Send to WMS to send the entire ASN to WMS.
This example illustrates the process for receiving an ASN in DMSi’s test system. Your processes may vary. If you are not able to receive an ASN in WMS, please contact the Majure Data support team at Epicor for assistance.
1. Enter RC to select the Receiving operation.
2. Enter a receiving type of RA (Receive ASN).
3. Enter the ASN (dispatch) ID.
4. Enter the stock code.
5. Enter “y” to confirm the stock code selection.
6. Enter the quantity being received.
7. Scan a new unit or cart number.
8. Scan the storage location or cart number.
9. Repeat steps 4-8 for each item on this ASN.
10. When you have finished with this ASN, enter F1.
11. Enter an OC to finish receiving this ASN.
12. If you’ve fully received the ASN, enter Y. When the ASN has been fully received, Agility closes the PO and the dispatch/ASN.
13. WMS asks you to enter the next ASN ID. If you have more ASNs to receive, repeat steps 3-12 until all ASNs have been received.
AR23058 - How to Set up SO and CM reason codes
Agility
- Sales Orders
Setup · The first place to go for set up is SO Parameters.
System Administration > Module Controls > Sales Order Parameters
· On the SO/Quote/CM 2 tab, select the desired value for the field “Reason code when Canceling SO/CM”. There are multiple options depending on how you want to prompt:
o Do Not Prompt – This is the default and does not prompt for a reason.
o Prompt and do not require – displays the prompt but does not require a reason to be selected.
o Require reason code only – displays the prompt and requires a reason code, but does not require a comment.
o Require reason code and comment – displays the prompt and requires both a reason code and a comment.
· The second part of the setup that needs to be done is to set up the reason codes. Data Files > Lookup Codes > Reason Codes
· There are 2 new types of Reason codes that can now be set up. Those are:
o Canceled Sales Order
o Canceled Credit Memo
· When setting up these new reason codes, the only relevant settings are: Type, Reason, and Available for Use. You must independently set up codes for use in SO’s and CM’s.
Canceling an order with the SO Parameter set to Prompt. · Like before you just need to cancel the order.
· You will get this prompt when canceling the order. You can select the reason code and type in a comment describing why the order is being canceled.
o Red Text shows required fields on the SO Parameter. If not required, text shows black.
· If you go back into the Canceled SO, you will now see an icon next to the Status.
· Selecting that icon will show you the date the transaction was canceled, the user that canceled it, and the reason code and comment if they were used.
· Additionally, columns for Cancel Comment and Cancel Reason Code have been added to the SO Viewer so you can add those and see the reason reasons from multiple canceled orders at the same time through the viewer.
AR23123 - How to find A/R Trade Out of Balance (OOB)
Agility
- A/R
How to find A/R Trade Out of Balance (OOB)
In order to begin the process, you need to know the DATE the OOB occurred and the amount. A/R OOB occurs when the A/R Trade G/L account balance does not equal the A/R Aged Trail Balance report total for the “Open Amt” column. Each step below is a separate step to research so if you don’t find the answer in step 1, move to step 2, and so on. This documents helps you identify the issue but you may still need to contact DMSI support for research and resolution.
A.
Confirm that G/L Recon is pulling the necessary A/R Trade GL accounts
1.
Confirm that A/R Trade G/L accounts are setup with a G/L Recon category of A/R Trade assigned. Go to General Ledger > Reports > G/L Accounts Listing Report. Set the “Include Account Types” field = AS – Asset
2.
Review the list and confirm that all A/R accounts are marked with G/L Recon Category = A/R Trade. Also confirm that any G/L accounts with the category are in fact A/R Trade accounts.
Keep this report available as you work through some of the other steps.
B.
Run programs for unposted entries
1.
Go to General Ledger > Posting Functions > A/R posting to G/L
2.
Select the correct branch and posting period and posting year for the date the OOB occurred and click OK. An audit report will generate with any pending entries that posted. Looks to see if that amount matched your OOB.
3.
If the A/R posting program results in no postings then run for General Ledger > Posting Functions > Post Unposted Activity.
4.
Select branch, select the posting period for the date, set Original = ALL & Run. An audit report will generate with any pending entries that posted. Review to see if that amount matched your OOB.
C.
Look for JE’s in the A/R Trade G/L Account
1.
Review the G/L for any journal entries as users should not be making JE’s into A/R Trade G/L account unless we tell them to make a JE to fix an OOB.
2.
General Ledger > Inquiries > G/L Detail Inquiry
a.
Update the “from” posting period/year to span back at least 2 years or more in the past
b.
Posting date from/to should be date span in which the A/R Trade OOB occurred.
c.
Click Search to display results and then update the Sort by to Source and journal entries will appear on the top.
D.
Confirm there are only postings to A/R Trade where source = A/R
A/R Trade is one of those accounts that can have entries from A/R
1.
Go to General Ledger > Inquiries > G/L Detail Inquiry
a.
Select the posting period in which the out of balance occurred
b.
Posting date from/to should be date span in which the A/R Trade OOB occurred.
c.
Click Search to display results and Sort by Source. Scan the entries for anything other than A/R xxxx
E.
Confirm offset GL posting for AR entries
Based on the date your A/R Trade went out of balance, pull the A/R – G/L Detail Report for that branch and the activity on that date. You will be reviewing the report to confirm that the offset GL’s listed are NOT A/R Trade G/L account. If you see offset equal to A/R Trade G/L account then that means both the DR and the CR posted to A/R Trade and this would be the reason for your out of balance. You will need to do a journal entry to correct.
1.
Go to Accounts Receivable > Reports > A/R G/L Detail Reports
2.
Select the branch
3.
Set Report type = Detail
4.
Set Activity date for date of OOB
5.
Select appropriate Posting Year
6.
Select appropriate Posting period and RUN
F.
Search A/R Aged Trail Balance Report for OOB value
In some cases we can find the offending records via search of A/R Aged Trial Balance.
1.
Go to Accounts Receivable > Reports > A/R Aged Trial Balance
2.
On the Select Criteria tab, select the appropriate branch.
3.
On the Report Options tab:
a.
Select Report Type = Summary and detail report.
b.
Sort & Subtotal = Customer Name or Customer ID
c.
Run
d.
Look at top of report for any Invoices/CM without a customer name/cust ID.
e.
At the top left of the cyberquery window, select Edit then Find…
f.
The “find” will appear at the bottom left of the window, key in exact amount of OOB variance and click Next – it will highlight the amount found on the report.
G.
Run query on AR records created via Open Item Entry
Usually during Go Live or an acquisition, people may create AR records via conversion or manually via Open Item Edit. None of these actions create an entry to the General Ledger; they only create the open AR record. This query will aid you in identifying any AR records create via Open Item Entry as this may be the cause of the OOB.
1.
Go to Report Writer – VCQ Report Writer
If you get the Cyberquery Wizard window, click Cancel button
2.
Click the Keyboard icon at the top center of the screen.
3.
Paste the text from step 4 into the “enquiry” section of the report writer screen and click the running man icon to run the report. Search for date/amount of OOB. You will need to create JE between A/R Trade and offset G/L account (probably sales/converted sales GL).
4.
TEXT for query
viewpoint native;
where
aropen:open_item_entry =
1
and aropen:open_amt <>
0
list/duplicates/domain="aropen"
aropen:customer_code
aropen:created_date
aropen:tran_id
aropen:ref_type
aropen:ref_num
aropen:open_flag
aropen:open_amt
aropen:open_item_entry
sorted by
aropen:Created_date
aropen:open_item_entry
aropen:open_amt
AR23290 - Billtrust Implementation Overview
Agility
- Billtrust
This document describes how Agility and Billtrust work together, and the steps which need to be taken in Agility to use the Billtrust interface. If you are interested in learning more about Agility’s Billtrust interface, please contact a DMSi Productivity Solutions consultant to ensure that you have the tools and licensing needed to use Agility’s Billtrust interface, and to discuss how the Billtrust interface interacts with other DMSi products.
How Agility’s Billtrust interface works Agility’s Billtrust interface uses the following steps to generate XML files containing invoice and statement data and send these files to Billtrust.
1. An Agility user or Automated Processing initiates a process which generates XML files (invoices one or more orders or uses Accounts Receivable > Open Items > Print Account Statements with Process via Billtrust set to generate one or more statements).
2. Agility creates an XML file for each invoice or statement, and stores them in the XML_OUT_DATA table. These files display in E-Commerce > Log Maintenance with a status of Generated .
3. An Automated Processing queue which transmits invoices and/or statements to Billtrust runs. This process sends all files with a status of Generated to the target address saved in System Administration > Restricted Processing > File Transfer Maintenance (record type Billtrust Invoice or Billtrust Statement ).
4. Agility sends the Processing Activity Log to specified users via the E-Commerce Processing Activity notification, if one has been created at System Administration > Restricted Processing > Notification Maintenance (optional).
5. Agility changes the transmitted files’ status from Generated to Sent in E-Commerce > Log Maintenance .
Billtrust then delivers invoices and statements to your customers using the forms you’ve designed.
Records which Agility does not send to Billtrust Agility’s Billtrust interface sends all invoices and statements to Billtrust for processing, with the following exceptions:
· EDI invoices.
· Finance charge invoices for EDI customers.
· Invoices for the POS cash customer defined in System Administration > Module Controls > Branch Parameters .
· Invoices for the shipping branch of a branch transfer.
· Contract billing adjustments
· Charge or cost adjustments.
DMSi use only As of v602, the Billtrust Transmission process is allowed to use between 22 and 30 async server connections. This value is derived from the default value of 20 connections set inside code plus the value in the maxasynchconnectionserver tag (default = 2), up to a value of 10. If the tag is missing or blank or contains a value greater than 10, the additional number of connections is set to 4. The number of connections to be used by the process upon each run is dependent upon the number of records to be sent to Billtrust as each 500 records will use a separate connection up to the max connections based on configuration.
To ensure there are enough connections available to service this process, when a customer moves forward with Billtrust, the request for a review of the maximum connections available for that customer's PAS instance should also be done. The configuration for each customer's PAS instance contains limits that supersede the limits imposed in the code noted above. Engineering can review and advise on any adjustments needed to accommodate the processing.
Before testing: Defining your form layouts In this phase, you and Billtrust will design your invoice and statement forms. Once you have a design, Billtrust will begin coding your forms. You will use the billtrustxml support program to generate XML files for individual invoices and statements, and then send these files to Billtrust to test against.
A large portion of the Billtrust implementation process involves you reviewing invoices and statements generated by Billtrust. To ensure that Billtrust creates your forms as desired, send many examples of each document type (account statements, credit memos, finance charge invoices, and sales order invoices) which include a wide array of customer settings, payment terms, and sale types. When Billtrust generates files, please review them as soon as possible, so any issues are noticed and addressed in a timely manner.
Follow these steps to manually generate invoice and statement XML files.
Check all related print/display settings in Data Files > Misc. Information > Forms Assignment .
1. Select a Form type (Account Statements , Credit Memos , Invoices , and Finance Charge Invoices ), and click Search .
2. Review the different “Print… ” options.
Notes on specific Forms Assignment settings by form type:
Invoices
Print Reprinted Info : Agility always includes the print time in the XML file, regardless of this setting.
Agility ignores the following settings when generating invoice XMLs:
· Collate Pages for Multiple Copies to Single Printer
· Custom Processing
· Display Printer Selection Window Upon Original Print
· Email Option – Use User Email on Emailed Form
· Fax Option – Fax Time
· Fax Option – Sort by Fax Number
· Print to Printer Default Tray
Finance Charge invoices : Agility ignores the following settings when generating Finance Charge invoice XMLs:
· Collate Pages for Multiple Copies to Single Printer
· Display Printer Selection Window Upon Original Print
· Email Option – Use User Email on Emailed Form
· Fax Option – Fax Time
· Fax Option – Sort by Fax Number
· Print to Printer Default Tray
Account Statements
Print Cycle Code: When set to Yes , Agility always sends your cycle code in the XML file, regardless of the contents of the Cycle Code field on the Accounts Receivable > Open Items > Print Account Statements screen. When set to No , Agility sends no cycle codes. Additional rules tied to the Cycle Code for printing, such as printing for a single customer, do not apply when printing account statements for Billtrust.
Agility ignores the following settings when generating account statement XMLs:
· Collate Pages for Multiple Copies to Single Printer
· Custom Processing
· Display Printer Selection Window Upon Original Print
· Email Option – Use User Email on Emailed Form
· Fax Option – Fax Time
· Print to Printer Default Tray
· Print Customer ID & Balance Due at Bottom of Statements
· Print Invoices with Statements
· Include Finance Charge Invoices
The “Print …” settings on Data Files > Payment Terms determine whether or not Agility includes due dates and the “You may deduct…” phrase in invoice XML files. If Agility does not send these items to Billtrust, Billtrust cannot include them on your invoices and statements. Set all Payment Terms accordingly.
Determine which invoices, statements, and finance charge invoices you want to send to Billtrust to use in testing. Including multiple customers, sale types, transaction types (sales orders, credit memos, finance charges), and payment terms gives your Billtrust team the widest assortment of data possible, to ensure that they include all options in their coding. The more scenarios you cover at this stage—and the more files you send—the better the testing process will go, with fewer surprises later.
· Invoice : Get the transaction’s full invoice number. You will enter this number into the billtrustxml support program.
· Statement : Define and save criteria on Accounts Receivable > Open Items > Print Account Statements . You will need to select a set of criteria in the support program to generate statements.
Use System Administration > Restricted Processing > Support Programs to run the billtrustxml support program.
1. Select Program: Choose billtrustxml .
2. Run billtrustxml .
3. On the Generate Billtrust XML screen
1. Select a Branch .
2. Select a Form Type .
3. Enter the criteria associated with the Form Type.
· Invoice: Enter the transaction’s full invoice number (usually includes branch prefix, transaction ID, a dash, and then the shipment number).
· Statement: Select the version of Print Account Statements created above.
4. Click Generate XML .
5. Email all generated XML files to Billtrust.
Testing prior to go-live Once you have working form layouts, you will test the full cycle of generating XML files for invoices and statements, transmitting these files to Billtrust, and reviewing the forms Billtrust generates from your XML files.
This review process is a vital part of your Billtrust implementation. When Billtrust generates forms, please review them as soon as possible, so any issues are noticed and addressed in a timely manner.
DMSi suggests performing the following steps in Test before changing any settings in Production.
Refresh your Test environment. This will load all recent transactions and settings.
Ask DMSi Support to activate the Agility license for the Billtrust interface. Activating the license allows Agility to start creating XML files, but does not initiate any transmissions to Billtrust.
Ask Billtrust to provide your login credentials for Billtrust’s FTP test site (URL, login, and password; credentials for Billtrust’s test and live FTP sites vary).
Create System Administration > Restricted Processing > File Transfer Maintenance records for Billtrust Invoice and Billtrust Statement . These records contain the information (FTP site address, login credentials) Agility uses to connect to Billtrust’s site and transmit the XML files.
Define separate File Transfer Maintenance records for Billtrust Invoice and Billtrust Statement .
· Enter and save the target address (URL or server name), login ID, and password from Billtrust. Billtrust’s live and test sites should use separate credentials.
· Once you’ve entered and saved the credentials, test the connection.
· As of v544, Agility supports SFTP to Billtrust, but only if the Method option is set to SFTP .
Activate the Billtrust Interface at System Administration > Restricted Processing > Interface/Form Setup .
I. When ready to test, check Active for both BilltrustINV (Billtrust Interface for Invoices) and BilltrustST (Billtrust Interface for Statements).
II. Set or disable Include Finance Charge Invoices
III. Set the Number Days History to Retain .
Define and save statement criteria on Accounts Receivable > Open Items > Print Account Statements .
· Set Type to Open activity .
· Set Process via Billtrust on the Print Options tab of version(s) of the form being used to generate statements for Billtrust. (If “Process via Billtrust” is not set, Agility prints statements based on Forms Assignment and Laser Controls settings instead of generating XML files.)
In System Administration > Restricted Processing > Automated Processing > Queue Maintenance , create Jobs and Queues to generate XML files for statements. (No Jobs or Queues are needed for invoices. Invoicing an order generates an XML file, with a prefix of “BTI”.)
Job settings :
i. Task category : Forms.
ii. Form type : Billtrust Account Statements.
iii. Form name : Desired version of Print Account Statements with Process via Billtrust set.
iv. Accessed by : If the form is accessed by a specific user, Agility displays the user ID here.
v. Set the Processing Branch.
vi. Add the Job to a Queue and schedule the Queue.
vii. Statement XMLs have a prefix of “BTS.”
Create Jobs and Queues at System Administration > Restricted Processing > Automated Processing > Queue Maintenance to send invoice and statements XMLs to Billtrust.
· Invoices
i. Job settings
1. Task category : External Interface .
2. External interface type : Billtrust Invoice .
3. Set the Processing Branch .
ii. Add the Job to a Queue and schedule the Queue.
· Statements
i. Job settings
1. Task category : External Interface .
2. External interface type : Billtrust Statement .
3. Set the Processing Branch .
ii. Add the Job to a Queue and schedule the Queue.
· When a Queue runs, Agility sends all XML files of the corresponding form type (invoice or statement) which have a status of Generated to Billtrust, then updates the status to Sent .
Optional: Create notifications to notify users that Agility has sent files to Billtrust
· System Administration > Restricted Processing > Notification Maintenance
· Event E-Commerce Processing Activity
· Activity : Select events Billtrust Invoice and Billtrust Statement
When testing is complete but you have not yet gone live on Billtrust, access System Administration > Restricted Processing > Interface/Form Setup : Uncheck Active for BilltrustINV (invoices) and BilltrustST (statements).
6.
Prior to go-live · Billtrust delivers all invoices and statements to customers, so your customer delivery preferences need to be stored in Billtrust’s system. DMSi can provide a CyberQuery report to export this information for import into Billtrust’s system.
· If you want the forms you send to customers to include A/R open balance information, please let your DMSi implementation team know—we have a macro which does this, and can add it to your system.
Using lockbox payments with Billtrust (EDI form R823) If Billtrust is creating the payment file correctly, Agility should match payments to customers. If needed, however, you can create customer bank records in Agility.
· Access the customer record at Data Files > Customer Information > Customers .
· At Customer Maintenance , pull up a customer, then click Display credit payment info .
· When the Credit and Payment window opens, click Customer Bank Maintenance .
· At Bank Reference Maintenance , enter Bank ID , Account Number , and Routing Number . You do not need to select an Account type .
1. Bank Name is always BILLTRUST.
2. Account number is Agility’s customer code.
3. Routing number is always a nine-digit ID for your company, provided by Billtrust.
4. You should not need to assign a default branch .
You can use Data Files > Customer Information > Customer Import to populate customer bank information. The relevant fields are in the Sold-to Credit and Misc and Bill-to Credit and Misc field sets.
If this Billtrust implementation is your company’s first experience with Electronic Data Interchange, please contact DMSi, and we will have an EDI specialist contact you.
Going live with Billtrust in your Production environment After you’ve successfully tested the Billtrust interface in Test and your custom forms are working as desired, you are ready to activate Billtrust in your Production environment.
Ask DMSi Support to activate the Billtrust license in your Production database.
Create System Administration > Restricted Processing > File Transfer Maintenance records for Billtrust Invoice and Billtrust Statement.
a. Request target address (URL or server name), login ID, and password from Billtrust. Test and Prod have separate credentials.
b. Define separate File Transfer Maintenance records for Billtrust and Billtrust Statement.
c. Once credentials entered, test the connection.
d. As of 544/545, Agility supports SFTP to Billtrust, but must be set to do so.
2.
Activate the BilltrustINV and BilltrustST interfaces at System Administration > Restricted Processing > Interface/Form Setup .
a. BilltrustINV
· Check Active.
· Enter a value for # Days History to Retain . (The first time each day Agility sends invoices to Billtrust, it purges all files with an age greater than this value and a status other than Generated [Canceled, Sent, etc.])
· Set Include Finance Charge Invoices as desired.
b. BilltrustST
· Check Active.
· Enter a value for # Days History to Retain . (The first time each day Agility sends statements to Billtrust, it purges all files with an age greater than this value and a status other than Generated [Canceled, Sent, etc.])
Define and save statement criteria at Accounts Receivable > Open Items > Print Account Statements .
· Set Type to Open activity .
· Set Process via Billtrust on the Print Options tab of version(s) of the form being used to generate statements for Billtrust. (If Process via Billtrust is not set, Agility prints statements based on Forms Assignment and Laser Controls settings instead of generating XML files.)
Access System Administration > Restricted Processing > Automated Processing > Queue Maintenance to create a Job and Queue to generate account statements. (No set-up is needed for invoices: Agility creates an XML each time an order is invoiced, with a prefix of “BTI”).
Job settings:
· Task category : Forms
· Form type : Billtrust Account Statements.
· Form Name : Desired version of Print Account Statements with Process via Billtrust set
· Accessed By : If the form is accessed by a specific user, Agility displays the user ID here
· Set the Processing Branch .
· Add the Job to a Queue and schedule the Queue.
· XML filename prefix is “BTS.”
Access System Administration > Restricted Processing > Automated Processing > Queue Maintenance to create Jobs and Queues to send data to Billtrust
Invoices
· Job settings
1. Task category : External Interface .
2. External interface type : Billtrust Invoice .
3. Set the Processing Branch .
· Add the Job to a Queue and schedule the Queue.
Statements
· Job settings
1. Task category : External Interface .
2. External interface type : Billtrust Statement .
3. Set the Processing Branch .
· Add the Job to a Queue and schedule the Queue.
When a Queue runs, Agility sends all XML files of the corresponding type (invoice or statement) which have a status of Generated to Billtrust, then updates the files’ status to Sent.
If you manually run Print Accounts Statements , Agility generates XMLs for those statements. Running this Queue sends them to Billtrust.
Billtrust delivers all documents to your customers, so you will need to maintain your customers’ delivery in Billtrust’s system, if you haven’t already. DMSi can provide a CyberQuery report which you can use to export this information from Agility for import into Billtrust’s system.
Using the Billtrust interface with other DMSi products · EDI (Electronic Data Interchange): Billtrust can also provide a payment portal for your customers. If you exercise this option, Billtrust will create payment files using the standardized EDI (Electronic Data Interchange) 823 lockbox format and transmit them to you. You can then use Agility’s EDI interface to receive these files and apply the payments. If this Billtrust implementation is your company’s first experience with EDI, please inform DMSi, and we will have an EDI specialist contact you.
If you want Agility to automatically apply different payment types to different G/L accounts, you will need to perform some extra steps:
o Create an additional E-Commerce > Bank Reference record for each payment type, each with a unique Mailbox ID .
o Billtrust will need to send each set of payments in a separate file to the unique mailbox IDs you defined above.
· Doc Storage/WorldView: With your Billtrust credentials, WorldView can connect to Billtrust’s FTP site and retrieve invoices and/or statements. If you plan to exercise this option, please ask Billtrust to create your files as PDFs. (By default, Billtrust creates files as CSVs, but WorldView needs PDFs.)
AR23406 - Why is My Macro not Running from the Dashboard?
Agility
- Cyberquery
AR23635 - How to use an Alternate UOM to correct a UOM factor on an item with activity
Agility
- Inventory
How to use an alternate UOM to correct a UOM factor on an item with Activity When you need to change a UOM conversion factor on an item after activity exists you can utilize an alternate UOM vs having to renumber and create a new item . For example, the vendor changed pricing a 4’x8’ from nominal pricing (eg 4x8 = 32 sf) to actual pricing (eg 48”x 96” = 33 sf).
When using this option, you define a separate / similar UOM code for each costing factor (eg 32’ vs 33’).
Steps to Support this Option 1. Define a UOM code for the alternate UOM
Data Files > Item Information > UOM Codes
2. Define an UOM conversion factor for the alternate UOM
Data Files > Item Information > UOM Conversions
3. Add the new alternate UOM factor to the item
Data Files > Item Information > Items > display UOM conversion toolbar option
You can eliminate Step 2 by defining the new UOM conversion factor at the same time as adding the new UOM alternate UOM to the item.
4. Change the Cost UOM code on the item supplier record
Data Files > Item Information > Items > assigning item suppliers toolbar option
Example using a base item defined with a stocking and costing UOM of SH.
UOM conversion previously set up for the standard conversion of SH to SH based on 32’.
Add Alternate UOM Conversion Factor to the Item Add an alternate UOM for the oversized costing UOM (such as OMSF) and assign to a factor based on 33’.
Example:
Original Stocking to Costing UOM is SH to MSF based on 32’
Alternate UOM is based on Stocking to Costing of OMSF based on 33’
Define Cost UOM for Supplier If you only have one primary supplier for the item define the new alternate Costing UOM on the item supplier record. If you have multiple suppliers assigned to the item and they are using different UOM factors, define the appropriate costing UOM factor to each item supplier record.
Example:
Primary Supplier assigned with the original Stocking UOM to Costing UOM factor.
For the additional suppliers requiring the alternate UOM, assign the Cost UOM based on the new alternate UOM.
The system continues to use the standard costing UOM factor so you only need to define the Cost UOM value on the item supplier if different than the default costing UOM. For explanation purposes only, both records were defined above.
Impact on Purchase Order For the Primary Supplier, when entering a PO the costing UOM of MSF is auto assigned.
For the additional supplier, the costing UOM of OMSF is auto assigned.
When costing based on ‘Last PO Cost’ the system continues to reference last PO cost on both orders regardless of who is the primary supplier (unless item flag is set “update last PO cost for primary supplier only”.)
Only the costing UOM value changes to back into the factor. In the last example above, the costing value of $3787.0818 OMSF was assigned.
Impact on Sales Order The system continues to calculate average the same regardless of the alternate UOM assigned.
MISC Notes The system continues to report market costs in the default costing UOM. Even if you are no longer using the original costing UOM on purchases, the system continues to report everything in the original UOM which cannot be reassigned.
When you have a large number of items that need to be assigned the new alternate UOM, create a spreadsheet with the following columns (in this specific order):
Item, Factor, From, To
Then populate the records in the spreadsheet that you want to update with the new alternate UOM conversion factor and send to DMSi who can mass load the data for you.
To mass update the Cost UOM on the item supplier record for primary suppliers you can use the Item Import. To mass update the Cost UOM on the item supplier record for the non-primary suppliers, you can use the Item Mass Update. Using both options you need to have the alternate UOM conversion factor defined in the system before running the programs.
Consider this other option: AR825 – How to correct UOM factor on Item with activity – Renumbering an item .
AR23717 - How to set up and run automated Support Programs
Agility
- Automated Processing
The following Support Programs can now be run using automated processing in order to keep data clean on a proactive basis.
· Updqtyttls (update quantity totals)
· dlorphbocm(Delete Orphan BO and commits)
· rebldonord(Rebuild item on order)
To set up these programs: System Administration > Restricted Processing > Automated Support Programs
Choose the support program you wish to automate and select the criteria you want for the program.
Save the criteria giving it a unique name. Repeat for each support program.
To manually run: System Administration > Restricted Processing > Automated Support Programs
Open the saved support program you would like to run using the Open icon in the top left corner of the screen. Select the run button in the bottom right corner of the screen.
The audit report for that support program will be generated via Cyberquery.
To automatically run: System Administration > Restricted Processing > Automated Processing > Queue Maintenance
1. Create a new job. In the top middle of the screen, click the New Job icon (white sheet of paper icon).
2. After entering a job name and description, click Add task.
3. In Task Settings, select “Update Process” for your task category, “Automated Support Programs” for your process type, and then the corresponding Support Program. Then, search for your process name.
4. Repeat this process if running multiple support programs.
5. After all tasks are added, save the job.
6. Click on the Queue tab in the top left corner, then create a new queue and fill in the detail fields. You will want a Queue name and the frequency (weekly, monthly), interval to run and Start time.
7. Add your job name to the queue.
8. Save the queue.
When running from automated processing, no audit report will be generated.
Note: These three support programs are no longer available in the support programs list.
AR23835 - Downloading .df Files for Pro2SQL ahead of Agility Upgrade
Agility
- Pro2SQL
AR23986 - Cyberquery FAQ
Agility
- Cyberquery
Parameters/Prompts How to add a Parameter/Prompt into a query?
Copy and paste the following prompts you need into a query to add a prompt. Keep in mind you will need to add the defined variable into the where statement.
Examples:
Branch Prompt
define string xbranch = parameter/prompt = “Enter Branch ID”
where po_header:system_id=xbranch
Beginning/Ending Date Prompt This prompt defaults to have your starting date 7 day prior to todays date and your ending date the run date.
Define date xstartdate = parameter/prompt = “Enter Start Date” default todaysdate -7
Define date xenddate = parameter/prompt = ”Enter End Date” default todaysdate
where so_header:invoice_date >= xstartdate and so_header:invoice_date<=xenddate
Sales Agent ID prompt
Define string xsalesagent = parameter/prompt=”Enter Sales Agent ID”
Where so_header:xsalesagent
Sales Order # Prompt
Define number xso_id = parameter/prompt =”Enter Sales Order Number”
Where so_detail:so_id=xso_id
File Relationships How do I link tables that are unrelated?
For example, a Customer wants a report of Items sold on Sales Orders in the past month but also wants to see the value in the Misc Cost Price 1 field.
When attempting to run you will get this error that the relationship cannot be found in dictionary. This means you will need to create a file relationship.
To do so, click on the table name that you need to link to the domain. In this example, we need to link item_content_def_branch to the so_detail table.
Clicking on the table will show you the valid indexes to link a table to the item_content_def_branch table.
You will need to pick an index that can be linked easily to the So_detail table. For example, index 1 would be difficult because the So_detail table does not have a thinkness, width, and length field we can directly connect to. The easiest index would be number 4 since the System ID is in the so_detail table and the item is on the item table linked to so_detail.
Next, you will define a file
You will need to set the System ID and Item equal to fields in linked tables to the so_detail as shown below.
Common switches and how they are used. /domain – sets the domain of the report
Example: list/domain= ”item_branch”
/heading – changes the default columns heading
Example: so_detail:qty_ordered/heading=”QTY ON ORDER”
/nocommas – removes commas from printing in the report
Example: so_detail:order_totals/nocommas
/newline – adds a blank line before the next printed line
Example: item_branch:item/newline
/decimalplaces – allows you to set the amount of decimal places to print on the report
Example: so_detail:cost/decimalplaces=2
/noduplicates – does not print the duplicate values on successive lines
Example: so_detail:cust_code/noduplicates
/title – sets the title of the report
Example: list/title=”SO vs Linked Quote Totals”
Upon running you should get an output with no errors if you linked the tables correctly.
How do I total a column? If you are wanting to total data in a CQ Report, you can use a List/nodetail report with an “End of Statement”. The end of statement will allow you to total the columns.
For example, take the query below – it is showing a list of item activity for a specified start date along with the branch, item, qty, activity type, and activity cost.
Let’s say that the Customer wants to total up the ext activity cost for each item by activity type. We can accomplish this by making the report a list/nodetail and adding an end of statement.
The first thing we are going to do is add a /nodetail switch in the list statement. This will suppress the detail from printing in the report.
Next, you will need to add an “End of Statement”
*Note* to create an end of statement, you will need to sort the report by the field you want to total the report by.
In this case, we want to total the activity by item. For this we are going to add Then we are going to add all the lines from our list statement and where we want the qty to be totaled, add total[table:field] so Cyberquery can total these values.
In the end of statement, you will also need to specify which column in the list statement you want to align the end of data with.
Once run, this report will total the item_activity qty for Sales Orders since the date specified in the parameter.
Using an “If then” Statement There may be a time when you want to print a different value than what the field actually shows.
For example, if an item is a stock item, the CQ value for that field is 1.
If you want Cyberquery to print “Yes” for stock items and “No” for nonstock items, you can use an “If then” Statement.
In the list you can put “If item_branch:stock=1 then “YES” else “NO””
AR24399 - AR Open and Paid Inquiry - v552 and under
Agility
- A/R
A/R Open and Paid Inquiry Overview The A/R Open and Paid Inquiry window is where you can research open and paid accounts receivable items. The Search by dropdown determines if you are looking at payments or invoices/transactions.
Note : This article is specific to Agility version v552 and below. If you are using version v553 or more recent, please reference AR20595 instead.
Setting up search criteria The Search Criteria section allows you to set up different criteria to meet different needs. Criteria can be saved, allowing you to quickly access information. Once the criteria has been modified to your liking, select Save Criteria and save your selections with the name of your choice and who is allowed to access it. You must have the action allocation to Save Criteria for All Users/Groups or Save Criteria for User set in order to complete this function. Criteria is saved with the value of the Search by dropdown as there are different columns available based on the value of the Search by dropdown.
Running Inquiry Once you have search criteria set up, select either of the Search buttons to pull in records. If changes are made to the criteria, select Search again to refresh the grid.
Payments Parent/Child Grid The A/R Open and Paid Inquiry is different than other inquiry windows within the A/R, A/P, and G/L modules as it utilizes a parent/child grid for each invoice/payment displayed.
When your Search by value is All payments or Single payment , the parent record represents a specific payment. Detail records underneath that parent represent all invoices to which the payment was applied.
In the below screenshot, since the Search by value is set to Single payment the parent shows that payment 1620-1 was entered on 01/06/20 for $85.09 while the details show that this payment was applied to invoice WEST00318223-001. The details also show that the invoice is considered closed since it has an Open amt of $0.00.
Invoice/Transaction Parent/Child Grid When the Search by dropdown is set to All invoices , Single invoice , or Single transaction the parent record displays information specific to the invoice or transaction while the detail records are all payments applied to the invoice or transaction.
In the below screenshot, since the Search by dropdown is set to Single transaction the parent shows that invoice WEST00318223-001 was invoiced on 01/06/20 for $85.89 while the details show the invoice was paid in full by check 1620-1 on 01/06/20.
Columns The customizable grid allows you to change the order in which the information is presented. For both invoices and payments. To edit the grid, right click in the grid and select Edit Custom View .
The Customize View window allows you to add columns to the grid by double clicking or selecting them and using the arrows to move them over to the Show these columns in this order section. Use the Applies to field to determine if you are customizing the invoices grid or the payments grid. To change the order of the columns, select the column and use the Move Up/Move Down buttons. The Move Up button moves columns to the left and the Move Down button moves columns to the right in the grid.
Grouping The grid allows for grouping so that you can quickly filter/summarize the data being presented. You can expand the group to see details. To turn on grouping, right click in the grid and select Group by Field . Once selected, you can drag the column heading up to the group section to have the grid group by that column. *Grouping MUST be done prior to being able to subtotal.
Select Summaries The Select Summaries option (i.e. Subtotals) allows you to summarize data at the group level, so you don’t have to expand the details to see the data. In the below screenshot, the Sum feature is turned on for the Open amount and shows the sum of all the invoices for customer 00006.
Exporting from the grid To export out the details, right-click then choose Export Grid to and select the output. You can choose Excel files (.xlsx, .xls and .csv), PDF or email the files.
Saving the grid Assign whatever ‘Group by Field’ options you’d like, and change the column width as desired. Then right-click the grid, and hit ‘Save Grid Settings to View’.
AR24407 - How to Calculate Average Cost after quantity adjustment at a different cost
Agility
- Inventory
How to calculate average cost after qty adjustment at a different cost The goal of this article is to help explain how average cost is calculated after a Receiving or Qty Adjustment done at a cost lower than the average cost. Things to keep in mind:
1. 1. UOM Conversions, this example is an FT to FT (1:1) conversion
2. 2. How is the cost carried? This is a cost carried at the Branch level example
a. You can narrow down the Item Activity Viewer to just that Tag, Content, Location level to make it easier to view
b. Make sure you are looking at just one dimension if carried at the dimension level
Question: Why did my Average Cost shoot up after a Receiving Adjustment?
Receiving Adjustment in question: First, you need to figure out the Inventory Valuation BEFORE the adjustment. In this case we are going to take 3843 FT X 4.1974 = 16,130.6082 FT Valuation in Stock before adjustment. As we can see in the Viewer, 2184 FT were adjusted out leaving us with 1659 FT on the RV ADJ line. If 2184 FT were adjusted out at the average cost at the time of the adjustment the valuation would have been: 2184FT X 4.1974 = 9169.1216 Value Removed from Inventory
The actual value removed was:
2184 FT X 2.3763 = 5189.8392 Value Removed from Inventory
The “Amount Abandoned” is the difference between the two amounts:
9169.1216 – 5189.8392 = 3979.2824
The Value of the remaining amount at the current average cost would have been:
1659 FT X 4.1974 = 6963.4866
The Reassigned Amount ends up being the “amount abandoned” + value of remaining quantity at current average cost:
3979.2824 + 6963.4866 = 10,942.769
The remaining qty divided by the “reassigned amount” is what calculates the new Current Average cost and the reason why it shot up in cost:
10,942.769 / 1659 FT = 6.5960
*Due to rounding this amount could be a fraction of a penny off.
AR24427 - How to set up Installed Sales in Agility
Agility
- Installed Sales
AR24521 - How to use the Image Bin v522+
Agility
- Image Gallery
How to Use the Image Bin
1.
Go to http://images.dmsi.com as a hosted user. If you are locally hosted, you can access http://imageslh.dmsi.com and follow the same instructions below.
2.
Contact Support to get your API URL and service name. In this example, we will use ‘http://agilityapi.dmsi.com’ as my API URL and “dmsidevel” as my service name. Note: Be sure to include the http:// in your API URL field.
3.
Log in with your Agility username and password.
4.
Select an existing directory or create a new directory with the “Create Folder” button. Note: DMSi recommends removing spaces to avoid any errors in the image URL, since this URL will contain the folder names.
5.
Select Upload Files
Select the image(s) from your local directory and upload. Note: When naming images, it is easiest to use the item code here to easily find them again if future edits are needed. The multiple file upload will work in most browsers, including Chrome and Edge. If using Internet Explorer, you must download SilverLight to use the multiple file functionality.
6.
Once you have uploaded your images, select “Export Image list” on the folder to which you uploaded images.
7.
Save as an Excel spreadsheet. Note that you will need to add 2 columns to the spreadsheet:
a.
Type – valid values are Image or Document. This is a required field. Because your image repository only houses Images, your type will always need to be populated with ‘Image’ when you’re exporting from the Image Bin
b.
Primary – valid values are Yes or No. This is not a required field, but if you leave this field blank or if this column is excluded, the uploaded image will not be a primary image, even if it’s the only image associated with the item
8.
Save this updated spreadsheet on a shared folder that you can access from Agility.
9.
In Agility, go to Data Files > Misc. Info > Images and Documents. Select the “Import Images and Documents” icon.
10.
Create a Layout Definition by clicking the ‘Add new record’ icon: , select your transaction file, and map over the fields to the appropriate column.
11.
Click Save to start the Import
12.
You can view the imported image in Stock Status. You can access Stock Status by going to Data Files > Item Information > Items and click on the ‘Display Stock Status’ icon: . You can also access Stock Status by going to Sales Orders/Quotes > Stock Status. In Stock Status, click on the ‘View Image’ icon: . Note: This only shows the primary image associated with this item.
You can view all images and documents associated with the item in Item Maintenance, by clicking on the ‘Assign Images and Docs’ icon: .
NOTE: Documents can be imported in the same way; however, the Image Bin cannot house documents. Like your images, your docs must be exposed to the internet. You can do this by housing these docs on a webserver you may have or by using a publicly accessible document storage URL. The only difference in your content on the import (step 8 above) will be to change the value of your ‘Type’ to ‘Document’.
AR24534 - Settings that Affect PartnerView
Agility
- PartnerView
The following describes the menu allocations, action allocations, user profile settings, and PartnerView Parameters that affect what is visible in PartnerView.
General Navigation The following settings affect general navigation across the site.
PartnerView ParametersPure Chat account key – the account key must be specified for the Chat fields to display across the site. Menu AllocationsProducts, Quotes, Orders, Invoices, Credit Memos, Billing – the corresponding menu displays in PartnerView when the option is set for that module. Product Listing The following settings affect what is displayed when viewing the products list.
PartnerView ParametersMaximum number of items to return in product search – controls the maximum number of items returned when searching. Display customer item quicklists in product search – determines whether customer-specific quicklists display in the Quicklists drop-down.Display extended description on items – controls whether the item extended description displays under the short descriptionDisplay link to external website in product search – when set, a link is displayed.Link display name – controls the link text.External website URL – controls the hyperlink URL. Menu Allocations Shopping cart – when unset, the Qty and UOM fields and Add to Cart button aren’t visible. The following settings affect the visibility of available inventory and prices.
PartnerView ParametersDisplay total available quantity for all branches – controls whether the quantity displayed is for the selected branch or all branches. User Profile defaultsInventory display setting – determines whether the quantity or “In Stock/Out of Stock” displays for an item. Action AllocationsView available inventory – when denied, quantity information isn’t visible.View inventory prices – when denied, the item prices and cart total aren’t visible. Product Details The following settings affect what is displayed when viewing product details.
PartnerView ParametersDisplay extended description on items – when set, the extended description displays under the short description. User Profile defaultsInventory display setting – determines whether the quantity or “In Stock/Out of Stock” displays. Action AllocationsView available inventory – when denied, the quantity or “In Stock/Out of Stock” isn’t visible.View inventory prices – when denied, the item price isn’t visible. Menu AllocationsShopping cart – when unset, the Qty and UOM fields aren’t visible. The following settings affect the tabs displayed at the bottom of Product Details.
Action AllocationsView inventory prices – when denied, the Pricing tab isn’t visible.View available inventory – when denied, the Available tab isn’t visible.View on order inventory – when denied, the On Order tab isn’t visible. The following settings control the options and information visible on the Available tab.
Action AllocationsView available inventory details – when View available inventory is granted but this is denied, the Inventory Details option isn’t visible.View available inventory by branch – when View available inventory is granted but this is denied, the Totals by Branch option isn’t visible.View available inventory locations – when granted and viewing inventory details, the Location column displays.View available inventory lots – when granted and viewing inventory details, the Lot column displays. The following settings control the options and information visible on the On Order tab.
Action AllocationsView on order inventory by branch – when denied, the Totals by Branch option isn’t visible on the On Order tab in product details.View on order inventory by tran – when denied, the Transaction Details option isn’t visible on the On Order tab in product details. The following setting controls the part numbers included on the Part Numbers tab.
Action AllocationsView system part numbers – when denied, the part numbers associated with the item supplier aren’t visible in the list of part numbers. Net/Retail Pricing The following settings control whether Net or Retail prices are displayed, and the ability to change between Net and Retail pricing.
PartnerView ParametersAllow retail price display option – when unset, the Net/Retail link isn’t visible, and User Preferences isn’t available from the user menu.Allow list based retail price display – when unset, Retail price – markup on cost and Retail price – discount from list aren’t visible as options in User Preferences and Retail is the only option. Action AllocationsDisable on screen user preferences control – when granted, the Net/Retail link isn’t visible, and User Preferences isn’t available from the user menu.Enable retail price display – when denied, the Net/Retail link isn’t visible, and User Preferences isn’t available in the user menu.Enable net price display – when denied, Retail is displayed at the top and Net isn’t an option in the User Preferences Pricing Display Settings.Retail – Allow discount from list – when denied, Retail price – discount from list isn’t available in the Display drop-down.Retail – Allow markup from cost – when denied, Retail price – markup on cost isn’t available in the Display drop-down.When both Retail – Allow discount from list and Retail – Allow markup from cost are denied, only Retail appears in the drop-down. Quotes The following settings affect what is displayed when viewing, editing, and releasing quotes.
PartnerView ParametersAllow a quote to be copied – when unset, the Copy Quotes icon isn’t visible.Allow non-stock items to be copied – when unset, non-stock item aren’t included when copying a quote. Action AllocationsCopy quotes – when denied, the Copy Quotes icon isn’t visible.Disable edit of shipping address – when denied, the Shipping address link isn’t visible.Edit quotes – when denied, the Edit Quotes icon isn’t visible.Edit quotes – Disallow net price edit – when granted, the Price field is disabled when editing a quote in Net mode.Release quotes – when denied, the Release Quotes icon isn’t visible.Release quotes-partial – when denied, the Edit Qty button isn’t visible in Review and Submit Quote.View docs - Quote – Archived – when denied, the View Doc icon isn’t visible.View docs - Quote - Real-time – when denied, the View PDF and View Retail Quote icons aren’t visible. Orders The following settings affect what is displayed when viewing orders.
PartnerView ParametersDisplay link to external website in order search – when set, a link is displayed.Link display name – controls the link text.External website URL – controls the hyperlink URL.Display canceled sales orders – when denied, canceled sales orders aren’t returned in search results.Display credit hold and price hold statuses on sales orders – controls whether the status shows as Credit Hold/Price Hold or Open. Action AllocationsView docs - Delv Ticket – Archived – when denied, the View Doc and Export XML icons aren’t visible.View docs – Delv Ticket – Real-time – when denied, the View PDF icon isn’t visible.View docs - Order Ack – Archived – when denied, the View Doc and Export XML icons aren’t visible.View docs - Order Ack - Real-time – when denied, the View PDF icon isn’t visible.View docs – Invoice – Real-time – when denied, the View PDF icon isn’t visible.View docs – Invoice – Archived – when denied, the View Doc and Export XML icons aren’t visible. Credit Memos The following settings affect what is displayed when viewing credit memos.
Action AllocationsView docs - Credit memo – Archived – when denied, the View Doc icon isn’t visible.View docs - Credit memo - Real-time – when denied, the View PDF icon isn’t visible.View docs - RMA – Archived – when denied, the View Doc icon isn’t visible.View docs – RMA ack – Real-time – when denied, the View PDF icon isn’t visible. Invoices The following settings affect what is displayed when viewing invoices.
PartnerView ParametersAllow RMA creation – must be set to see the Actions column.Number of allowed days to create RMA – controls the availability of the Create RMA icon based on invoice date. Action AllocationsSubmit returns – when denied, the Actions column isn’t visible.View docs - Invoice – Archived – when denied, the View Doc icon isn’t visible.View docs - Invoice - Real-time – when denied, the View PDF icon isn’t visible.View docs - Delv Ticket – Archived – when denied, the View Doc icon isn’t visible.View docs – Delv Ticket – Real-time – when denied, the View PDF icon isn’t visible.View invoices for current branch only – when granted, only invoices for the selected branch are returned in search results. Cart The following settings affect what is displayed during cart checkout.
PartnerView ParametersRequested delivery date selection – controls whether the delivery date selection is based on routes or calendar dates.Display minimum order hold amount – controls whether the customer ship-to minimum order hold information appears at the bottom of the cart. User Profile defaultsDefault submit cart as – determines whether blank/Order/Quote appears by default in the Submit as field. Action AllocationsDisable edit of shipping address – when granted, the shipping address link isn’t visible.Submit orders – when denied, Orders doesn’t appear as a value in the Submit as drop-down.Submit quotes – when denied, Quotes doesn’t appear as a value in the Submit as drop-down. Billing The following settings affect what is displayed when viewing the billing information, including the available payment options.
A/R ParametersPartnerView A/R receipts batch ID – when denied, the “How would you like to pay” section, selection column, Amount to pay column, and payment buttons at the bottom aren’t visible. PartnerView ParametersDisplay available discount in Billing – when unset, the Available Discount Amt column isn’t visible.Allow discounts when paying by credit card – when unset, the Available Discount Amt column isn’t visible.Allow ACH payments – when unset, the “How would you like to pay” section isn’t visible. Action AllocationsApply payments to invoices – when denied, the “How would you like to pay”, selection column, Amount to pay column, and payment button section at the bottom isn’t visible.Apply open account credits to invoices – when denied, the Apply Credits button isn’t visible.Create cash on account – when denied, the Payment on Account button isn’t visible.View billing information for all ship-to's – when denied, only the billing info for the current ship-to is returned in the results. Agility Configurator The following settings affect what is displayed when configuring a work item.
Action AllocationsAgility Configurator print estimated price on form – when denied, the estimated price doesn’t display in the Print Configuration window when configuring a BOM item.View Agility Configurator component prices – when denied, the prices of the individual components aren’t visible.View Agility Configurator incomplete parent price – when denied, the price of the unit isn’t visible until configuration is complete. PartnerView Settings The following settings affect the availability of PartnerView settings.
Action AllocationsDisable theme administration – when granted, the Change Theme button isn’t visible in Settings.Read only access to content msgs – when granted, the Messages button isn’t visible in Settings. User Profile settingsUse debug feature – when unset, the Log Viewer button isn’t visible in Settings.
AR24556 - Avalara FAQ
Agility
- Avalara
Avalara FAQ How to make an order nontaxable/tax exempt? 3 ways to do this
1. If the customer sometimes has orders that are taxable and others nontaxable you can set the customer up to have the ability to set the tax category on the fly in order entry. To do this go to the customer ship to record under the default codes tab and check box “Set tax category in order entry only”. This will allow the user on the fly to make the orders for that customer nontaxable.
2. If the customer should always be taxable you can go to the Customer ship to record under the default codes tab > then update the tax category to G resale (or the proper category pertaining to the customer).
3. If they use Avalara’s Cert Capture, they will want to load the certificate information into Cert Capture making sure to follow the proper customer account id that we sent in Agility. If in Agility the setting on the sold to record is set to ship to, then the account would be the Agility account id followed by a dash and the ship to seq number (Tina-1). If it’s set at the sold to level the account in Cert capture needs to be the same as the Agility customer id (Tina). Once loaded they can recalculate the taxes on the order and it will make the order exempt.
Tax only credit memo with Avalara – how to? The best way to handle this situation: Create a credit memo for the entire order with the original invoice on the credit memo header. This will send the original invoice date to Avalara and calculate the tax credit based on the tax rates applicable at the time the order was invoiced. Then the order will need to be re-invoiced so that it picks up the tax certificate.
The work around that is not the best, but will work (with some caveats): They can enter a CM with the original invoice on the CM header. They can enter a sundry item that represents the tax category for the credit (this has to be entered for the total sell amount for all items that were charged tax for that tax category). This will create the tax credit for the tax amount that was incorrectly invoiced. Then they have to enter a debit for a sundry item that has a non-taxable category (IE: ON010000) for the same total sell amount so the net of the CM is for the tax credit only. If they use Tax Certificates, they have to make sure the tax certificate is dated after the original invoice, so it does not apply it based on the original invoice date. The tax reporting will be off since it will report these sundry items as taxable and non-taxable sales.
Receive this message: Following error(s) occurred on SO #xxxxxx, shipment #1: Unable to determine the taxing jurisdictions. Tax could not be calculated. Verify that the address is correct and then re-try invoicing it. Address must be valid (even if tax exempt) before it will allow you to invoice the order.
Tax on SO isn’t calculating correctly Troubleshooting tips
· Check the XML file to see what exactly Avalara is calculating
· Run the address through avataxrates.com to see what the address tax percentage should be….does that match Avalara?
· Also check to see the sale type/ship via. If it’s a will call order it most likely is using the branch’s address to calculate the tax % not the ship to address
User is unable to invoice a sales order. An address is incomplete or invalid. Tax could not be calculated. · Make sure the customer ship to address is valid
· Check the sale type/ship via.
· If it’s a will call order it most likely is using the branch’s address to calculate the tax % not the ship to address, make sure the branch customer is setup on the sales order parameters screen, then verify it has an address associated with it.
· If it’s a direct, the supplier’s address will need to be valid. Have them enter a valid address on the supplier ship from.
Rounding issues – Customer paid but there are pennies left on some orders after invoicing Agility brings back a tax rate from Avalara and then applies that to the order all the time up to invoicing. Since Avalara calculates an actual tax amount to charge at the time the order is invoiced, at invoicing, Agility uses that tax amount for the order (or portion of the order). What this can cause is a slight variance between what was calculated in tax based on the rate returned and used at all other times and what the tax that is returned from Avalara at time of invoicing. In the case of Maryland orders, for example, it is because that state tax is always rounded up instead of using standard rounding rules. Avalara applies this tax rule when they calculate the tax on the order. Since we are using rate at all other times, including when you are collecting payment in POS orders, this can cause a slight variance between the amount of the order at the time it is placed, and the payment is applied to when it is invoiced. These pennies will remain on the customer account UNLESS you set your SO parameters to write off the small variances. You should set a write-off threshold for POS transactions to accommodate this so that minor rounding differences will be auto written off. You will want, as a company, to determine how many cents is an acceptable threshold and then define that in System Administration > Module Controls > Sales Order Parameters > POS tab as well as what GL account set you want to write off the small variances to. There is also an underpayment message that is a user-defined text that prints on forms when the write-off threshold is applied to the order and a small amount appears as open when printed on the invoice Use this field to notify the customer that the invoice is considered paid in full.
AR24559 - FAQ Credit Card Issues
Agility
- Credit Cards
FAQ CREDIT CARD ISSUES
1. Why is the CC Payment option not available?
a. For customers on the interface, if they are logged into multiple sessions Agility will automatically disable the second session for CC.
i.The reason for this is because we had customers logging into test and running cards, the interface does not differentiate between test and Prod.
ii.I have had cases where they did not appear to be logged in twice but logging out and back in typically resolves the issue.
2. What address is used for manually entering CC.
a. With the interface they can choose to require and address when entering a card manually, if they do this, Agility will pull in the bill to address on the customer account, however they need to verify if this is the billing address of the Credit Card as that is what is needed.
3. Refund to previous payment, Payment not found
a. The first thing to check is the number of days since the previous payment was made. You can only refund to a previous payment if it is within 45 days.
b. You cannot refund to pin debit transactions. In the previous payment screen, if you scroll to the right in the column for CC tran type it will say Debit.
c. If it’s been more than 45 days, the customer needs to come in to swipe the card for the refund or they need to write the customer a check
4. Need to apply payment in Agility but not charge the card.
a. There are times when because of communication issues we do not get the response in Agility for the charge, when this happens the card is charged but no payment shows in Agility. That is what the Authorize Manually (payments tab) or Key in Authorization (CC icon) are for. These will only apply a payment in Agility and NOT charge the card.
5. Deleting a payment
a. If an order has not been invoiced, you can delete a payment from the previous payment window and it will refund the customer Credit Card. There is security to determine if a user can do this.
b. Backing out a payment through payment backout in AR does NOT credit the card.
c. Canceling the order without deleting the payment FIRST does not credit the CC. It will put a credit on the customer’s account
6. Payment on account
a. Can only be done through cash receipts, you cannot do a refund in cash receipts.
b. If a customer needs to refund a part or all of a payment on account, they have to do this through the IQ portal (website for payment info with Worldpay) they would then have to do a write off in Agility. If they want this to show on the CDA report, they would need to do a negative cash against GL and select to affect cash drawer , then do the write off to the same account from AR.
7. Unable to see stored CC
a. The stored cards (referred to as tokenized cards) are stored based on the branch parameters setting. These can be shared but only if the branches have the same account ID and Account token. If these are the same and the setting to store cards is correct, it may be a connectivity issue. When accessing stored cards, we make an API call to Worldpay to get the information.
8. Are transactions processed with stored cards considered card present?
a. Transactions processed with a stored card are considered “keyed” which means the same as manual entry.
9. Account showing a debit DP.
a. This occurs when a refund has been given on a SO or CM, and then a change is made to reflect that a refund is no longer due, Agility will then put that amount on an account as owed by the customer because the order reflects that “money” was given to the customer. Most common is a refund given and then the order cancelled. These show up As a IN type and the invoice reference starts with D example D00138509-01
10. Refund to previous payments - refund amount
a. You can only refund a previous payment up to the amount of the payment, the system tracks what has previously been refunded and will not let you refund more than the remaining amount.
11. Cancelling a Refund
a. You can cancel a refund from the previous payments window prior to the order being invoiced, and the customer card will be DEBITED for the amount.
12. “The remote server returned an error: (401) Unauthorized” error
a. User is trying to run the pairccdevice support program. When she clicks Get Lane, she is getting a “The remote server returned an error: (401) Unauthorized” error.
b. Troubleshooting steps:
i.Reboot the PC, make sure the computer name is correct.
ii.Check The network connection.
iii.Try a different Lane ID
iv.Try this device on a different PC/ or a different device on this PC
v.If this is still not working you will need to contact your device provider as it is likely a device issue.
AR24565 - How To Setup Agility for Credit Card Interface
Agility
- Credit Cards
Credit Card Interface Agility Install Steps Prerequisites:
· Your company must have a merchant account with WorldPay
· WorldPay will send you a Welcome email with credentials to the IQ site
1. System Configuration:
System Administration > System Configuration > System Config > Payment Provider tab
· Allow credit card storage box : Only check the box for “Allow credit card storage” IF you are signed up with Vantiv for PASS Tokenization (aka Stored Cards, aka Cards in the Cloud), and then activate the default Credit Card Storage URL
· The only way to save a credit card is to save when running a payment, there is no manual entry method as this information is stored with Vantiv not in Agility
· You can delete or update the expiration date for stored credit cards in Agility through the Customer Bill-To record
· There is a report that can be ran to maintain stored CC’s in Data Files > Customer > Customer Listings. This will give you information on expired cards and/or duplicates.
· Number of days history to retain: This is the number of days that Agility will store the XML files for Incoming and Outgoing credit card transactions. 30 or 45 days is typical
· Display billing address in Manual CC : Set to Do Not Display, Zip Code, or Zip Code required. The verification is only looking at Zip code and the number portion of the address
· Timeout seconds : Minimum recommendation is 120
Note (Tripos Direct Customers Only): The Developer Key and Secret in this screen will be revisited when the TriPos piece of the install occurs.
2. Branch Parameters
System Administration > Module Controls > Branch Parameters > Payment Settings tab
On the iQ Portal > Login > Self Service section > Search > Processing Credentials tab
· Processor: If this is being setup in advance of your CC Go Live, you can save the below information and leave the Processor set to None. Then, when ready to go live, Change the Processor from "None" to "Vantiv – No line display" for TriPos Direct, or “Vantiv – TriPos Cloud” for Cloud
· Account ID: Copy and Paste from iQ
· Account token: Copy and Paste from iQ
· Acceptor ID: Copy and Paste from iQ
· Application ID: 961
· Terminal ID: Copy and Paste from iQ
· Commodity Code: 4233 – this is the general commodity code for Building Materials Distributors
· Branch for storing credit cards: select branch – you can only share saved cards across branches that have the same Account ID and Account Token
· triPOS Cloud welcome message: leave blank
· Allow payment surcharge fee : If you will be applying a CC Surcharge fee for your credit card payments, check this box and select the GL Account you would like those surcharges to post to
Note: These settings are branch specific.
3. Payment Methods
Data Files > Misc Information > Payment Methods
DMSi recommends setting up a generic “Credit Card” Payment method, as identifying the card type is unnecessary for Agility to correctly process the card. Use this generic Credit Card Payment Method as the POS Default. You can then setup each individual type (Visa, Mastercard, etc.) and reference the CC type for reporting purposes if you would like.
· Payment method : CC
· Description : CC
· Payment Type : Credit Card
· POS default for payment type : check
· Overpayment : Decide what should be done with an overpayment on a credit card: Apply on account, Deposit on order, Not allowed, Return as cash
· Restrict from order entry : leave unchecked
· Default remaining amount into amount tendered : check
· Include in cash drawer reconciliation : check
· Include in summary report deposit totals : check
· Required in order entry : Check all 3: Authorization, Credit Card #, and Expiration Date
· G/L Account : Assign the G/L account you want these payments to post to – typically the branch Cash account
· Card Type : Other
· Authorization Method : Manual
· Apply credit card surcharge fee : Check if you want to charge a cc surcharge fee and assign your fee percentage
4. Default Receipt Printing
File > User Preferences > Sales tab
POS Payment Settings
· Print receipt from Payments window: check
· Print receipt from Cash Receipts window: check
DMSi recommends checking both of these boxes
5. Customer Default Settings for Stored Credit Cards (Only applies if you are setup to store credit cards)
Data Files > Customer Information > Customers
· Credit Card storage option: pick if you want to store the customer’s card at the Ship-To, Bill-To, or Do not store
o This can be Mass Updated in System Administration > Mass Updates > Customer Mass Updates
6. Sales Order Layout
Sales Orders/Quotes > Sales Order Entry > Information Tab > Edit Layout
Section : Payments
Check the box for the below fields:
i. Authorization # ii. CC Expiration Date iii. Credit Card # iv. Save Credit Card v. Saved Accounts
vi. Previous CC payment.
Note: you can use the Sales Order Layout to restrict which users can save new cards on account.
7. Security Actions
System Administration > Security Administration > Action Allocation
Below are the Security Actions regarding CC Payments – Grant access to users/groups accordingly
· Process Manual Credit Authorization: this action should only be granted to the person(s) who will have access to the Vantiv site for processing transactions outside of Agility. This process does not communicate a payment with Vantiv. The most common example for use of this option is communication timeouts or failures.
· Allow Manual CC Payment with Invalid Address : when using address verification, if the address does not match you have three options, cancel the payment, re-enter the address, or process anyway, this action determines if a user is allowed to process anyway if the address is not valid.
· Delete Payments : is an action allocation that determines if a user can delete a payment from the previous payments window on Sales Order POS transactions.
· Allow Refund in SO Entry : will allow the user to process a refund if changes are made to an order after payment has been applied and the change results in a credit due to the customer, or if a CM item is added to the order also resulting in a credit due.
· Enter SO’s : has to be allowed for the payments tab to be visible. This may be denied for a “Corp” user whom does not enter sales orders but may need to delete a payment.
Level III Transactional Data Setup – Only applies if you plan to do Level III type transactions
For Level III transactions, this is additional information requested by the card holder. Missing information will not keep the card from being processed but will go through at a higher rate. The areas in Agility that would potentially need information are the following.
· Country Codes – International Code (this is the most common missing piece of information)
o Data Files > Lookup Codes> Country Codes, make sure all country codes have an international code assigned. You can get a list of the codes here https://www.nationsonline.org/oneworld/country_code_list.htm
o USA = 840, CAN = 124, CHINA = 156
· Zip Codes – Make sure that all Customer Ship-tos have a zip code, and country code, which will both default into the Sales Order (no zip code on the Sales order is the second most common missing piece of information)
Less common but possible missing information includes
· Commodity Codes – Product Group Minors
o The product Group Minors, Data Files>Item Information> Product Groups have a field for Commodity codes at the Minor level. These codes identify with the material type associated with the PG Minor. When looking for detail Item information this code is what the Level III is looking for. You can look for lists of commodity codes online.
· Branch Controls – Remit to and default Country.
AR24584 - How to perform physical inventory in WMS
Agility
- Physical Inventory
How to perform physical inventory in WMS Before starting any of this, we recommend that you make sure all orders are closed out(Staged Orders are Invoiced, Remans/SO Work Orders are completed or set to Not Printed). Also make sure there are no Incoming records with a “Ready” status sitting out in the WMS Transaction Maintenance window.
Steps to complete full physical inventory:
1. Turn off sending of IA’s from WMS to Agility
2. Use RF guns to count each location
3. Once completed, perform Sync Dump process in WMS
4. Sync dump will create a PI workfile in Agility
Running Tag Comparison Report
1. Inventory Control > Physical Inventory > Comparison Report
2. Set the Open Only option
3. Use the dropdown to select the Workfile ID
4. Update the Include Records w/ Variance greater than to .00 qty
a. Recommended to run the report once with a .00 dollar variance and once with a .00 qty variance
5. Click on Run
6. Review report for variances
7. Correct qtys in WMS if needed and repeat steps 1-6 until variance is acceptable
Posting Inventory in Agility after acceptable tag comparison report variance
1. Inventory Control > Physical Inventory > Audit Report
2. Audit Report must be run prior to adjusting the inventory
a. Set Open Only option
b. Use dropdown to select the PI workfile
c. Click on Print
3. You can review report but it is not necessary.
4. Inventory Control > Physical Inventory > Update Quantity on Hand
5. Use dropdown to select the PI workfile and click on OK
**Make sure you turn back on the sending of IA’s from WMS to Agility
6.
AR24593 - How to set up Automated Period End
Agility
- General Ledger
How to set up Automated Period End Automated Period End allows you to change the default current period to the next period and close the current period for G/L, A/P, and/or A/R.
There are two main steps for setting this up. First, you must set up the automated period end. Second, you must add the automated period end to automated processing.
Automated Period End General Ledger > End of Period > Automated Period End
Create the saved criteria with the desired settings to run through Automated Processing for G/L, A/P and A/R. Save your criteria.
*DMSi recommends running through this in your TEST environment to make sure it is processing how you want it to.
Automated Processing Before you automate your period end, it is recommended to setup the following three reports in Automated Processing (as they are part of the period end reports that must be run at period end ):
A/P Aged Open Payables A/R Aged Trial Balance Inventory Valuation
Set each of these reports up the way you run them at month end and save the report criteria. You will most likely want each report to run for all branches sorted by branch.
There are other reports/inquiries that you can run each period from automated processing. These are listed in the Period End Procedures Checklist.
System Administration > Restricted Processing > Automated Processing > Queue Maintenance
Refer to AR863 – How to set up Automated Processing Jobs in Agility for this step. Here you will want to go into the Jobs tab and create a new job and add a new task with the following settings:
· Task category – set to “Standard Reports”
· Process type – set to A/P Aged Open Payables
· Process name – set this to the name of the saved report
· Process branch – select your Corporate branch
· ‘Sent to’ email – should be the email you want the report sent to
· Click OK.
Repeat this process for the other two reports, adding the tasks to the job.
Next, set up a task for each of the automated period ends.
· Task category – set to "Update process"
· Process type – set to "Automated Period End"
· Process name – select the Automated Period End saved criteria
· Process branch – select your Corporate branch
· ‘Sent to’ email – should be the email that receives the log file.
· Click OK.
The process also updates the branches that share the corresponding G/L, A/R, or G/L category with the selected Process branch .
Go to the Queues tab and create a new Queue titled “Automated Period End”. Select the Frequency and Time Interval to when you want these automated reports to be run (typically at the end of the day on the last day of the month). Add the job(s) previously created to the queue and save.
AR24604 - How to Back Out a Partially Applied or Partially Written Off Payment
Agility
- A/R
How to Back Out a Partially Applied or Partially Written Off Payment If attempting to back out a Payment that has been Partially Applied or Partially Written Off, Agility will prompt an error to let you know.
For Payments that have been Partially Applied, Agility recommends backing out the other Invoices so the entirety of the Payment can be backed out of Agility. However, if you only want to back out part of the Payment, follow the process below.
For Payments that have been Partially Written Off, the process below is the ONLY option for backing out the remainder of that Payment.
Go to Accounts Receivable > Payments > Payment Transfer Enter the Customer ID, Payment Method, Payment Date, and Payment ID to locate the Partially Applied or Partially Written Off Payment. Highlight that line, and then enter the SAME Customer ID in the bottom right of the A/R Payment Transfer screen. Note: Make sure your Period/Year are correct. Select “Transfer Item” and then select “Yes” for the prompted question to confirm. You may need to specify the Bill-to and/or Ship-to Seq. Leave the entire amount in the Allocate Amount field and select "Update" (if necessary). Note that the Payment ID will remain the same, but Agility will assign a new Invoice # (ex. CA-XXXXXXXXX) to the Payment to disassociate it with the original Payment record. You should get a "Payment Transferred Successfully" message Go to Accounts Receivable > Payments > Payment Backout Enter the Customer ID, Payment Method, Payment Date, and Payment ID to locate the Payment. Highlight that line and select your Reason in the bottom right of the A/R Payment Backout screen. Note: Make sure your Period/Year are correct. Proceed with the Backout Process by selecting the “Backout Item” option, and then selecting "Yes" when prompted to complete the Payment Backout. You should no longer receive an error. You should no longer receive an error. Select “Yes” when prompted to complete the Payment Backout.
AR24700 - Incorrect A/R Write Off - How to add the balance back or reverse write off?
Agility
- A/R
AR24750 - Why aren’t my RMAs showing in Order Processing (Print Delv Tickets/RMA tab)
Agility
- Order Processing
Why aren’t my RMAs showing in Order Processing (Print Delv Tickets/RMA tab)
Customer is trying to print a delivery ticket for a RMA, but the order is not showing when searching by All Shipments in Print Delv Ticekts/RMA in Order Processing.
I have two RMA’s, tran ID 6 and 7. Only RMA 6 is showing in Order Processing. Why?
SO Viewer is showing both RMA’s
The reason RMA 7 doesn’t show is because customer M001 #1 doesn’t have any Routes assigned to it.
Customer AP001 #3 does have routes, so RMA 6 shows in Order Processing.
AR24803 - Setup requirements for capturing customer signatures
Agility
- Forms
Capturing customer signatures when printing forms from Sales Order Entry or a function called from Sales Order Entry requires the following setup.
You must be using Element as your credit card payment processor and using a triPOS® Full Function POS MX 915 device to capture customer signatures.
Element's triPOS® needs to be installed on each PC that will be collecting customer signatures.
System Setup
Contact DMSi Techinical Support to assist in entering the required settings in connext.xml for your configuration.The connext.xml file must contain the following settings.
A Windows share must be configured to allow both Agility clients and the Agility AppServers to write the signature image into the Optio "images" folder. Once the share is setup and configured properly, you must enter the path into the connect.xml for the Agility Client and the Agility AppServers to use. Depending on your configuration, make the entries in the Master section of the connect.xml or in the appropriate Environment's section.
In a standard installation, Optio is installed in C:\Agility\Optio. An example of a Windows share for a standard installation would be \\agilserver\Optio.
The connect.xml tags for the signature feature are <OPTIO_SHARE_CLIENT> and <OPTIO_SHARE_SERVER>.
<OPTIO_SHARE_CLIENT> contains the full share path accessible by Agility Clients to the Optio installation directory. Using the above example, the path would be \\agilserver\optio. <OPTIO_SHARE_SERVER> contains the full share path accessible by AgilityAppServers to the Optio installation directory. If the Agility AppServers are running on a Unix server, the Windows share must be mounted on the Unix server and you must enter the path to the mount point.
If the Agility AppServers are running on a Windows server, use the Windows share.
Using the above example, if the AppServers are on a Windows server, you would enter \\agilserver\Optio. If the AppServers are on Unix, an example mount point would be /remote/agilserver/Optio.
Agility Setup
For sale types used on sales orders where the customer is present such as counter sales and customer pickup, set the form specific flag on each form you want to capture signatures. The flags are available under the heading 'Prompt for customer signature in SO Entry when printing'.
Access Sale Types Maintenance: Data Files > Sales Order Settings > Sale Types
Set the User Preference 'Do not require customer signature when printing forms' on users that print forms for orders with customer facing sale types, that will never have customers present. (Optional)
Access User Preferences: File > User Preferences
Update the 'Timout seconds for signature device' field if the default value of 60 seconds does not meet your needs.
Access System Configuration: System Adminstration > System Configuration > System Config
Define signature print options in Forms Assignment for the order acknowledgement, delivery ticket and invoice
Set 'Print customer signature' to Yes if signatures should print. Use the 'Customer signature label' field to define a custom label to print on the form. There is a default value of 'Customer Signature'.
The invoice has additional settings for printing credit card customer signatures. They do not affect printing the other customer signatures.
To print credit card customer signatures set 'Print payment receipt information' and 'Print credit card signature' to Yes. If you want to print credit card signatures on the Reprint of the invoice, set 'Print credit card signature on reprint' to Yes
Access Forms Assignment: Data Files > Misc Information > Forms Assignment
The following Sales Order Parameters settings are related to the order signature.
If you will be using the order signature for a single purpose, unset the SO parameter 'Prompt for customer signature in SO Entry' to suppress the display of the Signature Capture window and define a label in the 'Default order signature label' field.
If you will be using the order signature for multiple purposes define a label in the 'Default order signature label' field that will default into the Signature Capture window. Note: Leaving the default label field empty requires entering a label each time a signature is captured.
Access Sales Order Parameters: System Adminstration > Module Controls > Sales Order Parameters
AR24878 - Aged trial balance run for a prior date still including current invoices
Agility
- A/R
AR25071 - How To Setup Agility for Credit Card Interface
Agility
- Credit Cards
Credit Card Interface Agility Install Steps Prerequisites:
· Your company must have a merchant account with WorldPay
· WorldPay will send you a Welcome email with credentials to the IQ site
1. System Configuration:
System Administration > System Configuration > System Config > Payment Provider tab
· Allow credit card storage box : Only check the box for “Allow credit card storage” IF you are signed up with Vantiv for PASS Tokenization (aka Stored Cards, aka Cards in the Cloud), and then activate the default Credit Card Storage URL
· The only way to save a credit card is to save when running a payment, there is no manual entry method as this information is stored with Vantiv not in Agility
· You can delete or update the expiration date for stored credit cards in Agility through the Customer Bill-To record
· There is a report that can be ran to maintain stored CC’s in Data Files > Customer > Customer Listings. This will give you information on expired cards and/or duplicates.
· Number of days history to retain: This is the number of days that Agility will store the XML files for Incoming and Outgoing credit card transactions. 30 or 45 days is typical
· Display billing address in Manual CC : Set to Do Not Display, Zip Code, or Zip Code required. The verification is only looking at Zip code and the number portion of the address
· Timeout seconds : Minimum recommendation is 120
Note (Tripos Direct Customers Only): The Developer Key and Secret in this screen will be revisited when the TriPos piece of the install occurs.
2. Branch Parameters
System Administration > Module Controls > Branch Parameters > Payment Settings tab
On the iQ Portal > Login > Self Service section > Search > Processing Credentials tab
· Processor: If this is being setup in advance of your CC Go Live, you can save the below information and leave the Processor set to None. Then, when ready to go live, Change the Processor from "None" to "Vantiv – No line display" for TriPos Direct, or “Vantiv – TriPos Cloud” for Cloud
· Account ID: Copy and Paste from iQ
· Account token: Copy and Paste from iQ
· Acceptor ID: Copy and Paste from iQ
· Application ID: 961
· Terminal ID: Copy and Paste from iQ
· Commodity Code: 4233 – this is the general commodity code for Building Materials Distributors
· Branch for storing credit cards: select branch – you can only share saved cards across branches that have the same Account ID and Account Token
· triPOS Cloud welcome message: leave blank
· Allow payment surcharge fee : If you will be applying a CC Surcharge fee for your credit card payments, check this box and select the GL Account you would like those surcharges to post to
Note: These settings are branch specific.
3. Payment Methods
Data Files > Misc Information > Payment Methods
DMSi recommends setting up a generic “Credit Card” Payment method, as identifying the card type is unnecessary for Agility to correctly process the card. Use this generic Credit Card Payment Method as the POS Default. You can then setup each individual type (Visa, Mastercard, etc.) and reference the CC type for reporting purposes if you would like.
· Payment method : CC
· Description : CC
· Payment Type : Credit Card
· POS default for payment type : check
· Overpayment : Decide what should be done with an overpayment on a credit card: Apply on account, Deposit on order, Not allowed, Return as cash
· Restrict from order entry : leave unchecked
· Default remaining amount into amount tendered : check
· Include in cash drawer reconciliation : check
· Include in summary report deposit totals : check
· Required in order entry : Check all 3: Authorization, Credit Card #, and Expiration Date
· G/L Account : Assign the G/L account you want these payments to post to – typically the branch Cash account
· Card Type : Other
· Authorization Method : Manual
· Apply credit card surcharge fee : Check if you want to charge a cc surcharge fee and assign your fee percentage
4. Default Receipt Printing
File > User Preferences > Sales tab
POS Payment Settings
· Print receipt from Payments window: check
· Print receipt from Cash Receipts window: check
DMSi recommends checking both of these boxes
5. Customer Default Settings for Stored Credit Cards (Only applies if you are setup to store credit cards)
Data Files > Customer Information > Customers
· Credit Card storage option: pick if you want to store the customer’s card at the Ship-To, Bill-To, or Do not store
o This can be Mass Updated in System Administration > Mass Updates > Customer Mass Updates
6. Sales Order Layout
Sales Orders/Quotes > Sales Order Entry > Information Tab > Edit Layout
Section : Payments
Check the box for the below fields:
i. Authorization # ii. CC Expiration Date iii. Credit Card # iv. Save Credit Card v. Saved Accounts
vi. Previous CC payment.
Note: you can use the Sales Order Layout to restrict which users can save new cards on account.
7. Security Actions
System Administration > Security Administration > Action Allocation
Below are the Security Actions regarding CC Payments – Grant access to users/groups accordingly
· Process Manual Credit Authorization: this action should only be granted to the person(s) who will have access to the Vantiv site for processing transactions outside of Agility. This process does not communicate a payment with Vantiv. The most common example for use of this option is communication timeouts or failures.
· Allow Manual CC Payment with Invalid Address : when using address verification, if the address does not match you have three options, cancel the payment, re-enter the address, or process anyway, this action determines if a user is allowed to process anyway if the address is not valid.
· Delete Payments : is an action allocation that determines if a user can delete a payment from the previous payments window on Sales Order POS transactions.
· Allow Refund in SO Entry : will allow the user to process a refund if changes are made to an order after payment has been applied and the change results in a credit due to the customer, or if a CM item is added to the order also resulting in a credit due.
· Enter SO’s : has to be allowed for the payments tab to be visible. This may be denied for a “Corp” user whom does not enter sales orders but may need to delete a payment.
Level III Transactional Data Setup – Only applies if you plan to do Level III type transactions
For Level III transactions, this is additional information requested by the card holder. Missing information will not keep the card from being processed but will go through at a higher rate. The areas in Agility that would potentially need information are the following.
· Country Codes – International Code (this is the most common missing piece of information)
o Data Files > Lookup Codes> Country Codes, make sure all country codes have an international code assigned. You can get a list of the codes here https://www.nationsonline.org/oneworld/country_code_list.htm
o USA = 840, CAN = 124, CHINA = 156
· Zip Codes – Make sure that all Customer Ship-tos have a zip code, and country code, which will both default into the Sales Order (no zip code on the Sales order is the second most common missing piece of information)
Less common but possible missing information includes
· Commodity Codes – Product Group Minors
o The product Group Minors, Data Files>Item Information> Product Groups have a field for Commodity codes at the Minor level. These codes identify with the material type associated with the PG Minor. When looking for detail Item information this code is what the Level III is looking for. You can look for lists of commodity codes online.
· Branch Controls – Remit to and default Country.
AR25311 - Dispatch Basics / Dispatch Terminology / Dispatch Questions
Agility
- Dispatch Processing
Per Agility Help:
The freight dispatch function allows you to manage and coordinate the movement of outside or internal trucks by tying specific items and quantities on a purchase order, supplier return, sales order, sales order shipment, credit memo, or reman work order to a particular dispatch record, which you can print, update as needed, and track through A/P Recon and invoice entry.
By managing material using the dispatch module, you have greater control over the entire dispatch process since you know where the material is always located. In addition, the dispatch function tracks routes, stops, weight and load, allowing you to create the most efficient routes and consolidate freight orders when feasible.
Terminology:
Dispatch (e.g. freight dispatch)
Optional function allowing you to manage the delivery and pick up of orders, the related dispatch documents and freight payables for incoming and outgoing materials by tying specific items and quantities from a transaction to a dispatch record.
The following transaction types can be associated with a dispatch.
•(PO) Purchase order
•(SR) Supplier return
•(SR) Sales order
•(CM) Credit memo
•(RI/RO) Reman input/output
Dispatched transaction
A purchase order, supplier return, sales order, sales order shipment, credit memo or reman work order associated with a dispatch record.
Shipment info record
A means to track shipping information such as carrier ID, transport type and transport number on transactions regardless if you are using the Dispatch module.
Advance Shipping Notice (ASN)
Form used to provide dispatch information about material being shipped to a customer or from a supplier
For Agility sales orders, ASN forms (WMS/EDI) provide dispatch information to trading partners with whom you also trade invoices.
For Agility purchase orders, the ASN number used in mobile receiving corresponds to the dispatch ID assigned in the following situations.
· You dispatch the purchase order for freight purposes
· System auto dispatches purchase order upon processing an e-commerce interface file flagged to create dispatch
· You create a dispatch upon receiving notification from the supplier about the material being
· shipped
For each of these situations, you can then print the PO Check in List and perform mobile receiving by ASN, which displays and accumulates quantities of like items for all purchase orders on the ASN.
Third-party routing
· Appian Logistics Direct Route
· DQ Technologies Order Delivery Tracking System
The optional third-party routing interface allows you to utilize a third-party routing application to automatically calculate and optimize delivery routes for Agility purchase orders, supplier returns, sales orders, sales order shipments and credit memos.
This interface uses the dispatch function to control the data transmitted to the routing application and process data returned from the routing application. This interface utilizes screens within the Sales Orders/Quotes module.
Common Questions/Answers
How can I see which dispatches are not printed?
Answer
Assisted with going through the dispatch viewer, adding the printed search criteria, and sorting the viewer by the printed status. Also assisted in setting up the viewer to be used again in the future by going through the viewer saving options in the upper left portion of the viewer.
Any way to reprint the dispatch once the order is invoiced?
Answer
Once invoiced the only form you can reprint is the invoice
How to create a Dispatch from a Reman?
Answer
-You cannot create a Dispatch from RM entry. You need to open dispatch first, click Add button at the bottom and then add the Reman to it (RI for reman input or RO for reman output and you then need to select the operation so it will pull the items associated with the operation
AR25317 - Order Entry Branch Option - Agility Call Center Functionality
Agility
- Sales Orders
Scenario : A company is planning to build/have a centralized location that fulfils orders for other branch locations of the same company for its customers. This “Call Center” environment needs to ensure that they are inputting sales orders for the correct branch location so that there is little-to-no error in processing for its customers. Does Agility have functionality to ensure that the centralized branch location will create transactions inside of the proper branch?
Answer : Agility has a flag/parameter we can set that would be beneficial.
This is a feature we can implement that will prompt the Sales Order creator to "select a branch" at order entry. This allows for efficiency in creating the order in the proper branch and mitigates any mistakes along the way. This is the “Order Entry Branch Option” on the Customer Ship-to record > Default Flags tab.
There are two things we need to set inside of Agility to turn this feature "on": 1) Inside of each customer ship to record (data files > customer information > customers) there is a field that we can set that will say "Order entry branch option" in the "Default Flags" tab.
The options there are either Current Branch, Default Branch, or Prompt for Branch
-
You will need to update any customer's ship-to
record that is needed for this field.
-
A setting of "Prompt for Branch" will
be the setting to prompt the sales order creator to select the branch at Order
entry every time.
-
This can be updated via a customer import
("Order entry Branch option" column in Ship-to default flags
section)
-
If you need assistance with this, please let us
know at support@dmsi.com and
we can assist!
2) Once
all ship-to records are updated, go to System Admin > Module controls >
Sales order parameters.
Here, go
to the second tab (SO/Quote/CM 2) and check the box of "Use order entry
branch option on ship-to " so that we can utilize the customer’s ship-to
settings properly.
After these settings are both enacted for the call center’s
branch, then moving forward will look like this:
-
Whenever a user at the “Centralized location
Call Center” branch creates a sales order in Agility and inputs a customer
ship-to from the system, there will be a prompt that forces the user to Select
the Branch for the sales order to go into.
·
If there are ever questions, please let us know at
support@dmsi.com
AR25422 - How to manually process Marvin Orders
Agility
- Interfaces
1. Log into the OMS back office system. You can find this URL by going to E-Commerce > Interface Maintenance > select the Web Service Options tab for the Form/Interface Type of MARVIN.
2. Copy and paste the URL from the “URL” field into an IE session. Please make sure IE is used, otherwise the XML file you attempt to generate will have errors.
3. Once you have accessed the Marvin site by entering in the URL in IE, enter in the login credentials that are specified in Interface Maintenance.
4. Click on “GetOrdersByTimestamp”.
5. Specify your search criteria. To get your startDate, just copy and paste what is in your Last Order Retrieval field in Interface Maintenance to retain the correct formatting.
6. Adjust the startDate and endDate criteria as you see fit. Populate includeFeatures with “FALSE” and includeTextDetails with “TRUE”.
7. Click Invoke to bring up a single xml file with orders created within the date and time range you specified.
8. Save the XML file by clicking on the IE Tools icon > File > Save As and note the location to which you save the file.
9. To import the file, go to E-Commerce > Send/Receive > Select an Interface type of Marvin Windows. Change the Source of data to process value to “Load file from disk”.
10.10. Select your file by clicking on the icon to the right of the “File(s) to load” field, and click Run.
11.11. Your files will then be received, and you will get your normal confirmation in the Processing Activity Log that pops up once the send/receive process is complete.
AR25473 - How does the Loftware automated process work for labels?
Agility
- Data Files
New AP client is available with v440 Agility. This is version 6.0.0.0 of the AP client and includes the necessary pieces for the transferring the Loftware label files from one place to another. With this change, there are essentially 2 services that can be installed. They can be installed together or individually. Because of the combined installation option, there are some installation process changes to gather further information. See below.
AP File Transfer client configuration file contains a set of tags that is pretty much identical to the AP Queue client. In fact, most of the entries are duplicated from the original install. However, the ?dequeue? tag for the File Transfer service indicates how often the client should go out to move files from the location the appserver placed them (connect.xml tag) and where the user told the client to transfer them to (input during installation of the client and saved to ?FileSavePath? tag in configuration.xml). The value entered in the ?FileSavePath? should be the final location where Loftware is looking for it to pull in for processing.
In the installation, there are 2 sets of inputs for user/password for the File Transfer service. This first is for the user that will be running the File Transfer service via the API and it will be logging into Agility. It is assumed/expected that the user id will be the same as that used to run the normal AP processing for queues. The second user name and password is to be filled in if you will be accessing a remote share directory when accessing/moving files. This user should have all the necessary permissions to the directors where the files are being placed or transferred to. These fields are NOT saved in the Configuration.xml file. Instead they are saved inside the properties of the client as the LogOn information. The user name must be in the format ?domain\user?.
New tags are available for connect.xml in v440. They are: Loftware and Loftware_Appserver. These are NOT automatically added into connect.xml. When the customer wants this, tech will need to add the appropriate tag to the connect.xml file based on whether the customer is using Windows (Loftware) or Unix servers (Loftware_Appserver). This tag will indicate to the appserver where to store the PAS files generated for labels generated and is used when the File Transfer service needs to know where to pick up the label files from during the transfer. This location is ONLY used when generating pick files from Automated Processing because we needed files to be placed in a spot that the appserver could find them. The current label processing inside Agility does NOT run on the appserver. We did not want to force the change to the appserver from inside Agility. If the tag is missing from the connect.xml file or is there, but is blank, labels will be placed in/pulled from the ?startin? directory + \labels. If the \labels subdirectory does not exist, it will be created. (Either process ? generating labels or picking up labels for transfer ? can create that directory.) This will ensure that labels continue to be generated and printed even with the connect.xml does not have the appropriate information. Under these condition, an appserver error log entry will be created to alert users to the fact that the connect.xml is missing information for this process. **If the connect.xml is updated after labels are generated, but before they are picked up, there could be a mismatch of locations which would cause labels to not print. This should be a very rare situation, but could occur.
There is no new setup inside Agility for this process. Labels run through this process when they are setup to be run through Automated Processing (ie, run on the appserver). **It is important to note the label process when not running through automated processing, like expediting a pick, it still being run through the old method, which automatically places the .PAS file in the correct loftware directory immediately.
Labels files are generated 1 per pick file; this is existing functionality.
If the label file is larger than the BLOB file allows, the process will break the files up into multiple files, transfer the files and then combine them again into 1 large file for Loftware to process.
AR25444 - PartnerView Public user for Catalog Configuration
Agility
- PartnerView
PartnerView Public user for Catalog Configuration Specific setup is required for the catalog user to work correctly in the PV Web Config file.
If the output is from Agility, IE viewer or report, it processes through the Email Server. You will go to System Administration > Module Controls > Branch Parameters and Test the Mail Server. If you get those emails fine, you can work with Tech to see if the output email specifically hit the email server. PartnerView v4.5.4 introduces Catalog Search. The new functionality requires the creation and security administration of a public Guest user in Agility for the PrtnrView product to be used as the public user.
When utilizing the new Catalog Search functionality, PartnerView starts a session using the credentials of the Agility public Guest user you configure to retrieve inventory item information and pricing. This retrieval happens before the PartnerView user logs in with their personal login credential which then sets their Agility branch, customer and ship-to defaults accordingly.
Because the public user credentials are stored in the web configuration for PartnerView, once the user has been created AND you are ready to use the new functionality, a request to DMSi’s tech support team will need to be made that includes the user name and password of the public user as well as a confirmation that you wish to begin to use the new functionality. Please be sure to include whether you would like this turned on in your test environment, production environment or both. If you wish to see the functionality in your test environment, a separate request can be sent in to update production when you are ready.
Following are suggested guidelines for the creation and security setup of the public Guest user.
The following is an example setup for the guest user. Permissions granted may vary based on desired settings for prices, available qty and on order qty. Permissions denied should be entered this way for the generic user.
AR25502 - Billtrust Implementation Overview
Agility
- Billtrust
This document describes how Agility and Billtrust work together, and the steps which need to be taken in Agility to use the Billtrust interface. If you are interested in learning more about Agility’s Billtrust interface, please contact a DMSi Productivity Solutions consultant to ensure that you have the tools and licensing needed to use Agility’s Billtrust interface, and to discuss how the Billtrust interface interacts with other DMSi products.
How Agility’s Billtrust interface works Agility’s Billtrust interface uses the following steps to generate XML files containing invoice and statement data and send these files to Billtrust.
1. An Agility user or Automated Processing initiates a process which generates XML files (invoices one or more orders or uses Accounts Receivable > Open Items > Print Account Statements with Process via Billtrust set to generate one or more statements).
2. Agility creates an XML file for each invoice or statement, and stores them in the XML_OUT_DATA table. These files display in E-Commerce > Log Maintenance with a status of Generated .
3. An Automated Processing queue which transmits invoices and/or statements to Billtrust runs. This process sends all files with a status of Generated to the target address saved in System Administration > Restricted Processing > File Transfer Maintenance (record type Billtrust Invoice or Billtrust Statement ).
4. Agility sends the Processing Activity Log to specified users via the E-Commerce Processing Activity notification, if one has been created at System Administration > Restricted Processing > Notification Maintenance (optional).
5. Agility changes the transmitted files’ status from Generated to Sent in E-Commerce > Log Maintenance .
Billtrust then delivers invoices and statements to your customers using the forms you’ve designed.
Records which Agility does not send to Billtrust Agility’s Billtrust interface sends all invoices and statements to Billtrust for processing, with the following exceptions:
· EDI invoices.
· Finance charge invoices for EDI customers.
· Invoices for the POS cash customer defined in System Administration > Module Controls > Branch Parameters .
· Invoices for the shipping branch of a branch transfer.
· Contract billing adjustments
· Charge or cost adjustments.
Before testing: Defining your form layouts In this phase, you and Billtrust will design your invoice and statement forms. Once you have a design, Billtrust will begin coding your forms. You will use the billtrustxml support program to generate XML files for individual invoices and statements, and then send these files to Billtrust to test against.
A large portion of the Billtrust implementation process involves you reviewing invoices and statements generated by Billtrust. To ensure that Billtrust creates your forms as desired, send many examples of each document type (account statements, credit memos, finance charge invoices, and sales order invoices) which include a wide array of customer settings, payment terms, and sale types. When Billtrust generates files, please review them as soon as possible, so any issues are noticed and addressed in a timely manner.
Follow these steps to manually generate invoice and statement XML files.
Check all related print/display settings in Data Files > Misc. Information > Forms Assignment .
1. Select a Form type (Account Statements , Credit Memos , Invoices , and Finance Charge Invoices ), and click Search .
2. Review the different “Print… ” options.
Notes on specific Forms Assignment settings by form type:
Invoices
Print Reprinted Info : Agility always includes the print time in the XML file, regardless of this setting.
Agility ignores the following settings when generating invoice XMLs:
· Collate Pages for Multiple Copies to Single Printer
· Custom Processing
· Display Printer Selection Window Upon Original Print
· Email Option – Use User Email on Emailed Form
· Fax Option – Fax Time
· Fax Option – Sort by Fax Number
· Print to Printer Default Tray
Finance Charge invoices : Agility ignores the following settings when generating Finance Charge invoice XMLs:
· Collate Pages for Multiple Copies to Single Printer
· Display Printer Selection Window Upon Original Print
· Email Option – Use User Email on Emailed Form
· Fax Option – Fax Time
· Fax Option – Sort by Fax Number
· Print to Printer Default Tray
Account Statements
Print Cycle Code: When set to Yes , Agility always sends your cycle code in the XML file, regardless of the contents of the Cycle Code field on the Accounts Receivable > Open Items > Print Account Statements screen. When set to No , Agility sends no cycle codes. Additional rules tied to the Cycle Code for printing, such as printing for a single customer, do not apply when printing account statements for Billtrust.
Agility ignores the following settings when generating account statement XMLs:
· Collate Pages for Multiple Copies to Single Printer
· Custom Processing
· Display Printer Selection Window Upon Original Print
· Email Option – Use User Email on Emailed Form
· Fax Option – Fax Time
· Print to Printer Default Tray
· Print Customer ID & Balance Due at Bottom of Statements
· Print Invoices with Statements
· Include Finance Charge Invoices
The “Print …” settings on Data Files > Payment Terms determine whether or not Agility includes due dates and the “You may deduct…” phrase in invoice XML files. If Agility does not send these items to Billtrust, Billtrust cannot include them on your invoices and statements. Set all Payment Terms accordingly.
Determine which invoices, statements, and finance charge invoices you want to send to Billtrust to use in testing. Including multiple customers, sale types, transaction types (sales orders, credit memos, finance charges), and payment terms gives your Billtrust team the widest assortment of data possible, to ensure that they include all options in their coding. The more scenarios you cover at this stage—and the more files you send—the better the testing process will go, with fewer surprises later.
· Invoice : Get the transaction’s full invoice number. You will enter this number into the billtrustxml support program.
· Statement : Define and save criteria on Accounts Receivable > Open Items > Print Account Statements . You will need to select a set of criteria in the support program to generate statements.
Use System Administration > Restricted Processing > Support Programs to run the billtrustxml support program.
1. Select Program: Choose billtrustxml .
2. Run billtrustxml .
3. On the Generate Billtrust XML screen
1. Select a Branch .
2. Select a Form Type .
3. Enter the criteria associated with the Form Type.
· Invoice: Enter the transaction’s full invoice number (usually includes branch prefix, transaction ID, a dash, and then the shipment number).
· Statement: Select the version of Print Account Statements created above.
4. Click Generate XML .
5. Email all generated XML files to Billtrust.
Testing prior to go-live Once you have working form layouts, you will test the full cycle of generating XML files for invoices and statements, transmitting these files to Billtrust, and reviewing the forms Billtrust generates from your XML files.
This review process is a vital part of your Billtrust implementation. When Billtrust generates forms, please review them as soon as possible, so any issues are noticed and addressed in a timely manner.
DMSi suggests performing the following steps in Test before changing any settings in Production.
Refresh your Test environment. This will load all recent transactions and settings.
Ask DMSi Support to activate the Agility license for the Billtrust interface. Activating the license allows Agility to start creating XML files, but does not initiate any transmissions to Billtrust.
Ask Billtrust to provide your login credentials for Billtrust’s FTP test site (URL, login, and password; credentials for Billtrust’s test and live FTP sites vary).
Create System Administration > Restricted Processing > File Transfer Maintenance records for Billtrust Invoice and Billtrust Statement . These records contain the information (FTP site address, login credentials) Agility uses to connect to Billtrust’s site and transmit the XML files.
Define separate File Transfer Maintenance records for Billtrust Invoice and Billtrust Statement .
· Enter and save the target address (URL or server name), login ID, and password from Billtrust. Billtrust’s live and test sites should use separate credentials.
· Once you’ve entered and saved the credentials, test the connection.
· As of v544, Agility supports SFTP to Billtrust, but only if the Method option is set to SFTP .
Activate the Billtrust Interface at System Administration > Restricted Processing > Interface/Form Setup .
I. When ready to test, check Active for both BilltrustINV (Billtrust Interface for Invoices) and BilltrustST (Billtrust Interface for Statements).
II. Set or disable Include Finance Charge Invoices
III. Set the Number Days History to Retain .
Define and save statement criteria on Accounts Receivable > Open Items > Print Account Statements .
· Set Type to Open activity .
· Set Process via Billtrust on the Print Options tab of version(s) of the form being used to generate statements for Billtrust. (If “Process via Billtrust” is not set, Agility prints statements based on Forms Assignment and Laser Controls settings instead of generating XML files.)
In System Administration > Restricted Processing > Automated Processing > Queue Maintenance , create Jobs and Queues to generate XML files for statements. (No Jobs or Queues are needed for invoices. Invoicing an order generates an XML file, with a prefix of “BTI”.)
Job settings :
i. Task category : Forms.
ii. Form type : Billtrust Account Statements.
iii. Form name : Desired version of Print Account Statements with Process via Billtrust set.
iv. Accessed by : If the form is accessed by a specific user, Agility displays the user ID here.
v. Set the Processing Branch.
vi. Add the Job to a Queue and schedule the Queue.
vii. Statement XMLs have a prefix of “BTS.”
Create Jobs and Queues at System Administration > Restricted Processing > Automated Processing > Queue Maintenance to send invoice and statements XMLs to Billtrust.
· Invoices
i. Job settings
1. Task category : External Interface .
2. External interface type : Billtrust Invoice .
3. Set the Processing Branch .
ii. Add the Job to a Queue and schedule the Queue.
· Statements
i. Job settings
1. Task category : External Interface .
2. External interface type : Billtrust Statement .
3. Set the Processing Branch .
ii. Add the Job to a Queue and schedule the Queue.
· When a Queue runs, Agility sends all XML files of the corresponding form type (invoice or statement) which have a status of Generated to Billtrust, then updates the status to Sent .
Optional: Create notifications to notify users that Agility has sent files to Billtrust
· System Administration > Restricted Processing > Notification Maintenance
· Event E-Commerce Processing Activity
· Activity : Select events Billtrust Invoice and Billtrust Statement
When testing is complete but you have not yet gone live on Billtrust, access System Administration > Restricted Processing > Interface/Form Setup : Uncheck Active for BilltrustINV (invoices) and BilltrustST (statements).
6.
Prior to go-live · Billtrust delivers all invoices and statements to customers, so your customer delivery preferences need to be stored in Billtrust’s system. DMSi can provide a CyberQuery report to export this information for import into Billtrust’s system.
· If you want the forms you send to customers to include A/R open balance information, please let your DMSi implementation team know—we have a macro which does this, and can add it to your system.
Using lockbox payments with Billtrust (EDI form R823) If Billtrust is creating the payment file correctly, Agility should match payments to customers. If needed, however, you can create customer bank records in Agility.
· Access the customer record at Data Files > Customer Information > Customers .
· At Customer Maintenance , pull up a customer, then click Display credit payment info .
· When the Credit and Payment window opens, click Customer Bank Maintenance .
· At Bank Reference Maintenance , enter Bank ID , Account Number , and Routing Number . You do not need to select an Account type .
1. Bank Name is always BILLTRUST.
2. Account number is Agility’s customer code.
3. Routing number is always a nine-digit ID for your company, provided by Billtrust.
4. You should not need to assign a default branch .
You can use Data Files > Customer Information > Customer Import to populate customer bank information. The relevant fields are in the Sold-to Credit and Misc and Bill-to Credit and Misc field sets.
If this Billtrust implementation is your company’s first experience with Electronic Data Interchange, please contact DMSi, and we will have an EDI specialist contact you.
Going live with Billtrust in your Production environment After you’ve successfully tested the Billtrust interface in Test and your custom forms are working as desired, you are ready to activate Billtrust in your Production environment.
Ask DMSi Support to activate the Billtrust license in your Production database.
Create System Administration > Restricted Processing > File Transfer Maintenance records for Billtrust Invoice and Billtrust Statement.
a. Request target address (URL or server name), login ID, and password from Billtrust. Test and Prod have separate credentials.
b. Define separate File Transfer Maintenance records for Billtrust and Billtrust Statement.
c. Once credentials entered, test the connection.
d. As of 544/545, Agility supports SFTP to Billtrust, but must be set to do so.
2.
Activate the BilltrustINV and BilltrustST interfaces at System Administration > Restricted Processing > Interface/Form Setup .
a. BilltrustINV
· Check Active.
· Enter a value for # Days History to Retain . (The first time each day Agility sends invoices to Billtrust, it purges all files with an age greater than this value and a status other than Generated [Canceled, Sent, etc.])
· Set Include Finance Charge Invoices as desired.
b. BilltrustST
· Check Active.
· Enter a value for # Days History to Retain . (The first time each day Agility sends statements to Billtrust, it purges all files with an age greater than this value and a status other than Generated [Canceled, Sent, etc.])
Define and save statement criteria at Accounts Receivable > Open Items > Print Account Statements .
· Set Type to Open activity .
· Set Process via Billtrust on the Print Options tab of version(s) of the form being used to generate statements for Billtrust. (If Process via Billtrust is not set, Agility prints statements based on Forms Assignment and Laser Controls settings instead of generating XML files.)
Access System Administration > Restricted Processing > Automated Processing > Queue Maintenance to create a Job and Queue to generate account statements. (No set-up is needed for invoices: Agility creates an XML each time an order is invoiced, with a prefix of “BTI”).
Job settings:
· Task category : Forms
· Form type : Billtrust Account Statements.
· Form Name : Desired version of Print Account Statements with Process via Billtrust set
· Accessed By : If the form is accessed by a specific user, Agility displays the user ID here
· Set the Processing Branch .
· Add the Job to a Queue and schedule the Queue.
· XML filename prefix is “BTS.”
Access System Administration > Restricted Processing > Automated Processing > Queue Maintenance to create Jobs and Queues to send data to Billtrust
Invoices
· Job settings
1. Task category : External Interface .
2. External interface type : Billtrust Invoice .
3. Set the Processing Branch .
· Add the Job to a Queue and schedule the Queue.
Statements
· Job settings
1. Task category : External Interface .
2. External interface type : Billtrust Statement .
3. Set the Processing Branch .
· Add the Job to a Queue and schedule the Queue.
When a Queue runs, Agility sends all XML files of the corresponding type (invoice or statement) which have a status of Generated to Billtrust, then updates the files’ status to Sent.
If you manually run Print Accounts Statements , Agility generates XMLs for those statements. Running this Queue sends them to Billtrust.
Billtrust delivers all documents to your customers, so you will need to maintain your customers’ delivery in Billtrust’s system, if you haven’t already. DMSi can provide a CyberQuery report which you can use to export this information from Agility for import into Billtrust’s system.
Using the Billtrust interface with other DMSi products · EDI (Electronic Data Interchange): Billtrust can also provide a payment portal for your customers. If you exercise this option, Billtrust will create payment files using the standardized EDI (Electronic Data Interchange) 823 lockbox format and transmit them to you. You can then use Agility’s EDI interface to receive these files and apply the payments. If this Billtrust implementation is your company’s first experience with EDI, please inform DMSi, and we will have an EDI specialist contact you.
If you want Agility to automatically apply different payment types to different G/L accounts, you will need to perform some extra steps:
o Create an additional E-Commerce > Bank Reference record for each payment type, each with a unique Mailbox ID .
o Billtrust will need to send each set of payments in a separate file to the unique mailbox IDs you defined above.
· Doc Storage/WorldView: With your Billtrust credentials, WorldView can connect to Billtrust’s FTP site and retrieve invoices and/or statements. If you plan to exercise this option, please ask Billtrust to create your files as PDFs. (By default, Billtrust creates files as CSVs, but WorldView needs PDFs.)
AR25515 - Cyberquery reports not running after upgrade
Agility
- Cyberquery
You are trying to run saved CQ reports, but get an error stating the reports are compiled using an old version. Anytime you install a new version of Agility, you will need to recompile the reports.
The images associated with this article are contained in a separate Word document attached to this article.
1. Go to Report Writer > VCQ Report Compiler (Image 1).
2. Here (Image 2), you can compile a single report or all reports at once.
If you know the report name, but not where it is stored, click “Include sub-directories in compile.”
Click Run.
*** DMSi recommends that you DO NOT select “All.” This will compile every CQ report, including each pass on multipass reports. ***
3. The compile process launches a CQ window, detailing the results of the compile process.
If the pop-up report contains the line, “Enquiry [report name] is compiled – no errors,” then everything is fine, and your report is ready for use (Image 3).
If the pop-up report does not include the report name and specify that it’s compiled (Image 4), make sure you’ve spelled the report name correctly, and check “Include sub-directories…,” if you haven’t already. Run the compiler again.
4. If you are still not able to compile the report, please contact DMSi Support.
AR25533 - Using Installed Sales
Agility
- Installed Sales
This article details how to use and navigate within Agility Installed Sales.
As of version 544, Installed Sales can be accessed via core Agility or via a standalone web browser. However, Installed Sales is currently being released only to customers who wish to take part in Beta testing. From within core Agility, you can find it at Sales Orders/Quotes > Installed Sales. Otherwise, from any computer or tablet (iOS, Android), go to agility.dmsi.com and login with your Agility credentials with the proper Org ID appended to your login. This is something you should have been notified of during implementation/setup, so please contact Agility Support if you do not know it.
If your normal Agility login is:
Login: jsmith PW: 123
You would use this to log in to Installed Sales for your company at agility.dmsi.com
Login: jsmith.orgid PW: 123
The landing page in Installed Sales is the Summary tab, which has a row of quick metrics to review your projects at the top of the page and 3 widgets to quickly Find a Project, review Overdue Tasks by Owner, and any tasks that are on the schedule for Today. The data shown on the dashboard will be by branch and you can switch branches with the dropdown in the top right corner. You can see Agility version and database information by clicking your name in the very top right and can logout from here as well.
Creating a New Project You can create a new project within Installed Sales separately from a transaction within core Agility. Click the blue New Project button found at the top right of your dashboard (on the Summary tab). The project editor will open in a “drawer” on the right side of your screen.
1. Project name – Give your project a name, such as the address of the jobsite or any particular nomenclature you may use. This is a required field.
2. Category – If you categorize your projects, such as “Windows” and “Doors”, but not required.
3. Date – Expected completion date of the project, but not required.
4. Status – List of user-defined statuses to choose from to. This is a required field.
5. Owners – Agility user who is responsible for the project. This is a required field.
6. Description – If your project needs more description or to capture other pertinent details
7. Customer ID – ID of the Agility customer for whom this project is for. You can search for the customer using the “Search ID” button. This is a required field.
8. Ship to seq # - the specific ship-to/job seq # for this Agility customer. You can search for the customer using the “Search seq #” button. This is a required field.
9. Click Create to create the project. The new project will then open on your screen.
When a project is manually created in this way, it will not be linked to any transactions in Agility yet. Therefore, to link a sales order or quote to an existing Installed Sales project, enter the Project ID in the Sales Project field on the sales order or quote or search for it using the Sales Project locator.
Find a Project On the main dashboard (Summary tab), there is a Find a Project widget on the left side. Here you will find the list of open projects (sorted by Project ID). If you know the Project ID or part of the Project Name, you can type it in the search field to go straight to a project without scrolling or to narrow the list down.
1. My Projects – will filter the project list to only the ones with the current user as the owner
2. Show Closed Projects – the list will not show closed projects by default, but you can check this filter if you are searching for a closed project.
Overdue Tasks by Owner On the main dashboard (Summary tab), there is an Overdue Tasks by Owner widget in the middle. Here you will find the list of Agility owners and a breakdown of the number of active tasks they own and how many are overdue (based on the task’s end date/time and if not yet completed). If any tasks do not have an owner assigned (the assignee on a task), they will show as “Unassigned”.
Today On the main dashboard (Summary tab), there is a Today widget on the right side. Here you will find any tasks that have yet to occur today. Each task will display the start and end time, as well as the specific Project ID and Name that it belongs to.
Feedback On ANY page in Installed Sales, you will find the Leave Feedback button (the blue paper airplane button found at the bottom right). If at any time while using Installed Sales, you think “I really like how this works” or “I wish this worked differently”, PLEASE drop us a quick note with the Feedback button. It will take you straight to the Comment field so you can quickly type the thought you just had and will default in your name and email address from the current user. You only need to click Submit so it finds its way to us at DMSi. Your feedback will help fine-tune the Installed Sales module as we progress through the Beta phase and into its more-final state. We will be eagerly reviewing all feedback that we receive so any and all comments you wish to share are welcome.
The Installers tab shows all internal and external installers that your company works with. Each one will have their own “card” and will display their contact information as well the user-defined color they are assigned. Clicking on an installer will take you to the Installer view.
Installer View When viewing a single Installer, on the left side of the screen you see the Projects for which this installer has tasks that they are assigned to. Clicking on a Project will expand to show the list of tasks that Installer has for the project. Click on a task to open the Task Editor in the drawer if you need to make changes to a task.
You can also view the schedule in calendar format for this specific installer. You can switch between Month/Week/Day views and navigate to different months/weeks/days as well. You can even filter by Project or Assignee if necessary.
Scrolling to the bottom of the screen, you will see a section that shows any purchase orders linked to this Installer (Purchase Orders will only display for external installers since they are linked to an Agility Supplier ID). This will only display a purchase order if it is linked to a sales order that is linked to this sales project.
A calendar view of scheduled tasks and events for all projects can be seen on the Schedule tab. There is an option to filter the events by a specific Project, Installer, and/or Assignee (found at the top of the calendar). By clicking the filter icon, you can also show completed tasks (they are hidden by default), hide on track tasks, or hide off track tasks. To quickly clear any and all filters set, click Clear All.
There are many options for navigating around the calendar. The calendar icon at the top left of the calendar allows you to quickly look at a different month in a “baby” calendar while leaving the main calendar where it is at. If you click a different date within the baby calendar, it will navigate the main calendar to that date. By clicking the Today button, you can quickly return the main calendar to the view with today’s date. Search for an event by clicking the magnifying glass icon and typing a keyword. Lastly, you can switch the view of the calendar between month, day, week, or agenda view.
Tasks will display with their respective Project ID and the task name. Click on an event to open the task editor in the drawer. Tasks are colored based on the assigned installer’s color (set in Installed Sales Maintenance in Agility). Any task that does not have an installer assigned will be the default gray and will display a + for the installer badge. Tasks that have one installer assigned will appear in that installer’s assigned color and the installer badge will show their initials. Tasks that have more than one installer assigned will be the default gray but will have a number on the installer badge indicating how many installers are assigned to that task. Clicking on the installer badge will display an Installers pop-up to quickly view which installers are assigned. You can also easily remove or add new installers from this pop-up. Lastly, you can quickly duplicate or delete a task by clicking the 3 dots on the right side of the event.
Action Needed Above the calendar on the top right, you will find a bell icon which houses the Action Needed list. In this list, you will find all tasks that were set to either Needs Date or Needs Labor but do not yet have dates or installers assigned yet. The number of tasks that need action will show as the red badge over the bell icon.
Click on the task to set dates or click the installer badge (+ icon) to add installers. You can toggle the lists between tasks needing dates and tasks needing labor. A task that needs both dates and labor will show on each list. Once the respective action is done, it will be removed from the respective list.
When focused on a single project, you will see the project details at the top of the page in the dark blue header. Details include the Project ID, Project Name, Customer ID and Ship-to Seq #, Project Status, Project Owner, Category, and Description. This header displays on all tabs within a project.
You can also edit the project details by clicking the Edit button in the top right of the header. This will open the project details in the “drawer” to the right side for you to edit. Don’t forget to click Save after your changes are made. If you want to delete a project, this is where you will find the Delete button.
Summary tab (in Project View) The Project Summary tab will be the default starting page when viewing a project. Below the header you will find a handful of quick metrics that give you a quick snapshot of the project. These metrics cards may change over time but currently show progress data on tasks as well as revenue and cost data for the project.
Much like the All Projects Summary page, you will see a Today section that shows any tasks for this project that are coming up today. If you utilize phases when organizing tasks for projects, the Phase Completion section in the middle of the page will show you the completion progress by phase. On the right side, a Comments section exists for leaving ad hoc notes regarding the project in a noticeable spot.
Tasks tab The second tab in the project view is where tasks (and phases) are created and maintained. To create a task, you can either use the quick create option or click the New Task button. To quick create, find the quick create field, type the name of the task, and hit enter. Even faster, the quick create task field is the first tab position upon opening the tasks tab, so that’s TAB+type+ENTER to create a task. One more tab and you’re at the quick create phase field. Phases can be used to categorize tasks that occur within a common theme, for example, Planning, Labor, and Wrap-up phases. Of course, you can also click the New Phase button to open the phase editor in the “drawer”. Within the phase editor, you can assign an owner to a phase if you’d like.
To edit a phase or task, click on the phase or task title on the page and it will open the editor in the “drawer”. When editing a task, you can add a description, maintain the phase it belongs to, assign a priority, assign an owner, and maintain the status (on track or off track). You will also decide whether the task needs a date assigned to it or if installers/laborers should be scheduled for it. Therefore, check Needs Date and/or Needs Labor if those apply to this task (only Needs Date is set to ‘yes’ by default). You can set the actual dates or the installers at this time or come back to it when you are ready to schedule things. Tasks that have Needs Date and Needs Labor set to ‘yes’, but no dates or installers are assigned yet will appear in the Action Needed list (on the Schedule tab) until date or installers are set. A task can be set for specific start and end times or a more general ‘All day’. When Needs Labor is set to ‘yes’, the Assign Installers button will appear. Click it to open the list of installers from which to assign one or more installers for the task.
Lastly, comments can be added at the bottom. Don’t forget to Save your work. To complete the task, click Save and Complete (click this button again to “uncomplete” the task). If you’d like to delete the task, you will do that from this window.
Back in the Tasks tab, you can drag-and-drop tasks and phases within the page by clicking on the 6 dots “handle” on the left side of the task/phase card. In doing this, you can easily organize and reorder your tasks and phases for the project. Drag tasks into phases, rearrange the order of entire phases… drag-and-drop makes it easy.
The calendar icon on a task card switches you to the calendar (Schedule tab) for a quick glance. You can also mark a task complete by clicking the Complete circle on the right side of the task card.
Schedule tab (in Project view) A calendar view of scheduled tasks and events for the project can be seen on the Schedule tab. Sales orders will appear on their expected delivery date (when linked to the project) and purchase orders will appear on their expected receipt dates (when linked to a sales order that is linked to the project). You can also filter the tasks that display on the calendar by a specific Installer and/or Assignee (found at the top of the calendar). Otherwise, all other functionality in this tab is the same as the All Projects calendar (see All Projects Schedule tab).
Installers tab (in Project view) The installers tab shows all installers assigned to tasks on this project. Their respective tasks will show below their card. Clicking on the installer card will open the Installer view for that installer. Clicking on a task will open the task editor in the drawer. You can quickly unassign an installer from a task on this page as well.
Transactions tab Any quotes, sales orders, or credit memos that are linked to the project will display in the Transactions tab. This is the Sales Project Transaction Viewer that can be found in core Agility (and was initialized by the “dfltvwr” support program during setup, contact Agility Support if you do not see any data in this tab you expect to see). The criteria, column order, and sort and subtotal settings are set by the Sales Project Transaction Viewer in Agility but can be updated within Installed Sales as well for the current user. Drag a column header to the top of the viewer to sort by that criteria or drag the column headers around to rearrange the order that the data is displayed. Click the Settings button to restore the grid defaults or to show or hide certain columns. The viewer displays data at the detail level by default, but it can be toggled to the summary level as well.
Metrics tab The metrics tab displays data related to the gross margin, revenue, cost, and payment history for this project. The top of the page separates the gross margin data (and broken out revenue and cost) by quoted, projected, and actual numbers. Quoted numbers are derived from quotes only. Projected numbers are derived from invoiced and uninvoiced amounts from sales orders/credit memos, plus any amounts unreleased from quotes. Actual numbers are from invoiced numbers only. In the middle of the page are graphs for a visual representation of the same data. At the bottom of the page is a grid showing payment history for transactions linked to this project. A quick snapshot of the customer’s credit status also displays above the payment history grid. The column order of the payment history grid can be adjusted using the Settings button.
From any page in Installed Sales, use “CTRL + /” to open the keyboard shortcuts available for the current page. There may be some useful hot keys that will enable you to move throughout Installed Sales at a quick pace. For example, hitting “F” on any page will take you straight to the Feedback window. Also, hitting “\” will open the Skip Navigation that may help to save you time as well.
AR25537 - How to set up Installed Sales in Agility
Agility
- Installed Sales
Verify the users that will be accessing the Installed Sales module have access to Sales Order/Quotes module and the Installed Sales menu option.
Also, v erify the users that will be defining key records for Installed Sales have access to Data Files module and Installed Sales Maintenance menu option under Sales Order Settings.
1. In Agility, navigate to System Administration > Security Administration > Security Maintenance.
2. Select a specific user ID or group ID and click “Edit Menu Security”.
3. Find “Installed Sales” under the Sales Orders/Quotes menu and “Installed Sales Maintenance” under Sales Order Settings within the Data Files menu.
In order to begin using some of the functions of Installed Sales, some data setup is required within Installed Sales Maintenance.
1. In Agility, navigate to Data Files > Sales Order Settings > Installed Sales Maintenance. The initial window gives a visual idea of how installed sales projects are structured.
An owner is a person responsible for managing an installed sale project. Owners are selected from a list of Agility users.
1. Click the “Owners” link on the left side of the Installed Sales Maintenance window.
2. A list of Agility user IDs is presented on the left. Select the users from the Available list and move them to the Owners list on the right to create the list of owners that can be assigned to a sales project. You are required to define at least one owner.
Statuses are user-defined and are used to identify milestones along the installed sale workflow.
1. Click the “Statuses” link on the left side of the Installed Sales Maintenance window.
2. Click the New button on the right side of the window to create a new status.
3. Name – enter the name of the Status
4. Active – uncheck if you no longer want the status to be visible as an option
5. Type – either “Open” or “Closed”. Change to “Closed” if it is a status that signals the end of the project or no further attention is required (such as “Cancelled” or “Completed”). You are required to have at least one open status and one closed status.
6. Description – 200 character field to list the details explaining the status.
7. Click “Save & New” to continue entering another status or “Save & Close” if done entering statuses.
8. You should see your saved statuses in the list on the main Status screen.
9. To update a status, select a status record and click the Edit button, or double-click on the row.
10. If you find it easier to do data entry in Excel or have a long list of status es to create, you can import a file from Excel. Click the Import button and then the “Export default layout” icon to generate the import template to use. When you’re ready to import, make sure the correct file path is shown in the Transaction file field and click Process. Any errors will be shown in an audit file. For more help with imports in Agility, see the Imports help doc page .
11. If you want to make several changes to your list of existing statuses, you can also Export the list with the Export button and then re-import it.
12. The statuses will display within Installed Sales in the order they show on this screen. If you’d like to reorder the sequence, use the Reorder button to open a window where you can move a status up or down in the list.
A category is assigned to a sales project for grouping capabilities. A category is not required on a sales project, but it can be helpful if you offer a variety of installation services, such as windows, doors, or roofing.
1. Click the “Categories” link on the left side of the Installed Sales Maintenance window.
2. Click the New button on the right side of the window to create a new category.
3. Category – type the name of the category, up to 30 characters
4. Active – uncheck if you no longer want the status to be visible as an option
5. Description – 200 characters to add more detail about the category
6. Click “Save & New” to continue entering another status or “Save & Close” if done entering statuses.
7. You should see your saved categories in the list on the main Category screen.
8. To update a category, select a category record and click the Edit button or double-click on the row.
9. If you find it easier to do data entry in Excel or have a long list of categories to create, you can import a file from Excel. Click the Import button and then the “Export default layout” icon to generate the import template to use. When you’re ready to import, make sure the correct file path is shown in the Transaction file field and click Process. Any errors will be shown in an audit file. For more help with imports in Agility, see the Imports help doc page .
10. If you want to make several changes to your list of existing categories, you can also Export the list with the Export button and then re-import it.
Installers are divided into separate “external” and “internal” lists. I nstallers are unique by branch by default but can be shared with other branches.
External An external installer is a person or company that is contract ed for installation work. They are linked to an existing Supplier ID within Agility.
1. Click the New button on the right side of the window to create a new installer.
2. Installer ID – give the external installer an installer ID ( 15 character limit).
3. Active – uncheck if you no longer want the installer to be visible to assign to projects
4. Supplier ID – assign an existing Supplier ID and ship-from seq number that should be linked to this installer. Contacts (on the specified ship-from record for the supplier) are used to identify specific people to assign to a project within Installed Sales.
5. Color – assign a color that will help you identify tasks assigned to that installer in a project schedule.
Internal An internal installer is a person employed by your company that does installation work. They do not need to have an Agility user ID.
1. Click the New button on the right side of the window to create a new installer.
2. Installer ID – give the internal installer an installer ID (15 character limit).
3. Active – uncheck if you no longer want the installer to be visible to assign to projects
4. First and Last name are required fields. Fill out the phone and email information if it adds value.
5. Color – assign a color that will help you identify tasks assigned to that installer in a project schedule.
In order to associate a sales order to a project in Installed Sales, the first step is to designate a specific sale type as an “installed sale”. Any time a sales order is created that should be linked to an installed sales project, this sale type should be assigned to the order.
1. In Agility, navigate to Data Files > Sales Order Settings > Sale Types.
2. Create a new sale type that will be used for installed sales orders and check the “installed sale” option
a. This option controls the functionality that links sales orders to installed sales projects.
Sales orders or quotes with the installed sale sale type can auto-create sales projects with default values upon saving the sales order or quote. This functionality is controlled in Installed Sales Parameters. These settings can be shared across branches based on the Sales Project category in System Profile Definition (see section above), but the default is set to be unique by branch.
1. In Agility, navigate to System Administration > Module Controls > Installed Sales Parameters.
2. Select a record (by branch) to update the auto-create sales projects settings.
3. The options for auto-creating sales projects are:
a. Yes – projects will be auto-created upon save of a sales order or quote with the default values specified
b. No – sales projects will not be auto-created upon save of sales order or quote
c. Prompt – upon save of a sales order or quote, the user will be prompted to create a new sales project and the default values may or may not be editable at that time (depending on the “editable” setting for each field).
4. Default title – specify the values to use to build the project title assigned to an auto-created project (Customer ID, Ship-to name, Ship-to sequence, Ship-to address, Ship-to city, Ship-to state, Ship-to ZIP). This can be editable at the time of creation and is a required field.
5. Default status – specify which status to assign to an auto-created project. Statuses are user-defined values set up in Installed Sales Maintenance (see Statuses section above). This can be editable at the time of creation and is a required field.
6. Default owner – specify one or multiple owners to assign to an auto-created project. Owners are user-defined values set up in Installed Sales Maintenance (see Owners section above). This can be editable at the time of creation and is a required field.
7. Default category - specify which category to assign to an auto-created project. Categories are user-defined values set up in Installed Sales Maintenance (see Categories section above). This can be editable at the time of creation but is not required.
8. Expected completion date – specify the date you expect the auto-created project to be completed. Can set as a relative date or an actual date, but will more than likely set as a relative date. If a project typically takes 45 days to complete, then select a “run date” of “45 days”. This is not required, however, so leaving a run date of 0 days will not set an expected completion date.
Add the Sales project field to the header section in MyUI Designer to view, assign, or update the installed sales project attached to the order. If utilizing the auto-create sales projects feature described in the Installed Sales Parameters section, the Sales project field will display the project ID upon saving the sales order. If not using the auto-create sales project feature, you can manually assign project IDs to sales orders once the project has been created within the Installed Sales module.
Note: the Sales project field is already visible in Quote and Credit Memo Entry.
1. From Sales Order Entry, click the Information tab, then Edit Layout.
2. For the Order Information section, click Add/Remove Fields.
3. Find the “Sales project” field in the list and check the box to show the field. Leave it as editable.
4. Move the field where you want it to display in the Order Information layout below.
5. Click Save and close the window.
Utilizing specific labor items on installed sales orders will be helpful in triggering additional functionality within Installed Sales. You may only use a single, generic “labor” item or you may want to designate more specific labor items, such as “window install” or “warranty work”. Currently, an item marked as a “sales project labor item” can auto-create phases and tasks within Installed Sales when that item is saved on an order.
1. In Agility, navigate to Data Files > Item Information > Items.
2. Pull up the labor item code (or create a new one) and ensure the Item Type is set as “Sundry”.
3. Once Sundry is selected, check the parameter that says “Sales project labor item”.
Once an item is flagged as a “sales project labor item”, you can set up specific phases and tasks as a template if, say, you always do the same sequence of tasks for a specific labor item. For example, if you have a labor item such as “window install” and for that type of project, you always do the same tasks, such as a “site walkthrough”, “rough opening review”, “install windows”, “trim work”, and “release payment” you can create these as template tasks for that item so that they are automatically created whenever that item is added to an order linked to a sales project.
1. In Agility, navigate to Data Files > Item Information > Items.
2. Pull up the labor item code and ensure it is flagged as a “sales project labor item”.
3. Click the “Installed sales phase and task template” icon at the top of the window (last icon).
4. The Phase and Task Maintenance window will open. From here, you can create phases and/or tasks that you want to be created for this labor item. You can type a task or phase title into the “Quick enter…” fields to quickly add a task/phase (hit Enter to add). Or you can click the New Task or New Phase buttons to add more details.
a. Phase – Phases are simply a way to categorize tasks to help organize a longer list. For example, you may want to have a “Planning” or “Pre-work” phase, an “Install” phase, and/or a “Post-install” phase.
b. Task – Tasks are specific actions that typically need to be scheduled and/or have installers assigned to. For example, a “rough opening review” may not need to be scheduled for a specific date and may not even need a specific person assigned to it, but it is still a task that needs to be done. However, something like “install windows” is a task that definitely needs to be scheduled and have a labor team or installer(s) assigned to it.
5. Click “New Phase”.
6. Give the Phase a title (the only required field). Add an Assignee if there is only one person who will always own an entire phase (otherwise, it can be assigned on a project by project basis).
7. Click Create to save the phase.
8. Now click “Create new task” under your newly created phase.
9. Give the Task a title (the only required field). Feel free to add a description if more detail is needed.
10. Phase should be the phase that this task belongs to (auto-populated if “Add new task” is clicked under a specific phase).
11. Priority – High, Medium, Low, or None (default). Colors will be assigned to these tasks based on the priority selected (High = red, Medium = orange, Low = blue).
12. Assignee – the person that is responsible for this task being completed. This is NOT necessarily the installer assigned to the task.
13. Status – either On Track (default) or Off Track.
14. Needs date – will be checked by default. This implies that the task needs to be scheduled for specific dates on the calendar (to be determined once project is created).
15. Needs labor – This implies that an installer (or installers) needs to be assigned to this task (to be determined once a project is created).
16. Click Create to save the task.
17. Continue to add phases and tasks as needed. Once your list is created, you can click on any phase or task to edit or delete it. You can also drag-and-drop the order around by click-and-holding the 6 dots image on the left side.
18. Once your list of tasks is arranged how you like it, these will be auto-created on the sales project anytime that labor item is saved to an order.
API Parameters In order to utilize the Attachments feature within Installed Sales, AWS S3 credentials must be populated in AWS S3 Maintenance within API Parameters (System Administration > Module Controls > API Parameters). AWS S3 is what is used to store the files that can be attached to a sales project. A tech case is needed to create the necessary S3 information that will be placed in API parameters. Contact Fran Vonderfecht to get a new user’s system-defined S3 credentials populated within API Parameters.
A valid record in this window will have a valid S3 bucket name, region, access key, and secret key populated. All customers can have a system-defined S3 record created with credentials that DMSi provides. The system-defined record, however, will appear masked in this window for security reasons. However, you will be able to see whether it is the “System” record and/or the “Active” record. If a customer would like to use their own S3 credentials, they can create a record in this window with their own S3 bucket name, region, and keys and set it as the “active” record. For non-“system” records, the bucket name and region will display, but the keys will be masked.
AR25535 - How to Calculate Average Cost after quantity adjustment at a different cost
Agility
- Inventory
How to calculate average cost after qty adjustment at a different cost The goal of this article is to help explain how average cost is calculated after a Receiving or Qty Adjustment done at a cost lower than the average cost. Things to keep in mind:
1. UOM Conversions, this example is an FT to FT (1:1) conversion
2. How is the cost carried? This is a cost carried at the Branch level example
a. You can narrow down the Item Activity Viewer to just that Tag, Content, Location level to make it easier to view
b. Make sure you are looking at just one dimension if carried at the dimension level
Question: Why did my Average Cost shoot up after a Receiving Adjustment?
Receiving Adjustment in question: First, you need to figure out the Inventory Valuation BEFORE the adjustment. In this case we are going to take 3843 FT X 4.1974 = 16,130.6082 FT Valuation in Stock before adjustment. As we can see in the Viewer, 2184 FT were adjusted out leaving us with 1659 FT on the RV ADJ line. If 2184 FT were adjusted out at the average cost at the time of the adjustment the valuation would have been: 2184FT X 4.1974 = 9169.1216 Value Removed from Inventory
The actual value removed was:
2184 FT X 2.3763 = 5189.8392 Value Removed from Inventory
The “Amount Abandoned” is the difference between the two amounts:
9169.1216 – 5189.8392 = 3979.2824
The Value of the remaining amount at the current average cost would have been:
1659 FT X 4.1974 = 6963.4866
The Reassigned Amount ends up being the “amount abandoned” + value of remaining quantity at current average cost:
3979.2824 + 6963.4866 = 10,942.769
The remaining qty divided by the “reassigned amount” is what calculates the new Current Average cost and the reason why it shot up in cost:
10,942.769 / 1659 FT = 6.5960
*Due to rounding this amount could be a fraction of a penny off.
AR25548 - Cyberquery (CQ) sample: PV Guest User Listing Report
Agility
- Cyberquery Samples
This report can be run to see the customers that have PV guest user logins and the last day the user logged in. The prompts built into the report will allow those running the report to narrow it down to a particular customer, customer ship-to, sales agent 1, or any combination of the three. The report can be modified to exclude some or all of these prompts.
viewpoint native; define string xcust_id = parameter prompt "ENTER CUSTOMER ID" default "ALL";
number xcust_seq = parameter prompt "ENTER SEQUENCE #" default 0;
string xsa = parameter prompt "ENTER SALES AGENT ID" default "ALL"; file xcust_shipto = access cust_shipto, set cust_shipto:system_id = user_ctl:default_cust_key_sysid, cust_shipto:cust_key = user_ctl:default_cust_key, cust_shipto:cust_key_sysid = user_ctl:default_cust_key_sysid, cust_shipto:seq_num = user_ctl:default_shipto_seq_num; file xgsm_user = access gsm_user, set gsm_user:user_obj = user_ctl:user_obj; where user_ctl:default_cust_key <> "" and ( xcust_seq = xcust_shipto:seq_num or xcust_seq = 0 ) and ( xcust_id = xcust_shipto:cust_code or xcust_id = "ALL" ) and ( xsa begins with xcust_shipto:sales_agent_1 or xsa begins with "ALL" ) list/domain="user_ctl"/duplicates xcust_shipto:sales_agent_1/heading="OUTSIDE SALES REP" xcust_shipto:shipto_name/heading="CUSTOMER NAME" xcust_shipto:seq_num/heading="SHIP TO SEQ" user_ctl:user_or_group_id/heading="USER ID" user_ctl:user_name/heading="USERNAME" xgsm_user:last_login_date/heading = "LOGIN DATE" user_ctl:default_branch/heading="DEFAULT BRANCH" user_ctl:email_address/heading="EMAIL ADDRESS" user_ctl:created_date/heading="CREATED" user_ctl:update_date/heading="UPDATED" sorted by xcust_shipto:sales_agent_1 user_ctl:default_cust_key
AR25552 - How to Set up Reman Scheduling
Agility
- Inventory Control
Using Schedule Manager for Reman Work Orders Schedule Manager has been available to schedule sales order work orders. With Agility v512, Schedule Manager provides the ability to schedule reman work orders. For remans, the operation is what is scheduled. Therefore, each operation must have a department assigned in order for a schedule date and completion date to calculate, allowing the reman operation to display in Schedule Manager.
Setting up an operation for scheduling In order for an operation to calculate the schedule and completion dates, you must assign a Schedule type and Department to the operation. If desired, you may also assign a Schedule resource. In this example, only the Schedule type and Department are assigned.
In Agility, access Data Files > Inv Control Settings > Operation Maintenance Enter the operation you wish to maintain and select Search or use the locator to find and select the operation Once the operation is displayed in the Operation Maintenance window, select the schedule rule icon to add the Schedule type and Department Complete the following steps in the Schedule Rule Maintenance window a. From the Schedule type dropdown, select the Schedule type you wish to assign b. From the Department dropdown, select the Department you wish to assign If applicable, select a Schedule assignment, Schedule resource, Department capacity, and/or Resource capacity Once all selections are made, select OK to exit Schedule Rule Maintenance and save your changes
Creating a reman with a scheduled operation Now that the operation has been set up with a schedule rule, the schedule and completion dates are calculated for the operation based on how the Schedule type and Department are set up in Schedule Maintenance. The steps below provide an example of applying an operation set up for scheduling to a reman.
Create a reman with an operation that is set up for scheduling Once the reman is saved, the system calculates the expected schedule date and expected completion date for the operation The dates are also carried to the reman header If multiple operations with different dates exist on the reman, the header displays the earliest schedule date and the latest completion date for all of the operations Displaying remans in Schedule Manager Now that the reman with a scheduled operation has been saved and the dates have been calculated, the reman operation can be viewed and maintained in Schedule Manager
Access Inventory Control > Schedule Manager and select your search criteria a. Criteria name —If applicable, select a saved viewer from the Criteria name dropdown or use the default viewer for remans, Resource Schedule for Reman b. Schedule date —If you do not wish to select a date range, check All next to Schedule dateNote : Selecting ‘All’ instead of entering a date range may take several minutes to return results c. From —To enter a date range, select whether you wish the From date to be a Run date or an Actual dateRun date —calculate a date based on run date, number of days added or subtracted, and the day basis Example: Current day (5/13/16) minus 2 weekdays = 5/11/16Actual date —enter a date in the format of mm/dd/yy d. To —If entering a date range, select the same date type (Run or Actual) you selected for the From date for the To date and enter the date/date variables e. Tran type/Tran ID —To view all transactions, select <all> for the tran type To view a single reman, select Reman for the Tran type and enter the Reman ID in the Tran ID field f. Schedule type —To search for specific Schedule types, select the desired Schedule types from the dropdown or select <all> to search for all Schedule types g. Department —To search for specific Departments, select the desired Departments from the dropdown or select <all> to search for all Departments h. Schedule resource —To search for specific Schedule resources, select the desired Schedule resources from the dropdown or select <all> to search for all Schedule resources i. Print status —To search for specific Print statuses, select the desired Print statuses from the dropdown or select <all> to search for all Print statuses j. WO/Reman status —To search for specific Reman statuses, select the desired Reman statuses from the dropdown or select <all> to search for all Reman statuses k. Include only work orders/reman work orders with backorders —If you wish to include only reman work orders with backordered items, check the selection box After all selections have been made, select Search Records The work orders and remans that fall within the specified search criteria display in Schedule ManagerNote: If you have operations without a Department with manually entered schedule and completion dates, those reman operations will display in Schedule Manager as well The user can specify how the results are grouped and sorted. In addition, the columns that display in the grid are customizable. See the Help doc for more information on setting up custom views in Schedule Manager. Updating remans in Schedule Manager After completing a search in Schedule Manager, the department, resource, schedule date, and/or print status can be updated using the Update Records option described in the steps below. Note: Updating an operation will fully recalculate the schedule dates for the entire reman.
In Schedule Manager, highlight the reman operation(s) you wish to update Select Update Records Complete the following steps in the Schedule Manager Update window a. Schedule date —If you wish to change the Schedule date, select the Schedule date check box and choose a new date from the New schedule date calendar in the dropdown b. Department —If you wish to change the Department, select the Department check box, the Method to change the Department, and, if applicable, the department you wish to assign from the New department dropdownMethod: Assign New Department —Select this option if you wish to select a different, existing department from the New department dropdown Update Department Based on Current Settings —Select this option if you wish to update the operation on the reman order to match the current department setup c. Resource —If you wish to change the Resource, select the Resource check box, the Method to change the Resource, and, if applicable, the resource you wish to assign from the New resource dropdownMethod: Assign New Resource —Select this option if you wish to select a different, existing resource from the New resource dropdown Update Resource Based on Current Settings —Select this option if you wish to update the operation on the reman order to match the current resource setup d. Print status —If you wish to change the Print status, select the Print status check box and choose the new print status from the New status dropdownNote: Updating the Print status updates the Print status for the entire reman, not just the operation After all selections are complete, select OK to exit the Schedule Manager Update window and save your changes After exiting Schedule Manager Update, all changes are reflected immediately in the Schedule Manager window Printing selected remans in Schedule Manager After completing a search in Schedule Manager, multiple selected remans or a single selected reman can be printed using the steps described below.
In Schedule Manager highlight the reman(s) you wish to print Select Print Reman Work Order The Print Reman Work Orders, Print Options for Reman Work Order, and Select Laser Printer for Reman Work Order windows will display The Print Options for Reman Work Order window will display according to your default print options Make any necessary changes and select OK Complete the following steps in the Select Laser Printer for Reman Work Orders window a. Printer 1 & 2 —Select the printer(s) if you wish to print a copy of the reman form(s) b. Fax —If you wish to fax the reman form(s), select the Fax checkbox and enter the fax number c. Email —If you wish to email the reman form(s), select the Email checkbox and enter the email address(es) After all selections are complete, select OK to exit the Select Laser Printer for Reman Work Orders window and generate the reman form(s) Once printing is complete, the Print Reman Work Orders window closes automatically
AR25594 - How to find SALES Out of Balances (OOB)
Agility
- General Ledger
How to find Sales Out of Balance (OOB) In order to begin the process, you need to know the DATE the OOB occurred and the amount. Each step below is a separate step to research so if you don’t find the answer in step 1, move to step 2, and so on. A. Confirm that GL recon is pulling the necessary SALES GL accounts1. Confirm that SALES GL’s are setup with a GL Recon category of SALES assigned. Go to General Ledger > Reports > G/L Accounts Listing Report. Set the “Include Account Types” field = IC – Income
2. Review the list and confirm that all SALES accounts are marked with GL Recon Category = SALES. Also confirm that any GL account with the category are in fact SALES accounts.
Keep this report available as you work through some of the other steps.
B. Look for JE’s in the SALES G/L Account1. Review the GL for any journal entries as users should not be making JE’s into SALES GL account unless we tell them to make a JE to fix an OOB. General Ledger > Inquiries > GL Detail Inquiry
a. Update the “from” posting period/year to span back at least 2 years or more in the past
b. Posting date from/to should be date span in which the SALES OOB occurred.
c. Click Search to display results and then update the Sort by Source and journal entries will appear on the top.
C. Confirm that SALES GL only has posting with source of A/R Inv 1. Review the GL for any posting to the SALES GL and confirm that all entries have a source equal to “A/R Inv”. Go to General Ledger > Inquiries > GL Detail Inquiry
a. Select the posting period in which the out of balance occurred
b. Posting date from/to should be date span in which the Sales OOB occurred.
D. Run programs for unposted entries1. Go to General Ledger > Posting Functions > A/R posting to G/L
2. Select the correct branch and posting period for the date the OOB occurred and click OK. An audit report will generate with any pending entries that posting. Looks to see if that amount matched your OOB.
3. If AR posting did not fix, run for General Ledger > Posting Functions > Post Unposted Activity.
4. Select branch, select the posting period for the date, set Original = ALL & Run. An audit report will generate with any pending entries that posted. Look to see if that amount matched your OOB.
E. Run AR Commission Viewer to find Customer Charges and confirm setupOn you GL Recon report, charges set to effect GM and setup to post SALES GL, the value will be contained within SALES GL value and SALES will stay in balance on GL Recon. If charges are affecting GM are NOT set to affect a SALES GL, the value of the charge will display in a separate column than normal sales. It may appear as if SALES is out of balance but the difference should match the amount displaying in the Charges/Cost GM column.
1. Go to Accounts Receivable > Commission Viewer
2. Select the branch in which the out of balance occurred
3. Select sales agent position 1 for all sales agents and all other positions to none as this will prevent you from seeing the same data twice if you have more than one sales agent typically assigned to your Sales Orders.
4. Enter the invoice date range for when the out of balance occurred
5. Select the column display indicated in the screenshot and sort by “Charge Type”
6. If the value of your Sales is out of balance by the value of a charge, you will need to look at the Customer Charges setup. Go to Data Files > Charges and Costs > Customer Charges. Customer charges affecting inventory should be set to post to SALES
F. Review Sales Account Parameters for Transfer sale types Please note that this step only applies if you invoice your own branches for material transfers, creating A/R Invoice and A/P accruals.
1. Go to Data Files > Sales Order Settings > Sales Account Parameters
2. Pull up the parameters for your transfer sale type.
a. If you invoice your branches and create A/R and A/P records, you should have a special transfer SALES account that is isolated to transfer sales as transfer sale types are excluded from SALES reporting in Sales Analysis and other sales reports.
AR25592 - How to find COGS Out of Balance (OOB)
Agility
- General Ledger
How to find COGS Out of Balance (OOB) In order to begin the process you need to know the DATE the OOB occurred and the amount. Each step below is a separate step to research so if you don’t find the answer in step 1, move to step 2, and so on. A. Confirm that GL recon is pulling the necessary COGS GL accounts1. Confirm that COGS GL’s are setup with a GL Recon category of COGS assigned. Go to General Ledger > Reports > G/L Accounts Listing Report. Set the “Include Account Types” field = EX – Expense
2. Review the list and confirm that all COGS accounts are marked with GL Recon Category = COGS. Also confirm that any GL account with the category are in fact COGS accounts.
Keep this report available as you work through some of the other steps.
B. Look for JE’s in the COGS G/L Account1. Review the GL for any journal entries as users should not be making JE’s into COGS GL account unless we tell them to make a JE to fix an OOB. General Ledger > Inquiries > GL Detail Inquiry
a. Update the “from” posting period/year to span back at least 2 years or more in the past
b. Posting date from/to should be date span in which the inventory OOB occurred.
c. Click Search to display results and then double click the Source column to sort by that and journal entries will appear on the top.
C. Confirm that COGS GL only has posting with source of A/R Inv 1. Review the GL for any posting to the COGS GL and confirm that all entries have a source equal to “A/R Inv”. Go to General Ledger > Inquiries > GL Detail Inquiry
a. Select the posting period in which the out of balance occurred
b. Posting date from/to should be date span in which the inventory OOB occurred.
D. Run programs for unposted entries1. Go to General Ledger > Posting Functions > A/R posting to G/L
2. Select the correct branch and posting period for the date the OOB occurred and click OK. An audit report will generate with any pending entries that posting. Looks to see if that amount matched your OOB.
3. If AR posting did not fix, run for General Ledger > Posting Functions > Post Unposted Activity.
4. Select branch, select the posting period for the date, set Original = ALL & Run. An audit report will generate with any pending entries that posted. Look to see if that amount matched your OOB.
E. Run AR Commission Viewer to find Order Costs and confirm setup 1. Go to Accounts Receivable > Commission Viewer
2. Select the branch in which the out of balance occurred
3. Select sales agent position 1 for all sales agents and all other positions to none as this will prevent you from seeing the same data twice if you have more than one sales agent typically assigned to your Sales Orders.
4. Enter the invoice date range for when the out of balance occurred
5. Select the column display indicated in the screenshot and sort by “Cost Type”
6. If the value of your COGS out of balance is the value of a header cost, you will need to look at the Order Cost setup. Go to Data Files > Charges and Costs > Order Costs.
a. The G/L debit should be pointing to your COGS account
b. The G/L credit account should not be going to COGS account
c. The credit and debit accounts should not be the same.
F. Review Sales Account Parameters for Transfer sale types 1. Go to Data Files > Sales Order Settings > Sales Account Parameters
2. Pull up the parameters for your transfer sale type.
a. If you transfer material at cost, then your “cost-of goods” section should point to a branch transfer clearing account
b. If you invoice your branches and create A/R and A/P records, you should have a special transfer COGS account that is isolated to transfer sales as transfer sale types are excluded from COGS reporting in Sales Analysis and other sales reports.
AR25649 - How to download the List of Reorder Info query and run it.
Agility
- SPO
How to download the List of Reorder Info query and run it.
Log into the Wedge. Go to dmsi.com/wedge . Put your username and password in and click Login to Account.
Click on the Articles tab. Choose a category equals of Cyberquery Samples, then type Reorder info the Articles contains field. Click Search. Click on the link for the List of Reorder Information article.
A new window will open with the text of the query. Highlight the text that contains the query (starting at /* This query will...). Then type Control C (this is Copy).
Go into Agility and click on the Report Writer button. Then click on VCQ Report Writer.
The Cyberquery report wizard may pop open: if it does, click Cancel.
Click on the Select Language Editor button to switch the view.
Click your cursor into the Enquiry section and paste the query (Control V).
To save the query, click on the Save button.
The Save enquiry as box will come open. Click on the Up One Level button to move to the cq_reports folder.
In the cq_reports folder, put list_of_reorder_info in as the File Name and click Save.
You can now run the report by clicking the Run button (or hitting the F6 button). When you run, you will need to specify some answers to prompts about branch, buyer, supplier, product group and stock items.
If you would like to run the report from your dashboard or from the VCQ Reports, you will need to compile the report. To compile, go to Report Writer/VCQ Report Compiler.
In the Report name field, type in list_of_reorder_info.eq. Click Run.
A report will print to your screen. If the compile went through, it will say Enquiry “list_of_reorder_info” compiled-no errors.
To run the report from the VCQ Reports, go to the Report Writer/VCQ Reports.
Click the + next to the cq_reports folder.
Find the list_of_reorder_info report, click on it then click Run.
To add the report to your dashboard, go to the Saved Reports section of the Dashboard. Click the Add Custom Report link.
In the Report name field, type in list_of_reorder_info.eq. In the Text to display, you can change this field to be whatever you want to call your report. Click OK.
To run it, click on the Run link next to the name of the report.
AR25664 - Item Branch Record Not Found Error in Sales Analysis Conversion
Agility
- System Administration
Item Branch Record Not Found Error in Sales Analysis Conversion
The user is running a Sales Analysis Conversion. They have codes set up if an invalid Customer, Product Group, Item, Sales Agent, or Location is found. When they run the conversion there are several items that are not processing with an error message of Item Branch Record Not Found. The items are all invalid items but for some reason the system is not using the conversion template set up when the conversion was run.
The issue is that the invalid items were valid items at one time and had Item Dimension Records built before the items were deleted from the system. The Sales Analysis Conversion program checks for the Item Dimension Record first, finds a valid record, then looks for an actual item record. The system will not use the template conversion item because a valid Item Dimension Record was found.
To process these records, contact DMSi to remove the invalid Item Dimension Records (item_dim table) prior to processing the Sales Analysis file.
AR25751 - How to Set up SO and CM reason codes
Agility
- Sales Orders
Setup · The first place to go for set up is SO Parameters.
System Administration > Module Controls > Sales Order Parameters
· On the SO/Quote/CM 2 tab, select the desired value for the field “Reason code when Canceling SO/CM”. There are multiple options depending on how you want to prompt:
o Do Not Prompt – This is the default and does not prompt for a reason.
o Prompt and do not require – displays the prompt but does not require a reason to be selected.
o Require reason code only – displays the prompt and requires a reason code, but does not require a comment.
o Require reason code and comment – displays the prompt and requires both a reason code and a comment.
· The second part of the setup that needs to be done is to set up the reason codes. Data Files > Lookup Codes > Reason Codes
· There are 2 new types of Reason codes that can now be set up. Those are:
o Canceled Sales Order
o Canceled Credit Memo
· When setting up these new reason codes, the only relevant settings are: Type, Reason, and Available for Use. You must independently set up codes for use in SO’s and CM’s.
Canceling an order with the SO Parameter set to Prompt. · Like before you just need to cancel the order.
· You will get this prompt when canceling the order. You can select the reason code and type in a comment describing why the order is being canceled.
o Red Text shows required fields on the SO Parameter. If not required, text shows black.
· If you go back into the Canceled SO, you will now see an icon next to the Status.
· Selecting that icon will show you the date the transaction was canceled, the user that canceled it, and the reason code and comment if they were used.
· Additionally, columns for Cancel Comment and Cancel Reason Code have been added to the SO Viewer so you can add those and see the reason reasons from multiple canceled orders at the same time through the viewer.
AR25818 - Minimum Order Hold Processing
Agility
- Customer
Minimum Order Hold Processing
Use the minimum order hold feature to control shipping costs by requiring a customer ship-to location to order a minimum amount before you make a delivery to them.
To set up minimum order hold for a customer ship-to:
Go To > Data Files > Customer Information > Customers > Define Ship-To
Under the Default Flags tab, enter the desired amount in the minimum order hold amount field.
To set up minimum order holds that are branch specific :
From the Ship-to record, select the Maintain Branch Settings icon.
You will have to enable default flags, and then you can set a minimum order hold for the branch selected.
To update the minimum order hold processing amount for multiple customers via mass update:
Go To > System Administration > Mass Updates > Customer Mass Update
Field Name: Minimum Order Hold Amount; Enter the desired new value and click add.
Validate the procedure and then run the process. Click Yes When prompted.
The apply minimum order hold rules flag must be set on sale types and ship via methods that will be used with minimum order requirements.
Go To > Data Files > Sales Order Settings > Sale Types
Go To > Data Files > Ship Via Methods
After saving a sales order that does not meet the minimum order hold requirements, the status will change to Minimum Order Hold . Once the order is put on hold, it cannot be processed further until it is released or until the customer ship-to meets the minimum order requirements. (The order will not be accessible in Order Processing.)
Create a sales order viewer to use as a minimum order hold queue .
Go To > Sales Orders/Quotes >Viewers > SO Viewer
Within the Order Criteria tab, set Included minimum order hold/on hold orders to “Only minimum order hold/ on hold orders”.
Review security to limit which users can release orders from minimum order hold. “Release SO from Minimum Order Hold/On Hold” security action controls whether you can release an order from minimum order hold or unset the “On Hold” flag in Sales Order Entry. The action also controls whether you can release orders via the “Release from on hold/min order hold” process selection from the sales order viewer results screen.”
Go To > System Administration > Security Administration > Action Allocation
AR25878 - How to download a Cyberquery Samples query and run it.
Agility
- Cyberquery Samples
How to download a Cyberquery Samples query and run it. Log into the Wedge. Go to dmsi.com/wedge . Put your username and password in and click Login to Account. Click on the Articles tab. Choose a category equals of Cyberquery Samples, then type what you are looking for in the 'Article contains' field. Click Search. When you find the right query, click the link for the article. A new window will open with the text of the query. Highlight the text that contains the query (starting at /* This query will...). Then type Control C (this is Copy). Go into Agility and click on the Report Writer button. Then click on VCQ Report Writer. The Cyberquery report wizard may pop open: if it does, click Cancel. Click on the Select Language Editor button to switch the view. Click your cursor into the Enquiry section and paste the query (Control V). To save the query, click on the Save button. The Save enquiry as box will come open. Click on the Up One Level button to move to the cq_reports folder. In the cq_reports folder, type what you want the name of the query to be (using the _ character instead of spaces and all lowercase letters), then click Save. You can now run the report by clicking the Run button (or hitting the F6 button). If you would like to run the report from your dashboard or from the VCQ Reports, you will need to compile the report. To compile, go to Report Writer/VCQ Report Compiler. In the Report name field, type in the name of your report (like list_of_reorder_info.eq). Click Run. A report will print to your screen. If the compile went through, it will say something like Enquiry “list_of_reorder_info” compiled-no errors. To run the report from the VCQ Reports, go to the Report Writer/VCQ Reports. Click the + next to the cq_reports folder. Find the list_of_reorder_info report, click on it then click Run. To add the report to your dashboard, go to the Saved Reports section of the Dashboard. Click the Add Custom Report link. In the Report name field, type the name of the report. In the Text to display, you can change this field to be whatever you want to call your report. Click OK. To run it, click on the Run link next to the name of the report.
AR25919 - Cyberquery Shortcut keys
Agility
- Cyberquery
Cyberquery Shortcut Keys
CQW shortcut keys Action Details Key Clone Clone this Cyberquery window. Launches a new instance of CQW with the query or macro from the current window loaded as an Untitled document. CTRL-SHIFT-C Find Find text CTRL-F Find next Find next occurrence of text F3 or down arrow keyFind previous Find previous occurrence of text Shift-F3 or up arrow key Find and replace (Windows)Find and replace text CTRL-H Find and replace (HTML)Find and replace text CTRL-ALT-H Help Displays help about the currently selected pane F1 New query Create a new query CTRL-N Open query Open an existing query CTRL-O Open next file Opens the next file from the latest Open dialog, including any filtering CTRL-SHIFT-n Open previous file Open the previous file from the latest Open dialog, including any filtering CTRL-SHIFT-p Paste as new macro Pastes a macro from the Windows clipboard into CQW CTRL-SHIFT-V Point-and-click help Displays help on the next item that you click SHIFT-F1 Print report Print the report CTRL-P Quick run Refresh the report display with cached data F5 Run Refresh the report display with data from the server F6 Run In version 8.21-1A and later: When the Record Selection dialog box is open pressing F6 refreshes the report display with data from the server and closes the dialog box. F6 Run In version 8.21-1A and later: When the Record Selection dialog box is open pressing Shift-F6 refreshes the report display with data from the server and leaves the dialog box open. Shift-F6 Save query Save the query CTRL-S Switch Switch from the Language Editor to the Report Editor SHIFT-ALT-R Switch Switch from the Report Editor to the Language Editor SHIFT-ALT-L
Report Editor and Visual Editor Shortcut Key
The following shortcut key can be used with the report editor or the visual editor.
Report editor and visual editor shortcut key Action Details Key Switch Switch focus between panes TAB
Report Wizard Shortcut Keys
The following shortcut keys can be used with the Report Wizard (on its first page).
Report Wizard shortcut keys Action Details Key Display the Open dialog box Open a query CTRL-O Paste query Paste query from Windows clipboard into CQW CTRL-V Paste macro Paste macro from Windows clipboard into CQW CTRL-SHIFT-V
Report Pane Shortcut Keys
The following shortcut keys can be used with the report editor , visual editor and language editor but only when the report pane is selected.
Report pane shortcut keys Action Details Key Clear Clears the current selection ESC Find Find text CTRL-F Find and replace (Windows)Find and replace text CTRL-H Find and replace (HTML)Find and replace text CTRL-ALT-H Maximize report viewer Pressing this once closes the other panes, and makes the report pane as large as possible. Pressing again returns the report pane to its original size.
F8 or SPACEBAR
Options Pane Shortcut Keys
The following shortcut keys can be used in the Options pane.
Options pane shortcut keys Action Details Key Expand Expands the tree for the currently selected table + (numeric keypad)Expand everything Expands everything under the current selection * (numeric keypad)Collapse Collapses the tree for the currently selected table - (numeric keypad)Collapse/Go to Parent Collapses the current selection if expanded otherwise goes to the parent LEFT ARROW Expand/Go to first child Expands the current selection if it is not expanded, otherwise goes to the first child
Editing Shortcut Keys
The following table shows the Windows shortcut keys that can be used when editing text in dialog boxes and the language editor.
Editing shortcut keys Action Details Key Copy Copies selected text to clipboard CTRL-C Cut Removes selected text and places on clipboard CTRL-X Delete Delete the character to the right of the cursor or the selected text DELETE Delete line Deletes the current line CTRL-U Delete to end of line Deletes from the cursor to end of line CTRL-K Delete word right Deletes from the cursor to the end of the current word CTRL-DELETE Delete word left Deletes from the cursor to the start of the current word CTRL-BACKSPACE Insert/Over-write Toggles between over-write and insert mode INSERT Move down Moves the cursor down one line DOWN ARROW Move left (character) Moves cursor to the left one character at a time LEFT ARROW Move left word Moves the cursor to the left one word at a time CTRL-LEFT ARROW Move right (character) Moves cursor to the right one character at a time RIGHT ARROW Move right (word) Moves the cursor to the right one word at a time CTRL-RIGHT ARROW Move to end (line) Moves the cursor to the end of the line END Move to end (text) Moves the cursor to the end of the text CTRL-END Move to start (line) Moves the cursor to the beginning of the line HOME Move to start (text) Moves the cursor to the beginning of the text CTRL-HOME Move up Moves the cursor up one line UP ARROW Paste Pastes current clipboard contents CTRL-V Redo Last undone action is redone CTRL-Y Select Selects all text in current pane or dialog box CTRL-A Select left (character) Selects text to the left one character at a time SHIFT -LEFT ARROW Select left (word) Selects text from the cursor to the left one word at a time SHIFT-CTRL-LEFT ARROW Select right (character) Selects text to the right one character at a time SHIFT-RIGHT ARROW Select right (word) Selects text from the cursor to the right one word at a time SHIFT-CTRL-RIGHT ARROW Select to start (line) Selects text from the cursor to the beginning of the line SHIFT-HOME Select to start (text) Selects text from the cursor to the beginning of the text SHIFT-CTRL-HOME Select to end (line) Selects text from the cursor to the end of the line SHIFT-END Select to end (text) Selects text from the cursor to the end of the text SHIFT-CTRL-END Select down Selects text from the cursor, down one line at a time CTRL-DOWN ARROW Select up Selects text from the cursor up, one line at a time CTRL-UP ARROW Undo Last action is undone CTRL-Z
AR25926 - Buyer Limits VCQ Report Setup
Agility
- Purchasing
Buyer Limits VCQ Report Setup This report looks at PO’s created on current date and have not yet been printed. Then it compares the total cost on the PO to the buyer limit. If the cost is greater, it will print the PO info on the report .
This report works in conjunction with an action allocation and setting up Buyer limits.
1. Set up Buyer Limits and deny action to print PO’s over Buyer purchasing limits
a. Go to Data Files > Supplier Information > Buyers. Set your buyer limit.
The system restricts the purchase order from being printed if the order total exceeds the limit for the buyer(s) assigned to the non-transfer purchase order. To print the order, the order total must be reduced or a user with permission granted to the 'Print purchase order over buyer purchase limit' security action can print the order.
b. Go to System Administration > Security Administration > Action Allocation
Deny permission to “Print Purchase Order Over Buyer Purchase Limit”
2. Create the VCQ Report
a. Open VCQ Report Writer and switch to language editor
b. Click on File > New Enquiry
c. On the enquiry screen paste in the report below.
d. Save your enquiry. Naming recommendation: buyer_limits
where ( po_header:created_date = todaysdate ) and po_header:printed = 0 list /nodetail/noreporttotals/nobanner/domain="po_header" po_header:system_id po_header:buyer suppname:supplier_code po_detail:ext_cost buyer:per_po_limit po_header:po_idsorted by po_header:system_id po_header:buyer po_header:po_idend of po_header:po_id if total[po_detail:ext_cost] > buyer:per_po_limit then { po_header:system_id/noheading/align=po_header:system_id po_header:buyer/noheading/align=po_header:buyer po_header:po_id/noheading/nocommas/align=po_header:po_id suppname:supplier_code/noheading/align=suppname:supplier_code total[po_detail:ext_cost]/align=po_detail:ext_cost buyer:per_po_limit/noheading/align=buyer:per_po_limit }
Automated Processing Setup 1. Create a new job/queue called Buyer Limits
a) Go to System Administration > Restricted Processing > Automated Processing > Queue Maintenance
b) Click the plus sign on the new job tab and fill out as follows.
c) The Report subfolder name is only needed if you saved the file into a subfolder in the cq reports directory.
d) Set the email address of any users that should receive the Buyer Limits report.
e) Set the report data type to PDF or excel
f) Save the job and create a queue that will run this job once a day or multiple times a day, however you desire. In the example below the job is set up to begin running at 6am CST, then run every two hours and stopping at 9pm CST.
g) Note you can also run this report on demand by placing this report on your dashboard or accessing and running through VCQ Reports to get a listing of PO’s that are over their buyer limits throughout the day without waiting for the normal runtimes to generate the report.
AR25945 - How to find A/R Trade Out of Balance (OOB)
Agility
- A/R
How to find A/R Trade Out of Balance (OOB)
In order to begin the process, you need to know the DATE the OOB occurred and the amount. A/R OOB occurs when the A/R Trade G/L account balance does not equal the A/R Aged Trail Balance report total for the “Open Amt” column. Each step below is a separate step to research so if you don’t find the answer in step 1, move to step 2, and so on. This documents helps you identify the issue but you may still need to contact DMSI support for research and resolution.
A.
Confirm that G/L Recon is pulling the necessary A/R Trade GL accounts
1.
Confirm that A/R Trade G/L accounts are setup with a G/L Recon category of A/R Trade assigned. Go to General Ledger > Reports > G/L Accounts Listing Report. Set the “Include Account Types” field = AS – Asset
2.
Review the list and confirm that all A/R accounts are marked with G/L Recon Category = A/R Trade. Also confirm that any G/L accounts with the category are in fact A/R Trade accounts.
Keep this report available as you work through some of the other steps.
B.
Run programs for unposted entries
1.
Go to General Ledger > Posting Functions > A/R posting to G/L
2.
Select the correct branch and posting period and posting year for the date the OOB occurred and click OK. An audit report will generate with any pending entries that posted. Looks to see if that amount matched your OOB.
3.
If the A/P posting program results in no postings then run for General Ledger > Posting Functions > Post Unposted Activity.
4.
Select branch, select the posting period for the date, set Original = ALL & Run. An audit report will generate with any pending entries that posted. Review to see if that amount matched your OOB.
C.
Look for JE’s in the A/R Trade G/L Account
1.
Review the G/L for any journal entries as users should not be making JE’s into A/R Trade G/L account unless we tell them to make a JE to fix an OOB.
2.
General Ledger > Inquiries > G/L Detail Inquiry
a.
Update the “from” posting period/year to span back at least 2 years or more in the past
b.
Posting date from/to should be date span in which the A/R Trade OOB occurred.
c.
Click Search to display results and then update the Sort by to Source and journal entries will appear on the top.
D.
Confirm there are only postings to A/R Trade where source = A/R
A/R Trade is one of those accounts that can have entries from A/R
1.
Go to General Ledger > Inquiries > G/L Detail Inquiry
a.
Select the posting period in which the out of balance occurred
b.
Posting date from/to should be date span in which the A/P Clearing OOB occurred.
c.
Click Search to display results and Sort by Source. Scan the entries for anything other than A/R xxxx
E.
Confirm offset GL posting for AR entries
Based on the date your A/R Trade went out of balance, pull the A/R – G/L Detail Report for that branch and the activity on that date. You will be reviewing the report to confirm that the offset GL’s listed are NOT A/R Trade G/L account. If you see offset equal to A/R Trade G/L account then that means both the DR and the CR posted to A/R Trade and this would be the reason for your out of balance. You will need to do a journal entry to correct.
1.
Go to Accounts Receivable > Reports > A/R G/L Detail Reports
2.
Select the branch
3.
Set Report type = Detail
4.
Set Activity date for date of OOB
5.
Select appropriate Posting Year
6.
Select appropriate Posting period and RUN
F.
Search A/R Aged Trail Balance Report for OOB value
In some cases we can find the offending records via search of A/R Aged Trial Balance.
1.
Go to Accounts Receivable > Reports > A/R Aged Trial Balance
2.
On the Select Criteria tab, select the appropriate branch.
3.
On the Report Options tab:
a.
Select Report Type = Summary and detail report.
b.
Sort & Subtotal = Customer Name or Customer ID
c.
Run
d.
Look at top of report for any Invoices/CM without a customer name/cust ID.
e.
At the top left of the cyberquery window, select Edit then Find…
f.
The “find” will appear at the bottom left of the window, key in exact amount of OOB variance and click Next – it will highlight the amount found on the report.
G.
Run query on AR records created via Open Item Entry
Usually during Go Live or an acquisition, people may create AR records via conversion or manually via Open Item Edit. None of these actions create an entry to the General Ledger; they only create the open AR record. This query will aid you in identifying any AR records create via Open Item Entry as this may be the cause of the OOB.
1.
Go to Report Writer – VCQ Report Writer
If you get the Cyberquery Wizard window, click Cancel button
2.
Click the Keyboard icon at the top center of the screen.
3.
Paste the text from step 4 into the “enquiry” section of the report writer screen and click the running man icon to run the report. Search for date/amount of OOB. You will need to create JE between A/R Trade and offset G/L account (probably sales/converted sales GL).
4.
TEXT for query
viewpoint native;
where
aropen:open_item_entry =
1
and aropen:open_amt <>
0
list/duplicates/domain="aropen"
aropen:customer_code
aropen:created_date
aropen:tran_id
aropen:ref_type
aropen:ref_num
aropen:open_flag
aropen:open_amt
aropen:open_item_entry
sorted by
aropen:Created_date
aropen:open_item_entry
aropen:open_amt
AR25984 - Cyberquery Troubleshooting Tips
Agility
- Cyberquery
AR26001 - Cyberquery (CQ) Sample: Table Sharing for All Branches
Agility
- Cyberquery Samples
AR26128 - How to access open orders for a customer within order entry?
Agility
- Sales Orders
To quickly access a list of open orders for a customer you can quickly run a Open Sales Order Viewer from the toolbar. The system automatically loads the customer from the sales order as the customer for the viewer. With the viewer results you then open a related tran by simply double clicking a transaction record, or keep the pending order list displayed in the background while continuing to work on the new order.
Initial Setup Instructions
To define the viewers you want to access within sales order entry complete the following:
Set up a Sales Order Viewer record. On the Information tab of the sales order entry ribbon, click the Saved Viewers toolbar icon. Select 'Add Viewer' Locate the viewer you want to display on your list within sales order entry and click OK. The system adds the selected viewer to your list. How to run the viewer from within sales order entry
Either start a new order and enter the customer shipto, or display an existing order to populate the customer and shipto sequence fields. Click Saved Viewers toolbar icon, locate the desired viewer, then click Run. The system automatically populates the customer into the viewer criteria prior to running the viewer. Note
The Saved Viewers list is custom to each user so each sales agent can customize their viewer list.
AR26147 - Query Name: Item Verification_Thick and Width
Agility
- Inventory
Query Name: Item Verification_Thick and Width
Related Case: 1932734
Related Project: 114584 in v544 – Sheet good item type (standard thickness, width, size format)
When setting Standard Thickness or Standard Width on a sheet good item type record assigned to existing item records, the item records need to be updated with the new settings. While support program 'updstdwidth' exists allowing you to assign the standard width to all dimensions on selected items, there may be records which did not meet the right conditions to automatically complete the update.
The attached query allows you to identify those item records which need manual review and update. The query identifies two types of records:
1. item dimension records where the thickness or width value does not match the standard thickness or standard width that is set up on the item
2. item records where multiple widths or thicknesses exist which the support program could not update automatically
After running the report, review the records and update the Standard Thickness and Standard Width fields accordingly.
NOTE: This report should be run after hours as it could take extra time to process.
Query Details:
/* Note this query must be copied into a macro. You can open a macro by either using the control M or select ""File","New", "New Macro". */
-----Extract valid Branches
where system_id not one of "00CORP"
list /domain="system_file"/nodefaults/pagelength=0
',"'+system_file:system_id+"-"+company_name+'"'
top of report
'"ALL"'
;run
rreplace branch_list.cq
cli mv branch_list.cq branch_list.inc
------Extract Valid Types -------------
where item_type:type = "Sheet Good"
list /domain="item_type"/nodefaults/pagelength=0
',"'+item_type:item_type_name+'"'
top of report
'"ALL"'
;run
rreplace type_list.cq
cli mv type_list.cq type_list.inc
----------------- Enter Prompts ------------------
define string xpara_branch = parameter/prompt="Enter Branch or ALL" default "ALL"
valid
include "branch_list.inc"
define string para_type = parameter/prompt = "Enter Item Type or ALL" default "ALL"
valid
include "type_list.inc"
define string para_check = parameter/prompt="Verify Thickness or Width" default "Thickness"
valid "Thickness","Width"
define string para_validate =parameter/prompt="Verify to item or check inconsistant dimensions" default "Item"
valid "Item", "Inconsistant Dimensions"
define xbranch = subfield(xpara_branch,"-",1)
list /domain="dummy"/nodefaults/pagelength=0
xbranch/newline
para_type/newline
para_check/newline
para_validate/newline
;run
rreplace report_par.cq
cli mv report_par.cq report.par
---------------Print Verification Report -------------------------------
define string para_branch = parameter/prompt="Enter Branch or ALL" default "ALL"
define string para_type = parameter/prompt = "Enter Item Type or ALL" default "ALL"
define string para_check = parameter/prompt="Verify Thickness or Width" default "Thickness"
valid "Thickness","Width"
define string para_validate =parameter/prompt="Verify to item or check inconsistant dimensions" default "Item"
valid "Item", "Inconsistant Dimensions"
define file system_file = access system_file,
set system_id = item_content_def_branch:system_id
define file item_type = access item_type,
set system_id = "00CORP",
set item_type_name = item:item_type_name
define number xcheck = if para_check ="Thickness" then item_content_def_branch:thickness
else if para_check ="Width" then item_content_def_branch:Width
define number xitem_size_check = if para_check ="Thickness" then item:standard_thickness
else if para_check ="Width" then item:standard_width
define number xinvalid_size = if para_validate = "Item" and xitem_size_check = xcheck then 0
else if para_validate = "Item" and xitem_size_check <> xcheck then 1
else 0
define xcount = 1
define xnum_sizes = if total[xcount,xcheck] = 1 then 1 else 0
define xsize1 = if total[xnum_sizes,item_content_def_branch:system_id] = 1 and total[xcount,xcheck] = 1 then xcheck else 0
define xsize2 = if total[xnum_sizes,item_content_def_branch:system_id] = 2 and total[xcount,xcheck] = 1 then xcheck else 0
define xsize3 = if total[xnum_sizes,item_content_def_branch:system_id] = 3 and total[xcount,xcheck] = 1 then xcheck else 0
define xsize4 = if total[xnum_sizes,item_content_def_branch:system_id] = 4 and total[xcount,xcheck] = 1 then xcheck else 0
define xsize5 = if total[xnum_sizes,item_content_def_branch:system_id] = 5 and total[xcount,xcheck] = 1 then xcheck else 0
define xsize6 = if total[xnum_sizes,item_content_def_branch:system_id] = 6 and total[xcount,xcheck] = 1 then xcheck else 0
define xsize7 = if total[xnum_sizes,item_content_def_branch:system_id] = 7 and total[xcount,xcheck] = 1 then xcheck else 0
define xsize8 = if total[xnum_sizes,item_content_def_branch:system_id] = 8 and total[xcount,xcheck] = 1 then xcheck else 0
define xsize9 = if total[xnum_sizes,item_content_def_branch:system_id] = 9 and total[xcount,xcheck] = 1 then xcheck else 0
define xsize10 = if total[xnum_sizes,item_content_def_branch:system_id] = 10 and total[xcount,xcheck] = 1 then xcheck else 0
define xzero_record = if item_content_def_branch:thickness = 0 and width = 0 and length = 0 then "Y" else "N"
define xvalid = if (item:item_type_name = para_type or
(para_type = "ALL" and item_type:type = "Sheet Good"))
and ((xitem_size_check > 0.0000000000 and para_validate = "Item") or para_validate <> "Item" )
and xzero_record = "N"
then "Y"
where item:stock_to_pc_calc > " "
and (item_content_def_branch:system_id = para_branch or para_branch = "ALL")
and xvalid = "Y"
list /domain="item_content_def_branch"/nobanner/duplicates/nodefaults --/nodetail --/hold="hf_variances"
--#item_content_def_branch:item/name="prt_item"
--#thickness width length
--#item:description/name="prt_desc"
--#xnum_sizes
--#item:standard_thickness/heading="STD Width"
--#item:standard_width/heading="STD Length"
--#xsize1/heading=para_check+"1"
--#xsize2/heading=para_check+"2"
--#xsize3/heading=para_check+"3"
--#xsize4/heading=para_check+"4"
--#xsize5/heading=para_check+"5"
--#xsize6/heading=para_check+"6"
--#xsize7/heading=para_check+"7"
--#xsize8/heading=para_check+"8"
--#xsize9/heading=para_check+"9"
--#xsize10/heading=para_check+"10"
--#xinvalid_size
--#xcheck
--#xitem_size_check
sorted by item_content_def_branch:item system_id xcheck
end of item_content_def_branch:system_id/noheading
if
(( para_validate <> "Item" and total[xnum_sizes] > 1 )
or (para_validate = "Item" and total[xinvalid_size] <> 0 )
)
then {
item_content_def_branch:item
item:description
item_content_def_branch:system_id
system_file:company_name
item:standard_thickness
item:standard_width
item:item_type_name
total[xnum_sizes]/name="num_size"
total[xsize1]/name="size1"
total[xsize2]/name="size2"
total[xsize3]/name="size3"
total[xsize4]/name="size4"
total[xsize5]/name="size5"
total[xsize6]/name="size6"
total[xsize7]/name="size7"
total[xsize8]/name="size8"
total[xsize9]/name="size9"
total[xsize10]/name="size10"
}
top of page
"Item #"/align=item_content_def_branch:item
"Item Description"/align=item:description
"Branch ID"/align=item_content_def_branch:system_id
"Branch Name"/align=system_file:company_name
"# of sizes"/align=num_size
"STD Thickness"/align=item:standard_thickness
"STD Width"/align=item:standard_width
"Item Type"/align=item:item_type_name
para_check+"1"/align=size1
para_check+"2"/align=size2
para_check+"3"/align=size3
para_check+"4"/align=size4
para_check+"5"/align=size5
para_check+"6"/align=size6
para_check+"7"/align=size7
para_check+"8"/align=size8
para_check+"9"/align=size9
para_check+"10"/align=size10
;run/parameter=report.par
rreplace item_verification.cq
view
AR26186 - How to implement OrderPad
Agility
- OrderPad
Implementation Requirements Install the Automated Processing client on a computer that has Internet access and is running constantly. If you are already using supplier returns, there are no additional requirements for use with OrderPad.
Implementation First Steps
Use the Customer Item Quicklist Criteria screen to define criteria records for building quicklists to display based on the customer within the OrderPad screen.
Go to: System Administration > Restricted Processing > Automated Processing > Quicklist Criteria
You can build a quicklist of the top items in the following categories for branch and customer sold-to and/or ship-to or customer reporting group. Top items are based on invoiced orders only.
- Hits – include items sold most often to the customer - Total sales amt – include items with the largest total sales amount sold to the customer - GM % – include top items based on the highest gross margin percentage on the items
** Regardless of criteria, the system creates a unique Quicklist record for each branch, customer, customer level (e.g. sold-to and ship-to record).**
Implementation Next Steps
Go to: System Administration > Restricted Processing > Automated Processing > Queue Maintenance
- Create a Job for each saved criteria - Add job to queue to run on proper interval
If you wish to see supplier rebate information in OrderPad, go to: Sales Orders/Quotes > OrderPad > Right click in the grid > Select Edit Custom View > Add the 'Rebate' field to the 'Show these columns' list
Implementation Final Steps
Start using OrderPad. Agility automatically applies rebates to items in the OrderPad and to new orders when they are released.
If you have access to the 'View Other Cost' security action and the Show Cost option is set, you can review and update supplier rebates for a detail line.
See it in Action
Fastest Way to Check Pricing and Availability for a List of Items
Fastest Way to Check Availability and Price of Tally Items
AR26188 - Why is My Macro not Running from the Dashboard?
Agility
- Cyberquery
AR26217 - How to Implement and Automate the Customer Net Profitability Report
Agility
- Sales Orders
Implementation Requirements
Install the Automated Processing client on a computer that has
Internet access and is running constantly.
Implementation First Steps
Determine what the cost per line or transaction for different sale types is. To determine this use cost to serve measurements or simply take operating expenses (not contributing to Gross Margin) divided by number of sales orders or lines for a branch for a time period. These cost to serve figures are used to 'Apply additional costs per Transaction or Line Item' on the Report Options tab of the Customer Net Profitability Report.
Implementation Next Steps
Go to: Sales Orders > Queries/Reports > Customer Net Profitability On the Selection Criteria Tab - Select the branch used for cost to serve figures in the first step. - Select the Customer range, Sale Type range, Sales Agent range and Entered by for the report. Typically 'All' is selected for each of these criteria. - Select the transaction type, typically 'Invoices'. - Select the relative date for the report, typically a range like the past 3, 6 or 12 months. On the Report Options Tab - Typically the Cost Type is 'Default'. - Set the 'Apply additional costs per' based on how you calculated cost to serve amounts for operating expenses. - Set the additional costs for Direct orders, Warehouse orders, Will call order and Credit memos. - Set the sale types for will call transactions - Set the desired sort and subtotals as well as rank option desired. If exporting to Excel, unselect print report headings otherwise set report headings options as desired. Save the criteria for the Customer Net Profitability Report for All Users, a User Group or a User with a name that indicates what the criteria includes.
Implementation Final Steps
Go to System Administration > Restricted Processing > Automated Processing > Queue Maintenance - Create a Job with the Customer Net Profitability Report that was saved in the previous step - Create a Queue and include the Job from the previous step - Schedule the Queue to run as frequently as you would like
AR26215 - How to implement Notifications for Critical Sales Order Changes
Agility
- System Administration
Implementation Requirements
Install the Automated Processing client on a computer that has Internet access and is running constantly.
The 'Expected Delv Date Change' notification is based on a change to the expected delivery date on a sales order detail and the 'Backorder Qty Available...' notifications are based on availability of previously backordered material. Each of these notifications are generated through Automated Processing which requires the above setup.
Implementation First Steps
Go to: System Administration > Restricted Processing > Notification Maintenance - Monitor quantities previously backordered that are now available - Create a new record for the event 'Backorder Qty Available Items Ready to Ship' to monitor for individual items that are now available to ship. - Create a new record for the event 'Backorder Qty Available SO Ready to Ship' to monitor for sales orders that previously had at least one item on backorder that is now available to ship. - Create a new record for the event 'Backorder Qty Available Parent Ready to Build' to receive an alert when a parent item that previously had at least one component on backorder is now ready to be built. - Specify the recipient(s) - Send for All records or only those meeting certain criteria - Create the email message subject and body with System Inputs
Implementation Next Steps
Go to: System Administration > Restricted Processing > Notification Maintenance - Monitor expected delivery date changes - Create a new record for the event 'Exp Delv Date Change' - Specify the recipient(s) - Create the email message subject and body with System Inputs - Send for All records or only those meeting certain criteria - Criteria available for this notification is within the 'More Details' link
Implementation Final Steps
Go to: System Administration > Restricted Processing > Automated Processing > Queue Maintenance
-Review the 'Notifications - BO Qty Available' queue - Verify the queue's On Hold flag is unset - Modify the recommended interval if desired (defaults to every 5 minutes)
- Review the 'Notifications - Exp Delv Date Change' queue - Verify the queue's On Hold flag is unset - Modify the recommended interval if desired (defaults to every 5 minutes)
AR26455 - How to perform physical inventory in WMS
Agility
- Physical Inventory
How to perform physical inventory in WMS
1. Turn off sending of IA’s from WMS to Agility
2. Use RF guns to count each location
3. Once completed, perform Sync Dump process in WMS
4. Sync dump will create a PI workfile in Agility
Running Tag Comparison Report
1. Inventory Control > Physical Inventory > Comparison Report
2. Set the Open Only option
3. Use the dropdown to select the Workfile ID
4. Update the Include Records w/ Variance greater than to .00 qty
a. Recommended to run the report once with a .00 dollar variance and once with a .00 qty variance
5. Click on Run
6. Review report for variances
7. Correct qtys in WMS if needed and repeat steps 1-6 until variance is acceptable
Posting Inventory in Agility after acceptable tag comparison report variance
1. Inventory Control > Physical Inventory > Audit Report
2. Audit Report must be run prior to adjusting the inventory
a. Set Open Only option
b. Use dropdown to select the PI workfile
c. Click on Print
3. You can review report but it is not necessary.
4. Inventory Control > Physical Inventory > Update Quantity on Hand
5. Use dropdown to select the PI workfile and click on OK
**Make sure you turn back on the sending of IA’s from WMS to Agility
6.
AR27278 - Cyberquery (CQ) sample: POD Signature Verification
Agility
- Cyberquery Samples
This report prints an audit POD signatures that were captured for orders with a ship date of run date or previous day. The report lists all orders by route and if the signature if the signature was captured or handwritten or not captured.
-- The report does not contain any prompts to allow running in the automated processing on a daily basis. The report may need to be modified to exclude branches that are not using POD and also to exclude routes that are not delivery routes.
--This report will need to be copied into a macro. To copy the report into a macro open the report writer and then in the upper left of the screen click on “File” and “New” and select Macro.
--You can also automatically open a macro by using the key sequence of control key M. Since the entire report is in a macro there is no need to compile the query.
--Suggested Naming Convention: pod_signature_verification.mf
/* pod_signature_verification This report prints the orders with a ship date of today or the previous day along with how the signature was captured */
define string ximage = if related_image:image_info = null then "Not Captured" else "Captured"; define string xno_sig = if related_image:no_signature = 1 then "Customer not available" else "Customer present"; define string xresults = if ximage = "Captured" and xno_sig = "Customer not available" then "Customer not available" else ximage;
where related_image:image_type = "POD Signature" and related_image:related_table = "shipments_header"
list/domain="related_image" /nodetail /hold="hf_related_image" related_image:related_table related_image:related_table_guid related_image:image_info /heading="Text of Signature" ximage /heading="Image Avail" xno_sig /heading="Customer Avail" xresults /heading="Results"
sorted by related_image:related_table_guid
end of related_image:related_table_guid /noheading related_image:related_table related_image:related_table_guid/keyelement=1 related_image:image_info ximage /name="image_avail" xno_sig /name="cust_avail" xresults /name="results" ;run define date xdate1 = todaysdate-1;
define file ximage = access hf_related_image, set hf_related_image:related_table_guid = shipments_header:shipments_header_guid, outer join;
define string xstatus = switch(shipments_header:status_flag) case "S" : "Staged" case "L" : "Loaded" case "E" : "En Route" case "D" : "Delivered" case "I" : "Invoiced" default : shipments_header:status_flag;
define xcustomer = cust_shipto:cust_code + " - " + str(cust_shipto:seq_num);
define string xroute = if shipments_header:route_id_char > "" then uppercase(shipments_header:route_id_char) else if so_header:route_id_char > "" then uppercase(so_header:route_id_char) else " ";
define number xall = 1; define number xsig = if ximage:results <> null then 1 else 0;
define string xtype_name = if ximage:results = "Captured" and ximage:image_info <> "" then "Typed:"+ximage:image_info else if ximage:results = "Captured" then "Handwritten Only" else if ximage:results = null then "Not Captured" else ximage:results
define xvalid = if sales_type:transfer = 0 and sales_type:will_call = 0 -------Need to remove this if Will call routes should be included and xroute not one of " " --------May want to add common carrier routes here and sales_type:inv_affect = 1 --------This excludes directs and other nondelivered sales types then "Y" else "N" where shipments_header:type = "SO" and shipments_header:ship_date => xdate1 and shipments_header:ship_date =< todaysdate and shipments_header:shipment_num = so_header:shipment_num --and shipments_header:system_id one of " " --add branches to process otherwise all branches will process and xvalid = "Y"
list/domain="shipments_header" /nobanner/duplicates/noheadings/nopageheadings /title="Daily ePOD Signature Verification" /pagelength=66 xcustomer /width=16 cust_shipto:shipto_name shipments_header:so_id /width=8/nocommas shipments_header:shipment_num /width=8 /center shipments_header:ship_date /mask="mm/dd/yyyy" xroute /width=10 xstatus /width=12 xtype_name xall/hidden xsig/hidden
sorted by shipments_header:system_id shipments_header:ship_date xroute cust_shipto:cust_code cust_shipto:seq_num shipments_header:so_id
top of xroute /noheading
"Route: "+xroute +" "+delv_route:description+" Ship Date: " + str(shipments_header:ship_date,8)/newline "Invoicing"/align=xstatus/newline "Customer"/align=xcustomer "Name"/align=cust_shipto:shipto_name "SO ID"/align=shipments_header:so_id "Ship #"/align=shipments_header:shipment_num "Ship Date"/align=shipments_header:ship_date "Route"/align=xroute "Status"/align=xstatus "POD Status"/align=xtype_name
end of xroute " "/newline "Total Orders: " + str(total[xall])/align=cust_shipto:shipto_name "Responses: " + str(total[xsig]) "Captured: " + str((total[xsig] divide total[xall]) * 100) + "%"/newline
top of page/noheading "Report run for starting date of: " + str(xdate1,8) "Page number: " + str(pagenumber)/align=xstatus/right/newline=2
if pagenumber <> 1 then { "Route: "+xroute + " "+delv_route:description+" Ship Date: " + str(shipments_header:ship_date,8)/newline "Invoicing"/align=xstatus/newline "Customer"/align=xcustomer "Name"/align=cust_shipto:shipto_name "SO ID"/align=shipments_header:so_id "Ship #"/align=shipments_header:shipment_num "Ship Date"/align=shipments_header:ship_date "Route"/align=xroute "Status"/align=xstatus "POD Status"/align=xtype_name }
;run rreplace pod_signatures view