Sometimes you want to create a view in PeopleSoft which is based on another view.
Example:
View 1 (named PS_LOCKED_USR_VW) is defined as follows:
SELECT OPRID FROM PSOPRDEFN WHERE ACCTLOCK = 1;
View 2 (named PS_GET_LOCKED_NAME_VW) is defined as follows:
SELECT A.NAME FROM PS_PERSON_NAME A, PS_LOCKED_USR_VW B WHERE A.EMPLID = B.EMPLID;
When creating views using the createvw.dms script (or the REPLACE_VIEW * command from Data Mover) the situation above creates an error, because Data Mover is building views in alphabetic order. This means that views PS_GET_LOCKED_NAME_VW is built before view PS_LOCKED_USR_VW and goes into error.
Setting dependencies between PeopleSoft views
Sometimes you want to create a view in PeopleSoft which is based on another view.
Example:
View 1 (named PS_LOCKED_USR_VW) is defined as follows:
SELECT OPRID FROM PSOPRDEFN WHERE ACCTLOCK = 1;
View 2 (named PS_GET_LOCKED_NAME_VW) is defined as follows:
SELECT A.NAME FROM PS_PERSON_NAME A, PS_LOCKED_USR_VW B WHERE A.EMPLID = B.EMPLID;
When creating views using the createvw.dms script (or the REPLACE_VIEW * command from Data Mover) the situation above creates an error, because Data Mover is building views in alphabetic order. This means that views PS_GET_LOCKED_NAME_VW is built before view PS_LOCKED_USR_VW and goes into error.