Release 7.6, 6/2020 |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
New Features and Enhancements - Release 7.6Release 7.5 is also available at this time: click What's New in Release 7.5. Known Problem: Our development team is in the process of making Premier ERP browser-independent. We hope to release this feature later in the year. The development work is being done across multiple releases, with the goal of minimizing disruption to our users' organizations. This work has been tested extensively across all areas in the system. However, we recently discovered that three (3) Quick Click panels do not function with the changes as expected. For example, one of the problem panels is the Quick Click for Purchase Orders for Matching. As a result, these panels will not currently return search results. This issue will be corrected in the next available update. We apologize for any inconvenience this may cause. ERP Materials Management and FinancialsSourcing and Contract Management (SCM)
ReportsERP/SCM Problem ResolutionsERP Materials Management and Financials Enhancements
|
Field Label | Field Name | Data Type | Length |
Create User ID | CreateUser | varchar | 20 |
Create User Name | UserName | varchar | 20 |
Del To Loc | DelToLoc | varchar | 3 |
Dept#/Name | DeptName | varchar | 50 |
Issue To Dept | IssueToDept | varchar | 20 |
Issue To Dept Desc | IssueToDeptDesc | varchar | 50 |
Issue To Org | IssueToOrg | varchar | 15 |
Organization | Organization | varchar | 15 |
Package ID | PackageID | varchar | 250 |
Pick No | PickNo | numeric | 15 |
Piece Count | PieceCount | varchar | 20 |
PO No | PONo | varchar | 15 |
Receipt No | ReceiptNo | varchar | 15 |
Signature Date | SignatureDate | datetime | 23 |
ERP Problem: A system note was written to non-file requisition lines indicating that the requisition lines already existed on the associated POs. In fact, the non-file lines did not exist. This problem was traced to the timing the system uses to process through the existence/non-existence of a PO line, and has been resolved. This incorrect system note should no longer occur.
ERP Problem: Scenario: a user created a PO invoice with a missing line where a quantity exception existed. The user entered the line with a quantity exception on the Missing Lines tab, and then cleared the missing line exception with the action "Select existing PO Line and match Invoice Line." The user then cleared the quantity exception with "Invoice Correct." The problem was that if the PO line had an existing receipt for part of the quantity, the original receipt did not get matched.
This problem was traced to how the system processes the quantity exception, in this case, and has been resolved. The receipt will now match, and the invoice can be completed.
SCM Problem: Removing a local entity from a contract did not remove the local entity's manufacturer information, leaving the contract unmatched. When users unregistered a local entity from the manufacturer Entity on a contract header, sometimes the contract detail rows retained the removed entity name, and sometimes displayed no manufacturer entity value. This problem has been resolved. When a contract has a reassigned local entity, the correct manufacturer displays as designed.
To remove a local entity association:
If you just removed an entity association, you will need to wait a few minutes for the process to complete before assigning a new entity. Otherwise, when you try to assign a new entity, an error message appears" "Entities cannot be Identified, background processes may still be running."
To create a new entity association:
Copyright © 2020 by Premier Inc. All rights reserved.