Overview
Currently the price change happens when copying of items from templates/old carts and then clicking on review cart. SRM UI5 has a different concept of cross catalog search (where prices within our index can easily not be up-to-date); the actual price change must come more often and easily than in the typical SRM 7.0 cart. Therefore, when we order a UI5 cart we must have price check again and actually change the outdated price by the new one.
Price validation and update will be triggered in the following scenarios:
The following new flags are introduced in the IMG node Define External Web Services:
Price Update
BAdI BBP_BDI_MDFY_CTLG_CNFG_SCRN:
To make these flags visible a BAdI BBP_BDI_MDFY_CTLG_CNFG_SCRN is implemented. This BAdI is defined in SRM CORE i.e. SRMSERVER. But there is a default implementation for SRM UI 1.0 Add-on where the flag is always visible. This is an internal bAdi.
Items can be added to the cart in the following ways:
There is a possibility of updating the price from catalog or enterprise search while one adds an item to the cart, and then click Review Cart.
This is done by maintaining the customization, as mentioned below:
While adding the item from search, price is always copied from enterprise search (TREX).
While adding item from favorite, template and existing shopping cart if the flag Validate Product Data from SAP Enterprise Buyer is checked the following behavior is expected, as mentioned below:
Validating and updating price while ordering
While ordering the cart, price of the item from shopping cart is validated and updated depending on the configuration defined for the catalogs.
Configuration
There is a possibility of validating and updating the price from catalog or enterprise search while ordering the cart by maintaining the customization as mentioned below:
Check the flag Price Update in in IMG node Define External Web Services.
This configuration updates the price of an item in shopping cart from catalog or enterprise search (TREX) only when the following set up is configured:
The advantage of the BAdI is as follows:
Price update can be controlled for SRM CORE and SRM Add-On separately based on sub type. If the same SRM system is used for both the application i.e. CORE and Add-On, price update is only triggered for Add-On based on the sub type which is available as a default implementation.
The following combination for the configuration that is maintained in IMG node Define External Web Service is shown in the table below.
Note:
Validate | Activate | Update | Dummy | Behavior |
X | 0 | 0 | 0 | Validation occurs from catalog or TREX based on the above customizing stated In this scenario, price gets updated on adding item from (MyCarts, Favourites etc) and then clicking Review Cart. |
X | X | 0 | 0 | The above-mentioned scenario exists; in addition, the following occurs:
|
X | X | X | 0 | The above-mentioned two scenario's exist; in addition, the following occurs:
|
X | X | X | X | The above scenario exists; in addition the following occurs:
|
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
9 | |
9 | |
5 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 |