Skip to Content
Author's profile photo K.K Cijumon

SRM UI5 Shopping cart – Dynamic Forms

Would you like to change the SRM product detail page to capture any kind of data from your users ? Do you consider using SRM for e.g. to order catering service along with food menu OR order Training with additional information ?

Welcome to SRM UI5 Dynamic Forms – Available with note 2484661 –  Configurable Form for catalog search,  in SRMNXP01 150, SRMNXP01 100

The dynamic forms are searchable in the catalog search in SRM UI Add-on shopping cart. These forms can either be generic forms, where the item is the form, or non-generic form, where the item is the catalog item, enhanced by the form tab.

The forms can be added to the shopping cart either through the item detail or from the search screen. If the user attempts to add the item to the shopping cart from the search screen, the generic form will pop up so the user can fill the form and add it from the item detail screen. For non-generic forms, the form will pop-up only if the form is mandatory.

Once the form is added to the shopping cart, the form is not available anymore and all subsequent changes to the fields should be done in the corresponding shopping cart item.

The filled forms can be saved and reused later. These saved forms are independent from any shopping cart. The user can reload the form and edit it before adding the form to the shopping cart. The user can also edit or delete the form in the saved form management view.


Report /SRMNXP/DELETE_DYN_FORMS allows an administrator user to delete saved forms based on dates, user or Form Id.


Generic Form


Non-Generic Form



Business Function: SRM_SSP_UX_INNOV_2


Implementation: Follow the steps mentioned in the implementation note 2484661

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Former Member
      Former Member

      Dear Cijumon,

      One question we would have - the note mentions notes 2486155, 2419172 and 2481466 should be implemented if we have the right release, but are in a lower support pack - which is the case for us. But, after download we noticed no all SP are accepted and you not need to be under the SP 03 (we have 01). Is this correct or is a mistake? Also, if it is correct (which I presume it is), is there any workaround we could do in order to implement this functionality?

      Thank you,



      Author's profile photo Laurent Burtaire
      Laurent Burtaire

      Hello Daniela,


      in the OSS note 2484661 - Improvement note: Configurable Form for catalog search if you open the correction instructions, you can see minimum SP level for SRMNXP01, release 150 is the SP03.

      For release 100, it is SP07.

      So if your system is below those SP, you will have first to update your component, then apply OSS notes.

      Or your can implement the second last SP.