Release 7.11 |
||||||
New Features and Enhancements - Release 7.11.0A summary of enhancements made in updates since Release 7.10 is also included in this document. These include Update 7.10.5.3 whic fixes some problems with SCM price exceptions. ERP Materials Management and FinancialsSourcing and Contract Management (SCM)
ERP Materials Management and Financials Enhancements You can now create separate requisitions that generate separate POs at the header level, and not just at the line level.
Currently, on purchase orders generated from requisitions, the field Separate PO by Requisition can be selected on a requisition line. When the field is selected, the requisition line is entered on a separate PO for the vendor. With this enhancement, an entire requisition (and all its lines) can now be designated as "separate." This feature allows separate POs at the requisition header level, and prevents lines from multiple requisitions to be combined on a purchase order. Also, for requisitions whose lines are all "Separate PO," it avoids having to select the field on each line. Here are the details of this enhancement. (See Figures 1- 4 )
Below are examples: Editing a Regular Requisition Header with the New Separate PO FieldMaterials Management main Contents > Requisitioning > Requisitions > New Editing an Order Guide Requisition Header with the New Separate PO FieldMaterials Management main Contents > Requisitioning > Order Guides for Requisitioning > Create Requisition from Order Guide Separate PO Field Value on the Header Defaults to the Requisition LinesSeparate PO Column on the Requisitions ListHere are the PO lines on the unauthorized PO created for the requisition above (Figure 5). If another requisition is created for the same vendor, its lines will not migrate to the same PO as the PO generated using Separate PO By Requisition at the header level. PO Lines Generated from Above Order Guide Requisition: Separate PO By RequisitionYou can change the status of individual lines by editing the requisition (Figure 6) and unselecting Separate PO By Req. Changing the Separate PO by Requisition Status on Two LinesSCM EnhancementsMouse over the blue shaded area on an expiring supply contract to display spend on the contract.
Displaying Spend on an Expiring Contract by Mouse-Over on the Shaded AreaPreviously, for an expired contract users could "unreject" and "accept" an item with rejected prices. That capability has been removed in this release.You can display rejected items on a contract using the link on the "Work With Contract" page Actions panel (Figure 8). Opening the List of Rejected Items on an Expired Contract
Items with Rejected Prices: Disabled Unreject for Expired ContractsFor unexpired contracts, you can "unreject" any item by selecting the box Unreject & Accept. However, with this release, you can no longer do so for expired contracts. The box is grayed out and cannot be selected. The indicator Exp that a contract has expired is now visible on all panels that display the contract number.For example, in Figure 8 above, Exp appears on the Contract Info panel. SCM Problem Resolutions
Getting an Error When Trying to Add a Contract Document from the "Workbench" ListThis problem has been resolved so that documents can be added to a contract whether the user selects the "Workbench" icon, or opens the contract for editing.
Enhancements and Problem Fixes from UpdatesThe following changes were covered in previously released Notes for each hotfix or update. ERP - In some cases, 810 Invoices show "No Data" when edited under the 810 Exceptions menu. Analysis shows-that records for the invoice were incorrectly unavailable to the edit. This problem has been resolved so that editing of these invoices works as designed.
- Invoices created from 810s were ending up with a Quantity exception if the relevant item was not received and the 810 listed the same item multiple times for the same PO and PO line. When ERP creates an invoice match detail record from an 810, the received quantity is set as the invoiced quantity and the invoice goes into receipt exception. Later, when the item is received, the receipt exception clears. However, the received quantity was being set incorrectly, and not visible to the user. When the user noticed that the invoiced quantity was incorrect and changed it, the invoice had a quantity exception. Users were able to select a vendor’s suspended AP location for a check request. A vendor’s AP location for check payments was suspended because the vendor had an alternate AP location set up for ACH payments. However, when check requests were entered, users could select the suspended location. This problem has been resolved so that in situations like this, validations are in place for the suspension so users cannot select the suspended AP location for check requests. - The system was able to post journal vouchers whose journal entries were out of balance. The likely source of the problem was that the journal vouchers were created from a GL export, and while the import was running, the system encountered a lock. The system could not update either the debit or credit amount on the journal voucher header. When the JV was later edited, the status changed from incomplete to entered. The code checks that the debits and credits are equal, and if they are, the status of the JV can be changed to entered. Since both the debit amount and credit amount on the JV were zero, the edit allowed this to happen.
- An out-of-balance approved EDI 810 invoice for a blanket PO created an out-of-balance journal voucher that-the system posted. The blanket PO had a single non-file, zero cost, zero quantity line with receipts. In this situation, processing the 810 import normally creates an invoice with a missing line exception, even if the distribution detail line for the matched amount does not yet exist. When clearing the missing line exception on the invoice and selecting the PO's receipt line to match, code should create the match distribution line, if it is not found. That was not happening. As a result, the PO liability GL transaction was not created when the invoice was approved and left a one-sided AP transaction.
- PO Invoices were being set as sales taxable when the vendor's AP location had a tax type of nontaxable.
- Blanket requisitions with zero cost/zero quantity lines were dropping the charge override department. When matching the PO to the invoice, users received a message that the GL account was invalid. Because the expense code -- but not the override charge department -- was copied to the PO line, the system was trying to validate the expense code against the department/organization, and could not. This problem has been resolved. When matching PO invoices generated from blanket requisitions that contain.. • zero quantity line(s) you will not receive an error message for an invalid GL account. - When clearing an invoice tax exception for a non-EDI invoice, the invoice would go into EDI Tax Exception status. This problem was traced to the code that sets the EDI Tax Exception flag. The problem has been resolved and clearing non-EDI tax exceptions behaves as designed. The Org Override Charge and the Department Override Charge values are now updated correctly on the PO Line records.
- With some activities, users noted an increase in concurrency errors; for example, changing the buyer on bill-only POs, and then trying to authorize the POs. In general, this problem occurred when modifying information on the PO header for a non-manual / unauthorized PO, and then trying to authorize, authorize later, or save the PO. A long pause could occur, the system would time out and produce an “unspecified error.” Other incorrect behavior could also occur when trying to edit PO lines.
- Inventory transactions for EDI invoices (direct delivery POs) displayed on-hand quantity for non-stock/non-file item lines. (Non-file and non-stock items do not normally have on-hand quantity.) This problem was related to the way ERP completes invoices and multiple receipt records when the first line is non-file/non-stock. The problem was traced to parts of the code that set transaction types for different types of lines. This problem has been resolved so that on-hand quantities display correctly for direct delivery items. - Some EDI 810 invoices with exceptions were not appearing on the 810 Import Exceptions - All Organizations list. The application now displays imported EDI 810 invoices with a known 810 detail exception
- Users could not process large numbers (over 100) of contract Price Exceptions. The system would time out when the Price Exceptions were being worked. This problem has been resolved so that large numbers of exceptions can be resolved without time outs. - When the price exception count was clicked on the Contract Workbench's Exception tab, data was displayed, but contained items with a zero price difference. The problem occurred because the system was displaying items on tiers that were manually activated, and whose items should not have appeared as price exceptions. This issue was resolved so that SCM only displays price exceptions for tiers where "Activate All Items" was selected. - When a contract appeared on the Contract Workbench Price Exceptions tab and the Exceptions tab of the Work with Contract panel, when the price exception count was clicked, the number of records displayed on the Price Exceptions panel did not match the price exceptions count for that contract. This problem has been resolved so that the counts are consistent. Copyright © 2022by Premier Inc. All rights reserved. |