|
The pricing on the sales order line for internally supply purchase orders is determined by the INT_SUPPLY_PRICE_OVRD parameter in program MURM, Initialization Parameter Maintenance. The following settings can be used: N - the unit price on the sales order will be 0. C - the unit price on the sales order will match the unit price on the purchase orders. Any other setting indicates that standard pricing will be used on the sales order. When a sales order is backordered, the purchase order is updated with the new sales order number. As long as the backorder is O - Complete status, updates to the purchase order will update the backorder. The POEM_INTERCO_WARN parameter in program MURM, Initialization Parameter Maintenance, can be set up so that a warning is displayed when the sales order is not open. When the parameter is set to Y, a warning will be displayed in program POEM, PO Entry/Maintenance, when a user queries an internal purchase order, only one sales order is associated with the purchase order, the sales order is not open, and there are no open back orders for the sales order. Purchase orders for internal suppliers can be received in program REOM, One Step Receiver Entry/Maintenance. When the sales order is status S - Confirmed Complete, the sales order number can be entered in the Internal Sls Order field. Press the [Receive PO] button to receive the quantities that were shipped. The receiver will be closed automatically. If the REOM_INT_SO_REQD parameter in program MURM, Initialization Parameter Maintenance, is set to Y, receipt of internal supply purchase orders requires receipt of entire sales order shipment. Internal supply purchase orders received with program REOM, One Step Receiver Entry/Maintenance, are subject to the following restrictions: The purchase order cannot contain controlled items. The purchase order cannot have distribution detail. The resulting receiver detail lines and quantities will match the sales order shipment. The receiver cannot be maintained manually. Shipment of internal sales orders can be recorded in program OEICS, InterCompany Quick Ship. |
|
|
Modified to allow a mass update of the promise date for all displayed purchase order lines. |
|
|
New report displaying the internal purchase order lines that can be closed either because they were fully or overly received or because they were under received and no sales backorder exists for the remainder. |
|
|
The PO_COST_VARIANCE_ALLOWED parameter for the plant in program MURM, Initialization Parameter Maintenance, determines whether the price on the purchase order will be compared against the purchase order unit cost for maintain on hand items to see if it is within tolerance levels. The change in unit price is checked against the PO cost on the Pricing Tab. The default purchase unit of measure is determined as follows: If there are no vendor quotes for the item, the stock unit of measure is the default. If a purchase unit of measure has been entered before the item number is entered, the vendor quote record for that item and purchase unit of measure is used. For new records with vendor quotes, the vendor quote record for the stock unit of measure is used first. If there is no vendor quote record for the stock unit of measure, the first vendor quote record for that item is found and the purchase unit of measure from that record is used. Added the Send To tab which displays the vendor fax and email send to information for this purchase order. If the fax/email information for a report class differs for this purchase order and vendor, you can change it here. For more information, see the program documentation. When reports that are assigned to report class POP are transmitted, a comment is written to the purchase order regarding who, how and when the purchase order was transmitted. |
|
|
Modified the Use active-managed table for POSE flag. Checkbox set to on or off indicates whether the data in program POSE, Create Purchase Orders from Sales, is based on the standard view with real time data or a faster detail view that is maintained completely by database triggers on the sales order header, sales order lines, and model configuration information. Records only exist for ORD type sales orders with O - Open Order, J - Confirmed Incomplete, or S - Confirmed Complete statuses. When this flag is set to off, the data in program POSE, Create Purchase Orders from Sales, is based on the standard view with real time data. When this flag is set to on, the data in program POSE, Create Purchase Orders from Sales, is based on a detail view that is maintained completely by database triggers on the sales order header, sales order lines, and model configuration information. Records only exist for ORD type sales orders with O - Open Order, J - Confirmed Incomplete, or S - Confirmed Complete statuses. When the Include Drop Ships flag is on, users can modify the unit cost for drop shipped non maintain on hand items in program POSE, Create Purchase Orders from Sales, when the S type cost is not dynamic, i.e. is not average or actual cost. If you do not want the purchase cost to be able to be updated in a non-dynamic cost environment, set this flag to off. |
|
|
Added the [Show Purge Log] button, which displays information about previous purges. |
|
|
The PO_COST_VARIANCE_ALLOWED parameter for the plant in program MURM, Initialization Parameter Maintenance, determines whether the price on the purchase order will be compared against the purchase order unit cost to see if it is within tolerance levels. The change in unit price is checked against the last cost retrieved when the line was re-priced. |
|
|
Added Archive Purged Records flag, which when set to on will store the purged records in the requisition history tables. Added [Show Archive Log] button for users to view the archive log, which includes the information about when the records were last archived/purged. |
|
|
Modified to use the new detail table when the Use active-managed table for POSE flag is set to on in program POPM, PO / Receiving Parameter Maintenance. The PO_COST_VARIANCE_ALLOWED parameter for the plant in program MURM, Initialization Parameter Maintenance, determines whether the price on the purchase order will be compared against the purchase order unit cost to see if it is within tolerance levels. The change in unit price is checked against the original PO cost on the line. When the S type cost is non-dynamic, i.e. is not average or actual cost, users cannot modify the unit cost for drop shipped non maintain on hand items in program POSE, Create Purchase Orders from Sales, unless the Include Drop Ship Lines flag is set to on in program POPM, PO / Receiving Parameter Maintenance. |
|
|
Added New Default flag. Set this flag to on, if the entered location should be the default location for the item in program ICEM, Item Plant Maintenance. The default setting of this flag is determined by the RCVG_UPDATES_DEFBIN parameter in program MURM, Initialization Parameter Maintenance. When set to YES, the flag defaults to on. When set to NO, ZEROASK, and ASK, flag defaults to off. When set to ZERO, the flag defaults to off unless the item does not have a quantity on hand in the plant, in which case the flag defaults to on. |
|
|
Added Internal Sls Order field for use with the Internal Suppliers feature. Receiving Internal Supplier Purchase OrdersInternal supply purchase orders received with program REOM, One Step Receiver Entry/Maintenance, are subject to the following restrictions: The sales order must be status S - Confirmed Complete. The purchase order cannot contain controlled items. The purchase order cannot have distribution detail. The resulting receiver detail lines and quantities will match the sales order shipment. The receiver cannot be maintained manually. If the REOM_INT_SO_REQD parameter in program MURM, Initialization Parameter Maintenance, is set to Y, receipt of internal supply purchase orders requires receipt of entire sales order shipment. 1. In the Init field, enter your initials. 2. In the Internal Sls Order field, enter the internal supplier sales order number being received. 3. Enter the sales order suffix for the internal supplier sales order. 4. Press [Commit]. 5. Press the [Receive PO] button. 6. The shipped quantities are received and the receiver is closed. |
|
|
Added Archive Purged Records flag, which when set to on will store the purged records in the archiving tables. Added [Show Archive Log] button for users to view the archive log, which includes the information about when the records were last archived/purged. |
|
|
Modified to use third party shipping accounts entered for the vendor in program VESM, Third Party Vendor Maintenance, for freight charges. In the THP Acct field, if the vendor is going to pay the freight cost for the transaction, enter the third party account in this field. You can double click in this field to view a list of values of the third party accounts for the vendor and ship via code in program VESM, Third Party Vendor Maintenance. If the third party account entered does not exist in program VESM, Third Party Vendor Maintenance, the user will be prompted to add it to the program automatically. The third party address sent to the shipping interface will be the return to vendor address. If the vendor is going to pay the freight cost for the transaction, set the Vendor Pays Frt flag to on. When this flag is set to on, and the vendor for the transaction is assigned a third party account in program VESM, Third Party Vendor Maintenance, for the ship via code, the freight charges will be charged to the third party account. In addition, freight charges will not be included the credit voucher. For more information, see the Third Party Shipping Accounts for Shipping Interfaces section. Modified so that non-stock items cannot be entered on the RTV Maintenance tab and must be entered on the Open Quarantine Non Stock tab similar to the Open Quarantine Items tab. Added OOB Items tab to display out of balance items where the quantity in the quarantine location does not match the return quantity reported for the line. Added the [Clear Zero Qtys] button to allow users to clear quarantine lines where the return quantity and original quantity are zero. |
|
|
Added Archive Purged Records flag, which when set to on will store the purged records in the archiving tables. Added [Show Archive Log] button for users to view the archive log, which includes the information about when the records were last archived/purged. |
|
|
Added the second page of the program which displays the Invoice Inquiry by Vendor, including the vendor number, name, and accounts payable balance. For each invoice, the invoice number, invoice date, enterprise, amount, available discount, type, status, voucher number, check number, due date, check date, invoice balance, and check amount are displayed. At the bottom of the screen, in the Payment Inquiry section, the invoice number, void flag, discount amount, payment ID, check number, check date, and check amount are displayed for the invoice selected in the middle block. If the vendor has the Active flag set to off, the name will be displayed in red. Added an Inactive flag. This flag will be set to on when the vendor has the Inactive flag set to off in program VEMM, Vendor Master Maintenance. Vendor comments can be maintained in this program. |
|
|
If the vendor has the Active flag set to off, the name will be displayed in red. Modified to validate the third party account according to the ship via code assigned to the vendor. ACH Payments for VendorsACH electronic payments can be set up for vendors, however some custom programming is required. If you wish to use ACH electronic payments, contact your NDS Project Manager for more information about the custom programming required. Vendors are set up with the payment type CCK, and the ACH Flag set to on. In addition, the bank information must be entered in the lower block of program VEMM, Vendor Master Maintenance. When program APCP, Check Printing, is run, checks are not written for ACH Payments, but the payment record is created with an ACH prefix followed by the number assigned from the from the ACH_CHECK_NO sequence in program SPAN, Auto Number Control.
|
|
|
Vendor shipping accounts entered in this program are no longer tied to the shipping accounts entered in program CMMM, Customer Master Maintenance for customers. Modified this program so that it can be used to allow vendors other than shipping vendors to have third party accounts that can be used when returning products to vendors using program RTVM, Return to Vendor Maintenance. Removed Third Party Account Restriction for Customers parameter RESTRICT_CMMM_THP_ACCTS in program MURM, Initialization Parameter Maintenance. Entry of third party accounts in program CMMM, Customer Master Maintenance, no longer requires a duplicate entry in program VESM, Third Party Vendor Maintenance. For more information, see the program documentation. |
|
|
You can do further queries in the lower block. Press [Enter Query] with your cursor in the lower block. The program will ask whether or not you wish to use the header criteria in your query. |
|
|
VUTM, Vendor Upload |
Added new features and fields for file uploads. In the File Location pop-list, select Database if you are running NDS Applications in web mode. Select Client Server if you are running NDS Applications in client server mode. * The setting of this pop-list determines whether the file will be uploaded from a directory on the web server or from a directory accessible from the local computer. In the Directory Name field, if the File Location pop-list is set to Database, enter the Oracle named directory from which you are importing the file. * A list of values is provided. If the list of values is blank, contact your database administrator as some set up is required. See the Set up for Delimited Files in Web NDS section for more information about Oracle named directories. * If no Directory Name is provided when the File Location is set to Database, the default directory is determined by the VUTM_UTL_DIR parameter in program MURM, Initialization Parameter Maintenance. * If the File Location pop-list is set to Client Server, leave this field blank. In the File Name field, the entry depends on whether you are importing from the Client Machine or the Database Server. Any data file type can be imported. * If the File Location pop-list is set to Client Machine, enter the directory and file name into the field. * If the File Location pop-list is set to Database, enter only the file name and its extension into the field. The Directory Name field is used to determine from which Oracle named directory the file will be imported. |