Onventis 2025.3

The new Onventis 2025.3 release contains various enhancements, improvements, and bug fixes. Check out the complete list below!

Procure-to-pay

New "IsEndReceived" Field in Onventis Buyer Public API for Orders 

• Added the "IsEndReceived" field (boolean) to the Onventis Buyer Public API (GET /orders endpoint). 

• This field indicates whether a final confirmation has been received for each order position. 

Enhanced cXML Order and OrderChange with Organizational Object Details 

The cXML Order and OrderChange documents now include two new header-level fields: 

<OrderRequestHeader type="new" orderID="001234" orderDate="2025-01-26T10:00:00"> 
    <Extrinsic name="OrgObjectNr">12345</Extrinsic> 
    <Extrinsic name="OrgObjectTitle">Finance Department</Extrinsic> </OrderRequestHeader>

These fields provide additional organizational context, enhancing order processing and reporting accuracy. They are included only when data is available

Improved Visibility and Guidance for Mandatory and Source Articles 

• Replaced inline text with an info icon to indicate quantity edit restrictions for Mandatory and Source articles - consistently across Shopping Cart, Purchase Orders, and Demand Positions for improved usability. 

• Added "Source" and "Mandatory" labels to items in the "List of Items to Be Released" when a mandatory reference exists. 

• Labels are visually aligned with those in the "Requisition Line Items" view. 

Configurable "Total Amount" Column & Filtering in Requisition Line Items 

• Added a new "Total Amount" column in the requisition line item view, calculated as Price Unit × Quantity. 

• Users can enable or disable this column via a checkbox in User Settings → Display → Requirement Line Items. 

• User preferences for displaying the "Total Amount" column persist across sessions. 

• The "Total Amount" column dynamically recalculates upon updates and supports sorting, improving requisition management usability. 

• Filtering: Users can now filter Requsition line item by their Total Amount, using operators for efficient request management. 

Default Values When Converting RFQ to Purchase Order 

• Improved handling when converting RFQs to Purchase Orders: 

  • Requisition line item (RLI)-based RFQs: Original RFQ values (including Account Assignment Category) are preserved. 

  • Free-text RFQs: Purchaser’s standard default values are applied. 

  • Ensures data consistency, reduces manual data entry, and aligns with sourcing procedures based on RFQ origin. 

Supplier-Specific Material Group Mapping in Shopping Cart and Purchase Orders 

• Introduced a new organizational setting (Org Settings → Purchase Order → General) to enable supplier-specific material group restrictions. 

• When activated, the shopping cart and purchase orders will display only the material groups mapped and approved for the selected supplier. 

• Changing the supplier in the shopping cart resets the material group selection, prompting users to choose again based on the updated supplier mapping. 

• Ensures accurate adherence to supplier-material group mappings, improving purchasing compliance and data quality. 

Note: This enhancement applies specifically to shopping carts and purchase orders. Demand positions, sales orders, and service notes remain unaffected

Setting to Disable Internal Article Condition Updates During Order Process & Approval

• A new setting has been introduced under Organization Settings > Catalogs to provide customers with greater flexibility during the order process. The setting is titled:
  "Do not update internal Article Conditions during order process & approval"

• This setting is disabled by default.

• When enabled, the system skips the update and validation of internal article conditions during:

  • Shop cart to Order transfer

  • Shop cart to RLI transfer

  • Order sending

  • Order approval

• Users will not receive pop-up notifications about item data changes when this setting is active.

• When the setting is disabled, the default behavior (article condition updates and pop-ups) remains unchanged.

Email Handling Aligned with Complaint Type "Internal"

• The system now ensures that no emails are sent to suppliers when a complaint is marked as "Internal".

• Previously, supplier notifications were still triggered despite the internal classification.

• This change aligns email behavior with the intended internal-only nature of such complaint types.

• Applies to the following complaint actions: Send, Resend, Reopen, Close, Cancel, Stop Edit Mode (Supplier), and Send Current Status.

SAP Related Key-Update

• New Option to Hide Surcharges in Order PDF
  A new setting has been introduced under Org Settings → Order → Order PDF to suppress surcharge visibility in order documents. When the "Do not display any surcharges in the order PDF" option is enabled, all surcharges at the position level are excluded from the PDF output.

• Automated Demand List Export via BC-Job
  The Excel export of the Demand List can now be automated via BC-Job, similar to the existing OrderList export. This includes filter selection and configuration for SMTP, SFTP, and static port options within BC administration, enabling smoother integration with external systems.

• Excel Import Extended to Support Demand Closure
  Excel-based demand import has been enhanced with a new column CloseDemand (values: 1 = close, 0 = keep open) to support automatic closing of demand positions. When marked for closure, the system mirrors the manual “Close” function, including triggering any configured interfaces and logging the action with the comment “Closed by import.”

• SAP Attachments Excluded from Resending in Order Changes
  For SAP-integrated orders, attachments originally imported from SAP (e.g. technical drawings) are now flagged with creation source = 1 and will not be resent to SAP during order changes triggered from Onventis. Only new attachments created within Onventis (e.g. sales order confirmations) will be transmitted, supporting both embedded base64 and FTP-based formats.

• SAP order imports have been enhanced to support the <WEPOS> indicator for workflow determination.  

  • If <WEPOS> is present, the system assigns the defined non-standard workflow (typically including goods receipt). 

  • If <WEPOS> is absent, the system assigns the defined standard workflow (typically excluding goods receipt). 

  • Workflow assignment respects organizational unit-specific configurations, defaulting to general settings when org-unit-specific settings aren't provided. 

    XML

    <IDOC BEGIN="1">
      <E1EDP01 SEGMENT="1">                <!-- Line item segment -->
        <POSEX>00010</POSEX>               <!-- Item number -->
        <Z1EDPWE SEGMENT="1">              <!-- Custom segment for additional data -->
          <WEPOS>X</WEPOS>                 <!-- WEPOS indicator (X = present, apply non-standard workflow) -->
        </Z1EDPWE>
      </E1EDP01>
    </IDOC>

Source-to-Contract

Round cap in dutch auctions

From now on, dutch auctions have a round cap of 100 rounds. If 100 rounds have passed and line item is not auctioned, the line item will be finalized by the application.

Supplier Management

🚀 Feature release: With the brand new File network repository the file management in Supplier management is reaching the next level.