Michelle D.
Active Member
Hi all,
As you can see from the title, our Cardex is quite large: over 100 million rows and growing rapidly every day. I'm familiar with the Item As-Of Generation and have ours up-to-date as of this Spring. However, we can't actually purge anything because we need the transactional details. In addition to needing usage data, etc in UBE's, we have several systems outside of JDE that require as much historical data as possible. I can't just purge the data into a new table and then use both the F4111 and the new purged F4111 table because it will still be just as slow if not slower. I've just moved the data around, not eliminated anything. The as-of generation is close, but it doesn't capture a low enough level. We need the DCT as well. I was thinking of copying that program and modifying it to write the summary record at the level of ITM, MCU, LOCN, LOTN, GLPT, DCT (that's the standard functionality plus DCT). And then perhaps we could purge it.
We can't possibly be the only company with a very large Cardex where the transactional records are actually still required by users, UBE's, and other outside systems. What have others done for a solution?
Thanks in advance for sharing!
As you can see from the title, our Cardex is quite large: over 100 million rows and growing rapidly every day. I'm familiar with the Item As-Of Generation and have ours up-to-date as of this Spring. However, we can't actually purge anything because we need the transactional details. In addition to needing usage data, etc in UBE's, we have several systems outside of JDE that require as much historical data as possible. I can't just purge the data into a new table and then use both the F4111 and the new purged F4111 table because it will still be just as slow if not slower. I've just moved the data around, not eliminated anything. The as-of generation is close, but it doesn't capture a low enough level. We need the DCT as well. I was thinking of copying that program and modifying it to write the summary record at the level of ITM, MCU, LOCN, LOTN, GLPT, DCT (that's the standard functionality plus DCT). And then perhaps we could purge it.
We can't possibly be the only company with a very large Cardex where the transactional records are actually still required by users, UBE's, and other outside systems. What have others done for a solution?
Thanks in advance for sharing!