Skip to Content

Historical PO import has wrong pricing


We installed 5 years of historical data for a client for purchasing. Only the purchase orders and their basic line details were imported and then closed and no transactions were performed to these POs. This was done to assess historical prices and sources.

Unfortunately on import via DTW there was a rogue line which knocked 9,000 lines of POR1 prices out of sequence. The result was items with the incorrect price for all lines.

I cannot update prices on a closed PO. I cannot also not remove the PO legally. The archive solution will only allow me to "remove" less than half of the entries. So my plan, barring any other solution, is:

Create a new Db. Copy across the settings, master data, etc via Quick Copy.

Copy across the transactional data minus the rogue POs. But how can I avoid the painful exercise of DTW? Is there a quick method of copying transactional data across 2 databases?

Running SAP B1 9.2 PL04, on SQL.


Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

2 Answers

  • Posted on Mar 06, 2017 at 08:02 AM

    Hi Alan,

    The only way to avoid using the DTW, is to build you own import tool, however, that wouldn't really change much.

    On your next try, I recommend that you create a separate backup of the empty db, and also it might be easier to correct the existing import files, instead of leaving stuff out.



    Add comment
    10|10000 characters needed characters exceeded

  • Posted on Mar 07, 2017 at 09:46 AM

    Thanks Johan.

    Thinking afterwards, this would require an import of the likes of existing delivery notes, etc which would need to be closed off prior to import similar to a go-live. Would I be correct? I don't see copying across the journal entries as well as all open and closed documents being feasible? Or have I got tunnel vision right now?


    Add comment
    10|10000 characters needed characters exceeded