The world of SAP is ever-changing and working in this industry you need to stay on top of things. Luckily, that’s exactly what we like to do here at CANGURU. With its CPQ Release 2202, SAP is introducing some nifty new updates for its CPQ users. Since the 5th of February, these new functionalities have seen the light of day in all lower environments (development, sandbox and testing). Production environments are set to be updated on 19th February. So what’s new? Let’s dig in.
External Configurator Integration
Easily the biggest change to be introduced: SAP CPQ can now be integrated with the configurator of an external system. This makes it possible for products to be created and maintained in SAP CPQ while performing product configuration in a different system. The only requirement being that the master data is the same in SAP CPQ and the system whose configurator is used, or the data, is mapped to SAP CPQ. This integration allows businesses that have already defined products in another system to use the SAP CPQ quoting capabilities while continuing to use their existing configurator.
Business Partner Custom Fields
As of now, it is possible to create custom fields on business partners, which can be used for a variety of business-specific purposes. Administrators can specify a value for that custom field for a specific business partner and that value will be displayed on the Involved Party when used on a quote. Admins can also choose if these custom fields are visible and editable, as well as determine the access level for different permission groups. Newly created custom fields are hidden by default until made visible.
Attribute Import Improvement
Excel templates for importing attributes must now contain an attribute system ID column, in order to prevent potential issues with updating attributes with the same name. For all new attributes being imported the column needs to be empty, because the system ID is generated in the system during the attribute creation. If existing attributes are being updated, the column needs to be populated with the correct system ID. Otherwise a new attribute will be created. A new, adapted template can easily be downloaded in the system.
Logic Between Selected Permissions Groups
Creating a user permission group has become more flexible with the introduction of the new field Logic Between Selected Permission Groups. Administrators now have the possibility to choose which logic to apply between multiple permission groups when the system filters users:
AND: the user must belong to all selected permission groups to be included in the main permission group
OR: the user must belong to at least one of the selected permission groups to be included.
Because this release introduces a whole swathe of improvements, we’ve chosen to highlight only some of our favourites here. Intrigued and want to know more? Don’t hesitate to contact us! Our experts are happy to be of assistance.