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.

To avoid this situation you can specify a Build Sequence on a view. PeopleSoft builds views according to this sequence, so first all views with sequence number 0 (zero) will be build, then all views with sequence number 1 etcetera. You can find the Build Sequence option on the properties of the record, on the Record Type tab:

So in case of the example, if you specify a Build Sequence number of 0 (zero) on view 1 and a Build Sequence number of 1 on view 2 the creation of these views will no longer create an error.

 Viewed 11162 times by 2770 visitors

Posted by: Frank Kortekaas (8 post(s)).