We have had a few problems over the past few months in regards to the automatic backflushing of components on a production order.

We have a production order with with approximately 35 components. 34 out of the 35 are set to backflush. 1 component is set to issue (it is a lot controlled item).

The process that takes place within our "Stores" is as follows:

Maintain Outbound Data - for the item which needs to be manually issued (it is a lot controlled item)
Release Outbound Data
Report Operations Complete - we have our parameters to automatically backflush goods.
Report Production Orders Complete
Generate Inbound
Release Inbound
Close Production Order

What actually happens is that the only component to get issued to this production order is the one that was manually issued. Nothing gets backflushed.

If I look at ticst001 Actual Qty, Issue and Subsequent Delivery fields are all set to zero.

This tells me that the stores personnel are actually "zeroing out" the quantities to be issues within the session Enter material Issue for production orders. They say that this is not the case. I have set-up a test company and I can't re-create the issue.

Has anyone every had a problem like this? How can I show that these fields are actually being manually zeroed out?

Any ideas would help.
Thanks

Is this problem occurring only with this product (and/or with products that have some lot controlled items.)

Do you have backflushing working correctly on other items.

Terry

Better log a case with Baan and see if there is a solution for this problem. I did not experiece this particular problem ever, but in general if there is something going really crazy, it may have come through some bad fix for another problem, which messes up the standard behavior.

Ravi

Yes, we have many items set-up as backflushing and they work correctly. I have logged a case with Baan support ... hopefully they will be able to help.

Thanks
Barb

I also faced a problem which is slightly different from this.

In my case subsequent delivery qty doesn't get transferred to the filed 'to issue' for the quantity completed in operations.

In overcome this problem by making count point YES for the first operation in the routing used.

This is working fine, for precautions I have generated a report session, which tells me what is the difference between qty completed & qty backflushed.

U can try by making count point YES for the first operaiton it may help

Thanks, I will try that.