Adjutant Wiki - User contributions [en]

Accounts Payable ACH Setup Process

2024-05-22T15:34:02Z

Jared:

__NOTOC__
==General Description==

The Accounts Payable ACH process generates an ACH formatted file, known as an AP EFT file, per AP check paid. This file can then be uploaded to your bank to reconcile AP invoices.

==Initial Setup==

Before this file can be created and used, some basic setup must be completed.

===Add Vendor's ACH Data===

'''1.''' Navigate to the '''[[Organizations]]''' screen, and select a vendor.

'''2.''' If the vendor doesn't already have the "Vendor ACH/EFT Data" attribute, click the "plus" sign in the green box on the right, and add the attribute to the record.

[[image:ap_ach_1.png]]

[[image:ap_ach_2.png]]

'''3.''' Save the newly added attribute, then click the underlined "Vendor ACH/EFT Data" attribute on the vendor record screen edit it on the '''[[EFT Data]]''' screen.

'''4.''' Enter the EFT/ACH data for the vendor and click "save."

[[image:ap_ach_3.png]]

===Setup the [[ACH Data Setup - ACHDATA Rule|ACH Data Setup Rule]]===

'''1.''' Navigate to '''[[Rule Maintenance]]''' and select '''ACH Data Setup - ACHDATA''' from the dropdown.

'''2.''' Select "New Rule Details" to add a checking account to the rule.

'''GL Account''' - Here you will specify the checking account from which payments will be made.

'''File Name''' - This is where you will specify the name of the file that is generated.

'''Format''' - The Standard Entry Class (SEC) code used by the GL account. You can also use an 'AMEGY' format. Contact your consultant to discuss the correct SEC code. More information on SEC codes can be found '''[https://achdevguide.nacha.org/ach-file-details here]'''

'''Batch Number''' A number that identifies a group of transactions that the system processes and balances as a unit.

[[image:AP_ACH_rule_Setup.png]]

===Setup ACH Checking Accounts===

'''1.''' Navigate to '''[[System Cash/Checking Accounts]]'''

'''2.''' Add the ACH information to the GL Account referenced in the rule above.

'''3.''' Select the check forms to be used for payments from this account.

'''4.''' Define the check numbers to be used for generated checks from this account. By default, check numbers will count up incrementally by 1 with each ACH transaction processed in Adjutant.

[[image:setup_ach_ss.png]]

===Setup Email Template===

[[File:EFT.png]]

===[[Generate AP EFT File]]===

'''1.''' Once you have created an AP check and it has been approved for payment, navigate to the Generate AP EFT File screen by going to '''Transactions > Accounts Payable > [[Generate AP EFT File]]'''.

'''2.''' Select the account from which the payment will be made. The Transaction Date and First Check Number will auto populate based on today's date, and the check counter from the Checking Account screen of the selected account.

'''3.''' Enter the vendor information for the AP invoice to be paid, and click '''Generate EFT'''. A file will be generated that can be saved and uploaded to your bank.

[[File:AP_ACH_Setup_Generate_AP_EFT_File.png]]

[[Category:Accounts Payable]]

Accounts Payable ACH Setup Process

2024-05-22T15:33:14Z

Jared:

__NOTOC__
==General Description==

The Accounts Payable ACH process generates an ACH formatted file, known as an AP EFT file, per AP check paid. This file can then be uploaded to your bank to reconcile AP invoices.

==Initial Setup==

Before this file can be created and used, some basic setup must be completed.

===Add Vendor's ACH Data===

'''1.''' Navigate to the '''[[Organizations]]''' screen, and select a vendor.

'''2.''' If the vendor doesn't already have the "Vendor ACH/EFT Data" attribute, click the "plus" sign in the green box on the right, and add the attribute to the record.

[[image:ap_ach_1.png]]

[[image:ap_ach_2.png]]

'''3.''' Save the newly added attribute, then click the underlined "Vendor ACH/EFT Data" attribute on the vendor record screen edit it on the '''[[EFT Data]]''' screen.

'''4.''' Enter the EFT/ACH data for the vendor and click "save."

[[image:ap_ach_3.png]]

===Setup the [[ACH Data Setup - ACHDATA Rule|ACH Data Setup Rule]]===

'''1.''' Navigate to '''[[Rule Maintenance]]''' and select '''ACH Data Setup - ACHDATA''' from the dropdown.

'''2.''' Select "New Rule Details" to add a checking account to the rule.

'''GL Account''' - Here you will specify the checking account from which payments will be made.

'''File Name''' - This is where you will specify the name of the file that is generated.

'''Format''' - The Standard Entry Class (SEC) code used by the GL account. You can also use an 'AMEGY' format. Contact your consultant to discuss the correct SEC code. More information on SEC codes can be found '''[https://achdevguide.nacha.org/ach-file-details here]'''

'''Batch Number''' A number that identifies a group of transactions that the system processes and balances as a unit.

===Setup Email Template===

[[File:EFT.png]]

[[image:AP_ACH_rule_Setup.png]]

===Setup ACH Checking Accounts===

'''1.''' Navigate to '''[[System Cash/Checking Accounts]]'''

'''2.''' Add the ACH information to the GL Account referenced in the rule above.

'''3.''' Select the check forms to be used for payments from this account.

'''4.''' Define the check numbers to be used for generated checks from this account. By default, check numbers will count up incrementally by 1 with each ACH transaction processed in Adjutant.

[[image:setup_ach_ss.png]]

===[[Generate AP EFT File]]===

'''1.''' Once you have created an AP check and it has been approved for payment, navigate to the Generate AP EFT File screen by going to '''Transactions > Accounts Payable > [[Generate AP EFT File]]'''.

'''2.''' Select the account from which the payment will be made. The Transaction Date and First Check Number will auto populate based on today's date, and the check counter from the Checking Account screen of the selected account.

'''3.''' Enter the vendor information for the AP invoice to be paid, and click '''Generate EFT'''. A file will be generated that can be saved and uploaded to your bank.

[[File:AP_ACH_Setup_Generate_AP_EFT_File.png]]

[[Category:Accounts Payable]]

File:EFT.png

2024-05-22T15:32:04Z

Jared:

Accounts Payable ACH Setup Process

2024-05-09T18:16:36Z

Jared:

__NOTOC__
==General Description==

The Accounts Payable ACH process generates an ACH formatted file, known as an AP EFT file, per AP check paid. This file can then be uploaded to your bank to reconcile AP invoices.

==Initial Setup==

Before this file can be created and used, some basic setup must be completed.

===Add Vendor's ACH Data===

'''1.''' Navigate to the '''[[Organizations]]''' screen, and select a vendor.

'''2.''' If the vendor doesn't already have the "Vendor ACH/EFT Data" attribute, click the "plus" sign in the green box on the right, and add the attribute to the record.

[[image:ap_ach_1.png]]

[[image:ap_ach_2.png]]

'''3.''' Save the newly added attribute, then click the underlined "Vendor ACH/EFT Data" attribute on the vendor record screen edit it on the '''[[EFT Data]]''' screen.

'''4.''' Enter the EFT/ACH data for the vendor and click "save."

[[image:ap_ach_3.png]]

===Setup the [[ACH Data Setup - ACHDATA Rule|ACH Data Setup Rule]]===

'''1.''' Navigate to '''[[Rule Maintenance]]''' and select '''ACH Data Setup - ACHDATA''' from the dropdown.

'''2.''' Select "New Rule Details" to add a checking account to the rule.

'''GL Account''' - Here you will specify the checking account from which payments will be made.

'''File Name''' - This is where you will specify the name of the file that is generated.

'''Format''' - The Standard Entry Class (SEC) code used by the GL account. You can also use an 'AMEGY' format. Contact your consultant to discuss the correct SEC code. More information on SEC codes can be found '''[https://achdevguide.nacha.org/ach-file-details here]'''

'''Batch Number''' A number that identifies a group of transactions that the system processes and balances as a unit.

[[image:AP_ACH_rule_Setup.png]]

===Setup ACH Checking Accounts===

'''1.''' Navigate to '''[[System Cash/Checking Accounts]]'''

'''2.''' Add the ACH information to the GL Account referenced in the rule above.

'''3.''' Select the check forms to be used for payments from this account.

'''4.''' Define the check numbers to be used for generated checks from this account. By default, check numbers will count up incrementally by 1 with each ACH transaction processed in Adjutant.

[[image:setup_ach_ss.png]]

===[[Generate AP EFT File]]===

'''1.''' Once you have created an AP check and it has been approved for payment, navigate to the Generate AP EFT File screen by going to '''Transactions > Accounts Payable > [[Generate AP EFT File]]'''.

'''2.''' Select the account from which the payment will be made. The Transaction Date and First Check Number will auto populate based on today's date, and the check counter from the Checking Account screen of the selected account.

'''3.''' Enter the vendor information for the AP invoice to be paid, and click '''Generate EFT'''. A file will be generated that can be saved and uploaded to your bank.

[[File:AP_ACH_Setup_Generate_AP_EFT_File.png]]

[[Category:Accounts Payable]]

AMS Setup

2023-08-28T18:08:08Z

Jared:

__NOTOC__
==Overview==

This is a guide for consultants to use to set up an AMS connection from start to finish. Setup typically takes a few hours and involves making connections from the Eclipse software to the Adjutant database.

The goal is to establish an ODBC connection from Eclipse to Adjutant reading a specific set of data tables. The function of the integration is for Adjutant to pass order and bundle information into Eclipse/AMS and to receive back production and material usage information.

In the past, AMS Integration involved sending flat files across the servers back and forth with the necessary data. As of today, the most efficient way to pass data back and forth is by a direct SQL data transfer.

This set up assumes a hosted connection, though non-hosted connections have a similar and at times identical setup.

AMS Integration runs off of a service called AdjAmsProcess.exe.

==Initial Set Up==

There are a number of things that can and should be set up before you are ready to "flip the switch". The Database Set Up section, the Item Attributes section, and the Rule Setup sections should all be completed before working with Eclipse for the integration.

Once you are ready to "flip the switch", you will complete the Eclipse Setup section, then the Setup Options section, then the Coil Table Population section, then the Ready to Test section. This set up needs to be done all at once, so be sure you budget your time to get each of these done and troubleshoot if needed.

===Database Set Up===

Eclipse uses what is called "On Demand" coil verification. This means when a user scans a coil, they call back a special database table that has all the right information in place. This means that David will need to create new AMS specific data tables. These tables will be matched up in the Eclipse screen below. Typically the tables are named AMS_*** where the *** will match the Eclipse name. For the On Demand coil table, David will typically name the view AMS_STOCK_WhseName

Sending the following email to support@abiscorp.com should make the ticket you need. Be sure to replace your customer name, custno, and resource ID in the tag and body below.

''Please create the AMS tables needed for Eclipse integration on [your customer's] system. ''

''custno['''CUSTNO''']''

''resid['''Your ResID''']''

''escalate[y]''

''priority[p2]''

===Item Attributes===

For Adjutant to recognize and push an item out to Eclipse, it needs to have the proper item attribute (Attribute name "AMS" with form "AMSPROD" in the Item Attribute Rule).

[[image:amsrule.png]]

The AMS Product Attribute jump screen has three fields. These fields will need to line up with the Eclipse data exactly. The preferred scenario is that the customer sets up their Eclipse items with the same names as their item codes in Adjutant. That makes for an easy data import. This information can be filled out using an Excel import (download here) and shows data from the AMSXREF table.

* AMS Material: This is the material as AMS understands it to use make this item. Similar to the BOM material in Adjutant.
* AMS Product: This is the AMS name for the item you are making.
* AMS Machine Number: This is the corresponding Machine ID.
* Plant/Rollformer/Machine/Length(FT) Grid: This is used if there are different machines used in each plant. This is controlled in the AMSXREFD table.

Please note that any item and material that is interacting with AMS/Eclipse will need this attribute. This means that every coil will have the attribute with '''only''' the Material section filled out. Adjutant will remove the other fields and recognize it as material.

For a more detailed run through of the AMS Xref Import, [http://www.abiscorp.com/faq/index.php?title=AMS_Cross-Reference_Import_Guide See this guide]

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

===Rule Setup===
There are a few rules that need to be set up.

'''AMS Process Rule (AMSPROCESS)'''

This rule will determine the various processes that are used. These entries are warehouse specific, so if setting up for multiple warehouses, should include each entry shown below ''per each warehouse''. Important note: The Loctid (num 1) is the Warehouse Key number.

Everything else should be set up as shown in the image, paying special attention to which is an import or export process (Log 1 and Log 2 respectively).

[[File:AMS Wiki Rule AMS Process.png]]

'''AMS Printer Rule (AMSPRINTER) - Optional - '''

This rule will allow you to set the printers per machine per location to print bundle and carton tags. There are certain set up options (see below) that are needed to print labels from the machine based on bundling done during the S2P process.

The machine name (Text 1) must match the profile machine rule exactly for it to work. The UNC Name for the printer (Text 2) must match the UNC name for the printer in Printer Control exactly. This will be paired with the Loctid (num 1) to allow you to print to machines in multiple warehouses.

[[File:AMS Wiki Rule AMS Printer.png]]

'''AMS Scrap Rule (AMSSCRAPXREF) - Optional - '''

This rule will allow you to match scrap codes sent back from AMS to different item codes. This is useful if you wanted to direct various kinds of scrap into different expense accounts. Text 1 will be the numeric Scrap Code received from AMS. Text 2 is the Item Code that it will go against. It is possible that these AMS codes are dynamic and can change. You will need to work with AMS and with your customer to make sure they are correct and are being used.

[[File:AMS_Wiki_Rule_Scrap.png]]

==Eclipse Setup==

This section will describe everything that needs to take place on the Eclipse side. Your customer will need to grant you some form of screen share access to the computer on which Eclipse is installed.

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

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

Step 3: Each tab, except for tab (3) has sources that need to be matched up to our new tables. Important note - the "Tables" drop down is NOT in alphabetical order. You have to find the tables exactly as they are shown in the screenshot (ex. "ams_orderin"). There are other tables that look similar to this but are not correct. To begin the match up, follow these steps:
* On the System DSN for Import Data drop down, choose the database (probably "adjutant")
* For the User ID and Password for Import Data, enter the database credentials you used to make the ODBC connection
* Hit Connect at the bottom. The grayed out drop down fields should become available to select now.
* For each "Source" row, select the matching Table. The table will always have an "ams_" before it. On tab Import(1), each table has "in" appended to it (ex. ams_orderin, ams_bundlein, etc).
* Hit disconnect and Apply

[[File:AMS Wiki Eclipse t1.png|500px]]

Step 4: Repeat the steps above for tab Export Local (2) and Verify Coil (4). On the Verify Coil tab, you will select the AMS_Stock_WhseName table to use, and make sure that "Verify Coil data from SQL Server Tables" is checked.

[[File:AMS Wiki Eclipse t2.png|500px]]

[[File:AMS Wiki Eclipse t4.png|500px]]

Step 5: Close the SQLSetup program and run the Eclipse program. In one of the menus there should be a way to connect to a source database (screenshots unavailable). It should be able to connect without stalling out.

==Setup Options==

Several set up options are available, depending on how Adjutant and Eclipse will be used together. Certain things need to be considered, such as bundling, scrapping and label printing.

Below are several important options related to AMS. Not all are required - required options will say "(REQ)" next to the option. This list is not extensive. There are many more that are specific to certain customers and not relevant to a normal set up.

* AMS (REQ) - turns the whole thing on.
* AMSASSEMPWO (REQ) - enables the logic to auto assemble and complete work orders coming from AMS.
* AMSPRODSQL (REQ) - enables SQL transfer for production information.
* AMSORDERSQL (REQ) - enables SQL transfer for sending orders.
* AMSSQLLEN (REQ) - sends items to the machine based on bundle# and length (longest to shortest)
* AMSCTAG - will print bundle tags for bundles created when they are sent to AMS. This will use the AMSPRINTER rule set up previously to determine which printer is used.
* AMSLABEL -
* SUBSTOAMS - will allow subassemblies to be sent to AMS during the S2P process.
* AMSANYCOIL - will allow Adjutant to accept and use whatever coil is scanned through AMS regardless of production plant.
* AMSADDCOIL - when set, adjusts coil in Adjutant to meet AMS demand.
* AMSSKIPBUNDLE - will skip the bundle process during the S2P. Orders will be manually bundles using the scanner.
* AMSSCRAP - will enable the AMS Scrapping process. This will need the AMSSCRAP rule set up previously.

==Coil Table Population==

Before you begin testing, you will need to run the Purge and Reload Controller Coils process in order to populate the AMS stock table with the current inventory. This will take all the open coils for the selected warehouse, remove and re-add them so they can be processed into the AMS_Stock_WhseName table. For most customers, this should take 10 minutes or less, but it should be run outside of business hours because it does lock the itemtrack table.

Once completed, run "Select * From ams_stock_WhseName" to verify that the coils are in.

[[File:AMS Wiki Purge Coil.png]]

==Ready to Test==

Once Eclipse is ready and connected, flipping on the setup options and running the AdjAmsProcess will make the integration live.

AdjAMSProcess.exe is the process used to push data back and forth. Make sure you have the latest version from the FTP folder. Run it in a local session to test for errors.

The best way to test is to take an order with an item having the Adj AMS attribute and send it to production. The line should appear in the amsorder table (select top 100 * from amsorder). The amsorder.datesent field should get filled out as the AMS process pushes it to the Eclipse database table, ams_orderin. Once it processes from there, have your customer verify they can see it in Eclipse.

When coil is scanned from the Eclipse/AMS machine, it should verify from the Adjutant coil tag.

Tracking return usage is more difficult since this can only be done as the machine actually does the production. With your customer, settle on an order being run and track it through in the amsproduct table. If it shows in that table, verify the PWO has usage assigned and is completed. The amsproduct table should have the coil that was scanned in the amsproduct.coilmat field. If you find "NO COIL MATCH", it was not able to find the coil.

If nothing is coming back, turn off the services, and go back to the start to make sure the right set up options and tables are matched correctly.

Once you are confident that everything is set up correctly, send an email to support to set up AdjAMSProcess as a service if they are hosted. Otherwise, set up AdjAMSProcess in the customers' Service + in their system.

==Troubleshooting==

Q: What if the customer says they completed the job in AMS but a carton tag didn’t print?
A: Look at the amsproduct table where orderno= the SO#. When the bundle # changes a tag should have been printed. Look at procdate and compare that to labelmast for that same time.

Q: What if the SQL tables are connected but Eclipse is not able to find the coil, even though it's in the table?
A: Verify the xlwin.ini file in the Customer's Eclipse folder. Close Eclipse and the COMM program. Open xlwin.ini using notepad. Verify the following are set to "T"

ImportSQLServer = T

ExportSQLServer = T

CoilSQLServer = T

If they are "F", change them to a "T" and save.

==Helpful Contacts==

If all else fails, and you need to get AMS involved, Finn O'Mahoney is the best contact at the company. He has always been able to answer questions quickly and has helped to resolve any issues we've dealt with in the past. Finn O'Mahony <fomahony@amscontrols.com>

[[Category: Help]]
[[Category: Internal]]
[[Category: AMS]]
[[Category: Setup Guides]]

Schedule

2022-04-27T20:40:20Z

Jared:

File:Quest.png

2022-04-27T20:38:15Z

Jared:

Schedule

2022-04-27T20:37:41Z

Jared:

__NOTOC__
==Adding icons to a scheduled task==

This guide outlines how to add icons to a scheduled task.

[[File:icon example.png]]

==Setup==

# Go to Maintain > System > Menu Prompts and search for an image that you want to use.

[[File:menu1.png]]
[[File:menu3.png]]

# Go to Maintain > Task Management > UDFs/Forms/Decision Trees and add a new UDF question.

[[File:udf1.png]]

# While still at Maintain > Task Management > UDFs/Forms/Decision Trees, go to the Forms tab and create a new form. Once you've created the new form, link the UDF you created in the previous step.

[[File:udf2.png]]

# Go to Maintain > Task Management > Standard Task Maintenance and link the UDF form to the desired standard task.

[[File:stask.png]]

==How-To Topic Part Two==
Consider whether or not an additional note is required to give an overview or additional information about this step. For example, if this is an optional step, or a step that maybe some customers will not need to complete - that information could be entered here.

Delete this section if the process only requires a single section.

# If the process involves multiple screens or multiple, distinct steps, break it up into sections using the headers.
# Continue using the same format for additional steps.
#* You can link to another page in this wiki using the exact page name [[Contact Import Guide]] or you can override the link name [[Contact Import Guide|like this]]
#** Or you can use a full URL link [http://www.abiscorp.com/faq/index.php?title=Contact_Import_Guide like this]
#* You can link to a category page in this wiki and override the link name [[:Category:Best Practices|like this]] or just do this [[:Category:Best Practices]]
#* You can link to an external URL with the following format just by pasting the link - http://www.abiscorp.com/adjwiki/rule-itemcat.ashx
#** Or you can override the link name [http://www.abiscorp.com/adjwiki/rule-itemcat.ashx like this]

==Additional Information==
This section is an optional place to document any follow-up steps, further considerations, or links to other pages that may be helpful. Delete this section if it is not needed.

Just for reference, below is an example of an indented bullet list, along with guidance for when to use bold formatting.

* '''Menu Paths''' should be bold for easy reference
** '''Screen Names''' should be bold
*** '''Tab Names''' inside of screen should also be bold
**** '''Field Names''' should generally be bold. There may be cases where using single quotes for a 'field name' is appropriate.
***** 'Sections' in a screen such as the 'Customer' section label in the '''Order Entry''' screen should use single quotes
***** 'Column labels' in a grid should generally use single quotes
***** 'OK' or 'Cancel' buttons (or any other buttons on a pop-up message) should have single quotes
* I have used italics for things like ''Report Names'' when I am referring to the report and not the screen name for the report, and for ''filenames.xlsx''

<code>Updating the Category tags is critical to helping customers find content. Review the Categories list and tag all categories below</code>

[[Category: Help]]
[[Category: Internal]]

File:Stask.png

2022-04-27T20:36:32Z

Jared:

File:Udf2.png

2022-04-27T20:35:43Z

Jared:

File:Udf1.png

2022-04-27T20:33:56Z

Jared:

Schedule

2022-04-27T20:22:14Z

Jared:

__NOTOC__
==Adding icons to a scheduled task==

This guide outlines how to add icons to a scheduled task.

[[File:icon example.png]]

==Setup==

# Go to Maintain > System > Menu Prompts and search for an image that you want to use.

[[File:menu1.png]]
[[File:menu3.png]]
==How-To Topic Part Two==
Consider whether or not an additional note is required to give an overview or additional information about this step. For example, if this is an optional step, or a step that maybe some customers will not need to complete - that information could be entered here.

Delete this section if the process only requires a single section.

# If the process involves multiple screens or multiple, distinct steps, break it up into sections using the headers.
# Continue using the same format for additional steps.
#* You can link to another page in this wiki using the exact page name [[Contact Import Guide]] or you can override the link name [[Contact Import Guide|like this]]
#** Or you can use a full URL link [http://www.abiscorp.com/faq/index.php?title=Contact_Import_Guide like this]
#* You can link to a category page in this wiki and override the link name [[:Category:Best Practices|like this]] or just do this [[:Category:Best Practices]]
#* You can link to an external URL with the following format just by pasting the link - http://www.abiscorp.com/adjwiki/rule-itemcat.ashx
#** Or you can override the link name [http://www.abiscorp.com/adjwiki/rule-itemcat.ashx like this]

==Additional Information==
This section is an optional place to document any follow-up steps, further considerations, or links to other pages that may be helpful. Delete this section if it is not needed.

Just for reference, below is an example of an indented bullet list, along with guidance for when to use bold formatting.

* '''Menu Paths''' should be bold for easy reference
** '''Screen Names''' should be bold
*** '''Tab Names''' inside of screen should also be bold
**** '''Field Names''' should generally be bold. There may be cases where using single quotes for a 'field name' is appropriate.
***** 'Sections' in a screen such as the 'Customer' section label in the '''Order Entry''' screen should use single quotes
***** 'Column labels' in a grid should generally use single quotes
***** 'OK' or 'Cancel' buttons (or any other buttons on a pop-up message) should have single quotes
* I have used italics for things like ''Report Names'' when I am referring to the report and not the screen name for the report, and for ''filenames.xlsx''

<code>Updating the Category tags is critical to helping customers find content. Review the Categories list and tag all categories below</code>

[[Category: Help]]
[[Category: Internal]]

File:Menu3.png

2022-04-27T20:20:49Z

Jared:

File:Menu2.png

2022-04-27T20:15:19Z

Jared: Jared uploaded a new version of File:Menu2.png

Schedule

2022-04-27T20:13:44Z

Jared:

__NOTOC__
==Adding icons to a scheduled task==

This guide outlines how to add icons to a scheduled task.

[[File:icon example.png]]

==Setup==

# Go to Maintain > System > Menu Prompts and search for an image that you want to use.

[[File:menu1.png]]
[[File:menu2.png]]
==How-To Topic Part Two==
Consider whether or not an additional note is required to give an overview or additional information about this step. For example, if this is an optional step, or a step that maybe some customers will not need to complete - that information could be entered here.

Delete this section if the process only requires a single section.

# If the process involves multiple screens or multiple, distinct steps, break it up into sections using the headers.
# Continue using the same format for additional steps.
#* You can link to another page in this wiki using the exact page name [[Contact Import Guide]] or you can override the link name [[Contact Import Guide|like this]]
#** Or you can use a full URL link [http://www.abiscorp.com/faq/index.php?title=Contact_Import_Guide like this]
#* You can link to a category page in this wiki and override the link name [[:Category:Best Practices|like this]] or just do this [[:Category:Best Practices]]
#* You can link to an external URL with the following format just by pasting the link - http://www.abiscorp.com/adjwiki/rule-itemcat.ashx
#** Or you can override the link name [http://www.abiscorp.com/adjwiki/rule-itemcat.ashx like this]

==Additional Information==
This section is an optional place to document any follow-up steps, further considerations, or links to other pages that may be helpful. Delete this section if it is not needed.

Just for reference, below is an example of an indented bullet list, along with guidance for when to use bold formatting.

* '''Menu Paths''' should be bold for easy reference
** '''Screen Names''' should be bold
*** '''Tab Names''' inside of screen should also be bold
**** '''Field Names''' should generally be bold. There may be cases where using single quotes for a 'field name' is appropriate.
***** 'Sections' in a screen such as the 'Customer' section label in the '''Order Entry''' screen should use single quotes
***** 'Column labels' in a grid should generally use single quotes
***** 'OK' or 'Cancel' buttons (or any other buttons on a pop-up message) should have single quotes
* I have used italics for things like ''Report Names'' when I am referring to the report and not the screen name for the report, and for ''filenames.xlsx''

<code>Updating the Category tags is critical to helping customers find content. Review the Categories list and tag all categories below</code>

[[Category: Help]]
[[Category: Internal]]

File:Menu2.png

2022-04-27T20:12:11Z

Jared:

File:Menu1.png

2022-04-27T20:11:59Z

Jared:

Schedule

2022-04-27T20:11:46Z

Jared:

__NOTOC__
==Adding icons to a scheduled task==

This guide outlines how to add icons to a scheduled task.

[[File:icon example.png]]

==Setup==

# Go to Maintain > System > Menu Prompts and search for an image that you want to use.

==How-To Topic Part Two==
Consider whether or not an additional note is required to give an overview or additional information about this step. For example, if this is an optional step, or a step that maybe some customers will not need to complete - that information could be entered here.

Delete this section if the process only requires a single section.

# If the process involves multiple screens or multiple, distinct steps, break it up into sections using the headers.
# Continue using the same format for additional steps.
#* You can link to another page in this wiki using the exact page name [[Contact Import Guide]] or you can override the link name [[Contact Import Guide|like this]]
#** Or you can use a full URL link [http://www.abiscorp.com/faq/index.php?title=Contact_Import_Guide like this]
#* You can link to a category page in this wiki and override the link name [[:Category:Best Practices|like this]] or just do this [[:Category:Best Practices]]
#* You can link to an external URL with the following format just by pasting the link - http://www.abiscorp.com/adjwiki/rule-itemcat.ashx
#** Or you can override the link name [http://www.abiscorp.com/adjwiki/rule-itemcat.ashx like this]

==Additional Information==
This section is an optional place to document any follow-up steps, further considerations, or links to other pages that may be helpful. Delete this section if it is not needed.

Just for reference, below is an example of an indented bullet list, along with guidance for when to use bold formatting.

* '''Menu Paths''' should be bold for easy reference
** '''Screen Names''' should be bold
*** '''Tab Names''' inside of screen should also be bold
**** '''Field Names''' should generally be bold. There may be cases where using single quotes for a 'field name' is appropriate.
***** 'Sections' in a screen such as the 'Customer' section label in the '''Order Entry''' screen should use single quotes
***** 'Column labels' in a grid should generally use single quotes
***** 'OK' or 'Cancel' buttons (or any other buttons on a pop-up message) should have single quotes
* I have used italics for things like ''Report Names'' when I am referring to the report and not the screen name for the report, and for ''filenames.xlsx''

<code>Updating the Category tags is critical to helping customers find content. Review the Categories list and tag all categories below</code>

[[Category: Help]]
[[Category: Internal]]

Schedule

2022-04-27T20:08:35Z

Jared:

__NOTOC__
==Adding icons to a scheduled task==

This guide outlines how to add icons to a scheduled task.

[[File:icon example.png]]

==How-To Topic==
When appropriate, you may need to enter a sentence or two to relay additional information immediately below the header and before you begin the steps.

# When referencing how a customer should access the desired '''Screen Name''', format the menu path like '''Transaction > System > Change Running User'''.
#* Notice that the menu path and screen name should be bold.
# All Action list buttons like '''Cancel Changes''' for example, should also be bold.
# Whenever possible, consolidate steps using the <nowiki> #* </nowiki> bullet points.
#* This can help keep the numbered list from growing to a high number.
#* For example, a how-to with 23 steps can be more intimidating and make a simple procedure look like too many steps.
#* But the bullet points break it up.
# As long as you don't skip spaces between the <nowiki> # </nowiki> characters, it will auto number. Even a single space can mess it up.

# Review carefully, because a skipped space will mess up the sequencing.
# Continue the steps using the same pattern.

==How-To Topic Part Two==
Consider whether or not an additional note is required to give an overview or additional information about this step. For example, if this is an optional step, or a step that maybe some customers will not need to complete - that information could be entered here.

Delete this section if the process only requires a single section.

# If the process involves multiple screens or multiple, distinct steps, break it up into sections using the headers.
# Continue using the same format for additional steps.
#* You can link to another page in this wiki using the exact page name [[Contact Import Guide]] or you can override the link name [[Contact Import Guide|like this]]
#** Or you can use a full URL link [http://www.abiscorp.com/faq/index.php?title=Contact_Import_Guide like this]
#* You can link to a category page in this wiki and override the link name [[:Category:Best Practices|like this]] or just do this [[:Category:Best Practices]]
#* You can link to an external URL with the following format just by pasting the link - http://www.abiscorp.com/adjwiki/rule-itemcat.ashx
#** Or you can override the link name [http://www.abiscorp.com/adjwiki/rule-itemcat.ashx like this]

==Additional Information==
This section is an optional place to document any follow-up steps, further considerations, or links to other pages that may be helpful. Delete this section if it is not needed.

Just for reference, below is an example of an indented bullet list, along with guidance for when to use bold formatting.

* '''Menu Paths''' should be bold for easy reference
** '''Screen Names''' should be bold
*** '''Tab Names''' inside of screen should also be bold
**** '''Field Names''' should generally be bold. There may be cases where using single quotes for a 'field name' is appropriate.
***** 'Sections' in a screen such as the 'Customer' section label in the '''Order Entry''' screen should use single quotes
***** 'Column labels' in a grid should generally use single quotes
***** 'OK' or 'Cancel' buttons (or any other buttons on a pop-up message) should have single quotes
* I have used italics for things like ''Report Names'' when I am referring to the report and not the screen name for the report, and for ''filenames.xlsx''

<code>Updating the Category tags is critical to helping customers find content. Review the Categories list and tag all categories below</code>

[[Category: Help]]
[[Category: Internal]]

Schedule

2022-04-27T20:07:57Z

Jared:

__NOTOC__
==Adding icons to a scheduled task==

This guide outlines how to add icons to a scheduled task.

[[File:Icon example.png]

==How-To Topic==
When appropriate, you may need to enter a sentence or two to relay additional information immediately below the header and before you begin the steps.

[[File:Example_Image.png]]

# When referencing how a customer should access the desired '''Screen Name''', format the menu path like '''Transaction > System > Change Running User'''.
#* Notice that the menu path and screen name should be bold.
# All Action list buttons like '''Cancel Changes''' for example, should also be bold.
# Whenever possible, consolidate steps using the <nowiki> #* </nowiki> bullet points.
#* This can help keep the numbered list from growing to a high number.
#* For example, a how-to with 23 steps can be more intimidating and make a simple procedure look like too many steps.
#* But the bullet points break it up.
# As long as you don't skip spaces between the <nowiki> # </nowiki> characters, it will auto number. Even a single space can mess it up.

# Review carefully, because a skipped space will mess up the sequencing.
# Continue the steps using the same pattern.

==How-To Topic Part Two==
Consider whether or not an additional note is required to give an overview or additional information about this step. For example, if this is an optional step, or a step that maybe some customers will not need to complete - that information could be entered here.

Delete this section if the process only requires a single section.

# If the process involves multiple screens or multiple, distinct steps, break it up into sections using the headers.
# Continue using the same format for additional steps.
#* You can link to another page in this wiki using the exact page name [[Contact Import Guide]] or you can override the link name [[Contact Import Guide|like this]]
#** Or you can use a full URL link [http://www.abiscorp.com/faq/index.php?title=Contact_Import_Guide like this]
#* You can link to a category page in this wiki and override the link name [[:Category:Best Practices|like this]] or just do this [[:Category:Best Practices]]
#* You can link to an external URL with the following format just by pasting the link - http://www.abiscorp.com/adjwiki/rule-itemcat.ashx
#** Or you can override the link name [http://www.abiscorp.com/adjwiki/rule-itemcat.ashx like this]

==Additional Information==
This section is an optional place to document any follow-up steps, further considerations, or links to other pages that may be helpful. Delete this section if it is not needed.

Just for reference, below is an example of an indented bullet list, along with guidance for when to use bold formatting.

* '''Menu Paths''' should be bold for easy reference
** '''Screen Names''' should be bold
*** '''Tab Names''' inside of screen should also be bold
**** '''Field Names''' should generally be bold. There may be cases where using single quotes for a 'field name' is appropriate.
***** 'Sections' in a screen such as the 'Customer' section label in the '''Order Entry''' screen should use single quotes
***** 'Column labels' in a grid should generally use single quotes
***** 'OK' or 'Cancel' buttons (or any other buttons on a pop-up message) should have single quotes
* I have used italics for things like ''Report Names'' when I am referring to the report and not the screen name for the report, and for ''filenames.xlsx''

<code>Updating the Category tags is critical to helping customers find content. Review the Categories list and tag all categories below</code>

[[Category: Help]]
[[Category: Internal]]

File:Icon example.png

2022-04-27T20:07:33Z

Jared:

Schedule

2022-04-27T20:06:29Z

Jared:

__NOTOC__
==Adding icons to a scheduled task==

This guide outlines how to add icons to a scheduled task.

[[File:Example.jpg]]

==How-To Topic==
When appropriate, you may need to enter a sentence or two to relay additional information immediately below the header and before you begin the steps.

[[File:Example_Image.png]]

# When referencing how a customer should access the desired '''Screen Name''', format the menu path like '''Transaction > System > Change Running User'''.
#* Notice that the menu path and screen name should be bold.
# All Action list buttons like '''Cancel Changes''' for example, should also be bold.
# Whenever possible, consolidate steps using the <nowiki> #* </nowiki> bullet points.
#* This can help keep the numbered list from growing to a high number.
#* For example, a how-to with 23 steps can be more intimidating and make a simple procedure look like too many steps.
#* But the bullet points break it up.
# As long as you don't skip spaces between the <nowiki> # </nowiki> characters, it will auto number. Even a single space can mess it up.

# Review carefully, because a skipped space will mess up the sequencing.
# Continue the steps using the same pattern.

==How-To Topic Part Two==
Consider whether or not an additional note is required to give an overview or additional information about this step. For example, if this is an optional step, or a step that maybe some customers will not need to complete - that information could be entered here.

Delete this section if the process only requires a single section.

# If the process involves multiple screens or multiple, distinct steps, break it up into sections using the headers.
# Continue using the same format for additional steps.
#* You can link to another page in this wiki using the exact page name [[Contact Import Guide]] or you can override the link name [[Contact Import Guide|like this]]
#** Or you can use a full URL link [http://www.abiscorp.com/faq/index.php?title=Contact_Import_Guide like this]
#* You can link to a category page in this wiki and override the link name [[:Category:Best Practices|like this]] or just do this [[:Category:Best Practices]]
#* You can link to an external URL with the following format just by pasting the link - http://www.abiscorp.com/adjwiki/rule-itemcat.ashx
#** Or you can override the link name [http://www.abiscorp.com/adjwiki/rule-itemcat.ashx like this]

==Additional Information==
This section is an optional place to document any follow-up steps, further considerations, or links to other pages that may be helpful. Delete this section if it is not needed.

Just for reference, below is an example of an indented bullet list, along with guidance for when to use bold formatting.

* '''Menu Paths''' should be bold for easy reference
** '''Screen Names''' should be bold
*** '''Tab Names''' inside of screen should also be bold
**** '''Field Names''' should generally be bold. There may be cases where using single quotes for a 'field name' is appropriate.
***** 'Sections' in a screen such as the 'Customer' section label in the '''Order Entry''' screen should use single quotes
***** 'Column labels' in a grid should generally use single quotes
***** 'OK' or 'Cancel' buttons (or any other buttons on a pop-up message) should have single quotes
* I have used italics for things like ''Report Names'' when I am referring to the report and not the screen name for the report, and for ''filenames.xlsx''

<code>Updating the Category tags is critical to helping customers find content. Review the Categories list and tag all categories below</code>

[[Category: Help]]
[[Category: Internal]]

Schedule

2022-04-27T20:01:35Z

Jared: Created page with "__NOTOC__ ==Overview== This guide provides an example template that can be copied to create a how-to wiki page. Use the Actions menu to select 'Edit', then CTRL+A to select..."

__NOTOC__
==Overview==

This guide provides an example template that can be copied to create a how-to wiki page. Use the Actions menu to select 'Edit', then CTRL+A to select all, then CTRL+C to copy. The text copied to the clipboard can be pasted into the new page. A practical example of this layout in use can be found [[Creating a Manual Journal Entry|here]].

This page only exists as an example of layout options, and as a place to hold some formatting tips on links, images, bullet points, etc. Once you have copied the page contents, return to the [http://www.abiscorp.com/employee/index.php?title=Creating_a_New_Wiki_Page Creating a New Wiki Page] wiki on the Employee Wiki for the instructions on how to actually create the new page, paste this page content as starter point, and apply categories.

The information below this line is presented as an example of what each section should contain in a general 'How-To' style wiki page.

The Overview sections should contain a brief description of the purpose of this page. This section is what the customer will see first, so the text here should tell them immediately whether or not this is the page they are looking for.

==How-To Topic==
When appropriate, you may need to enter a sentence or two to relay additional information immediately below the header and before you begin the steps.

[[File:Example_Image.png]]

# When referencing how a customer should access the desired '''Screen Name''', format the menu path like '''Transaction > System > Change Running User'''.
#* Notice that the menu path and screen name should be bold.
# All Action list buttons like '''Cancel Changes''' for example, should also be bold.
# Whenever possible, consolidate steps using the <nowiki> #* </nowiki> bullet points.
#* This can help keep the numbered list from growing to a high number.
#* For example, a how-to with 23 steps can be more intimidating and make a simple procedure look like too many steps.
#* But the bullet points break it up.
# As long as you don't skip spaces between the <nowiki> # </nowiki> characters, it will auto number. Even a single space can mess it up.

# Review carefully, because a skipped space will mess up the sequencing.
# Continue the steps using the same pattern.

==How-To Topic Part Two==
Consider whether or not an additional note is required to give an overview or additional information about this step. For example, if this is an optional step, or a step that maybe some customers will not need to complete - that information could be entered here.

Delete this section if the process only requires a single section.

# If the process involves multiple screens or multiple, distinct steps, break it up into sections using the headers.
# Continue using the same format for additional steps.
#* You can link to another page in this wiki using the exact page name [[Contact Import Guide]] or you can override the link name [[Contact Import Guide|like this]]
#** Or you can use a full URL link [http://www.abiscorp.com/faq/index.php?title=Contact_Import_Guide like this]
#* You can link to a category page in this wiki and override the link name [[:Category:Best Practices|like this]] or just do this [[:Category:Best Practices]]
#* You can link to an external URL with the following format just by pasting the link - http://www.abiscorp.com/adjwiki/rule-itemcat.ashx
#** Or you can override the link name [http://www.abiscorp.com/adjwiki/rule-itemcat.ashx like this]

==Additional Information==
This section is an optional place to document any follow-up steps, further considerations, or links to other pages that may be helpful. Delete this section if it is not needed.

Just for reference, below is an example of an indented bullet list, along with guidance for when to use bold formatting.

* '''Menu Paths''' should be bold for easy reference
** '''Screen Names''' should be bold
*** '''Tab Names''' inside of screen should also be bold
**** '''Field Names''' should generally be bold. There may be cases where using single quotes for a 'field name' is appropriate.
***** 'Sections' in a screen such as the 'Customer' section label in the '''Order Entry''' screen should use single quotes
***** 'Column labels' in a grid should generally use single quotes
***** 'OK' or 'Cancel' buttons (or any other buttons on a pop-up message) should have single quotes
* I have used italics for things like ''Report Names'' when I am referring to the report and not the screen name for the report, and for ''filenames.xlsx''

<code>Updating the Category tags is critical to helping customers find content. Review the Categories list and tag all categories below</code>

[[Category: Help]]
[[Category: Internal]]

Track Length Cost Update

2021-01-12T18:48:24Z

Jared:

Track Length Cost Update

2021-01-12T16:29:19Z

Jared:

Track Length Cost Update

2021-01-12T15:43:22Z

Jared:

==Overview==

This screen allows a user to update the base cost and ordering min/max quantites for items with 'Track Length' selected in the Item Master screen.

==How-To Topic==

[[File:Track Length Cost Update.png]]

# Adjust the CommCode/Profile/Gauge/Color filters at the top of the page to isolate the items you want to change. Once the filters are set, select the '''Refresh Table''' button.
# Change the '''Calculate Based On''' field to determine which field to use as a basis for the calculations (which field will be increased or decreased to determine the base cost).
#* '''Standard Cost (Global)''' uses the item's current '''Standard Cost (Global)''' cost as a basis for the calculations.
#* '''Base Cost (EA)''' uses the item's '''Current Cost (EA)''' cost.
#* '''Base Cost (CWT)''' uses the item's '''Current Cost (CWT)''' cost.
# All Action list buttons like '''Cancel Changes''' for example, should also be bold.
# Whenever possible, consolidate steps using the <nowiki> #* </nowiki> bullet points.
#* This can help keep the numbered list from growing to a high number.
#* For example, a how-to with 23 steps can be more intimidating and make a simple procedure look like too many steps.
#* But the bullet points break it up.
# As long as you don't skip spaces between the <nowiki> # </nowiki> characters, it will auto number. Even a single space can mess it up.

# Review carefully, because a skipped space will mess up the sequencing.
# Continue the steps using the same pattern.

==How-To Topic Part Two==
Consider whether or not an additional note is required to give an overview or additional information about this step. For example, if this is an optional step, or a step that maybe some customers will not need to complete - that information could be entered here.

Delete this section if the process only requires a single section.

# If the process involves multiple screens or multiple, distinct steps, break it up into sections using the headers.
# Continue using the same format for additional steps.
#* You can link to another page in this wiki using the exact page name [[Contact Import Guide]] or you can override the link name [[Contact Import Guide|like this]]
#** Or you can use a full URL link [http://www.abiscorp.com/faq/index.php?title=Contact_Import_Guide like this]
#* You can link to a category page in this wiki and override the link name [[:Category:Best Practices|like this]] or just do this [[:Category:Best Practices]]
#* You can link to an external URL with the following format just by pasting the link - http://www.abiscorp.com/adjwiki/rule-itemcat.ashx
#** Or you can override the link name [http://www.abiscorp.com/adjwiki/rule-itemcat.ashx like this]

==Additional Information==
This section is an optional place to document any follow-up steps, further considerations, or links to other pages that may be helpful. Delete this section if it is not needed.

Just for reference, below is an example of an indented bullet list, along with guidance for when to use bold formatting.

* '''Menu Paths''' should be bold for easy reference
** '''Screen Names''' should be bold
*** '''Tab Names''' inside of screen should also be bold
**** '''Field Names''' should generally be bold. There may be cases where using single quotes for a 'field name' is appropriate.
***** 'Sections' in a screen such as the 'Customer' section label in the '''Order Entry''' screen should use single quotes
***** 'Column labels' in a grid should generally use single quotes
***** 'OK' or 'Cancel' buttons (or any other buttons on a pop-up message) should have single quotes
* I have used italics for things like ''Report Names'' when I am referring to the report and not the screen name for the report, and for ''filenames.xlsx''

<code>Updating the Category tags is critical to helping customers find content. Review the Categories list and tag all categories below</code>

[[Category: Help]]
[[Category: Internal]]

Track Length Cost Update

2021-01-12T15:42:12Z

Jared:

==Overview==

This guide provides an example template that can be copied to create a how-to wiki page. Use the Actions menu to select 'Edit', then CTRL+A to select all, then CTRL+C to copy. The text copied to the clipboard can be pasted into the new page. A practical example of this layout in use can be found [[Creating a Manual Journal Entry|here]].

This page only exists as an example of layout options, and as a place to hold some formatting tips on links, images, bullet points, etc. Once you have copied the page contents, return to the [http://www.abiscorp.com/employee/index.php?title=Creating_a_New_Wiki_Page Creating a New Wiki Page] wiki on the Employee Wiki for the instructions on how to actually create the new page, paste this page content as starter point, and apply categories.

The information below this line is presented as an example of what each section should contain in a general 'How-To' style wiki page.

The Overview sections should contain a brief description of the purpose of this page. This section is what the customer will see first, so the text here should tell them immediately whether or not this is the page they are looking for.

==How-To Topic==
When appropriate, you may need to enter a sentence or two to relay additional information immediately below the header and before you begin the steps.

[[File:Track Length Cost Update.png]]

# Adjust the CommCode/Profile/Gauge/Color filters at the top of the page to isolate the items you want to change. Once the filters are set, select the '''Refresh Table''' button.
# Change the '''Calculate Based On''' field to determine which field to use as a basis for the calculations (which field will be increased or decreased to determine the base cost).
#* '''Standard Cost (Global)''' uses the item's current '''Standard Cost (Global)''' cost as a basis for the calculations.
#* '''Base Cost (EA)''' uses the item's '''Current Cost (EA)''' cost.
#* '''Base Cost (CWT)''' uses the item's '''Current Cost (CWT)''' cost.
# All Action list buttons like '''Cancel Changes''' for example, should also be bold.
# Whenever possible, consolidate steps using the <nowiki> #* </nowiki> bullet points.
#* This can help keep the numbered list from growing to a high number.
#* For example, a how-to with 23 steps can be more intimidating and make a simple procedure look like too many steps.
#* But the bullet points break it up.
# As long as you don't skip spaces between the <nowiki> # </nowiki> characters, it will auto number. Even a single space can mess it up.

# Review carefully, because a skipped space will mess up the sequencing.
# Continue the steps using the same pattern.

==How-To Topic Part Two==
Consider whether or not an additional note is required to give an overview or additional information about this step. For example, if this is an optional step, or a step that maybe some customers will not need to complete - that information could be entered here.

Delete this section if the process only requires a single section.

# If the process involves multiple screens or multiple, distinct steps, break it up into sections using the headers.
# Continue using the same format for additional steps.
#* You can link to another page in this wiki using the exact page name [[Contact Import Guide]] or you can override the link name [[Contact Import Guide|like this]]
#** Or you can use a full URL link [http://www.abiscorp.com/faq/index.php?title=Contact_Import_Guide like this]
#* You can link to a category page in this wiki and override the link name [[:Category:Best Practices|like this]] or just do this [[:Category:Best Practices]]
#* You can link to an external URL with the following format just by pasting the link - http://www.abiscorp.com/adjwiki/rule-itemcat.ashx
#** Or you can override the link name [http://www.abiscorp.com/adjwiki/rule-itemcat.ashx like this]

==Additional Information==
This section is an optional place to document any follow-up steps, further considerations, or links to other pages that may be helpful. Delete this section if it is not needed.

Just for reference, below is an example of an indented bullet list, along with guidance for when to use bold formatting.

* '''Menu Paths''' should be bold for easy reference
** '''Screen Names''' should be bold
*** '''Tab Names''' inside of screen should also be bold
**** '''Field Names''' should generally be bold. There may be cases where using single quotes for a 'field name' is appropriate.
***** 'Sections' in a screen such as the 'Customer' section label in the '''Order Entry''' screen should use single quotes
***** 'Column labels' in a grid should generally use single quotes
***** 'OK' or 'Cancel' buttons (or any other buttons on a pop-up message) should have single quotes
* I have used italics for things like ''Report Names'' when I am referring to the report and not the screen name for the report, and for ''filenames.xlsx''

<code>Updating the Category tags is critical to helping customers find content. Review the Categories list and tag all categories below</code>

[[Category: Help]]
[[Category: Internal]]

Track Length Cost Update

2021-01-12T15:17:21Z

Jared:

==Overview==

This guide provides an example template that can be copied to create a how-to wiki page. Use the Actions menu to select 'Edit', then CTRL+A to select all, then CTRL+C to copy. The text copied to the clipboard can be pasted into the new page. A practical example of this layout in use can be found [[Creating a Manual Journal Entry|here]].

This page only exists as an example of layout options, and as a place to hold some formatting tips on links, images, bullet points, etc. Once you have copied the page contents, return to the [http://www.abiscorp.com/employee/index.php?title=Creating_a_New_Wiki_Page Creating a New Wiki Page] wiki on the Employee Wiki for the instructions on how to actually create the new page, paste this page content as starter point, and apply categories.

The information below this line is presented as an example of what each section should contain in a general 'How-To' style wiki page.

The Overview sections should contain a brief description of the purpose of this page. This section is what the customer will see first, so the text here should tell them immediately whether or not this is the page they are looking for.

==How-To Topic==
When appropriate, you may need to enter a sentence or two to relay additional information immediately below the header and before you begin the steps.

[[File:Track Length Cost Update.png]]

# Adjust the CommCode/Profile/Gauge/Color filters at the top of the page to isolate the items you want to change.
# Change the '''Calculate Based On''' field to determine which field to use as a basis for the calculations (which field will be increased or decreased to determine the base cost).
# All Action list buttons like '''Cancel Changes''' for example, should also be bold.
# Whenever possible, consolidate steps using the <nowiki> #* </nowiki> bullet points.
#* This can help keep the numbered list from growing to a high number.
#* For example, a how-to with 23 steps can be more intimidating and make a simple procedure look like too many steps.
#* But the bullet points break it up.
# As long as you don't skip spaces between the <nowiki> # </nowiki> characters, it will auto number. Even a single space can mess it up.

# Review carefully, because a skipped space will mess up the sequencing.
# Continue the steps using the same pattern.

==How-To Topic Part Two==
Consider whether or not an additional note is required to give an overview or additional information about this step. For example, if this is an optional step, or a step that maybe some customers will not need to complete - that information could be entered here.

Delete this section if the process only requires a single section.

# If the process involves multiple screens or multiple, distinct steps, break it up into sections using the headers.
# Continue using the same format for additional steps.
#* You can link to another page in this wiki using the exact page name [[Contact Import Guide]] or you can override the link name [[Contact Import Guide|like this]]
#** Or you can use a full URL link [http://www.abiscorp.com/faq/index.php?title=Contact_Import_Guide like this]
#* You can link to a category page in this wiki and override the link name [[:Category:Best Practices|like this]] or just do this [[:Category:Best Practices]]
#* You can link to an external URL with the following format just by pasting the link - http://www.abiscorp.com/adjwiki/rule-itemcat.ashx
#** Or you can override the link name [http://www.abiscorp.com/adjwiki/rule-itemcat.ashx like this]

==Additional Information==
This section is an optional place to document any follow-up steps, further considerations, or links to other pages that may be helpful. Delete this section if it is not needed.

Just for reference, below is an example of an indented bullet list, along with guidance for when to use bold formatting.

* '''Menu Paths''' should be bold for easy reference
** '''Screen Names''' should be bold
*** '''Tab Names''' inside of screen should also be bold
**** '''Field Names''' should generally be bold. There may be cases where using single quotes for a 'field name' is appropriate.
***** 'Sections' in a screen such as the 'Customer' section label in the '''Order Entry''' screen should use single quotes
***** 'Column labels' in a grid should generally use single quotes
***** 'OK' or 'Cancel' buttons (or any other buttons on a pop-up message) should have single quotes
* I have used italics for things like ''Report Names'' when I am referring to the report and not the screen name for the report, and for ''filenames.xlsx''

<code>Updating the Category tags is critical to helping customers find content. Review the Categories list and tag all categories below</code>

[[Category: Help]]
[[Category: Internal]]

File:Track Length Cost Update.png

2021-01-11T14:43:55Z

Jared:

Track Length Cost Update

2021-01-11T14:42:55Z

Jared:

==Overview==

This guide provides an example template that can be copied to create a how-to wiki page. Use the Actions menu to select 'Edit', then CTRL+A to select all, then CTRL+C to copy. The text copied to the clipboard can be pasted into the new page. A practical example of this layout in use can be found [[Creating a Manual Journal Entry|here]].

This page only exists as an example of layout options, and as a place to hold some formatting tips on links, images, bullet points, etc. Once you have copied the page contents, return to the [http://www.abiscorp.com/employee/index.php?title=Creating_a_New_Wiki_Page Creating a New Wiki Page] wiki on the Employee Wiki for the instructions on how to actually create the new page, paste this page content as starter point, and apply categories.

The information below this line is presented as an example of what each section should contain in a general 'How-To' style wiki page.

The Overview sections should contain a brief description of the purpose of this page. This section is what the customer will see first, so the text here should tell them immediately whether or not this is the page they are looking for.

==How-To Topic==
When appropriate, you may need to enter a sentence or two to relay additional information immediately below the header and before you begin the steps.

[[File:Track Length Cost Update.png]]

# When referencing how a customer should access the desired '''Screen Name''', format the menu path like '''Transaction > System > Change Running User'''.
#* Notice that the menu path and screen name should be bold.
# All Action list buttons like '''Cancel Changes''' for example, should also be bold.
# Whenever possible, consolidate steps using the <nowiki> #* </nowiki> bullet points.
#* This can help keep the numbered list from growing to a high number.
#* For example, a how-to with 23 steps can be more intimidating and make a simple procedure look like too many steps.
#* But the bullet points break it up.
# As long as you don't skip spaces between the <nowiki> # </nowiki> characters, it will auto number. Even a single space can mess it up.

# Review carefully, because a skipped space will mess up the sequencing.
# Continue the steps using the same pattern.

==How-To Topic Part Two==
Consider whether or not an additional note is required to give an overview or additional information about this step. For example, if this is an optional step, or a step that maybe some customers will not need to complete - that information could be entered here.

Delete this section if the process only requires a single section.

# If the process involves multiple screens or multiple, distinct steps, break it up into sections using the headers.
# Continue using the same format for additional steps.
#* You can link to another page in this wiki using the exact page name [[Contact Import Guide]] or you can override the link name [[Contact Import Guide|like this]]
#** Or you can use a full URL link [http://www.abiscorp.com/faq/index.php?title=Contact_Import_Guide like this]
#* You can link to a category page in this wiki and override the link name [[:Category:Best Practices|like this]] or just do this [[:Category:Best Practices]]
#* You can link to an external URL with the following format just by pasting the link - http://www.abiscorp.com/adjwiki/rule-itemcat.ashx
#** Or you can override the link name [http://www.abiscorp.com/adjwiki/rule-itemcat.ashx like this]

==Additional Information==
This section is an optional place to document any follow-up steps, further considerations, or links to other pages that may be helpful. Delete this section if it is not needed.

Just for reference, below is an example of an indented bullet list, along with guidance for when to use bold formatting.

* '''Menu Paths''' should be bold for easy reference
** '''Screen Names''' should be bold
*** '''Tab Names''' inside of screen should also be bold
**** '''Field Names''' should generally be bold. There may be cases where using single quotes for a 'field name' is appropriate.
***** 'Sections' in a screen such as the 'Customer' section label in the '''Order Entry''' screen should use single quotes
***** 'Column labels' in a grid should generally use single quotes
***** 'OK' or 'Cancel' buttons (or any other buttons on a pop-up message) should have single quotes
* I have used italics for things like ''Report Names'' when I am referring to the report and not the screen name for the report, and for ''filenames.xlsx''

<code>Updating the Category tags is critical to helping customers find content. Review the Categories list and tag all categories below</code>

[[Category: Help]]
[[Category: Internal]]

Track Length Cost Update

2021-01-11T14:42:12Z

Jared:

__NOTOC__
==Overview==

This guide provides an example template that can be copied to create a how-to wiki page. Use the Actions menu to select 'Edit', then CTRL+A to select all, then CTRL+C to copy. The text copied to the clipboard can be pasted into the new page. A practical example of this layout in use can be found [[Creating a Manual Journal Entry|here]].

This page only exists as an example of layout options, and as a place to hold some formatting tips on links, images, bullet points, etc. Once you have copied the page contents, return to the [http://www.abiscorp.com/employee/index.php?title=Creating_a_New_Wiki_Page Creating a New Wiki Page] wiki on the Employee Wiki for the instructions on how to actually create the new page, paste this page content as starter point, and apply categories.

The information below this line is presented as an example of what each section should contain in a general 'How-To' style wiki page.

The Overview sections should contain a brief description of the purpose of this page. This section is what the customer will see first, so the text here should tell them immediately whether or not this is the page they are looking for.

==How-To Topic==
When appropriate, you may need to enter a sentence or two to relay additional information immediately below the header and before you begin the steps.

[[File:Track Length Cost Update.png]]

# When referencing how a customer should access the desired '''Screen Name''', format the menu path like '''Transaction > System > Change Running User'''.
#* Notice that the menu path and screen name should be bold.
# All Action list buttons like '''Cancel Changes''' for example, should also be bold.
# Whenever possible, consolidate steps using the <nowiki> #* </nowiki> bullet points.
#* This can help keep the numbered list from growing to a high number.
#* For example, a how-to with 23 steps can be more intimidating and make a simple procedure look like too many steps.
#* But the bullet points break it up.
# As long as you don't skip spaces between the <nowiki> # </nowiki> characters, it will auto number. Even a single space can mess it up.

# Review carefully, because a skipped space will mess up the sequencing.
# Continue the steps using the same pattern.

==How-To Topic Part Two==
Consider whether or not an additional note is required to give an overview or additional information about this step. For example, if this is an optional step, or a step that maybe some customers will not need to complete - that information could be entered here.

Delete this section if the process only requires a single section.

# If the process involves multiple screens or multiple, distinct steps, break it up into sections using the headers.
# Continue using the same format for additional steps.
#* You can link to another page in this wiki using the exact page name [[Contact Import Guide]] or you can override the link name [[Contact Import Guide|like this]]
#** Or you can use a full URL link [http://www.abiscorp.com/faq/index.php?title=Contact_Import_Guide like this]
#* You can link to a category page in this wiki and override the link name [[:Category:Best Practices|like this]] or just do this [[:Category:Best Practices]]
#* You can link to an external URL with the following format just by pasting the link - http://www.abiscorp.com/adjwiki/rule-itemcat.ashx
#** Or you can override the link name [http://www.abiscorp.com/adjwiki/rule-itemcat.ashx like this]

==Additional Information==
This section is an optional place to document any follow-up steps, further considerations, or links to other pages that may be helpful. Delete this section if it is not needed.

Just for reference, below is an example of an indented bullet list, along with guidance for when to use bold formatting.

* '''Menu Paths''' should be bold for easy reference
** '''Screen Names''' should be bold
*** '''Tab Names''' inside of screen should also be bold
**** '''Field Names''' should generally be bold. There may be cases where using single quotes for a 'field name' is appropriate.
***** 'Sections' in a screen such as the 'Customer' section label in the '''Order Entry''' screen should use single quotes
***** 'Column labels' in a grid should generally use single quotes
***** 'OK' or 'Cancel' buttons (or any other buttons on a pop-up message) should have single quotes
* I have used italics for things like ''Report Names'' when I am referring to the report and not the screen name for the report, and for ''filenames.xlsx''

<code>Updating the Category tags is critical to helping customers find content. Review the Categories list and tag all categories below</code>

[[Category: Help]]
[[Category: Internal]]

Track Length Cost Update

2021-01-11T14:40:25Z

Item Master Import Guide

2021-01-08T17:57:10Z

Jared:

==General Data Import Notes==

Refer to the [[Data Import General Information]] page for information and guidance on general import timeline, formatting import templates, as well as how to ensure you are using the most current template information for data imports.

==Item Master Import Notes==

===Timing and Preparation===

The Item Master Import should occur early in the setup process, because item records are essential for setup testing, training, and user testing in most of the applications. The Item Control rules should be complete prior to importing. The [[Item Control Setup Guide]] covers all of the Rule Maintenance records that should be completed prior to importing item master records.

Item Master import files are commonly separated into multiple imports based on item type, department, category, or any number of item grouping details. Item Department is a common file grouping, because if the import files are separated by department, it is easy to assign the correct department attributes during the import.

Separating the import files by item type can also help with completing the required unit of measure values in the file. Customer item control data generally does not have the same level of unit related fields as Adjutant, and there may be many blank unit related columns that must be completed prior to importing.

The Item Master import is just the first step in building a complete inventory system. There are multiple other imports required to complete setting up the Item Control records. These other imports, such as quantities, cost tiers, coil inventory, configurations, and bills of material, require that the base item record is created first, and should be completed soon after the Item Master import.

The Item Master import does not generally need to be run again as a go-live import. Once the base item records are imported and all items are represented, there is generally no need to re-import.

Occasionally, additional item records must be created in order to accomodate a new selling or production procedure, or accomodate a shift in processes due to difference between a legacy system and Adjutant. When creating new item records for these types of situations, be sure to complete any other required imports for the new item codes.

===General Notes===

'''OHF Records''' If you are importing items for a single warehouse/single owner location, the Item Master import can build the default OHF records automatically. If you are importing for a multi-warehouse and/or multi-owner locations, and ALL imported items on the file are valid for ALL OHF combinations, the Item Master import can also automatically build the needed OHF records for all combinations. If some items are exclusive to certain OHF records, it may be easiest to handle this with separate Item Master import files. Or, depending on the situation, you may be able to use the Item Import (DET) file, also known as the Min/Max file to create the needed OHF combinations.

'''Item Attributes''' The Item Master import can automatically create the Catch Weight attribute if the CW columns is 'Y' and the related CW columns are filled in. It will also create the Coil Lot (Coil Receipt Defaults) attribute if the Coil column is 'Y'.

Another reason to consider separating the import files is automatically apply other attributes to certain item types during import. For example, the Buyout, Purchase in QuickBuy, Warning Note, and other special attributes can be auto-assigned to every item on the import if the attribute is flagged during the import. To set an attribute as available in the Item Master import, set the 'Show in Import' (Logic2) option in the Item Attributes (ITEMATTRIB) rule.

==Item Master Import File Data Scrubbing==

Every customer's data will have different issues that need addressing. Some of the issues will not make themselves visible until after the data has been imported and is in use during parallel testing. This is why it is critically important to perform an early import, and keep accurate notes on issues that need to be addressed on a supplemental import, or for a complete re-import. Some common things that need attention during Item Master data scrubbing include:

* '''Units''' - It is common for customer item data to only include a single unit of measure value for each item. Review all item import files carefully and fill in any required unit fields with the correct unit of measure for the different transaction types (purchase, stock, sell). Setting up items with the wrong units can have dramatic effects on costing, GL postings, and other transactions throughout Adjutant. Review the unit details carefully with the customer before importing. It can be difficult to correct unit-related issues after item records have been used.

* '''Cost''' - Verify that the current cost is entered in the AvgCost column for each item. Also make sure the stock unit of measure relates to the AvgCost value, because it will default to use the stock unit for the AvgCost. When imported, it sets the correct cost for the item for sales orders and purchase orders.

* '''Unit Weights''' - Unit weight can be critically important throughout multiple Adjutant systems and processes such as production and shipping. It is best practices to make sure that all sold items have a unit weight that corresponds to the stock unit imported.

==Item Master Import Screen (ITEMIMPORT)==

Menu Location: Transaction>>Importers/Exporters>>Item Control>>Item Master Import

[[File:ITEMIMPORT.png]]

'''Item File Name/Browse:''' Use the Browse button to locate and select the completed Item Master import template file (in XLS format).

'''Export Template:''' Generates a blank Item Master import template file

'''Map Fields:''' Fields must be mapped prior to importing. If no changes have been made to the column headings, the mapping screen should show all green, and you can click OK to continue. If any of the Input Field Name columns on the left are red, single-click on the line on the left column, and then double-click the desired mapped field in the right column to complete the mapping. Repeat for any red lines on the left that should be mapped. If there are additional columns in the source file that should NOT be mapped, they can be left unmapped (displayed in red). Mandatory fields will require that they be mapped before clicking OK.

'''Default Warehouse:''' Sets the warehouse location for any imported items where the WHSE column on the import file is left blank. This list is populated by Warehouse Control records that have been created.

'''Default Owner:''' Sets the inventory owner for any imported items where the OWNERID column on the import file is left blank. This list is populated with Organization records that have the Inventory Owner attribute.

'''Default HedlFor:''' Sets the inventory holder for any imported items where the HELDFOR column on the import file is left blank. This list is populated from the Item Held For Codes (HOLDER) Rule Maintenance record. If a catch-all code such as 'DEF' is used, make sure the HOLDER rule is set up properly.

'''Create All Combinations:''' Selecting this box will create separate OHF (ITEMDET) records for each OHF combination based on the owners and held for records that have been set up.

'''Unit Group:''' Sets the unit group for any imported items where the UNITGRP column is left blank

'''Unit:''' Sets ALL unit values for any imported items where any unit-related column (PURUNIT, STKUNIT, SELLUNIT, etc) is left blank

'''Validate Units:''' Selecting this box will verify that all unit values on the import are valid defined units in the Unit of Measure (UNITS) rule, and that they are valid units for the selected Unit Group. For example, if FT is not defined as a valid unit in the IND Unit Group according to the rule, it will not pass verification.

'''Ignore Bad Vendnos:''' Selecting this box will import the VENDNO column data as-is, without verifying that the vendor number exists in Address Book.

'''Check for Inactive Items:''' Selecting this box will check all imported item numbers against existing item numbers that have been marked as inactive, and will reject the imported items if there is a match.

'''Select Attributes:''' Attributes selected during the import process will be applied to ALL imported items. Review and verify that the attributes are set correctly before each import. Correcting associated attributes can be a complicated process. Attributes show up in this list based on the 'Show on Import' (Logic2) field in the Item Attributes (ITEMATTRIB) Rule Maintenance record.

==Item Master Import File Definitions==

Required fields are indicated with an * ; Required fields that can be auto-filled by the Import screen are indicated with **

'''*f1 - Item''' - Item number/code (20 character max, alphanumeric, no spaces allowed). The following special characters are allowed (. - + / _)

'''*f2 - Descrip''' - Item Description (99 alphanumeric character max)

'''**f3 - UnitGrp''' - Item Unit of Measure Group (examples are LENGTH, WEIGHT, TIME, IND). Must match a value in the UNITS rule.

'''**f4 - PurUnit''' - Item purchase unit (Unit values should match UNITS rule exactly, including capitalization, generally use ALL CAPS for units)

'''**f5 - StkUnit''' - Item stocking unit (Unit values should match UNITS rule exactly, including capitalization, generally use ALL CAPS for units)

'''**f6 - SellUnit''' - Item sell unit (Unit values should match UNITS rule exactly, including capitalization, generally use ALL CAPS for units)

'''*f7 - AvgCost''' - Item’s current average cost per stocking unit

'''*f8 - Price''' - Item’s price per pricing unit

'''**f9 - PriceUnit''' - Item’s pricing unit (Unit values should match UNITS rule exactly, including capitalization, generally use ALL CAPS for units)

'''**f10 - CostUnit''' - Item’s costing unit associated with the Standard Cost (STDCOST) value (Unit values should match UNITS rule exactly, including capitalization, generally use ALL CAPS for units). Referred to as the Pur Cost Unit on the Item Master screen.

'''*f11 - StkFlag''' - Y if the item is stocked in the warehouse, N if it is not (made to order items are not stocked)

'''f12 - SerialFlag''' - Y if the item is serialized, N if it is not (serialized items have a serial number for every quantity of 1)

'''f13 - LotFlag''' - Y if the item is lot controlled, N if it is not (all coils are lot controlled).

'''f14 - Vendno''' - The vendor code of the item’s default supplier

'''f15 - Vpartno''' - The default supplier’s item code

'''f16 - HeldFor''' - Item's Held For name from the HOLDER rule. This is generally only used in locations where inventory can be held for other entities. Generally, all items should be imported with the default HeldFor name from the HOLDER rule, unless given specific instructions to create multiple HeldFor records.

'''f17 - Whse''' - Enter the warehouse name (not the ID code) for the primary warehouse where these items are located/produced

'''f18 - Taxable''' - Y if the item is taxable, N if it is not

'''f19 - UnitW''' - The item’s unit weight per stocking unit

'''f20 - Cubes''' - Used in Warehouse Management System shipping calculations and forms (rare)

'''f21 - DecQty''' - The number of decimals that should be available when entering quantities of the item on a purchase or sales order (valid entries are 0-5)

'''f22 - MiscItem''' - Y if the item is miscellaneous, N if it is not

'''f23 - Resell''' - Y if you plan on selling this item, N if you do not. If this field is left blank, the item cannot be added to a sales order.

'''f24 - PackCode''' - Item Packing Code (accepts single character letters from A - T). Can be used to group items that should be packed together by this code. (rare)

'''f25 - ABCCode''' - Item ABC ranking code (accepts single character letters from A - Z). Can be used to manually assign ABC rankings to inventory items. The Item ABC Code Assignments screen can be used to automatically assign the ABC Code based on usage or value, once usage and on-hand quantity information is available. (rarely used during item import)

'''f26 - Pgroup''' - The item’s pricing group. Customer pricing may be broken into item pricing groups; e.g. customer XYZ gets 40% off PANELS, 50% off COLDFORM, and 30% off ACCESSORIES, for component
sales. Leaving this field blank can cause pricing issues if pricing is based on price group breakdowns.

'''f27 - ComCode''' - The item’s commodity code. Commodity codes are used in procurement and determine which suppliers can bid on which items. Commodity Codes can also be used as filters for certain inventory reports.

'''f28 - BaseCost''' - The item's base cost. This value can be useful if you are pricing your items using a cost-plus method.

'''f29 - ProdLine''' - This field is no longer used

'''*f30 - ItemCat''' - Item’s category for creating transaction categories. Item Categories are combined with Customer Categories to create a Transaction Category that is used to drive revenue and cost to the correct GL accounts. DEF should be entered for most items, unless a specific accounting model has been established based on item category. Review the revenue and cost accounting procedures carefully to determine the desired entries for each item . If left blank, the item record will not be usable until the category is filled in.

'''f31 - SqFt''' - The item's square footage per stocking unit

'''f32 - WarLen''' - If the item has an associated warranty length, enter it here (maximum 5 characters alphanumeric)

'''f33 - Produce''' - Y if the item is produced in the plant, N if the item is not produced

'''f34 - SearchCode''' - Custom text that can be used to generate a search screen for items with the same/similar search code value. For example, all items with the search code of 'Trim' will display in a search code display (by double-clicking on the item Search Code field), regardless of their item number or description. (maximum 35 characters, alphanumeric)

'''f35 - ProdGrp''' - Item’s product group. Enter one of the following in the column - '''M''' (Material), '''L''' (Labor), '''E''' (Equipment), '''X''' (Expense), or '''S''' (Subcontract). All items must be assigned to one of the 5 system-defined categories that drive revenue and cost accounting.

'''f36 - OwnerID''' - Item's inventory owner. This is generally only used in locations where inventory can be owned by other entities and the accounting needs to be kept separate. Generally, all items should be imported with the default OwnerID value, unless given specific instructions to create multiple Owner records, and multiple OHF combinations.

'''f37 - iClass''' - Custom text field available for further identifying item groups. Can be used on certain reports or custom reports. (maximum 10 characters, alphanumeric)

'''f38 - StdCost''' - Item’s standard cost per pricing unit

'''f39 - Coil''' - Y if the item is a coil. Coil items will automatically be assigned the Coil Receipts Default attribute. All coil items should also have the LotFlag column set to Y.

'''f40 - SingleIssue''' - Y if the item is the SingleIssue Item box should be checked in the Catch Weight attribute screen. This is only saved for catch-weight items (CW column set to Y).

'''f41 - CW''' - Y if the item is a catch-weight item. Catch-weight items will automatically be assigned the Catch Weight attribute.

'''f42 - OldItem''' - This field is no longer used

'''f43 - CWSPriceConv''' - Catch-Weight conversion factor between stock unit and pricing unit. (numeric, up to 5 digits)

'''f44 - CWSTKConv''' - Catch-Weight conversion factor between catch unit and stock unit. (numeric, up to 5 digits)

'''f45 - CWSellConv''' - Catch-Weight conversion factor between stock unit and selling unit. (numeric, up to 5 digits)

'''f46 - CWPurCon''' - Catch-Weight conversion factor between stock unit and purchase unit. (numeric, up to 5 digits)

'''f47 - CWUnit''' - Catch-Weight Unit

'''f48 - PackQty''' - Quantity to pack. (numeric, up to 5 digits)

'''f49 - AllOrder''' - Enter Y to set the Allocate at Order flag in Item Master

'''f50 - EDICode''' - Item's EDI code (alphanumeric, up to 10 digits, rare)

'''f51 - UPCCode''' - Item's UPC code (alphanumeric, up to 12 characters)

==Item Master Import Reconciliation==

Reconciling imported data should begin with spot-checking several records field-by-field for complete data import. Pick records from the source file that have the most data columns filled in. Verify that all source file data fields imported correctly and display as expected.

Run the Item Master Report and verify that the imported records all display with the key values filled in. You can also verify that the number of records imported matched the number of records reported. If there are fewer items reported, looks for items that did not get imported and reconcile.

Try to sell various items on a sales order to verify that the correct flags and defaults are working as expected.

Try to order various items on a purchase order to verify that costs and units work as expected.

==Item Master Import Additional Steps==

Complete the required additional imports based on how the item will be used. For example:

*Item Quantity (O/H) Data
*SOC Data
*Profile Data
*Min/Max Data
*Coil Quantity Data
*and many more

==Item Master Import Database Tables==

'''ITEMMASTER''' - Each imported item creates a unique IKEY tied to the ITEM value. Most of the Item Master fields are imported to the ITEMMASTER table.

'''ITEMDET''' - Item OHF details are created in the ITEMDET table. Each OHF combination has a unique KEYNO based on the associated IKEY (from ITEMMASTER) and the combination of Warehouse (LOCTID), Owner (VENDID), and HELDFOR.

'''PCXREF''' - Attributes added to item records will create cross-reference entries in the PCXREF table. The TYPE will generally be the attribute name or code. The PARENTID and CHILDID will generally match the IKEY value of the associated item.

'''ATTRIBUTE TABLES''' - Attributes such as Catch Weight and Coil Receipt Defaults create their own data tables with details from the attribute jump screens. For any attribute jump screens created that contain data, you should find a separate data table, such as CWINFO (for Catch Weight) or COILJUMP (for Coil Receipt Defaults). The associated FORM (jump screen) name from the ITEMATTRIB rule is generally the same name as the data table. These tables will usually link to the item using the IKEY value.

[[Category: Item Control]]
[[Category: Import Guides]]

AP Invoice Import Guide

2020-10-27T17:15:53Z

Jared: /* AP Invoice Import Header File Definitions */

==General Data Import Notes==

Refer to the [[Data Import General Information]] page for information and guidance on general import timeline, formatting import templates, as well as how to ensure you are using the most current template information for data imports.

==AP Invoice Import Notes==

===Timing and Preparation===

The AP Invoice Import should occur after all vendors have been imported, which should mean that all Address Book setup items have been completed, and all the General Ledger Chart of Accounts has been imported. The [[Address Book Setup Guide]] covers all of the Rule Maintenance records that should be completed prior to importing vendor records.

In order to accurately import 1099 amounts associated with AP invoices, all vendors should be set up with the correct 1099 Type in their Remit To attribute screen. The AP Invoice Import requires the 1099 Type be filled in on the Remit To record.

The AP Invoice Import is generally used to import only the open accounts payable invoices at the time of go-live. However, it is possible to import fully paid historical AP invoice records for reference. If importing both open and fully paid AP invoices, separate the paid records into a separate import batch. This will make it simpler to reconcile the open AP invoices.

If performing an AP Check Import, the AP Invoice Import should be completed first, then the AP Check Import.

===General Notes===

'''Invoice Balance''' - Confirm with the customer that the correct unpaid balance is being used for all imported invoices. Also confirm whether the total of all AP invoice balance amounts, by AP control account, is reconcilable to the GL open accounts payable balance. This is a common way to reconcile the imported details against the expected GL balance. Address and document any discrepancies or expected issues for reconciling during the go-live conversion.

'''Invoice Dates''' - Confirm the correct AP invoice dates with the customer. Adjutant uses an invoice date, posted date, and due date for each imported invoice. Make sure the dates align with customer expectations.

'''GL Accounts''' - The GL accounts in the Header file control the accounts used in report selections and approval processes. The GL accounts in the Distributions file control the accounts used in distribution detail reporting. For each invoice, the APACC in the Header file should match the CTRL ACCT in the Distribution file. There can be multiple AP/CTRL accounts, but each imported invoice should have these accounts match between the Header and the Distributions files.

==AP Invoice Import File Data Scrubbing==

Every customer's data will have different issues that need addressing. Some of the issues will not make themselves visible until after the data has been imported and is in use during parallel testing. This is why it is critically important to perform an early import, and keep accurate notes on issues that need to be addressed on a supplemental import, or for a complete re-import. Some common things that need attention during AP invoice data scrubbing include:

* '''Payment Priority''' - This field may not have a counterpart in the customer's legacy data. Look for any similar field such as payment type or check type that can be converted to a payment priority equivalent value. Filter the source data to look for all variations on a corresponding field and make sure each variation is mapped to a hard-code payment priority value.

* '''Terms''' - Make sure terms data is accurate and matches an entry in the TERMS rule. Any imported PTERMS value that does not exist in the TERMS rule will create a blank entry in the rule. Best practice is to match each invoice terms to a valid TERMS entry. In some systems, invoice terms are a text field and there is no standardization on the legacy system. For these instances, it is best to scrub each term rule until it matches an existing TERM. Alternatively, you can create a catch-all TERM rule for unknown, incomplete, or undefined term details in the source data.

==AP Invoice Import Screen (IMPORTAPINV)==

Menu Location: Transaction>>Importers/Exporters>>Accounting>>AP Invoice Import

[[File:APINV_Import.png]]

'''File Name(Header)/Browse:''' Use the Browse button to locate and select the completed AP Invoice Header import template file (in XLS format). Note - both the Header and Distributions files are required and must be imported at the same time.

'''File Name(Dists)/Browse:''' Use the Browse button to locate and select the completed AP Invoice Distributions import template file (in XLS format). Note - both the Header and Distributions files are required and must be imported at the same time.

'''Export Template:''' Generates a blank AP Invoice Header or Distributions template file

'''Map Fields:''' Fields must be mapped prior to importing. If no changes have been made to the column headings, the mapping screen should show all green, and you can click OK to continue. If any of the Input Field Name columns on the left are red, single-click on the line on the left column, and then double-click the desired mapped field in the right column to complete the mapping. Repeat for any red lines on the left that should be mapped. If there are additional columns in the source file that should NOT be mapped, they can be left unmapped (displayed in red). Mandatory fields will require that they be mapped before clicking OK.

'''Sage/AccPac/SBT Data:''' This checkbox is no longer used

'''Validate to TXT file:''' Selecting this box will create an TXT errors file listing any rows that would create errors such as invalid data, or duplicate records. If no errors are found in the file, the import will still process and no error file will be generated. Checking the validate box only prevents the import process if errors are encountered.

==AP Invoice Import Header File Definitions==

'''*f1 - Invno''' - AP invoice number

'''*f2 - Vendno''' - Vendor number in Adjutant

'''*f3 - PPriority''' - Payment priority value. '2' is the most common entry.

'''*f4 - PTerms''' - Payment terms for the selected invoice. Valid terms from the TERMS rule should be used. If an entry is found during import that doesn't match an existing TERMS rule record, that entry will be added to the TERMS rule with no other rule details. This allows the import to complete, but could add unwanted records to the TERMS rule.

'''*f5 - PurAmt''' - Original AP invoice amount

'''f6 - PaidAmt''' - Cumulative amount paid toward this invoice. If also importing an AP Check file, this amount should match the total of all non-void checks linked to the invoice.

'''*f7 - Balance''' - AP invoice open balance

'''f8 - UDRef''' - AP invoice reference #

'''*f9 - APAcc''' - AP payable GL account stored in the APMAST table. This is used for selecting AP invoice records by payable account on some reports. This value should match the account flagged as the control account in the AP Invoice Distribution import.

'''*f10 - PurDate''' - AP Invoice Date value

'''*f11 - TranDte''' - AP invoice Post Date value

'''*f12 - DueDate''' - AP invoice Due Date value

'''f13 - DisDate''' - AP invoice Discount Date value

'''f14 - PDisc''' - Field not in use

'''f15 - PDays''' - Field not in use

'''f16 - PNet''' - Field not in use

'''f17 - Discount''' - Field not in use

'''f18 - DisAmt''' - AP invoice discount dollar amount. This value gets saved in the APMAST table as an approved discount amount. Any value imported will load into the Approve AP Invoice screen as a pre-set discount value.

'''f19 - AdjAmt''' - AP invoice adjustment dollar amount. This value gets saved in the APMAST table as an approved adjustment amount. Any value imported will load into the Approve AP Invoice screen as a pre-set adjustment value.

'''f20 - AprPay''' - Approved payable amount. Any entry here will set the approved to pay flag. Leave this blank to process approvals through the Approve to Pay process. This amount should match the balance value, or if using discounts and adjustments, it should match the remaining balance.

'''f21 - AprAdj''' - Marks the adjustment amount as approved

'''f22 - Amt1099''' - AP invoice 1099 Amt value. The Remit To 1099 Type is used to set the 1099 Type on the invoice record.

'''f23 - Buyer''' - Field not in use

'''f24 - CheckNo''' - AP Check number for last check paid on this invoice. Check details imported on this file will only update the APMAST table, and will not create any records in the Payment tab. The AP Check Import must be used to create details in the AP Invoice Payment tab.

'''f25 - CheckDate''' - AP Check date for last check paid on this invoice. Check details imported on this file will only update the APMAST table, and will not create any records in the Payment tab. The AP Check Import must be used to create details in the AP Invoice Payment tab.

'''f26 - ChkAcc''' - AP Checking GL Account associated with this invoice

'''f27 - Typ1099''' - This field is not used to set the 1099 Type. In order to import 1099 amounts with AP Invoices, the vendor's Remit To record must be set up with the default 1099 Type, which will be used for any imported 1099 amounts on AP invoices.

'''f28 - Descrip''' - AP Invoice Notes value

'''f29 - Template''' - Enter 'Y' to mark the associated line as a template record

'''f30 - Voucher''' - AP invoice Voucher field value

*'''f31 - VRemitTo''' - Remit To organization number

==AP Invoice Import Distribution File Definitions==

Each AP Invoice should have at least two lines per invoice in this file - one line for the control account total amount, and additional distribution lines that total up to the original invoice balance.

'''f1 - Invno''' - AP invoice number that links to the invoice number in the header file

'''f2 - Vendno''' - Vendor number in Adjutant

'''f3 - UDRef''' - Field not in use

'''f4 - GLAcnt''' - GL Account associated with each line of distribution detail

'''f5 - Amount''' - Distribution amount for the associated detail. The control account distribution amount should equal the original invoice amount (puramt) and the balancing distribution details should add up the offsetting balance for the original invoice amount. Credit amounts (generally for the CtrlAcct amount) should be entered with the credit sign in the format -999.99. These amounts are imported as already posted to the general ledger, and they will not create accounting entries.

'''f6 - CtrlAcct''' - Enter 'Y' to code the line as the payable control account distribution entry. This sets the GL Account and the Amount as the Control Account entries in the GL Distribution tab. Leaving the CtrlAcct field empty sets the associated line as a balancing distribution entry. Each imported invoice should have a Ctrl Acct amount that matches the total of all distribution lines linked to the same invoice.

'''f7 - Descrip''' - Distribution note entry for non-control account lines

==AP Invoice Import Reconciliation==

Reconciling imported data should begin with spot-checking several records field-by-field for complete data import. Pick records from the source file that have the most data columns filled in. Verify that all source file data fields imported correctly and display as expected.

Review the TERMS rule for any unexpected records added to the rule. Depending on the number of records involved, the rule maintenance records can be cleaned up, and the associated Remit To records can be manually updated. Otherwise, clean up the TERMS rule, then delete the imported records, re-scrub the source file, and re-import.

Run the AP Aging Report and compare the open AP balance against the AP control account GL balance. If the source data was provided along with a clear GL cutoff balance, the two balances should be equal. Look for any data issues, such as incorrect aging, or missing details.

Run the AP Invoice Report and compare against imported data. Make sure all records and all data fields report as expected.

Run the Approve AP Invoices process and spot-check a few individual invoices for approval balances and settings. Try approving a single invoice using the 'A2P' button and look for any issues with approval amounts.

Verify that all 1099 amounts imported correctly by spot-checking several different vendors.

Review the imported invoices in the Organization Air Hammer and confirm that data displays as expected.

==AP Invoice Import Additional Steps==

There are no additional steps required to complete the AP Invoice import. The AP Check Import can be run after the AP Invoice Import, if requested.

==AP Invoice Import Database Tables==

'''APMAST''' - Each imported invoice from the Header file creates a new KEYNO in the APMAST TABLE, linked to the imported APINVNO value. The APMAST KEYNO value is the link to the APDIST table (as KEYNOH in APDIST).

'''APDIST''' - Each imported distribution detail line will create an entry in the APDIST table. The KEYNOH value should match the APMAST KEYNO value for the associated AP invoice. The PTYPE will be 'D' for distribution details, and 'C' for Control lines. Note that imported AP Check details will also create details in the APDIST table, so be careful of deleting any unintended records.

[[Category: Accounts Payable]]
[[Category: Import Guides]]

AP Invoice Import Guide

2020-10-27T17:14:24Z

Jared: /* AP Invoice Import Header File Definitions */

==General Data Import Notes==

Refer to the [[Data Import General Information]] page for information and guidance on general import timeline, formatting import templates, as well as how to ensure you are using the most current template information for data imports.

==AP Invoice Import Notes==

===Timing and Preparation===

The AP Invoice Import should occur after all vendors have been imported, which should mean that all Address Book setup items have been completed, and all the General Ledger Chart of Accounts has been imported. The [[Address Book Setup Guide]] covers all of the Rule Maintenance records that should be completed prior to importing vendor records.

In order to accurately import 1099 amounts associated with AP invoices, all vendors should be set up with the correct 1099 Type in their Remit To attribute screen. The AP Invoice Import requires the 1099 Type be filled in on the Remit To record.

The AP Invoice Import is generally used to import only the open accounts payable invoices at the time of go-live. However, it is possible to import fully paid historical AP invoice records for reference. If importing both open and fully paid AP invoices, separate the paid records into a separate import batch. This will make it simpler to reconcile the open AP invoices.

If performing an AP Check Import, the AP Invoice Import should be completed first, then the AP Check Import.

===General Notes===

'''Invoice Balance''' - Confirm with the customer that the correct unpaid balance is being used for all imported invoices. Also confirm whether the total of all AP invoice balance amounts, by AP control account, is reconcilable to the GL open accounts payable balance. This is a common way to reconcile the imported details against the expected GL balance. Address and document any discrepancies or expected issues for reconciling during the go-live conversion.

'''Invoice Dates''' - Confirm the correct AP invoice dates with the customer. Adjutant uses an invoice date, posted date, and due date for each imported invoice. Make sure the dates align with customer expectations.

'''GL Accounts''' - The GL accounts in the Header file control the accounts used in report selections and approval processes. The GL accounts in the Distributions file control the accounts used in distribution detail reporting. For each invoice, the APACC in the Header file should match the CTRL ACCT in the Distribution file. There can be multiple AP/CTRL accounts, but each imported invoice should have these accounts match between the Header and the Distributions files.

==AP Invoice Import File Data Scrubbing==

Every customer's data will have different issues that need addressing. Some of the issues will not make themselves visible until after the data has been imported and is in use during parallel testing. This is why it is critically important to perform an early import, and keep accurate notes on issues that need to be addressed on a supplemental import, or for a complete re-import. Some common things that need attention during AP invoice data scrubbing include:

* '''Payment Priority''' - This field may not have a counterpart in the customer's legacy data. Look for any similar field such as payment type or check type that can be converted to a payment priority equivalent value. Filter the source data to look for all variations on a corresponding field and make sure each variation is mapped to a hard-code payment priority value.

* '''Terms''' - Make sure terms data is accurate and matches an entry in the TERMS rule. Any imported PTERMS value that does not exist in the TERMS rule will create a blank entry in the rule. Best practice is to match each invoice terms to a valid TERMS entry. In some systems, invoice terms are a text field and there is no standardization on the legacy system. For these instances, it is best to scrub each term rule until it matches an existing TERM. Alternatively, you can create a catch-all TERM rule for unknown, incomplete, or undefined term details in the source data.

==AP Invoice Import Screen (IMPORTAPINV)==

Menu Location: Transaction>>Importers/Exporters>>Accounting>>AP Invoice Import

[[File:APINV_Import.png]]

'''File Name(Header)/Browse:''' Use the Browse button to locate and select the completed AP Invoice Header import template file (in XLS format). Note - both the Header and Distributions files are required and must be imported at the same time.

'''File Name(Dists)/Browse:''' Use the Browse button to locate and select the completed AP Invoice Distributions import template file (in XLS format). Note - both the Header and Distributions files are required and must be imported at the same time.

'''Export Template:''' Generates a blank AP Invoice Header or Distributions template file

'''Map Fields:''' Fields must be mapped prior to importing. If no changes have been made to the column headings, the mapping screen should show all green, and you can click OK to continue. If any of the Input Field Name columns on the left are red, single-click on the line on the left column, and then double-click the desired mapped field in the right column to complete the mapping. Repeat for any red lines on the left that should be mapped. If there are additional columns in the source file that should NOT be mapped, they can be left unmapped (displayed in red). Mandatory fields will require that they be mapped before clicking OK.

'''Sage/AccPac/SBT Data:''' This checkbox is no longer used

'''Validate to TXT file:''' Selecting this box will create an TXT errors file listing any rows that would create errors such as invalid data, or duplicate records. If no errors are found in the file, the import will still process and no error file will be generated. Checking the validate box only prevents the import process if errors are encountered.

==AP Invoice Import Header File Definitions==

*'''f1 - Invno''' - AP invoice number

*'''f2 - Vendno''' - Vendor number in Adjutant

*'''f3 - PPriority''' - Payment priority value. '2' is the most common entry.

*'''f4 - PTerms''' - Payment terms for the selected invoice. Valid terms from the TERMS rule should be used. If an entry is found during import that doesn't match an existing TERMS rule record, that entry will be added to the TERMS rule with no other rule details. This allows the import to complete, but could add unwanted records to the TERMS rule.

*'''f5 - PurAmt''' - Original AP invoice amount

'''f6 - PaidAmt''' - Cumulative amount paid toward this invoice. If also importing an AP Check file, this amount should match the total of all non-void checks linked to the invoice.

*'''f7 - Balance''' - AP invoice open balance

'''f8 - UDRef''' - AP invoice reference #

*'''f9 - APAcc''' - AP payable GL account stored in the APMAST table. This is used for selecting AP invoice records by payable account on some reports. This value should match the account flagged as the control account in the AP Invoice Distribution import.

*'''f10 - PurDate''' - AP Invoice Date value

*'''f11 - TranDte''' - AP invoice Post Date value

*'''f12 - DueDate''' - AP invoice Due Date value

'''f13 - DisDate''' - AP invoice Discount Date value

'''f14 - PDisc''' - Field not in use

'''f15 - PDays''' - Field not in use

'''f16 - PNet''' - Field not in use

'''f17 - Discount''' - Field not in use

'''f18 - DisAmt''' - AP invoice discount dollar amount. This value gets saved in the APMAST table as an approved discount amount. Any value imported will load into the Approve AP Invoice screen as a pre-set discount value.

'''f19 - AdjAmt''' - AP invoice adjustment dollar amount. This value gets saved in the APMAST table as an approved adjustment amount. Any value imported will load into the Approve AP Invoice screen as a pre-set adjustment value.

'''f20 - AprPay''' - Approved payable amount. Any entry here will set the approved to pay flag. Leave this blank to process approvals through the Approve to Pay process. This amount should match the balance value, or if using discounts and adjustments, it should match the remaining balance.

'''f21 - AprAdj''' - Marks the adjustment amount as approved

'''f22 - Amt1099''' - AP invoice 1099 Amt value. The Remit To 1099 Type is used to set the 1099 Type on the invoice record.

'''f23 - Buyer''' - Field not in use

'''f24 - CheckNo''' - AP Check number for last check paid on this invoice. Check details imported on this file will only update the APMAST table, and will not create any records in the Payment tab. The AP Check Import must be used to create details in the AP Invoice Payment tab.

'''f25 - CheckDate''' - AP Check date for last check paid on this invoice. Check details imported on this file will only update the APMAST table, and will not create any records in the Payment tab. The AP Check Import must be used to create details in the AP Invoice Payment tab.

'''f26 - ChkAcc''' - AP Checking GL Account associated with this invoice

'''f27 - Typ1099''' - This field is not used to set the 1099 Type. In order to import 1099 amounts with AP Invoices, the vendor's Remit To record must be set up with the default 1099 Type, which will be used for any imported 1099 amounts on AP invoices.

'''f28 - Descrip''' - AP Invoice Notes value

'''f29 - Template''' - Enter 'Y' to mark the associated line as a template record

'''f30 - Voucher''' - AP invoice Voucher field value

*'''f31 - VRemitTo''' - Remit To organization number

==AP Invoice Import Distribution File Definitions==

Each AP Invoice should have at least two lines per invoice in this file - one line for the control account total amount, and additional distribution lines that total up to the original invoice balance.

'''f1 - Invno''' - AP invoice number that links to the invoice number in the header file

'''f2 - Vendno''' - Vendor number in Adjutant

'''f3 - UDRef''' - Field not in use

'''f4 - GLAcnt''' - GL Account associated with each line of distribution detail

'''f5 - Amount''' - Distribution amount for the associated detail. The control account distribution amount should equal the original invoice amount (puramt) and the balancing distribution details should add up the offsetting balance for the original invoice amount. Credit amounts (generally for the CtrlAcct amount) should be entered with the credit sign in the format -999.99. These amounts are imported as already posted to the general ledger, and they will not create accounting entries.

'''f6 - CtrlAcct''' - Enter 'Y' to code the line as the payable control account distribution entry. This sets the GL Account and the Amount as the Control Account entries in the GL Distribution tab. Leaving the CtrlAcct field empty sets the associated line as a balancing distribution entry. Each imported invoice should have a Ctrl Acct amount that matches the total of all distribution lines linked to the same invoice.

'''f7 - Descrip''' - Distribution note entry for non-control account lines

==AP Invoice Import Reconciliation==

Reconciling imported data should begin with spot-checking several records field-by-field for complete data import. Pick records from the source file that have the most data columns filled in. Verify that all source file data fields imported correctly and display as expected.

Review the TERMS rule for any unexpected records added to the rule. Depending on the number of records involved, the rule maintenance records can be cleaned up, and the associated Remit To records can be manually updated. Otherwise, clean up the TERMS rule, then delete the imported records, re-scrub the source file, and re-import.

Run the AP Aging Report and compare the open AP balance against the AP control account GL balance. If the source data was provided along with a clear GL cutoff balance, the two balances should be equal. Look for any data issues, such as incorrect aging, or missing details.

Run the AP Invoice Report and compare against imported data. Make sure all records and all data fields report as expected.

Run the Approve AP Invoices process and spot-check a few individual invoices for approval balances and settings. Try approving a single invoice using the 'A2P' button and look for any issues with approval amounts.

Verify that all 1099 amounts imported correctly by spot-checking several different vendors.

Review the imported invoices in the Organization Air Hammer and confirm that data displays as expected.

==AP Invoice Import Additional Steps==

There are no additional steps required to complete the AP Invoice import. The AP Check Import can be run after the AP Invoice Import, if requested.

==AP Invoice Import Database Tables==

'''APMAST''' - Each imported invoice from the Header file creates a new KEYNO in the APMAST TABLE, linked to the imported APINVNO value. The APMAST KEYNO value is the link to the APDIST table (as KEYNOH in APDIST).

'''APDIST''' - Each imported distribution detail line will create an entry in the APDIST table. The KEYNOH value should match the APMAST KEYNO value for the associated AP invoice. The PTYPE will be 'D' for distribution details, and 'C' for Control lines. Note that imported AP Check details will also create details in the APDIST table, so be careful of deleting any unintended records.

[[Category: Accounts Payable]]
[[Category: Import Guides]]

File:PAX3.png

2020-10-15T20:19:04Z

Jared:

File:PAX2.png

2020-10-15T20:18:53Z

Jared:

File:PAX1.png

2020-10-15T20:18:40Z

Jared: