MFG Accounting and real time production

radi8

Well Known Member
We are in the beginning stages of implementing the DSI Barcoding solution for inventory and production reporting.
Currently, we do manufacturing reporting via work orders the day after production is completed. After the backflush we run the manufacturing reporting reports and posts (R31802A) on a daily basis to capture the as-of inventories. But, to do this, no backflush operations can be in process.

Our production process is pretty basic where product is produced and palletized at the work station. The material handler will then scan that palletized unit and record the production. The scan will do the backflush of materials as it is recorded. Simple and effective process.

The issue resides in the manufacturing accounting of the product, since no production can be in the process of being reported when the R31802A is run. Has anyone else run into this issue? If so, how have you resolved the issue? Can anyone offer any suggestions?
 
Hi.

Do you manufacturing work on 24x7?

If not, why not schedule the R31802A to a non manufacturing time?

or make a report interconnect and launch R31802A as per Work order basis just after the scan informs the order and his bacflush

you will have tons of R31802A but you could create a custom report for listing differences or summary information at end of day and use only R31802A for variance processing
 
Currently, due to the slow time of year, we manufacture 24/5, but this will change to 24/7 during peak times.

I thought about spawning the R31802A at the same time the production is posted, but was not sure if this was 'best practice'.

The problem with doing it over a weekend (or posting multiple days) is that this batch has issues with large postings.

I will investigate the first option and move on from there. Thanks for the update and help.
 
To support a 24 hr mfg operation we fetched the code for Business Object Reservations and had developer insert it into R31802 and also all of the related work order transactions (material issues, completions, Hrs & Qtys Post, DSI scripts, etc.) that change CTSx values in any of the work order system files. I think the objects have to also be added to UDC 00/RR. I believe the event rules needed are: N550095B & N0000602. Make sure you have a good developer so they don't screw up R31802.

Process: All of the related objects check F00095 for an existing record for the DOCO in F4801, if none is found, write record into F00095 and continue with the transaction (including the business functions within R31802). Once complete, delete the record from F00095.

We also added a UBE to check for old record reservations and delete once enough time had passed that there couldn't still be activity.

Hope this helps.
 
I think implementing Object Reservations (checking for it, executing the object code only if not reserved and then releasing the reservation) in objects which do not inherently support it is a better option than trying to find a time when the operations are down.

The only care to be taken is that the scope of this enhancement should extend to include "all related objects" (as mentioned in the previous post) rather than just the R31802. In all probability, the transaction objects (Mfg issues, completions, WO entry etc.) have the functionality built in. But it's better to be safe.
 
Mfg accounting and real time production.!

Hi, greetings.! This is with reference to your old post..is it possible to run manufacturing accounting when real production is on..we have dc link and workorder completetion happ ns through dc link bsfn...and plant runs 24 7..we run manufacturing accounting at night everyday...and when we compare the amounts it shows some variance for some of batches..we are only taking into account transaction types of IC.! Any help would help.! Thanks




***********************


We are in the beginning stages of implementing the DSI Barcoding solution for inventory and production reporting.
Currently, we do manufacturing reporting via work orders the day after production is completed. After the backflush we run the manufacturing reporting reports and posts (R31802A) on a daily basis to capture the as-of inventories. But, to do this, no backflush operations can be in process.

Our production process is pretty basic where product is produced and palletized at the work station. The material handler will then scan that palletized unit and record the production. The scan will do the backflush of materials as it is recorded. Simple and effective process.

The issue resides in the manufacturing accounting of the product, since no production can be in the process of being reported when the R31802A is run. Has anyone else run into this issue? If so, how have you resolved the issue? Can anyone offer any suggestions?
 
Back
Top