Over the years we have seen odd things  happening with PO lines.  PO-A  locks up, We loose PO lines, we gain PO lines.  Unknown lines appear on POs.  We have even had POs save without a vendor.  We sometimes have PO lines disappear on one PO to show up later on a different PO.  Sometimes we can be in the middle of  entering a PO and the lines we entered  just disappear.   We have saved purchase orders with multiple line only to print them and see one line.   Sometime phantom items just appear on a PO.    
 
Copying POs sometimes create a problem.   If we copy a PO and delete a few lines and save the PO it will look fine.  We can enter and exit and view the PO a zillion times and only see one line (perfect!) but when we list it to the screen we see several of the lines we deleted are there (even though you couldn't see them on the line item screen)  You cant go back and re-delete these lines because they are not on the line item screen... you only see these mystery lines when you print.        
 
From an archive search I know that similar things have happened to others.  It seems PO -A  may be a little problematic.   PO-A is fair  in DBA (difficulty whencopying POs)  and PO-A is very problematic in EVO, especially with that daily hourly internal stack error.    Stuff like this does not happen to us in SO-A or WO-A.   We copy template  in Sales Orders everyday with no problem.  We can add and delete lines with no problems in SO-A.   But we have tons of problems with PO-A  

Thoughts found from the archives..... Is it problematic to copy an open PO?  Should copying POs be reserved to only old closed POs?   Could using no location cause problems in PO-A?    I read in the archives that one user saved ever line before adding the next line.    
 
Our PO-A problems began before we print so I cant blame it on a rtm. or an rtx.
 
Any discussion appreciated.  
 
Laura