Has anyone used the Data Archive Manager process and loaded the history tables that existed in another environment? I would like to not have to have the history tables exist in the current environment if I can successfully load them to another (archive env) and remove the data from the current environment.
I have been able to get this to partially work by utilizing the non-standard sql table name feature on the record definition. I can successfully load a base history table in my current enviornment and load any non-base history in an archive specific environment that would be like a data warehouse. At this time, I'm unable to load all history tables in the archive environment.
Is there a trick in using the PSARCHIVE app engine for this type of scenario or will customizations have to be done?
Title | Under | Posted on |
---|---|---|
Component interface Error: no rows exist for the specified keys | PeopleSoft Technical | 03/15/2019 - 3:54am |
ADD 24 months starting from current month.(peoplesoft) | PeopleSoft Functional | 07/29/2018 - 8:44pm |
TRC values dropdown | PeopleSoft Technical | 04/04/2018 - 12:54am |
how to find missing sequence in GRID and print the mising sequence number while saving through peoplecode | PeopleSoft Technical | 09/11/2017 - 4:49am |
Recent comments
2 years 17 weeks ago
2 years 22 weeks ago
2 years 22 weeks ago
2 years 24 weeks ago
2 years 24 weeks ago
2 years 24 weeks ago
2 years 26 weeks ago
2 years 28 weeks ago
2 years 31 weeks ago
2 years 37 weeks ago