PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 01/31/2019 10:35 AM by  Bill Ianni
Data Cleanup Process
 2 Replies
Sort:
You are not authorized to post a reply.
Author Messages
Shannon S
Lead Application Analyst - Infor SCM
Private
Basic Member
(42 points)
Basic Member
Posts:28


Send Message:

--
01/31/2019 8:57 AM

    We are in the process of trying to get our system and data cleaned up but are unsure what jobs can "archive" the data. For example, we have several open lines that were not received from almost 3 years ago so at this point, we just need to cancel and clean up the data so the PO can be closed. 

    Can anyone share their best practices for how they keep their system clean - what jobs they run, who runs them and how often? 

    We are on v10, just migrated to 2012 servers and are hosted by Infor (AMS). 

    Thanks so much in advance!!

    Shannon 

    Kat V
    Sr Supply Chain System Analyst
    South Broward Hospital District
    Veteran Member
    (2824 points)
    Veteran Member
    Posts:966


    Send Message:

    --
    01/31/2019 9:40 AM

    I run a PO254 for the year I'm wanting to close and dump to excel. Filter for any value that isn't "closed". Those are your Open PO Headers.

    I then run a sql for those PO numbers to find the open lines.  Note: You can likely run PO223 from the get go, but we've had an issue with a bad paint.
      
    I use Don Petersen's Cancel Remaining self contained spreadsheet and try to cancel. Run PO190 and see if any of them go away. After that, it's PO64 to see what's going on and working the RNI and MNR. I have a folder called "Die In A Fire" especially for this - which is the best indication of my feelings on the subject.

    Bill Ianni
    Private
    Private
    Veteran Member
    (324 points)
    Veteran Member
    Posts:108


    Send Message:

    --
    01/31/2019 10:35 AM
    As you are hosted, paint screens and sql are probably out of the realm of possibility for you. Here is the "Lawson way" of doing it...
    First, determine a cutoff date from which your wish to archive. Hypothetically, suppose you wanted to archive eligible transactions prior to 2015...
    1. Run one of the reports that gives you open PO Lines (PO220, etc) and isolate the pre 2015 lines you are interested in archiving.
    2. Build an MS Add ins upload wizard to archive each line (that will be the V function code). This effectively closes the line without creating a financial impact. Add ins will confirm each line successfully archived or provide a message as to why it cannot archive. For example, if an item has been inactivated, it cannot archive. Solution is to reactivate the item, perform the upload again to archive the line. Then inactivate the item again. Reasons preventing archive from being successful... Inactive Agreement (or is date out of range), item, item location, requesting location, ship to location, vendor, vendor location, accounting unit, account, activity or account category (or is date out of range). These have to be fixed before the line will archive.
    You are not authorized to post a reply.