D365 Finance & Operations and Dynamics AX Forum

While resolving a user error we discovered we had orphaned records in the WHSTMPWORKLINE which is a temporary table used in the wave creation process.  One of the resolution steps was to delete all records orphaned in the table.  We determined the orphaned records not related to the issue we were working were from some post go live challenges that have also since been resolved.

We have been monitoring the table since this issue and now have records being orphaned multiple times per week.  From what we can glean this is related to our replenishment process.

Has anyone had a similar challenge?  We are struggling to trace what action is causing these to be orphaned.  We do not see any results that would help us pin down details as it seems the work is created correctly even with the orphaned records being left behind.

Thanks for any help!

------------------------------
Nicole Aalders
Bush Brothers & Company
Knoxville TN
------------------------------

Nicole,
I have seen orphaned record when a wave is not allowed to complete once it is started. I haven't seen it with replenishment but with sales order pick work and production picking work. Records stuck in the temp table can create false reservations that are not tracable. I hope this helps.

------------------------------
Sarah Gabriel
Operations Business Analyst
Kai USA Ltd
Tualatin OR
------------------------------

Original Message:
Sent: Sep 10, 2019 11:07 AM
From: Nicole Aalders
Subject: Orphaned Records in WHSTMPWORKLINE


While resolving a user error we discovered we had orphaned records in the WHSTMPWORKLINE which is a temporary table used in the wave creation process.  One of the resolution steps was to delete all records orphaned in the table.  We determined the orphaned records not related to the issue we were working were from some post go live challenges that have also since been resolved.

We have been monitoring the table since this issue and now have records being orphaned multiple times per week.  From what we can glean this is related to our replenishment process.

Has anyone had a similar challenge?  We are struggling to trace what action is causing these to be orphaned.  We do not see any results that would help us pin down details as it seems the work is created correctly even with the orphaned records being left behind.

Thanks for any help!

------------------------------
Nicole Aalders
Bush Brothers & Company
Knoxville TN
------------------------------

Hi Sarah,

Thanks for the reply.  It confirms what we thought was happening.

Did you just delete the orphaned records?  I think we may need to setup a process to remove the records until we can figure out what action is causing them to be created and stop it from happening so regularly..

Thanks again,



------------------------------
Nicole Aalders
Bush Brothers & Company
Knoxville TN
------------------------------

Original Message:
Sent: Sep 11, 2019 11:17 AM
From: Sarah Gabriel
Subject: Orphaned Records in WHSTMPWORKLINE

Nicole,
I have seen orphaned record when a wave is not allowed to complete once it is started. I haven't seen it with replenishment but with sales order pick work and production picking work. Records stuck in the temp table can create false reservations that are not tracable. I hope this helps.

------------------------------
Sarah Gabriel
Operations Business Analyst
Kai USA Ltd
Tualatin OR

Original Message:
Sent: Sep 10, 2019 11:07 AM
From: Nicole Aalders
Subject: Orphaned Records in WHSTMPWORKLINE


While resolving a user error we discovered we had orphaned records in the WHSTMPWORKLINE which is a temporary table used in the wave creation process.  One of the resolution steps was to delete all records orphaned in the table.  We determined the orphaned records not related to the issue we were working were from some post go live challenges that have also since been resolved.

We have been monitoring the table since this issue and now have records being orphaned multiple times per week.  From what we can glean this is related to our replenishment process.

Has anyone had a similar challenge?  We are struggling to trace what action is causing these to be orphaned.  We do not see any results that would help us pin down details as it seems the work is created correctly even with the orphaned records being left behind.

Thanks for any help!

------------------------------
Nicole Aalders
Bush Brothers & Company
Knoxville TN
------------------------------

Hi Nicole,
Yes, we deleted them because we only had a few infrequently. However I did it when I knew nothing was processing, like Sunday night.
Good luck and post an update when you get it worked!

------------------------------
Sarah Gabriel
Operations Business Analyst
Kai USA Ltd
Tualatin OR
------------------------------

Original Message:
Sent: Sep 12, 2019 03:01 PM
From: Nicole Aalders
Subject: Orphaned Records in WHSTMPWORKLINE

Hi Sarah,

Thanks for the reply.  It confirms what we thought was happening.

Did you just delete the orphaned records?  I think we may need to setup a process to remove the records until we can figure out what action is causing them to be created and stop it from happening so regularly..

Thanks again,



------------------------------
Nicole Aalders
Bush Brothers & Company
Knoxville TN

Original Message:
Sent: Sep 11, 2019 11:17 AM
From: Sarah Gabriel
Subject: Orphaned Records in WHSTMPWORKLINE

Nicole,
I have seen orphaned record when a wave is not allowed to complete once it is started. I haven't seen it with replenishment but with sales order pick work and production picking work. Records stuck in the temp table can create false reservations that are not tracable. I hope this helps.

------------------------------
Sarah Gabriel
Operations Business Analyst
Kai USA Ltd
Tualatin OR

Original Message:
Sent: Sep 10, 2019 11:07 AM
From: Nicole Aalders
Subject: Orphaned Records in WHSTMPWORKLINE


While resolving a user error we discovered we had orphaned records in the WHSTMPWORKLINE which is a temporary table used in the wave creation process.  One of the resolution steps was to delete all records orphaned in the table.  We determined the orphaned records not related to the issue we were working were from some post go live challenges that have also since been resolved.

We have been monitoring the table since this issue and now have records being orphaned multiple times per week.  From what we can glean this is related to our replenishment process.

Has anyone had a similar challenge?  We are struggling to trace what action is causing these to be orphaned.  We do not see any results that would help us pin down details as it seems the work is created correctly even with the orphaned records being left behind.

Thanks for any help!

------------------------------
Nicole Aalders
Bush Brothers & Company
Knoxville TN
------------------------------

Thanks for the input Sarah!

We have decided to run a SQL job to monitor the WHSTmpWorkLine table for a while longer.  We will also delete periodically as the records grow to include a large number of cases.

There is a potential hot fix: KB 4339951 [Backport] Blocking when a wave fails and need to clean up when another wave is running on Table WHSTmpWorkLine.

Our challenge is we have no way to test if we cannot proactively cause the issue.  For now we have decided to monitor and continue efforts to determine what steps lead to this situation so we can test.  Blindly installing a hot fix is not something we would like to do.

Thanks!

------------------------------
Nicole Aalders
Bush Brothers & Company
Knoxville TN
------------------------------

Original Message:
Sent: Sep 11, 2019 11:17 AM
From: Sarah Gabriel
Subject: Orphaned Records in WHSTMPWORKLINE

Nicole,
I have seen orphaned record when a wave is not allowed to complete once it is started. I haven't seen it with replenishment but with sales order pick work and production picking work. Records stuck in the temp table can create false reservations that are not tracable. I hope this helps.

------------------------------
Sarah Gabriel
Operations Business Analyst
Kai USA Ltd
Tualatin OR

Original Message:
Sent: Sep 10, 2019 11:07 AM
From: Nicole Aalders
Subject: Orphaned Records in WHSTMPWORKLINE


While resolving a user error we discovered we had orphaned records in the WHSTMPWORKLINE which is a temporary table used in the wave creation process.  One of the resolution steps was to delete all records orphaned in the table.  We determined the orphaned records not related to the issue we were working were from some post go live challenges that have also since been resolved.

We have been monitoring the table since this issue and now have records being orphaned multiple times per week.  From what we can glean this is related to our replenishment process.

Has anyone had a similar challenge?  We are struggling to trace what action is causing these to be orphaned.  We do not see any results that would help us pin down details as it seems the work is created correctly even with the orphaned records being left behind.

Thanks for any help!

------------------------------
Nicole Aalders
Bush Brothers & Company
Knoxville TN
------------------------------