Adjutant Wiki - User contributions [en]

Profile Color One - PCOLORONE Rule

2024-08-05T15:04:43Z

Amohammad:

__NOTOC__
===General Information===

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

'''Function''' This rule allows users to define profile colors used in production labeling, reporting, and machine interfaces.

'''Special''' Refer to the Special Reflexes section below for additional information on how the numbered profile rules work.

[[File:Profile_Color_One_Rule.png]]

===Rule Setup – Text Fields===

'''Color:''' Enter the profile color name (use ALL CAPS)

'''Description:''' Enter an alternate description for the color

'''Color Code:''' Enter an abbreviation of the color

===Rule Setup – Number Fields===

'''Color ID:''' Assign a numerical ID for the profile color

===Rule Setup – Logic Fields===

'''There are no Logic fields in use.'''

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

===Profile Naming Best Practices===

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, we recommend using ALL CAPS for the profile rule details.

[[Category:Item Control]] [[Category:Production]] [[Category:Rule Maintenance]]

Profile Color One - PCOLORONE Rule

2024-08-05T15:04:35Z

Amohammad:

__NOTOC__

===General Information===

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

'''Function''' This rule allows users to define profile colors used in production labeling, reporting, and machine interfaces.

'''Special''' Refer to the Special Reflexes section below for additional information on how the numbered profile rules work.

[[File:Profile_Color_One_Rule.png]]

===Rule Setup – Text Fields===

'''Color:''' Enter the profile color name (use ALL CAPS)

'''Description:''' Enter an alternate description for the color

'''Color Code:''' Enter an abbreviation of the color

===Rule Setup – Number Fields===

'''Color ID:''' Assign a numerical ID for the profile color

===Rule Setup – Logic Fields===

'''There are no Logic fields in use.'''

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

===Profile Naming Best Practices===

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, we recommend using ALL CAPS for the profile rule details.

[[Category:Item Control]] [[Category:Production]] [[Category:Rule Maintenance]]

Apply Cash Receipts

2024-08-05T15:04:14Z

Amohammad:

__NOTOC__
== General Information ==

'''Default Menu Location:''' Transaction >> Accounts Receivable >> Apply Cash Receipts

'''Screen Name:''' CASHREC

'''Function:''' The Apply Cash Receipts screen is used to enter cash receipts and apply them against open AR invoices.

To apply cash to an invoice, click the '''New Cash Receipt''' button. Then enter the Custno (customer number) or Company (customer name). The system will automatically bring up all open invoices for that customer. Select the appropriate Cash Account and enter the Cash Amount from the customer. Then, check which invoices to apply the cash payment to, and the system will automatically allocate the amount of the payment across the invoice(s) selected. The allocated amount can be change by editing the Paid Amt column in the bottom grid.

[[File:Apply_Cash_Receipt_to_Customer_Invoices.PNG]]

To enter an open credit, enter the amount of the credit in Cash Amount and click Save. A modal window will display asking "Create Open Credit with Un-Applied Balance?" Click '''Yes'''. A second modal window will display with fields for the AR Account, Description, and Invoice Status. Fill these out and click '''OK''' to issue the unapplied amounts as an Open Credit.

[[File:Create_Open_Credit.PNG]]

[[File:Select_Account_for_Open_Credit.PNG]]

After the payment has been allocated across the selected invoices, click '''Save''' to complete the cash receipt.

===Fields===

'''Custno/Company:''' Enter/select the customer that the payment is from.

'''Invno:''' Enter/select a specific invoice to pay with the cash receipt.

'''Adjustment Account/Description:''' The number and description of the offsetting account that will be used for adjustments to the invoice (bad debt, bank fees, write-off, etc). Can be set to default to a specific account.

'''Cash Acct:''' Select the appropriate Cash account from the drop down box.

'''Currency:''' Will default based on the Cash Account selected.

'''Cash Amount:''' Enter the amount of the payment.

'''Discount Account:''' The number and description of the offsetting account that will be used for customer discounts. Can be set to default to a specific account.

'''Reference #:''' Enter a reference number for the cash receipt; this may be the check number.

'''Bank Dep #:''' Enter a reference number for the bank deposit (optional); this may be the check number, date or a sequential number of your choice.

'''Transaction Date:''' The date when the transaction will go into Adjutant. This is often referred to as a the accounting date, because this is when the transaction will show as posted to the general ledger.

'''Postmark Date:''' The PostMark Date is the 'paid' date. This is the date which is primarily used for calculating discounts.

'''Project ID:''' Use this field to tie the cash receipt to an existing project in Adjutant, if applicable.

'''Phase:''' Select the phase of the project.

'''Type:''' Select the cash receipt type.

'''Notes:''' Leave any applicable notes or comments for this cash receipt.

'''Balance:''' Displays the total balance for all invoices, including open credits and deposits.

'''Adjustment:''' Displays the total adjustments entered into the Adj Amt fields.

'''Discount:''' Displays the total discounts entered into the DisC Amt fields.

'''Unapplied:''' Displays the amount unapplied to invoices.

'''Applied:''' Displays the amount applied to invoices.

'''Paid Amt:''' The amount paid on a specific invoice. Will auto-fill when the record is selected, and can be manually overriden.

'''Disc Amt:''' Enter the amount of customer discount on a specific invoice.

'''Ajd Amt:''' Enter the amount of adjustment on a specific invoice.

'''Prepayment Type:''' Check either Open Credit or Deposit if the customer has paid in advance.

'''Payment Type:''' Select from Cash, Check, Credit Card, Other, or NSF (insufficient funds).

'''Include Paid Invoices:''' Check to display all paid invoices in the Invoice List grid.

[[Category: Accounts Receivable]]

Apply Cash Receipts

2024-08-05T15:03:57Z

Amohammad:

== General Information ==

'''Default Menu Location:''' Transaction >> Accounts Receivable >> Apply Cash Receipts

'''Screen Name:''' CASHREC

'''Function:''' The Apply Cash Receipts screen is used to enter cash receipts and apply them against open AR invoices.

To apply cash to an invoice, click the '''New Cash Receipt''' button. Then enter the Custno (customer number) or Company (customer name). The system will automatically bring up all open invoices for that customer. Select the appropriate Cash Account and enter the Cash Amount from the customer. Then, check which invoices to apply the cash payment to, and the system will automatically allocate the amount of the payment across the invoice(s) selected. The allocated amount can be change by editing the Paid Amt column in the bottom grid.

[[File:Apply_Cash_Receipt_to_Customer_Invoices.PNG]]

To enter an open credit, enter the amount of the credit in Cash Amount and click Save. A modal window will display asking "Create Open Credit with Un-Applied Balance?" Click '''Yes'''. A second modal window will display with fields for the AR Account, Description, and Invoice Status. Fill these out and click '''OK''' to issue the unapplied amounts as an Open Credit.

[[File:Create_Open_Credit.PNG]]

[[File:Select_Account_for_Open_Credit.PNG]]

After the payment has been allocated across the selected invoices, click '''Save''' to complete the cash receipt.

===Fields===

'''Custno/Company:''' Enter/select the customer that the payment is from.

'''Invno:''' Enter/select a specific invoice to pay with the cash receipt.

'''Adjustment Account/Description:''' The number and description of the offsetting account that will be used for adjustments to the invoice (bad debt, bank fees, write-off, etc). Can be set to default to a specific account.

'''Cash Acct:''' Select the appropriate Cash account from the drop down box.

'''Currency:''' Will default based on the Cash Account selected.

'''Cash Amount:''' Enter the amount of the payment.

'''Discount Account:''' The number and description of the offsetting account that will be used for customer discounts. Can be set to default to a specific account.

'''Reference #:''' Enter a reference number for the cash receipt; this may be the check number.

'''Bank Dep #:''' Enter a reference number for the bank deposit (optional); this may be the check number, date or a sequential number of your choice.

'''Transaction Date:''' The date when the transaction will go into Adjutant. This is often referred to as a the accounting date, because this is when the transaction will show as posted to the general ledger.

'''Postmark Date:''' The PostMark Date is the 'paid' date. This is the date which is primarily used for calculating discounts.

'''Project ID:''' Use this field to tie the cash receipt to an existing project in Adjutant, if applicable.

'''Phase:''' Select the phase of the project.

'''Type:''' Select the cash receipt type.

'''Notes:''' Leave any applicable notes or comments for this cash receipt.

'''Balance:''' Displays the total balance for all invoices, including open credits and deposits.

'''Adjustment:''' Displays the total adjustments entered into the Adj Amt fields.

'''Discount:''' Displays the total discounts entered into the DisC Amt fields.

'''Unapplied:''' Displays the amount unapplied to invoices.

'''Applied:''' Displays the amount applied to invoices.

'''Paid Amt:''' The amount paid on a specific invoice. Will auto-fill when the record is selected, and can be manually overriden.

'''Disc Amt:''' Enter the amount of customer discount on a specific invoice.

'''Ajd Amt:''' Enter the amount of adjustment on a specific invoice.

'''Prepayment Type:''' Check either Open Credit or Deposit if the customer has paid in advance.

'''Payment Type:''' Select from Cash, Check, Credit Card, Other, or NSF (insufficient funds).

'''Include Paid Invoices:''' Check to display all paid invoices in the Invoice List grid.

[[Category: Accounts Receivable]]

Apply Cash Receipts

2024-08-05T15:03:29Z

Amohammad:

Profile Color One - PCOLORONE Rule

2024-08-05T14:42:53Z

Amohammad:

===General Information===

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

'''Function''' This rule allows users to define profile colors used in production labeling, reporting, and machine interfaces.

'''Special''' Refer to the Special Reflexes section below for additional information on how the numbered profile rules work.

[[File:Profile_Color_One_Rule.png]]

===Rule Setup – Text Fields===

'''Color:''' Enter the profile color name (use ALL CAPS)

'''Description:''' Enter an alternate description for the color

'''Color Code:''' Enter an abbreviation of the color

===Rule Setup – Number Fields===

'''Color ID:''' Assign a numerical ID for the profile color

===Rule Setup – Logic Fields===

'''There are no Logic fields in use.'''

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

===Profile Naming Best Practices===

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, we recommend using ALL CAPS for the profile rule details.

[[Category:Item Control]] [[Category:Production]] [[Category:Rule Maintenance]]

Profile Color One - PCOLORONE Rule

2024-08-05T14:40:53Z

Amohammad:

===General Information===

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

'''Function''' This rule allows users to define profile colors used in production labeling, reporting, and machine interfaces.

'''Special''' Refer to the Special Reflexes section below for additional information on how the numbered profile rules work.

[[File:Profile_Color_One_Rule.png]]

===Rule Setup – Text Fields===

'''Color:''' Enter the profile color name (use ALL CAPS)

'''Description:''' Enter an alternate description for the color

'''Color Code:'''

===Rule Setup – Number Fields===

'''Color ID:''' Assign a numerical ID for the profile color

===Rule Setup – Logic Fields===

'''There are no Logic fields in use.'''

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

===Profile Naming Best Practices===

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, we recommend using ALL CAPS for the profile rule details.

[[Category:Item Control]] [[Category:Production]] [[Category:Rule Maintenance]]

Profile Color One - PCOLORONE Rule

2024-08-05T14:40:10Z

Amohammad:

===General Information===

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

'''Function''' This rule allows users to define profile colors used in production labeling, reporting, and machine interfaces.

'''Special''' Refer to the Special Reflexes section below for additional information on how the numbered profile rules work.

[[File:Profile_Color_One_Rule.png]]

===Rule Setup – Text Fields===

'''Color:''' Enter the profile color name (use ALL CAPS)

'''Description:''' Enter an alternate description for the color

'''Color Code:'''

===Rule Setup – Number Fields===

'''Color ID:''' Assign a numerical ID for the profile color

===Rule Setup – Logic Fields===

'''There are no Logic fields in use.'''

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

===Profile Naming Best Practices===

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, we recommend using ALL CAPS for the profile rule details.

[[Category:Item Control]] [[Category:Production]] [[Category:Rule Maintenance]]

Profile Color One - PCOLORONE Rule

2024-08-05T14:35:07Z

Amohammad:

===General Information===

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

'''Function''' This rule allows users to define profile colors used in production labeling, reporting, and machine interfaces.

'''Special''' Refer to the Special Reflexes section below for additional information on how the numbered profile rules work.

[[File:Profile_Color_One_Rule.png]]

===Rule Setup – Text Fields===

'''Color:''' Enter the profile color name (use ALL CAPS)

'''Description:''' Enter an alternate description for the color

'''Color Code:'''

===Rule Setup – Number Fields===

'''Color ID:''' Assign a numerical ID for the profile color

===Rule Setup – Logic Fields===

'''There are no Logic fields in use.'''

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

===Profile Naming Best Practices===

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, we recommend using ALL CAPS for the profile rule details.

File:Profile Color One Rule.png

2024-08-05T14:34:54Z

Amohammad:

Profile Color One - PCOLORONE Rule

2024-08-05T14:29:51Z

Amohammad: Created page with " ===General Information=== '''Default Menu Location''' Maintain >> System >> Rule Maintenance '''Function''' This rule allows users to define profile colors used in produ..."

===General Information===

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

'''Function''' This rule allows users to define profile colors used in production labeling, reporting, and machine interfaces.

'''Special''' Refer to the Special Reflexes section below for additional information on how the numbered profile rules work.

[imageauto|Profile Color One Rule|{UP}/Rule Maintenance/RULE-PCOLORONE.png]

===Rule Setup – Text Fields===

'''Color:''' Enter the profile color name (use ALL CAPS)

'''Description:''' Enter an alternate description for the color

'''Color Code:'''

===Rule Setup – Number Fields===

'''Color ID:''' Assign a numerical ID for the profile color

===Rule Setup – Logic Fields===

'''There are no Logic fields in use.'''

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

===Profile Naming Best Practices===

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, we recommend using ALL CAPS for the profile rule details.

Item Master - Attributes

2024-06-26T21:15:28Z

Amohammad:

__NOTOC__
===General Description===

'''Default Menu Location''' Maintain >> Item Control >> Item Master

Item Attributes are maintained in the '''Rule Maintenance ''' screen under Item Attributes.

[[File:Item_Master_Attribute.png]]

====Fields/Filters====

'''Asset:''' Select this attribute if you want an asset to be created in the Asset Information screen every time you receive the item.

An item with this attribute must be a stock item and serialized.

'''BOM (Bill of Material):''' Select this attribute if the item contains a bill of material. The Bill of Material Master window will open.

'''BUYINQB (Force to Buy in QB):''' This attribute will force the item to the Purchase module of Quick Buy, even if marked as produced.

'''BUYCONFIG:''' This attribute can be put on an item that's on the BOM of a configurable part. This will order the BOM item (the one with the BUYCONFIG attribute) when the user selects the 'PO' button from a sales order containing the configurable part. The raw materials from the BOM will be combined on the PO (one line per item). This is meant to work with items that are stocked in the same way they are configured (driven by the controlling quantity on the configuration screen). So if the item on the BOM is controlled by the Length question, the raw material is meant to have a stocking unit of FT.

'''COA (Certificate of Analysis):''' This attribute is intended for hazardous materials. When this attribute is added to a lot-controlled item, it adds a jump screen to each lot (accessible by clicking on a lot in the #Lot tab of Item Master) that holds specific information about that lot.

'''Coil Lot''' Activates a jump screen to Coil Defaults when attribute is saved. ''Coil Defaults'' screen is used to catagorize in detail the specifics of each coil type

'''CW (Catch-Unit Item):''' Select this attribute if the item has a catch unit associated with it, must be a stock item.

'''Do Not Update BCost on Receipt:''' Select this attribute if you want the base cost of the item to remain fixed, no matter what price the item is received at.

'''Freight Type Item:''' Select this attribute if you want the item to be flagged as a freight item on any sales order or invoice.

'''LOCKSOCPRICE (Lock Config Price):''' This attribute locks in the configuration price for the item and does not allow any edits to the configurable pricing.

'''Modify, Base:''' Select this attribute if the item is a base for modifications, must be a stock item. This attribute is required to modify the item in the Modification Processor.

'''Modify, Add-in:''' Select this attribute if the item is an add-in for modifications on the base items. This attribute is required to modify the item in the Modification Processor.

'''NOPWOASSLABEL (No Label on Assembly):''' Select this attribute to suppress production labels from being printed when item is produced.

'''No Labels (PONOLABEL):''' Select this attribute if you do not want any barcode labels to be printed when the item is received.

'''Packing Type Item:''' Select this attribute if you want the item to be flagged as a packing item on any sales order or invoice.

'''POGROUP###:''' This attribute - where '###' is a number - can place items on separate purchase orders when they are ordered at the same time. For example items with 'PO Group 001' will be placed on the first generated PO and items with 'PO Group 002' will be on a second purchase order. The name (text 1) on the Item Attributes rule follows the format of 'POGROUP###' where ### denotes the number. For example, POGROUP001.

'''PRICEMATRIX:''' Allows users to use thePrice Matrix Screen to price the item.

'''PRODLABELQTY:''' Prints one production label per qty to make on the production work order. For example, if the PWO is for 20 of an item, then this attribute will print 20 labels.

'''PWO2PO:''' Used for buyouts of produced items. This attribute will force an item on the BOM of a sales order line to a PO from the sales order. For example, let's say there is an item called PRODBEAM that goes to the shop for production. On the BOM of that PRODBEAM item is a buyout called BUYOUTBEAM. If you add PRODBEAM to a sales order then select the PO button from the sales order screen, the BUYOUTBEAM will display in the Create Purchase Order screen.

'''PWONOWARN:''' Suppress the message for specific items during the S2P process that warns the user that some items cannot be produced with current stock levels.

'''REQLINKPO:''' Will not allow an item to be shipped on a sales order unless it has been linked to a purchase order and that purchase order has been properly received.

'''SHOWMOD:''' Will display Modification Processor when this item is added to a Purchase Order. For more information refer to the [Processing-PO|Processing PO] page.

'''SO Use Required''' During SO line entry the Use field must be filled out before you can save the line.

'''SOC (Sales Order Configurator Setup):''' Select this attribute if the item is configurable. The Product Configurator will allow the user to set up the possible configurations of the item, should not be a stock item.

'''SONOISLOTNO:''' This can be added to lot controlled items so that the lot number that is assigned during the PO receipt is the same as the linked sales order.

'''SWI:''' This attribute contains the jump screen (AMSPROD) and will flag the system to push data to SWI machines (to be used with the SWI setup option and rule. Contact your consultant for more information on integration setup with SWI).

'''UPBCOST:''' Select this attribute if you want the item's base cost to be updated when a PO is received with a price higher than the current base cost.

'''UPBCOSTBOTH:''' This attribute will update the item's base cost when a PO is received. The difference between this and the UPBCOST attribute is the UPBCOST attribute will only adjust it if the PO receipt cost is higher than the current base cost. The UPBCOSTBOTH attribute will also adjust the item's base cost if the last received cost is lower than the current base cost.

'''Use System Flag for BCost Update:''' Check this attribute if you want the default system setting to decide the base cost update.

Item Master - Attributes

2024-06-26T21:06:51Z

Amohammad:

__NOTOC__
===General Description===

'''Default Menu Location''' Maintain >> Item Control >> Item Master

Item Attributes are maintained in the '''Rule Maintenance ''' screen under Item Attributes.

[[File:Item_Master_Attribute.png]]

====Fields/Filters====

'''Asset:''' Select this attribute if you want an asset to be created in the Asset Information screen every time you receive the item.

An item with this attribute must be a stock item and serialized.

'''BOM (Bill of Material):''' Select this attribute if the item contains a bill of material. The Bill of Material Master window will open.

'''BUYINQB (Force to Buy in QB):''' This attribute will force the item to the Purchase module of Quick Buy, even if marked as produced.

'''BUYCONFIG:''' This attribute can be put on an item that's on the BOM of a configurable part. This will order the BOM item (the one with the BUYCONFIG attribute) when the user selects the 'PO' button from a sales order containing the configurable part. The raw materials from the BOM will be combined on the PO (one line per item). This is meant to work with items that are stocked in the same way they are configured (driven by the controlling quantity on the configuration screen). So if the item on the BOM is controlled by the Length question, the raw material is meant to have a stocking unit of FT.

'''COA (Certificate of Analysis):''' This attribute is intended for hazardous materials. When this attribute is added to a lot-controlled item, it adds a jump screen to each lot (accessible by clicking on a lot in the #Lot tab of Item Master) that holds specific information about that lot.

'''Coil Lot''' Activates a jump screen to Coil Defaults when attribute is saved. ''Coil Defaults'' screen is used to catagorize in detail the specifics of each coil type

'''CW (Catch-Unit Item):''' Select this attribute if the item has a catch unit associated with it, must be a stock item.

'''Do Not Update BCost on Receipt:''' Select this attribute if you want the base cost of the item to remain fixed, no matter what price the item is received at.

'''Freight Type Item:''' Select this attribute if you want the item to be flagged as a freight item on any sales order or invoice.

'''LOCKSOCPRICE (Lock Config Price):''' This attribute locks in the configuration price for the item and does not allow any edits to the configurable pricing.

'''Modify, Base:''' Select this attribute if the item is a base for modifications, must be a stock item. This attribute is required to modify the item in the Modification Processor.

'''Modify, Add-in:''' Select this attribute if the item is an add-in for modifications on the base items. This attribute is required to modify the item in the Modification Processor.

'''NOPWOASSLABEL (No Label on Assembly):''' Select this attribute to suppress production labels from being printed when item is produced.

'''No Labels (PONOLABEL):''' Select this attribute if you do not want any barcode labels to be printed when the item is received.

'''Packing Type Item:''' Select this attribute if you want the item to be flagged as a packing item on any sales order or invoice.

'''POGROUP###:''' This attribute - where '###' is a number - can place items on separate purchase orders when they are ordered at the same time. For example items with 'PO Group 001' will be placed on the first generated PO and items with 'PO Group 002' will be on a second purchase order. The name (text 1) on the Item Attributes rule follows the format of 'POGROUP###' where ### denotes the number. For example, POGROUP001.

'''PRICEMATRIX:''' Allows users to use thePrice Matrix Screen to price the item.

'''PRODLABELQTY:''' Prints one production label per qty to make on the production work order. For example, if the PWO is for 20 of an item, then this attribute will print 20 labels.

'''PWO2PO:''' Used for buyouts of produced items. This attribute will force an item on the BOM of a sales order line to a PO from the sales order. For example, let's say there is an item called PRODBEAM that goes to the shop for production. On the BOM of that PRODBEAM item is a buyout called BUYOUTBEAM. If you add PRODBEAM to a sales order then select the PO button from the sales order screen, the BUYOUTBEAM will display in the Create Purchase Order screen.

'''PWONOWARN:''' Suppress the message for specific items during the S2P process that warns the user that some items cannot be produced with current stock levels.

'''REQLINKPO:''' Will not allow an item to be shipped on a sales order unless it has been linked to a purchase order and that purchase order has been properly received.

'''SHOWMOD:''' Will display Modification Processor when this item is added to a Purchase Order. For more information refer to the [Processing-PO|Processing PO] page.

'''SO Use Required''' During SO line entry the Use field must be filled out before you can save the line.

'''SOC ([^Product Configurator|Sales Order Configurator Setup]):''' Select this attribute if the item is configurable. The Product Configurator will allow the user to set up the possible configurations of the item, should not be a stock item.

'''SONOISLOTNO:''' This can be added to lot controlled items so that the lot number that is assigned during the PO receipt is the same as the linked sales order.

'''SWI:''' This attribute contains the jump screen (AMSPROD) and will flag the system to push data to SWI machines (to be used with the SWI setup option and rule. Contact your consultant for more information on integration setup with SWI).

'''UPBCOST:''' Select this attribute if you want the item's base cost to be updated when a PO is received with a price higher than the current base cost.

'''UPBCOSTBOTH:''' This attribute will update the item's base cost when a PO is received. The difference between this and the UPBCOST attribute is the UPBCOST attribute will only adjust it if the PO receipt cost is higher than the current base cost. The UPBCOSTBOTH attribute will also adjust the item's base cost if the last received cost is lower than the current base cost.

'''Use System Flag for BCost Update:''' Check this attribute if you want the default system setting to decide the base cost update.

Item Master - Attributes

2024-06-26T21:06:10Z

Amohammad:

__NOTOC__
===General Description===

'''Default Menu Location''' Maintain >> Item Control >> Item Master

Item Attributes are maintained in the '''Rule Maintenance ''' screen under Item Attributes.

[[File:Item_Master_Attribute.png]]

====Fields/Filters====

'''Asset:''' Select this attribute if you want an asset to be created in the Asset Information screen every time you receive the item.

An item with this attribute must be a stock item and serialized.

'''BOM ([^bom2|Bill of Material]):''' Select this attribute if the item contains a bill of material. The Bill of Material Master window will open.

'''BUYINQB (Force to Buy in QB):''' This attribute will force the item to the Purchase module of Quick Buy, even if marked as produced.

'''BUYCONFIG:''' This attribute can be put on an item that's on the BOM of a configurable part. This will order the BOM item (the one with the BUYCONFIG attribute) when the user selects the 'PO' button from a sales order containing the configurable part. The raw materials from the BOM will be combined on the PO (one line per item). This is meant to work with items that are stocked in the same way they are configured (driven by the controlling quantity on the configuration screen). So if the item on the BOM is controlled by the Length question, the raw material is meant to have a stocking unit of FT.

'''COA (Certificate of Analysis):''' This attribute is intended for hazardous materials. When this attribute is added to a lot-controlled item, it adds a jump screen to each lot (accessible by clicking on a lot in the #Lot tab of Item Master) that holds specific information about that lot.

'''Coil Lot''' Activates a jump sreen to [^coiljump|Coil Defaults] when attribute is saved. ''Coil Defaults'' screen is used to catagorize in detail the specifics of each coil type

'''CW (Catch-Unit Item):''' Select this attribute if the item has a catch unit associated with it, must be a stock item.

'''Do Not Update BCost on Receipt:''' Select this attribute if you want the base cost of the item to remain fixed, no matter what price the item is received at.

'''Freight Type Item:''' Select this attribute if you want the item to be flagged as a freight item on any sales order or invoice.

'''LOCKSOCPRICE (Lock Config Price):''' This attribute locks in the configuration price for the item and does not allow any edits to the configurable pricing.

'''Modify, Base:''' Select this attribute if the item is a base for modifications, must be a stock item. This attribute is required to modify the item in the Modification Processor.

'''Modify, Add-in:''' Select this attribute if the item is an add-in for modifications on the base items. This attribute is required to modify the item in the Modification Processor.

'''NOPWOASSLABEL (No Label on Assembly):''' Select this attribute to suppress production labels from being printed when item is produced.

'''No Labels (PONOLABEL):''' Select this attribute if you do not want any barcode labels to be printed when the item is received.

'''Packing Type Item:''' Select this attribute if you want the item to be flagged as a packing item on any sales order or invoice.

'''POGROUP###:''' This attribute - where '###' is a number - can place items on separate purchase orders when they are ordered at the same time. For example items with 'PO Group 001' will be placed on the first generated PO and items with 'PO Group 002' will be on a second purchase order. The name (text 1) on the Item Attributes rule follows the format of 'POGROUP###' where ### denotes the number. For example, POGROUP001.

'''PRICEMATRIX:''' Allows users to use thePrice Matrix Screen to price the item.

'''PRODLABELQTY:''' Prints one production label per qty to make on the production work order. For example, if the PWO is for 20 of an item, then this attribute will print 20 labels.

'''PWO2PO:''' Used for buyouts of produced items. This attribute will force an item on the BOM of a sales order line to a PO from the sales order. For example, let's say there is an item called PRODBEAM that goes to the shop for production. On the BOM of that PRODBEAM item is a buyout called BUYOUTBEAM. If you add PRODBEAM to a sales order then select the PO button from the sales order screen, the BUYOUTBEAM will display in the Create Purchase Order screen.

'''PWONOWARN:''' Suppress the message for specific items during the S2P process that warns the user that some items cannot be produced with current stock levels.

'''REQLINKPO:''' Will not allow an item to be shipped on a sales order unless it has been linked to a purchase order and that purchase order has been properly received.

'''SHOWMOD:''' Will display Modification Processor when this item is added to a Purchase Order. For more information refer to the [Processing-PO|Processing PO] page.

'''SO Use Required''' During SO line entry the Use field must be filled out before you can save the line.

'''SOC ([^Product Configurator|Sales Order Configurator Setup]):''' Select this attribute if the item is configurable. The Product Configurator will allow the user to set up the possible configurations of the item, should not be a stock item.

'''SONOISLOTNO:''' This can be added to lot controlled items so that the lot number that is assigned during the PO receipt is the same as the linked sales order.

'''SWI:''' This attribute contains the jump screen (AMSPROD) and will flag the system to push data to SWI machines (to be used with the SWI setup option and rule. Contact your consultant for more information on integration setup with SWI).

'''UPBCOST:''' Select this attribute if you want the item's base cost to be updated when a PO is received with a price higher than the current base cost.

'''UPBCOSTBOTH:''' This attribute will update the item's base cost when a PO is received. The difference between this and the UPBCOST attribute is the UPBCOST attribute will only adjust it if the PO receipt cost is higher than the current base cost. The UPBCOSTBOTH attribute will also adjust the item's base cost if the last received cost is lower than the current base cost.

'''Use System Flag for BCost Update:''' Check this attribute if you want the default system setting to decide the base cost update.

Item Master - Attributes

2024-06-26T21:05:18Z

Amohammad: Created page with "__NOTOC__ ===General Description=== '''Default Menu Location''' Maintain >> Item Control >> Item Master Item Attributes are maintained in the '''Rule Maintenance ''' screen..."

__NOTOC__
===General Description===

'''Default Menu Location''' Maintain >> Item Control >> Item Master

Item Attributes are maintained in the '''Rule Maintenance ''' screen under Item Attributes.

[[File:Item_Master_Attribute.png]]

====Fields/Filters====

'''Asset:''' Select this attribute if you want an asset to be created in the Asset Information screen every time you receive the item.

An item with this attribute must be a stock item and serialized.

'''BOM ([^bom2|Bill of Material]):''' Select this attribute if the item contains a bill of material. The Bill of Material Master window will open.

'''BUYINQB (Force to Buy in QB):''' This attribute will force the item to the Purchase module of Quick Buy, even if marked as produced.

'''BUYCONFIG:''' This attribute can be put on an item that's on the BOM of a configurable part. This will order the BOM item (the one with the BUYCONFIG attribute) when the user selects the 'PO' button from a sales order containing the configurable part. The raw materials from the BOM will be combined on the PO (one line per item). This is meant to work with items that are stocked in the same way they are configured (driven by the controlling quantity on the configuration screen). So if the item on the BOM is controlled by the Length question, the raw material is meant to have a stocking unit of FT.

'''COA (Certificate of Analysis):''' This attribute is intended for hazardous materials. When this attribute is added to a lot-controlled item, it adds a jump screen to each lot (accessible by clicking on a lot in the #Lot tab of Item Master) that holds specific information about that lot.

'''Coil Lot''' Activates a jump sreen to [^coiljump|Coil Defaults] when attribute is saved. ''Coil Defaults'' screen is used to catagorize in detail the specifics of each coil type

'''CW (Catch-Unit Item):''' Select this attribute if the item has a catch unit associated with it, must be a stock item.

'''Do Not Update BCost on Receipt:''' Select this attribute if you want the base cost of the item to remain fixed, no matter what price the item is received at.

'''Freight Type Item:''' Select this attribute if you want the item to be flagged as a freight item on any sales order or invoice.

'''LOCKSOCPRICE (Lock Config Price):''' This attribute locks in the configuration price for the item and does not allow any edits to the configurable pricing.

'''Modify, Base:''' Select this attribute if the item is a base for modifications, must be a stock item. This attribute is required to modify the item in the Modification Processor.

'''Modify, Add-in:''' Select this attribute if the item is an add-in for modifications on the base items. This attribute is required to modify the item in the Modification Processor.

'''NOPWOASSLABEL (No Label on Assembly):''' Select this attribute to suppress production labels from being printed when item is produced.

'''No Labels (PONOLABEL):''' Select this attribute if you do not want any barcode labels to be printed when the item is received.

'''Packing Type Item:''' Select this attribute if you want the item to be flagged as a packing item on any sales order or invoice.

'''POGROUP###:''' This attribute - where '###' is a number - can place items on separate purchase orders when they are ordered at the same time. For example items with 'PO Group 001' will be placed on the first generated PO and items with 'PO Group 002' will be on a second purchase order. The name (text 1) on the Item Attributes rule follows the format of 'POGROUP###' where ### denotes the number. For example, POGROUP001.

'''PRICEMATRIX:''' Allows users to use the [http://www.abiscorp.com/AdjWiki/Price%20Matrix.ashx|Price Matrix Screen]Price Matrix Screen to price the item.

'''PRODLABELQTY:''' Prints one production label per qty to make on the production work order. For example, if the PWO is for 20 of an item, then this attribute will print 20 labels.

'''PWO2PO:''' Used for buyouts of produced items. This attribute will force an item on the BOM of a sales order line to a PO from the sales order. For example, let's say there is an item called PRODBEAM that goes to the shop for production. On the BOM of that PRODBEAM item is a buyout called BUYOUTBEAM. If you add PRODBEAM to a sales order then select the PO button from the sales order screen, the BUYOUTBEAM will display in the Create Purchase Order screen.

'''PWONOWARN:''' Suppress the message for specific items during the S2P process that warns the user that some items cannot be produced with current stock levels.

'''REQLINKPO:''' Will not allow an item to be shipped on a sales order unless it has been linked to a purchase order and that purchase order has been properly received.

'''SHOWMOD:''' Will display Modification Processor when this item is added to a Purchase Order. For more information refer to the [Processing-PO|Processing PO] page.

'''SO Use Required''' During SO line entry the Use field must be filled out before you can save the line.

'''SOC ([^Product Configurator|Sales Order Configurator Setup]):''' Select this attribute if the item is configurable. The Product Configurator will allow the user to set up the possible configurations of the item, should not be a stock item.

'''SONOISLOTNO:''' This can be added to lot controlled items so that the lot number that is assigned during the PO receipt is the same as the linked sales order.

'''SWI:''' This attribute contains the jump screen (AMSPROD) and will flag the system to push data to SWI machines (to be used with the SWI setup option and rule. Contact your consultant for more information on integration setup with SWI).

'''UPBCOST:''' Select this attribute if you want the item's base cost to be updated when a PO is received with a price higher than the current base cost.

'''UPBCOSTBOTH:''' This attribute will update the item's base cost when a PO is received. The difference between this and the UPBCOST attribute is the UPBCOST attribute will only adjust it if the PO receipt cost is higher than the current base cost. The UPBCOSTBOTH attribute will also adjust the item's base cost if the last received cost is lower than the current base cost.

'''Use System Flag for BCost Update:''' Check this attribute if you want the default system setting to decide the base cost update.

File:Item Master Attribute.png

2024-06-26T21:03:23Z

Amohammad:

Sales Order Default Dates - SODATES Rule

2024-05-28T20:48:39Z

Amohammad: Created page with "__NOTOC__ ===General Information=== '''Default Menu Location''' Maintain >> System >> Rule Maintenance '''Function''' The Sales Order Default Dates rule allow setting def..."

__NOTOC__

===General Information===

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

'''Function''' The Sales Order Default Dates rule allow setting default date offsets for various date types on the Sales Order screen.

[[File:Default_Dates.png]]

===Rule Setup – Text Fields===

'''Date Type:''' This should be either "PWO DUE", "PWO Sch(A)", "PWO Sch(L)", "SO REQ", or "SO LOAD" to identify if the offset settings apply to the PWO Due Date, PWO Scheduled Date, SO Req Date, or SO Load Date.

''Note: The PWO Due date is offset from the SO Req Date. The PWO Sch(A) date is offset from the SO Add Date. The PWO Sch(L) date is offset from the SO Load Date. The SO Req and SO Load dates are offset from the SO Date. Also note that there are two options for PWO Sch Date and only one of those 2 options should be used for defaulting the PWO Schedule Date.''

===Rule Setup – Number Fields===

'''Offset Days:''' This should be the number of days to offset the specified date type. Negatives can be entered here.

===Rule Setup – Logic Fields===

'''Active:''' Check this box to activate the offset date settings for the selected line.

[[Category:Rule Maintenance]]

File:Default Dates.png

2024-05-28T20:47:55Z

Amohammad:

Quote Import Mapping - RFQMAP1 Rule

2024-05-14T21:20:01Z

Amohammad:

__NOTOC__

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

'''Function:''' This rule maps column headers of the CSV format spreadsheet for importing quote lines to specific configuration questions. The 'Import Column' entry in the rule must EXACTLY match the column heading in the spreadsheet in order to import.

[[File: Quote_Import_Mapping_Screen.png]]

==Rule Setup – Text Fields==
'''Import Column (text1, char, 50):''' Enter the column heading as it displays on the spreadsheet you're using for the import.

'''SOC Report Code (text2, char, 10):''' Enter the report code of the matched item's configuration question that the column's value should update. The following report codes are hardcoded since they relate to fields on the Customer Quote screen (instead of configuration questions):

''PRICE'' - This maps to the Sell Price field on the Line Items tab;

''SHIPWHSE'' - Transfers to the Ship Warehouse field on the Line Items tab;

''PLANT'' - Transfers to the Plant field on the Line Items tab;

''PRODNOTES'' - Transfers to the Production section of the line item notes;

''DESCRIP'' - Overrides the item description on the Line Items tab.

[[Category: Quoting]] [[Category: Rule Maintenance]]

HOW TO - Send Out Text Message Updates with Twilio Integration

2024-05-14T20:04:00Z

Amohammad:

__NOTOC__

==How to send out text message updates with Twilio integration==

===Overview===

Adjutant has the ability to utilize a Twilio account to send SMS message notifications instead of email-based SMS messaging:
Notifications include:
*The order has been sent to production.
*The production work order was marked completed.
*The linked shipping event has been marked shipped.
*The shipping event has been marked as delivered.

===Setup===

'''1) Create the new TWILIO Rule Maintenance record.'''
The SID, AuthCode, and phone number should all be accessible by the Twilio account holder. Please not that the UseCode must exactly match the Contact Attribute (ATT_CON) Rule Maintenance record.

[[File:Twilio_Setup.png]]

'''2) Create the contact attribute in the Contact Attributes (ATT_CON) Rule Maintenance record making sure that the Attribute Code exactly matches the UseCode in the Twilio rule.'''

[[File:Contact_Attribute_Rule.png]]

'''3) Add the attribute to a contact record and utilize the Email Address 2 field to store the phone number used for SMS communications.'''

===Additional Notes===

The Email Address 2 field can be updated to say 'Twilio #' as this field is customizable.

[[File:Custom_Contact.png]]

[[Category:Order Entry]] [[Category:Production]] [[Category:Rule Maintenance]]

File:Contact Attribute Rule.png

2024-05-14T20:03:49Z

Amohammad:

File:Twilio Setup.png

2024-05-14T20:03:05Z

Amohammad:

HOW TO - Send Out Text Message Updates with Twilio Integration

2024-05-14T19:44:07Z

Amohammad:

__NOTOC__

==How to send out text message updates with Twilio integration==

===Overview===

Adjutant has the ability to utilize a Twilio account to send SMS message notifications instead of email-based SMS messaging:
Notifications include:
*The order has been sent to production.
*The production work order was marked completed.
*The linked shipping event has been marked shipped.
*The shipping event has been marked as delivered.

===Setup===

'''1) Create the new TWILIO Rule Maintenance record.'''
The SID, AuthCode, and phone number should all be accessible by the Twilio account holder. Please not that the UseCode must exactly match the Contact Attribute (ATT_CON) Rule Maintenance record.

[[File:Twilio_Integration_Rule.png]]

'''2) Create the contact attribute in the Contact Attributes (ATT_CON) Rule Maintenance record making sure that the Attribute Code exactly matches the UseCode in the Twilio rule.'''

[[File:Contact_Attribute.png]]

'''3) Add the attribute to a contact record and utilize the Email Address 2 field to store the phone number used for SMS communications.'''

===Additional Notes===

The Email Address 2 field can be updated to say 'Twilio #' as this field is customizable.

[[File:Custom_Contact.png]]

[[Category:Order Entry]] [[Category:Production]] [[Category:Rule Maintenance]]

File:Twilio Integration Rule.png

2024-05-14T19:43:22Z

Amohammad:

HOW TO - Send Out Text Message Updates with Twilio Integration

2024-05-13T14:01:09Z

Amohammad:

__NOTOC__

==How to send out text message updates with Twilio integration==

===Overview===

Adjutant has the ability to utilize a Twilio account to send SMS message notifications instead of email-based SMS messaging:
Notifications include:
*The order has been sent to production.
*The production work order was marked completed.
*The linked shipping event has been marked shipped.
*The shipping event has been marked as delivered.

===Setup===

'''1) Create the new TWILIO Rule Maintenance record.'''
The SID, AuthCode, and phone number should all be accessible by the Twilio account holder. Please not that the UseCode must exactly match the Contact Attribute (ATT_CON) Rule Maintenance record.

[[File:Twilio_Integration.png]]

'''2) Create the contact attribute in the Contact Attributes (ATT_CON) Rule Maintenance record making sure that the Attribute Code exactly matches the UseCode in the Twilio rule.'''

[[File:Contact_Attribute.png]]

'''3) Add the attribute to a contact record and utilize the Email Address 2 field to store the phone number used for SMS communications.'''

===Additional Notes===

The Email Address 2 field can be updated to say 'Twilio #' as this field is customizable.

[[File:Custom_Contact.png]]

[[Category:Order Entry]] [[Category:Production]] [[Category:Rule Maintenance]]

Events

2024-05-10T20:25:30Z

Amohammad:

__NOTOC__

===General Information===

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

'''Function''' An event is an action that is created in the system when certain activities are performed. Events are created in a rule, and can be used to trigger routes that launch tasks.

[[File:Rule_Maintenance.png]]

Events use three pieces of information. The Event name which is the general event format, the Type, which is the module being used, and the code, which mainly use Create (CR) or edited (ED)

===Event Set Up===

'''ADDASSET (Type = ASSET Code = CR)''' Creates an event when a new asset is made.

'''ADDBILLTO (Type = BILLTO Code = CR)''' Creates an event when a new Bill To attribute is given to an organization.

'''ADDENT (Type = ENT Code = CR)''' Creates an event when a new organization is made.

'''ADDSHIPTO (Type = SHIPTO Code = CR)''' Creates an event when a new Ship To attribute is given to an organization.

'''ADDITEM (Type = ITEM Code = CR)''' Creates an event when a new item is made.

'''ADDSOLDTO (Type = SOLDTO Code = CR)''' Creates an event when a new Sold To attribute is given to an organization.

'''PROJ-Xyyy (Type = PROJ-Xyyy Code = CR)''' Where yyy represents the Project Event code from the [http://abiscorp.com/AdjWiki/Rule-PROJXEVENT.ashx?NoRedirect=1|PROJXEVENT]rule. This event is created based on setup from the Project Events rule where you can assign a task and a day count. The event is created when the project goes beyond the designated day count without the designated task being completed.

'''PHASE-SDATE-XX (Type = PHASE-SDATE-XX Code = ED)''' Where XX represents the Project Type code from the Project Type rule. This event is created when the phase start date is changed. When the change occurs, the original start date is stored for reference in the email template as -~msnphase.postartdate~.

'''PHASE-EDATE-XX (Type = PHASE-EDATE-XX Code = ED)''' Where XX represents the Project Type code from the Project Type rule. This event is created when the phase end date is changed. When the change occurs, the original end date is stored for reference in the email template as -~msnphase.poenddate~.

'''SOBO-XXX (Type = SOBO-XXX Code = CR)''' This event allows sending unique alerts for each warehouse location that marks items as Backordered. The XXX represents the warehouse's database ID (LOCTID). The new event is triggered any time Sales Order items are marked as Backordered from the Line Item View tab of the Sales Order screen, the Load Shipping Event screen, or through Scanner Prompts 74 & 79.

'''7479INV (Type = 7479INV Code = CR)''' This event allows users to create alerts for 'Possible Inventory Issue' messages received during loading procedures through Prompts 74 and 79. Details on the Sales Order, line number, material and quantity associated with the possible inventory are updated in rttask.note field, which should be added to the email template for the alert.

[[Category:Rule Maintenance]]

POS Surcharge - POSSURCHARGE Rule

2024-05-10T20:18:44Z

Amohammad:

__NOTOC__

==General Information==

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

'''Function''' Setting up this rule will include a transaction fee when processing defined payment types in the POS and Apply Cash Receipts screens.

[[File: POS_Surcharges_Rule_Screen.png]]

===Rule Setup – Text Fields===

'''Type:''' Enter one of the following payment types (CC, CASH, CHECK, OTHER, NSF).

'''GL Account:''' Enter the desired GL account to be used when posting the transaction fee.

===Rule Setup – Number Fields===

'''Percentage:''' Enter the desired percentage of the transaction fee.

[[Category: Accounts Receivable]] [[Category: Order Entry]] [[Category: Rule Maintenance]]

HOW TO - Send Out Text Message Updates with Twilio Integration

2024-05-10T20:15:07Z

Amohammad:

__NOTOC__

==How to send out text message updates with Twilio integration==

===Overview===

Adjutant has the ability to utilize a Twilio account to send SMS message notifications instead of email-based SMS messaging:
Notification include:
*The order has been sent to production.
*The production work order was marked completed.
*The linked shipping event has been marked shipped.
*The shipping event has been marked as delivered.

===Setup===

'''1) Create the new TWILIO Rule Maintenance record.'''
The SID, AuthCode, and phone number should all be accessible by the Twilio account holder. Please not that the UseCode must exactly match the Contact Attribute (ATT_CON) Rule Maintenance record.

[[File:Twilio_Integration.png]]

'''2) Create the contact attribute in the Contact Attributes (ATT_CON) Rule Maintenance record making sure that the Attribute Code exactly matches the UseCode in the Twilio rule.'''

[[File:Contact_Attribute.png]]

'''3) Add the attribute to a contact record and utilize the Email Address 2 field to store the phone number used for SMS communications.'''

===Additional Notes===

The Email Address 2 field can be updated to say 'Twilio #' as this field is customizable.

[[File:Custom_Contact.png]]

[[Category:Order Entry]] [[Category:Production]] [[Category:Rule Maintenance]]

File:Custom Contact.png

2024-05-10T20:15:01Z

Amohammad:

HOW TO - Send Out Text Message Updates with Twilio Integration

2024-05-10T20:11:48Z

Amohammad:

__NOTOC__

==How to send out text message updates with Twilio integration==

===Overview===

Adjutant has the ability to utilize a Twilio account to send SMS message notifications instead of email-based SMS messaging:
Notification include:
*The order has been sent to production.
*The production work order was marked completed.
*The linked shipping event has been marked shipped.
*The shipping event has been marked as delivered.

===Setup===

'''1) Create the new TWILIO Rule Maintenance record.'''
The SID, AuthCode, and phone number should all be accessible by the Twilio account holder. Please not that the UseCode must exactly match the Contact Attribute (ATT_CON) Rule Maintenance record.

[[File:Twilio_Integration.png]]

'''2) Create the contact attribute in the Contact Attributes (ATT_CON) Rule Maintenance record making sure that the Attribute Code exactly matches the UseCode in the Twilio rule.'''

[[File:Contact_Attribute.png]]

'''3) Add the attribute to a contact record and utilize the Email Address 2 field to store the phone number used for SMS communications.'''

===Additional Notes===

The Email Address 2 field can be updated to say 'Twilio #' as this field is customizable.

[[File:Contact_Attribute.png]]

[[Category:Order Entry]] [[Category:Production]] [[Category:Rule Maintenance]]

HOW TO - Send Out Text Message Updates with Twilio Integration

2024-05-10T20:11:35Z

Amohammad:

__NOTOC__

==How to send out text message updates with Twilio integration==

===Overview===

Adjutant has the ability to utilize a Twilio account to send SMS message notifications instead of email-based SMS messaging:
Notification include:
*The order has been sent to production.
*The production work order was marked completed.
*The linked shipping event has been marked shipped.
*The shipping event has been marked as delivered.

===Setup===

'''1) Create the new TWILIO Rule Maintenance record.'''
The SID, AuthCode, and phone number should all be accessible by the Twilio account holder. Please not that the UseCode must exactly match the Contact Attribute (ATT_CON) Rule Maintenance record.

[[File:Twilio_Integration.png]]

'''2) Create the contact attribute in the Contact Attributes (ATT_CON) Rule Maintenance record making sure that the Attribute Code exactly matches the UseCode in the Twilio rule.'''

[[File:Contact_Attribute.png]]

'''3) Add the attribute to a contact record and utilize the Email Address 2 field to store the phone number used for SMS communications.'''

===Additional Notes===

The Email Address 2 field can be updated to say 'Twilio #' as this field is customizable.

[[File:Contact_Attribute.png]]

[[Category:Order Entry]] [[Category:Production]] [[Category:Rule Maintenance]]

HOW TO - Send Out Text Message Updates with Twilio Integration

2024-05-10T20:09:04Z

Amohammad:

__NOTOC__

==How to send out text message updates with Twilio integration==

===Overview===
Adjutant has the ability to utilize a Twilio account to send SMS message notifications instead of email-based SMS messaging:
Notification include:
*The order has been sent to production.
*The production work order was marked completed.
*The linked shipping event has been marked shipped.
*The shipping event has been marked as delivered.

===Setup===

'''1) Create the new TWILIO Rule Maintenance record.'''
The SID, AuthCode, and phone number should all be accessible by the Twilio account holder. Please not that the UseCode must exactly match the Contact Attribute (ATT_CON) Rule Maintenance record.

[[File:Twilio_Integration.png]]

'''2) Create the contact attribute in the Contact Attributes (ATT_CON) Rule Maintenance record making sure that the Attribute Code exactly matches the UseCode in the Twilio rule.'''

[[File:Contact_Attribute.png]]

'''3) Add the attribute to a contact record and utilize the Email Address 2 field to store the phone number used for SMS communications.'''

===Additional Notes===
The Email Address 2 field can be updated to say 'Twilio #' as this field is customizable.

[[File:Contact_Attribute.png]]

[[Category:Order Entry]] [[Category:Production]] [[Category:Rule Maintenance]]

HOW TO - Send Out Text Message Updates with Twilio Integration

2024-05-10T20:05:26Z

Amohammad: Created page with "==How to send out text message updates with Twilio integration== ===Overview=== Adjutant has the ability to utilize a Twilio account to send SMS message notifications instea..."

==How to send out text message updates with Twilio integration==

===Overview===

Adjutant has the ability to utilize a Twilio account to send SMS message notifications instead of email-based SMS messaging:
Notification include:
*The order has been sent to production.
*The production work order was marked completed.
*The linked shipping event has been marked shipped.
*The shipping event has been marked as delivered.

===Setup===

'''1) Create the new TWILIO Rule Maintenance record.'''
The SID, AuthCode, and phone number should all be accessible by the Twilio account holder. Please not that the UseCode must exactly match the Contact Attribute (ATT_CON) Rule Maintenance record.

[[File:Twilio_Integration.png]]

'''2) Create the contact attribute in the Contact Attributes (ATT_CON) Rule Maintenance record making sure that the Attribute Code exactly matches the UseCode in the Twilio rule.'''

[[File:Contact_Attribute.png]]

'''3) Add the attribute to a contact record and utilize the Email Address 2 field to store the phone number used for SMS communications.'''

[[File:Contact_Attribute.png]]

[[Category:Order Entry]] [[Category:Production]] [[Category:Rule Maintenance]]

File:Contact Attribute.png

2024-05-10T19:52:41Z

Amohammad:

HOW TO - Send Out Text Message Updates for a Sales Order

2024-05-10T18:38:26Z

Amohammad: Created page with "__NOTOC__ ==How to send out text message updates for a sales order== ==Overview== Adding a contact attribute (SMSUPDATE) will allow customers (contacts) to receive text mes..."

__NOTOC__

==How to send out text message updates for a sales order==

==Overview==

Adding a contact attribute (SMSUPDATE) will allow customers (contacts) to receive text messages at the following stages of a Sales Order's life cycle:

*Items are sent to production (S2P button on the sales order)
*Items are produced (PWO is complete)
*Shipping Event has a status of "Shipped"
*Shipping Event is marked as "Delivered"

==Setup==

'''1) Fill out the text message address for contacts'''

The first step is to fill out the contact's 'Email 2' with their phone number in the format of an email address. Please note all carriers have different formats for sending text messages through email, so you'll need to determine the customer's cell phone provider as well. As of January 2017, here is the format for four major carriers:

'''AT&T:''' 10digitphonenumber@txt.att.net (XXXXXXXXXX@txt.att.net)

'''Verizon:''' 10digitphonenumber@vtext.com (XXXXXXXXXX@vtext.com)

'''Sprint:''' 10digitphonenumber@messaging.sprintpcs.com (XXXXXXXXXX@messaging.sprintpcs.com)

'''T-Mobile:''' 10digitphonenumber@tmomail.net (XXXXXXXXXX@tmomail.net)

'''2) Assign the contact attribute'''

Next, attach the contact attribute SMSUPDATE to any contact wanting to receive text updates. If this contact attribute doesn't exist on your system, please contact us for help.

'''3) Create templates for your text messages'''

Since these text messages are being sent via email, you need to create the following entries in the Email Templates screen in Adjutant:

[[File: SMS_Email_Template_Scren.png]]

'''Template Name'''
*SMS S2P - sent when the items are sent to production;
*SMS PWOCOMP - sent when the PWO is completed;
*SMS SESHIP - sent when the Shipping Event is shipped;
*SMS SEDEL - sent when the Shipping Event is delivered;

If you need help setting any of this up, please contact us at support@abiscorp.com.

'''4) Determine a process for opting in and option out of text messages'''

You'll need to figure out a way to get the word out to your customers on how to enroll in text message updates. Additionally, you'll need to communicate how they should contact you to opt out of receiving text message updates. If someone doesn't want to receive text messages anymore, remove the SMSUPDATE attribute and the email 2 entry from their contact record.

==Process==

When the setup is complete, any contact with the SMSUPDATE attribute will receive updates provided that:

*The contact is: 1) linked to the organization on the sales order; 2) associated with a valid text message address; and 3) updated to contain the SMSUPDATE attribute.
[[File: SMSUPDATE_Contact_Screen.png]]

*The 'SMS Update' checkbox is selected on the sales order. (This will be selected automatically if a contact with the SMSUPDATE attribute is selected.):

[[File: SMSUPDATE_Sales_Order_Screen.png]]

You can verify sent text messages by running the Email Log Report in Adjutant.

==FAQ==

'''Question: ''' Is there a way to limit text messages so they only go out to the Contact listed on the sales order?

'''Answer: ''' Yes. This can be done by activating the SMSONLYONE setup option.

[[Category: Order Entry]] [[Category: Production]]

ACH Data Setup - ACHDATA Rule

2024-05-09T20:01:25Z

Amohammad:

__NOTOC__

==General Information==

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

'''Function''' The AP ACH Data rule controls the ACH format details and the link to the AP Bank G/L Account. This rule also holds the base ACH file name and the default email address that is used if no AP Contact email address is associated with the Remit To record on the check.

[[File: AP_ACH_Data_Setup.png]]

==Rule Setup – Text Fields==

'''GL Account:''' Enter the GL account number that matches the Cash/Checking Gl account that has been set up to create EFT payments in ACH format.

'''File Name:''' Enter the base file name that will be used when creating the ACH file. A batch/sequence number will be appended to the end of this base file name to create a unique file each time.

'''Format:''' Enter the ACH format name provided by development. Valid entries are 'AMEGY', 'CIBD', and blank which will default to AMEGY format. Any additional formats will have to be submitted to Development as a new scope. The Amegy format is based on the NACHA standard so it may work for most banks.

'''Default Email:''' Enter the email address that should receive the payment processed email (PRINTEFT template) if there is no email associated with the AP Contact on the payment. This should be an internal address of the AP Clerk, or Office Manager.

==Rule Setup – Number Fields==

'''Batch Counter:''' This number sets the batch numbering increment.

==Rule Setup – Logic Fields==

There are no logic fields in use on this rule.

[[Category: Accounts Payable]] [[Category: Rule Maintenance]]

Air Hammer Default Days

2024-05-09T20:00:13Z

Amohammad: Created page with "__NOTOC__ ===General Information=== '''Default Menu Location''' Maintain >> System >> Rule Maintenance '''Function''' The Air Hammer Default Days rule controls the default..."

__NOTOC__

===General Information===

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

'''Function''' The Air Hammer Default Days rule controls the default look-back date range for each associated Air Hammer screen. By default, each Air Hammer screen will show the last 30 days of records if no overrides exist in this rule.

[[File:Air_Hammer.png]]

===Rule Setup – Text Fields===

'''Screen:''' Enter the system-defined name for each Air Hammer such as 'ORG', 'CONTACTS', 'ITEM', or 'ASSET'

'''Description:''' Description (friendly name) for the associated screen.

===Rule Setup – Number Fields===

'''Days:''' Specify the number of days to override the default of 30 days.

===Rule Setup – Logic Fields===

'''All Days:''' Checking this box defaults the 'All' checkbox for the associated Air Hammer which overrides the date range and shows all records.

[[Category:Rule Maintenance]]

File:Air Hammer.png

2024-05-09T20:00:07Z

Amohammad:

"Make Customer" Extra Attribute Rule

2024-05-09T19:56:29Z

Amohammad:

__NOTOC__

===General Information===

'''Default Menu Location''': Maintain >> System Manager >> Rule Maintenance >> Make Customer Extra Attributes (ENTMAKECUST)

'''Screen Name''': RULEM

'''Function:''' This rule allows the user to add additional attributes to be added to the organization when the MAKE CUSTOMER button is used. By default the Make Customer button will add the Bill To, Sold, To and Ship To attributes. This allows additional attributes to be added as well.

[[File:Extra_Attributes.png]]

===Fields===

Text1 = Organization Attribute name from the Organization Attributes (ATT_ENT) rule. Allows for 30 characters.

----

Num fields not in use

----

Log fields not in use

[[Category:Rule Maintenance]]

File:Extra Attributes.png

2024-05-09T19:56:22Z

Amohammad:

"Make Customer" Extra Attribute Rule

2024-05-09T19:55:19Z

Amohammad: Created page with "__NOTOC__ ===General Information=== '''Default Menu Location''': Maintain >> System Manager >> Rule Maintenance >> Make Customer Extra Attributes (ENTMAKECUST) '''Screen N..."

__NOTOC__

===General Information===

'''Default Menu Location''': Maintain >> System Manager >> Rule Maintenance >> Make Customer Extra Attributes (ENTMAKECUST)

'''Screen Name''': RULEM

'''Function:''' This rule allows the user to add additional attributes to be added to the organization when the MAKE CUSTOMER button is used. By default the Make Customer button will add the Bill To, Sold, To and Ship To attributes. This allows additional attributes to be added as well.

[imageauto||{UP}/Rule Maintenance/Rule ENTMAKECUST.png]

===Fields===

Text1 = Organization Attribute name from the Organization Attributes (ATT_ENT) rule. Allows for 30 characters.

----

Num fields not in use

----

Log fields not in use

[[Category:Rule Maintenance]]

1099 Types - TYPE1099 Rule

2024-05-09T19:53:41Z

Amohammad:

__NOTOC__

==General Information==

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

'''Function''' The 1099 Types rule controls the valid 1099 reporting types for use in the Accounts Payable system. The Vendor 1099 Type is set in the vendor's Remit To attribute record. The 1099 Types rule also controls the 1099 form associated with each type, and the 1099 box where the amount will display.

[[File:1099_Type.png]]

==Rule Setup – Text Fields==

'''Type:''' Enter the 1099 Type name that will display in all 1099 Type drop-downs. A maximum of 30 characters are allowed but not all 30 characters may display in all drop-downs.

'''Code:''' Assign a unique two-character code for each type.

'''Form:''' Specify the base form name associated with each 1099 type. The form names are system defined. Consult with your Implementation Consultant for the appropriate form name.

==Rule Setup – Number Fields==

'''1099 Form Box:''' Indicate the box number on the associated 1099 form to display the 1099 type's dollar amount.

'''Number per Page:''' Indicate how many 1099 forms should be produced on each page.

'''1096 Form Box:''' Indicate the box number on the associated 1096 Summary form to check for the associated 1099 type.

==Rule Setup – Logic Fields==

'''Default:''' Check the default box for one of the 1099 types to prompt it as the default 1099 Type when loading the Print 1099 screen.

[[Category: Accounts Payable]]
[[Category: Rule Maintenance]]

Item Master Q&A

2024-05-09T19:51:18Z

Amohammad: Created page with "===Settings Tab Questions=== '''Q:''' What is the "Cubes" box for? *'''A:''' Cubes is another way of measuring the volume of an item. By definition, a cube is a measurement u..."

===Settings Tab Questions===

'''Q:''' What is the "Cubes" box for?
*'''A:''' Cubes is another way of measuring the volume of an item. By definition, a cube is a measurement used in wholesale purchasing and shipping. The case cube denotes how much volume a case of any given item will take up in your warehouse. The case cube may be measured in cubic feet or cubic meters. In both cases, although the single case cube measurement tells you how much space the case takes up, it doesn't break that information down into 3 dimensions. Knowing the actual dimensions of a case is useful too, and is usually included on any spec or wholesale sheet that lists the case.

'''Q:''' What is the "EDI" box for?
*'''A:''' Electronic Data Interchange. It is a type of invoicing used by many corporations, although it is somewhat dated. By definition, it is the transfer of data from one computer system to another by standardized message formatting, without the need for human intervention. EDI permits multiple companies, possible in different countries, to exchange documents electronically.

'''Q:''' What is a "Pack Code"?
*'''A:''' Pack code is used to signify what can be packed together, it is not commonly used.

'''Q:''' What does Lot Controlled mean?
*'''A:''' Lot controlled means that the item is sold in groups or heats. So, if a company sells a bunch of cable wire to someone, they will sell it in huge strands. The strand itself has a lot number. The company would track the inventory of this lot number as it depleted from inventory. It is heavily used in the metal and steel industry.

'''Q:''' What does checking the "Consumable" box do?
*'''A:''' Consumable means the item is purchased for overhead or internal use and will not be sold. When you mark something as consumable, it will allow a user to purchase the item without it being linked to a sales order. By default, and depending on setup options, users are not able to create a PO for a non stock item unless it is marked a consumable or tied to a sales order.

'''Q:''' What does the "Costing" drop down field do and how do you edit it?
*'''A:''' Costing is the accounting costing method. Most will be SI-WeightedAvg. It is set once, and never changed.

'''Q:''' Are all of the costs (base, direct, indirect, freight in, freight out, avg cost, and std cost) provided for us by the company using Adjutant?
*'''A:''' Most customers use base, avg and std. The others are not used much anymore.

'''Q:''' Are all of the different groups (price group, commodity, prod grp, item cat, and class) used for reporting?
*'''A:'''Yes, they are all used for a variety of things:
Each item will belong in a commodity group. This grouping is used for reporting, purchasing, quoting, etc.
Some examples might be "Clips, Trim, Accessory, Coldform, Steel, Coil, Fastener, Flashing, Panel, etc".
'''Item cat'''- This is your item transaction category. Every order has a transaction category (this is made up of the CUSTOMER CATEGORY [found in the soldto] and the ITEM CATEGORY), this combination is tied to revenue and cost accounts that tell the system where the transaction should hit the GL.
'''Product Group'''- Most will be labor.
'''Item Class'''- Used in a lot of reporting and I believe cycle counts.
Each item will belong in a Price Group as well. Price Groups are used in Adjutant to determine pricing in the Contract Master, calculate and setup customer pricing, and determine margins (mainly used to set up customer/contract pricing).

===OHF Tab Questions===

'''Q:''' What is "CC" for?
*'''A:''' Cycle count code is used to segment out your cycles counts.

'''Q:''' What are bins?
*'''A:''' They are used for storage classification in the warehouse. Could be aisles, rows, zones, etc.

'''Q:''' What is a "PWO Bin"
*'''A:''' This is a production bin (if item is staged in the warehouse somewhere AFTER production and BEFORE shipping)

'''Q:''' What is "Lead Time"?
*'''A:''' How long it takes for an item to get here from the vendor.

'''Q:''' What is "ScrapAt"?
*'''A:''' It tells the system what level to scrap the item quantity at.

UDFs/Forms/Decision Trees

2024-05-08T21:01:12Z

Amohammad: Created page with "__NOTOC__ ===General Information=== '''Default Menu Location:''' Maintain>> Routing>> UDFs/Forms/Decision Trees '''Screen Name:''' TASKQALL '''Function:''' File:UDF.pn..."

__NOTOC__

===General Information===

'''Default Menu Location:''' Maintain>> Routing>> UDFs/Forms/Decision Trees

'''Screen Name:''' TASKQALL

'''Function:'''

[[File:UDF.png]]

====User Defined Fields====

'''User Field:''' The name of the question to ask the user

'''Type:''' This is the type of answer field. You may choose from Lists, text, numbers, dates, multi-lists (for lists that will contain more than one answer), etc.

'''Min Value:''' A defined minimum numeric value for the answer

'''Max Value:''' A defined maximum numeric parameter for the answer

'''Min Length:''' A defined minimum character length for the answer

'''Max Length:''' A defined maximum character length for the answer

'''DecQty:'''

'''Report Code:'''

'''Calculation:'''

'''Group Code:'''

'''Action Code:'''

'''QLong:'''

''Check Boxes''
* '''Skip Ans 2'''
* '''Common Question:''' This will update the answers for all other copies of this question that are linked to the same object.
* '''Proj Question:''' Will update answers for copies of this same question across multiple tasks if they are tied to the same project.
* '''Optional'''

====Forms Tab====
'''Form Name:''' This is the name given to the form

====Decision Trees Tab====

[[Category:Production]] [[Category:System Admin]]

File:UDF.png

2024-05-08T21:00:45Z

Amohammad:

PWO Reports Rule

2024-05-08T20:54:25Z

Amohammad: Created page with "__NOTOC__ ===General Information=== '''Default Menu Location''' Maintain >> System >> Rule Maintenance '''Function''' This rule controls the reports that show up in the..."

__NOTOC__

===General Information===

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

'''Function''' This rule controls the reports that show up in the Report drop down on the Production Work Order screen

[[File:PWO_Reports.png]]

===Rule Setup – Text Fields===

'''Description:''' The report description that will show in the dropdown.

'''Form:''' The screen name of the report you wish to add.

===Rule Setup – Number Fields===

'''No Number Fields In Use'''

===Rule Setup – Logic Fields===

'''No Logic Fields In Use'''

[[Category:Production]] [[Category:Rule Maintenance]]

File:PWO Reports.png

2024-05-08T20:54:08Z

Amohammad:

Production WIP Summary

2024-05-08T20:07:34Z

Amohammad: Created page with "__NOTOC__ ===General Information=== '''Default Menu Location''' Report >> Production >> Production Summary '''Screen Name:''' PWOWSUMMARY '''Function:''' The Production W..."

__NOTOC__

===General Information===

'''Default Menu Location''' Report >> Production >> Production Summary

'''Screen Name:''' PWOWSUMMARY

'''Function:''' The Production WIP Report shows the item input/output information.

[[File:Production_WIP_Reports.png]]

===Fields/Filters===

'''PWO#:''' The production workorder number.

'''Customer:''' Customer

'''Input Item:''' Input item

'''Start Date:''' The start date

'''End Date:''' The end date

'''Date To User:''' Either the Accounting Date or Timestamp Date can be selected.

'''Owner:''' The company can be selected.

'''Plant:''' Select a plant.

'''WIP Type:''' Select PWO WIP, Timesheet WIP, or Both.

[[Category:Production]]

File:Production WIP Reports.png

2024-05-08T20:02:44Z

Amohammad:

Production Summary

2024-05-08T19:55:42Z

Amohammad: Created page with "__NOTOC__ ===General Information=== '''Default Menu Location''' Report >> Production >> Production Summary '''Screen Name:''' PWOSUMMARY '''Function:''' The Production Su..."

__NOTOC__

===General Information===

'''Default Menu Location''' Report >> Production >> Production Summary

'''Screen Name:''' PWOSUMMARY

'''Function:''' The Production Summary report shows the item input/output information.

[[File:Production_Summary.png]]

===Fields/Filters===

'''PWO#:''' The production workorder number.

'''Start Date:''' The start date.

'''End Date:''' The end date.

'''Accounting Date or Timestamp Date:''' Either the accounting date or timestamp date can be selected.

'''Custno:''' Customer

'''Company:''' Company

'''Input Item:''' Input item

'''Output Item:''' Output item

'''Salesperson:''' Salesperson

[[Category:Production]]