1. Onventis 11.8

Onventis 11.8

The new Onventis 11.8 release contains various improvements and bug fixes in the Procure-to-Pay, Supplier Management, and Core areas and new features in Source-to-Contract. Check out the complete list below!

Release date: Tuesday, December 21, 2021

Supplier Management

The function for restarting a qualification has been extended to the statuses “sent” and “expired.” The supplier’s e-mail address is also output to the user for control purposes.

update

Procure-to-pay

A few missing translation strings were adjusted so that buttons, field names, or descriptions are displayed correctly again.

update

Until now the user needs to manually fill in the purchasing group which is assigned to the material group at the shop cart. With this new implementation, the system behavior is improved so that the shop cart can be sent without much effort.

update

Fixed an error, which caused the checkbox for the framework order to be still seen while transferring a request for quotation even if the checkbox of “mark framework order at header level” is deactivated in the organization settings.
Also, the framework order checkbox was not activated in the purchase order even if it was activated at both the organization settings and at the page while transferring RFQ to order.

bug

Fixed an error that caused the organization object to be removed from the purchase order when the Organisation Object is not assigned to the approver and the approver has the user right to change Organisation Objects in orders and shopping cart.

bug

The possibility to close a purchase order with the status “Being processed” is now only possible if the corresponding user right “Manually complete the order being processed” has been assigned.

Similar, orders, that have already been sent to the supplier can only be completed and archived if the user right “Manually complete order” has been assigned.

update

Fixed an error that caused orders to be automatically archived based on the defined timeframe in the order processing workflow, even though an end-confirmed goods receipt, delivery note, or service note was canceled and the order therefore not closed anymore.

bug

The selection checkboxes are only shown in the requirement line item list if they can be used. Up to now, the selection checkboxes were shown, even when they had no function at all because of missing access rights, for example.

update

With dynamic account assignment determination, items in the shopping cart are automatically assigned to an account. In the future, users will be informed that manually adjusted account assignment information of the items will change if the organizational unit or the organizational object in the shopping cart is changed, insofar as the organizational unit or the organizational object represent valid criteria for the account assignment determination.

update

We extended the logic of additional article fields so that they are correctly considered in the case that a demand position with additional fields is linked to a catalog item with additional fields. There are two main scenarios that make the extended behavior clear:

  • if the linked catalog position has the same or different additional fields, the additional fields of the catalog position are not be overwritten by the additional fields of the free text line item. In this case, the following message is shown to the user: “The additional fields of the free text line item were emptied, because the linked catalog position contains own additional fields.”.
  • if the linked catalog position does not have any additional fields, the additional fields of the free text line item are be skipped. In this case, the following message is shown to the user: “The additional fields of the free text line item were emptied because the linked catalog position does not have any additional fields”.
update

We have adjusted the renumbering of approval steps in the order approval, requisition line item approval, and invoice approval in case steps are deleted.

When a step number is assigned multiple times, and a step is deleted, the following steps will no longer recalculate and keep their set number. When a step number is assigned only once, and a step is deleted, the following steps will recalculate to fill the resulting gap in numbers.

You can still manually adjust the step numbers at any time.

update

We have adjusted the system behavior so that a person in charge of an account allocation object only has to approve an order, invoice and service note once if they are approvers on multiple steps for this account allocation object.

update

We fixed an error, that caused sequential steps in an approval workflow to be renumbered and triggered in parallel. This situation occurred if there is an approval workflow configured, where more than one step with the same step number is triggered. Now workflow steps are triggered sequentially when they have the same step number unless they are configured as parallel steps.

bug

Platform & Core

Users can now change their “user language” in their user profile even if they do not have the right to change other values in the user profile.

The user language field has been moved to the Base data tab of the user profile for easier access.

Users are therefore enabled to work with the application in the language they prefer.

update

The template user setting allows customers to transfer values from a designated template user to other users during the user import. If a user is configured as a template user, the delta between the user import file and the template user is taken from the template user. This functionality is now extended, so that also the User Group, Organisational Unit, Organisational Object, the Superior as well as the Hierarchy level is taken from the template user unless these information are specified in the import template or empty.

update

The menu and application icons of Onventis Buyer have been reworked to ensure consistency across all Onventis applications and now feature a more streamlined and modern look.

update

Source-to-Contract

Fixed a bug that prevented a material group from being selected during the creation of a request for quotation text template.

bug

From now on, external files that a supplier has attached in the header data of an offer will automatically be transferred to a purchase order if it has been newly created from a request. These files are attached in addition to the external files from the RfQ itself, in the purchase order under “External file(s)”.

Furthermore, both external file attachments from an RfQ and external file attachments from an offer are also transferred to a purchase order if no new purchase order is created, but the offer is transferred to an existing purchase order.

update

Team members in RFQs will now also receive email notifications if a supplier participates or refuses to participate in an RFQ, provided that the team member has the right to see the supplier tab in the RFQ.

Team members will also receive the email notifications that a supplier has sent an offer to an RFQ, provided that the team member has the right to see the offer tab in the RFx.

If you do not want to send these emails, you can disable the global email templates, but then the coordinator of the RFQ will not receive any emails either.

update

Additional fields of RFx items will now also be transferred when a bid is transferred to a purchase order, provided that additional fields are available for purchase order items.

update

Previously, scale quantities were displayed on the supplier side in the offer item on the far right of the page. This often led to this quantity being overlooked. From now on, the quantity is displayed on the left, creating a better overview.

update

With the help of the checkbox “Use organizational unit of demand position in requests,” it is now possible that the transfer of a requisition into a request is based on the requester’s organizational unit and no longer on the purchaser’s organizational unit. When requisition items are added to existing RFxs, the organizational unit is no longer changed. If requirements are aggregated together into a request, the application checks whether the same organizational unit exists for all requirements. If yes, then this is used as a basis, if no, the standard organizational unit of the purchaser is used as a basis.

If a quotation is converted into one or more purchase orders and the checkbox is activated, the application will in the future take the organizational unit of the underlying requirement into account when creating the purchase orders. The default values can be accepted as usual, or overwritten using the settings options below on the same page.

update

An error has been fixed whereby already archived requests were also displayed in the widget for dates and deadlines in the area “Request for quotation with offer period deadline < 3 days”.

bug

From now on, contracts from the new contract management are also displayed in the supplier master data record.

A contract will be displayed if the supplier has been referenced in the contract by means of a lookup field. A mere textual mention is not sufficient.

update

Fixing a bug, that caused some customer-specific fields in contract management to be displayed with a “_” prefix.

bug

Fixing a bug, that caused some customer-specific fields in contract management to be translated automatically.

bug