Purchase Order Setup Guide - Revision history

Mwillard at 23:07, 8 December 2022

2022-12-08T23:07:43Z

Show changes

Mwillard at 14:55, 8 December 2022

2022-12-08T14:55:42Z

Mwillard at 17:24, 5 December 2022

2022-12-05T17:24:57Z

Freddy at 16:22, 21 December 2021

2021-12-21T16:22:41Z

Freddy at 15:43, 16 April 2018

2018-04-16T15:43:31Z

Freddy at 15:43, 16 April 2018

2018-04-16T15:43:02Z

Freddy at 15:27, 16 April 2018

2018-04-16T15:27:54Z

Freddy at 15:01, 16 April 2018

2018-04-16T15:01:44Z

Freddy at 14:00, 16 April 2018

2018-04-16T14:00:37Z

Freddy at 18:51, 13 April 2018

2018-04-13T18:51:07Z

@@ Line 1: / Line 1: @@
+__NOTOC__
 == Overview ==
@@ Line 159: / Line 158: @@
 *If the customer will use the legacy screen for specific purposes, create a shortcut to the screen on the specific user's desktop.
 ==Scrub and Import Open Purchase Order Data==
@@ Line 176: / Line 189: @@
 * Verify that printing is working
 * Verify that both outbound/inbound emailing are working
 [[Category:Setup Guides]]
 [[Category:Purchasing]]

← Older revision		Revision as of 17:24, 5 December 2022
Line 181:		Line 181:

	[[Category:Setup Guides]]		[[Category:Setup Guides]]
−	[[Category:~~Purchase Orders~~]]	+	[[Category:Purchasing]]

@@ Line 165: / Line 165: @@
 If the client requires an open purchase order conversion, refer to Purchase Order Conversion Guide (UNDER CONSTRUCTION) for detailed information on the import and reconciliation process.
 <br>
 <br>

@@ Line 55: / Line 55: @@
 *The default PO form can be set in the PO Types rule, and individual vendors can be set to a default PO Type in the 'Sold From' attribute.
@@ Line 68: / Line 63: @@
 *If the client does not have any group pricing rules, vendor pricing can be set in the Item Master C/V Part screen.
 *If the client has vendor pricing that is defined by vendor groups, define the groups in the Vendor Cost Groups (ENTVGRP) rule, and set up the Vendor Pricing screen.

@@ Line 149: / Line 149: @@
-===Set up Credit Card Vendors===
+===Confirm version of PO Receipt Screen===
-Discuss how the customer wants to handle credit card charges and credit card invoice payments. Determine if they will be using the Merge CC Invoices process.
+Adjutant has a legacy version of the PO Receipt screen that is still in use, and has been used at new clients for specific functions.  Generally, new clients should be using the 'New' PO Receipt screen for all receiving functions.
-*If the customer will be using the CC process, set up all credit card vendors with the 'Credit Card Vendor' Org Attribute, and set the default Pay Priority to 'C' in the Remit To record.
+The NEWPOREC CID Setup Option should be enabled to make the 'PO Rec' button in the PO screen open the new version of the PO Receipt screen .
-Refer to Accounts Payable Conversion Guide (UNDER CONSTRUCTION) for detailed information on the import and reconciliation process.
+==Scrub and Import Open Purchase Order Data==
 <br>
 <br>

@@ Line 23: / Line 23: @@
 *The taxable flag in PO Line Item Entry must be checked, and the vendor (or the Tax% in PO Header) must have a tax rate in order to calculate taxes on a PO
@@ Line 45: / Line 55: @@
 *The default PO form can be set in the PO Types rule, and individual vendors can be set to a default PO Type in the 'Sold From' attribute.
@@ Line 60: / Line 62: @@
-===Review the Default PO Clearing Account===
+===Vendor Pricing===
@@ Line 86: / Line 79: @@
 The department entry marked as Default will populate the department in a new Purchase Order, unless the logged in user has a Resource attribute set with a department.
 ===FOB (Free on Board) Codes (FOB)===
@@ Line 92: / Line 88: @@
 The rule in MASTER has the most common entries, and should be valid for most clients. Add any additional FOB codes as needed.
 ===Freight PO Item (FREIGHTPOITEM)===
 The Fright PO Item is only used for clients that are generating purchase orders from shipping event records.  The item in this rule is used as the line item when generating a freight PO.
 ===Freight Terms (FREIGHT)===
 Freight terms are valid in Order Entry, Shipping, and Purchase Orders.  Add any needed freight types to this rule to populate the list of available freight types in the associated applications.
 ===PO Bid Types (POBTYPE)===
@@ Line 109: / Line 102: @@
 The MASTER rule has a default entry. If the client is planning to use Vendor Bids, confirm that all needed bid types are set up.
 ===PO Comment Codes (ORDNOTE)===
 The PO Comment Codes rule allows users to set up predefined notes that can be included on purchase orders. The functionality is similar to the comment codes that can be used on orders and invoices.  Add any needed quick PO comment codes in this rule.
 ===PO Date Defaults (PODATES)===
 The PODATES rule controls how the PO Req Date and the PO Est Date are set on a new PO.  The rule allows you to override the default logic when creating new POs.  Verify the entries in this rule are what the client wants.
 ===PO Form Number of Copies (POOPTION)===
 The POOPTION rule provides one of the more comical internal rule names.  If the client needs anything other than one copy of the PO form to print with every request, update the rule accordingly.
 ===PO Form Section 4 Overrides (POBLOCK4)===
 The POBLOCK4 rule was created to hold certain print overrides based on FOB and PORT entries for a specific customer.  Review ECR 23735 to determine if this rule would be useful for your client.
 ===PO Ports (PORT)===
 The PORTS rule holds the valid entries for the Port drop-down list on a purchase order.  If the rule is empty, Port will not be filled in and will not be required in order to add a PO.
 ===PO Types (POTYPE)===
 The POTYPE rule controls the valid types, default form to use, GL Group, and which type is the default entry.  If the client is not interested in controlling or reporting purchase orders by type, an entry is still required as the default type.
 ===Ship Via Codes (SHIPVIA)===
@@ Line 151: / Line 132: @@
 Review this rule carefully for any special options and reflexes.  Add any needed ship via methods to the rule.
 ===Terms of Payment Codes (TERMS)===

@@ Line 75: / Line 75: @@
-==Review and Update Rule Maintenance Records==
+The POOPTION rule provides one of the more comical internal rule names.  If the client needs anything other than one copy of the PO form to print with every request, update the rule accordingly.
-The TYPE1099 rule defines the valid 1099 reporting types that can be assigned to vendors in the Remit To attribute.  The 1099 Type can also be set at the AP Invoice level if setup option APMULTI1099 is enabled. The rule from the MASTER CID contains the most common 1099 types needed for most customers.  Notify the MASTER CID System Administrator of any valid new 1099 types that need to be added to the MASTER CID rule.
+===PO Form Section 4 Overrides (POBLOCK4)===
-The APCHKOVERFLOW rule controls when and how paid invoice details that exceed the number of available lines on the check stub are handled. If the Print Details option is checked, the overflow message will NOT print on the stub, but the allowed number of invoices will print. If the Print Details option is unchecked, and the check form is correctly set up to print the overflow message, ONLY the overflow message will print on the stub.
+===PO Ports (PORT)===
-* The 'll_printoverflow' expression is used as a Print When on the check form to control printing/hiding of invoice details and the overflow message.
+The PORTS rule holds the valid entries for the Port drop-down list on a purchase order.  If the rule is empty, Port will not be filled in and will not be required in order to add a PO.
-===AP Voucher Stamps (VOUCHSTAMP)===
+===PO Types (POTYPE)===
-The VOUCHSTAMP rule allows users to create custom image overlays that can be 'stamped' on to AP Voucher documents in the Voucher List screen. The stamps are saved with the document in the Doc Vault.
+The POTYPE rule controls the valid types, default form to use, GL Group, and which type is the default entry.  If the client is not interested in controlling or reporting purchase orders by type, an entry is still required as the default type.
 ===Doc Vault Drop Folders (DROPFOLDERS)===
-Review the drop folder entries for AP Invoice and AP Voucher.
+Review the drop folder entries for Vendor Bids (BPONO) and Purchase Orders (PONO).
@@ Line 111: / Line 159: @@
-==Review and Complete Additional Accounts Payable Setup==
+==Review and Complete Additional Purchase Order Setup==
-===Set up Templates and Recurring Payables===
+===Set up Templates and Recurring Orders===
-Discuss AP Invoice Templates and Recurring Payables with customer.
+Discuss Purchase Order Templates and Recurring Purchase Orders with customer.
-*Set up any templates and/or recurring payables as needed with the customer. Use the [http://www.abiscorp.com/AdjWiki/rec1.ashx Recurring Order WIki] as a reference for the recurrence codes.
+*Set up any templates and/or recurring orders as needed with the customer. Use the [http://www.abiscorp.com/AdjWiki/rec1.ashx Recurring Order WIki] as a reference for the recurrence codes.

← Older revision		Revision as of 14:00, 16 April 2018
Line 136:		Line 136:

	[[Category:Setup Guides]]		[[Category:Setup Guides]]
−	[[Category:Purchase ~~Order~~]]	+	[[Category:Purchase Orders]]

@@ Line 13: / Line 13: @@
 ===Review/Discuss Purchasing Sales Tax Policies===
-Work with the client to determine how taxes are handled for purchases.  Under most circumstances, items purchase for resell are not taxed. However, every industry and state is unique, and nothing should be assumed when it comes to taxes.
+Work with the client to determine how taxes are handled for purchases.  Under most circumstances, items purchase for resell are not taxed, and the majority of our clients do not regularly charge tax on POs. However, every industry and state is unique, and nothing should be assumed when it comes to taxes.
 Review and update the following items in regard to taxing on purchase orders:
 *POUSETAXFLAG Setup Option - Uses the taxable flag from each item record
-*POSPLITTAX Setup Option - Splits up tax amounts in the ITEMACT records
+*POSPLITTAX Setup Option - Splits up tax amounts in the ITEMACT records; posts tax amounts separately, and keeps received inventory value at the cost before tax