AP Custom Priorities - APPP Rule - Revision history

Freddy at 19:06, 25 October 2023

2023-10-25T19:06:22Z

Freddy at 19:03, 25 October 2023

2023-10-25T19:03:06Z

Freddy at 18:32, 25 October 2023

2023-10-25T18:32:13Z

Freddy at 20:58, 9 January 2023

2023-01-09T20:58:04Z

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

2023-01-09T20:36:42Z

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

New page

__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: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:''' Not in use.

===Rule Setup – Number Fields===

'''Color ID:''' Assign a numerical ID for the profile color. This is used in several places in the database, make sure that the Color ID is unique per each record.

===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:Rule Maintenance]]
[[Category:Accounts Payable]]

@@ Line 6: / Line 6: @@
 '''Function'''  This rule allows users to define custom AP Payment Priorities for Check and Non-Check Payments that override the system default payment priorities of 1 through 8 that only apply to check payment types. For example, if only 4 check type payment priorities are needed, but a user wanted to define 4 unique non-check payment priorities, this rule can be used to override the system defaults and define the new structure of payment priorities.
-'''WARNING'''  Setting up this rule will disable the use of the legacy payment priority code of 'N' for Non-Check Payments. Implementing this new feature will require assistance from ABIS personnel to replace any existing uses of the 'N' payment priority code throughout Adjutant with a valid non-check payment code defined in the new APPP rule. This may include updates to any Vendor Remit To records with a code of 'N' as well as any open AP Invoices tied to a payment priority code of 'N'.
+'''WARNING'''  Setting up this rule will disable the use of the legacy payment priority code of 'N' for Non-Check Payments. When this rule is set up, Adjutant AP processes will reference this rule to determine the valid non-check type payment priorities and will no longer assume 'N' as the only valid non-check priority. Implementing this new feature will require assistance from ABIS personnel to replace any existing uses of the 'N' payment priority code throughout Adjutant with a valid non-check payment code defined in the new APPP rule. This may include updates to any Vendor Remit To records with a code of 'N' as well as any open AP Invoices tied to a payment priority code of 'N'.
 '''Do not add this rule unless you are actively coordinating with ABIS personnel to adjust existing Vendor and AP Invoice data to work with the new rule settings.'''

@@ Line 4: / Line 4: @@
 '''Default Menu Location''' Maintain >> System >> Rule Maintenance
-'''Function'''  This rule allows users to define custom AP Payment Priorities for Check and Non-Check Payments that override the system default payment priorities of 1 through 8 that only apply to check payment types.
+'''Function'''  This rule allows users to define custom AP Payment Priorities for Check and Non-Check Payments that override the system default payment priorities of 1 through 8 that only apply to check payment types. For example, if only 4 check type payment priorities are needed, but a user wanted to define 4 unique non-check payment priorities, this rule can be used to override the system defaults and define the new structure of payment priorities.
 '''WARNING'''  Setting up this rule will disable the use of the legacy payment priority code of 'N' for Non-Check Payments. Implementing this new feature will require assistance from ABIS personnel to replace any existing uses of the 'N' payment priority code throughout Adjutant with a valid non-check payment code defined in the new APPP rule. This may include updates to any Vendor Remit To records with a code of 'N' as well as any open AP Invoices tied to a payment priority code of 'N'.

@@ Line 21: / Line 21: @@
 '''Special notes regarding the Priority Code values'''
-* The priority codes of 'C' (Credit Card), 'E' (EFT), 'M' (Manual Check), and the legacy code of 'N' (Non-Check) are reserved by the system and should not be used.
+* The priority codes of 'C' (Credit Card), 'E' (EFT), 'M' (Manual Check), 'P' (Prepaid check) and the legacy code of 'N' (Non-Check) are reserved by the system and should not be used.
 * When defining custom codes, the codes MUST be sequential according to the check or non-check priority ranges. This is to allow ranges to work in the corresponding AP screens.
 ** For example, in the example above, codes 1 through 4 are used for check type priorities and codes 5-8 are used for non-check priorities. This will allow screens like Approve AP Invoices to recognize the range of priorities.
-** Letters can be used in the priority code field, but the reserved codes of C, E, M, and N cannot be used.
+** Letters can be used in the priority code field, but the reserved codes of C, E, M, N and P cannot be used.
-** The alpha ranges of F through L may be used, or the ranges of O through Z can be also be used.
+** The alpha ranges of F through L may be used, or the ranges of Q through Z can be also be used.