WAVE RELEASE based on DELIVERY CREATION DATE or PLANNED SHIP DATE in SAP EWM

2 weeks ago 7

Dear Experts,

Good day.

We person a request related to WAVE RELEASE based connected DELIVERY CREATION date oregon PLANNED SHIP DATE.

My 1st question related to modular SAP EWM behavior, Wave merchandise criteria disorder based connected SAP F1 definition.

hari_y11_0-1731157694340.png

According to above, question merchandise should hap based connected “yard departure date”,  below is our example:

Delivery created day 11/07/2024 / 14:00:04

Yard departure date. 11/08/2024

hari_y11_2-1731157736712.png

Planned GI connected 11/08/2024

hari_y11_3-1731157761800.png

Wave Template, merchandise days 0.

hari_y11_4-1731157784329.png

Wave merchandise date  11/07/2024 / 15.01.00

hari_y11_5-1731157796166.png

As per modular behaviour the Wave merchandise day calculation is updating a time prior(yard day -1 day) to existent departure day signifier the yard, which is confusing, wherefore it is taking -1 day?

Some different cases:

Ex 1: wave instauration date 11-06-2024 and departure day from gait is 11-07-2024 merchandise day is updated 11-06-2024  and question got released connected merchandise day 11-06-2024 merchandise clip 15:01:00 arsenic per question template 

Ex 2: wave instauration date 11-06-2024 and departure day from gait is 11-08-2024 merchandise day is updated 11-07-2024 and question would merchandise connected 11-07-2024 astatine 15:01:00

Ex 3: wave instauration date 11-06-2024 and departure day from gait is 11-13-2024 merchandise day is updated 11-07-2024 and question would merchandise connected 11-12-2024 astatine 15:01:00 

Question 1 is: Why strategy taking Yard day -1 time for release?

Question 2 : If we privation the question merchandise based on  DELIVERY CREATION day oregon PLANNED SHIP DATE immoderate options available?

Kindly assistance to execute this solution oregon to recognize nonstop question merchandise logic.

Thanks,

Hari

 SAP Extended Warehouse Management SAP Community SAP Knowledge Warehouse 

@sapewm @SAP 

Read Entire Article