Release 2024.1

Over the last 3 years, we have introduced several document types in our purchasing section, like Purchase Requisition, Purchase Order, Confirmation, Demand and Reservation. According to this, we need to streamline the labels on all these documents. In particular, we are adjusting the label for document type, document Id and document name.

The basket in top right corner and the edit screen for this basket will get the name ‘basket’, in German ‘Einkaufswagen’. Whenever a user will decide to edit an existing document like a Purchase Requisition, he will process the changes in the basket.

Navigation buttons for CHECK basket, SAVE basket and BACK to previous screen are reorganized to follow best practise standards.

If the One-Click SUBMIT button is hidden in the mini basket on the right hand side following the system customizing, then the alternative button GO TO BASKET will be displayed. In this case, user must navigate through the basket detail screen so he can verify the data in the basket accordingly.

The confirm button on the create confirmation screen has been adjusted to ‘Confirm receipt’ (in German: 'Empfang bestätigen').

There are several cases where users cannot submit a basket with the data they entered. Now users can save their basket to their personal ‘basket draft’ list so that they can resume further processing at a later date. Users can save several basket draft documents as needed.

By introducing the new ‘Demand Center’, we are supporting new business scenarios for our customers. The ‘Demand Center’ can be understood as the successor of the former SAP SRM ‘Sourcing Cockpit’. Demand Center is supporting two user roles:

1. DEMAND_OWNER
   When a requester is submitting a basket, the system will create a ‘Demand Document’ in the cloud instead of a purchase requisition in SAP.

2. DEMAND_MANAGER
   A demand manager will process the new items he is receiving in the demand center. After reviewing the business need addressed in form of demand items, he can consolidate several items into follow-on documents like purchase requisition.

In future releases, we are also planning to support the conversion of demand items into sourcing events and operational contracts.

If a Goods Receipt or Service Entry Sheet has been posted by a user, there might be a need to cancel such a document. By doing so, the system might ask the user to select a cancellation reason, following SAP standard configuration.

This feature can be granted only to customers who will update the BeNeering Cloud Adapter (BCA) in their SAP.

The screens for Goods Receipt list, Service Entry sheet list and their document detail screens will show the document status ‘Accepted’ and ‘Cancelled’ as applicable. This differentiation is also reflected in the document flow.

Users can now enter a delivery address and/or accounting data in the basket by selecting a profile they have configured in their personal user settings. In the past it was only possible to change the profile in user settings for new items in the basket. Now you can update your pre-defined address/accounting data directly from the basket.

This feature can be granted only if the Cloud Forms for delivery address and/or accounting will be re-configured to include the new selection button.

In exceptional cases, there is a need to connect an external app like SAP Fiori to the Guided Buying application.

Example use case: A user is submitting a basket that creates a Purchase Requisition with a workflow. Once of the workflow steps considers a controller, who will need access from this basket view to another Fiori App, so he can register additional master data in SAP like an asset, that is pushed back to update the Purchase Requisition.

Dynamic Cloud Forms are designed to build the user interface in purchasing. The tooltip function has been extended to support a formatted help text by following HTML patterns in the configuration.

The workflow Inbox in Cloud has been extended to support the ‘assign to me’ function as another option in the ‘forward’ workitem logic.

This feature can be only supported for customers running the Central Workflow logic in BeNeering Cloud

The product list in the SHOP application on left hand side and the basket item list have been adjusted to follow our new material design.

Now it is possible to create a confirmation for a Purchase Requisition, even if the final delivery flag has been set in previous confirmations. You can also remove the final delivery flag by posting a new confirmation. The system will not allow creating a confirmation if the outstanding quantity is 0.

In previous versions it was only possible to search for a purchase requisition by entering the document Id. Now we support search by:

• document name

• Supplier AID,

• Goods Recipient (additional configuration required),

• Creator (additional configuration required).

This feature can be granted only to customers who will update the BeNeering Cloud Adapter (BCA) in their SAP.

In previous release we have introduced the display of service items following the service hierarchy in SAP. With this release, we are introducing new cloud form that shall support the creation of a limit item with several lines of service items - both connected on item level in a purchase requisition. Also the edit function for limit item and service items is supported on basket level too.

For compatibility reasons with SAP, the Cloud forms connected in a basket will follow the field structure as known from SAP MM-SRV. The Cloud form guiding the user in the process before the add-to-basket button is pressed can be another one.

The Sourcing App in Supplier Portal can now support additional filters like ‘Event Date’.

Customizing in Supplier Portal is needed: additional filters can be added by connecting customer fields.

Each time a catalog is uploaded by a supplier or buyer, it will run through the validation engine to verify the uploaded content. In order to simplify the onboarding of new catalogs, we are introducing ‘Validation Rule Templates’ that can be applied to catalog containers. By applying a ‘Validation Rule Template’ to an existing catalog container, the validation rules inside this template are copied to this catalog.

This function must be requested and can be granted only to buyer administrators, who are responsible for content creation in the catalog module.

Editors functionality was extended by:

• basic handling of table component,

• additional component attributes (new button types, extended search-help functionality),

• it is possible to search Dynamic Cloud Forms by description,

• general usability improvements.