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 |
|---|---|---|
| MD5 - SHA checksum of a file. | PeopleSoft Technical | 02/07/2012 - 5:29am |
| nVision Tabular Report through PIA with prompts | PeopleSoft Technical | 02/02/2012 - 10:07pm |
| Can we create an AE to mass update Position - Jobcode data? | PeopleSoft Technical | 01/18/2012 - 3:11am |
| Pay Components on job data can be defaulted and setup based on the rules? | PeopleSoft Functional | 01/05/2012 - 4:58am |
Post new comment