Adjutant Wiki - User contributions [en]

Profile Import Guide

2023-03-07T17:08:08Z

Tcampbell:

__NOTOC__
==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.

==Profile Import Notes==

===Timing and Preparation===

The Profile Import should occur soon after the Item Master records have been imported and reviewed.

===General Notes===

The Profile Import will add profile records if they do not exist, but can also be used to update/replace existing records. The update function will replace all matched profile record details with the data in the latest import file.

The Profile Import creates profile data in a profile database linked to the item number. The profile data is displayed in Item Master through a department item attribute with the 'PROFILE' form tied to the attribute. The profile import process will not create the item department attribute. You must assign the department attribute in order for the imported profile details to display.

===Profile Rules Special Reflexes===

Profile Rule Maintenance records with number designations in the rule name have special reflexes designed to handle custom lists per item type. The reflexes use specific keywords in the associated item description to match item types to certain rule numbers. The item description names and their associated rule numbers are listed below.

*ONE: All profile rules with ONE in the rule name are coded to match against the following keywords in the item description
**PANEL
**TRIM
**SSR (SSR uses the PWIDTHTHREE rule for width, but uses ONE for all others)

*TWO: All profile rules with TWO in the rule name are coded to match against the following keywords in the item description
**CEE
**ZEE
**EAVE STRUT
**PRESS BRAKE
**CHANNEL

*THREE: The only profile rule with THREE in the rule name is Profile Width Three (PWIDTHTHREE) and is matched against SSR in the item description.

If the associated item description has text that exactly matches any of the bulleted items above, the profile screen drop-down list will be limited to only rule entries from the corresponding numbered rule. For example, if editing the profile color details for an item with 'PRESS BRAKE' in the item description, only items from PCOLORTWO will show up in the drop-down as valid for 'PRESS BRAKE' items.

If the associated item description does not have any text that matches any of the bulleted items above, the drop-down list will include ALL of the entries from ONE and TWO (and THREE for the Width drop-down). For example, if editing the profile color details for an item with the description 'Generic Item', the drop-down for profile color will include ALL of the entries from PCOLORONE and PCOLORTWO.

This can mean that items with descriptions that do not fall exclusively into the keywords above can end up displaying duplicate values in the drop-downs if the same profile names appear in both the ONE and TWO versions of the rule. Selecting either of the duplicated displayed profile detail options is generally fine, since they are both valid options. It will not matter if the option is selected from the ONE or TWO rule record.

The special reflexes need to be understood when building the profile rules. They also need to be understood when importing profile details. Imported details may import to the database, but may not show up in the profile screen if the combination of item description and numbered profile rule details prevent the imported profile information from showing up in the profile drop-down selection.

==Profile 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.

For consistency, and to avoid issues with conflicting details, you should always use ALL CAPS for the profile text1 values. There are several layers of coding to match the profile details and profile keys to various machine interfaces. Many of the third-party interfaces will generate errors or fail to validate details if they are not passed in ALL CAPS. To avoid errors and possible data mismatch issues, you should always use ALL CAPS for the imported profile details, which should match the ALL CAPS profile rule details. The following data fields should be updated to ALL CAPS before importing:

*Gauge (generally a number, but can include text)
*Profile
*Color
*Material
*Machine
*Width (generally a number, but can include text)

The fields above are all tied to profile rules, and the rules must contain the corresponding data in order to import. Review amd standardize spelling, capitalization, etc, before attempting to import. The import will not add rule details.

'''Width and Gauge: ''' Review these columns carefully prior to import. If Width is entered as a fraction (8 15/16, for example), the Excel column data may display the fraction as entered, however, Excel will automatically store the value as a decimal number (8.9375). If the customer's data should be imported as as a fraction value, the Excel column must be formatted as text in order to store the value correctly.

'''Girth:''' The girth column should be imported as a numeric field with decimals. It will not handle fraction values. For example, if '8 15/16' is entered on the import file, and the column is formatted as text, it will ignore everything after the first digit, and will import as 8.0000. If the customer data is in fractions, you can use the same Excel logic described above with the Width and Gauge fields to your advantage. If the Girth column is formatted as General, Excel will automatically convert the fraction values to decimal equivalents and store the value as a decimal. The import process will import and save the decimal value in this case. Review the data carefully and understand how it will import. Girth is not a rule-based field (even though a rule exists), it imports as a number.

==Profile Import Screen (IMPORTPROFILE)==

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

[[File:Profile_Import.png]]

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

'''Export Template:''' Generates a blank Profile 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.

'''Validate to XLS File:''' Generates a XLS file of errors that will prevent the import from completing.

==Profile Import File Definitions==

Required fields are indicated with an *

'''*f1 - Item''' - Item number in Adjutant that the profile is attached to

'''f2 - Gauge''' - Gauge value (ALL CAPS) for the item profile. The value must exist in the PGAUGEONE or PGAUGETWO rule.

'''*f3 - Profile''' - Profile name (ALL CAPS) for the item profile. The value must exist in the PROFILE rule.

'''f4 - Color''' - Color value (ALL CAPS) for the item profile. The value must exist in the PCOLORONE or PCOLORTWO rule.

'''f5 - Girth''' - Numerical girth (up to 4 decimals) for the item profile

'''f6 - Material''' - Material value (ALL CAPS) for the item profile. The value must exist in the PMATONE or PMATTWO rule.

'''f7 - Machine''' - Production machine name (ALL CAPS) for the item profile. The value must exist in the PMACHINE rule.

'''f8 - Width''' - Width value (ALL CAPS) for the item profile. The value must exist in the PWIDTHONE, PWIDTHTWO, or PWIDTHREE rule.

'''f9 - ExcTrimGen''' - Enter 'Y' to check the 'Exclude from TrimGenius' box for the item profile

'''*f10 - ShortDesc''' - Short description (up to 50 characters) for the item profile

'''f11 - TypeDesc''' - Longer description (up to 100 characters) for the item profile

==Profile 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 profile data throughout production testing for accuracy.

==Profile Import Additional Steps==

There are no additional steps required for the BOM Import.

==Profile Import Database Tables==

'''PROFILEXRF''' - Profile details are stored in the PROFILEXRF table, linked to the item IKEY. Each imported record will have a unique PROFKEY value tied to the IKEY. There should no be duplicate IKET records. Only one profile record should exist per item.

'''PCXREF''' - Profile details are displayed in Item Master through the linked PROFILE form on the department item attribute. The Profile Import doesn't actually update the PCXREF table, but it may be helpful to find the associated department attribute records. The PCXREF TYPE field will be the name from the department item attribute rule. It should be the two character department code. The PARENTID and CHILID values should be the item's IKEY value.

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

MBS to Excel

2023-02-27T16:41:21Z

Tcampbell:

==General Description==

'''Default Menu Location''' Transaction >> Importers/Exporters >> MBS/QuestWare Integration >> BOM to Excel

'''URL''' mbstoexcel_S.htm

[[File:MBS_to_excel.png]]

'''Function''' The BOM to Excel interface links an externally created BOM to a project in Adjutant then creates a standardized Excel spreadsheet. The spreadsheet can be edited before importing into Adjutant by using the [[mbsgrid|Excel BOM Importer]].

File:Unitsrule3.png

2023-02-24T15:18:49Z

Tcampbell:

File:Unitsruleexample.png

2023-02-24T15:18:35Z

Tcampbell:

Units of Measure - UNITS Rule

2023-02-24T15:17:37Z

Tcampbell:

__NOTOC__

===General Information===

'''Default Menu Location''' Maintain >> System >> Rule Maintenance

'''URL''' RuleMain_S.htm?rulename=UNITS

'''Function''' Set up units of measure for items in system.

[[image:unitsrule.png]]

===Text Values===

'''NAME:''' The name of the unit as you wish it to appear in the system.

'''BASE UNIT:''' The base unit of conversion.

'''GROUP:''' The group the unit belongs in (Unit Group on ItemMaster).

'''FACTOR:''' Enter the factor from the first unit (Name per Base Unit)

'''FACTOR2:''' Enter the factor for the second unit (Base Unit per Name)

[[image:unitsruleexample.png]]

In the example above:
FACTOR is 16 OZ (Name) per 1 LBS (Base Unit)
FACTOR2 is equal to 0.0625 LBS (Base Unit) per 1 OZ (Name).

===Logic Values===

'''Default''' Flags this as the default Unit when no unit is specified. In the majority of cases, the only rule detaul that should have this flag is EA, with a Base Unit of EA and a Group of IND (see picture below)

'''Default Grp''' Flags this as the default Unit Group when none is specified. Only one entry should have this flag, and this setting should almost never be modified.

'''No Conversion''' If this flag is checked, Adjutant will not attempt to perform any conversions for this unit.

[[image:unitsrule3.png]]

[[Category:Rule Maintenance]]

Units of Measure - UNITS Rule

2023-02-24T14:54:13Z

Tcampbell:

File:Unitsrule.png

2023-02-24T14:53:30Z

Tcampbell:

Units of Measure - UNITS Rule

2023-02-24T14:53:18Z

Tcampbell: Created page with "__NOTOC__ ===General Information=== '''Default Menu Location''' Maintain >> System >> Rule Maintenance '''URL''' RuleMain_S.htm?rulename=UNITS '''Function''' Set up units..."

Seshippingrecordlist

2023-02-23T17:33:09Z

Tcampbell: Tcampbell moved page Seshippingrecordlist to SE Shipping Record List

#REDIRECT [[SE Shipping Record List]]

SE Shipping Record List

2023-02-23T17:33:09Z

Tcampbell: Tcampbell moved page Seshippingrecordlist to SE Shipping Record List

SE Shipping Record List

2023-02-23T17:32:43Z

Tcampbell: Created blank page

Contract Management Setup Options

2023-02-15T15:36:21Z

Tcampbell: Created page with "__NOTOC__ ===Contract Management Setup Options=== '''CHECKOVERLAP''' - When enabled, issues an alert that the contract dates overlap with an existing contract, but still allo..."

__NOTOC__
===Contract Management Setup Options===

'''CHECKOVERLAP''' - When enabled, issues an alert that the contract dates overlap with an existing contract, but still allows users to save.

'''NEWLOOKUP''' - NEWLOOKUP

'''NEWMSNNUM''' - If set, then map project drop folders to Project Number instead of Project ID.

MBS to Excel

2023-02-02T18:59:09Z

Tcampbell:

Sales Tax Calculations on Quote/SO/Invoice

2023-01-26T20:55:24Z

Tcampbell:

__NOTOC__
===General Information===

Sales Tax is calculated according to the Tax Table of the Ship To listed on each Quote/Sales Order/Invoice line.

'''If the SOLDTO record is marked as Tax Exempt all SHIPTO children will automatically be tax exempt, regardless of the Tax Table that is selected.'''

===Tax Tables===

Tax Tables are maintained in the Tax Table Master screen.

They are composed of at least one Tax Rate. There are six different types of Tax Rates: State, County, City, Metro Transit Authority (MTA), Special Purpose District (SPD), and Other.

Companies subscribed to the ABIS Sales Tax Update Service have their Tax Tables updated on the 1st of each month.

===Sales Tax Calculation===

The Quote, Sales Order, and Invoice calculate sales tax per line and per jurisdiction. The shipto address and shipping warehouse of each line is used to assign the tax table for each line. The tax for each jurisdiction is totaled in order to calculate the Extended Tax Amount for each line. This amount for each line is totaled in order to calculate a total sales tax amount.

For shipments to Texas addresses from Texas warehouses, an overlay logic can be used. The overlay tax table is added to the warehouse record in Adjutant. The tax table for the warehouse is used as the base tax table, and the tax table for the shipto address is overlayed on top of the warehouse table. The rates are applied in the following order.

City, County, MTA. SPD. Locals

If the base tax table (whse) plus each piece of the shipto taxtable is less that 8.25, then the piece is added.

Example

The whse tax rate is 7.50%, and the ship to rate is 8.25% (6.25% state, .5% county, 1.5% city)

The 7.5 base + 1.5 city is more than 8.25, so the city cannot be used.

The 7.5 base + .5 count is less than 8.25, so the new rate is 8

These process is carried out for all the parts of the shipto tax rate.

This new rate is then used for the line.

Sales Tax Calculations on Quote/SO/Invoice

2023-01-26T20:55:01Z

Tcampbell: Created page with "__NOTOC__ ===General Information=== Sales Tax is calculated according to the Tax Table of the Ship To listed on each Quote/Sales Order/Invoice line. '''If the SOLDTO record..."

__NOTOC__
===General Information===

Sales Tax is calculated according to the Tax Table of the Ship To listed on each Quote/Sales Order/Invoice line.

'''If the SOLDTO record is marked as Tax Exempt all SHIPTO children will automatically be tax exempt, regardless of the Tax Table that is selected.'''

===Tax Tables===

Tax Tables are maintained in the [http://www.abiscorp.com/AdjWiki/GetFile.aspx?File=Sales%20Tax%5ctaxtablemaster.jpg|Tax Table Master] screen.

They are composed of at least one Tax Rate. There are six different types of Tax Rates: State, County, City, Metro Transit Authority (MTA), Special Purpose District (SPD), and Other.

Companies subscribed to the ABIS Sales Tax Update Service have their Tax Tables updated on the 1st of each month.

===Sales Tax Calculation===

The Quote, Sales Order, and Invoice calculate sales tax per line and per jurisdiction. The shipto address and shipping warehouse of each line is used to assign the tax table for each line. The tax for each jurisdiction is totaled in order to calculate the Extended Tax Amount for each line. This amount for each line is totaled in order to calculate a total sales tax amount.

For shipments to Texas addresses from Texas warehouses, an overlay logic can be used. The overlay tax table is added to the warehouse record in Adjutant. The tax table for the warehouse is used as the base tax table, and the tax table for the shipto address is overlayed on top of the warehouse table. The rates are applied in the following order.

City, County, MTA. SPD. Locals

If the base tax table (whse) plus each piece of the shipto taxtable is less that 8.25, then the piece is added.

Example

The whse tax rate is 7.50%, and the ship to rate is 8.25% (6.25% state, .5% county, 1.5% city)

The 7.5 base + 1.5 city is more than 8.25, so the city cannot be used.

The 7.5 base + .5 count is less than 8.25, so the new rate is 8

These process is carried out for all the parts of the shipto tax rate.

This new rate is then used for the line.

File:Security Bulk Select Permissions.png

2023-01-25T22:10:02Z

Tcampbell:

File:Security Bulk Select Process Group.png

2023-01-25T22:09:39Z

Tcampbell:

File:Security Bulk Sec Main.png

2023-01-25T22:08:39Z

Tcampbell:

Bulk Security Update

2023-01-25T22:07:47Z

Tcampbell:

__NOTOC__
===General Description===

'''Default Menu Location''': Transaction >> System Manager >> Bulk Security Update

'''URL''': BulkSecurityUpdate_S.htm

'''Function''': This screen is used to modify the security and permissions for a user, or multiple users at a time.

[[image:Security_Bulk_Sec_Main.png]]

===Using the Bulk Security Update===

'''STEP 1:''' Select the User/Users which will be updated.

'''STEP 2:''' From the 'Process Group' dropdown, select the Process Group of securities you wish to update (Address Book, Accounts Rec, Accounts Pay, etc).

[[image:Security_Bulk_Select_Process_Group.png]]

'''STEP 3:''' Select which securities the selected users will have from the list of 'tokens'. Tokens are essentially screens or modules. For each token, a user can have the permission to View/Edit/Add/Del/Deny. These are not all inclusive (in other words, a user may be able to VIEW something, but not necessarily have permission to EDIT it).

[[image:Security_Bulk_Select_Permissions.png]]

'''STEP 4:''' Once you have selected the permissions for the user/users, click the UPDATE button in the bottom right hand corner of the screen.

NOTE: The screen must be updated on EACH Process Group. For Example: After finishing the securities for the 'Address Book' Process Group, user must hit the update button before moving to another process group, in order for changes to save.
[[category:Setup Options]]

Bulk Security Update

2023-01-25T21:57:13Z

Tcampbell: Tcampbell moved page Bulksecurityupdate to Bulk Security Update

Bulksecurityupdate

2023-01-25T21:57:13Z

Tcampbell: Tcampbell moved page Bulksecurityupdate to Bulk Security Update

#REDIRECT [[Bulk Security Update]]

Bulk Security Update

2023-01-25T21:56:54Z

Tcampbell: Created blank page

User Record Import Guide

2023-01-25T21:54:19Z

Tcampbell:

__NOTOC__
==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.

==User Record Import Notes==

The Import User screen creates the User in Adjutant attribute record, links it to the Contact ID, and can complete all of the required fields in the User Details tab and the User Password Settings tab. The import program can even establish user security mimics.

===Timing and Preparation===

User in Adjutant details and all of the appropriate named user license flags should be set up as soon as possible once the core system setup items have been completed. User licenses are generally billed from the very beginning of the implementation, so customers should be able to access the system as soon as it is available. Setting up user records immediately avoids a situation where customers are being billed for user licenses that they are unable to use.

All Address Book setup items should be completed prior to beginning the Contacts, Customer, and Vendor imports. The [[Address Book Setup Guide]] covers all of the Rule Maintenance records that should be completed prior to importing customer, vendor and contact records.

The User Import can be completed immediately after the employee contact records have been imported with the [[Contact Import Guide|Import Contacts]] screen, or after they have been added manually. The internal contact records should be added prior to completing the Customer and Vendor imports. User records, resource records, salespersons, account managers, buyers, and project attributes should be established for employee records prior to importing the Organization records so that links to salespersons, account managers, and buyers can be made in the organization import files.

===General Notes===

Many of the fields on the Import User Records template are mandatory. Required fields are noted below in the file definitions section.

The Password Settings fields must be filled in on the import file. CID password setting defaults are not loaded during the import.

==User Record Import File Data Scrubbing==

Since nearly all of the data fields in the User Import file are Adjutant security specific fields, the customer will not have a source file to provide for this data. Generally, the only customer-supplied data for this file will be the userids, passwords, and email settings. In many cases the userids and passwords will be generated by ABIS personnel.

Because the data for this file is mostly generated by ABIS personnel to speed up the process of adding users, there is no customer data scrubbing required.

==Import User Screen (IMPORTUSER)==

Menu Location: Transaction>>Importers/Exporters>>Other>>Import User Records

[[File:IMPORTUSER.png]]

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

'''Export Template:''' Generates a blank User 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.

'''Validate to XLS File:''' Selecting this box will create an XLS 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.

==User Record Import File Definitions==

Required fields are indicated with *

'''*f1 - Contid''' - Contact ID (CONTID (keyno) of contact record)

'''f2 - Userid''' - Desired User ID. If left blank, the system will generate a UserID based of the contact name.

'''f3 - Password''' - Desired Password

'''f4 - Admin''' - Should the user be an Admin in Desktop (Y/N)

'''f5 - Defprinter''' - User's Default Printer ID

'''f6 - Termid''' - Scanner terminal ID

'''f7 - Freq''' - Scanner frequency setting

'''*f8 - Defloctid''' - Default Warehouse name. Enter the Warehouse name, not the LOCTID value.

'''*f9 - Defcid''' - Default CID name

'''f10 - DefLaser''' - Default Laser Printer name

'''f11 - DefLaserNo''' - Default Laser Printer ID

'''*f12 - Lang''' - User's default language. Use ENG for English.

'''*f13 - Active''' - Sets the Active field in the USERID datatable. Should be Y for all new user imports.

'''f14 - Ext''' - Phone extension

'''f15 - DefScreen''' - Blank will default to 'CID Pulldown for Menu'. In order to set a different screen default, it must be entered in the format 'do form sogrid' where you would replace the 'sogrid' part with the desired screen name.

'''f16 - FaxUser''' - Fax UserID value

'''f17 - FaxPass''' - Fax Password value

'''f18 - FaxPress''' - Fax Press Name value

'''*f19 - DMenu''' - Default menu name. Must match exactly to a valid saved menu. 'Default' is the most common entry.

'''f20 - SMTPserver''' - SMTP server name

'''*f21 - ReqLet''' - Require letters in password. Enter Y or N.

'''*f22 - ReqNum''' - Require numbers in password. Enter Y or N.

'''*f23 - ReqOth''' - Require special characters in password. Enter Y or N.

'''*f24 - MaxLen''' - Maximum length for password. DO NOT LEAVE BLANK. The number entered must be equal to or higher than the entry in MinLen, otherwise there will be issues during password reset. If left blank, it will import zero and prevent any password entry over 0 characters.

'''*f25 - MinLen''' - Minimum length for password. For best practices, enter a value of 8 or higher.

'''f26 - Expin''' - Number of days for password to expire

'''*f27 - NeverExp''' - Enter Y to check the 'Never Expire' box. Enter N to expire password according to the 'Expire In' days.

'''f28 - ReuseIn''' - Allow the same password to be reused in '''XX''' days

'''f29 - LoAfter''' - Lock the user out after '''##''' unsuccessful login attempts. DO NOT LEAVE BLANK. This entry must be greater than 0.

'''f30 - LoFor''' - If the user is locked out, lock them out for '''##''' minutes

'''f31 - PasswordExpDate''' - Sets the manual password expiration date in the USERID datatable

'''*f32 - ActiveUser''' - Enter Y to set the 'Active User' flag. Enter N to leave the 'Active User' field blank.

'''*f33 - NoChange''' - Enter Y to set the 'User Cannot Change Password' flag. Enter N to leave it blank and allow password changes.

'''*f34 - ForceChange''' - Enter Y to set the 'Change Password at Next Login' flag. Enter N to leave it blank.

'''f35 - SMTPuser''' - SMTP User ID

'''f36 - SMTPpassword''' - SMTP password

'''f37 - SMTPdomain''' - SMTP domain

'''*f38 - ESMTP''' - Enter Y to set the ESMTP flag. Enter N to leave it blank.

'''*f39 - DNUFlag''' - Enter Y to set the Desktop Named User flag. Enter N to leave it blank.

'''*f40 - WNUFlag''' - Enter Y to set the Web Named User flag. Enter N to leave it blank.

'''*f41 - TNUFlag''' - Enter Y to set the Terminal Named User flag. Enter N to leave it blank.

'''f42 - MimicID''' - Enter the CONTID value for the UserID that this record should mimic

'''f43 - SMTPPort''' - SMTP port number

'''f44 - TUserID''' - Terminal UserID for scanners

'''f45 - TuPassword''' - Desired password for scanners

'''f46 - DST''' - Enter Y to set the DST (Daylight Savings Time) flag. Enter N to leave it blank.

'''f47 - GMTOff''' - Enter the number of hours to offset the user's system time based on GMT. Negative hours are allowed.

'''*f48 - SMTPTLS''' - Enter Y to set the SMTP TLS flag. Enter N to leave it blank.

'''*f49 - SMTPSSL''' - Enter Y to set the SMTP SSL flag. Enter N to leave it blank.

'''f50 - SMTPAuth''' - Sets the SMTP Authorization type. Entry must exactly match one of the system-defined types. Most common entry is 'Default'. Other possible entries are 'None', 'Login', and 'Plain'.

==User Record 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.

Verify that the following fields imported as expected by spot-checking the User In Adjutant Detail tab:

*Default Screen
*Default Menu
*Mimic ID
*SMTP Authorization

Review the License Status screen and verify that the expected number of user licenses matches the value in the Actual column for each license type.
all phone numbers and phone codes imported as expected. Spot-check several phone1 through phone4 records.

Test several passwords by logging in, or having imported users log in and verify that basic log in works as expected.

==User Record Import Additional Steps==

The User Import process does not establish security tokens, unless imported users are mimics of a user with established security tokens. Set up desired security for each user by using Bulk Security Update or by setting up mimic users with security.

'''ABIS-ONLY:''' For new clients, create a Contact Import file from the user data that can be imported into live ABIS. This contact import will build the contact names and email addresses for use with the support ticketing system.

==User Record Import Database Tables==

Importing user records can affect the following databases:

'''USERID''' - Each imported user is assigned a unique USERID value and a unique KEYNO. Each USERID is linked to a CONTID that matches the user's contact record.

'''PCXREF''' - Each imported user will create an entry in this table. The PTABLE value for all of these should be CONTACT, and the TYPE value should be USER. The PARENTID and CHILDID values will correspond to CONTIDs linked to the USERID.

[[Category: Address Book]]
[[Category: Import Guides]]
[[Category: System Manager]]

File:IMPORTUSER.png

2023-01-25T21:54:02Z

Tcampbell: Tcampbell uploaded a new version of File:IMPORTUSER.png

Mimic/Copy User Security

2023-01-25T21:48:37Z

Tcampbell:

__NOTOC__

===General Description===

'''Default Menu Location''': Maintain >> Address Book >> Contact >> User in Adjutant

'''Screen Name''': USERS

'''Function''': The function of Mimic/Copy allows you to copy one user's security rights to another user.

===How To Mimic/Copy User Security===

'''STEP 1:''' Open the Contact/User whose security you will be updating, and then click the 'User in Adjutant' attribute.

'''STEP 2:''' In this screen, click the 'User Security' tab, and click the edit button in the upper left hand corner of the screen.

'''STEP 3:''' Type in the user whose security you wish to copy and click the Copy button (if the user is from another CID, pick that CID from the drop down box).

[[image:Security_Mimic_UserScreen3.png]]

[[category:Setup Options]]

File:Security Mimic UserScreen3.png

2023-01-25T21:48:23Z

Tcampbell:

Mimic/Copy User Security

2023-01-25T21:48:02Z

Tcampbell: Created page with "__NOTOC__ ===General Description=== '''Default Menu Location''': Maintain >> Address Book >> Contact >> User in Adjutant '''Screen Name''': USERS '''Function''': The fu..."

File:Security Profile User info.png

2023-01-25T21:39:54Z

Tcampbell:

File:Security Profile Create.png

2023-01-25T21:39:05Z

Tcampbell:

Security Profiles

2023-01-25T21:36:26Z

Tcampbell: Created page with "===How To Create A Security Profile=== '''STEP 1:''' Create a user in Adjutant2020 from the Contact screen. For the 'Name' of the contact, type in the Security Profile you wi..."

===How To Create A Security Profile===

'''STEP 1:''' Create a user in Adjutant2020 from the Contact screen. For the 'Name' of the contact, type in the Security Profile you wish to use. For example, the name could be 'Client Billing Profile'. Give the Contact a 'User In Adjutant' attribute.

[[image:Security_Profile_Create.png]]

'''STEP 2:''' On the 'User In Adjutant' screen, make sure the user is active, but has NO LICENSES:

[[image:Security_Profile_User_info.png]]

Now this profile can be given permissions and securities like any other user in Adjutant, and this profile can be used as a security 'role' when creating new users (this can be done by using the Copy/Mimic security function).

[[category:Setup Options]]

Route Maintenance

2023-01-25T15:00:41Z

Tcampbell:

__NOTOC__

===General Description===
'''Default Menu Location:''' Maintain >> Routing >> Route Maintenance

'''URL:''' RouteMain_S.htm

'''Function''' The Route Maintenance screen is used to add and maintain routes of standard tasks.

[[image:routemain.png]]

===Route Creation===

Select the add button at the top left. Type in the name of the route you want to make in the top field. Once the name is correct, click the save button.

Select add and enter the task that will come first in the route. Select the other options for that task and hit save. The first task must always have a Seq# of '''1'''.

Add as many tasks as necessary in the order they should occur.

The settings tab of the Route Maintenance screen will control what event in the system starts the route. Routes can be manually started from different areas of Adjutant, but for an event to start a route, it must be selected on this screen. The events that show up in the list to choose from are generated from the Event List rule.

[[image:routemaintsettings.png]]

===Fields===

'''Route Name:''' The name of the route.

'''Task:''' The standard task you are entering or editing in the route.

'''Predecessors:''' The predecessor(s) for the standard task you have selected.

'''Create Upon x of Line #:'''
Select the event and task to create this task on.

:::::CR-''Create'': Will start the task being entered at the creation of the Line# entered

:::::AS-''Assign'': Will start the task being entered when the Line# entered is Assigned to a Resource

:::::CO-''Complete'': Will start the task being entered upon the completion of the Line# entered

:::::ST-''Start'': Will start the task being entered once the Line# entered is "Punched-in" or Started

'''Constraint:''' Select the constraint.

:::::ASAP will be scheduled soon as possible

:::::ALAP will be scheduled as late as possible

:::::Fixed will be scheduled at a fixed time and not moved.

'''Cycle:''' Select the cycle, to fire task from Line # Selected.

:::::Start-Start: Schedules the start of the task being entered to fire at the same time as the Line# entered

:::::Start-Finish: Schedules the start of the task being entered to fire once the Line# entered is completed

'''Lag Time:''' Select the lag time according to your cycle in days (d), weeks (w), months (m). For example, 1 day would be typed as 1d. '''''This field must not be left blank'''''

'''DTree Form:''' This box needs to be checked when a decision tree is being added to the route. The decision tree line will always be the end of the route.

:::::Line# (next to DTree Form) - This will pull the decision tree form from the task on the line specified here.

[[category:Workflow Routing]]

File:Routemaintsettings.png

2023-01-25T14:58:26Z

Tcampbell:

File:Routemain.png

2023-01-25T14:56:59Z

Tcampbell:

Route Maintenance

2023-01-25T14:55:45Z

Tcampbell:

__NOTOC__

===General Description===
'''Default Menu Location:''' Maintain >> Routing >> Route Maintenance

'''URL:''' RouteMain_S.htm

'''Function''' The Route Maintenance screen is used to add and maintain routes of standard tasks.

[[image:routemain.png]]

===Route Creation===

Select the add button at the top left. Type in the name of the route you want to make in the top field. Once the name is correct, click the save button.

Select add and enter the task that will come first in the route. Select the other options for that task and hit save. The first task must always have a Seq# of '''1'''.

Add as many tasks as necessary in the order they should occur.

The settings tab of the Route Maintenance screen will control what event in the system starts the route. Routes can be manually started from different areas of Adjutant, but for an event to start a route, it must be selected on this screen. The events that show up in the list to choose from are generated from the Event List rule.

[[image:routemaintsettings.png]]

===Fields===

'''Route Name:''' The name of the route.

'''Task:''' The standard task you are entering or editing in the route.

'''Predecessors:''' The predecessor(s) for the standard task you have selected.

'''Create Upon x of Line #:'''
Select the event and task to create this task on.

:::::CR-''Create'': Will start the task being entered at the creation of the Line# entered

:::::AS-''Assign'': Will start the task being entered when the Line# entered is Assigned to a [^Resource Screen|Resource]

:::::CO-''Complete'': Will start the task being entered upon the completion of the Line# entered

:::::ST-''Start'': Will start the task being entered once the Line# entered is [^Virtual Time Clock|"Punch-in"]/ or Started

'''Constraint:''' Select the constraint.

:::::ASAP will be scheduled soon as possible

:::::ALAP will be scheduled as late as possible

:::::Fixed will be scheduled at a fixed time and not moved.

'''Cycle:''' Select the cycle, to fire task from Line # Selected.

:::::Start-Start: Schedules the start of the task being entered to fire at the same time as the Line# entered

:::::Start-Finish: Schedules the start of the task being entered to fire once the Line# entered is completed

'''Lag Time:''' Select the lag time according to your cycle in days (d), weeks (w), months (m). For example, 1 day would be typed as 1d. '''''This field must not be left blank'''''

'''DTree Form:''' This box needs to be checked when a decision tree is being added to the route. The decision tree line will always be the end of the route.

:::::Line# (next to DTree Form) - This will pull the decision tree form from the task on the line specified here.

[[category:Workflow Routing]]

Route Maintenance

2023-01-25T14:47:18Z

Tcampbell: Tcampbell moved page Routemain to Route Maintenance

Routemain

2023-01-25T14:47:18Z

Tcampbell: Tcampbell moved page Routemain to Route Maintenance

#REDIRECT [[Route Maintenance]]

Route Maintenance

2023-01-25T14:47:02Z

Tcampbell: Created blank page

Submit to Production

2023-01-23T22:05:19Z

Tcampbell: Created page with "__NOTOC__ ===General Information=== '''Default Menu Location''': None - the Submit to Production screen is called from the Sales Order screen when the SOASKPRODQTY setup op..."

__NOTOC__

===General Information===

'''Default Menu Location''': None - the Submit to Production screen is called from the Sales Order screen when the SOASKPRODQTY setup option is turned on.

'''Screen Name''': S2P

'''Function:''' Allows users to view and modify the quantities of each production item before submitting the order to production.

[[image:SubmitToProduction.png]]

===Fields/Columns===

'''Qty to Produce''': This column can be changed. The qty shown here is what will be submitted to production. Any qty not equal to the order qty on the SO will be highlighted in yellow. Any item with a qty of zero will not be submitted to production.

'''Stk/NonStk''': Displays whether the production item is a stock item or not. Stock items can be pulled from stock.

'''On Hand''': The current on hand qty of the item in the same warehouse as the production plant on the SO line.

'''Avaliable''': The current available qty (on hand less allocated) of the item in the same warehouse as the production plant on the SO line.

'''Pull From Stock''': This column can be changed if the item is marked as stock.

'''Force Together''': Check this box for multiple lines if you want to force them together onto a PWO. This is useful for certain cases where you want to group items together in production that wouldn't normally be grouped.

'''Single PWO''': Check this box for any line that you want separated onto its own PWO.

Neither the Force Together or Single PWO columns are applicable for production environments where a single item is always on a PWO (SINGLEPWO setup option turned on).

===Buttons===

'''All''': Sets the Qty to Produce equal to the SO order qty for each line.

'''None''': Sets the Qty to Produce equal to zero for each line.

'''Non-Stk Only''': Sets the Qty to Produce equal to the SO order qty for non-stock items and the Qty to Produce equal to zero for stock items.

'''Qty Needed''': Sets the Qty to Produce equal to the difference between the SO order qty and the Available qty, unless the Available Qty is less than zero in which case the Qty to Produce is set to the SO Order Qty.

'''Split''': Allows you to split one production line into multiple yields. A screen will pop up and allow you to enter the number of yields and the new qty for each one. The total qty of the yields must match the Qty to Produce.

'''Produce''': Sends the items to production and makes Production Work Orders.

===Setup Options===

The SOASKPRODQTY setup option must be turned on in order for this screen to pop up when you submit an order to production.

The S2PFULLQTY setup option sets the Qty to Produce column equal to the Order Qty, regardless of stock status and on hand availability. With this setup option turned off, the Qty to Produce and Pull From Stock columns are automatically adjusted accordingly to the item's Available Qty.

[[image:s2pfullqyt]]

[[Category:Order Entry]]

PO Buyout Config Report Codes Rule - BUYCONFIGRCODE

2023-01-23T20:58:14Z

Tcampbell:

__NOTOC__

===General Information===

'''Default Menu Location''' Maintain >> System >> Rule Maintenance

'''URL''' RuleMain_S.htm?rulename=BUYCONFIGRCODE

'''Function''' This rule controls which configuration questions are displayed in the SO link window on the purchase order (example below).

[[image:BUYCONFIGRCODE.png]]

===Rule Setup – Text Fields===

'''Configuration''' This is what you want the column label to be on the SO link screen.

'''Report code:''' The report code for the value you want to display in the column.

===Rule Setup – Number Fields===

'''Sorter:''' This is the order you want the columns to display.

[[category: Rule Maintenance]][[category:Purchasing]]

File:BUYCONFIGRCODE.png

2023-01-23T20:56:48Z

Tcampbell:

PO Buyout Config Report Codes Rule - BUYCONFIGRCODE

2023-01-23T20:55:13Z

__NOTOC__

===General Information===

'''Default Menu Location''' Maintain >> System >> Rule Maintenance

'''URL''' RuleMain_S.htm?rulename=BUYCONFIGRCODE

'''Function''' This rule controls which configuration questions are displayed in the SO link window on the purchase order (example below).

[[image:BUYCONFIGRCODE.png]]

===Rule Setup – Text Fields===

'''Text:''' This is what you want the column label to be on the SO link screen.

'''Rcode:''' The report code for the value you want to display in the column.

===Rule Setup – Number Fields===

'''Sorter:''' This is the order you want the columns to display.

[[category: Rule Maintenance]][[category:Purchasing]]

Purchase Order - Line Item View

2023-01-23T20:48:17Z

Tcampbell:

__NOTOC__

===General Information===

'''Default Menu Location''' The Purchase Order Icon is available from the toolbar.

'''URL''' Orders_S.htm

'''Function''' The Item View tab gives the user a summary view of the line-item information for that Purchase Order.

===Additional Functions===

'''Cost Edits'''

Users have the ability to quickly edit costs for each line item from this tab. First, put the order into Edit Mode. Once in Edit Mode, the "Pur Cost" column header will turn red, indicating that it is ready for editing. Then, simply click on the line item you would like to change, and type in the new cost.

After completing all the needed edits, click on the save button from the action panel on the right side of the screen. After saving, the new costs will be visible on the Main tab, and the Item View tab.

[[image:purchaseordermod.gif]]

[[category:Purchasing]]

PO Extra Columns Rule - POCOLUMNS

2023-01-23T20:39:37Z

Tcampbell:

__NOTOC__
===General Information===

'''Default Menu Location''' Maintain >> System >> Rule Maintenance

'''URL''' RuleMain_S.htm?rulename=POCOLUMNS

'''Function''' This rule allows users to define custom columns to display Sales Order Configuration (SOC) details on the Purchase Order Line Items and Line Item View screens. Associated SOC data linked to the defined SOC Report Code is shown in the line item grid view for any Report Codes defined in this rule. The functionality is similar to the Sales Order Columns (SOCOLUMNS) rule.

[[image:POCOLUMNS.png]]

===Rule Setup – Text Fields===

'''Column Label:''' Enter the column label for the associated SOC Report Code data.

'''Report Code:''' Enter the alphanumeric report code from the SOC question that you want to display.

===Rule Setup – Number Fields===
'''Sort Order:''' Assign a numeric sort order (1-5).

===Rule Setup – Logic Fields===
'''There are no Logic fields in use.'''

[[category:Rule Maintenance]] [[category:Purchasing]]

PO Extra Columns Rule - POCOLUMNS

2023-01-23T20:39:15Z

Tcampbell:

File:POCOLUMNS.png

2023-01-23T20:38:14Z

Tcampbell:

PO Extra Columns Rule - POCOLUMNS

2023-01-23T20:37:38Z

Tcampbell:

{TOC}

===General Information===
'''Default Menu Location''' Maintain >> System >> Rule Maintenance

'''Function''' This rule allows users to define custom columns to display Sales Order Configuration (SOC) details on the Purchase Order Line Items and Line Item View screens. Associated SOC data linked to the defined SOC Report Code is shown in the line item grid view for any Report Codes defined in this rule. The functionality is similar to the Sales Order Columns (SOCOLUMNS) rule.

[[image:POCOLUMNS.png]]

===Rule Setup – Text Fields===

'''Column Label:''' Enter the column label for the associated SOC Report Code data.

'''Report Code:''' Enter the alphanumeric report code from the SOC question that you want to display.

===Rule Setup – Number Fields===
'''Sort Order:''' Assign a numeric sort order (1-5).

===Rule Setup – Logic Fields===
'''There are no Logic fields in use.'''

[[category:Rule Maintenance]] [[category:Purchase Orders]]

PO Extra Columns Rule - POCOLUMNS

2023-01-23T20:37:05Z

Tcampbell: Created page with "{TOC} ===General Information=== '''Default Menu Location''' Maintain >> System >> Rule Maintenance '''Function''' This rule allows users to define custom columns to displ..."

{TOC}

===General Information===
'''Default Menu Location''' Maintain >> System >> Rule Maintenance

'''Function''' This rule allows users to define custom columns to display Sales Order Configuration (SOC) details on the Purchase Order Line Items and Line Item View screens. Associated SOC data linked to the defined SOC Report Code is shown in the line item grid view for any Report Codes defined in this rule. The functionality is similar to the Sales Order Columns (SOCOLUMNS) rule.

[[image:POCOLUMNS.png]]

===Rule Setup – Text Fields===

'''Column Label:''' Enter the column label for the associated SOC Report Code data.

'''Report Code:''' Enter the alphanumeric report code from the SOC question that you want to display.

===Rule Setup – Number Fields===
'''Sort Order:''' Assign a numeric sort order (1-5).

===Rule Setup – Logic Fields===
'''There are no Logic fields in use.'''
[[categoru:Rule Maintenance]] [[category:Purchase Orders]]

File:Printpolabels.png

2023-01-23T20:20:42Z

Tcampbell:

Print Purchase Order Labels

2023-01-23T20:20:25Z

Tcampbell: /* General Description */

__NOTOC__

===General Description===

'''Default Menu Location''' Reports >> Purchase Order >> Purchase Order Labels

'''URL''' PoLabel_S.htm

'''Function''' The Purchase Order label screen allows the printing of items on a purchase order onto labels. Select the labels to be printed by checking them off. All or none can be selected and the system will automatically check off all items or uncheck all items. Labels to skip determines the position to begin printing the labels on. Label Printer or Laser printer can be selected.

[[image:printpolabels.png]]

[[Category: Purchase Orders]]

Print Purchase Order Labels

2023-01-23T20:20:01Z

Tcampbell:

__NOTOC__

===General Description===

'''Default Menu Location''' Reports >> Purchase Order >> Purchase Order Labels

'''Screen Name''' POLABEL

'''Function''' The Purchase Order label screen allows the printing of items on a purchase order onto labels. Select the labels to be printed by checking them off. All or none can be selected and the system will automatically check off all items or uncheck all items. Labels to skip determines the position to begin printing the labels on. Label Printer or Laser printer can be selected.

[[image:printpolabels.png]]

[[Category: Purchase Orders]]