Archived Deleting a batch?

[FredPanda3]

This might seem like a stupid question, but is there a way to delete a batch that has already been dropped (on accident)?

 

[allnew2]

This might seem like a stupid question, but is there a way to delete a batch that has already been dropped (on accident)?

Delete no , burning yes, but if you burn a batch it will show up on the suspect pull.

 

[REDcardJJ]

Delete no , burning yes, but if you burn a batch it will show up on the suspect pull.

what's burning a batch? just scanning through it but not actually pulling?

 

[REDcardJJ]

Move, scan, pull, MyWork, scan, backstock. It's easier with two devices, as switching apps constantly tends to cause issues.

thanks!

 

[NPC]

Is it bad to burn batches?

 

[REDcardJJ]

Like allnew2 said, it'll be flagged as suspect and your name will appear on the suspect report for your ETL. Burning batches can negatively impact sales, so it's usually a big no-no.

But there are times when it's necessary. Just make sure to partner with your TL/ETL so they have a heads up that you'll appear on the report.

i'm not planning on doing it, i just like to know things. i don't get in the backroom very much these days anyway

 

[allnew2]

what's burning a batch? just scanning through it but not actually pulling?

Pulling and backstock right back

 

[allnew2]

No error is created.
What I would always do, (even though it really fucks the counts) is say i pulled 99 which would trigger a 'did you pull all from this location' box which I would answer 'no' and would leave 'some' located there.

Some is a error

 

[NKG]

The correct way to burn batches- Scan backroom label, scan item, note quantity go into mywork and scan it back in. Repeat. If you don't do this- you will fuck up the backroom.

 

[PackAndCry]

We found that if you drop another manual in on top of a manual, it seems to overwrite the old one. Same with a POG fill.

 

[NPC]

it's bad because it ups SFQ and prevents replenishing those items even longer until someone manually fills, or enough sell to trigger replenishment.

Ah got it. But is there a time limit? Often I see people going to push what they pulled, only to have to backstock it anyway. So it doesn't cause issue, say after 20 minutes?

 

[NKG]

I actually learned a lot in this tread

 

[allnew2]

The correct way to burn batches- Scan backroom label, scan item, note quantity go into mywork and scan it back in. Repeat. If you don't do this- you will fuck up the backroom.

Correct but it you are the person who burns the batch your name will be on a suspect pull . And that’s not good for my report

 

[NKG]

Correct but it you are the person who burns the batch your name will be on a suspect pull . And that’s not good for my report

So basically pull it ?

 

[allnew2]

Ah got it. But is there a time limit? Often I see people going to push what they pulled, only to have to backstock it anyway. So it doesn't cause issue, say after 20 minutes?

Do they pull and push the manuals after the freight unload?

 

[allnew2]

So basically pull it ?

Or have one of your friend backstock it behind you 😎

 

[NKG]

Or have one of your friend backstock it behind you 😎

If I pull it, I have to have someone else backstock it not to be suspect?

 

[allnew2]

Or have one of your friend backstock it behind you 😎

If you pull it someone else has to backstock back that way no one is on the report 😉

 

[allnew2]

If I pull it, I have to have someone else backstock it not to be suspect?

No because the report is for suspect pulls only , meaning just for the one that pulls the batch . Ie i did it with transition I pulled it and then I made the other team member go back and backstock it

 

[NKG]

No because the report is for suspect pulls only , meaning just for the one that pulls the batch . Ie i did it with transition I pulled it and then I made the other team member go back and backstock it

How do I prevent this

 

[allnew2]

How do I prevent this

You can’t really . For transition for example if they pre-tie it just make the report green but not actually setting it , the batch will continue to ask for it. The best way is drop manual caf and fix counts with exf since you can no longer do audits

 

[NKG]

You can’t really . For transition for example if they pre-tie it just make the report green but not actually setting it , the batch will continue to ask for it. The best way is drop manual caf and fix counts with exf since you can no longer do audits

Good to know

 

[allnew2]

I do not know specifically what the limit is, but I imagine it's no more than 5 minutes.

Its actually An hour , because you don’t give yourself enough time to pull , stock and backstock after

 

[PackAndCry]

Correct.

I hate to pull one of these, but at least it's maybe semi-related- would you happen to know anything about backstock from transitions from pulling right back out after it's backstocked? Even if we correct every SFQ and capacity, stuff pulls back out hours or days later even if none sold. For example, we completed the STAT transition mid last week, but even today there was a huge STAT batch for items that the accumulator should have known were already full. Are we doing something wrong? Since we drop Visual Out Of Stocks or Lows batches when we tie, is it trying to pull the items out after the fact because they "should" have been in the original POG fill, even though it let us choose the type?

 

[gsa4lyfe]

Its actually An hour , because you don’t give yourself enough time to pull , stock and backstock after

No suspect items only pop up on the report if they are pulled and then backstocked within 5 minutes I believe it is but it's definitely not as long as an hour.