How to handle cases where configuration tables like PS_GVT_POI_TBL or other feature sets that don’t apply to your company are not being implemented. In many cases complete dimensions will be empty and look-ups in fact jobs will fail.
The nicest thing about PeopleSoft after the whole PIA Metadata-driven interface and its impact on data quality is how meticulous PeopleSoft engineers are about documentation and sticking to naming standards, here’s a simplified diagram of the wharehouse architecture and the naming standard for objects in each section of the schema:
Today I got an error that reads like this: JobControl (@<JOB_NAME>): Controller problem: Error calling DSSetParam($<PARAMETER_NAME>), code=-3 [ParamName does not reference a known parameter of the job] After a quick debug/issue tracking session on Director I found out that one of the jobs in my master sequence was missing all of our standard parameters with […]
In order to move PeopleSoft HRMS9.0 data into EPM9.0 your team will need to deploy the ETL “Integration Update” for HRMS9.0 (HRMS=HCM). IU jobs need to be deployed to a separate project if you are running on linux.
Not having to do all the leg work necessary to arrive at table-level data lineage in the PeopleSoft EPM Warehouse is a great testimony to good documentation and a great culture back there at big PS….
We had one or two issues related to DataStage ETL maps that were skipped when we applied MP5 and multiple bundles on our development environment. To prevent this issue from happening again I decided to re-install all of our ETL maps from scratch using a Sharepoint wiki to keep track of the update level applied […]
Peoplesoft EPM ETL Configuration
Shangye Zhineng RSS Feed