Historically, it wasn’t possible to know the financial impact of scrapping. In 8.9, the Scrap Transactionlog and Scrap by WO reports were enhanced to calculate the value of scrap. 

It uses the Cost Per Unit value of the product to calculate the value of the scrapped quantity. 

The APIs continue to be improved in 8.9. 

Resend successful integrations 

Previously, when a payload was sent successfully, the “Resend” button would not display. It is now possible to resend an integration payload even if it was successful the first time. This allows more flexibility when correcting mistakes in the payload or at the ERP/external system end. 

Add Export button to Integration Logs  

You can select a single record in the Integration Log and click the Export button to view the complete log details on a new screen. You can then export the log information in a properly formatted Excel file. 

Prevent trigger of integration log based on custom logic 

When an integration is triggered, but the configured SQL doesn't return any data, there are two possible reasons for this:

1. There is no payload to send.
2. There is an error.

It used to be impossible to distinguish between the two. In 8.9, you can now distinguish between the two and choose whether to ignore, as in the case of empty payloads, or to return an error message.

A new setting in integration, Ignore On Empty Payload. The integration log processer will ignore the record if: 

The integration log processer will throw an error on the record if: 

Multiple outbound API calls from a single trigger 

Integration Manager has been updated to support multiple outbound API calls from a single trigger point within Eyelit MES-M. Previously only a single API call could be made. 

For example, a scrap may trigger both an inventory transaction in an ERP and a non-conformance in a QOS.

Material Item Transactions 

Ability to Move and List Material Items through API calls. 

We've added validation to prevent you from editing a job to reduce the quantity ordered to a quantity that is less than that which has already been started.

The Schedule Manager screen now makes the Recipe, BoM and Workflow visible and easier to work with. 

The Schedule Manager provides easier access to issues related to jobs. The Schedule Manager displays the issue status ("On Hold" or "Not Started") with red indicators and exclamation icons when issues are linked to a job. 

A new column indicates the number of issues (job, job op, item, node) linked, so you can see whether a job on hold has issues against it, or whether the job was put on hold for some other reason. 

The Linked Issues button appears when selecting a job with an issue (see image above). It opens the Issue Tracker pop-up with the job filtered. 

The Principle Name, which is required to federate user accounts, is now included in the user import capability. 

Originally, those with access to user management permissions via the system ‘User Administrator’ role were the only users that could view all users in the User Manager but they could also create users, assign licenses, etc. - i.e. this was an ‘all or nothing’ system role. 

In 8.9, additional user permissions were created that allow roles with those permissions to either view all user accounts or just the accounts of users who are their subordinates. This separates the viewing of user profiles from transactions. 

The following permissions were added: 

In 8.4, we introduced the ability to replenish the amount of WIP scrapped so that the final completed quantity remains at what was originally targeted. The limitation was that this functionality was not possible within a parallel flow. In 8.9, that functionality was extended to a parallel flow.

The scrap options are set up in Workstation Button Profile and are:

• Scrap - No replenish: The scrapped quantity will not be automatically replenished. You can manually append (if the workflow version and the operation scrap mode allow) which will start the appended quantity at the first operation in the workflow.
• Scrap - Replenish at current op: A quantity equivalent to the scrapped quantity will automatically be adjusted on at the current operation in the workflow. 
• Scrap - Replenish at previous op: A quantity equivalent to the scrapped quantity will be adjusted on at a selected previous operation in the workflow. In a parallel flow, this option is restricted to operations within that channel. If not on a parallel flow, only operations not on a parallel flow channel will be allowed. 
• Scrap - Replenish from start op: A quantity equivalent to the scrapped quantity will automatically be appended and starts at the first operation in the workflow.

Restrict Material Transactions to a Material Reason Type 

In 8.9, the introduction of the Material Reasons Type functionality allows you to manage numerous reasons and easily associate them to transactions. For example, you might have a set of material reasons that only relate to scrap, pick reverse, or release, etc.  

This enhancement allows you to group the reasons and assign them to specific transactions, and this allows you to quickly zero in on the reason types when doing analytics. The image provides a few examples. 

Issues 

Issues may optionally be associated with one of the following scopes; Item Scope, Job Scope, Job Op Scope, Item Op Scope or Node Scope.

Prior to 8.9, those scopes were either enabled or disabled globally and if enable, were available for issues of all types and if disabled, were not available for issues of any types. In 8.9, it's now possible to configure scopes on a type-by-type basis. 

When you add a new issue, it would adhere to the settings for that type rather than be restricted to a global setting.

With the new configuration, operators are no longer presented with scopes that are invalid for their particular issue types which simplifies the experience for operators and limits the chance of making mistakes.

The Translations languages have been expanded to include Spanish (Costa Rica) and Spanish (Latin America).