SAP for Retail Discussions
Join conversations about personalization, omnichannel strategies, and operational excellence in retail using SAP for Retail software.
cancel
Showing results for 
Search instead for 
Did you mean: 

WSM3 listing-delisting BADI/SMOD enhancement options

Rashmits
Explorer
0 Kudos
1,756

Hi Andreas,

We have a 'Z4' listing procedure with Z function module as exit class, enhanced MM41 for few Z fields, also enhanced WSM3 for 'delete listing checkbox'.

We need SAP BADI/exit options to implement logic for below requirements

1. on WSM3 add a validation for listing and delisting based on a condition.

2. Modify the WLK1-DATBI to +90 days while delisting.

3. delisting to add additional entry in the WLK1 table.

Please suggest the enhancement that can be used?

Regards,

Rashmi

3 REPLIES 3

andras_strobl
Product and Topic Expert
Product and Topic Expert
0 Kudos
837

Hi Rashmi,

SAP offers the following options for enhancing the standard logic:

  • BADI_WSM_DELETE_WLK1 (method DELETE_LISTING_CONDITIONS or SET_PARAMETER to manipulate the selection UI)
  • BADI_ASORT_LISTING_DATE_CHANGE (method CHANGE_DATE)
  • LIST_DISCONTINUATION (method LISTING_PARAMETER_SET might be useful to control discontinuation

You could use these for date changes and listing condition deletion.
(I remark, that it does not make much sense to speak about delisting, when you would like to change the DATBI to +90 days. It is a simple validity date change. Namely as soon as the DATBI is not reached, the listing condition is still valid, except of having the SSTAT'='5' value. Otherwise, when reaching the today+90 days, the listing condition will be not valid anymore (due to the expiration, and is logically equivalent to delisting).)

Best regards,
Andras

0 Kudos
837

Thanks Andras.

While I could use the first one.
I am not able to find BADI_ASORT_LISTING_DATE_CHANGE. Is it available on S4HANA on premise 1610?

andras_strobl
Product and Topic Expert
Product and Topic Expert
0 Kudos
837

Hi Rashmi,

The BADI_ASORT_LISTING_DATE_CHANGE is available from ECC 600 up to recent S/4 versions.

Maybe you have not yet implemented the SAP note delivering this implementation.

Try to download the note 2917808, which has also attached a PDF as short documentation for the BAdI.

Best regards,
Andras