Ericl
Active Member
Question for you who archive with ARCTOOLS from DCSoftware.
Does your ARCTOOLS environment have its own F0011 Batch Header table, so that Batch header-to-detail relationships are maintained in the archive environment?
Do you agree that having F0011 batch header in archive environment is a good idea?
Currently, our production PRODDTA and archive JDEARCDTA environments both point to our single instance of F0011 Batch Header that resides in production.
After archiving E1 tables with ARCTOOLS, when we are signed onto the E1 archive environment, there are no batch headers because our next run of R007031 in production had cleaned up production F0011 Batch Header, deleting all batch headers for which no detail existed (because detail records had been moved to library JDEARCDTA).
We could rebuild batch headers by running R007021 in the E1 archive environment, but that effort would be erased when R007031 runs again.
We are considering putting an instance of F0011 into the JDEARCDTA library and run R007021 and R007031 over that environment.
Reference: Oracle E1: 09: Overview of Batch to Detail Integrity Report (R007031) in EnterpriseOne Financial Management (Doc ID 1378537.1)
Reference: Oracle E1: 09: Overview of Transactions to Batch Headers Integrity Report In EnterpriseOne (R007021) (Doc ID 664745.1)
Does your ARCTOOLS environment have its own F0011 Batch Header table, so that Batch header-to-detail relationships are maintained in the archive environment?
Do you agree that having F0011 batch header in archive environment is a good idea?
Currently, our production PRODDTA and archive JDEARCDTA environments both point to our single instance of F0011 Batch Header that resides in production.
After archiving E1 tables with ARCTOOLS, when we are signed onto the E1 archive environment, there are no batch headers because our next run of R007031 in production had cleaned up production F0011 Batch Header, deleting all batch headers for which no detail existed (because detail records had been moved to library JDEARCDTA).
We could rebuild batch headers by running R007021 in the E1 archive environment, but that effort would be erased when R007031 runs again.
We are considering putting an instance of F0011 into the JDEARCDTA library and run R007021 and R007031 over that environment.
Reference: Oracle E1: 09: Overview of Batch to Detail Integrity Report (R007031) in EnterpriseOne Financial Management (Doc ID 1378537.1)
Reference: Oracle E1: 09: Overview of Transactions to Batch Headers Integrity Report In EnterpriseOne (R007021) (Doc ID 664745.1)
